Related
I have developed an app that requires root (su) and sqlite3, among a few other linux command line tools. I developed it on a Captivate running a Cognition 2.2 ROM and everything works swimmingly.
However, there are reports that this is a no-go on Droid X as it is missing sqlite3.
True, there are plenty of instructions on how to install sqlite3 using the adb. However, since this issue keeps coming up with respect to the Droids, I am wondering if anyone has developed an easy way to "one-click" install or the likes for sqlite3 on the Droids. I would work on this but unfortunately I do not have a Droid and the guys at work with them refuse to root them (lame).
Thanks for the help!
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.
Very nice m8,
i'm using it on my CM7 Build #0, with much apps i have 156MB free..
cool man sounds orsum will have to add this to my new rom
Would you say this is better than the normal Froyo App2sd? is it any faster at loading the apps one the sd card loading from **** drive mode?
Froyo app2sd sucks, this one is heaps better as apps are stored on ext partition, so you save way more internal phone memory. And yea its fast.
Sent from my HTC Wildfire using XDA App
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
I have now installed this, how do i know apps are being moved to the sd card?
I would love to for those roms. I'll have to look at the roms. Unfortunately, I don't have a ZTE Blade, but I don't own most of these phones that Darktremor works on (I only have a Sprint Hero and a Sprint Evo).
The more roms, the better.
danne_jo said:
nice to se you here tkirton
but i would love to see you @ ZTE blade forum to
will use your app in those roms
Click to expand...
Click to collapse
Run a2sd check. That will check the configuration and tell you if everything is setup correctly.
-Howad- said:
I have now installed this, how do i know apps are being moved to the sd card?
Click to expand...
Click to collapse
You can also just start "Titanium Backup" and check memory in the main screen
I installed Darktremor app2sd on Modaco custom rom (Froyo), and must say its excelent, I got internal memmory of 160 mb free, and now with 100 apps installed have 155 mb free. My ext3 partition is 512 mb and Dalvik cache is on ext3. With zipalign phone work well, no issues about stability, widgets work normal (its not case with Froyo a2sd).
Thanks Tkirton for this.
bump---new version available.
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
I want to know about that too. Can we flash the new version on top of the original one? Will it harm the installed apps?
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Just flash on top of it.
rudyshy said:
is there something what i have to do before installation?
i already have 2.7.5.2 .. or just install from new zip file?
anything before or after? (cahesd or smtg.)
Click to expand...
Click to collapse
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
WackyWookie said:
"a2sd help" moves apps to phone???
"a2sd cachesdreset" doesn't seem to work???
Click to expand...
Click to collapse
Describe the steps that you went through in installing it, including any commands you ran after the install.
vilks said:
how to instal it? i instaled it on 2.3 codegen from recovery chosing zip i downloaded and now everyting doesnt work in my phone. all programs are messed... i dont understand. now i need to reinstal new rom? because i lost a lot of programs and all widgets cant load.
Click to expand...
Click to collapse
tkirton said:
Download the 03a version...the Help issue is described on the first message.
Type a2sd reinstall to put the apps back on the phone.
As for a2sd cachesdreset, I will look into it.
UPDATE: I see the issue with a2sd cachesdreset. I'll issue an update shortly. In the meantime, use a2sd cachesd and, if you want to reset the cache, type a2sd resetcache
Click to expand...
Click to collapse
Ah good I was starting to doubt my phone's installation, good to know it's a bug...
Sent from my HTC Wildfire using XDA App
WhisperCore
WhisperCore integrates with the underlying Android OS to protect everything you keep on your phone. This initial beta tech-demo features full disk encryption and basic platform management tools for Nexus S phones. WhisperCore presents a simple and unobstrusive interface to users, while providing powerful security and management APIs for developers.​
anyone tried this?
tempted to give it a go now!
Edit:
Just flashed it... BEWARE.. will erase all data / system / user data and 'unroot' your phone. When i rebooted, the padlock had gone and the phone was unrooted. Had to reflash cwm and restore backup.
and when rooting it back, it will ERASE SD CARD... so
BACKUP EVERYTHING FIRST =)
Not bad though, runs vanilla 2.3.3 with disk encryption and option to encrypt 'sd card', no other mods I could tell.
phrag said:
anyone tried this?
tempted to give it a go now!
Click to expand...
Click to collapse
I've tried. Not bad.
Anyone else tried this that can provide some more information?
Is it a new rom?
After using this for a week I have to say I'm impressed.
Its fast, battery is good and has been completely stable so far.
Hopefully there will be more modules coming soon. I dont think it would work using Netarchy kernel or similar.
Anyone know how I can get a tun.ko file that will work?
I used the D4 utility to root my Motorola Droid 4 running, at the time, GB. I then DL'd Titaninum Backup and Voodoo root keeper. I have recently gotten the OTA ICS and believe I preserved my root with voodoo. I did have some issues that root keeper seemed to resolve. My question is; do I need to factory reset and reroot with a different utility or am I good? The only issues I seem to have now is 1. My wallpaper seems to "zoom" in going from landscape view to normal portrait view 2. 4g/3g freezing and not opening websites without backing out and/or rebooting 3. My sound is sometimes off when going from muted to any volume (seems only with videos and or streaming music ie: youtube, iheart, etc)
A lot of people experience issues when upgrading to ICS. While the update is supposed to bring you to 4.x from 2.x as seamlessly as possible, the reality is there will always be issues.
Do a factory reset to give your ICS a "fresh" start and you'll find it should run much more smoothly. If you kept root via RootKeeper you should be good, but you can always re-root using the 4.0.4 root tool found here:
http://forum.xda-developers.com/showthread.php?t=1707214
Sent from my DROID4 using Tapatalk 2
DISCLAIMER: I have no clue so everything below is speculation. Hopefully I don't make someone's informed answer more difficult...
When you root you're going to get a su binary (or did I install Superuser?).
Voodoo OTA Rootkeeper lets you backup/protect the root (binary). Then you can temp un-root and subsequently restore root.
Before going to ICS one should:
- in Voodoo OTA RootKeeper: Delete su backup (delete the backed up su binary)
- in Superuser: check for updates and update to latest binary (updates su to the latest binary)
- in Voodoo OTA RootKeeper: Protect root (saves the updated su binary)
- in Voodoo OTA RootKeeper: temp un-root and then restore root (refreshes loaded/running copy to current binary?)
Since it worked for you after the upgrade I'm guessing you already had the latest su binary. and you don't need to do anything further with respect to root?
There are 2 versions of the D4 utility. One for GB and one for ICS. You want to be using the ICS one now
Apparently you did not have safestrap installed before the update to ICS.
My understanding for safestrap is that you have to completely uninstall it first or the update fails.
- in safestrap: uninstall recovery
- in Settings->Applications->Manage Applicaions: uninstall safestrap
- in a file explorer with root capabilities: delete /system/bin/logwrapper
- in a file explorer with root capabilities: rename /system/bin/logwrapper.bin -> /system/bin/logwrapper
...not real clear on that last one. I gather that installing or using safestrap moves logwrapper to logwrapper.bin and uses a modified logwrapper in it's place? So you need to restore the original one? Maybe because otherwise the updater's check for system files fails?
[Sorry about sort of hijacking your thread to verify my understanding of this but I'm getting ready to make the leap myself and it appears I have a similar setup to yours]
You don't really have to worry about updating the su binary as long as there is a back-up in voodoo. The ICS only utility should re-root without any trouble if you lost it in the update. You can also use RSD Lite and the ICS fastboot file to start over fresh if you like.
The Magician Type 0 said:
A lot of people experience issues when upgrading to ICS. While the update is supposed to bring you to 4.x from 2.x as seamlessly as possible, the reality is there will always be issues.
Do a factory reset to give your ICS a "fresh" start and you'll find it should run much more smoothly. If you kept root via RootKeeper you should be good, but you can always re-root using the 4.0.4 root tool found here:
http://forum.xda-developers.com/showthread.php?t=1707214
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for my ignorance, but when I do a factory reset I will lose everything correct and will have to dl my apps and root again? or should I 1.unroot, 2.factory reset, 3.then root again?
You shouldn't loose root and will not lose superuser if it was installed as a system app. You will have reinstall any app you downloaded from the market or sideloaded. Otherwise your phone will be like the day you got it, without any user data.
jsnweitzel said:
You don't really have to worry about updating the su binary as long as there is a back-up in voodoo. The ICS only utility should re-root without any trouble if you lost it in the update. You can also use RSD Lite and the ICS fastboot file to start over fresh if you like.
Click to expand...
Click to collapse
If I were to root my droid with ICS only tool, will I be able to unroot and go to stock if needed, ie: warranty, etc.
kexec is now fully working!
Kexec host kernel: https://github.com/willcast/ubuntu-kernel-tenderloin branch is "kexec"
Graphical bootloader: https://github.com/willcast/kexecboot
Compiled host kernel uImage UPDATED: https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
THE ATTACHED KERNEL PATCH (decomp_copy_atags.diff) _MUST_ BE APPLIED for ANY kernel to be bootable FROM kexec.
YouTube: http://www.youtube.com/watch?v=ko_4cOj_5iM
Kexec kernel and OS installation is best performed through SmackMe2, which is available in its own thread on this site.
I have no idea what you are saying, but keep up the great work!
Keep up the good work man , one question with you work in the future can we delete web os from the touchpad forever?
I imagine that's already possible. Use lvm to delete all the logical volumes not tied to another OS and then delete the uImage.webOS symlink. That deletes webOS, frees mostof its space and removes it from the moboot menu.
If you choose to do that, though, using the doctor to restore WEBOS will be even more difficult because you'll have to wipe out everything AND potentially need to "unbrick" your TP (using the method involving NovaCom, the small boot image ripped from the doctor and a string of LVM commands that is posted on sone or other forum.)
Lvm? Can you make a tutorial? How to remove webos from touchpad?
Thank you
Before this is complete or posted for testing, I think we will need a tutorial and links to files of how to fix the tp from a full brick such as issues with removing and restoring webos.
Great job if your boot loader works as planned we will have a full multi-boot device with a few restrictions(drivers for untested ports, etc).
Keep it up.
Sent from my cm_tenderloin using xda app-developers app
Awesome that you're resuming development castrwilliam! Can't help you with kexec though, sorry. I hang around in the Motorola Defy forums and some developers like Quarx have tried pursuing the kexec route in order to load custom kernels onto the Defy, might be worthwhile to throw him a PM. Would be great to have a more flexible bootloader!
I anyone needs a full restore, this thread helped me out. I followed the instructions when I screwed up and doctored without removing partitions. I believe WebOS Doctor handles repartitioning, so it should work:
http://forum.xda-developers.com/showthread.php?t=1426244
WORKING (but non-Kexec) Android multiboot for TouchPad.
DON'T TRY ANYTHING UNTIL YOU HAVE READ THE WHOLE POST!!
Beta 2 Updated with support for my Froyo Qcom kang.
I created a script that can install multiple versions of Android on the HP Touchpad, side by side, such that they can be selected at the MoBoot menu and operate independently. The script modifies them, on the Touchpad itself, to work with the new names for the partitions.
I want your feedback on this installer. It is used in the same way as ACME Installer but only shares one line of actual code with it (and it also uses the same binaries and config files on the initial ramdisk image, but they are Open Source so that should'nt matter.) I'll be posting this on XDA in a minute, my username there is also "castrwilliam".
If you do choose to use (TEST!) this:
- You need to create a folder on your media partition (the one that is shown when you select USB mode) with the following zips:
moboot [moboot_0.3.5.zip]
(the rest are optional but I recommend using them all so that you can help me test everything)
Froyo Test [Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip]
CM7 alpha3.5 [update-cm-7.1.0-tenderloin-a3.5-fullofbugs.zip]
CM9 latest nightly [cm-9-xxxxxxxx-NIGHTLY-tenderloin.zip]
CM10 latest preview [cm-10-xxxxxxxx-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM.zip]
2.3.x gapps [gapps-gb-xxxxxxxx.zip]
4.0.x gapps [gapps-ics-xxxxxxxx.zip]
4.1.x gapps [gapps-jb-xxxxxxxx.zip] MAKE SURE not to use 4.2 gapps!
(NO Android Recovery will work yet, so don't try. It will reject TWRP and CWM at least.)
- If you already have Android and/or Moboot and/or native Linux (Ubuntu, etc.) installed:
* back up any data on your media volume. webOS should back up your apps for you.
* make both a nandroid (which WON'T work to restore in a multiboot config, but if you go back to single boot, it will be fine) and a Titanium backup [which should be portable to the same OS.]
* run ACMEUninstaller and then run SmackMe-Installer.
* if you have native Linux, backup your /etc and /home (I recommend the lovely GNU tar and gzip/bzip2). That should be the majority of what to keep.
* ALSO uninstall any native Linux you may be using after you back it up.
* lastly unzip and novacom boot the SmackMe-Installer.
If you don't already have Android, MoBoot OR native Linux, just:
* back up any data on your media volume. webOS should back up your apps for you.
* then unzip and novacom boot the SmackMe-Installer.
youtube demo:
http://www.youtube.com/watch?v=8Hhy20lzhR4&feature=youtu.be
File should be attached. Report bugs by PM'ing me, or posting in this thread
Can i remove webos with this multiboot? And stay only on android and ubuntu?
This is strictly an installer. I was going to write a webOS removal script. However, android doesn't have the needed binaries. That leaves me two options: make another thing like SmackMe to do it or do it under whatever version of native Ubuntu you are running. Either way, I really don't want to have to test it myself. If I need to I'll have to doctor my touchpad EVERY TIME I do it. That's a lot of doctoring and a lot of flash write wear. So the answer is basically "find me a dev that wants to remove webos too. They'll either make you one or beta test mine." Sorry man.
Amazing keep up the good work castrwilliam !
Strange request
Hey, does anyone here still have the 2011 Froyo (2.2.1) system dump for Touchpad? It wasn't CM6, just something that HP accidentally released and someone over at Rootzwiki dumped. I'm posting this here because I have no account and they'd think I'm a noob there. All the links are down to it and I want to try messing around with its files, just for kicks. Maaaaybe I can get it to boot, and add support for it to the SmackMe installer, so at least I can have *four* versions of Android on my touchpad.
http://forum.xda-developers.com/showthread.php?t=1234381
You know, 'cause I'm just that crazy.
Wow it's been hard to find it but i think this is the good dump:
http://download.digiex.net/Consoles/Tablets/HP-Touchpad-Android2.2.1-Disk-Images.zip
sources:
http://digiex.net/downloads/downloa...hpad-android-2-2-1-system-image-download.html
it's alive! (sorta)
Somebody on XDA found a link that I thought was dead. It was the mmc dump of someone who had Froyo leaked by HP onto their fire-sale Touchpad.
FAQ:
"Obviously nobody wants this. Everybody's running Jelly Bean."
That's exectly why I did it. My point is to do the most outrageous and downright unnecessary things possible with commonplace hardware.
"What doesn't work?"
Rotation, sound, wi-fi, softkeys (i.e. Home, Back, Menu, Search.)
"What does work?"
Camera (OH HAYULL YA), touchscreen, battery reading, power button, volume button (but it dosen't matter b/c sound is borked).
"I can haz Modded Froyo?!"
Not yet.
YouTube: http://www.youtube.com/watch?v=zX29IcTIB14
Hah awesome work, I think you hold the record of most different OS'es on one device now! It looks quite functional already.
Oh and about the "Obviously nobody wants this. Everybody's running Jelly Bean." quote, I only run WebOS and your Ubuntu 12.10 port on the TP!
As soon as I get my power button sorted out I am on this!
Sent from my slim_tenderloin using xda app-developers app
Hey everyone! Froyo here!
I've just zipped up my Froyo kang such that it will work if flashed from SmackMe, and if you're crazy enough to run it alone, hopefully also Android recovery.
sound works!!
The Wi-Fi works now BUT YOU NEED A STATIC IP ADDRESS. (problems with dhcpcd)
The buttons are hacked to work (by my new shell script: /system/bin/buttond, check it out) as follows:
Volume Down is Back
Volume Up is Menu
Center is Home.
Obviously once the audio works (if ever) that will be an issue. My embarrassing secret (at least probably to the devs here) is that I don't know Java. That makes it difficult to mod on any touchscreen buttons...
The real audio library is /system/lib/libaudioflinger.real.so and the stub one (default via a symlink) is /system/lib/audioflinger.so. Using the real one causes bootloops.
Auto rotation still won't function.
Google Apps and even Facebook are included in this ROM. (It's not CM6.) So are some potentially geeky Qualcomm apps.
Don't set up your Google Account during first boot, because it will ask you to slide the keyboard open. That sounds pretty impossible onn this device. Set it up from Settings later, and you shouldn't have that issue.
UPDATED due to install issues with actual Android Recovery. Redownload.
Download Initial Version (Alpha Minus-One-Point-One): https://www.dropbox.com/s/wcs2mra8aedj1hf/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip
Download Second Version (Alpha 0.2): https://www.dropbox.com/s/t1cptjj5i02epas/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.2-incl-gapps.zip
^^^
I wanted to try froyo soo bad when I heard about those dumps last year (I think) lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
jacobas92 said:
^^^
I wanted to try this soo bad when I heard about it last year lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
Click to expand...
Click to collapse
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
castrwilliam said:
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
Click to expand...
Click to collapse
Ok, thanks!