Database Info

Updated 3-3-09 - JFv1.43 for UK RC9 firmware! also ADP 1.5 post 2

Official APD1.5 image in Post 2
Here's the new JFv1.43 RC9 for all you UK users. Enjoy!
--- announcement for JFv1.43 Holiday
New! JFv1.43 is a bugfix release for the Holiday (ADP1.1h) version. This release fixes the issues most people were having with Latitude hanging after clicking "I agree". More info on my blog.
The links below have been updated with the new versions.
--- announcement for JFv1.42
The ADP1.1h version of JFv1.42 is out! This is based on the new ADP1.1 OTA that was put out this morning. I've also released a JFv1.42 version of RC33, that fixes the issue with adb not being enabled in recovery mode. You can find more details here
The links below have been updated with the new versions.
--- announcement for RC33
The RC33 version of JFv1.41 is here! Links are below. It is essentially the same as the RC30 version, as far as my changes are concerned. You of course get all the goodies included in RC33.
Note: RC33 contains a radio update. I chose not to include this in the RC33 update itself, because I personally don't want it re-flashing the radio every time I apply this update. Here (md5: cf8714d273fb0274574d9e3831e11fdd) is a separate update that *just* flashes the radio. You only need to install this update once (unless you happen to flash an nbh at some point in the future, in which case you should re-flash the radio afterwards).
To check if you have the new radio, go into the about phone screen in settings and check the baseband info. It should end with 1.22.14.11
note: I have no clue what the differences are in the new radio. I just assume they are good, and that it's better to use the new radio than the one from RC30.
note: (yes, I love Notes ). You shouldn't need to do a wipe if you're going from RC29 or RC30 to RC33. I've even had reports that you don't need to do a wipe going from ADP1.1 to RC33. Give it a shot if you want, and let us know if you had to wipe. Don't forget to do a nandroid backup first
note: (couldn't resist). The first/initial boot after upgrading to RC33 make take a minute or two. Just give it some time before concluding that you need to do a wipe.
------------------------
(original release annoucement for JFv1.41)
This version contains... *drumroll* multi-touch support! Thanks to lukehutch, zinx and ryebrye, this build allows android applications to receive multi-touch events. The built-in browser now supports multi-touch zooming! It also includes an "Auto-Rotate" setting that you can enable, to allow it to change screen orientation, based on the orientation of the phone. You can turn on auto-rotate in the browser settings (it's off by default).
See lukehutch's blog post for more information about the new multi-touch support, as well as a few other demo multi-touch apps he created that you can try out after installing JFv1.4. He also mentions a few issues that are present in browser, that you might run into while playing with zoom.
Other changes of note for JFv1.41 include:
a console in recovery mode. You can press alt+x to exit out of the recovery program and go directly to a console.
the ADP1 build is now based on the ADP1.1 firmware. See this thread for information about the changes in ADP1.1
the ADP1 build now includes .odex files for all of the system apks and jars. This means that you will have more space available in /data for all of your apps and caches, although less space available in /system
busybox's vi should now save files correctly, instead of saving them as blank files
One thing that I would like to point out about the ADP1.1 build is that it allows you to skip the initial google registration. This will make registering over wifi painless. You just click the "skip registration" button in the registration app, enable wifi in settings, then open the registration app again by trying to access one of the google apps (gmail, market, etc.), and then you can register over wifi.
Downloads:
ADP1.1: (md5: 076ba12c3e733805ba1c865ab48d370c)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.43/JFv1.43_Holiday.zip
http://jf.andblogs.net/2009/02/11/jfv143/
RC33: (md5: 6ecf0ea8175e1aece8a770253447b6a8)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.42/JFv1.42_RC33.zip
http://jf.andblogs.net/2009/02/10/jfv142/
RC9: (md5: 5a722ad92c9dd1081987b2ad9814111f)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.43/JFv1.43_RC9.zip
http://jf.andblogs.net/2009/03/03/jfv143-rc9/
In the console in recovery mode, there are a number of "special keys" that you should be aware of:
Code:
ctrl search
caps lock menu (on the keyboard)
arrow keys call + w,a,s,d
change virtual console call + 1,2,3...0
scroll console home + w,s
page up menu (above the trackball) + w
page down menu (above the trackball) + s
home menu (above the trackball) + a
end menu (above the trackball) + d
escape back
reboot menu (above the trackball) + search + backspace
Also, you can type "reboot" to reboot, and type "recovery" to go back into the recovery program.
JFv1.41 can be installed in the usual way. Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. If you are switch between versions, e.g. from RC30 to ADP1, you must also do a wipe in recovery mode (alt+w). This will clear all your data/settings/apps, and you will have to re-register once it boots back up. If you are staying on the same build, i.e. from JFv1.31 RC30 to JFv1.41 RC30, then you shouldn't have to do a wipe.
NOTE: If you are on the stock ADP1 image, you will need to upgrade to JFv1.31, then boot normally at least once, before upgrading to JFv1.41, to keep from having to perform a wipe. If you try to go from stock ADP1 -> JFv1.41 directly, you will have to do a wipe.
NOTE: If you end up with 2 Superuser whitelist apps in the app menu, you can uninstall one of them in Settings->Applications->Manage Applications. There will only be 1 that is uninstallable, so don't worry about uninstalling the wrong one.
Note: To install these updates, you need to have a recovery image that uses test keys. If any of the following are true, you most likely have a recovery image that uses test keys
you have installed my modified recovery image in the past
you have an ADP1
you currently have one of my modified firmwares installed
If this is your first time installing one of my firmwares, you may be interested in the other changes that have been made in previous versions, which are included in this version. Some of the notable features include:
Many more commands are available to use on the terminal. busybox is included, to provide standard commands like cp, grep, less, more, vi, sed, cp.. etc.
A secure way to get root access, through Koush's superuser application. To get root, open up terminal emulator and type su. A new window will open asking if you want to allow root access. Click "Yes" or "Always", and it will go back to the terminal emulator, and you'll have root access
A number of useful kernel modules that you can use. For example, ext2, cifs, and a host of others
A full phone backup utility. Boot into recovery mode with home+power, and then press alt+b to perform a backup. It stores the backup as .img files in a subfolder of the nandroid folder of your sdcard. To restore the backup, you have to have the engineering spl or hardspl installed, and then flash the images with the fastboot utility
ota updates are disabled. This is to prevent t-mobile from automatically updating your phone with a new update that removes your root access.
some applications that are missing on RC8 (the uk version) have been added. For example, the voice dialer and the amazon mp3 store.
when you connect to the phone using adb, you have root access
I've attached a full changelog vs the official builds for each version.
Here are the updated Build Environments for JFv1.41. These can be used to create an update identical to JFv1.41, or to create one modified to suit your tastes/preferences. You can find more info about the build environments over at my v1.31 post
ADP1.1: (md5: ce591333f2252d805c5eaccae332f5e7)
http://jf.odiness.com/v1.43/JFv1.43_Holiday_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/02/11/jfv143/
RC33: (md5: b3b0bc89c4b417b6ce6728fd9cc2c7fc)
http://jf.odiness.com/v1.42/JFv1.42_RC33_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/02/10/jfv142/
RC9: (md5: 0d0845f85382e5689f015a2904f928a0)
http://jf.odiness.com/v1.43/JFv1.43_RC9_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/03/03/jfv143-rc9/

Official ADP1.5 image
JesusFreke’s AndBlog
The official 1.5 firmware is here finally!
When is your 1.5 coming out?
May 1, 2009
The answer is… wait for it.. wait for it..
NOW!
If only i had a nickel for every time someone asked me that over the last week or two
This build is based on the official HTC ADP1.5 image. You should install the 1.5 radio from that HTC page before using this build.
Some of the important changes/features
* I’m now including a much better Superuser app, courtesy of zinx
* I’ve rebuilt the kernel and enabled netfilter support, to allow tethering.
* You can see/download both paid and protected apps in the market
* Luke’s multitouch kernel patch and browser patch have been ported to the .27 kernel and 1.5 browser.
* Support for the “apps to sdcard” hack. There’s not a separate “apps to sdcard” build. You can use the same build whether you are doing apps to sdcard or not. Thanks to haykuro for explaining how he’s done this in his images, so I can make my builds compatible. See here for a tutorial on setting this up.
* I’m not including a recovery image in this build. I ran into some snags getting all of the recovery features to work with the 1.5 recovery image, so I’ll forgo that for now. If you don’t have a spiffy recovery image yet, I’ve packaged up the most recent recovery image from JFv1.43 as a separate update.
If you are already running a “rooted” build (ADP/mine/haykuros/the dudes/whatever), it is available for download via the jf updater app (available on the market). If you don’t see it, open up the app settings, and choose either ADP1 or “All the updates” for the “System Mod Version” setting.
Or you can always download the update.zip file below and install it yourself. If you have a G1 and this is your first time installing a community firmware, you’ll need to follow any of the multitudes of tutorials out there for rooting your phone.
You can try to upgrade without a wipe, but if you run into any problems (for example, su/Superuser doesn’t work), you’ll need to perform a wipe. If you don’t want to wipe, take a nandroid backup before upgrading, so you can revert back to the backup.
JFv1.50 ADP1.5
JFv1.50 ADP1.5 Build Environment
JFv1.50 ADP1.5 CHANGES
JFv1.43 Recovery Only

Nothin but the best from the best! Works great man!
Thanks to you and everyone else that helped make this possible.
Stericson

Awesome! Great job mate, about to install.

OMG YES!!!!

Third!! Great Job JF, LukeHutch, Zinx, RyeBrye and everyone else who helped with this. Working great for me!

superb
will give it a go in a few hours
u've got to be the top supporter of the android community.
keep it up!!

Awesome!
Couldn't wait for a new update. You delivered like a champ!
Thanks peeps!
EDIT: Just a question, do I need to format my SD again like the other post says?

hey JF
for each of your releases you have said "If you are staying on the same build, i.e. from JFv1.31 RC30 to JFv1.4 RC30, then you shouldn't have to do a wipe" but every time i install one of your builds i get stuck with an infinite boot loop and have to perform a wipe. Any ideas? btw ive only used your adp builds on an adp

Great job, to you and all who contributed. Works great so far, loving the multi-touch zoom.

Installing now, i'll post in a sec when it works
Edit: of course, it works great!! multitouch is something I would have never expected
Edit2: just installed rc33 and the radio update, everything works great . Posting from it now!

yesssssssssssssssssssssssssss

do the jf rc30 1.3 themes work with the new update or we going to need to update the themes

awesome job everyone! installed and loving it. thanks for all your hard work

Manacit said:
Installing now, i'll post in a sec when it works
Edit: of course, it works great!! multitouch is something I would have never expected
Click to expand...
Click to collapse
Nobody expects the Spanish Multi-Touch Inquisition!

kron2 said:
do the jf rc30 1.3 themes work with the new update or we going to need to update the themes
Click to expand...
Click to collapse
The themes for RC30 and RC8 should work. The only thing you have to watch out for is if the theme overwrites Browser.apk, you'll lose the multi-touch browser.
The themes for ADP1 will most likely need to be updated to work with ADP1.1 unfortunately.

This Is Great!

thx jf and the update works great

ok so i need to resign my browser.apk before doing the template or not? thank the best release yet
JesusFreke said:
The themes for RC30 and RC8 should work. The only thing you have to watch out for is if the theme overwrites Browser.apk, you'll lose the multi-touch browser.
The themes for ADP1 will most likely need to be updated to work with ADP1.1 unfortunately.
Click to expand...
Click to collapse

..wow
/10char

[Windows] Make update.zip of Google apps from NAND dump! Works w/ 1.6 and new Market!

GApps2zip
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1. This update.zip should be flashable on any build and it should work without a problem, but since I'm just a n00b sophomore in highschool, I am naturally poor and can't guarantee anything.
Because there are already a few alternatives to this for Linux and the majority of Android users use Windows, I decided to make this a Windows-only batch script.
You MUST have the Java Runtime Environment installed in order to run this script! The signing utility requires Java and you won't be able to flash an unsigned update. If it doesn't work even if you have Java, you may have to reinstall Java as it is not in your PATH variable for whatever reason.
UPDATE: Updated and, as far as I know, should now work fine with the 1.6 developer images from HTC as well as personal NANDroid backups of most all 1.6 Android ROMs.
INSTRUCTIONS
1) Either do a or b. It is advised to use a personal NANDroid backup (b) as it does not violate any licenses, but it has not been testeda) Google for the file "signed-dream_devphone_userdebug-img-14721.zip" It should be on the HTC support page for the ADP 1, but it wont be the first result in Google. It is not advised to use this method as you need to agree to a license prohibiting modification of the file in order to download it. Rename the file to "backup.zip"​b) Restore to a regular build that has all of the Google Apps (like the regular OTA cupcake update) and then run a NANDroid backup. Then make a zip file that only has the system.img file from the NANDroid dump and name the zip "backup.zip"​2) If you haven't already, unzip the entire contents of the gapps2zip.zip file into a directory. For sake of simplification, I am assuming it is unzipped to C:\gapps2zip
3) Place the "backup.zip" file in the same directory as the GApps2zip.bat file (C:\gapps2zip) and DON'T rename it or unzip it.
4) Open up a command prompt window (Hit Windows + R, type in CMD, then click OK)
5) cd to the directory in which the GApps2zip.bat file, utils directory and the backup.zip file. For example:
Code:
cd C:\gapps2zip
6)Type in "GApps2zip.bat" (without the quotes) and hit enter. Watch and wait.
7) If all goes well, you should have an update_gapps.zip folder in C:\gapps2zip. Put it on your SD card, make a NANDroid backup, and flash after flashing an AOSP (Android Open Source Project) build that doesn't include the Google Apps.
Credits
Cyanogen for his hard work and dedication
Maxisma for a similar script on which this is based
Google for their ingenious ideas (although their legal department can be a pain)
Everyone who is willing to test this script out
Everyone else xD
Redistribution
Feel free to redistribute the archive wherever you like, but please give me credit along with Maxisma and do not modify the archive in any way.

Great job unk!

amgupt01 said:
GApps2zip - Created by Ankush Gupta (twitter.com/unkzdomain and unkzdomain.com)
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1. This update.zip should be flashable on any build and it should work without a problem, but since I'm just a n00b sophomore in highschool, I am naturally poor and can't guarantee anything.
Because there are already a few alternatives to this for Linux and the majority of Android users use Windows, I decided to make this a Windows-only batch script.
You MUST have the Java Runtime Environment installed in order to run this script! The signing utility requires Java and you won't be able to flash an unsigned update.
This script does NOT work on a build that includes the new market as there are some incompatibilities with the files for it and the ones provided by HTC (namely the MarketUpdater.apk for the new market). This is pretty much doesn't matter however, because all AOSP builds will not include ANY Android market anyways.
INSTRUCTIONS
1) Google for the file "signed-dream_devphone_userdebug-img-150275.zip" (It should be on the HTC support page for the ADP 1, but it wont be the first result in Google)
2) If you haven't already, unzip the entire contents of this zip file into a directory. For sake of simplification, I am assuming it is unzipped to C:\gapps2zip
3) Place the "signed-dream_devphone_userdebug-img-150275.zip" file in the same directory as the GApps2zip.bat file (C:\gapps2zip) and DON'T rename it.
4) Open up a command prompt window (Hit Windows + R, type in CMD, then click OK)
5) cd to the directory in which the GApps2zip.bat file, utils directory and the signed-dream_devphone_userdebug-img-150275.zip file. For example:
Code:
cd C:\gapps2zip
6)Type in "GApps2zip.bat" (without the quotes) and hit enter. Watch and wait.
7) If all goes well, you should have an update_gapps.zip folder in C:\gapps2zip. Put it on your SD card, make a NANDroid backup, and flash after flashing an AOSP (Android Open Source Project) build that doesn't include the Google Apps.
Credits
Cyanogen for his hard work and dedication
Maxisma for a similar script on which this is based
Google for their ingenious ideas (although their legal department can be a pain)
Everyone who is willing to test this script out
Everyone else xD
Redistribution
Feel free to redistribute the archive wherever you like, but please give me credit along with Maxisma and do not modify the archive in any way.
Click to expand...
Click to collapse
when it asks u to replace system.img, do you click yes or no?

Looks interesting ill test it out later

Guyver75 said:
when it asks u to replace system.img, do you click yes or no?
Click to expand...
Click to collapse
You click Yes. You shouldnt have extracted the zip though, but it won't make a difference anyways.

Looks interesting ill test it out later

amgupt01 said:
You click Yes. You shouldnt have extracted the zip though, but it won't make a difference anyways.
Click to expand...
Click to collapse
oh ok, oops. i clicked no. guess ill have to redo it

ok trying to understand this. From what i get is you download, Lets say cm 4.2 without google (made up rom dont go looking for it)
then you flash that to are phone.
next when flash update_gapps.zip
Then we will have a cm rom with google apks?
And in returns the update_gapps is kinda like a theme only adding the needed files?

xile6 said:
ok trying to understand this. From what i get is you download, Lets say cm 4.2 without google (made up rom dont go looking for it)
then you flash that to are phone.
next when flash update_gapps.zip
Then we will have a cm rom with google apks?
And in returns the update_gapps is kinda like a theme only adding the needed files?
Click to expand...
Click to collapse
Exactly. The only thing is that since this uses an official, legal source, it doesn't include the new market and stuff...

Ok cool but once 1.6 adp1 is out we will have to update the script and do this again?

amgupt01 said:
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1.
Click to expand...
Click to collapse
I applaud your efforts to help the community. Many thanks.
For those who think this is proof modding and this community will live on, think again. What he's doing aids and abets violation of Goog's rights. This thread will be locked and the links taken down. Welcome to the new world of Android.

xile6 said:
Ok cool but once 1.6 adp1 is out we will have to update the script and do this again?
Click to expand...
Click to collapse
Well, provided that HTC distributes ADP 1.6 the same way as they are 1.5 and that the file dependencies for closed-source apps are similar, we could just reuse this same script with maybe a few minor modifications.

ytj87 said:
I applaud your efforts to help the community. Many thanks.
For those who think this is proof modding and this community will live on, think again. What he's doing aids and abets violation of Goog's rights. This thread will be locked and the links taken down. Welcome to the new world of Android.
Click to expand...
Click to collapse
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.

@ amgupt01
Thanx now all we got to do is let the builds continue.

great job mr. sophomore, you should get together with cyanogen on this although i'm sure he's probably going to do something similar.

is it safe to sign in to google with the newly created update_gapps2zip?

amgupt01 said:
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
Click to expand...
Click to collapse
I think the issue is that Google doesnt want its closed source apps put on non google-experience phones. This guy's method allows just that.
Cyanogen's method (from what I can gather) is to run an app on your phone that backs up the apps that you have on your phone (presumably licensed copies that you acquired when you purchased your phone, or during an OTA update), and then restores them after you run his barebones ROM. In this manner, you are only using backed up copies of software you are entitled to use.
I read somewhere (maybe in Google's C&D? I'm to lazy to go look) that Google does not allow these applications to be copied or extracted or something to that affect.
Honestly, why on earth would we expect them to react any differently?! This is a growing pain. We will all be better for it when its passed.
Here's how I'm planning on riding this out:
1. When Cyanogen releases 4.2, I will unroot my phone, and get the most recent OTA update from Tmobile.
1. Install Cyanogen's 4.2 ROM, using whatever method of installation is required to back up my closed source applications and restore them.
2. Continue to update Cyanogens ROMs this way until we discover that our old closed source apps are no longer compatible with our state of the art ROM.
3. Begin to seek out alternative apps, or check progress of the new "Open Android Alliance" or whatever those guys are calling themselves since this whole fiasco started, to see how feasible that option is.
4. Buy a new phone? I mean, how far down the road are we talking here?! And yes, when the time comes, assuming Google doesn't do something completely draconian that makes us pine for the good old days when they sent a C&D to Cyanogen, it will be another Android phone (subsequently rooted, of course)
I don't really see another legal option.

Code:
Cyanogen on twitter
So I think I've come up with a solution that should work and not violate any licenses. Just need to polish it up a bit.about 14 hours ago from twidroid
Thanks for this script.. i am amazed of how fast the community is getting up from the C&D .... Open Android Alliance is kicking off, Maxima is already out with a NO Google ROM, and this script, to get google's apps... wonderful...

amgupt01 said:
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
Click to expand...
Click to collapse
amg, I'm worried on two fronts.
1, HTC is redist'ing Goog bits. They may very well get a c&d. I can't imagine HTC has a license to freely distribute them to anyone and everyone. I have to believe the license is for use on HTC hardware, not any user worldwide as download and extraction would allow.
2, you are aiding in the grabbing of those bits that a user may not have license to.
Granted, I know the vast majority of us have license. But there a few non-Goog experience phone owners around here. I suspect the mods will lock down.
But again... I think that would be wrong. We have license to the bits and grabbing them from HTC is not a violation IMO. But we'll see.
Thank you.

amg,
From the HTC license page when you download:
-----
You may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the Google Software or any part of the Google Software. You may only load the Google Software onto the Android Developer Phone 1, and except in conjunction with third party software that makes up the Android system image, you may not combine any part of the Google Software with other software, or distribute any software or device incorporating a part of the Google Software.
-----
So it's clear this is illegal. I think HTC will have to pull this down sooner or later as widespread extraction starts.
btw, I think you're fine. HTC will hear from Goog and this thread will be locked. But otherwise don't worry.

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Desire] (01/29/2011)

Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.

Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.

Desire aint listed??

I don't have any roms using it in Desire...hence why I'm posting this. But:
Kurt666
- For testing on Pay's ROM for Desire v1.4 (HTC Desire)​
Click to expand...
Click to collapse
So there is one rom that is tested with it.
I've checked a good segment of the roms here, and it should work just fine, especially the 2.7.5 version (as the swap, dalvik-cache and the applications are all separate functions now).
I'm trying to expand the program's scope. I have six different platforms that run it (21 roms total) and I have one Desire rom tested...but none actually using it (my fault...should've expanded this a month ago).
Nekromantik said:
Desire aint listed??
Click to expand...
Click to collapse

Backing up just now my Open Desire 1.5 on nandroid.
Going to be your guinea pig for Open Desire (AOSP)
I will paste the logcat output of my first boot (if there will be any)

Will try to test on modaco r3.1, wish me luck
Sent from my HTC Desire using Tapatalk

well, it seems that it changed... Nothing.
http://pastebin.com/6D346gwX
Maybe the chef was already using your script?

So it didn't work?
Sent from my HTC Desire using Tapatalk

antz88c said:
So it didn't work?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
It booted in the same time that it booted without applying the tremor script, and I think that the logcat was quite similar too.
And the free space reported is the same than before.
So, it didn't work, or it was already working before
EDIT:
I decompressed the script inside OSx, and I looked inside folders.
Well, it seems that the script didn't run at all, since I have no "a2sd" neither "app2sd" on my /system/bin.
REEDIT:
I ran it again, now it seems that it actually ran.
I will provide my new pastebin later

http://pastebin.com/mx3PsHwZ
First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems
Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj

Boot loop only here, nandroid back to my previous ROM.
Sent from my HTC Desire using Tapatalk

antz88c said:
Boot loop only here, nandroid back to my previous ROM.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Please provide logcat, otherwise your test wil be useless to the developer.

This sounds very interesting, and I would like to try and help when I can, which probably won't be for a couple of days.
But........for when that day comes.......how do I do a logcat?
Sorry, I am still relatively new to the whole Android thing.

StuMcBill said:
This sounds very interesting, and I would like to try and help when I can, which probably won't be for a couple of days.
But........for when that day comes.......how do I do a logcat?
Sorry, I am still relatively new to the whole Android thing.
Click to expand...
Click to collapse
yes, i got a bootloop on defrost 1.8.
how to do a logcat?

bradputt said:
yes, i got a bootloop on defrost 1.8.
how to do a logcat?
Click to expand...
Click to collapse
decompress android sdk (check on google for the sdk package, is quite small), then go inside the "tools" folder (I assume you have already your drivers installed).
then go on command prompt, and
Code:
adb logcat
will show the logcat.
Code:
adb logcat > bootlog.txt
will create the boot log (you won't actually see anything on screen since the output is redirected on the txt file.
You can:
start your phone
type adb logcat
CTRL+C when the phone is booted.
It will automatically stop if a reset occurs.
Then you go on pastebin (search on google) and paste the txt inside the pastebin.
And you can provide here simply the pastebin url that you can find after the submit button.

Nope...I can tell that's not my script. That must be what's already in Modaco...which means it's another file I haven't caught on the renaming script.
Are you using Modaco?
gatsu_1981 said:
well, it seems that it changed... Nothing.
http://pastebin.com/6D346gwX
Maybe the chef was already using your script?
Click to expand...
Click to collapse

Last time I saw that message, root wasn't working correctly. At least it wasn't working correctly on my phone.
Is there something different relating to root on these phones? Does the boot sequence have root access to /system (or is this phone have nand protection on it? I know the Evo has that but can be circumvented).
That part is just a piece that moves other apps2sd/dalvik-cache/zipalign programs so they don't interfere...the 2.7.5 Preview Fix 2 also removes those files during the flashing process, so that part really is only a failsafe.
The main program comes after that part (04apps2sd for busybox run-parts, a2sd for direct run).
gatsu_1981 said:
http://pastebin.com/mx3PsHwZ
First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems
Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj
Click to expand...
Click to collapse

The important piece is the part after the realignment program...the one that starts with:
[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1
The lines after that one is the Apps2SD portion.
gatsu_1981 said:
http://pastebin.com/mx3PsHwZ
First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems
Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj
Click to expand...
Click to collapse

tkirton said:
The important piece is the part after the realignment program...the one that starts with:
[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1
The lines after that one is the Apps2SD portion.
Click to expand...
Click to collapse
I can't understand what you mean.
Do you need some other line from adb logcat output? Since there is no more lines after the * line it just keeps resetting.
Or are you telling that it's installed? If so, why it keeps resetting our phone on froyo?
If I can help please send more flashable version or update this thread, I already have my nandroid so testing it for you will be very quick.

EDIT: double post...sorry.

[REVISION] [TOOL/LIB] Flashy v2.0.2 Alpha GUI Flasher/remote control using .net/mono

This is my revision of the Flashy tool, look below for the original thread and an explanation what it's meant for.
Don't know if it's worth the effort, but made a repo at github aswell, here is the link, any feedback is much appreciated.
For commiters, pls keep the master branch clean to "stable" builds, for commiting while development the workinprogress branch is ment for.
Changelog is below.
Will split it up to source changes and tool changes soon.
theq86 said:
Hello devs,
I made a tool to quickly flash image files to the device. it uses fastboot and adb as backends, but offers a UI to do the work. This is not only a handy GUI tool, but a full object oriented library for the .NET Framework, which the tool builds upon. You can use the wrapper library to access the most important adb and fastboot commands from within any .NET program, thus building new real applications instead of batch files. it is up to you if you want a console application, a gui or even a windows or webservice, as long as you program in a .NET environment.
Flashy is just an example what is possible to do. You can use it to flash any file to your device without having to employ the console or write fastboot commands.
Recent changes:
* added splashscreen flashing capabilities to the library and the flashtool
If you found bugs or have improvement ideas, feel free to write in this thread.
Attachments:
1) the handy Flashy-Tool
2) The .NET Wrapper's source code. Public domain, feel free to download, change, compile, sell for a million bucks or print out for your grandma
3) The Flash Tool's source code, also PD
Click to expand...
Click to collapse
Original Thread

Changelog:
v2.0.2_ alpha
Workers administrate themselvs now
Library documented (can be extended)
Gui partialy documented
fixed fastboot output
splited timouts for fastboot and adb (finetuning needed)
added readline method to base of adb and fastboot
changed return type of execute methods, stream isn't returned anymore, readline replaces it
some minor changes
v2.0.1_ alpha
Windows & Mono support (Unix/Linux/MacOs)
Redesigned most parts of the library and gui (still something left)
Cleaned up sourcecode
Added adb shell support with custom commands (atm no preset, you have to type them yourself)
Added logcat support with custom filters (atm no preset, you have to type them yourself)
Custom path to adb (atm not split up in two paths for adb and fastboot) can be set
Check if adb and fastboot are present inside the directory, otherwise fastboot is disabled
Possibility to disable fastboot at the gui
Deleted most of the Messageboxes, using textbox at the mainwindow instead
Synchrone and Asynchrone (atm buggy, maybe using another approach for it) processing at the library, Gui asynchrone (library is still used synchrone for stability, but uses the output stream directly [works fluid with logcat])
Choosen adb-path is stored for following starts
and everything else i missed, sry it's late and i'm tired^^

reserved for future

did somebody already flash any spashscreen to DS?

docertabum said:
did somebody already flash any spashscreen to DS?
Click to expand...
Click to collapse
Yes did it now, but had a little bug, the gui tried to execute the command with adb instead of fastboot, my fault, shouldn't change (or copy and paste) code as late as i did yesterday, sry.
Added the fixed version.
Unfortunately there is no output of the progress shown atm (even if the same stream is used as with adb) but it works, have tried it myself (you need an nb file like usual when you try to flash a splash with fastboot, will also look if i can change this [convert it internal]), will take a look at it later, now it's first time to go home^^

Tectas said:
Got a little finding for you, the gui itself isn't that big impact, but i really like the library to setup your own Applications, even if it wouldn't be that much effort to build one yourself, it's nice to have.
In the op isn't mono mentioned, but it should work as well, will test it later.
Hope you enjoy it.
Original Thread
Added changelog, binarys and source of my revised version, hope you enjoy it
Click to expand...
Click to collapse
eheh... Always wanted to learn C# or derivatives. Maybe this is the incentive I needed. Terrific work, thanks mate!
Cheers

lowveld said:
eheh... Always wanted to learn C# or derivatives. Maybe this is the incentive I needed. Terrific work, thanks mate!
Cheers
Click to expand...
Click to collapse
If you want to, I can create a git repo for it
If it's pushed further like I want to, it will grow up to an allround tool.
Ah, but missed to document the source yet, will catch up later
Swifted from my Desire S far away from my PC

New version is up, enjoy it
Swifted from my Desire S far away from my PC

Added github repo, latest binary zip is also uploaded to it (but no changes since yesterday yet).

Just to keep you updated:
Been working on full async support for the library, it's not finished yet, (but not much is left).
Implemented it with almost the same pattern as in the GUI and just as a side node, in future it will always run async, if you use sync mode, it just fakes it by not starting more then one async process at the same time.
If someone wants to take a look at the current source, the workinprogress branch on github is at the current state.
Next I will take a look at is, more fastboot commands and goldcard creation (thx to the voters).
Fastboot is easy to implement and will come soon, the goldcard will take some time, because I need to figure out how I can generate the image.
Additional to this I will give the mainwindow a small beauty cure (I don't like the radio buttons^^) and will implement the interactive shell (to be honest, I already integrated the possibility in the lib, but haven't tested it yet [yes that's what I voted for ]).
And the last thing on my schedule is (except of bugfixes, if needed) the ability to store from the user flashed images or nb files, that he can choose them from a list if he needs one of them once more (i.e. Boot.img after a romupdate)(first step to recovery feature ).
Other things will also come for sure, but that's enough by now I think^^
If someone else wants something else, or got something that may should be on the list too, pls tell me.
Swifted from my Desire S far away from my PC

[ROM][4.2] Android 4.2 for Nerds

Here is my new ASOP distribution. I made no changes to the GUI but unlock all hidden Features and install BusyBox and a terminal. Superuser.apk doesn't work anymore with 4.2, so I have written quick-and-dirty replacement. But be warned: It gives alls apps root rights without asking. Install only apps you really trust. There is a new command "setup-swap". You can create or delete a swap file with it, if you need more memory. "install-gapps" doesn't work currently.
The "install-gnu" plug-in is much bigger now. It supports I18N and UTF-8 now. Your terminal is in the same language you set in the Android config. And I have added more programming languages, too. So if you want a real GNU environment on your Tablet, just type "install-gnu" on the command line. A Bluetooth keyboard is highly recommended.
Because of the December bug here is version 4.2.1 now:
Mirror 1
Mirror 2
My public key is here and here is the signature.
You install it like a factory firmware, so you need "fastboot" in your "PATH", then run "flash.sh". Warning: All data will be overwritten.

Supersu
x-alina said:
Superuser.apk doesn't work anymore with 4.2, so I have written quick-and-dirty replacement
Click to expand...
Click to collapse
Rom sounds good, might flash it, but about superuser, it hasn't worked very well since ICS was introduced (IMO), i have alsways used SuperSU, although 4.2 doesn't have full multi user settings on SuperSU yet, it has been patched to work. Just sayin XD
Also, have you thought about making some of these things flashable (like the install GNU and setup Swap) as I would love these alongside Paranoid android XD
Awesome stuff though =D

Thanks for your work! will test this out!

Nice work, will test it in some time.

All Mirrors are up and running now.
Sorry for the inconvenience.

Android 4.2.1 for Nerds
Because of the December bug here is version 4.2.1 now:
Mirror 1
Mirror 2

I'll test and sent you feedback...

x-alina said:
Here is my new ASOP distribution. I made no changes to the GUI but unlock all hidden Features and install BusyBox and a terminal. Superuser.apk doesn't work anymore with 4.2, so I have written quick-and-dirty replacement. But be warned: It gives alls apps root rights without asking. Install only apps you really trust. There is a new command "setup-swap". You can create or delete a swap file with it, if you need more memory. "install-gapps" doesn't work currently.
Try this mod for root permissions. http://forum.xda-developers.com/showthread.php?t=1663222
Click to expand...
Click to collapse