smali/baksmali v1.2.1 bugfix release
March 6, 2010I’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.
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.
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
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.
Update: There are now also wrapper scripts available for smali/baksmali, so you can call “baksmali …” instead of “java -jar baksmali.jar …”
Update 2: Now that the Eclair source is out, I’ve added a new build of deodexerant to the downloads page that works with 2.0
odex files getting you down? Now you can do something about them!
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.
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.