[Kaiser] Boot Android from SD-card - Tilt, TyTN II, MDA Vario III Android Development

I don't want to install Android on SD/NAND, I just want to boot it once to experiment a bit. It worked great on my Prophet (booting) but I don't really know how I have to do it on Kaiser.
Everytime I boot it says "Hold down DPad Center to launch installer" but I don't want to install it. I just want to run it. If I don't press the DPad Center it crashes with "Failed to reach system.img on SD Card" because I have "androidinstall.tar".
Can someone explain this to me?

This system is outdated now, we don't use system.img's anymore, the builds have got way to universal and technical for that. If you want to test android out just install it selecting the options for data and system on sd card. It will be slow but it will run off of 2 files called system.img and data.img to my knowledge. This is the only way if you don't want to create ext2 partitions for system and data on your SD Card. Read through the FAQ's and how to guides which are stickied at the top of the forum, they will guide you through.

Thans. Problem is I never get the "Sys on SDcard" and "Data on SDcard" options. It just asks to install, then says "Warning! Current system will be overwritten".

The 'current system will be overwritten' message refers to any install you may have on SD, when running from Haret you will not have the sys on SD option, since this option only applies if you are running the installer on a Nand-enabled system.
With haret install the installer already knows you will be installing to SD and gives only the Install option, since there are no MTD Partitions available to it.
All that will happen is that the installer will use the androidinstall.tar to install to SD, which you will then be able to run from that SD using Haret.exe.

Hey, I am having the same problem... when I try and boot using haret on my 1 gig fat32 sd card (polymod 2.1) I get ....
Hold down volume up or Dpad center to launch installer
I have tried it both holding down the center dpad, (on the bottom of the phone) and not hitting anything. Either way it immediately skips past that part and gives me:
sh:2 unknown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD Card
Am I doing something wrong... or what you seem to be saying is there are more modern instructions available now... the ones i'm following are on the htconandroid wiki (can't link as I'm a new poster).
I'm using the ATT Kaiser .... and would really really appreciate any insight... links to better guides... help etc...

The Haret method seemed not to be working for newer install .. check here:
http://forum.xda-developers.com/showthread.php?t=680963
and
http://forum.xda-developers.com/showthread.php?t=705337

so from the android installer, first time i go 1. install system.
this then says "this will wipe your existing system, are you sure?"
if i select yes, it will install to SD card folder and not overwrite windows?
i havent dared press it as i dont want to ruin my phone....
will it just install to sd card?

If you are running from Haret, the it cannot wipe WM, when it says it will wipe the system, that means any Android build you already have installed to the SD card.
To make this clearer if I can.
Nand install: This method requires you to flash a small NBH file to the phone, this Will wipe WM, after this nbh is flashed, every time you boot the phone it will boot linux in order to either install or run Android directly from the phone. You have a few different options using nand, system and data on nand, ( most common method), or system on SD, data on Nand, ( never seen wnyone use this ), System on nand, data on SD, ( this is another comon way of installing, gives more space for user data, and system on SD, data on SD, ( never seen this used either ). All of the above versions require you to flash the kernel and support files to nand.
Haret install: by far the best method for new users, this does not wipe WM, and uses the SD card for system and data, you simply put the required files on SD, run Haret.exe from WM, and it then unloads WM from memory, ( but not from Nand, if you reboot it will go back to WM), it will then load the kernel, and then either the installer, ( you still have to press+hold dpad centre, volume up, or centre of the screen [yes really, my preferred method in fact, can't accidentally press the wrong key that way]). The installer can only install to SD when using Haret, and what it does is to make a system and data image for haret to use after installation, these files are what the installer refers to when it tells you it will wipe the system, not WM, just the system and data image files on SD.
Hope that clears up a few things

Related

[Q] A few questions I need answered

I have a few questions:
1) Which is better? The Cyanogenmod 7 or The Nightly builds?
2) I really like the Sense UI. After flashing Cyanogenmod 7, can I change my "theme" to Sense UI?
3) Which ROMs you can recommend me? I like to use the Sense UI. So till the time ROMs have Sense UI, I'm cool with it. Most of the ROMs I see have different themes which I kinda don't like. I got a few other ROMs with Sense UI but they needed to do some partition in the SD card and stuff which didn't really go inside my brain
4) After performing a Nandroid backup, I should flash my rom. So why do a few devices get bricked? Can't they just restore the backup and be back to normal version again?
5) After rooting, should I connect my phone to any HTC online services?
6) If HTC future updates come out and I'm on my rooted phone then will the update automatically install itself or I need to backup to the original version and then update my phone?
Sorry, I'm really new to all this. So please don't flame me
Hi !
1) You may go with the nightly builds, they seem to be quite stable as a daily rom. You can reflash an old build if one is buggy anyway.
2) You can't switch to Sense UI with a Cyanogen 7 installation, but you can install Launcher Pro or another launcher and then apply a theme that looks like Sense.
3) Leedroid is by far the most known Sense rom on Desire. You can also look after Teppic74's rom and addons which are also nice if you don't want a rom that has an infinite nomber of addons or changes.
4) Pay attention not to change your recovery when you backup an old rom. You have to restore with the same recovery you backed up your rom.
5) You must be talking about HTCsense.com, this online service has appeared with Desire HD and Z, it isn't available on our Desire Froyo roms at the moment. If you want to try HD Roms and others with a later version of Sense UI, you won't be forced to connect to this service.
6) When a future updates come out, if you want to install a stock RUU, you'll only have to create a goldcard before installing the RUU. No matter your Desire is rooted or not, after the RUU install, you will be S-ON and unrooted.
But you should wait for developers to release roms with the new HTC update, therefore you won't have to root and S-OFF your device again.
Welcome on XDA
Hey, thanks for replying mate
I didn't understand the 4th point. Sorry I'm a noob at this
for the fifth point, I was talking about sync and other services.
Sorry, I misunderstood your 4).
Your device won't get bricked if you pay attention to what you are doing when flashing.
Make sure before any flash to :
- Check the MD5 hash of your rom
- Wipe Data, Cache, Dalbik-Cache when it is needed
for the fifth point, I was talking about sync and other services.
Click to expand...
Click to collapse
Do you talk about Google sync (calendars, contacts, gmail), Facebook, etc. ?
Oh okay. I got it and how do I install Leeroid? I don't see any tutorials around..
- Download .zip : http://leedroid.ftp.rshost.eu/Bravo-ROMs/LeeDrOiD_V2.4.1_A2SD.zip
- Copy your .zip on your SD card
- Root your phone with Unrevoked (you can find some tutorials around here)
- Turn off your phone, press volume down+power button to boot into bootloader and select RECOVERY.
- Wipe Data, Cache and Dalvik Cache
- Flash Leedroid's rom.
Maikoru said:
- Download .zip : http://leedroid.ftp.rshost.eu/Bravo-ROMs/LeeDrOiD_V2.4.1_A2SD.zip
- Copy your .zip on your SD card
- Root your phone with Unrevoked (you can find some tutorials around here)
- Turn off your phone, press volume down+power button to boot into bootloader and select RECOVERY.
- Wipe Data, Cache and Dalvik Cache
- Flash Leedroid's rom.
Click to expand...
Click to collapse
Sorry, but imho your guide is incomplete. I write the necessary new things in red:
- Download .zip : http://leedroid.ftp.rshost.eu/Bravo-ROMs/LeeDrOiD_V2.4.1_A2SD.zip
- Copy your .zip on your SD card
- Backup/copy all data of sd-card on your computer, just in case;
- Root your phone with Unrevoked (you can find some tutorials around here): noob-guide: http://forum.xda-developers.com/showthread.php?t=1016084; for advanced users: http://forum.xda-developers.com/showthread.php?t=696189
- Save your systemdata and apps; i recommend Titanium Backup (Menu>Batch>”Backup all systemdata and apps”).
- Turn off your phone, press volume down+power button to boot into bootloader and select RECOVERY.
- Made a full nandroid-backup. Reboot your phone. Copy all data on the sd-card to your computer again.
- Turn off your phone, press volume down+power button to boot into bootloader and select Recovery; now select "partition sd-card" and then "partition sd". Set 0 MB for SWAP, 512 MB for ext3 and rest for FAT32. If you cannot create ext3, create ext2. After complete partitioning, select "SD: ext2 to ext3". Now go back and select "USB-MS-Toggle". Now copy all the saved data back on your sd-card. Is this complete, select "other" and "toggle signature verify".
- Wipe Data, Cache and Dalvik Cache
- Flash Leedroid's rom.
- Restore all missing systemdata and apps (Titanium Backup>Menu>Batch>"Restore all missing systemdata and apps").
- Restart phone
First start can take some time, because all apps were moved to the sd-card.
Never post such incomplete guides, please.
My bad, I gave him an incomplete guide, but there are also plenty of them around this forum and Google.
Searching isn't hard : http://forum.xda-developers.com/showthread.php?t=1016084
Thank you for your replies guys
Also, will the tutorial work with Cool Sense? (http://forum.xda-developers.com/showthread.php?t=899943)
It will, don't forget to flash this .zip : http://wbss.ro/coolexe/Extra/Alignment_Cool.zip before installing the rom. (This .zip will convert your ext3 partition on your sd to ext4, and it will also align that partition)
Okay And what's the use of partitioning the SD? Does it increase the Storage space (Internal Memory)? I saw it on one of the ROMs. Not sure which.
And what are radios?
The Radio of your device is the thing which makes it possible to call and to have mobile internet. And some radios should be better than others, so they should increase battery life or so but i never felt a difference with different radios yet.
Royal King said:
Okay And what's the use of partitioning the SD? Does it increase the Storage space (Internal Memory)? I saw it on one of the ROMs. Not sure which.
And what are radios?
Click to expand...
Click to collapse
The use of partioning is, that u are able to save data on the sd.
If you ask, why you should do it with this ext3- partition (i do not know why you need swap-partition; i just set it to 0 MB, as i was told ): With this ext3- partion all apps you install are automatically moved on the sd-card, wether the programmer has destined it or not. On this way you consume less space internal memory, by what you save/increase indirectly internal memory. This function is available for roms with apps2sd(a2d).
If you really what to increase your internal memory, you need data2sd (also available in some roms here). Here ALL data were moved to your sd-card without exception and the system is leaded to believe that the free internal space is the free space on your sd-card. On this way you increase your internal memory directly, and you will never have any save problems any more.
The question about the radio was already answered.
That sounds really good! Thanks

[Q] ROM MANAGER not working for me

so, finally i decided to root and flash CM7
root with unrevoked went smooth and well (love when it says "this was a triumph")...
so i downloaded ROM MANAGER , made the Clockwork stuff and finally gave the instruction to partition the sd card (8gb, dunno the class... is 1 year old sandisk anyway)... the phone just reboot and get stuck with an image of a droid with a triangle and a "!" inside it...
i searched the fora but seems that no one got this problem...
please take in consideration that i am a total n00b, and i would like to do everything without too much effort from my side (please appreciate my honest being) ... i suppose that this partioning is necessary to run cm7 and app2sd...
how can i solve this problem?
reading other threads just gave me an enormous list of programs, linux, ubuntu etc etc and the basic result is me thinking: "wtf"
thank you for any useful answer...
Ciao!
Do full wipe/factory reset & dalvik cache wipe.
Try to repartition SD Card in recovery (choose 512mb+ ext partition and no swap)
Flash ROM from recovery, see what happens.
No need to use ROM Manager.
thx k3lcior
i wiped and ect
how to partition from recovery?
Depends on recovery, if you have some old one it might be not possible.
Just look at the recovery, should be somewhere in "Advanced" if i remember correctly.
ps.
Are you comfortable with linux?
There is very easy guide: http://www.youtube.com/watch?v=sVK-tJe8pXE&feature=related
Just instead of making 3 partitions make Fat32 and leave 1GB for ext2/3.
actually is Clockwork recovery v2.5.0.7 and is impossible to find any "partition sd" in the menus ... how can i get and install a different recovery (ie yours seems cool) ?
ps.
totally unfamiliar with linux...
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519
Download to flash through HBOOT. Put it onto your sdcard, rename it to PB99IMG.zip and boot into bootloader. (hold vol - and power)
If somehow it still didnt worked, you can try to Root again with Unrevoked, download this: http://forum.xda-developers.com/attachment.php?attachmentid=661319&stc=1&d=1311251519
Extract it, in Unrevoked choose "Custom Recovery" at the top under "file" and select the .img file you extracted, should be good. ;-)
ok i dl the file, put in sd and renamed it... and boot into bootloader, then pressing recovery its always giving me the old clockwork recovery...
is this related to rom manager always? should i uninstall it?
sorry for being sooo n00bish
When you put it into root of the sdcard (not any folders), renamed to PB99IMG.zip upon entering bootloader (vol- power) it should ask if you want to apply update, hit yes.
so finally i solved...
Updating from recovery was not working (same for bootloader), and i was starting to lose the hope...
so i managed to install CM7, planning to try a Panasonic program to partition drives in windows...
I have found in CM7 again ROM MANAGER, tried again to partition with no chance...
i re tried "Fix Permission" command into it and this time it worked (was not working in stock ROM)
then again partition with no chance...
in recovery mod i tried to install zip from SD (your recovery mod) , with no succes...
suddenly i have found in the menu "toggle permission" command, pressed it and then again "install zip from SD"
here come the mystery:
Phone started to partition the card, but without installing the new recovery... result: it seems that now card has a partition ...
i also installed the zip of gapps and now i can start to enjoy CM7 with all the google stuff etc...
im stille convinced that in the phone there are some gnomes that sometime are lazy and sometime not...
anyway i would like to thank you for your help and patience, hope that this experience might help someone other even if the best suggestion that i can give after all is : pray the gnomes...
Ciao!

[Q] Need help to install ICS

Hi Chiefs!
I am a newbie to rooting, planting, flashing etc etc however, to avoid frustrations from your end here are some of the first things that i have done.
I have read through the below links:
[cant post urls but its basically guides to rooting desire from xda forums]
I am using a Desire from Starhub in Singapore. I have recently upgraded to gingerbread 2.3.3 after which i realized that I should have not done that but anyway, now that it is done, I am now:
Revolutionary Now it is (Alpharev unlock)
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
Aug 10 2010, 17.72.18
I believe i should be able to install ICS now but when i download the ICS and rename as PB99IMG.ZIP and install it unzips and after parsing returns back to the hboot menu.
I must say confess that I may not have rooted correctly, because when i try and ls files in directories like cache, root or command I get permission errors.
Some help would be really appreciated, its just the sheer kick of being able to do it that drives me to post here.
You have to flash the zip-file from Recovery.
Check Tutorial(s) in Development-Section.
Sent from my HTC Desire using XDA
I tried that too sir .. but from recovery when I select the 'Apply update from SD card' it does not work, there is just a standard message 'rebooting with reason code' and something like 'unable to open /cache/command/...' and it reboots
danceunlimited said:
I tried that too sir .. but from recovery when I select the 'Apply update from SD card' it does not work, there is just a standard message 'rebooting with reason code' and something like 'unable to open /cache/command/...' and it reboots
Click to expand...
Click to collapse
nandroid backup first:
backup and restore -> backup
then full wipe:
wipe data/factory reset
then flash ROM:
install zip from sd card --> choose zip from sd card
(choose the correct ROM.zip)
'apply update from SD card' is something else.
First you have to partition your SD card. Go in the Recovery to 'advanced' and then 'partition sd card'. Choose 1GB EXT4 and 128MB SWAP... (all your files on the SD card will be deleted... maybe you have to secure them first). Then put the File with an SD card adapter on the sd (if you have one... if you don't have one and youre unable to boot complietly into the system, try without partitioning). When the file is on your sd boot into recovery...You have To choose 'install zip from sd-card' Or something like that... Then navigate To the folder where the ICS file is. Choose The file and here you are!!!
Sent from my HTC Desire using XDA
ph87 said:
First you have to partition your SD card. Go in the Recovery to 'advanced' and then 'partition sd card'. Choose 1GB EXT4 and 128MB SWAP... (all your files on the SD card will be deleted... maybe you have to secure them first). Then put the File with an SD card adapter on the sd (if you have one... if you don't have one and youre unable to boot complietly into the system, try without partitioning). When the file is on your sd boot into recovery...You have To choose 'install zip from sd-card' Or something like that... Then navigate To the folder where the ICS file is. Choose The file and here you are!!!
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
good point, though check each ROMs requirement if an ext partition is required. most will indicate a recommended size depends on how many apps you need, but most do not require a swap partition.
it's also better to use gparted to partition:
- backup your sd card first to PC,
- partition using gparted (search for a guide here somewhere)
- copy contents back to sd card, including ROM.zip
- nandroid backup, full wipe and install as above.
OK, looking at your help below i think i am sure that is something missing, and i definitely need help to figure that out ..
Firstly in recovery mode i dont get 'install zip from sd card' option.
I tried a full wipe and wipe data/factory reset, the zip stops at the same plc
BTW some other symptoms that gives me a feeling that i have not rooted completely or properly:
i installed SuperSU from chainfire and when i try to open it it says
There is no SU binary installed, and SuperSU cannotinstall it. This is the problem.
ROM Toolbox pro also says the same thing, 'failed to obtain root access'
ROM Manager also says that the superuser was not found at /system/bin/su or /system/xbin/su
i am using a windows xp laptop to do all the circus. If it is of any help, chiefs dont have to worry about backup and / or bricking my phone
danceunlimited said:
Firstly in recovery mode i dont get 'install zip from sd card' option.
I tried a full wipe and wipe data/factory reset, the zip stops at the same plc
Click to expand...
Click to collapse
are you sure you can't see 'install zip from sd card'??? it's the 3rd/4th option down in the main menu when you first boot into recovery. how are you even installing the zip when you say it stops at the same place?
danceunlimited said:
BTW some other symptoms that gives me a feeling that i have not rooted completely or properly:
i installed SuperSU from chainfire and when i try to open it it says
There is no SU binary installed, and SuperSU cannotinstall it. This is the problem.
ROM Toolbox pro also says the same thing, 'failed to obtain root access'
ROM Manager also says that the superuser was not found at /system/bin/su or /system/xbin/su
i am using a windows xp laptop to do all the circus. If it is of any help, chiefs dont have to worry about backup and / or bricking my phone
Click to expand...
Click to collapse
you probably didn't/haven't read all of the documentation, you need to flash superuser.zip. (flash the zip the same way as instructed above).
this however only roots your existing stock rom. you only need to do this if you want to backup apps and data (using something like Titanium Backup), and want to transfer them to a new rom.
whichever rom you end up using, DO NOT use ROM manager, it has been known to cause many problems with this phone, you don't need it.
check the rom thread if it requires an sd partition (most do), and set it up before installing the rom like i said above. also have a look at step 5 here
eddiehk6, you are right, I had never been to the this link for revolutionary ROM, i downloaded it from else where. After installing the correct this I understand what it means to have a 'different' recovery from the standard one that comes with the phone.
Most of the stuff went well after that including the installation of the latest ROM from sandvoid.
The problem is that after I restarted the phone after completing the installation, I see this "blue sparks flying from both sides of my screen to the center" splash, its been 10 minutes and how long should i let this go? Did i brick my phone? Argh! So close ...
ostyme electric
Yeeeeeeeeeeeeeeee Haaaaaaaaaaaaaaa! WOOT WOOT!
I just took out the battery and put it back and restarted to recovery mode, wiped dalvik cache and cache, (As usual super hasty and never RTFM) again!
Thank you all!
Time to spread the love of ICS!
Erm .. question ..
Where is my HTC Sync? I do see a process in there, but i see no option as to where i could "Sync calendar & Contacts", i upgraded my ROM from sandvoid 0.7
danceunlimited said:
Erm .. question ..
Where is my HTC Sync? I do see a process in there, but i see no option as to where i could "Sync calendar & Contacts", i upgraded my ROM from sandvoid 0.7
Click to expand...
Click to collapse
htc sync will only work with sense roms. i don't know what process you're seeing.
this is why we have gmail to sync contacts and calendar.
i know you're excited to have ICS, but remember it's still a beta rom, so there will be some issues as it's still being developed. you may not be able to post there yet, but you can still read the thread.
reading back i think you need to slow down a little. the key is reading, learning, understanding...before you do anything.
and google is your best friend , you can try it now to find out how to sync your contacts / calendar to gmail
Dang! NVM All hail Myphoneexplorer!! High time i donated something to them!

[TUT] What Is ClockworkMod And How To Use It [Complete Guide] [VeNuM]

Firstly all creadit goes to VeNuM. i haven't make this
Now, i found this helpful to NOOBS so i copied it.
Click to expand...
Click to collapse
What Is ClockworkMod Recovery And How To Use It On Android​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it. We do not discuss Touch recovery (and you shouldn’t use it on the ET4G) or Rogue recovery here. Those are different tuts…
All About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.
Introduction to ClockworkMod
ClockworkMod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices. It is the needed recovery for AOKP, AOSP, CM7 and 9. ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager.
Booting into ClockworkMod
On most Android devices including ones by Samsung, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device (volume up for our phones). This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery.
Tour
1.reboot system now
This one is self-explanatory.
2.apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses. This is what we are talking about:
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
1. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
2. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card.
3. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
4. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (we don’t), it’s best not to change this option.
5. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
1. Backup
Takes a Nandroid backup, as explained above.
2. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
3. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
1. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
2. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
3. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations.
1. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
2. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
3. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
5. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
6. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
7. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Using ClockworkMod for ROM, kernel, apps, theme or mod installation
While in the complete feature tour we have already shown you how to install a ROM, kernel, app, theme or any similar mod from a recovery-flashable zip file using the recovery options, those of you who jumped straight to this section expecting to get just this information quickly are at the right place!
This guide is primary focused on a full feature tour of ClockworkMod recovery but in our previously written guide on how to flash a ROM or app from a zip to an Android device file from recovery, we have already covered in detail how to use ClockworkMod for installing any ROM, kernel, app, theme or mod using a recovery-flashable zip file. While that guide is based on an older version of ClockworkMod recovery, everything in it still applies to the latest versions and should work flawlessly.
How To Install A ROM Or App From Zip File To Android Device From Recovery
Please note that the terms ‘installing’ and ‘flashing’ can be used interchangeably here and will mean the same thing.
Disclaimer: Although I have done my best to make the following procedure as safe as possible, you should still follow this guide at your own risk.
Rooting your device renders its warranty void.
ALWAYS take backups before rooting or flashing a custom ROM or app to your phone.
Flashing a defective ROM or app to your phone might brick it so choose the ROMs and software that you flash wisely and never install a ROM or application from an untrusted source.
AddictiveTips will not be liable if your device gets damaged or bricked during the process.
Official ROM updates from device manufacturers or carriers are released in conveniently packaged installation files that you can run on your computer while your Android device is connected to it, and they automatically take care of updating your phone’s system. Similarly, most applications are available directly in the Android Market for easy installation, or come packaged as convenient ‘.apk’ files that you can just run on your Android phone to install. The case is not the same with most custom ROMs and several custom applications, which come in .zip files rather than PC installers or .apk files.
The idea of installing a customized operating system to their smartphone can be quite intimidating for inexperienced users. Though once they get used to it, some of them end up trying out different ROMs for their devices several times a day. While I don’t exactly recommend that you flash every new ROM that is made available for your Android phone, we are here to help you get over the fear of flashing a ROM that enhances the capabilities of your device so that you can use it to its fullest potential.
Here is a quick look at what we will be covering in this guide. Feel free to skip to the real deal if you already meet the prerequisites.
• Before We Begin: Battery Check
• Before We Begin: Unlocking the Bootloader (Stock Android Devices Only)
• Before We Begin: Rooting
• Before We Proceed: Installing a Custom Recovery
• The Real Deal: Installing a Custom ROM to your Phone
• The Real Deal: Installing an App From a Zip File to your Phone
There are certain steps that you might not require, and we shall be mentioning them in each section.
Before We Begin: Battery Check
Before you proceed with any of the following steps, make sure your phone’s battery level is not too low. It is recommended to have it at 50% or more. Do NOT take this lightly. If your phone’s battery runs out while you are attempting to flash a custom ROM, there is a significant chance of your phone getting bricked and becoming unusable PERMANENTLY.
Before We Begin:Unlocking the Bootloader (Stock Android Devices Only)
Note: This step applies only to Android devices with stock version of Android installed. At the moment, Google Nexus One and Nexus S are the only two such devices available. You may skip this step if you are using any other Android device.
Users of stock Android devices such as the Google Nexus One or Nexus S also need to unlock its bootloader before they can proceed. Once you have done this, you may proceed to the next step.
Before We Begin: Rooting
Note: You may skip this step if your device is already rooted, or if you already know how to root it.
Before you can install a custom ROM to your device, your phone needs to be rooted. Rooting is basically administrator or root level access required to perform administrative tasks on your Android device. Once you are done with the rooting process, you may proceed to the next step.
Before We Proceed: Installing A Custom Recovery
Note: You may skip this step if you already have a custom recovery installed on your device.
Rooting grants you the necessary access level to execute administrative tasks on your Android device but it is the recovery that provides the tools necessary to actually perform those tasks. While every Android device ships with a recovery, the stock recovery is quite limited in what it lets you do, and you need a custom recovery image to perform advanced operations on your device. Once you have a custom recovery installed on your phone, you will be ready to proceed to the next step.
The Real Deal: Installing a Custom ROM to your Phone
Now that you have a custom recovery installed on your phone, you can perform all sorts of wonderful advanced operations on your device and this includes the ability to flash a ROM or application from a zip file. The procedure is pretty standard for most ROMs, though there are certain ROMs which require additional steps for their installation. Since those steps differ from ROM to ROM, pay attention to instructions and this includes only the standard instructions here.
• Manually
1. Download the ROM from the link given in the article featuring that ROM. It should be a zip file.
2. Connect your phone to your computer via USB and mount its storage card.
3. Copy the downloaded ROM to the root of the storage card.
4. Power your phone off and reboot it into recovery. This will involve using a combination of your device’s hardware keys. Once in recovery, you can navigate its menu using the volume up and volume down hardware keys or your phone’s trackball / optical track pad if it comes equipped with one.
5. Use the ‘backup and restore’ feature of recovery to backup your existing ROM installation, software and data. This step is known as performing a nandroid backup. ALWAYS perform a backup before flashing a custom ROM, UNLESS you can afford to lose everything that’s on your phone at the moment.
Note: ALWAYS choose to perform the following steps 6, 7 and 8 UNLESS the ROM you are attempting to flash is an updated version of the same ROM that you are currently using, and is compatible with the current installation’s data. It is usually mentioned with the update whether you can install it over a previous version without wiping its data or not.
6. Get back to the main recovery menu and use the option ‘wipe data/factory reset’. You will be prompted to confirm this action. Select “Yes – Delete all user data”.
7. From the main recovery menu, select ‘wipe cache partition’. You will be prompted to confirm this action. Select ‘Yes – Wipe Cache’.
8. From the main recovery menu, enter the ‘advanced’ menu. From this menu, select ‘Wipe Dalvik Cache’. You will be prompted to confirm this action. Select ‘Yes – Format/System’.
9. From the main recovery menu, enter the ‘Mounts and Storage’ menu. From this menu, select ‘Format/System’. You will be prompted to confirm this action. Select ‘Yes – Wipe Dalvik Cache’.
10. Go back to the main recovery menu by pressing the back button and select the ‘Install zip from SD card’ option.
11. Select ‘choose zip from sdcard’ to get a list of the files and folders on your SD card. Scroll to the ROM’s file that you copied there in step 3, and select it. You will be prompted to confirm this action. Select ‘Yes – Install file_name.zip’ where file_name.zip is the name of the zip file that you are trying to install.
12. Wait patiently while the ROM is flashed to your phone via recovery.
13. Once the installation is complete, head back to the main recovery menu if you aren’t there, and select ‘reboot system now’. Your phone will now boot into the newly installed ROM.
The Real Deal: Installing an App From a Zip File to your Phone
While most apps for Android devices are available at the app store for direct download and installation or as .apk files for direct installation, there are certain apps which are only available as zip files installable from recovery. Their installation procedure is the same as installing a custom ROM that we just featured above. However, there are a few minute differences.
• When installing an app from a zip file, you do NOT need to perform the ‘wipe data/factory reset’ or ‘wipe/system’ step so NEVER do that unless you know what you are doing, have a complete backup and want to start using your ROM as a fresh installation with the new app added.
• You might or might not need to wipe the cache and the dalvik cache for installing apps from zip file. This varies from app to app and the developers of such apps as well as many reviewers including us mention when featuring an app whether it requires a cache and dalvik cache wipe or not. However, it never hurts to wipe these caches anyway, and it does not effect the data on your device or its storage card.
There you go, this concludes the guide on how to flash a ROM or app from a zip file to your Android device using a custom recovery. To try out the skills that you just learned, search our site for custom ROMs for your phone and start flashing, always remembering to take backups first!
LOL x2
very nice guide........ also add CWM.zip madteam . skin with original thread link............
Sent from my GT-S6102 using Tapatalk 2
cwm link attached
one of da best threads in this forum,thx.
deathviper said:
What Is ClockworkMod Recovery And How To Use It On Android​
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it. We do not discuss Touch recovery (and you shouldn’t use it on the ET4G) or Rogue recovery here. Those are different tuts…
All About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.
Introduction to ClockworkMod
ClockworkMod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices. It is the needed recovery for AOKP, AOSP, CM7 and 9. ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager.
Booting into ClockworkMod
On most Android devices including ones by Samsung, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device (volume up for our phones). This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery.
Tour
1.reboot system now
This one is self-explanatory.
2.apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses. This is what we are talking about:
3. wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
4. wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
1. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
2. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card.
3. toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
4. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (we don’t), it’s best not to change this option.
5. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6. backup and restore Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
1. Backup
Takes a Nandroid backup, as explained above.
2. Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
3. Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
7. mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
1. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
2. format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
3. mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations.
1. Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
2. Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
3. Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4. Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
5. Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
6. Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
7. Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Using ClockworkMod for ROM, kernel, apps, theme or mod installation
While in the complete feature tour we have already shown you how to install a ROM, kernel, app, theme or any similar mod from a recovery-flashable zip file using the recovery options, those of you who jumped straight to this section expecting to get just this information quickly are at the right place!
This guide is primary focused on a full feature tour of ClockworkMod recovery but in our previously written guide on how to flash a ROM or app from a zip to an Android device file from recovery, we have already covered in detail how to use ClockworkMod for installing any ROM, kernel, app, theme or mod using a recovery-flashable zip file. While that guide is based on an older version of ClockworkMod recovery, everything in it still applies to the latest versions and should work flawlessly.
How To Install A ROM Or App From Zip File To Android Device From Recovery
Please note that the terms ‘installing’ and ‘flashing’ can be used interchangeably here and will mean the same thing.
Disclaimer: Although I have done my best to make the following procedure as safe as possible, you should still follow this guide at your own risk.
Rooting your device renders its warranty void.
ALWAYS take backups before rooting or flashing a custom ROM or app to your phone.
Flashing a defective ROM or app to your phone might brick it so choose the ROMs and software that you flash wisely and never install a ROM or application from an untrusted source.
AddictiveTips will not be liable if your device gets damaged or bricked during the process.
Official ROM updates from device manufacturers or carriers are released in conveniently packaged installation files that you can run on your computer while your Android device is connected to it, and they automatically take care of updating your phone’s system. Similarly, most applications are available directly in the Android Market for easy installation, or come packaged as convenient ‘.apk’ files that you can just run on your Android phone to install. The case is not the same with most custom ROMs and several custom applications, which come in .zip files rather than PC installers or .apk files.
The idea of installing a customized operating system to their smartphone can be quite intimidating for inexperienced users. Though once they get used to it, some of them end up trying out different ROMs for their devices several times a day. While I don’t exactly recommend that you flash every new ROM that is made available for your Android phone, we are here to help you get over the fear of flashing a ROM that enhances the capabilities of your device so that you can use it to its fullest potential.
Here is a quick look at what we will be covering in this guide. Feel free to skip to the real deal if you already meet the prerequisites.
• Before We Begin: Battery Check
• Before We Begin: Unlocking the Bootloader (Stock Android Devices Only)
• Before We Begin: Rooting
• Before We Proceed: Installing a Custom Recovery
• The Real Deal: Installing a Custom ROM to your Phone
• The Real Deal: Installing an App From a Zip File to your Phone
There are certain steps that you might not require, and we shall be mentioning them in each section.
Before We Begin: Battery Check
Before you proceed with any of the following steps, make sure your phone’s battery level is not too low. It is recommended to have it at 50% or more. Do NOT take this lightly. If your phone’s battery runs out while you are attempting to flash a custom ROM, there is a significant chance of your phone getting bricked and becoming unusable PERMANENTLY.
Before We Begin:Unlocking the Bootloader (Stock Android Devices Only)
Note: This step applies only to Android devices with stock version of Android installed. At the moment, Google Nexus One and Nexus S are the only two such devices available. You may skip this step if you are using any other Android device.
Users of stock Android devices such as the Google Nexus One or Nexus S also need to unlock its bootloader before they can proceed. Once you have done this, you may proceed to the next step.
Before We Begin: Rooting
Note: You may skip this step if your device is already rooted, or if you already know how to root it.
Before you can install a custom ROM to your device, your phone needs to be rooted. Rooting is basically administrator or root level access required to perform administrative tasks on your Android device. Once you are done with the rooting process, you may proceed to the next step.
Before We Proceed: Installing A Custom Recovery
Note: You may skip this step if you already have a custom recovery installed on your device.
Rooting grants you the necessary access level to execute administrative tasks on your Android device but it is the recovery that provides the tools necessary to actually perform those tasks. While every Android device ships with a recovery, the stock recovery is quite limited in what it lets you do, and you need a custom recovery image to perform advanced operations on your device. Once you have a custom recovery installed on your phone, you will be ready to proceed to the next step.
The Real Deal: Installing a Custom ROM to your Phone
Now that you have a custom recovery installed on your phone, you can perform all sorts of wonderful advanced operations on your device and this includes the ability to flash a ROM or application from a zip file. The procedure is pretty standard for most ROMs, though there are certain ROMs which require additional steps for their installation. Since those steps differ from ROM to ROM, pay attention to instructions and this includes only the standard instructions here.
• Manually
1. Download the ROM from the link given in the article featuring that ROM. It should be a zip file.
2. Connect your phone to your computer via USB and mount its storage card.
3. Copy the downloaded ROM to the root of the storage card.
4. Power your phone off and reboot it into recovery. This will involve using a combination of your device’s hardware keys. Once in recovery, you can navigate its menu using the volume up and volume down hardware keys or your phone’s trackball / optical track pad if it comes equipped with one.
5. Use the ‘backup and restore’ feature of recovery to backup your existing ROM installation, software and data. This step is known as performing a nandroid backup. ALWAYS perform a backup before flashing a custom ROM, UNLESS you can afford to lose everything that’s on your phone at the moment.
Note: ALWAYS choose to perform the following steps 6, 7 and 8 UNLESS the ROM you are attempting to flash is an updated version of the same ROM that you are currently using, and is compatible with the current installation’s data. It is usually mentioned with the update whether you can install it over a previous version without wiping its data or not.
6. Get back to the main recovery menu and use the option ‘wipe data/factory reset’. You will be prompted to confirm this action. Select “Yes – Delete all user data”.
7. From the main recovery menu, select ‘wipe cache partition’. You will be prompted to confirm this action. Select ‘Yes – Wipe Cache’.
8. From the main recovery menu, enter the ‘advanced’ menu. From this menu, select ‘Wipe Dalvik Cache’. You will be prompted to confirm this action. Select ‘Yes – Format/System’.
9. From the main recovery menu, enter the ‘Mounts and Storage’ menu. From this menu, select ‘Format/System’. You will be prompted to confirm this action. Select ‘Yes – Wipe Dalvik Cache’.
10. Go back to the main recovery menu by pressing the back button and select the ‘Install zip from SD card’ option.
11. Select ‘choose zip from sdcard’ to get a list of the files and folders on your SD card. Scroll to the ROM’s file that you copied there in step 3, and select it. You will be prompted to confirm this action. Select ‘Yes – Install file_name.zip’ where file_name.zip is the name of the zip file that you are trying to install.
12. Wait patiently while the ROM is flashed to your phone via recovery.
13. Once the installation is complete, head back to the main recovery menu if you aren’t there, and select ‘reboot system now’. Your phone will now boot into the newly installed ROM.
The Real Deal: Installing an App From a Zip File to your Phone
While most apps for Android devices are available at the app store for direct download and installation or as .apk files for direct installation, there are certain apps which are only available as zip files installable from recovery. Their installation procedure is the same as installing a custom ROM that we just featured above. However, there are a few minute differences.
• When installing an app from a zip file, you do NOT need to perform the ‘wipe data/factory reset’ or ‘wipe/system’ step so NEVER do that unless you know what you are doing, have a complete backup and want to start using your ROM as a fresh installation with the new app added.
• You might or might not need to wipe the cache and the dalvik cache for installing apps from zip file. This varies from app to app and the developers of such apps as well as many reviewers including us mention when featuring an app whether it requires a cache and dalvik cache wipe or not. However, it never hurts to wipe these caches anyway, and it does not effect the data on your device or its storage card.
There you go, this concludes the guide on how to flash a ROM or app from a zip file to your Android device using a custom recovery. To try out the skills that you just learned, search our site for custom ROMs for your phone and start flashing, always remembering to take backups first!
Click to expand...
Click to collapse
one of da best threads in this forum,thx
Where can I report bugs from CM 13 ?

[CWM/TWRP UTIL] ROMBlitz Script (GS4 and GS2)

ROMBlitz is a passive, yet extreme deep-cleaner, returning your ROM back to its initial-boot state.
ROMBlitz is about as close as you can get to a Factory Reset without having to set everything back up again!!!
Current Version: 1.05 (11/07/2016)
For a full changelog, see Post #3 below.
The script has been specifically developed and tested on my GT-I9505. It will also run on the following list of devices, but is of course untested by myself.
Supported Devices
GT-I9505*
SGH-M919
SGH-I337
jflte
jfltexx
GT-I9100*
I9100*
Installation Instructions
1. Download ROMBlitz.zip from the link below, and copy onto your device
2. To be extra safe, ensure the zip file's md5 checksum is correct
3. Reboot into Recovery
4. Install zip from SD card/External SD Card>Run ROMBlitz.zip
5. Reboot (and be patient!!!)
Downoad Here
Download Here
I have made every effort to test my script as thoroughly as I possibly can, but like anything else you flash onto your device, you do so at your own risk. I cannot be held responsible for any files/information lost from using this script that you did not foresee. Remember this will wipe your Internal SD card, so if you have any important files/photos contained within it, then perform adequate backups beforehand.
NOTE
I have seen a post on another forum regarding someone who downloaded another one of my scripts (Hawkernelwipe.zip), and the file that was received was Hawkernelwipe.zip.exe. I will only ever post up these scripts as recovery-flashable .ZIP files hosted on Dev-Host. If your download is anything other than this, then your PC is probably infected, and running such a file will probably infect your PC even further. Do not download from anywhere other than Dev-Host.
If you are ever unsure, check the md5 checksum before doing anything. This is one of the reasons for having md5 checksums in the first place.
All the Boring In-Depth Details
ROMBlitz clears any unnecessary files it encounters on your device, wiping the internal SD card, keeping any files/folders that you have defined in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt
Known temporary files are removed, along with ALL cache areas (which unlike a generic cache wipe, includes ALL individual application cache.), media thumbnails+database areas.
ROMBlitz will do all the work necessary for you to get your ROM as clean and clutter-free as possible!
ROMBlitz can be used to attempt to fix any minor problems your current ROM may have and possibly speed things up a little due to the space it frees up. Its worth giving this a try first before biting the bullet and performing a Factory Reset. You've got nothing to lose. However, ROMBlitz is not a cure for all evils, so don't expect miracles. Just remember its primary function, first and foremost, is to free up space on your device by removing unnecessary files and removing cache so that it gets regenerated.
Background Information - Remember Your First Boot?
When you booted your ROM up for the very first time, you would have noticed that it spent a very long time on the boot animation screen. During this time, your new ROM was generating individual application cache, and building all the necessary Android folders on Internal+External SD Cards for the applications in the new ROM to use.
After the initial boot animation screen completed, you would have seen the Android is upgrading, Optimising app xxx of xxx message. This is where Android builds up its all its Dalvik-cache area for the apps.
Once the ROM had settled down after this first boot (after the initial media scanner operations completed) you probably would have noticed that your new ROM was lovely and crisp and snappy.
ROMBlitz wipes all these areas, giving your ROM this fresh start again
The next power-up of your device after running ROMBlitz you will notice your device will take a long time to boot, as it has to perform all of the things that it did on your very first boot again. The boot animation screen will be running for quite some time, followed by the Android is upgrading, Optimising app xxx of xxx message.
Don't forget that known media areas will have also been wiped, so the Media Scanner will need to do far more work than usual on the next boot after a ROMBlitz, so expect the device to be quite laggy for a period of time afterwards.
You may also notice many applications are slower opening the first time you use them after a ROMBlitz. This is just the application re-initializing the any areas that may have been wiped.
When Should I Flash ROMBlitz?
If you frequently jump from ROM to ROM using Nandroid backup/restores, or are constantly flashing different ROMs, then you can very quickly gather tons of clutter on both your Internal and external SD cards. Every ROM you use creates its own folders on both SD Cards (TW ROMS especially!) thereby leaving large amounts of unnecessary files/folders on the cards between ROM-jumps. (unless of course you format the Internal SD Card, and remove /Android folder from the External SD manually each time before changing your ROM)
ROMBlitz will remove all this accumulated clutter on your Internal+External SD cards for you and deep-clean all the built up cache areas, giving your current/restored/new ROM the cleanest base possible to work from.
1. ROMBlitz before by a Nandroid Restore
Your SD Cards will be cleaned up, so expect a longer wait on the subsequent boot animation screen. All cache/media areas will be as of the time of the Nandroid backup, so you shouldn't expect to see the Android is upgrading, Optimising app xxx of xxx message.
2. ROMBlitz after a Nandroid Restore
All the cache and media areas previously mentioned will be cleared on your just-restored ROM, along with the areas described on both SD Cards. On the next boot you will see boot animation screen for a long time whilst the SD Card and application cache areas get rebuilt, followed by the Android is upgrading, Optimising app xxx of xxx message, as the Dalvik areas get regenerated.
3. ROMBlitz before you flash a new ROM
Regardless of if you are flashing a custom ROM through CWM or stock firmware with Odin, it's always a good idea to do a ROMBlitz beforehand. Doing so will clear the SD Card areas for you giving your new ROM the freshest, cleanest possible start.
4. ROMBlitz at any time on your current ROM
Flash ROMBlitz at any time if you just want to free up space and deep-clean your cache. Just expect a long boot next time.
5. ROMBlitz when you are experiencing problems
If you are experiencing problems with some applications behaving erratically or FC'ing, or perhaps you have a bootloop and you are contemplating a Factory Reset, then consider flashing ROMBlitz first. It may help you out, you never know. It's well worth a try before going the whole-hog, and jumping into a Factory Reset. You won't have anything to lose!
ROMBlitz Steps
Removes [int-sd]/Android and [ext-sd]/Android folders
Remove ALL files+folders from Internal SD card, except for any defined in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt
Delete ALL known temporary files found on the entire device
Remove ALL known media cache, databases, thumbnails etc. found on the entire device, and create .nomedia file in known areas that do not require media files, in order to speed up the Media Scanner process
Wipe dalvik cache from /data and /cache areas
Wipe all known cache areas from /cache, /data/system/cache and all individual application cache
Defining What You Want To Keep On Internal-SD
On the very first run of ROMBlitz, /sdcard/tmp/Hawker/ROMBlitz_Keep.txt will get automatically generated and the script then exits immediately, allowing you to reboot and edit this file to you own requirements.
This file's initial contents of areas to keep are:
snap_settings.bin
clockworkmod
data
DCIM
GravityBox
HawkerCore
IMEIBackup
Llama
LightManager
TitaniumBackup
TWRP
TopNTP
ViPER4Android
You MUST manually edit this file so that the files YOU want to keep on your Internal SD Card do not get wiped!
If you want to, you can manually create this file before the first run of ROMBlitz. Doing so would allow the script to run as normal on its very first run without the need to exit to edit. If you want to do this, then use a text editor on your device, or if done on your PC, use Notepad++ and ensure EOL is set to UNIX (LF). Create a folder called /sdcard/tmp/Hawker and copy this file into there.
Notes
If you always want ROMBlitz to wipe the ENTIRE Internal SD, you can do so by manually creating /sdcard/tmp/Hawker/ROMBlitz_KeepNone
[int-sd]/0 and [int-sd]/tmp folders will never be deleted by the script, even if the above file has been created
[int-sd]/Android and [ext-sd]/Android will always be deleted, even if included in the list of files to keep
Test Mode
You can call ROMBlitz.sh (which is in the tmp folder of the zip file) in Test Mode. This goes through all the motions as per a standard Recovery run, but it does not remove any files/folders in any way, and merely shows the commands that would have been executed. If you want to do this, then simply extract ROMBlitz.sh from the zip onto your device, and run it from there through a script manager type of application, through a terminal emulator, or adb shell.
Log File
A lot goes on during a ROMBlitz run, so everything that happens gets logged in /sdcard/tmp/Hawker/ROMBlitz.log for you subsequently examine if you need to.
Work In Progress
V1.05
1. Delete more temporary areas from /data partition
Identify more areas for wiping
Changelog
V1.04 (22/11/2015)
1. Better handling of file names containing spaces, including keep files
2. Hidden (.*) files are now also removed from Internal SD
3. Improved device detection
V1.03 (16/06/2015)
1. Report any files/folders in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt that do not exist on the Int. SD Card.
2. Script will now attempt to execute even if no build.prop file present (eg. after a /system wipe)
3. Fixed deletion of file names containing any space characters.
4. Display tweaks
V1.02 (14/05/2015)
1. Convert Kb deletion reporting to Mb/Gb if required.
2. Only show files that will be kept on Int. SD defined in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt that actually exist on the Int. SD Card.
3. /sdcard/tmp/Hawker/ROMBlitz_KeepNone now implemented.
V1.01 (14/05/2015)
1. Improvements to the way /sdcard/tmp/Hawker/ROMBlitz_Keep.txt is handled. Can also put a "#" at the start of the line to ignore the entry.
2. Display tweaks
V1.00 (13/05/2015)
1. Initial release
V1.01 (14/05/2015)
1. Improvements to the way /sdcard/tmp/Hawker/ROMBlitz_Keep.txt is handled. Can now also put a "#" at the start of any line to ignore the entry.
2. Display tweaks
Good Work Sir
Sweet as always. I have been using your GS2 & GS4 RomNuke since a while back. Good job as always. Thank you Sir.
I confirm this works like a charm on my sgh-m919!
This is a piece of work that deserves much appreciation. My T-mobile s4 becomes way faster after flashing this! Thanks !
V1.02
1. Convert Kb deletion reporting to Mb/Gb if required.
2. Only show files that will be kept on Int. SD defined in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt that actually exist on the Int. SD Card.
3. /sdcard/tmp/Hawker/ROMBlitz_KeepNone now implemented.
This seems a good cleaner... but im a bit curious...
It will clean my external SD Card or the internal?
I have movies in my SD card.. i want to keep them..
When will i flash this?
Is it before flashing a new ROM?
Thanks...
radz.min said:
This seems a good cleaner... but im a bit curious...
It will clean my external SD Card or the internal?
I have movies in my SD card.. i want to keep them..
When will i flash this?
Is it before flashing a new ROM?
Thanks...
Click to expand...
Click to collapse
It cleans both, but it only wipes INTERNAL on-mass as stated in OP.
The only things that will be removed from external is the /Android folder and any known temporary/cache-type files.
When to flash is up to you. Its all in the OP mate.
Will this work on AOSP?
I want to know if this works on AOSP roms as well.
Yousvel said:
I want to know if this works on AOSP roms as well.
Click to expand...
Click to collapse
I've not tried it personally, but there's no reason at all why it shouldn't
disconnect MTP in TWRP or it will not work
great work, regards
V1.03
1. Report any files/folders in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt that do not exist on the Int. SD Card.
2. Script will now attempt to execute even if no build.prop file present (eg. after a /system wipe)
3. Fixed deletion of file names containing any space characters.
4. Display tweaks
Hi, after read and read and read, I have a doubt yet... Thus script wipe only internal SD and delete only /Android folder in external SD? Or there is a risk to loose all my data in external SD? Thanks
biazoto said:
Hi, after read and read and read, I have a doubt yet... Thus script wipe only internal SD and delete only /Android folder in external SD? Or there is a risk to loose all my data in external SD? Thanks
Click to expand...
Click to collapse
I'll quote OP for you
ROMBlitz Steps
Removes [int-sd]/Android and [ext-sd]/Android folders
Remove ALL files+folders from Internal SD card, except for any defined in /sdcard/tmp/Hawker/ROMBlitz_Keep.txt
Delete ALL known temporary files found on the entire device
Remove ALL known media cache, databases, thumbnails etc. found on the entire device, and create .nomedia file in known areas that do not require media files, in order to speed up the Media Scanner process
Wipe dalvik cache from /data and /cache areas
Wipe all known cache areas from /cache, /data/system/cache and all individual application cache
V1.04 (21/11/2015)
1. Better handling of file names containing spaces, including keep files
2. Hidden (.*) files are now also removed from Internal SD
3. Improved device detection
Updated non-working download links (I think it may have been because I am no longer an XDA Recognized Contributor)
Also, updated to 1.05

Categories

Resources