Posting tweet...
Powered by Twitter Tools.
I’ve released v1.2.1, which is mostly a bugfix release to v1.2. There are a few performance improvements and enhancements in there as well.
As usual, you can grab a copy on the googlecode download page
After lots of hard work over the last month or two, smali/baksmali 1.2 is out!
The major new functionality in this release is that baksmali now supports deodexing without the help of deodexerant! It also has a new “register info” feature, to show the register types in the disassembly, and numerous minor fixes/changes/enhancements/tweaks/(and probably bugs)
As my Christmas present to everyone, I present smali/baksmali v1.1
This version has significant new functionality, and is much better able to handle the larger framework files that are floating around. There are a number of bug fixes as well.
As usual, you can grab the new versions from the googlecode download page
Now that the nook softroot is out, I’d like to take a moment to explain the structure of the updates, the nook bootup process in general, and how the softroot came about.
It’s 1.0. Yep, sure is. Go get it here.
Why should you get the new version you ask? Well, it’s been spiffified, of course. The new spiffiness includes:
And one final note: deodexerant will *not* work on 2.0 devices. Once the 2.0 source is released, I should be able to build a new deodexerant binary that will work on 2.0.
odex files getting you down? Now you can do something about them!
For the first time ever, with smali/baksmali 0.96, and some help from deodexerant, you can get rid of that optimized dex odor from your rom.
It slices! It dices! It turns odex files into .smali files, capable of being assembled into normal classes.dex files! And all for the low low price of $0.00. Can’t afford $0.00 right now? That’s ok! I guarantee I can get you low monthly payments of $0.00 for 12 months (offer good while supplies last)
Order now! Operators are standing by (they can also help with deodex instructions)
of smali/baksmali. (no, not a new rom :p)
smali/baksmali v0.95 is out. The major change in this version is a re-implemented/optimized version of dexlib, as well as changes in smali/baksmali to work with the new dexlib. Also, I’ve optimized baksmali, so it should run much much quicker now (up to 4x quicker). smali should also be a bit quicker, but nothing you’ll probably notice.
As far as new functionality goes, baksmali will now output registers that are mapped to method parameters using a p<n> syntax, instead of the normal v<n> syntax. i.e. p0 is the first method parameter (or the “this” reference, for non-static methods). This makes it much less of a pain when you need to increase the number of registers in a method. Previously, you would have to go through and bump up the number for all of the parameter registers, but with the p<n> syntax, you won’t have to. If you don’t want this functionality, you can use the -p command line argument to turn it off.
The new versions can be found at the project download page
I’ve decided to call it quits on the whole rom making thing. As I’m sure you’ve noticed, I haven’t done much work on the rom lately anyway, not to mention the way overdue CRC1 rom that I never got out. I’ll still be around of course, working on smali and hanging out on freenode. But I just don’t have enough interest in doing rom work anymore to continue.
I sincerely appreciate all the kind words about my roms, and I want to again thank everyone who has donated.
If you’re looking for a new rom to try, I recommend cyanogen’s stable or experimental roms. He’s put a lot of work into them, and they have many more features than mine do/did.
Also, If anyone wants to grab my build environment and maintain a “JF-style” build on their own, go for it 
If you need any pointers on how to update the build environment as new official releases come out, feel free to ask (There really isn’t all that much involved in it).
Putting together some pieces off the mailing lists, it looks like someone is working on a CDMA “Google-experience” phone. I’ve got your likely specs below. No word on carrier, no blurrycam pics, no FCC filings. Just the hints.
If you are on the US or EU versions of JFv1.51, you’ll likely get an OTA update notification soon, if you haven’t already. I had accidentally left in the otacerts.zip file, which allows OTAs to be downloaded and verified.
For now, there are a few possible work arounds.
1. delete the otacerts.zip file manually. The file is at /system/etc/security/otacerts.zip But keep in mind if you use this method your phone will continuously re-down the OTA and try to verify it, which is bad on your bandwidth usage and your battery life
2. Replace /system/build.prop on your phone with the one from the ADP1 version of JFv1.51
3. chmod 000 the OTA file in /cache (unconfirmed solution, but is likely to work)
Or you can ignore the popups for now, and wait for my new release based on the new update (CRC1). I promise to “disable” the OTA mechanisms in a better way than simply deleting otacerts.zip . I should be able to get something out soon (next few days)
In the meantime, even if you accidentally hit “accept” on the popup, it won’t be able to install the update when it gets into recovery, so you aren’t at risk of losing root access.