This is a complete package just unzip folder on sd card.
Here is original thread by neopeek
people having wifi problems check the original thread they have a fix
This is the CWM 1.9 thread wich is included in folder already
Using starfox test kernel from XDA (Rhodium only)
EDIT: per starfox dont use test kernels use his new vanilla stable kernel
GAPPS already included.
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word
DOWNLOAD
Sure, I'll bite. I've got an extra micro-sd card here. What's the worst that could happen?
It's a pretty fast build, I tried it on Neopeeks site.
It is MDPI, so the look of it isn't quite as crisp... (you can see what I mean by the notification bar 3g, etc...lower resolution basically) but I was impressed by the speed. All the animations, etc are disabled by default and I believe that's Zeam that is the default launcher... it is quite snappy out of the box.
what tweaks you did?
no tweaks just put it together
This version is the fastest thing I've tried (probably due to mdpi-gapps), but I have two major issues.
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
2) Camera is tremendously unstable. Most of the times it crashes bringing down the entire OS or if I am lucky it will crash the camera app and refuse to start again until a reboot.
Of course there are random hiccups here and there (like most builds), but it is quite close replacing WM for every day usage.
XavierGr said:
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
Click to expand...
Click to collapse
This is actually not that unusual... I would get this on my epic4g... which is an android phone .
If you don't mind, please use the vanilla kernel that I posted instead of the testing kernel. While I don't mind that it is being bundled, the [Test] kernel was never meant to be used for long term, and is liable to include stuff that is unstable and/or changed on my whim. The vanilla kernel contains some of the tweaks that I consider to be stable and is based on known autobuild releases+supports all devices. Thanks.
http://forum.xda-developers.com/showthread.php?t=1221499
-- Starfox
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
anish88 said:
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
Click to expand...
Click to collapse
There's nothing stopping you from doing that.
Including testing stuff into a public build is never a good idea. I wouldn't appreciate anything I distribute for testing to be put into a build. It's meant for testing, so anyone that installs/uses it should know full well what they're getting into. Placing it into a build circumvents that, and everyone ends up using it unknowingly.
To everybody with wi-fi issue:
I've done a small fix
http://www.multiupload.com/7NSGZQZXPC
(wich is in the first post of this thread on neopeek.com)
This will fix if your problem isn't the kernel
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
nekikekec said:
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
Click to expand...
Click to collapse
What problem did you have exactly and what do you mean by updating wifi-nvram?
I also have a wifi problem specifically with this build but can't solve it.
(Wifi works only once per boot)
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
nekikekec said:
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
Click to expand...
Click to collapse
That didn't work for me at all.
Can't get CWM working
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
nileshvedi said:
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
Click to expand...
Click to collapse
Did you set all your partitions as primary?
vzihome said:
Did you set all your partitions as primary?
Click to expand...
Click to collapse
Yes I did that too....
SD Card (All Partitions Primary)
Partition 1: 6.4 GB - FAT32
Partition 2: System - 300 MB - EXT2
Partition 1: Data - 300 MB - EXT2
Partition 1: Cache - 300 MB - EXT2
I put the npkboot folder with startup for RHOD100 on the SD Card (Root) and the NeoFroyo Zip also on the root.
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Run Haret from SD Card through File Explorer & press Volume Down - Result: Frozen Screen!!!
Does not enter into CWM recovery...
Are all the steps above right.
Regards,
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
WHY?
CWM rootfs works only in npkboot.
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
I'm a little confused with what you did.
Basically just unzip his folder you downloaded and then move the Entire npkboot folder to the root of ur sd card.
So there will be nothing on your sd card except the folder. Inside that folder will be everything just as you unzipped it. So for example haret would be at "Sdcard/npkboot/haret.exe". Then just switch/edit the startup.txt in the npkboot folder for your phone and boot into CWM.
You don't need to move anything outside of his npkboot folder that you unzipped.
Related
Starting this thread here for running this Eclair-Hero build on our Kaisers. Many thanks to all devs below!!
jamezelle said:
King Klair Hero 0.6
First and Foremost this build was ported by Mssmison and the ril(radio interface layer), and audio libraries were written by Vilord!!! im pretty sure the gps library was written by Srwalter. vilord may have helped port it to eclair. (will get back to you on that). without DZO we would still be using windows mobile "" but were not ""
To Donate: to these fine gents visit http://sourceforge.net/apps/trac/androidhtc/wiki/WikiStart and scroll down to the donation links
B to the E to the T to the A
this is very beta, well almost alpha(first release for us vogue users so report any bugs that havent been mentioned in this post)
what works:
gps
calls
data
wifi
sync(dont sign in to google during htc wizard, wait till next boot!! you have been warned!!!)
market
gmail
what doesn't:
camera
bluetooth
gtalk
get more widgets
will add screenies later
ENJOY
Click to expand...
Click to collapse
UPDATE 17 Dec:
Download the new rootfs below for working WiFi! Thanks enatefox!
Download:
system.sqsh [ver 0.6.01]
Eclair-ready__rootfs.img (rename to rootfs.img, of course)
eclairhero.user.conf (goes on your SD card in /android/conf)
OR if you have a swap partition on your SD card: eclairhero-swap_partition.user.conf (goes on your SD card as /android/conf/eclairhero.user.conf)
And if you don't have them already:
zImage-15-12-09 (the latest kernel from 15 Dec)
startup.txt (My personal HaRET startup.txt)
rootfs changelog:
Copied /init.cfg/init.eclairhero.rc to /init.cfg/init.eclairhero.kaiser.rc
Copied /init.cfg/init.eclair.rc to /init.cfg/init.eclair.kaiser.rc
Altered init to check that media folder exists in /sdcard/android/media instead of /sdcard/media
Altered init to support eclair.user.conf and eclairhero.user.conf
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Go straight to version 0.6.01 as posted above, version 0.6 gives me weird SIM errors.
This build takes FOREVER (5-10min) to boot. It goes through and even attempts to make a number of thumbnails for your images during first boot. I suggest watching it over adb so you'll know when it's settled and ready for input.
The HTC widgets are not working with this build.
TaskKiller is an absolute must, like other Hero builds this one loves to keep apps open.
Hmm, this build has successfully rebooted itself twice, during heavy use. I wish I knew how that worked, so we could get it to reboot on command!
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Almost downloaded Hero, just got vanilla Eclair to boot the first time. I'll look into wifi. Maybe it's me but Eclair seems faster than Donut but I haven't messed with it much. That should make Hero much nicer.. will post back when I get further
rugalck said:
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Click to expand...
Click to collapse
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
@enatefox:
O
Hero is very buggy, has too many problems to run daily for now. Overall Eclair Mike the fastest yet though! And the fonts are much better for qvga. Text autocomplete has issues.
polyrhythmic said:
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
Click to expand...
Click to collapse
Nah, don't worry, it was something really really stupid.
In the same file you said, it was like "zImage 11-12-09" so now I saved it saying just "zImage". Now works fine.
Waiting for wifi updates, great work guys!
BTW, is there any way to take screenshots?
damn bootloop. I'll look at this tomorrow but that's a promise . I don't know where these wifi files came from. I dropped in the ones that I've used and we'll see. Right now I'm fixing telnet and some other issues to post back with but it will take a little bit of time. We're going to get this working for daily use.
Here's working wifi for Eclair:
http://www.mediafire.com/?ezyzekjozj3
EDIT, I didn't get Hero to boot for me (looping) but I forgot to update Eclair Hero's conf file to match conf.eclair.kaiser.rc.. can someone either do that and repost or wait for me to finish some perm issues with it and I will upload one for Hero. Sorry about that.
I have got to be doing something wrong. I am using all of the files from the 1st post and the rootfs.img from enatefox's last post and this sat for 30 minutes. I even copied the user file to the sd card, to the /sdcard/CONF folder and into the /sdcard/Android/CONF folder and still it sits. I'll get a post of the last few lines up later to see if I just need to wait more or not. I am also using an empy 2GB Fat32 SD Card with the 1.71 radio. All other builds work but this one???
Any ideas?
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
rugalck said:
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
Click to expand...
Click to collapse
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
polyrhythmic said:
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Click to expand...
Click to collapse
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
FYI, your 'conf' and 'android' folders should be named in lowercase, if they aren't already.
The only way we can tell what is wrong is to see whatever the console says before it freezes, or ADB logs if you can make it that far. Post whatever you've got.
j101399j said:
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
If it wasn't created then... you wouldn't need to delete it, do you?
ROM Size: That's because I use mixed files from the different Eclair thread's.
It's a "package" of what worked fine on my device.
Most of the files are from this thread, but the system.sqsh is from this one:
http://forum.xda-developers.com/showthread.php?t=600154
Mirror File: http://rapidshare.com/files/322793487/android.rar.html (up to 10 times, I don't have a premium account D: )
j101399j said:
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
rugalck said:
ROM Size: That's because I use mixed files from the different Eclair thread's.
http://forum.xda-developers.com/showthread.php?t=600154
Click to expand...
Click to collapse
thank you, will try
polyrhythmic said:
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
Click to expand...
Click to collapse
I competly forgot about needing all lowercase letters; as for the data.img file, that is what I though; Thank you
[EDIT]
That is so wierd; I had to place the system.img into the /sdcard/android folder and the use user file in these 3 places /sdcard /sdcard/android and /sdcard/android/conf
Now it works. Don't know what changed, but it works
j101399j said:
thank you, will try
Click to expand...
Click to collapse
http://rapidshare.com/files/322793487/android.rar.html
I can almost guarantee you that the .conf file in your SD root and the .conf file in /android/ are ignored, try deleting them and just leave the .conf in the /conf/ directory. And yes, everything including the system.img/system.sqsh should go in the /android/ folder now.
I bet you can boot this Hero build, but it has a lot of bugs, you'll probably be happier with plain Eclair that rugalck linked.
hey guys ill update when king drops 0.7
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
RDilus said:
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
Click to expand...
Click to collapse
If it's the first boot, make sure to have at least 300mb free in your SD card.
rugalck said:
If it's the first boot, make sure to have at least 300mb free in your SD card.
Click to expand...
Click to collapse
not to be rude but im not stupid -.-'
i have like 5GB free...
It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.
It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.
ok thanks. i fixed it (rs bug when renaming files ^^)
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)
To be honest the bit I find most confusing is all the different versions!
i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed
ReadMe updated!
updated a bit...
Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...
updated the readme, not includes DualBoot howto and some other changes...
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...
THIS TOOL HAS BEEN DISCONTINUED. IF YOU REALLY NEED A LAGFIX, USE VOODOO. HOWEVER, WITH LATEST ROMS I DONT PERSONALLY FEEL A LAGFIX IS STILL NEEDED, THUS I DON'T USE ONE, AND WILL NOT CONTINUE DEVELOPING ONE
About
Here it is, yet another LagFix tool. It's certainly not the first, but it does offer some things others do not (at the time of this writing).
This patch uses the ext2/ext3 image in /data method.
IMPORTANT NOTICE FOR FROYO USERS
(1) Use ext2. ext3 is NOT supported on Froyo, only Eclair
(2) The installation will fail if you apps installed to SD. Go to Settings -> Applications -> Manage -> On SD card. Click each app and click "Move to phone". In the end, the "On SD card" list should be empty. Reboot. Install CFLagFix. When the fix is installed, you can move apps back to the SD card if you wish.
Features
- Lots of checks to make sure the fix is possible
- This is not just based on a script, but a lot of commands are performed and their results rigorously checked to be what is expected
- You can select (from a set of presets) which folders you want to lagfix
- You can select how big the image should be (between 128mb and all the free space in /data minus 250mb, to prevent low storage space warnings)
- The actual moving of data from RFS to the image is done in a boot loop, while the files are not in use. This minimizes the chance of corruption during move (settings being lost, etc)
- Comes with e2fsprogs, and e2fsck is performed each boot to fix a corrupted image
- Comes with it's own busybox, so no need to install it, and no chance for conflicts
- If an ext2 image is used, it is tuned to not reserve any blocks
- If an ext3 image is used, it is tuned to not reserve any blocks and use journalling
- Also moves databases (safely)
- Uninstall option
- Resize option, resize your partition whenever you want, to whatever (possible) size you want
- "Full automatic" option, this will max out the image size while still preventing the low storage space warning, and will also reclaim the space from the backup folders and automatically resize the image to max again after that space is reclaimed. This generally results in an image of about 1.5 GB. It'll also leave some space in case the system still needs to write in /data but not in the image.
- Progress monitor ("educated guess" about progress, not exact, but pretty close, usually!)
A fair number of these seem to be unique at the time of this writing.
Notes
- e2fsck result is stored in /data/cflf/e2fsck_result.txt
- list of mounted directories is stored in /data/cflf/mountlist.txt
- if ext3 is used /data/cflf/imageisext3 file will be present
- my own test rom is JM2+root-with-update.zip+ClockworkMod
Known issues
- In case the image is heavily corrupted, e2fsck may take longer to fix it than the rest of the boot process. Theoretically this could result in data loss
- ext3 does not seem to be supported on Froyo ROMs JP1/JP2/JP3
Credits
- mimocan, ykk_five, RyanZA, and all others who have chipped in for various lagfixes
- cynogen, e2fsprogs built for ARM
- kalpik, busybox APK
- ofcourse the original authors of those tools as well
- myself, this is all based on ADB Magic code
Donations
Please feel free to donate: http://www.jongma.org/dx.php
Requirements
- Windows
- Microsoft .Net 3.5 framework
- Phone in USB debugging mode
- SuperUser
Before using ...
I strongly recommend using ClockWorkMod and making a backup of your ROM. Just in case Also, during any operation, I advise having your phone hooked up so I can draw power from the computer.
Usage
- Unzip the attached file somewhere
- Make sure your phone is connected in USB debugging mode
- Make sure you have SuperUser installed
- Run CFLagFix.exe
There are three tabs:
Install LagFix
This tab allows you to install the LagFix, and lets you configure some options.
I recommand leaving the "Full automatic" option turned on, if you do, just press "Install !" and everything will be arranged for you. If you turn this option off, you can configure some settings manually, but note that using this does not reclaim wasted space of the backup files.
Note that you can still select to use ext3 instead of ext2, even if in "Full automatic" mode.
When you press "Install !", the program will be finished quickly, but your phone may continue working for 30 minutes or so, and keep rebooting very often. If you have a lot of data installed, it may take even longer.
Do NOT even touch your phone until Android boots up again!
A lot of things are checked before the install will start. You will need about 50% free in /data for the operation to work, but it will check this before making any modifications on your phone.
Resize Partition
This tab allows you to change the current ext2/ext3 partition size. The slider will only let you select values that are actually possible, i.e., bigger than your current data usage and smaller than the total space that could be occupied by the image.
Clicking "Resize !" will reboot your phone and resize the partition. Again, this can take an awfully long time! Don't panic, just wait it out.
Uninstall LagFix
This will uninstall the LagFix. It will completely remove it. Before removing it, however, it will move all files out of the image and back into the normal filesystem again, so no data is lost.
Clicking "Uninstall !" will reboot your phone and perform the uninstallation. Again, this can take an awfully long time! Don't panic, just wait it out.
Note that uninstallation will only work if you are using less than 50% of the device's capacity, but again the program will check this before making any modifications on your phone.
You can only uninstall installations of CFLagFix 1.20 and newer !!
BETA
This is very beta, use at your own risk!
WARNING
This patch is NOT compatible with ANY other lagfix tools. Either undo those completely, or just don't use this. If you were using one of those, I'd personally recommend a complete reflash of the firmware before using this patch.
WARNING #2
Before trying 1.80, please see this post.
Download
<< 1.70: 632
Changelogs
1.80, 15-08-10
- Redone some crucial parts of the patching procedure (for all install, resize and uninstall). Should fix all remaining issues!
1.70, 13-08-10
- Added /data/app-private/ folder
- Added progress monitor (estimates.... not exact)
- Moved /dbdata/databases to it's own partition, much faster for smaller read/writes
1.60, 12-08-10
- Updated codebase to ADB Magic 0.9, fixes issues with some weird pre-existing installations of busybox
1.50, 12-08-10
- Added "full auto" mode, "one click" solution for beginners
- Added ext3 support
- Added resize support
- Added uninstall support
- Fixed some issues
- Update scripts
1.20, 11-08-10
- Everything has been moved to /data/cflf/ , this - amongst other things - fixes issues with JP3
1.01, 11-08-10
- Adusted a permission error which could cause the system to be unable to create any new databases
Fix for 1.00 users: there isn't any yet. This is *beep* to fix manually. I would advise this "unpatch" method posted here: http://forum.xda-developers.com/showpost.php?p=7616676&postcount=29, then repatch with the latest version.
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
lyno said:
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
Click to expand...
Click to collapse
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Chainfire said:
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Click to expand...
Click to collapse
Ah yes! I removed all .net frameworks on this works laptop to be able to install some old COM files. Will re-install and test.
This looks so awesome! Thank you!
Any chance for open sourcing this?
installing now
Well im gonna give this a shot, have just installed the african jg8 and rooted,am doing this fix now.
Then ill try the 1.2 overclock on top, ill post a score shortly .
Not bad though i see one problem... it's windows only ^^
select which folders you want to lagfix
Click to expand...
Click to collapse
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this? -> it doesn't recognize both my internal & external sd, but i can browse them properly in Estrongs/astro
veenone said:
After the process finished, the Android displayed information about damaged internal SD, but everything was working.?
Click to expand...
Click to collapse
That sounds scary, think I'll wait a while before trying!
RyanZA said:
This looks so awesome! Thank you!
Any chance for open sourcing this?
Click to expand...
Click to collapse
Not at the moment, but maybe in the future
Tayutama said:
Not bad though i see one problem... it's windows only ^^
Click to expand...
Click to collapse
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
danamoult said:
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
Click to expand...
Click to collapse
You can't really lagfix all folders, as the process where the image is mounted is run asynchronously with the rest of the boot process. There will be havoc if the system can't load certain files because the image is not mounted yet. This is why you can't just lagfix the entire system, but only certain parts.
In the presets I have only added those folders that I feel are mostly safe to lagfix AND would actually benefit the speed of the phone.
Also, for some folders there is some discussion to whether or not it is beneficial to have them in the image, like /dbdata/databases. I personally feel it should be lagfixed, but not everyone agrees.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
Click to expand...
Click to collapse
I have not seen the "damaged internal SD" message before in any of my tests. It might be ROM specific (I'm personally using JM2). I would recommend rebooting (using the "hold power button + press power off" method) and see if the message still comes up. Let me know what happens.
And yes, feel free to post about it in your blog.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this?
Click to expand...
Click to collapse
Replying to the same message again, hehe.
Now that I'm thinking about, how exactly did your device got wiped ? Anything less than an actual firmware flash does not completely remove mimocan's fix, AFAIK. To completely undo it you'd have to completely reflash (and get stock kernel back), and possibly remove the ext partition from your SD. In other words, if you "wiped" from recovery, this is not a removal of mimocan (AFAIK).
Gallery is working fine for me, by the way, and as stated above, I have not seen that message in my tests with JM2 (neither with a lot of apps installed nor a clean flash).
(Then again, this is the first release, so there might be issues )
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
This fix is using exactly same space that is already reserved for user data and programs. And it is on the internal SD. So I really can't think how this fix could cause any damage at all. Thoughts?
I selected maximum Space, and now i have low internal memory. How to remove this fix or change the Space?
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
Use mimocan's fix if you want to use external SD - it is especially made for that! His thread is a sticky (at the top) in this forum.
veenone said:
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Click to expand...
Click to collapse
Mimocan's fix uses Odin. Like update.zip's, a "factory reset" does not remove patches made in this way, only a real flash does.
Either way, happy to see your problem is solved
I think the problem was the system didn't mount sd cards properly after several boots from CFLagFix. So it needs more reboots to mount the sdcard with structure change properly...
Chainfire said:
Not at the moment, but maybe in the future
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
Click to expand...
Click to collapse
It's a shame you can't open source this.
Personally, there is no way I'm going to run something like this without source - I believe you are just trying to help us out, but there is always the chance that you could be doing something damaging by mistake, or even installing a trojan on purpose.
I'll be following release though, looks awesome and hopefully you'll be able to open source this soon!
THIS BUILD IS OUTDATED, CHECK:
http://forum.xda-developers.com/showthread.php?t=1177721
I'd like to "present" my recompilation of XDAndroid FRX06 to work with Neopeek's CWM 1.8
No credit for me, but for all XDAndroid devs and Neopeek &co for this.
It doesn't have any other modifications apart from making it available to install from CWM, so everything that applies to FRX06 is useful here. You're the one to decide if you prefer looped or partitioned installs.
Don't try this if you don't know what you're doing. It's only tested by me, so what I'm looking for are TESTERS. PLEASE READ EVERYTHING CAREFULLY BEFORE DOING ANYTHING.
Normally it would be easy to return to previous state by repartitioning/formatting SD, but who knows. I take no responsability for any damage to your device.
The instructions for installing CWM are in Neopeek's forum. Only points:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
2.- Startup.txt, ts-calibration, kernel and modules must be in the same dir as haret.exe, in this case inside "npkboot" dir.
3.-To move in the CWM menu with our Blackys:
Peteflyman said:
I just toggle between "Reboot system now", push "Vol Up" to get directly to "Power off", and then toggle "Vol Down" to get back to "Reboot system now". I just do that a couple of times then "Back menu button enabled" usually shows up. That's it. Hope it works for you guys as well!
Click to expand...
Click to collapse
After the "back menu button enabled" you can use power off button to confirm menu selection. Just select "install zip from sdcard", "choose zip from sdcard" and choose my zip (ofc, don't uncompress it).
4.- You don't need to install Gapps, they're included in the build.
5.- After installed, "reboot system now" and start haret again. Let it work for a while without touching anything until you see PIN or unlock screen to begin using Android.
6.- I'd recommend rebooting a second time before starting to configure everything...
It should work in any device where CWM and XDAndroid work, but the configurations I attach here are for TOUCH HD (Blackstone). If you want to try with other devices, be careful to use the appropiate config files (they shouldn't be difficult to find in your device's forum).
I'm using 1337 kernel & modules from Glemsom's autobuild and it works perfectly with my device, feel free to use the one that suits you better.
Download link:
http://www.megaupload.com/?d=SUBUG5I8
If you have any problem, I'll try to help, but for CWM problems please ask in their forum as you'll find better assistance.
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
if you want to install any other build,or reinstall frx06,go to recovery,choose mounts and storage,then format data,format cache,format system (don't format sdcard for obvious reasons) and then mount data,cache,system,go back and install zip from sd card,choose your zip.
also if you find a build without gapps,go to cyanogenmod.com and grab it there,you should pich gapps for cyanogenmod 6 because that's the froyo build....MDPI or HDPI doesn't matter in our case
many problems are result of gapps missing (some builds come without them,this one doesn't) such as call rejecting or showing black screen instead of lockscreen when you wake the device,so be sure to install them
arrrghhh said:
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
Click to expand...
Click to collapse
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Eodun said:
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Click to expand...
Click to collapse
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
farukb said:
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
Click to expand...
Click to collapse
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Eodun said:
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Click to expand...
Click to collapse
you can at least start with
/system
/app (add or remove apps)
/fonts (obvious)
/framework (the "look" of the build is defined here,so if you want your froyo to look like ginger,take some of the ginger files and swap with those in this one)
/media (it'll tell you what to do by itself)
other folders are build regarded and some playing and asking pros is advised here
any screenshots ?
Simon_WM said:
any screenshots ?
Click to expand...
Click to collapse
It's a vanilla Froyo, identical to FRX06, so I didn't think they were needed. Just look at any basic original Froyo install.
Eodun said:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
Click to expand...
Click to collapse
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
every card is "original" just the manufacturer is different....eg trandescent cards dont work,what's your card?
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Eodun said:
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Click to expand...
Click to collapse
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
arrrghhh said:
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
Click to expand...
Click to collapse
Well, I can't tell because I'm in android now and can't extract it XD Never had the curiosity to check.
Let me see... Yeah, it has a "2" inside sort of a "C", so it must be a C2 8Gb SanDisk MicroSDHC lol
Working on FRX07 update.zip to test if it works with CWM
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
ypsmav said:
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
Click to expand...
Click to collapse
helicopter88 is already working on that
ypsmav said:
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
Click to expand...
Click to collapse
I don't think so. But if you backup everything with titanium backup and then restore apps, appdata and system settings (only those that appear in green) you'll have everything as before.
Eodun said:
Working on FRX07 update.zip to test if it works with CWM
Click to expand...
Click to collapse
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
arrrghhh said:
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
Click to expand...
Click to collapse
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
ypsmav said:
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
Click to expand...
Click to collapse
@arrrghhh: Yeah, I know the update is available, but ypsmav noticed the problem: I need the new rootfs for CWM, and I'm not able to adapt it. As I said, work is being done for that.
Thanks for your replies
Ps It will be a big problem if latest kernel doesn't boot. I haven't been able to boot with it. Edit: But still have to check if it boots with a clean data.
This is a re-pack based on Catherall's own guide here: [GUIDE] Booting an Android System when only Recovery is at your disposal
The main difference from his copy (cyanogenmod 7.1):
- Google Apps (20110828) applied
- Updated to latest Google Play Store (3.7.15)
- update.zip modified to work on 4EXT Touch Recovery (ui disable)
Tested so far off of 4EXT Touch Recovery 1.0.0.5 RC5
What doesn't work and probably will never work unless someone makes new kernel modules for 2.6.35.10 (ie: the .ko files can be placed in the BootManager folder, and then have the init.d scripts edited to load those modules, but thus far none of them have worked for me because they were not built for that exact kernel, I don't know how to compile modules etc).
- Wifi [won't turn on]
- Bluetooth [won't turn on]
- everything else he mentioned in his first post regarding adb/etc
Made this as a new thread because his is quite stale, and catherall hasn't been seen in like forever. And kind of hoping that with the new progress maybe someone will take the time to write up some new gingerbread drivers for this purpose.
If I had the knowledge I would have ported an extremely lightweight Gingerbread Rom to it to be used as sort of a 'emergency-droid' rom, and recompiled kernel modules so that wifi/etc would work.
Instructions
Download the zip, unpack, copy BootManager and update.zip [zip can be renamed] to the SD card. Boot into recovery mode, run the update.zip to start up CyanogenMod 7.1 form the SD Card. (The original README is in the zip)
When you're in for the first time you'll notice the usual Google Apps setup screen, but it'll be in german. To change the language:
Press "Setup abschliben"
Press "Sprache ändern", select appropriate language
Continue the Google Apps setup as usual
It is advised that you do not allow it to automatically let it restore/install your apps as there will be no wifi connectivity and would be done over your data connectivity.
Download Boot_From_SD_wPlay.zip (~135MB)
md5sum : a352017b37bb546ffe0327bbe78304fe
Video from when I was first playing with it (after I put the 4EXT code in, but before I added gapps).
aaaaand another service from Kbeezie... you just can't stop can you?
thanks!
Is it possible to adjust the size of the internal storage? Make it 1g or larger?
Please tell me how if its possible...
Verstuurd van mijn HTC Vision
feejzor said:
Is it possible to adjust the size of the internal storage? Make it 1g or larger?
Please tell me how if its possible...
Verstuurd van mijn HTC Vision
Click to expand...
Click to collapse
You should be able to modify the the image sizes with BootManager (from the market).... as the free version doesn't see 'Rom8' (which this is mounted), you would have to copy the contents of BootManager/Rom8 to BootManager/Rom1, adjust the image size to 1gb or whatever you wanted... then boot to cwm/4ext mount usb, and use your pc to copy the contents of Rom1 to Rom8 (keep a copy of the original Rom8 somewhere as a backup if it fails)
Never tried it, but it works in my head!
Hope it helps.
Is there anyway to make this permanent so that every time i turn on or reboot the phone, it boots from SD card ?
I use
fastboot boot boot.img
from cmd and after that wifi works and bluetooth works in case anyone is interested
00sand00 said:
I use
fastboot boot boot.img
from cmd and after that wifi works and bluetooth works in case anyone is interested
Click to expand...
Click to collapse
Nice finding! Anyway, can I ask you what boot.img file did you use?
Sent from my HTC Vision using Tapatalk 2
Mehrdad96 said:
Is there anyway to make this permanent so that every time i turn on or reboot the phone, it boots from SD card ?
Click to expand...
Click to collapse
This is unlikely without also writing some kind of bootloader on the internal memory to launch from the SD... which of course would require that the internal memory were not in some way damaged. So kind of a catch-22 to what you're asking. Shouldn't be using SD booting as a permanent solution, it's more like a way of still being able to do *some* things while you work out on getting the phone replaced.
And here I thought you and all your work was gone, nice to see ya around kbeezie!
Sent from my SGH-T839 using Tapatalk 2
Can someone please re-upload zip?
Anyone?
Sent from my GT-I9105P with RESURECTION REMIX KK 5.0.8