Related
So first of all i must say that im a completly noob at the android instalation on kaiser
I search for a noob tutorial but i coudnt fiind can someone post here a tutorial including files thanks
Here is the Guide in Sticky
How to replace Windows Mobile with Android (Guide) by Dukenukemx
scroll down to Installing Applications Onto SD Card using Ext2
This should help. The guide help me greatly, very easy to follow.
Hope this helps.
Its not tricky, I mean even I can do it, come on
I did edit a wiki page on this, but appears to be down, so here goes, from memory.
Backup any data first, just in case, not taking any responsibility for loss of data.
Firstly ensure your SD card if formatting correctly (FAT32), use on Gparted (linux live CD) to do this, (for me, I created two ext 2 partitions as well as I thought this would work best, works for me).
You then need the HaRET application to allow you to run Android. Google "haret.exe"
Extract the files this should create the right directory.
You then need to choose a build, this is personal choice, but I'll post the one I am testing right now. milanche's CyanogenMod 6 Kaiser
Put the installandroid.tar into the folder you created above.
Move to your SD card.
Find and run HeRET.
When screen shows text, tap and hold the center of the screen until you get a menu.
Choose install (ensure the options are set to SD).
Select Install
Once done, select Quit.
This then installs Android and can take a while, just leave it to get on with it.
You should then been booted into Android.
I might have forgotten something, as I am doing this from memory, but it should be fresh since I installed this last night.
Looks good to me, nice guide, don't think you missed anything
Thatnk you Zenity, but I know I couldn't have done this without your help in the begining when I first tried it. I know how it can seem all a bit over whelming.
I know a lot of people say 'search for it' but I did that just to see what I would find, and to be honest, I didn't get anything but that was of any use, so I can sympathis the search doesn't always get you the right results.
I could not remember the direcotry names when I wrote that at work and had to do it in a hurry as the entire office can see my magnified screen so it was a quick brain dump, not as nice as I would have liked to have written it given the time (which I did on the wiki but its down).
Anyway Keeps it fresh in my mind too.
I can only do this when I'm given the right files, I got confused myself when people started talking about different zImages. I tend to go for the builds where everything is bundled into one packing, as some can seem fragmented, ie Fresh Foryo, I don't doubt that it may be a good rom, but its deleivery is complicated (for me ).
Wish I had more time an experience to make my own build, I have done a bit of linix hacking in my time with shell scripts (getting wifi cardds working ona laptop etc), Its all interesting stuff.
thanks guys u helped me alot in the end i will instal android on an ext2 partition
Dear Leona,
The link seems no longer valid, can you tell where to find the latest HaRET application? Besides, how should I format my SD card? by special software? Thanks.
Dave
If you'd have problems with using Gparted Live CD like me... just because it does not mount SD card in adapter... here is what I did to partition the SDHC 4GB card...
I booted with HARET but did not select to install.. it gracefully fails to terminal
command: su
command: fdisk /dev/block/mmcblk0
deleted all current patrition (d)
created new partitions whith calculated size (8192 for 256MB)
changed type of the first and biggest patririon to FAT32 (t => c)
written all the changes to the partition table (w)
Than you should take out the card before rebooting and format FAT32 partition in win to upload all te android boot files, rebot the phone and follow with instalation...
But I must say, now I am using Scooters Cyanogen in NAND and it it far far easier
After I choose run, then a list of Linus commands ran, then it said
:loseup:/dev/block/loops: No such file or directory
Failed
Failed to reach system.img on SD card
By the way, anywhere I can download a complete set of files for running? Thanks.
try this:
http://forum.xda-developers.com/showthread.php?t=813382&page=31
look for the 4th post...
or this:
http://forum.xda-developers.com/showthread.php?t=855733
read a lot before attempting to do anything! use the search tool too, could be of some help.
For SD Partitioning, I remembered this Thread, which might help.
http://forum.xda-developers.com/showthread.php?t=619290
Sounds like you are not holding the centre Dpad button (or pressing the centre of the screen) while haret is loading, yes this can be Hit and Miss it winds me up no end.
If you have access to a Linux machine (or boot a Live CD), as well as being useful for SD partitioning it also maybe used to try out Atools (you'll need to install python and python-tk (via the package manager)) as this will get you the right Kernels, images and configure your default.txt file for you, though I haven't managed to get the build script bit working yet, but that is down to my lack of understanding the instructions
This is early, hacky, and built from the work of the guys on the Vibrant forums: http://forum.xda-developers.com/showthread.php?t=739647
anomalous3 figured out that "there was only one thing running as root that could safely be replaced; the boot logo player. So, all this does is replace the boot logo player with a script that calls userinit.sh from /data/local and then calls the (now renamed) bootlogo player for those of you who want that nifty startup screen"
What this does is allows the phone to mount an ext3 partition on boot so we can have a lag fix on JP3. I'm getting 1610 on quadrant and it's pretty stable. Please someone improve this!! shaunm89 and I just hacked this together from other's work.
Directions:
1.) Create an EXT3 partition on your external SD card of 2gb. It should be the second partition after the fat32 partition
2.) Flash Modaco's pre-rooted JP3 through Odin: http://android.modaco.com/content/s...insecure-boot-clockworkmod-recovery-for-odin/
3.) Boot the phone up. Open market and install Root Explorer (costs $) and Busybox. Update busybox
4.) Download these files: http://www.megaupload.com/?d=ONGUDAIJ
Copy them across to the SD card. Move playlogos1 and playlogosnow to /system/bin. Move userinit.sh to /data/local. Use root explorer to set permissions read (all 3) write (user only) execute (all 3). 0755 for those who know linux. You can use adb to push if you wanna get fancy.
5.) Reboot. Use root explorer to see if /sd-ext exists, and if so, whether /sd-ext/data and /sd-ext/dalvik-cache exist. If so it worked! If not, reboot again and then check.
That's it. Maybe someone can package this into an update.zip, maybe someone can take it and make it more stable and even faster (ext4 for example)
great! hope we could find an easier way
Sent from my GT-I9000
Is it a must to get the pre-rooted version of firmware? However using the original SP3 then root by myself?
On the other hand, I think I will modify your init.rc as I would rather to do all the moving by myself
Great job, hope we can get EXT4 soon.
In step 4, " Move userinit.sh to /local/data" should be data/local. Quadrant benchmark 1700.
seems like the script is calling busybox, but is it necessary to use root explorer. Could one substitute root explorer with adb?
I assume root explorer is just to do things adb can do, but locally on the device instead of attached via USB.
I tried this and it and i can see sd-ext and the subfolders but is this all we need to do?
is /data/data linked to the sdcard?
I am asking because i tried to reboot the phone without the sdcard in it and i can still see all my apps and everything is working fine.
Thoughts?
Also there is an error in section 4 of your instructions. there is no /local/data, it is /data/local.
Also playlogos1 and playlogosnow files needs to be renamed with a capital P for this to work.
No need to install root explorer if you can use adb to push the files. I just wasn't sure how to use adb to push to those directories.
I fixed the other mistake, thanks
This is not ideal but gets the job done. I'm hoping you guys can make it better!
Are you able to download anything from the market after doing this?
My market is just stuck on "starting download" and that's it.
clubtech said:
Are you able to download anything from the market after doing this?
My market is just stuck on "starting download" and that's it.
Click to expand...
Click to collapse
Protected apps don't show but i've been able to get all my other purchased and free apps installed and running fine.
Strange.
I'll flash again and try again.
Yea i don't know.
The market will download some and won't others.
Also my Quadrant test is getting stuck at 3/4 stage of the I/O test so it might be my SDCard which sucks.
I used a 16GB SanDik class 4 card.
clubtech said:
Yea i don't know.
The market will download some and won't others.
Also my Quadrant test is getting stuck at 3/4 stage of the I/O test so it might be my SDCard which sucks.
I used a 16GB SanDik class 4 card.
Click to expand...
Click to collapse
sandisk are one of the best cards you can get, kingston are known to get stuck at this stage, are you sure you don't have a fake sandisk card?
anyway if you leave it running after about 10 minutes quadrant will finish and still give you a massive score of over 1500.. just shows how reliable the quadrant scores are .
does it mean that quadrant is good but speed isnt?
Tried this fix on my JP3 but no luck. I don't get these folders.
Maybe it must be MoDaCo?
If I manually execute the script I get these folders, but after reboot they are gone.
Pretty new to this maybe I'm doing something wrong?
drygmasken said:
Tried this fix on my JP3 but no luck. I don't get these folders.
Maybe it must be MoDaCo?
If I manually execute the script I get these folders, but after reboot they are gone.
Pretty new to this maybe I'm doing something wrong?
Click to expand...
Click to collapse
Ok, did it from scratch today. Format, flashed MoDaCo prerooted JP3 and everything. Stilll I don't get this to work (
Please, any ideas?
Finally got it to run faster with this fix, thanks for sharing!
drygmasken said:
Ok, did it from scratch today. Format, flashed MoDaCo prerooted JP3 and everything. Stilll I don't get this to work (
Please, any ideas?
Click to expand...
Click to collapse
Also happened to me initially. /sd-ext won't show up or if it does, it doesn't contain the correct folders though it is listed when you run 'mount'. Laggy with Quadrant result at 975.
So, went back and reformatted SD w/Fat32 then EXT3, cleared cache/data, re-flashed Modaco's JP3, installed the latest Busybox, copied files per OP and I finally got it working after a couple of re-boots (3, i think). It is running smooth so far w/quadrant 1622. GPS seems to be getting locks on SATs quickly but you still can't get to LBSTest via the keypad. Still can't write to the external sd when mounted/shared to PC.
Also tried JAC's work (see this thread: [KERNEL/RECOVERY] Vibrant EXT2/3/4 with init.d support) since it has the nifty feature allowing user to put startup scripts on boot up. I flashed his kernel but i got stuck on the 'Vibrant' boot screen. anyways, will give it another try later.
titovic said:
Also happened to me initially. /sd-ext won't show up or if it does, it doesn't contain the correct folders though it is listed when you run 'mount'. Laggy with Quadrant result at 975.
So, went back and reformatted SD w/Fat32 then EXT3, cleared cache/data, re-flashed Modaco's JP3, installed the latest Busybox, copied files per OP and I finally got it working after a couple of re-boots (3, i think). It is running smooth so far w/quadrant 1622. GPS seems to be getting locks on SATs quickly but you still can't get to LBSTest via the keypad. Still can't write to the external sd when mounted/shared to PC.
Also tried JAC's work (see this thread: [KERNEL/RECOVERY] Vibrant EXT2/3/4 with init.d support) since it has the nifty feature allowing user to put startup scripts on boot up. I flashed his kernel but i got stuck on the 'Vibrant' boot screen. anyways, will give it another try later.
Click to expand...
Click to collapse
Which method do you use for making the ext3? I made my on my hero using Amon RA could that be a problem?
drygmasken said:
Which method do you use for making the ext3? I made my on my hero using Amon RA could that be a problem?
Click to expand...
Click to collapse
I used GParted Live CD as Paragon fails to format my AData card and sorry but I am not familiar with AMON RA.
1646 thanks, very fast!
Sent from my GT-I9000 using XDA App
Would this procedure work for ext4 partitioned SD Card?
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
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Clawsman said:
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
Click to expand...
Click to collapse
Full wipe wipes /cache, /data and /sd-ext to my knowledge. There is a possibility some of the files remain on /system. Use 4EXT to manually format each partition using format option.
Clawsman said:
it says.. "[email protected] #11"
Click to expand...
Click to collapse
That seems in order. Long name in attach marks modules added to that kernel.
Sent from my HTC Desire using Tapatalk
Ok
well.. i did the format manually in 4EXT.
I suspect some files still to be there..also some boot files containing malware script.
what file contains the boot script? i mean.. what file is the first to be triggered when booting in HBOOT. because many things in the recovery doesnt seem right. and the hboot fastrecovery starts with a delay.
Like when i want to partition or when i want to format all partitions except sd. Acts like it doesnt want to.
Anyway.. was just wondering if i could just adb and delete every file folder that is in in my phone and then flash recovery and ROM again.
Is that what RUU does?
is that something to recomend?
RUU is complete wipe of everything. /system, /hboot etc.
Download the correct one for your phone, *follow its instructions* (may need a gold card - google it) and run it on a clean pc.
Clean your pc ie format and reinstall after taking backups.
Then start again wit ha new hboot/rom setup.
Is that even possible? Infecting an Android phone via a Wi-fi network?
And Recovery shouldn't be able to get infected. I think ONLY /data can, and eventually /system if it's mounted as RW.
But on a wipe data gets deleted, and on a ROM install /system and boot (which holds the kernel and ramdisk) is deleted anyway.
RADIO starts before HBOOT. And there's absolutely no way they can be infected.
To be safe:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase recovery *OVERKILL*
Then just do fastboot flash recovery {RECOVERY}
And there's nothing more you must do. HBOOT reflashing is 100% pointless.
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
TVTV said:
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
Click to expand...
Click to collapse
I do what i can. There are many devs that know much more than me. Your thanks are appreciated
For me it's still strange, tho. Only data and system could be "infected"
Take a look at this: http://forum.xda-developers.com/showthread.php?t=1399076
It's a scheme i made on how HTC and Nexus devices work. (How they boot, what are the individual partitions, etc)
Clawsman said:
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Click to expand...
Click to collapse
An example of those infecting file?? What file in your root partition?? What path? Rom files are only on /system
Inviato dal mio Galaxy Nexus usando Tapatalk
I never use a anti virus and until now never have a problem...As i know!
Well it happened to me..
I have deleted everything.. I remember i checkd my log, and busybox files was moved to the system folder.. And all kinds of services was attached to Google map, calender, Facebook, wifi apps, market, etc..
And new apps installed like vpn, cam apps, recorders.. etc
Im currently using the free lookout...
And want to Buy a security tool.
Any advice Will be much appreciated.
Sent from my HTC Desire using xda premium
Hi,
First i will say thanks for the great rom, i will try it asap (a little bit more stable)
i read about this rom in the topic since it was started .
i have some Questions, it will be my first "clean" Android (without Sense)
There should be a installer after first start of the rom after flash? Where can i found more information about the things i can chose?
Evervolv toolbox, is that an addtional Settings Dialog with more Options or still a app which can be used as "standalone"
(sorry for the bad english)
When you install it you will get some options to choose a launcher and a2sd-script.
On first start you won't get the app to set your g-acc and so on, you'll have to do that in the system settings.
And the Evervolv-Toolbox are additional settings the this rom it's not a standalone app.
Hope this helps
grtz
Please note that Sandvold ICS v. 0.4.2.1 has some stability problems at the moment. Many people experience "black screen of death", device fails to turn on screen after a period of inactivity, battery has to be removed to reboot. I found that raising the minimum CPU speed from 245mhz to 384mhz completely removes this problem. With this small tweak the rom is great! You *should* be able to change this setting with Evervolv toolbox, sadly it does not work. For some reason the toolbox runs with insufficient rights to tweak cpu speed, I did my own scripts to set cpu speed from the console instead.
cheers
/Stig
stig_dk said:
Please note that Sandvold ICS v. 0.4.2.1 has some stability problems at the moment. Many people experience "black screen of death", device fails to turn on screen after a period of inactivity, battery has to be removed to reboot. I found that raising the minimum CPU speed from 245mhz to 384mhz completely removes this problem. With this small tweak the rom is great! You *should* be able to change this setting with Evervolv toolbox, sadly it does not work. For some reason the toolbox runs with insufficient rights to tweak cpu speed, I did my own scripts to set cpu speed from the console instead.
cheers
/Stig
Click to expand...
Click to collapse
Black-screen-issues can be solved by flashing MIUI-kernel:
http://www.miui-au.com/wp-content/plugins/download-monitor/download.php?id=166
Hi! I use ICS since beta 0.3.9 and I'm now updated to 0.4.4
This release seem very stable now. Just remember that the camera preview doesn't work. Also, you might have some problem with MMS.
App space problem
Hello - some help for a newbie please (well Desire newbie)...
I did try reading though Sandvolds thread, and I have tried to remedy, but I don't seem to get much further ....
I am running an ICS beta on my tablet, so I thought it would be interesting to try it on my Desire too. On the tablet there is more memory, so I have never experienced space problems with apps.
I rooted the Desire OK - and flashed 0.4.2.1 ... ran fairly smoothly, but hit space problems when trying to load up some of my favourite apps. I have a 16gb sd card. I downloaded apps2sd from the market - and moved some of the apps. However still not able to update some system apps from the market due to insufficient space (even though there appears to be enough).
Reading the other thread, I have gathered some/little understanding... and so before flashing 0.4.4 I reformatted my SD card from recovery choosing the largest ext4 that I could.
I was then ready to go to try 0.4.4.
On trying the Amarullz script and Nova launcher - I was having lots of lag after boot and I kept getting prompted to enter PIN number and reboot the phone. (I had done a factory wipe and cleared Dalvik after flashing the ROM).
I then reflashed choose Apex launcher, stock Kernal and data2sd option.
I wiped after flashing, did a few waits and reboots - as others recommended this.
Now seems to run quite smoothly, I have added back a bunch of apps via Titanium Backup ... but I don't see any apps 'automatically' being moved to sd card. I have moved as many as I can manually.
But I can also see that I am going to run out of space again soon ....
If I look in the settings at storage I see...
Internal storage - Apps 104MB Available 26.86MB
SD Card - Apps 239MB
Am I doing anything wrong?
Looloup said:
Hello - some help for a newbie please (well Desire newbie)...
I did try reading though Sandvolds thread, and I have tried to remedy, but I don't seem to get much further ....
I am running an ICS beta on my tablet, so I thought it would be interesting to try it on my Desire too. On the tablet there is more memory, so I have never experienced space problems with apps.
I rooted the Desire OK - and flashed 0.4.2.1 ... ran fairly smoothly, but hit space problems when trying to load up some of my favourite apps. I have a 16gb sd card. I downloaded apps2sd from the market - and moved some of the apps. However still not able to update some system apps from the market due to insufficient space (even though there appears to be enough).
Reading the other thread, I have gathered some/little understanding... and so before flashing 0.4.4 I reformatted my SD card from recovery choosing the largest ext4 that I could.
I was then ready to go to try 0.4.4.
On trying the Amarullz script and Nova launcher - I was having lots of lag after boot and I kept getting prompted to enter PIN number and reboot the phone. (I had done a factory wipe and cleared Dalvik after flashing the ROM).
I then reflashed choose Apex launcher, stock Kernal and data2sd option.
I wiped after flashing, did a few waits and reboots - as others recommended this.
Now seems to run quite smoothly, I have added back a bunch of apps via Titanium Backup ... but I don't see any apps 'automatically' being moved to sd card. I have moved as many as I can manually.
But I can also see that I am going to run out of space again soon ....
If I look in the settings at storage I see...
Internal storage - Apps 104MB Available 26.86MB
SD Card - Apps 239MB
Am I doing anything wrong?
Click to expand...
Click to collapse
1). www.revolutionary.io use this
2). www.alpharev.com download cm7r2.img
3). flash the hboot
Code:
fastboot flash hboot hboot.img
4). re-flash 4.4 and choose stock a2sd
5. enable a2sd
Code:
su
a2sd install
#choose settings#
Thanks for quick response..... I have a fee more questions....
I originally rooted my Desire via revolutionary .... do I need to do it again?
I guess I then flash the zip file.
The fastboot command - can I do this from the terminal app?
hi,
fastboot command and adb must be running from computer.
you need to instal sdk android sdk android
if you run revolutionary, u don t need to do once again but to flash an hboot you must be Soffed.
dunno if revolutionary does the job... i used alpharev to do son gain S-offed and able to flash hboot from fastboot command.
I saw the option to install agps in the installer but i chose gps. How can i add the agps when i already installed the rom? Because getting gps fix in navigation is taking way to long, so long that i abort it while trying
Getting closer
@bortak
1. Done OK
2. Done OK
3. Done OK
4. Done ... BUT ... no Gapps, no Terminal app ... not much really not even a keyboard (even after 2 reboots)
- The link to Gapps for CM7r2 no longer works
5. Unable to try this as no Terminal app ... and I can't get ADB working on my PC.
where have my apps gone?
So I can't get cm7r2 to work, so I reflashed hboot back to standard, I then reflashed 0.4.4 choosing stock a2sd. I installed a2sd via terminal and moved cache too. After reboot I installed a bunch of apps .... and eventually ran out of space - as if apps not being moved.
I then rebooted, and all of the apps except the paid apps have gone. I installed a couple of apps from the. Market and they have also gone after reboot.
I turned a2sd off, then I was able to keep apps over a reboot ..... but I would like to get a2sd working.
Any ideas?
For now I am manually moving apps to SD card.
Sorry for this question...
Your 3G, Wifi is working.. My wifi, 3G is not working..
3g (once APN set up) and wifi both working well
Looloup said:
@bortak
1. Done OK
2. Done OK
3. Done OK
4. Done ... BUT ... no Gapps, no Terminal app ... not much really not even a keyboard (even after 2 reboots)
- The link to Gapps for CM7r2 no longer works
5. Unable to try this as no Terminal app ... and I can't get ADB working on my PC.
Click to expand...
Click to collapse
Did you do a wipe after flashing the rom? I had a similar problem when doing that. CWM Recovery also deletes the sd-ext partition, and as on cm7r2 there are also system apps on sd-ext, they are gone.
With the included a2sd apps should be moved to sd-ext automatically. It is not shown on the phone.
How big is your ext4 partition? And did you create it with CWM Recovery? If so, try recreating with gPartEd.
muellersmattes said:
Did you do a wipe after flashing the rom? I had a similar problem when doing that. CWM Recovery also deletes the sd-ext partition, and as on cm7r2 there are also system apps on sd-ext, they are gone.
With the included a2sd apps should be moved to sd-ext automatically. It is not shown on the phone.
How big is your ext4 partition? And did you create it with CWM Recovery? If so, try recreating with gPartEd.
Click to expand...
Click to collapse
This.
10chars
I created the extra partition via CWM recovery - maybe too large as I made it 4gb.
I wiped the device and Dalvik cache after flashing the ROM.
I then set a2sd via terminal and allowed reboot.
I then downloaded apps (or restored via Titanium)
Eventually ran out of space when downloading apps - so they were not being moved.
Apps run OK.
When I did a normal reboot - the apps 'disappeared '.
Reading Bortaks debug guide the only thing I can see that looks relevant is to try reformatting the SC card with 2 primary partitions.
Read what i wrote? Do the following:
1) Recreate the partitions on your sdcard using GParted
2) Do a full wipe BEFORE flashing.
3) Re-flash the rom and select stock a2sd
4) Do NOT wipe again
4) Reboot, start Terminal emulator, set up a2sd
5) See if apps stay
On my first try I selected stock A2SD and set it up as explained using the terminal. (using a 2GB ext3 partition, placed after FAT32)
I rebooted and everything seemed fine, and I installed several apps. After a while, though, I got the "insufficient storage" error whenever I tried to install something. In the application manager the internal memory available had a large negative value.
I then wiped everything, reformated the 2GB ext3 partition to ext4, using "Minitool parition wizard" and reinstalled the Sandvold ICS ROM with Amarullz. Everything seems fine, and it shows 2GB internal memory. However, I've noticed that the ROM gets more unstable the more apps I install (it shows 500MB installed apps now, after removing around 50MB)...
Most of the time what happens is that system apps start crashing (Google Music, Dialler, Contacts, etc.) out of nowhere. After a while normal apps crash on execution as well. Google music is useless, as it crashes after a few songs and brings down the whole phone. Other music apps don't have this problem.
Am I doing anything wrong with the way I set up Amarullz? Should I retry stock A2SD with ext4?
I'm using stock HBOOT, Nova launcher and stock kernel.
Got there ..... but.....
After repartitioning my SD card for the third time ... I finally have this working.
Thanks to all for help/advice ..... but (isn't there always a but) ....
Downloads from the Market/Play are extremely slow maybe 5+ times the same apps took before .... I have tried on different WiFi connections - still the same.
Is this a consequence of the write speed of my SD card (it is only class 4) ... I did see a post in another thread where a class 4 wasn't recommended, but this was refuted by others using a class 4 card.
Otherwise all apps seem to be running OK, with no real loss of performance.
I guess once I have finally loaded up on all the apps I want, the Play updates will be more infrequent and less of an issue.