Related
Hi All,
[ADD 22-jan-2010]
I'm testing now the NAND flashfiles from Diagdave. For newbies: Your kaiser will boot directly to Android.. WinMO is past, history... not anymore on the phone
Very FAST when boot
Have try flash with Droid ION Donut 1.6, Hero Blend V242 and new WarmDonut and all are working.
WORKING: Data, Call , Camera and hard keybord
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth (known issues)
If you want try it yourself. The Kaiser-NAND-Installation.rar contain ony the 3 empty files, emty data.img and rootfs.img - HERE
be aware.. HAVE A WORKING WINMO Flash if you want go back to WinMO
There you have the 6 different flavor of the FLASH file itslef. (Thanks to DiagDave)
320 - Panel 1 - HERE
320 - Panel 2 - HERE
320 - Panel 3 - HERE
428 - Panel 1 - HERE
428 - Panel 2 - HERE
428 - Panel 3 - HERE
480 - Panel 1 - HERE
480 - Panel 2 - HERE
480 - Panel 3 - HERE
INSTALLATION:
Put all the files from the RAR on a empty SD Card
Put the FLASH file on the SD card. Rename it to KAISimg.nbh
Select you Android Build and rename it to system.sqsh and put this on the SD card
Startup in bootloader and flash your phone
Pull out the battery and restart your phone.
When everything is done restart your phone again so the APN will start as well
[INSTALLATION WHEN YOU WANT SWITCH BETWEEN WINMO AND ANDROID]
The reason i start this tread because i think smart guys can programming this ION version so BlueTooth will work also.
I have install a build from the Vogue tread and is SO fast.. The best version i have used at this moment only Bluetooth is not working.
My current WinMo config: (now removed and replaced by NAND andoid flash) but with this config everything was working fine for me in past:
Startup screen:
R: 1.71.09.01 download HERE
G: 25.75.40.03
D: 3.34.00.00 emo
WinMO Rom: Solace 3.1 download HERE
The files u need for this great working Android version (all versions i post here):
Latest Basefiles 16-11-2009 download HERE - Extract to your SD Card
Latest Rootfs download HERE - replace this one over the other of the basefile and your GPS IS WORKING!!!
You can choose between several builds. All are working ok but some of you want different flavors
Droid ION Donut 1.6 / system.sqsh download HERE rename to system.sqsh
Hero Blend V242 / system.sqsh download HERE rename to system.sqsh
Here i have post my own default.txt/startup.txt that i use for both builds:
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.gz
#
set cmdline "board-htckaiser.panel_type=2 ppp.apn=internet ppp.username= ppp.password= pm.sleep_mode=0 mddi.width=320 mddi.height=480 lcd.density=160 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Remarks
Use for Hero Blend: mddi.width=320 mddi.height=480 lcd.density=160
All system.sqsh are using the latest basefile and rootfs given above. When you switch between builds delete or rename data.img OR wipe data if you using fat32/ext2/ext2 SD card
When problem with rotation orientation you can try using zIMAGE-23-10-2009 - download HERE
Kaiser Battery problems you can try solution write on this page
[ADD 31-dec-2009]
All files are on my site - AndroidClone.nl
[ADD 23-jan-2010]
Since started my site there is dowloaded for 32GB of files... (MAX Bandwith is 50GB otherwise i must pay for every GB)
2324 (last update was 1574) times Basefile downloaed
1419 (last update was 1157) times Donut ION downloaded
1184 (last update was 953) times rootfs downloaded
706 (last update was 522) times Hero Blend v242 downloaded
359 (last update was 302) times the zipped empty data image downloaded
Donation welcome to increase the Bandwidth...
Received 10 euro.. Thanks
Hi, how can i configAndroid for work on my Kaiser wit Vodafone IT?
Is the first time that i will try Android with HaRET.
Could you help me?
Thansk.
Tommaso
Hi
Put everything in the ROOT of your Fat32 formatted SD card.
replace default.txt with default-kaiser.txt
start haret.exe within Windows. First time take some time before you see something so please wait...
After configuration is done you can go back to WinMO doing reset your Kaiser
Excuse me, if i post a stupid question...
Where can i find the last default-kaiser.txt?
Thank you very much!
download the files i given. Everything is in there
Ok... This evening, when i return home from work, i will download all, next i will put all on my SD card (i will replace the content of defuaul.txt with the content of default-kaiser.txt) and i will tap HaRET...
[edit]
Excuse me, the content of folders "conf" and "media" where have i to put?
have i to copy the folders to my SD or have i to compy only some files?
have i to modify some files?
[/edit]
I'm looking for finish this working day for try Android!!
Thanks.
Tommaso.
Everything in root. So conf and media need also in the root as folders with their files. SD Card must look like:
CONF
MEDIA
default.txt
haret.exe
initrd.gz
rootfs.img
zImage
system.sqsh
BUT..... The reason of this tread was if a programmer or smart guy can try this and can let work GPS and maybe Bluetooth would be great.
This version of ION Donut is so smooth and fast
does the vogue have working gps with this build? sorry if this is something know, can't search gps, i guess it's too short of a string for the search engine
Hi, i'veput on the SD card the file you tell me...
I have tappedon haret.exe and Andoid start booting.
I saw linux boot string running on the screen, after that, when it was pased 2 minutes my screen goes black. I've attended 5 minutes, after that i did a soft reset.
[edit 1] I tried to attend 10 minutes but nothing change. [/edit]
[edit 2] I tried also use default.txt instead of default-kaiser.txt but haret freez booting, when the loading bar arrive at the end. [/edit]
Have i to sttend lot of time?
Or is my kaiser that don't work very well?
Tommaso
kavejo said:
Hi, i'veput on the SD card the file you tell me...
I have tappedon haret.exe and Andoid start booting.
I saw linux boot string running on the screen, after that, when it was pased 2 minutes my screen goes black. I've attended 5 minutes, after that i did a soft reset.
[edit 1] I tried to attend 10 minutes but nothing change. [/edit]
[edit 2] I tried also use default.txt instead of default-kaiser.txt but haret freez booting, when the loading bar arrive at the end. [/edit]
Have i to sttend lot of time?
Or is my kaiser that don't work very well?
Tommaso
Click to expand...
Click to collapse
Steps in getting android to boot with the latest files.
1. Format your SD card in FAT32 and 2 ext2 partitions(one for the system and other for data) 256mb each. I found a gparted liveCD is the easiest way.
2. Try getting the latest basefiles from here...http://code.google.com/p/vogue-android/
3.Copy files to your fat32 partition, and you want to use a kaiser-default.txt, but change the resolution to what you like(or required) and rename to default.txt and use that. Also make sure you have the right .conf file in the /conf folder on your sd card.
4. Latest kernel makes the screen rotate upside down with the latest ext2 boot method for the kaiser so use the 10/23 zimage.
any way to increase the set amount of internal memory?
Tomorrow i will try... Thank you very much for your help!!!
Tommaso.
ajclai08 said:
Steps in getting android to boot with the latest files.
1. Format your SD card in FAT32 and 2 ext2 partitions(one for the system and other for data) 256mb each. I found a gparted liveCD is the easiest way.
2. Try getting the latest basefiles from here...http://code.google.com/p/vogue-android/
3.Copy files to your fat32 partition, and you want to use a kaiser-default.txt, but change the resolution to what you like(or required) and rename to default.txt and use that. Also make sure you have the right .conf file in the /conf folder on your sd card.
4. Latest kernel makes the screen rotate upside down with the latest ext2 boot method for the kaiser so use the 10/23 zimage.
Click to expand...
Click to collapse
I never have format my SD Card is several partitions... And everything is working. (exept GPS and Bluetooth for the given ION donut build)
Also never understoot will de system automatic detect the 2 ext2 partitions and will it use them automatic? Will also the system work faster?
Calibrate touchscreen:
"You can also calibrate the touchscreen by holding the camera button down (so that the keyboard is showing) while tapping the top right and then the bottom left of the screen. Do this while running the pointer location app in dev tools to check that it works. The keyboard now is the same as on the emulator."
Try this
kavejo said:
Hi, i'veput on the SD card the file you tell me...
I have tappedon haret.exe and Andoid start booting.
I saw linux boot string running on the screen, after that, when it was pased 2 minutes my screen goes black. I've attended 5 minutes, after that i did a soft reset.
[edit 1] I tried to attend 10 minutes but nothing change. [/edit]
[edit 2] I tried also use default.txt instead of default-kaiser.txt but haret freez booting, when the loading bar arrive at the end. [/edit]
Have i to sttend lot of time?
Or is my kaiser that don't work very well?
Tommaso
Click to expand...
Click to collapse
Open the default-kaiser.txt and edit the "htckaiser.panel_type=[Number]" with the number 1, 2 or 3 (try all of them, until it works).
dyetheskin said:
any way to increase the set amount of internal memory?
Click to expand...
Click to collapse
That's set in default. It's already the most you can (should ever) set it to. Remember the kernel and drivers take up memory as well
Android Failure
Hello Everyone,
I'm a newbie at this but I have read all the troubleshooting guidelines. Anyways, I have a Tilt (Kaiser), having issues loading the New Android. I'm the basefiles-20091116, have copied it to my microsd. I have edit Conf / to just have donut.user.
Now, when I run Haret.exe. I use the default-kaiser.txt to load Android, but after a few seconds I get a "Failed to find system.img on Sd card
/bin/shi can't access ttyi job control turned off " message.
Are there any suggestions to fix this issue?
Do you have a system.img/system.sqsh in the root directory of your sd card?
Android failure
To Whitehooptie, no I don't believe I have the system.img/system.sqsh your talking about. I've been looking for that in the basefiles. Can I find the system.img in the basefiles I've recently downloaded?
Cuzimbrownhuh said:
To Whitehooptie, no I don't believe I have the system.img/system.sqsh your talking about. I've been looking for that in the basefiles. Can I find the system.img in the basefiles I've recently downloaded?
Click to expand...
Click to collapse
Read the first post and you can see what you needed....
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!
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert
last updated: 2011-Oct-29 [DISCONTINUED]
ROM version described: 3.0.8
If you wish to use the data in this FAQ in any way, you are free to do so without any need for links\attribution, except for people mentioned in the FAQ itself - please mention them where applicable.
I'd like to thank Lee for the wonderful ROM, fred_be9300 for the initial FAQ, and anderl78 for... lots of help.
Also thanks to alpharev and others who are quoted or otherwise mentioned on this page.
Thread management
[DISCONTINUED]
======
1. What is the difference between A2SD+ and data++ versions of LeeDrOiD V3.x.x Bravo GB?
With Desire's stock ROM, little ROM is available for user apps as the \data partition is very small (147 MB).
With A2SD+ ROM, somewhat more is available, as dalvik cache and apps are moved to sd-ext. However, some data is still written to the \data partition, so no matter what, the "Internal memory" will decrease.
Data++ version gives you yet more internal memory for app installation than A2SD+ version, however, it is a little trickier to both flash and customize. As it does not move dalvik cache to SD, unlike A2SD+, dalvik cache still occupies a considerable amount of internal storage. This makes the system marginally quicker than A2SD+, at the expense of available internal memory and placing a cap on the total volume of installable apps (which is still considerably higher than in the A2SD+ version). Furthermore, it can be moved to sd-ext as well, freeing more memory still (see subsection "Things to know if using Data++" below, item 5).
To actually free more memory for user apps, data++ version moves a number of system files from \system partition to sd-ext. This in turn allows to redistribute the partitions of the phone memory:
- system partition is reduced to 90-100mb at the expense of files moved to sd-ext and\or deleted
- cache partition, originally 40 mb and empty most of the time, is reduced to 5mb
- data partition (the one shown as "internal memory" and available for your user apps\dalvik) is increased at the expense of the two mentioned above
This partitioning is determined by the hboot you use. So, in order to enjoy the benefits of data++, you will have to flash the required hboot first. There are currently several hboots that are compatible with LeeDroid Bravo GB. However, to obtain the maximum benefit you have to flash Oxygen hboot (revision 1), second best is Oxygen-r2. More details on flashing \ updating can be found in the respective section.
You can get an overview of different ROM variants looking at the picture Bravo ROM allocation.jpg by clicking the preview at the end of this post. The picture may be not very precise and perhaps even partially erroneous, but it will give you a graphical overview and it is correct in general.
Last point: data++ is NOT the same as Data2Ext. Simplified explanation: Data2Ext will increase the size of "internal memory" as percieved by your system to the size of your sd-ext (it may also usually require two ext partitions instead of one, etc, etc). Data++ will NOT increase your internal memory to the size of sd-ext; it will only free some NAND memory by moving some system files to sd-ext and re-allocating the freed space to \data by using oxygen hboot.
Things to know if using Data++:
1. As cache partition has been reduced to 5 mb in data++ version-compatible hboot:
- a ramdisk is used instead of it for caching downloads from the market. However, RAM is not used when not needed, so you should not worry about your RAM being squandered.
- to update the radio, you have to use fastboot ('fastboot flash radio radio.img'. Radio.img is to be extracted from the radio update.zip beforehand) or update radio using stock hboot prior to flashing modified hboot.
2. Since location of some system files has changed in data++ relative to stock ROM, flashing UOT kitchen mods and themes can be tricky. More on this below in the respective section.
3. Having sd-ext on sdcard may negatively affect the read\write performance of the fat32 partition (this one goes for A2SD+ as well, though).
4. There are two most suitable hboots for data++: oxygen r1 and oxygen r2. The difference between them is that r1 has a 90mb system partition while r2 has a 100mb one. As LeeDroid Bravo GB 3.0.7 has a system partition exceeding 90mb, you have two options:
- prudent option for people who have hands.sys and head.sys drivers installed on their system:
-- use oxygen r1, as it leaves more space in data partition hence more space for your apps
-- modify LeeDroid Bravo GB rom.zip in any of the below ways to reduce the size of \system folder:
--- open the rom.zip in either WinRAR, 7ZIP, Total Commander with an archive-reading plugin will also work, other methods have not been mentioned but might also work; do NOT unpack rom.zip, just open it
--- remove bootanimation (rom.zip\resource\customize\bootanimation.zip) and boot sound (should be somewhere near it) by pressing the del key inside the chosen app (WinRAR\7ZIP\TC)
--- and\or remove unnecessary stuff like wallpapers and jpegs and whatever you believe is ok from rom.zip\system\customize\resource
--- copy the modified rom.zip to sd card for flashing, keeping in mind you will have to turn off signature verification (as we've changed the rom.zip and the embedded signature is now no good) in the recovery prior to flashing (e.g in Amon-Ra it's Other\Toggle Signature Verification)
- strange option for people who are lazy and\or do not have hands.sys and head.sys drivers installed (what would they be doing flashing hboots and roms then is another question, particularly data++ roms):
-- use oxygen r2, as it has a 100mb system partition and no modification have to be made to rom.zip prior to flashing - but your data partition will be about 10mb smaller than with oxygen r1
5. Even if you install data++ version, which has dalvik in internal memory, you can move dalvik cache to sd-ext to free space for your apps at the cost of a small performance decrease. To learn more, see post by anderl78: http://forum.xda-developers.com/showpost.php?p=14297694&postcount=4751
6. If you want to go back from Data++ rom to a2sd+\stock rom, be it by flashing or restoring a nandroid, you will have to flash stock hboot first!
2. Requirments for flashing (i.e. before you flash, you need)
a. General requirements
- Rooted HTC Desire
- SD card partitioned into two partitions - FAT32 and EXT3 (EXT4 supported, haven't tried it but people confirm it works)
- hboot 0.93.x - some have reported successfully flashing with older hboots, but it usually took multiple attempts, so it's easier to S-OFF
- Desire should be fully charged, just in case
- It is always better to flash critical stuff using a notebook or UPS-connected PC for obvious reasons
To partition your card, you can use:
- your recovery
- ROM Manager app
- GPARTED (linux software for partitioning, also can be run on any PC using a boot-cd, site: http://gparted.sourceforge.net/livecd.php)
- minitool partition wizard (freeware windows partitioning program, site: http://www.partitionwizard.com/download.html)
- any other reasonably advanced partitioning program (such as Acronis Disk Director)
Keep in mind:
- both partitions should be primary (how to check if your partition is primary?)
- FAT32 should go first, EXT3\4 should go second (EXT4 claimed to be supported, not tested by author of this post)
- if partitioning via recovery\ROM manager, specify swap size as zero
- do not label the partitions
- reasonable size range for ext partition is 1-2gb
- if you are not experienced in partitioning, back up your sd card data (if you need it), for there are many ways to lose it when partitioning and only a few not to. You can just copy your sdcard data to a folder, then copy it back to fat32 partition if necessary.
- the last, but NOT the least: method of partitioning should be irrelevant, however, best results seem to be obtained by using GPARTED \ minitools partition wizard. Gparted is the surest way, but least convenient; minitool Partition Wizard is very easy to use and requires no reboots.
b. Requirements specific to Data++
- S-OFF
- Oxygen hboot downloaded and ready to flash
- Stock hboot in case you want to go back
Obtaining S-OFF is described here: http://alpharev.nl/ OR in detail http://forum.xda-developers.com/showthread.php?t=805811
Brief explanation (sapienti sat): download S-OFF CD http://alpharev.nl/alpharev.iso, burn it and reboot (or mount it as bootcd in a virtual machine and reboot), connect rooted HTC Desire, cross your fingers and follow instructions.
Flashing hboot is described here: http://alpharev.nl/ OR http://androidtricks.net/fastboot-custom-hboot-partition-table-htc-desire-52 OR http://forum.xda-developers.com/showpost.php?p=14259861&postcount=3683 OR read this post by anderl78 with detailed instructions of flashing it via fastboot.
Flashing hboot via PBIMG is in my opinion easier and is the only way I ever tried. Flashing via fastboot requires having ADB installed.
All necessary files can be found in the last section: "7. One-stop download reference".
3. Flashing guide
1. Make a Titanium backup of apps (optional but reasonable)
2. Make a Nandroid backup
3. Copy both backups (titanium and nandroid) to a PC for ultimate safety (optional but reasonable)
4. Have the following files on your SD card in the root folder:
- Lee's ROM (make sure to have modified the updater script if it's 3.0.8.2 Data++)
- Ext3 alignment patch
- [optional] radio if you update it from sd
- [optional] any other zips you may want to flash (kitchen mods, backlight mod)
- [optional] hboot files (stock and chosen oxygen) if you want to install Data++ using the PBIMG way
5. Flash recommended radio (32.56.00.32U_5.17.05.08), reboot to old rom to check in Settings\About phone\Software Information\Baseband version
6. Make sure you have an EXT3 partition as described in the Requirments section above (EXT4 claimed to be supported, not tested by author of this post)
7. [data++] Flash necessary oxygen hboot (r1 or r2) if you are flashing the data++ version
8. [optional but highly recommended] Perform a full wipe (can usually be omitted if updating from most prior sub-versions of this rom e.g. 3.0.x where x<8 but better to do this, you do have titanium backup anyhow). Still, you can always try flashing without wiping, and if it doesn't work or works but is buggy, you can reflash again with wiping.
9. [data++] Toggle signature verification to off if you are using oxygen-r1 hboot and have modified the rom.zip to reduce system partition
10. Flash rom.zip
11. Reboot and wait for the ROM to first-boot, which may take quite some time (up to 10-15-20 minutes is a safe bet; if you worry your battery will run low, nothing keeps you from connecting the charger)
12. If everything is OK, reboot back to recovery and flash optional mods if you have them (you can flash them right after flashing rom.zip prior to first-booting, but if the rom fails to boot it will be hard to determine the reason - maybe it's the rom, maybe it's the mod - so easier to flash after first-boot)
13. If you have problems flashing the rom \ first-booting, read the following section.
14. [optional] restore Titanium backup if you have one, but make sure you do not restore any red items. To totally make sure, you can choose to restore only user apps+data, and set up system settings by hand, if you like to be on the safe side.
Note: DO NOT flash EXT3 Alignment Patch as described on Lee's official page (step 3 of his flashing guide). With all due respect to Lee, flashing this patch has resulted in non-mountable sd-ext partition for many users. So do not flash it unless the rom won't start, as described in the following section.
The ext3 aligtnment patch has the following purpose, however, ROM works fine for virtually all who go without it and the opposite is not true. So the guidelines are:
- if it works without it, don't flash it;
- if it doesn't work without it, try flashing it
- if you you've flashed it first and the rom doesn't boot, use any partitioning software to delete the ext partition, then re-create it and flash without the alignment patch.
4. Troubleshooting ROM installation
Usually, failing to flash\boot the rom has the following causes:
1. Incorrect card partitioning - perhaps number one among other reasons.
To check for it, reboot to recovery (if you can't reboot by key combination, pull the battery). Try mounting sd-ext in recovery.
If it fails, this is indeed a problem.
Solutions:
- flash EXT3 Alignment Patch (http://leedroid.ftp.rshost.eu/Bravo_Addons/alignment-ext3.zip), then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- delete sd-ext partition in any partition manager such as Gparted \ minitool Partition Wizard and recreate it again, then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- if above fails, repartitioning the whole card (fat32 backup may be necessary if you have needed data on it), then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- if all above fails, ask the gurus such as anderl78 or mod-author, and don't forget to press the THANKS button once they have solved your problem
2. hboot - rom incompatibility, such as:
- flashing data++ rom on a device which is S-ON and\or has stock hboot (Solution: if so, S-OFF your device and flash correct hboot)
- flashing unmodified data++ rom with oxygen-r1 hboot (Solution: either modify rom or flash oxygen-r2 hboot)
- flashing a2sd+ rom on oxygen hboot (Solution: flash stock hboot)
- flashing rom on old hboot (<0.93): may take several tries, though I'd suggest S-OFFing as an easier alternative
3. Corrupt ROM file
- If flashing 3.0.8.2 Data++, modify the updater script as described here
- You may want to check MD5 signature for the rom file just in case
- If you have modified data++ rom to use oxygen-r1 hboot - make sure you did it without extracting stuff with consequent recompressing; make sure you haven't deleted anything not meant to be deleted
- If you tried integrating kitchen mods into rom.zip file - try flashing a vanilla rom, this way you'll determine the cause (maybe you modified rom.zip incorrectly, corrupting it)
4. Unrooted phone
Solution: Learn to RTFM and root your phone
You can read up here: http://forum.xda-developers.com/showthread.php?t=696189
5. Attempt to flash modified ROM without toggling signature verification to disabled
If you have modified your ROM, you have to toggle signature verification off; e.g in Amon-Ra it's in the menu Other\Toggle Signature Verification.
6. Other causes
If your problem does not fall under the above list, ask the gurus such as anderl78 or ROM-author in the MAIN THREAD, and don't forget to press the THANK button once they have solved your problem
5. Customizing guide
5.1. Kitchen customization - battery icon, etc.
To customize your phone by changing the appearance of top bar icons, notification panel, fonts, battery icon and the like you can use the UOT kitchen: http://uot.dakra.lt/kitchen/.
Just cook the file you need as described here http://forum.xda-developers.com/showthread.php?t=990829, then flash it from recovery.
Data++ customization
Now if you have installed data++ version, things may be somewhat complicated. This is due to the fact that in the data++ version, some system files are partially on sd-ext:
/system/app goes to /sd-ext/app_s
/system/framework goes to /sd-ext/framework_s
/system/media goes to /sd-ext/media_s
/system/fonts goes to /sd-ext/fonts_s
You can actually check it yourself by opening the rom.zip file.
As the files which are changed by the kitchen mod you have cooked are usually among the ones relocated, the mod has to be a little different from the standard.
There are several ways to do this:
1. When cooking the mod in the kitchen, set the "Kitchen\File Upload\Flashing for Data++ ROM option" to ON.
This worked for most users.
2. [OR] edit cooked file manually, replacing file paths as described below:
Open the theme's zip file (e.g. one from UOT) and edit \META-INF\com\google\android\updater-script file, changing paths of files that had been moved to sd-ext in the data++ rom. After that you can flash it from recovery as usual, having toggled signature verification to Disbled.
For instance, with the data++ version of 3.0.6 I used the following lines (could be different with 3.0.7 official data++, but enought to get the picture, and you can always figure out the paths and which of them to alter from rom.zip):
Code:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/sd-ext");
package_extract_dir("framework", "/sd-ext/framework_s");
package_extract_dir("app", "/sd-ext/app_s");
run_program("/sbin/busybox", "umount", "/sd-ext");
whereas original was like this:
Code:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("framework", "/system/framework");
package_extract_dir("app", "/system/app");
run_program("/sbin/busybox", "umount", "/system");
So it's the "spot 10 differences" game. Just check the official data++ rom.zip for files moved to sd-ext, then check what files are changed in the theme\mod zip, and alter the update script accordingly. Remember not to extract files and recompress them, but rather to open the archive and edit the script from the archive.
3. [OR] integrate the cooked file into rom.zip. To do this:
1) Browse through your cooked mod and see what modded files are in there. Usually its SystemUI.apk and framework-res.apk.
2) Extract these files to any folder.
3) Now open you rom.zip using WinRAR, 7ZIP, Total Commander with an archive-browsing plugin or any other decent software.
4) Locate the files you found in (1) and replace them by dragging the files extracted in (2) over them. E.g.:
You have extracted from the kitchen mod.zip:
framework-res.apk from the app\ folder
SystemUI.apk from the framework\ folder
to some temporary folder on your pc.
In data++ rom.zip, you'll most likely find
framework-res.apk in rom.zip\sd-ext\framework_s\
SystemUI.apk in rom.zip\sd-ext\app_s\
So, for each instance, you drag the respective file from temporary folder to the archive, and confirm if the program you're using asks if you want to replace the files. In any case, ignore the META-INF\ folder.
The resulting modified rom.zip should be flashed with Signature Verification toggled to Disabled in recovery, as we have modified it.
Troubleshooting:
Check if you have selected the right source files in the kitchen. In the UOT kitchen, on the FILE UPLOAD tab, under the heading "Select your rom from kitchen's list, or upload your own files", make sure you use "Kitchen's list", and select "LeeDrOiD 3.0.7 A2SD, ROM" from the dropdown. Alternatively, you can upload the actual files from the rom.zip.
If it still isn't working, then, most likely, you have incorrectly followed the above guide.
With all due respect, go to the main thread and bug people there - they will be very amused by yet another repetition of the "how do I flash the UOT kitchen mod on data++" topic... but will help you anyhow, as they are indeed nearly saints.
5.2. Adding notification panel widgets
The question of how to add widgets into the notification panel seems to appear every now and then in the main thread. There are many ways to do that. However, not all of them are easy\are easily customizable as the way I am describing below.
I solved it for myself by using the free Widgetsoid app.
It allows to make any number of highly customizable widgets, and can also place any of them in the notification bar.
The way to setup is first:
1. Install widgetsoid
2. Run it from the apps menu for initial settings:
ADVANCED tab:
- Flash led setting is METHOD 2
- Select desirable Brightness levels if you're going to use it (suggest using Seekbar first to get the hang of which levels are good for you, then using custom levels to set them up)
- I'd suggest setting "Widget focusable" to OFF, haptic feedback to ON
- Service in backgroud ON
NOTIFICATION tab:
- Hide notification icon to ON
- Open popup to OFF
Other settings you can change to your taste.
Then, to create your widget:
- Create a widget on your desktop, i usually use Widgetsoid Switcher 4x1 widget
- On network, Screen, Sound, Other, Shortcut tabs -- select which widgets are needed
- by clicking on a specific widget item in the preview you can move it to any place you want
- Go to theme tab, set it up to look as you want
- go to advanced tab, suggest following settings:
-- Modifiable - YES, you can turn it off later after you're sure you got what you wanted
-- Modifiable icon - up to you, I set it to off. What it does is show a small icon in top right corener which you can click to bring up widget editing screen; it works the same way without the icon, so it looks cleaner. It affects only the widgets placed on desktop, it won't be visible\usable in the notification panel widget
-- Notification - ON if you want to see the widget in the notification bar - so you want it ON
-- Widget invisible - as you want. If you check it, widget won't take place on your desktop, it'll only be visible in Notifications panel. Can't undo that later, so decide on the spot. You can always make another widget, though, if you later want to have one on the desktop and had made the previous one invisible.
-- Click Apply tab
It will ask you if you want to edit global prefs - no need to do that, so answer NO. The widget should appear in notification panel.
Some notes things:
- depending on notification panel style (transparent\white\other) you may want to change the color of your widget's icons so they are clearly visible (Widgetsoid app\Notification tab\Choose icon color). In transparent panel of 3.0.6-r2 it doesn't seem to work; as I remember, it worked with a white panel.
- In some cases, you may get a popup with the widget after you tap a widget item in notification panel after initial setup. If that happens, got to widgetsoid app, go to Notification tab, check state of "Open Popup" checkbox. If ON, set to off. If OFF but you still get the popup, check it to ON, then set it back to OFF, this solves the issue. It appears, you'll have to do that each time you add a widget to notification panel.
- If you made your widget visible only in notification panel and want to edit it, you can go to Widgetsoid app, go to Widgets tab, select widget you want to edit, tap the pencil button, edit as needed, tap apply tab.
- If you choose the widget to be Invisible on your dektop when you set it up initially, there is no way to uncheck this option if later you change your mind and want to see it on you dektop as well as in the notification panel. The only way you can do that is by recreating the widget.
- You can put more than one widget panel in the notification panel.
- If you use task killers (why would you want to?), make sure widgetsoid service is on the exceptions list.
VOILA, LeeDroid GB3.x.x with a notification tab switches in an easily customizable way!
PS you can watch it, if I am not mistaken, starting with 14:00 of the official widgetsoid video guide at http://www.youtube.com/watch?v=6pyf7U1cByI
6. Troubleshooting other issues:
There's not much issues I know of with this rom, unlike the HD ports. They may be user-specific, but I'm listing them here just in case.
- Lockscreen not appearing on power-on, i.e. after on button is pressed, phone starts direct to desktop.
Problem surfaced after several months of use. Fixed by reboot.
- When I want to select which calendars to be synced, I can only select [x] of my [x+n] calendars.
Fixed by clearing all data in the Settings>Applications section from processes containing the word Calendar.
7. One-stop download reference:
ROM links
ROM itself: see middle of this post
EXT 3 Alignment patch
Recommended radio 32.56.00.32U_5.17.05.08, MD5 03cd7972412bec4b4ed6f2699e4c9af0
S-OFF links
Site: http://alpharev.nl/
Live-CD used to S-OFF, MD5 3ca4c4803fe1eb309c980420788ad3f
HBOOT links
Site: http://alpharev.nl/
Bravo oxygen r1 (with 90mb system partition, alpharev took it down after releasing r2 for some reason):
- fastboot flashing: link courtesy of anderl78, OR backup link to same file, MD5 0ac1bd252276a7e81c24d601569746e1 (if you use the second link and want to check MD5, unpack .img first, then check MD5)
- PB99IMG flashing, MD5 4f19784ae373fbfd8c2e5de6d32696a0
Bravo oxygen r2 (with 100mb system partition):
- fastboot flashing, MD5 532e39f7b0e8cf9aff07d4556fe6d841
- PB99IMG flashing
Stock hboot:
- fastboot flashing, MD5 7bd5234711364880de1fa982dcf3a2d6
- PB99IMG flashing
Mods and fixes
- All mods courtesy of anderl78, so if you like them, I'd suggest pushing a THANKS button on the respective post by anderl78
- Nandroid prior to flashing is a reasonable policy
- Some mods may require toggling signature verification to "disabled" prior to flashing
Hardkey backlight always off (good for those who like to read at night), backup link
Bluetooth autoconnect
No-sense patches for A2SD+ and Data++ versions: for LD3.0.7 and for LD3.0.8
Camera tweak (media_profiles updated, reducing jpeg compression)
Unlimited browser tabs tweak
3G\EDGE\MMS not working:
- reset your APN to default (goto Settings\Wireless and Networks\Mobile networks\Access Point Names\ press MENU key on your device, choose RESET TO DEFAULT)
- if unsuccessful, enter APN details manually (your operator should know) OR see this post for how-to on importing a large APN preset list
Black HTC Home widget (flip-clock+weather), works for 3.0.x and 2.5.0
Various performance improvements
Autobrightness tweak for 3.0.8
Juwe11's Ramscript for Leedroid
Leedroid 3.0.8.2 data++ updater-script fix
Database defrag mod (frees internal memory, speeds up operation a bit, slows down boot a bit)
Tools
[url="http://www.paehl.de/cms/fastmd5_deutsch]Software to check MD5[/url]
GPARTED - linux software for partitioning, also can be run on any PC using a boot-cd
- site: http://gparted.sourceforge.net/livecd.php
- how-to: http://www.youtube.com/watch?v=sVK-tJe8pXE
MiniTool Partition Wizard - freeware windows partitioning program, site: http://www.partitionwizard.com/download.html
DISCLAIMER: whatever you do, you do on your own initiative and the results of your actions are your responsibility.
Hello s300pmu1!
respect, very good FAQ-Thread!
oxygen_r1 hboot (bravo_alphaspl-oxygen.img) http://db.tt/eNlzMrS
md5: 0ac1bd252276a7e81c24d601569746e1
hi,
indeed very well done.
I would suggest that this thread url is pasted to the OP Lee's thread. would be easer for everyone's as an howTO
awesome thread .. resolves most of the issues that crop up related to data++
Thx a lot. Seems to be complete and clear !!!
hi,
Is there a easy way to check if my sd-ext3 is set as primary? Im using Win7 and i try booting into Gpart via a usb drive, but it doesnt seem to detect my sd.
My sd-ext3 have been partitioned using RA when i flashed LeeDroid 2.4.0.
kobezt08 said:
hi,
Is there a easy way to check if my sd-ext3 is set as primary? Im using Win7 and i try booting into Gpart via a usb drive, but it doesnt seem to detect my sd.
My sd-ext3 have been partitioned using RA when i flashed LeeDroid 2.4.0.
Click to expand...
Click to collapse
Firtsly, if you partitioned using ROM manager \ Recovery, your partitions should be primary, because the writers of that software are not saboteurs
So you need to check it only if you partitioned the disk yourself using partitioning software and are no longer sure if you did it right (one can always forget).
If you're using Windows, it's very easy:
If you don't have a card reader or do not want to open your desire to get the card out of it:
1. Connect phone to PC with USB and boot into recovery
2. Enter USB-MS mode and wait for the PC to see your flash card
If you have a card reader and don't mind opening it to get the card out:
1. Open Desire, remove card
2. Connect card reader to your PC, stick the card into it, wait for the PC to see it
THEN:
3. In windows, press WinKey+R to get the Run dialog
4. Type DISKPART, wait for a prompt to appear (it could take some time)
5. type LIST and hit ENTER
6. It will show you a bunch of disks that are on your system. You have to find in the list the one which is your flash card (by the size) and mark its number.
7. Type SELECT DISK <disk number here> and hit ENTER
8. Type LIST PARTITION and hit ENTER
9. It will show you partitions and their types
10. After you're done, just close the windows with the mouse
ALTERNATIVELY, for the GUI-minded:
3. In windows, press WinKey+R to get the Run dialog
4. Type dikmgmt.msc and hit ENTER
5. Wait for it to initialize, locate your flash card in the bottom half of the screen, using scroll bar if necessary
6. It should show two partitions, xx.xxGB FAT32 / Healthy (Primary Partition) and x.xxGB / Healthy (Primary Partition)
7. When done, close the window.
OR, if you have acronis Disk Director, you can:
3. Launch it
4. Find your flash card
5. In the top half, partition types are specified
6. In the bottom half, you can check the color of the partition against the legend (primary is yellow, at least in version 10)
s300pmu1 said:
Firtsly, if you partitioned using ROM manager \ Recovery, your partitions should be primary, because the writers of that software are not saboteurs
So you need to check it only if you partitioned the disk yourself using partitioning software and are no longer sure if you did it right (one can always forget).
If you're using Windows, it's very easy:
If you don't have a card reader or do not want to open your desire to get the card out of it:
1. Connect phone to PC with USB and boot into recovery
2. Enter USB-MS mode and wait for the PC to see your flash card
If you have a card reader and don't mind opening it to get the card out:
1. Open Desire, remove card
2. Connect card reader to your PC, stick the card into it, wait for the PC to see it
THEN:
3. In windows, press WinKey+R to get the Run dialog
4. Type DISKPART, wait for a prompt to appear (it could take some time)
5. type LIST and hit ENTER
6. It will show you a bunch of disks that are on your system. You have to find in the list the one which is your flash card (by the size) and mark its number.
7. Type SELECT DISK <disk number here> and hit ENTER
8. Type LIST PARTITION and hit ENTER
9. It will show you partitions and their types
10. After you're done, just close the windows with the mouse
ALTERNATIVELY, for the GUI-minded:
3. In windows, press WinKey+R to get the Run dialog
4. Type dikmgmt.msc and hit ENTER
5. Wait for it to initialize, locate your flash card in the bottom half of the screen, using scroll bar if necessary
6. It should show two partitions, xx.xxGB FAT32 / Healthy (Primary Partition) and x.xxGB / Healthy (Primary Partition)
7. When done, close the window.
OR, if you have acronis Disk Director, you can:
3. Launch it
4. Find your flash card
5. In the top half, partition types are specified
6. In the bottom half, you can check the color of the partition against the legend (primary is yellow, at least in version 10)
Click to expand...
Click to collapse
Thank you so much for the detailed stepped.
I tried using the the steps with DiskPart as well as Disk Mgmt. But I can only see one primary partition on my 8GB SD, that is the FAT32 Primary with around 6GB+ size. I could not see the ext partition which I have partitioned to be 1GB.
Does this mean my ext3 is not primary? or Win7 just cant detect ext3 since it suppose to be for Linux?
Does this mean my ext3 is not primary? or Win7 just cant detect ext3 since it suppose to be for Linux?
Click to expand...
Click to collapse
It means, most likely, that something is wrong.
Win7 can detect sd-ext, though it will not be able to work with it.
Still, it will display the ext partition in both diskpart and diskmgmt.msc, and also show if it is primary.
How did you connect the flash card to your PC?
If you just connect your booted Desire to PC in "Disk Drive" mode, it will never show the sd-ext partition. You have to do it as described, from recovery or by using a card reader.
If you still can not see the sd-ext partition (BTW, what size is your card?), try partitioning it using recommended software (you can start with minitools partition wizard as it is much easier than Gparted and yields the same results).
first, I'm sorry I can't post my question in the main thread (not enough
posts ).
Question :
i have Leedroid 3.0.7 A2SD+ installed, everything seems fine, but I can see my internal storage free space going down and down (now only 5 mb) and at the same time the SD card (A2SD ext3 partition) still has 284 Mb free.
Anyone knows where the problem could be ?
Anyone knows where the problem could be ?
Click to expand...
Click to collapse
Yup. See the first post of this thread:
However, some data is still written to the \data partition, so no matter what, the "Internal memory" will decrease.
Click to expand...
Click to collapse
To get more memory, you will have to use Data++ version.
Or somehow integrate data2ext which will give you even more space (which is, however, rather complicated, and I assume, less stable).
s300pmu1 said:
Yup. See the first post of this thread:
To get more memory, you will have to use Data++ version.
Or somehow integrate data2ext which will give you even more space (which is, however, rather complicated, and I assume, less stable).
Click to expand...
Click to collapse
Hey guys,
Everybody just keeps saying that, but there must be a limit to data accumulation, isn't?
Even with data++, if it is just normal to lose 5mb each day without new installs or updates, well...
I'd address this question to anderl78\lee.
They are better equipped to answer it ^)
Just don't forget that apps do store data (e.g. gmail stores incoming mails somewhere, and this somewhere is most likely the \data partition).
TomLeeDesire said:
Even with data++, if it is just normal to lose 5mb each day without new installs or updates, well...
Click to expand...
Click to collapse
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
I'd address this question to anderl78\lee.
They are better equipped to answer it ^)
Just don't forget that apps do store data (e.g. gmail stores incoming mails somewhere, and this somewhere is most likely the \data partition).
Click to expand...
Click to collapse
Hello! I looked into the Rom configuration but could not find a problem that would cause this space consumption. Apps are saved in sd-ext, app-data is saved in nand Memory (internal).
Dalvik-cache is on ext or internal, depends in the Rom, is ok too.
In data++ is a little error, app-private (buyed apps) is not on sd-ext, its completely on internal memory. To change this, flash my dalvik2nand.zip ;-) (see link in OP) - perhaps its that? But this is only in data++ and not in a2SD+ ROM... I don't think this is the reason...
I looked into the space available here on my phone for a few days now, and I have to say nearly no space is gone... 116mb free to 115mb free in 3 days... Absolutely ok what I think. (data++ with the above dalvik2nand "extension" )
I think, the described problem is related to some apps, which are storing a lot of data in internal memory. If somebody have this problem, I recommend to see into "manage applications" sorted by needed space, or use "diskusage" from market to look, what app(s) are causing this.
One other thing I have seen is Titanium backup. After a flash I restored my apps with tb as usual. I wondered why some apps last so long to restore and suddenly i got a low space warning message. Looked into the apps and see for example xda-app using 90MB for data! Wiped all, restored nothing with tb, installed all from market and the problem is gone...
I hope this helps somebody... ;-)
Sent from my HTC Desire using XDA App
Ghisy said:
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
Click to expand...
Click to collapse
See my post above, you could use data++ without fear! ;-)
Sent from my HTC Desire using XDA App
Ghisy said:
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
Click to expand...
Click to collapse
Hey don't panic.
I am a happy data++ user.
Those 5mb were just a way to speak about this subject coming back every time.
I just can't stop installing and uninstalling apps so I have no real number to give you.
I also use a cache cleaner that frees some internal every day.
I just thought there would be a max data an app can store that would avoid explosion...
Thanks for your replies guys. I went ahead and updated to DATA++. I've checked apps sizes in the "manage applications" menu and they don't seem out of the ordinary.
I guess that's what you get when you have 130+ apps installed!
anderl78 said:
See my post above, you could use data++ without fear! ;-)
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
It may be something wrong with the A2SD version.. When I was using that I was constantly losing memory, I switched to the data++ version and no longer have the problem.. the memory always stays the same (give or take a few mb for app caches etc..).
Something seems weird with the A2SD version for sure.. (well that's what I think anyway lol)
himeshladva said:
It may be something wrong with the A2SD version.. When I was using that I was constantly losing memory, I switched to the data++ version and no longer have the problem.. the memory always stays the same (give or take a few mb for app caches etc..).
Something seems weird with the A2SD version for sure.. (well that's what I think anyway lol)
Click to expand...
Click to collapse
I can't believe it, cause a2sd+ Rom and data ++ Rom are using the same a2sd-script, the difference is, in easy words, only that the dalvik-cache is not moved to sd-ext in data ++ Rom. But I'm not the Rom-cook, perhaps I'm totaly wrong... I have only looked a bit into scripts and a few other things perhaps related to this - I'm not a real expert in this... Let's see, if lee provide us with more infos and perhaps a solution in his next build!
Sent from my HTC Desire using XDA App
credits
- almar (Marc)
- bsbsbs (Sándor)
- Egon
- phj (János)
- Voyteckst
- frenkie9999999
- spiderman1961
- kukafei
- linuxsight
- glimmling
- MinL
-Antoxa1998
thanks to all the above the dream of runing android on i8000 came true. and because of their job we were expecting faster and faster, more and more efficient and smooth versions.
i followed their path. got a version, modified it, combined the best parts of each ROM and i am offering a new ROM much closer to be complete and less beta.
DETAILS ABOUT THE ROM
It is not based on frenkiedroid as far as i know but followed other path onto chinese ROMS. I think it is faster than any other ROM (tell me if not). It has achived score 1035 on antutu on my class 10 sd card (this is almost the speed of a native android phone using cm6 and this fast hardware)
According to measuments made using Benchmark & Tuning it is up to 56% faster compared to the already fast frenkiedroid
Tested
bluetooth
wi-fi
3g
calling
sms
radio
gps
usb connection
battery lasts up to 2 days
Changelog
Version 8
Information, installation instructions and photos below (post no34)
http://forum.xda-developers.com/showpost.php?p=50188850&postcount=34
Alternative download of cm6new v8 with 2.6.32.9 kexec kernel
Download from here
Information, installation instructions and photos below (post no35)
http://forum.xda-developers.com/showpost.php?p=57062016&postcount=35
Version 7
Information, installation instructions and photos below (post no33)
http://forum.xda-developers.com/showpost.php?p=50188850&postcount=33
Version 6
Information, installation instructions and photos below (post no30)
http://forum.xda-developers.com/showpost.php?p=49775913&postcount=30
Version 5
Information, installation instructions and photos below (post no25)
http://forum.xda-developers.com/showpost.php?p=48486739&postcount=25
Version 4
Information and photos below (post no4)
http://forum.xda-developers.com/showpost.php?p=44427775&postcount=4
Version 3
(mirror) (sendspace service)
- fixed gsm not working with some SIM cards (now i hope it can work with all networks)
- improve speed compared to version 2
- fixed other bugs
Version 2
- improved build.prop
- fixed account problem
- fixed camera problem
- fixed some crash bugs
- installed suggested programs (freeware)
Version 1
(initial release)
This ROM has preinstalled only the basic programs to allow you add any other program you desire from market.
I also suggest you another package of apps (dialers, sms apps, pictures and video apps) here
Alternative kernels
froyob3 kernel
CM6B2kernel
mini kernel
medium kernel
big kernel (original)
Installation instuctions:
We backup our data on our card
download mini-tool
connect your phone with computer on usb disk mode for our sdcard της (alternatively you can select your storage, but here i describe sd-card installation)
install and run minitool
select your sd-card and erase all partitions.
create a) one partition primary fat32 (the sum of sd-card's mb minus 1533 mb), B) one partition primary ext4 for our android sized 1333 mb , γ) one partition primary linux swap with the rest 200 mb
select apply and wait
you decompress the file ROM and Tools.rar
We change the date of our computer on any date of sept 2011
we run ImageRecover.exe
select restore (normal) and next
search on your computer the disk, the folder that our ROM is stored ( .TBI file) and select it
on the new window select select the last down option
then on the new window select the partition of our sf card to install (this is the medium partition sized 1333 mb (will write next to it MBR1.....linux native) and click onto it and press next
On next window when see "all data on linux native partition lost" press "yes" and wait copying to reach 100%
reopen minitool an if after ext4 partition there is left some unused/unformated space (grey colour) delete linux swap partition and create a new linux swap primary partition including this time the previously seen unused space
when finish select settings on your phone and change usb connection mode on your phone to "my storage"
In the root of "my storage" we paste a) haret.exe, B) zImage, c) startup.txt from the folder "copy to storage card root" from the rar we downloaded and decompressed
Disconnect our phone from usb, enter "my storage" and run haret.exe
this is the end. android starts. hope you enjoy
Hi guys, any reports on testing this ROM?
I want to set up my old Omnia 2 with Android for my gf, so I'm looking for a stable and simple ROM for her.
Thanx.
sergio_sos said:
Hi guys, any reports on testing this ROM?
I want to set up my old Omnia 2 with Android for my gf, so I'm looking for a stable and simple ROM for her.
Thanx.
Click to expand...
Click to collapse
You can try either my ROM or twister2 ROM from here http://forum.xda-developers.com/showthread.php?t=2342764
they are both the same level
the fastest is mine
faster GPS in on mine (ms-based preconfigured)
wi-fi i think works a little better on twister
twister has preloaded facebook etc, while mine has only stock apps
mine has business (single) coloured menus while twister has fancy (multi) coloured menus
if you want to install optional apps that have ads and you are not expert on android then install twister
if you want to install apps that do not have ads (or have ads and you are android expert) you can choose mine
please not that some people mentioned that with my ROM their SIM card was not recognized. i am not sure if the same for your SIM, your country.
Only two ROMS to choose. so you need only a few hours to try them both and make your decision. the choise is yours
Samsung i8000 (omnia2) android cm6new rom v4
as I promised long ago to publish
SAMSUNG I8000 (OMNIA2) ANDROID CM6NEW ROM Version 4
- Support even more SIM
- Speed improvement - response
- Corrected some errors
- Upgrading of most programs
- Show ics (ice cream sandwich - android 4.0.X)
- Arrangements for energy savings
The new enhancements took me some time and study. I8000 reaches its limits due to its old drivers that are already written for mobile identical hardware with it.
Hope you like it and I expect opinions and suggestions to version 5 if there will be any further developments. Otherwise I will try to assist in the plan for android 2.3 on our mobile.
Explanation photo below
1 = home screen (the background is black on purpose because the amoled screen thus consumes less energy. If you want to change select another background with as many black dots. Black and not just dark color.)
2 = dialer with ics theme, search function names and support many languagesk. Make it default dialer if you like it
3 = new android ics Task Manager (task manager). Appear with long press of home button. If you do not like replace it with the Advanced Task Manager or ICS Task Manager / Switcher. To open them again by long pressing the central button select Settings / Cyanogenmod Settings / Input / Long-press home settings / select custom application
4 = ics camera
5 = menu ics (holo launcher)
6 = ics settings
For those who want even more contemporary look can choose Active lockscreen or Holo Locker
I tried installing this on my Omnia II.
I successfully create the partitions on my SD card, but when I go to starting the process with the ROM file, it comes back with the error message:
"The image file requires an updated version of this program."
I grabbed the latest version just to try it, and I need to purchase a key to make it work.
Yes, I reset my computer clock to September 1st, 2011. Do i need to reboot the machine after the clock reset?
Everything else so far seems to work fine, and if this works even half as good as I think it will, props to you for getting this done. I hate hate HATE winblows 6.5 on my Omnia II, and always wanted android. I tried a few of the older attempts years ago, but nothing was every stable enough to keep it.
Thanks again for any help.
where can i download the ROM ?
nemogamo said:
where can i download the ROM ?
Click to expand...
Click to collapse
download from here
http://www.gigasize.com/get/ndmo3y3hj2f
Ragnarkov said:
I tried installing this on my Omnia II.
I successfully create the partitions on my SD card, but when I go to starting the process with the ROM file, it comes back with the error message:
"The image file requires an updated version of this program."
I grabbed the latest version just to try it, and I need to purchase a key to make it work.
Yes, I reset my computer clock to September 1st, 2011. Do i need to reboot the machine after the clock reset?
Everything else so far seems to work fine, and if this works even half as good as I think it will, props to you for getting this done. I hate hate HATE winblows 6.5 on my Omnia II, and always wanted android. I tried a few of the older attempts years ago, but nothing was every stable enough to keep it.
Thanks again for any help.
Click to expand...
Click to collapse
ok try this ROM recovery program
http://www.gigasize.com/get/fososg405ld
please read very carefully instructions. hundreds of people verify programs are working how come not work only on some pc's ?
spkraul said:
ok try this ROM recovery program
http://www.gigasize.com/get/fososg405ld
please read very carefully instructions. hundreds of people verify programs are working how come not work only on some pc's ?
Click to expand...
Click to collapse
I tried this program, and again, comes up with the same error message.
I'm getting to the point where I have to change the date, then run image for windows, but it just keeps giving me that error.
I'm running windows Vista, could that be causing the issue? is there any other information I need to change or pay attention too?
I'm literally doing everything step by step, and yet its not working for me.
spkraul said:
download from here
http://www.gigasize.com/get/ndmo3y3hj2f
Click to expand...
Click to collapse
downloading.. take a longtime
would you mirror to mediafire or 4shared
thx.. will report when its done
nemogamo said:
downloading.. take a longtime
would you mirror to mediafire or 4shared
thx.. will report when its done
Click to expand...
Click to collapse
it's only 542.27 KB. how long time can get to download ?
even if you have dial up or the server is full you need seconds to download it
just make sure the time change is ok and better cut all internet connections before execute the program
spkraul said:
it's only 542.27 KB. how long time can get to download ?
even if you have dial up or the server is full you need seconds to download it
just make sure the time change is ok and better cut all internet connections before execute the program
Click to expand...
Click to collapse
i think you have mistaken me with ragnarkov
anyway i already downloaded the file
follow the procedure
until trying to restore image
got an error " the image file requires an updated version of this program"
internet id off
antivirus is off
date set to 1 september 2011
I've just tested it, the same problem I had as others already mentioned. I went back to the version 3, success! So I think the version 4 image is damaged or not correctly made. By the way, the version 3 that did work for me has no microsd card support. You should modify by yourself the startup.txt file to enable the sd card support.
Hope my words can be helpful to others.
santich said:
I've just tested it, the same problem I had as others already mentioned. I went back to the version 3, success! So I think the version 4 image is damaged or not correctly made. By the way, the version 3 that did work for me has no microsd card support. You should modify by yourself the startup.txt file to enable the sd card support.
Hope my words can be helpful to others.
Click to expand...
Click to collapse
i made my ROM to be installed on sdcard with sdcard support. Hundreds of users already installed it and no problems at all. i installed V4 again last night and no problem at all. my phone is i8000 8gb version if you install on storage card YES you should edit startup.txt and also edit vold.fstab and fstab files.
if find some free time from android 2.3 development project testings i will make a Version 5 and on this version i hope minor problems to be solved.
I downloaded the newest version of Image for Windows, which is v2.83 (the one in the package is v2.61), the tool to write the image into the partition ext4, and this time, everything went just like a charm.
I have to admit that the V4 image is a very good one. It's really fast and clean. I think the problem that we had before is caused by the lower version of Image for Windows. V2.61 can't load correctly the V4 image file, which I think is made by a higher version of Image for Windows. With the new version of Image for Windows, it's even not necessary to change the date.
The Chiese ringtones in this ROM are hilarious. I'm a Chinese, they are OK with me. But I think original ringtones would be better for common users, hehehe.
great work , will it work on omnia b7610 too !!
Where can I download mini tool ?
---------- Post added at 09:05 AM ---------- Previous post was at 08:24 AM ----------
aljo00 said:
Where can I download mini tool ?
Click to expand...
Click to collapse
found it
Will this work on the Verizon i920? Thanks in advance.
matthewtyson said:
Will this work on the Verizon i920? Thanks in advance.
Click to expand...
Click to collapse
technically yes it can run. but i do not own one to test it myself. you can try yourself and tell us your experiences. test on sd card installation first. it it pretty smooth and fast. you will be amazed. in case it will not work you can always check TwisterV2 ROM also very fast and smooth
see here http://forum.xda-developers.com/showthread.php?t=2342764
alternatively in case you meet some driver conflicts you can always use ubuntu and other ROM's drivers to edit this ROM and make it work for you.
spkraul said:
i made my ROM to be installed on sdcard with sdcard support. Hundreds of users already installed it and no problems at all. i installed V4 again last night and no problem at all. my phone is i8000 8gb version if you install on storage card YES you should edit startup.txt and also edit vold.fstab and fstab files.
if find some free time from testings i will make a Version 5 and on this version i hope minor problems to be solved.
Click to expand...
Click to collapse
I am facing the same issue, I cannot load my Storage Card.
1. I am confuse with term SD Card here. Is it refer to Storage Card or My Storage? Storage Card means external micro sd card, isn't?
2. I followed the instruction and put the Image to Storage Card. How can I activate the Storage Card Support by editting fstab files? Where can I find these files?
3. I had format Partition 1333Mb to ext4 File System, but I wonder why it always turn to ext3 after I restore TBI file(after ImageRecover step). Is it okay?
Thanks.