Related
Hi,
I search a way to run some terminal command at startup so that i can apply persistant tweak to the internal memory manager. ( how to here)
Is there an apps or something to do to achieve this?
Solved :
theboostman said:
I finaly found how to do the job. We can run script at boot even with Su permissions!
Using tasker to launch script at device boot.(I wanted to be able to set it directly in android like in windows anyway)
how to launch the script at boot :
Prerequisite (available in market):
- Tasker by Crafty Apps
- Locale Execute Plugin by Michael Mauch (no need for the main locale apps)
Create a "loadable" script:
Use script file in UNIX format with no extension in the name and use a key like "on" in your script to be able to start the script on tasker, if not it will not work.
I use NotePad ++ to create my script starting from a . txt and select Edit , EOL Conversion, Unix Format. Then save as "filename.txt" and rename to delete ".txt".
Copy the script on your sdcard (see samples in .zip attached)
In tasker, Create a new profile and select |System| , |Device Boot|.
Then select |New task| and |Add an action| , |Plugin| , |Execute|.
Then |Edit| and tip @! sh /sdcard/filename key
For example for file name "bofstask" that contain a script tweaking internal memory manager settings and vdd level of kamma's 1.4 kernel.
The script run when the key "on" is used, so tip @! sh /sdcard/bofstask on
Done.
Mod: Do you think this thread has to be moved on a more "developement" thread since it allow to run basic developpement script?
Click to expand...
Click to collapse
I've search a bit and found how to create the script than can be run to apply the settings I want but i still don't find where to put this file on the android system so that it will run at each boot...
It was very easy to do this in windows, I'm sure there is a way to do it in android!
please skilled guys point me to the right thread...
Run script at boot with SU permissions!
I finaly found how to do the job. We can run script at boot even with Su permissions!
Using tasker to launch script at device boot.(I wanted to be able to set it directly in android like in windows anyway)
how to launch the script at boot :
Prerequisite (available in market):
- Tasker by Crafty Apps
- Locale Execute Plugin by Michael Mauch (no need for the main locale apps)
Create a "loadable" script:
Use script file in UNIX format with no extension in the name and use a key like "on" in your script to be able to start the script on tasker, if not it will not work.
I use NotePad ++ to create my script starting from a . txt and select Edit , EOL Conversion, Unix Format. Then save as "filename.txt" and rename to delete ".txt".
Copy the script on your sdcard (see samples in .zip attached)
In tasker, Create a new profile and select |System| , |Device Boot|.
Then select |New task| and |Add an action| , |Plugin| , |Execute|.
Then |Edit| and tip @! sh /sdcard/filename key
For example for file name "bofstask" that contain a script tweaking internal memory manager settings and vdd level of kamma's 1.4 kernel.
The script run when the key "on" is used, so tip @! sh /sdcard/bofstask on
Done.
Mod: Do you think this thread has to be moved on a more "developement" thread since it allow to run basic developpement script?
Edit: Maybe should I just create a new thread and keep this one as it is...??
Ended up using SManager from the play store - working great!
most roms for dhd i have used also support init.d scripts. all you have to do is to put your script with no file extension in /system/etc/init.d folder and that is it
I. Before You Begin
1. We are assuming you have already setup the Android kitchen. If not, use our How To Setup The Kitchen procedure and then come back to this one when done.(first see the post creating an custom rom for android a)
2. We are also assuming you have already done our How To Root and How To Load a Custom ROM for your phone and have a custom recovery image.
2. This ONLY works for HTC Android devices at the moment, later versions might support others (check here for an update when it does).
3. Open the Kitchen in your Ubuntu Virtual Machine we created in the Kitchen Setup procedure by typing ./menu in the Terminal window in Ubuntu. Leave it open.
4. All of this is done INSIDE THE UBUNTU VIRTUAL MACHINE (that includes when I say “save to your computer” anywhere in here, means save to you Ubuntu Virtual Machine)!
II. Find a ROM to Dissect
There are two kinds of ROMs you can dissect to create your own custom ROM; Stock ROMs and Custom/Cooked ROMs. DsiXDA, creator of the ROM kitchen we are using, has put together a list of places to get stock ROMs for different devices and a quick how to load them into the kitchen:
From a Cooked ROM (Easiest Method):
1. Copy the update.zip (or equivalent ZIP file) to the original_update folder in the kitchen
2. Type the number for the option “Setup Working Folder from ROM” and hit enter in the Kitchen to create your working folder. (So if its number is 1, type 1 then hit enter).
From a Shipped ROM:
1. Find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device’s sub-forum).
The links below may help:
HTC Hero
Google Nexus One (android.modaco.com/topic/300414-21oct-stock-roms-erd79- frg83-images-zip-online-kitchen-optional-root-insecure/)
" copy paste on browser than download it "
HTC Magic
HTC Tattoo
2a. If the shipped ROM is in a .ZIP format, then simply extract the system.img and boot.img.
2b. If the shipped ROM is in .EXE format, then do the following:
A. In Windows, run the shipped ROM’s .EXE file till it gets to the first dialog. Stop there but don’t close the window yet.
B. Go to Start->Run and type: %TEMP%
C. When the folder opens, search for Rom.zip. Then, open it with an unzip tool. If you get errors trying to open the ZIP file with WinZip or the default Windows unzip program, then use 7Zip (download from "w_w_w_.7-zip.org/ "_" from link) to extract it.
D. Extract only two files from Rom.zip: system.img and boot.img
3. Copy the two .IMG files to your kitchen’s img_files folder in your Ubuntu Virtual Machine.
4. In the Terminal window that you opened in Section I, type 1 and hit enter to create a working folder from the two .img files.
Now, that you have either the update.zip in the original_update folder of the kitchen OR the system.img and boot.img of a shipped ROM in the img_files folder of the kitchen, you are ready to play with the ROM to make it your own.
III. Tweaking the Imported ROM Using the Automated Options in the Kitchen
So this is a basic kitchen, but you can do things like, add Root support, add/remove apps from the ROM, enable saving apps to the sd card, enabling Wifi tethering, do some automatic optimizations, and a few other things automatically just by selecting the option and hitting enter. It even allows you to put in your own scripts for the ROM to run (but that’s for more advanced users who know how to create scripts of course).
1. After importing a ROM using section II, select the options you want to do to the ROM (by typing the number of the option you want into the terminal/kitchen window and hitting enter. They are all pretty self explanatory.)
2. Continue this until you have all the automated options you want in the new ROM.
IV. Adding/Removing Applications from the ROM
1. In your Ubuntu Virtual Machine, goto Places at the top. Then click on Home Folder, then the WORKING folder that was created in section II when you dissected the original ROM or img files. Then goto system > app. (Also check Data > App as .apks can be put in there as well).
2. In the app folder you will see all the .apk files for all the applications you have currently in the ROM. Simply delete the ones you do not want to remove them from the ROM.
3. To add applications, simply copy any .apk file for the applications you want to add into the app folder.
V. Repackage the ROM so it can be Flashed onto a Phone
1. Once you have done whatever changes you want, you just need to type 99 and hit enter in the kitchen/terminal for the kitchen to take the working folder you have been messing with and compile it into a flashable update.zip ROM.
2. Once it is done compiling the ROM, we can transfer it to our phone.
VIa. Setup Ubuntu to See Your Phone via USB
1. In the Virtual Box windows with Ubuntu in it, click on Devices at the top then click Install Guest Additions. (It should autostart, if it doesn’t, click on the CD that appeared on the desktop in Ubuntu and then click on Autostart.sh. It will ask you for your password you created when setting up Ubuntu, put that in and let it install).
2. Once the Guest Additions are installed, close the Virtual Box Ubuntu Window (choose to Power Down the Machine).
3. Now, open Virtual Box itself (not Ubuntu) and highlight the Ubuntu machine, then click on Settings at the top.
4. Click on USB and make sure Enable USB Controller and Enable USB 2.0 are both enabled.
5. Now plug in your Android phone (do NOT mount the SD card, just plug it in).
6. Now in the USB menu of Virtual Box, click the + symbol on the right and then select your Android Device (name may be different).
7. Once that is installed, unplug your phone.
8. Now, Start your Ubuntu Virtual Box.
9. Once Ubuntu boots up, plug in your Android phone (do not mount the memory card yet) and look for the USB symbol at the bottom (fourth icon from the left) and hover over it and wait for it to say USB Device detected and display your phone. Once that happens, mount the sd card by pulling down the notification bar on your phone and clicking mount.
10. Ubuntu should pop up your SD card on the desktop (if any prompts come up just select do nothing and click ok). We can now transfer files to the memory card of our phone.
VIb. Use RapidShare to Transfer the File from Ubuntu to Windows (if Section VIa was giving you trouble)
1. If you can’t get the USB to work in Ubuntu, then simply open a Firefox browser window, goto Rapidshare.com and upload the ROM to there.
2.Once it is done uploading, ON YOUR WINDOWS COMPUTER NOT UBUNTU, put in the link it gave you when you finished uploading it, to download it to your Windows computer so we can transfer it to your phone.
VII. Flash the ROM
5. Copy the .zip file to the root of your SD card (NOT in any folders, just on the SD card itself).
6. Unplug the phone and turn it off.
7. Turn it back on by holding down home and power (do not let go until the recovery screen comes up) to get to recovery mode (you must have a custom recovery screen to do this, if you don’t find out How To Root and Load a ROM procedure for your phone and do those first).
8. Now select Nandroid Backup to create a backup before we flash the new ROM.
9. Once the backup is done, select Wipe Data / Factory Reset in recovery mode.
10. Select flash zip from sd card and select the ROM you just put on the sd card.
11. Once it is done flashing, click reboot. Enjoy!
Enjoy! Will update this as we add more things for you to tweak FeWant to Flash a New Splash Screen on Your 320×480 Resolution Android Device? Here’s how.
el free to suggest some in the meantime.
Thanks to DsiXDA for his awesome kitchen!
ohh... thanks
Very nice information.................
zero+ said:
I. Before You Begin
1. We are assuming you have already setup the Android kitchen. If not, use our How To Setup The Kitchen procedure and then come back to this one when done.(first see the post creating an custom rom for android a)
2. We are also assuming you have already done our How To Root and How To Load a Custom ROM for your phone and have a custom recovery image.
2. This ONLY works for HTC Android devices at the moment, later versions might support others (check here for an update when it does).
3. Open the Kitchen in your Ubuntu Virtual Machine we created in the Kitchen Setup procedure by typing ./menu in the Terminal window in Ubuntu. Leave it open.
4. All of this is done INSIDE THE UBUNTU VIRTUAL MACHINE (that includes when I say “save to your computer” anywhere in here, means save to you Ubuntu Virtual Machine)!
II. Find a ROM to Dissect
There are two kinds of ROMs you can dissect to create your own custom ROM; Stock ROMs and Custom/Cooked ROMs. DsiXDA, creator of the ROM kitchen we are using, has put together a list of places to get stock ROMs for different devices and a quick how to load them into the kitchen:
From a Cooked ROM (Easiest Method):
1. Copy the update.zip (or equivalent ZIP file) to the original_update folder in the kitchen
2. Type the number for the option “Setup Working Folder from ROM” and hit enter in the Kitchen to create your working folder. (So if its number is 1, type 1 then hit enter).
From a Shipped ROM:
1. Find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device’s sub-forum).
The links below may help:
HTC Hero
Google Nexus One (android.modaco.com/topic/300414-21oct-stock-roms-erd79- frg83-images-zip-online-kitchen-optional-root-insecure/)
" copy paste on browser than download it "
HTC Magic
HTC Tattoo
2a. If the shipped ROM is in a .ZIP format, then simply extract the system.img and boot.img.
2b. If the shipped ROM is in .EXE format, then do the following:
A. In Windows, run the shipped ROM’s .EXE file till it gets to the first dialog. Stop there but don’t close the window yet.
B. Go to Start->Run and type: %TEMP%
C. When the folder opens, search for Rom.zip. Then, open it with an unzip tool. If you get errors trying to open the ZIP file with WinZip or the default Windows unzip program, then use 7Zip (download from "w_w_w_.7-zip.org/ "_" from link) to extract it.
D. Extract only two files from Rom.zip: system.img and boot.img
3. Copy the two .IMG files to your kitchen’s img_files folder in your Ubuntu Virtual Machine.
4. In the Terminal window that you opened in Section I, type 1 and hit enter to create a working folder from the two .img files.
Now, that you have either the update.zip in the original_update folder of the kitchen OR the system.img and boot.img of a shipped ROM in the img_files folder of the kitchen, you are ready to play with the ROM to make it your own.
III. Tweaking the Imported ROM Using the Automated Options in the Kitchen
So this is a basic kitchen, but you can do things like, add Root support, add/remove apps from the ROM, enable saving apps to the sd card, enabling Wifi tethering, do some automatic optimizations, and a few other things automatically just by selecting the option and hitting enter. It even allows you to put in your own scripts for the ROM to run (but that’s for more advanced users who know how to create scripts of course).
1. After importing a ROM using section II, select the options you want to do to the ROM (by typing the number of the option you want into the terminal/kitchen window and hitting enter. They are all pretty self explanatory.)
2. Continue this until you have all the automated options you want in the new ROM.
IV. Adding/Removing Applications from the ROM
1. In your Ubuntu Virtual Machine, goto Places at the top. Then click on Home Folder, then the WORKING folder that was created in section II when you dissected the original ROM or img files. Then goto system > app. (Also check Data > App as .apks can be put in there as well).
2. In the app folder you will see all the .apk files for all the applications you have currently in the ROM. Simply delete the ones you do not want to remove them from the ROM.
3. To add applications, simply copy any .apk file for the applications you want to add into the app folder.
V. Repackage the ROM so it can be Flashed onto a Phone
1. Once you have done whatever changes you want, you just need to type 99 and hit enter in the kitchen/terminal for the kitchen to take the working folder you have been messing with and compile it into a flashable update.zip ROM.
2. Once it is done compiling the ROM, we can transfer it to our phone.
VIa. Setup Ubuntu to See Your Phone via USB
1. In the Virtual Box windows with Ubuntu in it, click on Devices at the top then click Install Guest Additions. (It should autostart, if it doesn’t, click on the CD that appeared on the desktop in Ubuntu and then click on Autostart.sh. It will ask you for your password you created when setting up Ubuntu, put that in and let it install).
2. Once the Guest Additions are installed, close the Virtual Box Ubuntu Window (choose to Power Down the Machine).
3. Now, open Virtual Box itself (not Ubuntu) and highlight the Ubuntu machine, then click on Settings at the top.
4. Click on USB and make sure Enable USB Controller and Enable USB 2.0 are both enabled.
5. Now plug in your Android phone (do NOT mount the SD card, just plug it in).
6. Now in the USB menu of Virtual Box, click the + symbol on the right and then select your Android Device (name may be different).
7. Once that is installed, unplug your phone.
8. Now, Start your Ubuntu Virtual Box.
9. Once Ubuntu boots up, plug in your Android phone (do not mount the memory card yet) and look for the USB symbol at the bottom (fourth icon from the left) and hover over it and wait for it to say USB Device detected and display your phone. Once that happens, mount the sd card by pulling down the notification bar on your phone and clicking mount.
10. Ubuntu should pop up your SD card on the desktop (if any prompts come up just select do nothing and click ok). We can now transfer files to the memory card of our phone.
VIb. Use RapidShare to Transfer the File from Ubuntu to Windows (if Section VIa was giving you trouble)
1. If you can’t get the USB to work in Ubuntu, then simply open a Firefox browser window, goto Rapidshare.com and upload the ROM to there.
2.Once it is done uploading, ON YOUR WINDOWS COMPUTER NOT UBUNTU, put in the link it gave you when you finished uploading it, to download it to your Windows computer so we can transfer it to your phone.
VII. Flash the ROM
5. Copy the .zip file to the root of your SD card (NOT in any folders, just on the SD card itself).
6. Unplug the phone and turn it off.
7. Turn it back on by holding down home and power (do not let go until the recovery screen comes up) to get to recovery mode (you must have a custom recovery screen to do this, if you don’t find out How To Root and Load a ROM procedure for your phone and do those first).
8. Now select Nandroid Backup to create a backup before we flash the new ROM.
9. Once the backup is done, select Wipe Data / Factory Reset in recovery mode.
10. Select flash zip from sd card and select the ROM you just put on the sd card.
11. Once it is done flashing, click reboot. Enjoy!
Enjoy! Will update this as we add more things for you to tweak FeWant to Flash a New Splash Screen on Your 320×480 Resolution Android Device? Here’s how.
el free to suggest some in the meantime.
Thanks to DsiXDA for his awesome kitchen!
Click to expand...
Click to collapse
thanks for the info..hope for othr mobs also it will com soon
Tell me when it works for SGY
Inform me when it starts working for SGY... PLz I want to make one..
Looking good if work on sgy hehe looking forward for info
Heey everyone here the quide for how to set up kitchen in linux virtualbox
Not made by me but made by the amazing guys from the unlockr Thanks!!!
Part 1
[I Before you begin]
1. This ONLY works for HTC Android devices at the moment, Also other devices!
[II. Download a Virtual Machine and Set It Up.]
1. Download VirtualBox for free from here (the one for Windows Hosts at the top). Then click next on the setup process until it installs.
2. Open VirtualBox and click on New.
3. Name the New Virtual Machine whatever you want (we named it Linux for simplicity’s sake).
4. For Operating System choose Linux, then choose Ubuntu for Version and click next.
5. Click Next again leaving the Memory Setting at what it is preselected at (should be 384mbs).
6. Click Next on the Boot Disk screen as well leaving boot hard disk and create new hard disk both selected.
7. Keep clicking Next until you get to the slider that asks how much space to set for the Linux. Move the slider to 8Gbs and click next.
8. Click next until it is done and shows you the original screen you started on but now with the Linux Machine Powered Off on the left.
[III. Install Linux Ubuntu on the Virtual Machine]
1. Download Ubuntu from here.
2. Once it is downloaded, in the VirtualBox program, click the Start button at the top.
3. Close out all the warnings that come up.
4. Then click on Devices > CD/DVD Devices > More CD/DVD Images… then select the .iso image for Ubuntu you downloaded.
6. Follow the prompts on the screen to install Ubuntu on your Virtual Machine.
7. Once it is installed and reboots, goto Applications > Accessories > Terminal and type this line with hitting enter at the end:
sudo apt-get install sun-java6-bin sun-java6-jre
It will ask you for a password, type in the password you created when you went through the Ubuntu installation process (it asked you for it before finishing the install).
Then it will ask you y/n. Hit y then enter. Then when it shows you the terms and conditions, hit right arrow on your keyboard and click enter to select ok. Then hit left arrow on your keyboard and enter to select Yes.
*NOTE – Your keyboard and mouse will not function on your regular computer once you use them in the Ubuntu virtual machine. To re-enable them, click the Ctrl button on the right side of your keyboard.
**IF YOU GET AN ERROR INSTALLING THE JAVA FILES,
Download the java files manually FROM INSIDE THE EMULATOR/LINUX using Firefox here:
Java6 Bin
Java6 Jre
Then open the Terminal App in Ubuntu and type this with hitting enter at the end of the line:
sudo dpkg -i sun-java6-jre_6.18-4_all.deb sun-java6-bin_6.18-4_i386.deb
And that should fix it.
[IV. Download and Setup The Android ROM Kitchen]
!THIS NEXT SECTION NEEDS TO BE DONE WITHIN THE UBUNTU VIRTUAL MACHINE!
1. Click on the Firefox logo at the top of your Ubuntu installation (in the Virtual Machine).
2. Type this into the url box:
theunlockr.com/2010/03/26/how-to-create-your-own-custom-rom-for-android-part-1-setting-up-the-kitchen (to navigate to this page from within the virtual machine).
3. Now download the latest version of the kitchen file  in the first post from the link below(again from inside the Ubuntu installation on the virtual machine. We are doing this because we want to save this file in our Ubuntu Virtual machine, NOT our regular computer).
Kitchen
4. Again on the Ubuntu machine, Find the .zip file you just downloaded, right click it and click open with Archive Manager and then click Extract at the top.
5. Once you click Extract, it will ask you where. Double click the folder that has the name you created when you installed Ubuntu (my username was theunlockr so my folder is called theunlockr. It is the first folder under recently used in the list on the left). Then click Extract at the bottom right.
[V. Run the Android ROM Kitchen]
1. To run the Android ROM kitchen, click on Applications at the top of Ubuntu > Accessories > Terminal then type the following and hit enter:
./menu
2. You will now be greeted by the simple text menu of the application. Enjoy!
VI. Create Your First Custom ROM
=================================================
Part 2
Before You Begin
1. We are assuming you have already setup the Android kitchen. If not, use our How To Setup The Kitchen procedure and then come back to this one when done.
2. We are also assuming you have already done our How To Root and How To Load a Custom ROM for your phone and have a custom recovery image.
2. This ONLY works for HTC Android devices at the moment, Also other devices
3. Open the Kitchen in your Ubuntu Virtual Machine we created in the Kitchen Setup procedure by typing ./menu in the Terminal window in Ubuntu. Leave it open.
4. All of this is done INSIDE THE UBUNTU VIRTUAL MACHINE (that includes when I say “save to your computer” anywhere in here, means save to you Ubuntu Virtual Machine)!
II. Find a ROM to Dissect
There are two kinds of ROMs you can dissect to create your own custom ROM; Stock ROMs and Custom/Cooked ROMs. DsiXDA, creator of the ROM kitchen we are using, has put together a list of places to get stock ROMs for different devices and a quick how to load them into the kitchen:
From a Cooked ROM (Easiest Method):
1. Copy the update.zip (or equivalent ZIP file) to the original_update folder in the kitchen
2. Type the number for the option “Setup Working Folder from ROM” and hit enter in the Kitchen to create your working folder. (So if its number is 1, type 1 then hit enter).
From a Shipped ROM:
1. Find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device’s sub-forum).
The links below may help:
2a. If the shipped ROM is in a .ZIP format, then simply extract the system.img and boot.img.
2b. If the shipped ROM is in .EXE format, then do the following:
A. In Windows, run the shipped ROM’s .EXE file till it gets to the first dialog. Stop there but don’t close the window yet.
B. Go to Start->Run and type: %TEMP%
C. When the folder opens, search for Rom.zip. Then, open it with an unzip tool. If you get errors trying to open the ZIP file with WinZip or the default Windows unzip program, then use 7Zip (download from here) to extract it.
D. Extract only two files from Rom.zip: system.img and boot.img
3. Copy the two .IMG files to your kitchen’s img_files folder in your Ubuntu Virtual Machine.
4. In the Terminal window that you opened in Section I, type 1 and hit enter to create a working folder from the two .img files.
Now, that you have either the update.zip in the original_update folder of the kitchen OR the system.img and boot.img of a shipped ROM in the img_files folder of the kitchen, you are ready to play with the ROM to make it your own.
III. Tweaking the Imported ROM Using the Automated Options in the Kitchen
So this is a basic kitchen, but you can do things like, add Root support, add/remove apps from the ROM, enable saving apps to the sd card, enabling Wifi tethering, do some automatic optimizations, and a few other things automatically just by selecting the option and hitting enter. It even allows you to put in your own scripts for the ROM to run (but that’s for more advanced users who know how to create scripts of course).
1. After importing a ROM using section II, select the options you want to do to the ROM (by typing the number of the option you want into the terminal/kitchen window and hitting enter. They are all pretty self explanatory.)
2. Continue this until you have all the automated options you want in the new ROM.
IV. Adding/Removing Applications from the ROM
1. In your Ubuntu Virtual Machine, goto Places at the top. Then click on Home Folder, then the WORKING folder that was created in section II when you dissected the original ROM or img files. Then goto system > app. (Also check Data > App as .apks can be put in there as well).
2. In the app folder you will see all the .apk files for all the applications you have currently in the ROM. Simply delete the ones you do not want to remove them from the ROM.
3. To add applications, simply copy any .apk file for the applications you want to add into the app folder.
V. Repackage the ROM so it can be Flashed onto a Phone
1. Once you have done whatever changes you want, you just need to type 99 and hit enter in the kitchen/terminal for the kitchen to take the working folder you have been messing with and compile it into a flashable update.zip ROM.
2. Once it is done compiling the ROM, we can transfer it to our phone.
VIa. Setup Ubuntu to See Your Phone via USB
1. In the Virtual Box windows with Ubuntu in it, click on Devices at the top then click Install Guest Additions. (It should autostart, if it doesn’t, click on the CD that appeared on the desktop in Ubuntu and then click on Autostart.sh. It will ask you for your password you created when setting up Ubuntu, put that in and let it install).
2. Once the Guest Additions are installed, close the Virtual Box Ubuntu Window (choose to Power Down the Machine).
3. Now, open Virtual Box itself (not Ubuntu) and highlight the Ubuntu machine, then click on Settings at the top.
4. Click on USB and make sure Enable USB Controller and Enable USB 2.0 are both enabled.
5. Now plug in your Android phone (do NOT mount the SD card, just plug it in).
6. Now in the USB menu of Virtual Box, click the + symbol on the right and then select your Android Device (name may be different).
7. Once that is installed, unplug your phone.
8. Now, Start your Ubuntu Virtual Box.
9. Once Ubuntu boots up, plug in your Android phone (do not mount the memory card yet) and look for the USB symbol at the bottom (fourth icon from the left) and hover over it and wait for it to say USB Device detected and display your phone. Once that happens, mount the sd card by pulling down the notification bar on your phone and clicking mount.
10. Ubuntu should pop up your SD card on the desktop (if any prompts come up just select do nothing and click ok). We can now transfer files to the memory card of our phone.
VIb. Use RapidShare to Transfer the File from Ubuntu to Windows (if Section VIa was giving you trouble)
1. If you can’t get the USB to work in Ubuntu, then simply open a Firefox browser window, goto Rapidshare.com and upload the ROM to there.
2.Once it is done uploading, ON YOUR WINDOWS COMPUTER NOT UBUNTU, put in the link it gave you when you finished uploading it, to download it to your Windows computer so we can transfer it to your phone.
VII. Flash the ROM
5. Copy the .zip file to the root of your SD card (NOT in any folders, just on the SD card itself).
6. Unplug the phone and turn it off.
7. Turn it back on by holding down home and power (do not let go until the recovery screen comes up) to get to recovery mode (you must have a custom recovery screen to do this, if you don’t find out How To Root and Load a ROM procedure for your phone and do those first).
8. Now select Nandroid Backup to create a backup before we flash the new ROM.
9. Once the backup is done, select Wipe Data / Factory Reset in recovery mode.
10. Select flash zip from sd card and select the ROM you just put on the sd card.
11. Once it is done flashing, click reboot. Enjoy!
Enjoy! Will update this as we add more things for you to tweak Feel free to suggest some in the meantime.
Thanks to DsiXDA for his awesome kitchen!
Thanks to Theunlockr For the amazing Guide !!!
greetings safariking
Video tutorials:
Part 2:http://www.youtube.com/watch?feature=player_embedded&v=q-1ErGSW0ik
Part 1: http://www.youtube.com/watch?feature=player_embedded&v=94Az1kcQvc4
Thanks safariking!
Thanks
very good tutorial thanks
Hi there
Does Android Kitchen Only work in virtual Machine for Ubunty? I have a full installtion of Ubunty and when I type ./menu at the terminal "no such file or directory" followed the installation video but I ain't getting nowhere
Cheers
atomicsoul said:
Hi there
Does Android Kitchen Only work in virtual Machine for Ubunty? I have a full installtion of Ubunty and when I type ./menu at the terminal "no such file or directory" followed the installation video but I ain't getting nowhere
Cheers
Click to expand...
Click to collapse
no.
kitchen can be used on all Linux/Unix OS.
中国人正在尝试提高!
(translation:Chinese people are trying to improve themselves!)
Very nice job. We thank you for your time and effort for writing all of that
Thanks
Sent from my GT-S5660 using xda premium
Just a note: linux isnt required
You can use windows, but does require to install cygwin (linux like terminal)
Sent from my GT-S5660 using xda premium
Welcome
I wrote this post to help people get their Archos g9 tablet running custom roms. If you have any improvement ideas, please post them so I can make this better source of information.
List of content:
Post 1
What is recovery
What is SDE and how to install it
-Also SDE for 4.0.25
List of most commonly used roms
How to install custom roms
How to install offical rom
How to multiboot android 4.0 based roms
Installing 3G stick and Huawei modems support.
Post 2
Change symlinks/binds.
Installing ADB
Installing SuperCharger
Installing Chainfire3D
But why?
FAQ
Useful links
What is recoveryYou can boot to recovery menu by holding volume- while booting your device. From recovery meny you can calibrate your touchscreen, wipe data and do this kind of stuff. Installing SDE creates new entry to recovery menu, called Special Developers Edition. There you can remove android kernel, flash new, export hdd and data. In recovery move up and down with volume + and -. Select by pressing power button
What is SDE and how to install itSDE is shortened word from Special Developers Edition. After SDE is installed, your tablet is able to boot to official rom, recovery, and SDE rom. Most of the roms advice you to use "Remove android kernel" from SDE before you install kernel. When you remove your android kernel from there and install kernel from custom rom, your archos boots directly to custom rom. If you don't delete it, your device boots to official, but keeping volume - while booting gives you change to boot to SDE.
There are 3 guides how to install SDE. Official SDE watermarks your device for archos (there is no watermark on screen ), so they can detect you have installed SDE in some point. It stays even if you remove SDE. Official way is more safe. Also, it removes "only" software warranty. If your devices powerbutton, Usb-port or etc brokes, you can still send it to warranty. Link to official SDE install guide. Big thanks for Shano56.
Then there is unofficial, a bit more dangerous method. It doesn't watermark your device, but is more complicated. Guide tells that it's outdated, but it worked for me. I used official 4.0.4 version while installing. Link to the guide. Big thanks to Shano56.
4.0.25 Guide, by surdu_petru
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
Click to expand...
Click to collapse
List of most commonly used romsThese roms are most commonly used. Most of them are still being developed. I also included link to rooted official honeycomb, because some people have better touchscreen responsibility with it.
ParanoidAndroid 3
Cyanogenmod 10, 4.2 mockup
Cyanogenmod 10
AOKP ROM
[email protected]
Clean_Slim&Fast(Based on official 4.0.25!)
Ubuntu. This requires special kernel, which is compatible with official android 4.0.4Overclockable stock rom
Early CM9
Stock ICS rom with root & busybox
Stock honeycomb with root. (FYI, kernel requires renaming while installing)
How to install custom romsCustom roms have different installing methods, but basic idea is same. You move image file with specified name to specified location.
When coming from stock rom or whengoing to stock rom:
CyanogenMod 10, AOKP, CyanogenMod 9
surdu_petru said:
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
[email protected], Ubuntu, Root 4.0.7 Clean_Slim&Fast
surdu_petru said:
Install :
- copy archos.ext4.update(archos.ext4 in case of Clean_Slim&Fast) in /mnt/storage/ , you can use this command > adb push archos.ext4.update(remove .update if Clean_Slim&Fast) /mnt/storage/
- go to SDE -> Developer Edition Menu -> ( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- after everything was installed - please reboot your device !
Click to expand...
Click to collapse
Honeycomb
Install like Cyanogenmod and AOKP and others, but rename initramfs.cpio.gz to initramfs.cpio.lzo
How to install official romDownload official 4.0.7 rom from here.
Now boot to recovery (hold volume- while booting) and choose update firmware.
Now there should be noew drive in your pc. Drop the downloaded firmware_archos_it4.aos to there and press ok in recovery. Keep usb plugged in while installing. It should take around 30 seconds to 2 minutes. Now choose ok again. your tablet should now reboot to stock rom.
4.0.24 Official is owrking on some devices, but because it won't work on all, i won't cover it here(yet)
How to multiboot android 4.0 based romsInstall modified initfram from this topic. Use the zimage from the rom you want to multiboot. AFAIK you can multiboot with following combos:
[email protected], Ubuntu (download newer kernel from later pages.), Root 4.0.7
and
AOKP, CyanogenMod 9.
You cant use [email protected] and AOKP because they do not use same kind of data. That means that after you have run first rom, the second will bootloop. That is also why it requires wiping data when changing from stock to aokp and vise versa.
Detailed:
Download dmenu-0.3a.zip, and extract initframfs to desktop. Then download [email protected] and stock 4.0.7 rooted. Extract Image files and zimage from either one of the roms. Now just instal like described in earlier section, while using initframfs from multiboot and kernel from other rom.
Installing 3G stick and Huawei modems support.
Trevd made a package to add 3G stick and extra Huawei modems work for AOKP and generally all ICS ROMs. This guy is awesome because he also made some Huawei modems work.
trevd said:
Hi surdu_petru and AOKP fans.
Great work as always, It's not a rom i'll ever use but It's the first time I've loaded an AOKP Rom, I like notification layout, I'll be having that away for my own personal rom Anyway I was more just passing through and noticed 3G was not working yet. As seen as though that seems to be my speciality and preoccupation/addiction for the last 9 months I thought I do something to remedy that situation for you.
Here's an hotfile link to download the update [ 3g-archos-aopk.7z ] this should contain everything you need to get the Archos 3G Dongle, just for ****s and giggles as a extra bonus i've also included the huawei support file as well :good:
Installation:
From a command prompt / bash terminal
Code:
7z x 3g-archos-aopk.7z
adb push 3g /
adb shell reboot_into sde
extracting the 3g-archos-aopk.7z will give youu a 3g directory in you current directory, we then push the contents of the 3g directory to the root direcotry on the device. This operation is recursive.
Have Fun!
What follows is a detailed explanation of what files and modifications are required to add 3G support.
Archos 3G Stick
The changes / additions to add this functionality breaks down like this ; The following required binary's were on the device already:
** /lib/modules/hso.ko is insmod'd by the device specific init file /etc/init/init..rc
Code:
/lib/modules/hso.ko[B]**[/B]
/usr/bin/usb_modeswitch
/system/lib/libtcl-ril.so
/system/bin/rild
/system/bin/pppd
/system/xbin/chat
/etc/ppp/init_pppd_datakey
/etc/ppp/ip-up-datakey
/etc/ppp/ip-down-datakey
/etc/ppp/peers/datakey
/etc/chatscripts/datakey_start
/etc/chatscripts/datakey_stop
/etc/usb_modeswitch/1bbb_f000
The following required services were already defined in the device specific init.rc's located in /etc/init/init..rc ,
*** switch_ms_3g defined by /etc/init/init.archos.rc
Code:
service service switch_ms_to_3g[B]***[/B]
service pppd_secrets
service pppd_datakey
service ril-daemon
So what's missing? you may ask as this pretty much is everything that is needed by the Archos 3G Stick.
Standard Archos Roms use the UsbKeyManager.apk system service to start the switch_ms_to_3g and ril-daemon service's. I replace that with my own ueventd handling native service and add an additional to configuration file keep everything clean
Code:
/system/bin/hotplugd
/init.dongle.rc
I've added the following line to the top of the /init.rc
Code:
import init.dongle.rc
All that is left to do now is enable mobile networks on the rom. I used apktool to decompile the /system/framework/framework-res.apk and change the following values
res/values/bools.xml
Code:
true
true
res/values/arrays.xml
Code:
wifi,1,1,1,-1,true
mobile,0,0,0,-1,true
mobile_mms,2,0,2,60000,true
mobile_supl,3,0,2,60000,true
mobile_hipri,5,0,3,60000,true
mobile_fota,10,0,2,60000,true
mobile_ims,11,0,2,60000,true
mobile_cbs,12,0,2,60000,true
wifi_p2p,13,1,0,-1,true
"1,1"
"0,1"
"7,1"
"9,1"
res/values/strings.xml
Code:
ppp1
Huawei Support
The extend this functionality further I added the following files
Code:
/etc/ppp/init_pppd_gprs
/etc/ppp/ip-up-gprs
/etc/ppp/ip-down-gprs
/etc/ppp/peers/gprs
/etc/chatscripts/gprs_start
/etc/chatscripts/gprs_stop
/etc/usb_modeswitch/ [ numerous configurations files ]
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
We also need to chmod 6755 /system/bin/pppd but that is handled/checked in the /init.dongle.rc so there is no need to do that manually
Click to expand...
Click to collapse
Change symlinks/bindsTrevd wrote guide to let people know how to change binds. That way you can move large folders, like Gameloft games and navigator files to ExternalSD, saving InternalSD space.
trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
Installing ADBADB comes from word android development bridge, and it allows you to debug, move files and get shell access to your tablet.
Archos said:
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
Go to the Android SDK page and download the latest SDK for your operating system.
For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
Click to expand...
Click to collapse
Running adb from anywhere
steviewevie said:
We need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Click to expand...
Click to collapse
sources:Archos, steviewevie
Installing SuperchargerSupercharger is a multiscript which makes the tablet work much better. Its created by Zeppelinrox, and its official topic is here. We are using also script manager in this guide. That way we can make MinFrees and OOM apply.
In this guide we'll use Apex launcher which is moved to /system/app for our default launcher.
We are also using adb to configure and run Supercharger.
Because stock launcher is odexed and i am not writing how to deodex, we are not using it.
First make sure apex is your default launcher. This can be tested by pressing home button in homescreen.
If it show mini previews of your homescreens, apex is your default launcher.
Now lets begin:
go to here and download newest file. At
the time of writing, it is Update 9_RC11_test6. Move it to your adb folder.
Then open commandline. This can be opened with windowskey + R and writing cmd. Navigate
to adb folder using cd command. I have made adb to run from anywhere, so i just navigate to the downloaded file.
Now use command "adb push v6* /mnt/sdcard" then use command "adb shell". Now you should have
shell access to your tablet. Now do following
su
cd /mnt/sdcard
sh V6* /remember capital V)
Supercharger script should open now. After presentation, script should print after telling your busybox version
"com.anddoes.launcher is the home launcher!" Now continue install. Supercharger will tell you everything you need to know.
So just follow the instructions. After choosing kernel tweak, you get bunch of permission denieds.
We can't help them, so lets just continue.I recommend on using all the tweaks that you can,
but it is your choise do you want to use or not. After all the selections are selected and your in
driver panel, choose number 32. It'll reboot your tablet and wipe dalvik. When the tablet has booted, lets run supercharger script again.
So write these again:
su
cd /mnt/sdcard
sh V6_Super*
After getting to drivers panel, you notice that minfrees are not in effect, and neither is OOM Grouping Fix BUT if they are, you can ignore this step..
Install script manager from market and open it. Give it root permissions and navigate to /system/etc/init.d
press SS99SuperCharger to open its settings. Now press the Su button and then Boot button.
Now press save, and then click it's name which appers to right. Then press back button and reboot.
Now Minfrees should work, and OOM too.
Now you can run 22 if you want to try it. Supercharger is now fully working.
Installing Chainfire3D
Chainfire said:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Click to expand...
Click to collapse
It is very useful for running gameloft games and other games too. I recommend buying it. There are some plugin for it, but i'm not going to tell you about it now.Play store link.
After downloading it, open it and choose "Chainfire3D Driver" and from there "install". Then confirm it and tablet should reboot. Now reopen it and choose "Default opengl setting". From there you can tweak 3D performance if some games lag. Also, if you install plugin, there you can apply them. I personally use "reduce texture quality".
But why?
This section is to point few reason why to follow these guides. Lets begin:
SDE
Well, you should install this if you want to customize your tablet. If your happy with your tablet running stock, you don't need this, or any other guides.
Custom roms/kernels
Custom roms allow you to use root, they make your tablet faster and add extra functionality. This "functionality" includes: Overclock, run init.d scripts, enable both cores with all governors, root and themes. The benefits are not limited to these, but I could name this quickly. If you wan't to try something which is close to stock, but still has root and some custom functionalities, i would recommend deodexed 4.0.7, or [email protected]
Install official roms
These roms do not require SDE, but will not include root or anything fun . Updating your official rom has many benefits. They include fixes and boost your tablets performance.
Multiboot
Multibooting allows you to have 2 or more roms, which you can choose which to boot on startup. I would recommend this if you want to test functions with root, but still have "backup plan" if testing rom renders unbootable.
3G support
Basicly this allowes some extra huawei 3G sticks to work. There is no list of working stick, you just have to try and hope.
Change symlinks/binds
These allow you to "move" eg. gameloft games to external sd, and allow you to acces your externalsd via internalsd folder.. That way your gamedata does not eat the valuable internalsd space.
ADB
You need this to transfer rom to your tablet. It is also required when you sent logcat reports to help remove bugs.
SuperCharger
This makes your tablet work more fluid. I personally install supercharger to all my android devices. It removes need for task killer, and makes the device work better. Everyone has different results, and it costs only time to install, so i would recommend installing it.
Chainfire3D
This tool allows you to play games made for other GPUs and it can tweak application graphics. You can make the game look worse, but run better or adjust the grphics for a bit higher, so the game looks nicer.
FAQ[/CENTER]
These questions and answers are collected from various sources.
surdu_petru said:
How to activate second core for all govenors in surdu_petrus roms?
To activate the second core, you need the following steps :
- copy /system/S1tweak in /system/etc/init.d/ or ( > adb shell ; # cp /system/S1tweak /system/etc/init.d ; # exit )
- open No-frills CPU Control :
- choose the desired Governor ( but not hotplug ) !
- choose the desired frequency , but not overclocked ! ( when the device will boot - will open with the selected frequency , so please choose max. frequency = your max. stock frequency )
- check "Apply on boot"
- check "Applay"
- check allow if superuser asked permission
- reboot your device !
- Now , both core will be used in any selected Governor ( other than hotplug ! ).
Click to expand...
Click to collapse
What modems does Trevds mod support?
trevd said:
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
Click to expand...
Click to collapse
Shano56 said:
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Click to expand...
Click to collapse
[/quote]
Useful linksSome link i consider useful are here:
G9 101 16GB 1.5GHz Teardown! (Lots of Images)
XBMC for android
Want faster GPS? Follow this guide
3th just i remember something to add. Comment and give me some feedback. It helps me to make this topic useful for beginners, and for those who seek info.
I meant to edit first post... well, this works as 4th reserved then.
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
trevd said:
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
Click to expand...
Click to collapse
Thanks for the feedback.
I removed the part which had github link, and modified the AOKP section to tell it works with all ICS ROMs.
I'll included your mini guide. I might even have some use for it myself...
Sent from my GT-I9100 using xda app-developers app
help me for multi boot ubuntu ics bleuv03
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
muti642 said:
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
Click to expand...
Click to collapse
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
muti642 said:
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
Click to expand...
Click to collapse
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
THX
julle131 said:
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
Click to expand...
Click to collapse
Thank you thanks you it works well, I do not use the right kernel or the good image of ubuntu. ps: the touchscreen does not work but using the OTG is perfect.
thank you again julie :good:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
solrakk6 said:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
Click to expand...
Click to collapse
Yes, you must use adb. I assume your "untoot" means unrooted. You use cd command to navigate to your adb folder and from there to platform-tools. Also drop archos.ext4.update to there. Then use the adb command to move the file. Moving file to that location does not require root.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
hondacity said:
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
Click to expand...
Click to collapse
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
hondacity said:
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
Click to expand...
Click to collapse
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
http://update.archos.com/9/gen9/gen9_4.0.26/firmware_archos_it4.aos
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
hondacity said:
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
Click to expand...
Click to collapse
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Dear,
I applied same as you say but ending on same 221 error. Any thoughts please.
Best regards.:crying:
If you got ANY questions? Feel free to ask here..
[HELP THREAD]Any Questions? Anyone Can Ask here [GT-5360/5510/5512/6102]
VERY LENGTHY THREAD?? Difficult to read in app? Yes I know friends!! That's why added hide/spoiler button to each post & link to first post in every posts end
Hi, Everyone, This is a GUIDE to NEW / EXISTING users.. There are guides below for advanced users too.. So i have shared my experience at XDA with you all to make others understand and help each other.
If you want to know something/ want me to include a topic here, please PM me.. I will see if i can help with that and write about it.
Hopefully this will help many of you, Now READ ON.. Click On "SHOW CONTENT" Button to See the content on each posts below!
DIFFICULTY LEVELS: It tells you how much difficult it is for you to do the task described below. See the headings of guides in every post to see difficulty of that task.
* --> Very Easy
** --> Easy
*** --> Moderate
**** --> Difficult
***** --> Very DifficultINDEX OF THIS THREAD:
* Abbreviations/Acronyms used in XDA (Android language) [SEE 2ND POST]
* Simple methods to get LOGCAT, DMESG [SEE 3RD POST]
* CWM MD5SUM mismatch error while restoring? Solution for this: [SEE 4TH POST]
* How to use SDCARD instead of internal storage for apps[LINK2SD] [SEE 5TH POST]
* Detailed steps to install Stock rom/Firmware through ODIN [SEE 6TH POST]
* ROM installations instructions [IN GENERAL] [SEE 7TH POST]
* Kernel installations instructions [IN GENERAL] [SEE 8TH POST]
* How to deodex a stock rom in easy way using DSIXDA Kitchen [SEE 9TH POST]
* USEFUL LINKS TO THREADS/GUIDES SECTION [SEE 11TH POST/1ST POST OF 2ND PAGE]
MISCELLANEOUS: [SEE 10TH POST]
* Thread Title tags confusing? Its explained here!
* Why give "Thanks"? Thanks meter explained!
* Stars, User Titles: Junior, Member, Senior Member........? Read to know more!
* XDA/TAPATALK app image uploading problems??
* Make your Thread/Post Aligned(Neat) by using BBCODE TAGS
* Battery Drain?? Read these tips to avoid it.
* Enable Whatsapp *AUTO DOWNLOAD IMAGE OPTION* in new versions [TRICK]
PLANNED GUIDES ARE:[12th POST]
How to make a kernel--Writing in progress
How to get 10 without spamming / complaining!!
How to modify apps background,looks etc.
CREDITS :
To all my friends and xda members who gave me info to learn about these things.
To anmolsharma1293, deathnotice01, jaison thomas, kidcarter93, lavadepa, MNgez, nikufellow, tjsgy, wcypierre who gave suggestions and info and tips to improve this guide.
To The-Captain our moderator for helping us to improve ourselves, learn more and being kind to new users too.
Credits are added to respective people in the posts related to them whenever i have taken info / used their work[if not done, i will do it soon]. Informations obtained from other threads have been added in the posts related to it and i have done it with the permission of the thread OP. If i have forgotten someone's name please do let me know, and i will add it ASAP..
And please tell me any suggestions to improve this guide to help newbies/noobs as this guide should help all of us to get better at things we can do with an android. PLEASE REPORT ME ANY MISTAKES IF I HAVE MADE IN WRITING THE GUIDE/ IF THERE IS A WRONG INFORMATION.. I WILL CORRECT IT ASAP..
If i missed anyones credit, please forgive me and let me know.. and i will add it as soon as i can, promise!
Thank you.
Abbreviations/Acronyms used in XDA (Android language)
The reason for this guide is that many new users would have difficulty to understand what are these short forms.. everyone says cwm, rom, cm, etc.. but no one says what it is.. and you may feel a bit shy/embarrassed to ask them what it is. So here is my attempt to cover them..
Please do let me know in PM if some words are missing and you want them to be covered.. i will gladly add them, thank you.
This Post is an inspiration from mrhaley30705's thread & Diablo67 thread.
Use CTRL+F to find a specific term.Difficulty --> *
XDA RELATED ACRONYMS
DEV: Developer
ERD: Elite Recognized Developer
FM/FSM: Forum Moderator/Forum Specific Moderator
RC: Recognized Contributor
RD: Recognized Developer
RT: Recognized Themer
SM: Senior Moderator
GENERAL
AFAIK: As Far As I Know
ATM - At the moment
BTDT - Been there done that
CRACK: The password / product key / license key illegally used for unauthorized usage are known as a crack of the software . Also please read the warning posted at warez meaning below. The same applies to cracks
ETA - Estimated time of arrival.. Note: Asking ETA in dev section is a big NO NO..!!
FTFY: Fixed that for you
FTW - For the win
FWIW: For what it's worth
FYI: For Your Information
IBTL/IB4L - In before the lock / In Before Lock
IDK: I Dont Know (Thats what it means and i am not saying i dont know about IDK!!)
IIRC - If I recall / remember correctly
IRC - Internet Relay Chat
LOL - Laugh out loud
NEWBIE: Someone who is new to this field/ forum and wants to learn how to do it rather than say "NOT WORKING! FIX IT!".
NOOB: Someone who is new and doesn't want to learn "HOW" its done, just want to "USE" the end product. So, please guys dont be a noob, be a newbie!
OP: Short for Original Poster, or the person who originally started the thread.
OT - Off Topic
PM: Short for Private Message. Allows users of XDA to send and receive non-public messages. Accessed from USER CP.
P.S: stands for Post Script. It is used when u wrote a message on a postcard and u forgot to mention an important information.*
ROFL - Roll on floor laughing
RTL: Right To Left support (In Some languages you have to start reading from right and end towards left side.. as against to usual method of reading from left to right)
SMH: Shake my head
STH: Something
TBH: To Be Honest
TIA: Thanks In Advance
THREAD: An individual issue page on the forum. This thing you're reading is a thread.
TLDR: Too long to read
TM: stands for Trademark.
USER CP: Short for User Control Panel. This button near the top of the XDA page allows users to update their avatar, personal information, and signature. PMs and subscribed threads can also be checked in this location.
WARES/WAREZ: Warez refers primarily to copyrighted works distributed without fees or royalties, and may be traded, in general violation of copyright law. To make it simple, it is any app/software which has to be paid to use them, but are used without paying any money.. PLEASE NOTE: THIS IS NOT TOLERATED AT XDA. SO PLEASE DONT POST WARES ANYWHERE ON XDA FORUMS. YOU WILL GET BANS/INFRACTIONS IF YOU DO SO!
ANDROID DEVICE RELATED:
ADB: Android Debug Bridge, a utility to run on a PC to allow connection to and control of an Android device. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
AOSP: Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK: An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Apps2SD:A method of storing applications and cache on the device's microSD card.
Bloatware: Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted
Boot Animation: Boot animation is a term for a graphical representation of the boot process of the operating system. After you switch on / reboot phone you see this.
BOOTLOADER: There are two of these; the primary and secondary bootloaders. These programs tell the Android device how to start up, and are critical to its functionality.
Bootloop: When your system recycles over and over without entering the main OS.
BRICK/(HARD BRICK): An Android device that is completely non-responsive, i.e. nothing lights up, the screen does nothing, no combination of button presses cause any reaction. Can only be restored by JTAG or warranty service.
BUILD.PROP: A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations. It is also used to make tweaks to boost speed/performance, etc.
BUSYBOX: An application that contains many standard Unix tools.
BUTTON COMBO/THREE BUTTON COMBO: The act of pressing several buttons at the same time to produce a desired result (e.g. press and hold volume up+home button+power button for 10 seconds will reboot into the RECOVERY menu at any movement when phone is on or Press and hold volume down+power button+home button to get into ODIN mode/DOWNLOAD mode).
Cache:A component that transparently stores data so that future requests for that data can be served faster.
CM: Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
CPU: It stands for Central Processing Unit and handles all the complex mathematical formulas necessary to do everyday things like surfing the Internet.
CSC - File with Carrier Customizations
Custom bin counter: A line of code in several Samsung Galaxy devices' bootloaders that counts the number of times a user uses ODIN to flash ROMS/KERNELS to the device. Commonly used to detect software modification. This is called custom bin down in ODIN mode and it should be 0 to claim warranty. Can be reset with GALAXY TOOLBOX APP by Doky73
Custom: Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs.
CWM: Short for ClockWorkMod Recovery Menu. This is a program that allows you to install custom ROMS/KERNELS as well as do many other customizations. Often referred to as the "RECOVERY MENU"/"CWM"
DALVIK CACHE: The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
DALVIK: The Android operating system's memory management tool. This program handles which other programs are running and assigns memory to them
DEODEXED: Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
DMESG: dmesg (for "display message") is a command on some Unix-like operating systems that prints the message buffer of the kernel..
DOWNLOAD MODE: Read Button combo to know about this.
EFS: The directory /efs on the Android device's internal storage. Contains files with the Android device's IMEI, wireless devices MAC addresses, product code, and other information..
EMMC: Short for Embedded MultiMediaCard. A chip architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array package.
EXT4: A journaling file system (e.g. NTFS, FAT32 are file systems) often used by Linux distributions. Can be used with Android.
EXTERNAL SD: A micro SD card that has been inserted in the micro SD slot in the Android device. Can be removed.
FACTORY RESET: This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card. It will just make it as a phone just bought from the store state.
FC/FORCE CLOSE: When a program on the Android device becomes unstable/gets an error, the DALVIK program will force it to terminate to prevent further system instability which appears as a Force Close message usually in phone.
FLASHING: The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
FREEZE: Specific to LINK2SD/TITANIUM BACKUP. Using these 2 apps, the user changes a program into a non-functional, but still installed, state. Useful for identifying problem and FCs.
gapps - Google Applications, like GMail, Calendar, Maps, G+, etc
GB - Gingerbread, AKA Android OS 2.3.X
GOVERNOR: A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA: Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS: Short for Ice Cream Sandwich, the Android OS version 4.0.x.
IMEI: Short for International Mobile Equipment Identity. A unique number to identify GSM, WCDMA, and iDEN phones. Used by GSM networks to identify valid devices.
INTERNAL SD: The internal storage memory of the Android device. Not a physical SD card that can be removed.
JB: Short for Jelly Bean, the Android OS version 4.1.x.
JIG: A piece of hardware that makes a physical connection between pins of the USB slot to force the Android device into DOWNLOAD mode.
JTAG: A process of connecting directly to the main board of the Android device to rewrite corrupted BOOTLOADERS.
KERNEL: The kernel is a program that constitutes the central core of a computer operating system. It has complete control over everything that occurs in the system.
LAST_KMESG: last_kmsg is a dump of the printk statements from the kernel before the operating system itself crashed.
LAUNCHER: A program that launches programs in Android. Examples are Touchwiz (Samsung), HOLO Launcher, Launcher Pro, ADW Launcher, and Go Launcher EX.
LCD Density: Pixel density is a measurement of the resolution of devices in various contexts; typically computer displays, image scanners, and digital camera image sensors.
LOGCAT: A command to view messages in one of the system logs. See Android logger.
LTE: Stands for Long Term Evolution. It is based on the GSM/EDGE and UMTS/HSPA network technologies, increasing the capacity and speed using a different radio interface together with core network improvements.
MAI77 method: Its only known here. So dont say this out of SGY forum. This is a method to flash kernel through CWM using Kernel flasher tool made by MAI77. Its basically you have kernel flasher tool and boot.img file in SDCARD root and you select kernel flasher tool in CWM and it will install boot.img file which is the kernel you selected.
MD5 CHECKSUM: A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
MIUI: A Chinese built-from-source ROM. Short for "Mobile Internet User Interface". Also can refer to the MIUI music player, which has been included in other ROMs.
Mod: The act of modifying a piece of hardware or software or anything else for that matter, to perform a function not originally conceived or intended by the designer.
MODEM: The software that interfaces with the phone's radio hardware to connect to cell phone towers.
NANDROID BACKUP: A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
ODEX: A file that is associated with an APK file, containing a list of the dependencies for the program. See also DEODEXED.
ODIN: A Samsung proprietary program that allows the Android device to be flashed back to stock or with custom software.
OVERCLOCKING/OC: Setting the processor's clock speed to run faster than its default setting, i.e. 1248 MHz (1.2 GHz) vs 832 MHz (Default)
OTA - Over-the-Air (usually used as "OTA update" for firmware updates that can be installed directly via 3G/4G/Wi-Fi without the need of an PC)
PIT FILE: Short for Partition Information Table file. One of the possible file types used while flashing with ODIN or HEIMDALL.
Port: To Take a rom or app from one phone and program it to work on a different one.
Ram: (Random Access Memory) A group of memory chips, typically of the dynamic RAM (DRAM) type, which function as the computer's primary workspace.
RECOVERY: The menu that allows a user to do many low-level operations on the Android Device. This menu can either be the stock Samsung menu, or the CLOCKWORKMOD RECOVERY MENU (CWM). See also CWM.
RFS: A Samsung-proprietary file system (e.g. NTFS, FAT32 are file systems) used on some Android devices. Stands for Robust File System.
RIL - Radio Interface Layer
ROM: The collection of programs, themes, and settings that create the general look-and-feel of your Android device. This is what most users will initially be wanting to change. Or custom ROM firmware file, Can also refer to a Read-only memory.
ROOT: Changing the permission level of the Android system to its most powerful level, the root user, allowing full access to the file system. More like Administrator permission in Windows OS.
SGY /SGYD /SGYP /SGYPD : Samsung Galaxy Y / Samsung Galaxy Y Duos / Samsung Galaxy Y Pro/ Samsung Galaxy Y Pro Duos
Sideloading: It means installing applications without using the official Android Market.
SOFT BRICK: A device that is not functioning correctly, but still shows some signs of operation. See also BRICK.
STOCK: The Android software version that comes installed on new devices, prior to sale to the user. Can also be used to refer to the Android software issued from Samsung or the carrier.
Superuser/SU: On many computer operating systems, the superuser is a special user account used for system administration. Depending on the operating system, the actual name of this account might be: root, administrator or supervisor.
TETHER: Connecting the Android device to a computer via a wired or wireless connection to allow the transfer of data through the Android device's internet connection. Commonly used to provide internet access to a laptop or desktop computer when other methods are not desired or available.
THEME: A collection of images, backgrounds, colors, font types, and other visual items to change the Android device's look and feel. Separate from LAUNCHER, and is usually FLASHed in CWM.
TWRP2 - an alternate recovery mode for your phone
UNDERVOLTING/UV: Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
Updater Script: When Android devices install updates via CWM/recovery mode they have to perform a wide range of functions on files and permissions. The scripting language is called Edify and is defined primarily in the bootable/recovery/{edify,edifyscripting,updater} directories of the Android source-code tree.
WCDMA: Short for Wideband Code Division Multiple Access. An air interface standard in 3G mobile communications networks that allows higher speeds and more users.
ZIPALIGNED: An archive alignment tool that provides important optimization to APK files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Reduces RAM consumption.
Simple methods to get LOGCAT, DMESG
Devs asking you to get a logcat and give?? Yes it helps a lot for devs if you give logcat to solve problem. So dont wait till devs ask you to get a logcat! Just give them a logcat when you tell them this/that doesnt work. This way theirs and yours time will be saved and unnecessary posts will be avoided. Now i will give you simple steps to do it. There are two main ways to do a logcat, 1. within android device, and 2. through adb using PC.WITHIN ANDROID DEVICE METHOD:
This i learnt from paxChristos from his thread.
1. Logcat within android device can be done in one of two ways, through a Logcat app: Difficulty --> *
Here are two good apps: aLogcat or Catlog
Both of these programs can dump their logs to a text file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
2. Through Terminal method: Difficulty --> **
Install Android Terminal Emulator app from Play Store..
Open terminal app you just installed..
Enter these commands:
After every command press ENTER/SUBMIT button
Code:
su
then accept the superuser popup message[it comes only first time if you select checkbox "remember the choice"]
Code:
logcat -v long > /sdcard/test.log
Or use this command:
The -v long puts the text in a nice format that is more easily readable. The *:W will search for all warnings, errors, and fatals, while the *:S will silence everything else.
So essentially, u will have a .txt file that has a log of all warnings and up, nothing else, and it'll look pretty too!
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
now press home button to minimize the terminal..
and do the task which is giving problems/ whichever task log you need to give to dev..
then drag the notification bar..
select terminal app in it..
now press and hold "Volume down button" and touch c button on keyboard.
This will stop the command..
now use this command twice
Code:
exit
Now app will get closed. go to sdcard to find test.log file.. upload it to here so that dev can access it..
Thank you for reading it with patience hope you can get logcat now..
Note: if you are stuck in boot and want to take logcat.. READ LOGCAT FROM ADB METHOD BELOW.. the above one is simple method for these tasks for eg.. if you are having some force close of app/lag etc.. then after entering second command press enter and then use home button to minimize terminal.. dont worry it will take log.. now open that app and once it gives force close then click on it and then open terminal again and press volume down button + c to terminate command.. then use exit command two times... done.. now go to sdcard and find a.txt file
From PC[i.e, ADB] LOGCAT METHOD :Difficulty --> ***
There is an advantage here. As doing this way, you can start using logcat when your device boots. There are 2 ways here again..
PREPARATION:
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
ADB USAGE INSTRUCTIONS:
Then go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb logcat > filename.txt
Or
Code:
logcat -v long > /sdcard/test.log
Or
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
Now perform tasks in android device of which you need to give logcat for the devs. Then use CTRL+C to end the command.
Now find the filename.txt inside the Android folder which has logcat. Upload this file and give link to dev..
Or There is another method called All in one logger tool by wcypierre which can get you logcat and dmesg. I have not tested it myself. But i am sure it will work and you can go to that thread and ask your queries about that tool if you want to use that. The dev will help you gladly. So, please thank him for his nice work.The full list of options that can be used with logcat command is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the *:W with any other letter from above to get more info.
From PC[i.e, ADB] GET DMESG:Difficulty --> ***
Note: You will need adb access for this to work, same as logcat. Read PREPARATIONS above to find adb files required and related setup.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things.
Go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb shell dmesg > dmesg.txt
To get last_kmsg:
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
From Android Device GET DMESG:Difficulty --> **
You can also get the dmesg by using terminal emulator.
Code:
dmesg > /sdcard/dmesg.txt
To get last_kmsg:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
FOR APP DEVS / ADVANCED USERS ONLY! LOGCAT INSTRUCTIONS:
Thanks to jaison thomas for this method! NOTE: I have not tested this. sorry. But it will definitely work. I edited the quoted message to make it simple.
jaison thomas said:
log cat using eclipse, i thought it will be simple for advanced users who are into app development.
I will guide how it works
1) install samsung kies in your pc
2) turn on usb debugging in phone.
3) install android plugin for eclipse .
4) now on eclipse click on "window" --> "show view" --> "other" --> "android" --> "log cat". Then click "ok".
Thats it .logcat window will be shown in lower bottom side of eclipse.it is having a green color icon. Also there may be a chance of logcat window minimised in eclipse.do look for a green icon.
5) now conect ur phone using datacable u can see all the things happening inside the phone in log cat window in eclipse.
NOTE: if you couldnt find android under other option.. Do this:
u didnt install android plugin for eclipse do as follows to install android plugin for eclipse.
1) click on help
2)click on install new software
3) then click on add.
4)then you will get a text box with name and location. in name text box type android or any thing,
in the location copy paste this
https://dl-ssl.google.com/android/eclipse/ and press ok,
5)In the Available Software dialog, select all check boxes and click Next.
6)In the next window, you'll see a list of the tools to be downloaded. Click Next.
7)Read and accept the license agreements, then click Finish.
8)If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
9)When the installation completes, restart Eclipse.
Click to expand...
Click to collapse
CWM MD5SUM mismatch error while restoring? Solution for this:
Difficulty --> **
If you have made a nandroid backup and we never actually test whether it works/not.. So, some day when you need to restore it.. you get an error while restoring that "md5sum mismatch" restore aborted!! Then you are in a really bad situation right?? Wrong.. Do this.. and the problem should be solved..
You need to edit nandroid.md5 file stored in /sdcard/clockworkmod/backup/"backup name"/nandroid.md5
NOTE: backup name is usually date and time of your backup/ you could have renamed it to some name.
You need terminal emulator app. Download from play store (android terminal emulator)
Open terminal emulator app and input these commands..
Code:
cd sdcard/clockworkmod/backup/2012-09-30.03.18.47
NOTE: Change 2012-09-30.03.18.47 to the name of your folder
To See what file extensions need to be included. type
Code:
ls
( lowercase "L") and hit enter.
This will list everything inside your current directory (backup files of that particular backup)
To make sure there is no nandroid.md5 file existing already, enter this command:
Code:
rm nandroid.md5
Now to make a new nandroid.md5 file
Code:
md5sum *tar > nandroid.md5
Now its ready to be used in restore inside CWM..
NOTE: USE this procedure to repair nandroid md5sum mismatch error if you are getting this on a backup which has not been modified. If you have opened the backup files to modify the files inside. Its not advised to do this. So, please take note of this.
Special Thanks to cynnar for this idea. i tweaked it to our device from his post.
CLICK HERE TO GO TO FIRST POST
How to use SDCARD instead of internal storage for apps[LINK2SD]
Difficulty --> **
Welcome to LINK2SD app friends!
Easiest app to install and use to extend your internal memory.
What it does?
It creates a symbolic link file(more like shortcut in windows) for apps in internal memory which will point to the real app which will be saved in your sdcard second partition! It mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.
It can also move user apps to SD card (force move), with batch moving (multiple apps moving at once) capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).Preparations:
* You need to have root permission/access[Rooted phone]
* A second partition on your SD card. You should have two partitions on SD card and both should be primary.
* The second partition is used for application files and can be ext2, ext3, ext4 or FAT32 (I prefer FAT32 and no issues i have seen, see note below to know why?).
Note:
1. The second partition will not be accessible through windows OS as it recognises only first partition on removable devices. In Linux you can access second partition too!
2. ext4 is the latest ext format but several ROMs/Kernels have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.
Steps to make 2nd Partition in SDCARD:
Connect phone to PC using USB Cable. Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
Now drag the notification bar from status bar in phone and select "USB Connected" messasge.
Then select "Connect USB storage" button.
Once it is connected, Make a backup of sdcard first to PC(Copy all files inside sdcard to any fodler in PC). Otherwise you will loose data in sdcard.
Now open "MiniTool Partition Wizard Home Edition" download it from This LINK
This tool is compatible with Windows 2000/XP/Vista & Windows 7. Or Use "Gparted" tool for linux users Or "iPartiton" for Mac users.
Note: this partition manager QUEUES the operations. So nothing is deleted and changed UNTIL you click "APPLY" and then confirm by clicking "OK".
Make sure you are deleting partition on SD card! (not your hard disk for example). Dont be afraid, just read everything and think twice before selecting correct drive. Do you see three gray icons on the bottom? Under each of them the capacity of each drive is listed, and SD CARD has slightly different icon. Check the sdcard capacity given in the window to select the proper one.
select "Create As": PRIMARY on the sdcard partition. Choose whatever size(leave some space which we will use for apps partition) you want for sdcard( to have your music, personal files, etc.).
Select "File System:" FAT32
select the second partition below the one you just created which will have the space left when partitioning the first partition.
Select "File System:" FAT32 (YOU can use Ext2, Ext3, Ext4 also.) But my suggestion is please use FAT32. You wont have problems as all ROMS/KERNELS support fat32 by default!
Click "apply" button on top left corner. Partitions will be created and card will be formatted.
Now put your files back to sdcard and disconnect from PC.
NOTE: You can also use CWM partition option. If you want to use CWM partition method to partition your sdcard then see here. I have never tried this method. So i cannot help you with that.Steps to install and use link2sd[2.2.3 version]:
Let the media scanner finish the scanning process, then open link2sd app and you will see a pop up menu "Select the file system of your SD card's second partition"
Choose your partition type for "second partition" you created while partitioning, say you choose "FAT32/FAT16" then your sdcard second partition should be FAT32/FAT16 which is nothing but FAT or vFAT.
Now Press OK. After 2-10 seconds you will see another pop up menu "Restart your phone" Press "OK" (message goes like this "Mount script created, please restart your phone to mount the second partition of your SD card.")
Now do a reboot of your phone.
Link2SD successfully installed.
To make space inside internal memory-->
* Now open LINK2SD app and you will see three buttons on top bar. click on the first button from left side. you will see:* All --> It will show you all the apk/app files in your phone (130+/- apps)
* System --> It will show you all the system apps in phone (100+/- apps)(stored in system memory)
* User --> It will show you all the User apps(i.e, installed by you) in your phone (30+/- apps)(stored in internal & sdcard & second partition memory)
* Linked --> It will show you all the linked apps in your phone (it wont show any now)(stored in your sdcard second partition memory)
* On SD card --> It will show you all the user apps (10+/- apps)(stored in your sdcard first partition. usual sdcard method)
* On internal --> It will show you all the user apps (10+/- apps)(stored in your sdcard first partition. usual sdcard method)
* Frozen --> It will show you all the apps that have been stopped. This is a method same as Titanium backup app "freeze" method. It makes your app invisible to phone. I.e, it will be installed and ready to use.. but you wont see it anywhere in launcher and if you click on a shortcut of such "frozen" app it will say "app not installed" or such message.* Now select options button in phone, then select "Multi-Select". Now press "select all" option.
* Now press "Actions" button. In new pop up window select "Create link"
* Now in new page which appears, select all 3 options to link application, dalvik-cache, library files. Then press "ok" button and wait till the process ends. It will take time depending upon how many apps you have. around say 5 minutes.
* Now go to linked option from top bar first button from left side. and see al the apps having linked->sdacrd tag on them which means they are now in sdcard second partition..
*Long press on any app to view more options.
NOTE: 1. you cannot move link2sd app from internal memory. It is better to keep it there.
2. System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
3. Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files.
4. Do not move keyboard apps to system memory. they wont work.
Advantages:
1. When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted in phone. Therefore linked applications are not affected and can be run without problems even when you have access through pc to sdcard.
2. You can use this app to uninstall system apps, move user apps to system apps or system apps to user apps.
3. You can integrate new updates of system apps which will be stored in internal memory to system apps. But please note: You should free the app first and then move them to/from system always for safety of apps so that they wont give FC. If some apps did gave FC after moving please restart the phone.
4. You can use clear cache, dalvik-cache, 2nd partition options. They wont harm your apps, they will remove only unwanted files.
Troubleshooting / Error occurance chances:
Question : When I click on "Move to SD card", I see a progress bar for 2-3 seconds and then:
pkg:/data/app/com.mobisystems.editor.office_registrered-1.apk Failure
[INSTALL_FAILED_INSUFFICIENT_STORAGE]
Answer : Your problem is a simple one.. your internal memory is low..
What link2sd actually does is.. first it moves the files to internal memory and then it sends to 2nd partition.. so you are having issues because.. say the apk file is 20 MB.. and your internal memory is around 20/less MB free.. So, it will give that error even if the second partition is totally empty..
For a work around to this.. you can make backup from titanium or just backup with any app.. then uninstall some apps.. then move that big app.. then reinstall these..
Hope your doubts are solved.. Enjoy the awesome app!
Apps Original thread link and the credit goes to RD bakpinar. So do thank him for this awesome app. You can also donate the dev by visiting his original thread.
CLICK HERE TO GO TO FIRST POST
Detailed steps to install Stock rom/Firmware through ODIN
Difficulty --> **
NOTE: Please dont install/flash FIRMWARE of OTHER DEVICES for your phones! through odin! Make double check before downloading whether its the right firmware for your phone!
Visit the threads respective to your devices to see the latest available firmware.. Links given below.
Samsung Galaxy Y --> [Stock][ROM][Odin] FIRMWARE THREAD BY DOKY73
Samsung Galaxy Y DUOS--> [Stock][ROM][Odin] FIRMWARE THREAD BY MANORANJAN2050
Samsung Galaxy Y PRO --> [Stock][ROM][Odin] FIRMWARE THREAD BY GianniDPC
Samsung Galaxy Y PRO DUOS --> [Stock][ROM][Odin] FIRMWARE THREAD BY MANORANJAN2050
To check the current version your mobile has.. Type this code in Dialer Tab which is where you type phone numbers to call..
Code:
*#*#1234#*#*
and check EX. PHONE: S6102DDLG1. See whether it is the latest by visiting samfirmware.com site and type your mobile no. for ex. 5360 in search box in right side of that site page and see whether any new update has come.
PREPARATION:
Switch on PC to windows OS and Login to your account. Make sure your device driver is already installed and your device got detected.. otherwise install kies software which will install drivers too.. Get kies from This LINK
Now connect your device to PC using USB Cable..
Open ODIN software from extracting the file you downloaded from using any of these applications like IZarc/ 7ZIP/ Winzip/ Winrar..
Note:
If you did above instruction and still device not detected? Then do this..
Unplug the usb cable..
Restart both PC and phone..
Then let the PC log in.. and give 5 mins time to it to load everything..
Then connect usb cable to phone and pc..
Open task manager in PC using CTRL+ALT+DELETE..
end process of adb.exe if its existing and kies too... do this end process only once..
Now open odin..
Instructions to install this through Odin:1. Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)... select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
2. Now when screen gets black.. immediately press and hold volume down+home button+power button..
you will see a page saying "Warning"
A custom OS can cause critical problems in your phone and installed applications.. and it will say some more in next paragraph..
Dont worry about it.. Now press "Volume up" to continue to odin mode..
3.you will see ODIN MODE written on top of screen in red..
Now make sure you are connected to your pc through usb cable and pc is logged in and open odin file..
4. Note: In Odin you will see a yellow/blue color in one box below "ID:COM" section.. If you are not seeing yellow/blue box restart your mobile and do same process from step 2. also restart your pc if its still not showing yellow. If it is showing then good.
5. Now select "PDA" button under "Files [Download]" section.. select "PDA_S****_(your firmware version no.).tar.md5" file
Now select "PHONE" button below "PDA" button in "Files [Download]" section.. select "MODEM_S****_(your firmware version no.).tar.md5" file
Now select "CSC" button below "PHONE" button in "Files [Download]" section.. select "CSC_S****_(your firmware version no.).tar.md5" file
Note: **** --> Your device model number. 5360 --> Samsung Galaxy Y, 6102 --> Samsung Galaxy Y Duos, 5512 --> Samsung Galaxy Y Pro Duos, 5510 --> Samsung Galaxy Y Pro.
6. Now remember!! Only "Auto Reboot" "F. Reset Time" options should be selected..
PDA, PHONE, MODEM also should be selected..
7. Now you are ready to flash through odin.. Just press "Start" button.. and wait around 10 minutes until odin finishes and the "yellow" box should show green... It will usually finish within 52 seconds to be precise..
8. Now your phone will reboot. If it starts showing Samsung logo again after few minutes.. Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)...and select "wipe data/factory" and select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
9. Now enjoy your brand new stock rom.. Hope this helps you!!NOTE: IF YOU CANT GO TO ODIN/DOWNLOAD MODE.. YOU NEED AN USB JIG to force phone to Odin mode automatically.. [REF] BORROW A USB JIG NEAR YOU..
CLICK HERE TO GO TO FIRST POST
ROM installations instructions [IN GENERAL]
Difficulty --> *
OK.. so I assume you have latest firmware.. Because its always good to have latest firmware update to avoid unnecessary problems as usually updates will have bug fixes and stability improvements.. If not, then First follow the guide I have given in this thread to install the firmware update if you are not on latest version..
OK, now that we have latest firmware update installed, lets proceed to ROM installation process!
* If you dont have these files Download and keep these files in sdcard (outside all folders / root of sdcard)..
1. Rom.zip file.. link is provided in first page of the ROM thread..
2. CWM file..
Now go to stock recovery by doing this..
Restart your mobile by holding three buttons...
Volume up+home button+power button..
Now when you see Samsung logo release the buttons..
After few seconds you will see 4 options written in red text..
Which is stock recovery (Android system recovery)...
* Select 2nd option in there.. "apply update from sdcard"
* Select "CWM.zip" file u have..
* In cwm(clockworkmod) which is with yellow text..
* Now go to backup and restore option.. make a backup first.. you need to have atleast 250-400 MB of free space in sdcard to do backup...if you dont care about your data/contacts/messages currently existing in phone then no need to make backup.
* Select "wipe data / reset" and then "wipe cache Partition"..
* select "install zip from sd"
* Select "Choose zip from sdca" first option now..
* Scroll down.. and select rom.zip file..
* Then select yes option.. and wait for few minutes for it to finish.. then come bak to previous screen using power button..
* Now select "reboot system now"
* Good, Now you have successfully installed the rom.. First boot takes time.. So wait till atleast 5-10 mins.. It will vibrate onec and then it will boot to your home screen.. This guide is in general. But usually all roms have installation guide..NOTE: THIS IS A GENERAL METHOD.. SHOULD WORK FOR MOST OF THE ROMS.. BUT IF THERE WAS ANY PROBLEM LET ME KNOW.. I WILL EXCLUDE IT FROM THIS GUIDE.. IF YOU CANT UNDERSTAND INSTRUCTIONS IN ROM THREADS THEN ONLY TRY THIS.. I HAVE WRITTEN THIS ASSUMING YOU ARE ON STOCK KERNEL/ YOUR KERNEL DOESNT HAVE CWM INBUILT. If it has.. then ignore stock recovery instructions mentioned in above instructions.. and directly start from CWM instructions..
CLICK HERE TO GO TO FIRST POST
Kernel installations instructions [IN GENERAL]
INSTALLATION PROCEDURE FOR KERNELS THROUGH CWM METHOD:Difficulty --> *
* First Download all the files required [from the kernel thread first page of whichever one you want to install]
* Copy these files inside SDCard.. Kernel.zip (kernel), CWM.zip (ClockWorkMod Recovery tool)
Note: Don't keep these files inside any "FOLDERS".. Just copy it to SDCard root (parent) folder (Outside of all folders)..
* Switch off your mobile.
After a small vibration (switch off confirmation) PRESS and HOLD 3 BUTTONS (VOLUME UP+HOME BUTTON+POWER BUTTON)
when samsung galaxy logo appears, release the 3 pressed keys..
* After few seconds.. You will see Android system recovery (red text with 4 options lines)..
Select "apply update from sdcard"
Note: (Volume up+down for "scrolling" through options or selection of files, home button for "select" any option.. in CWM only: power button for "back" option)
Then Select "CWM.zip".
* ClockworkMod Recovery v5.0.2.6 is loaded now.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Scroll and Select "Kernel.zip" and select "Yes"
Wait till the menu appears again.. Now Go back
* Select "Reboot system now" and you have successfully installed Kernel.INSTALLATION PROCEDURE FOR KERNELS THROUGH ODIN METHOD:Difficulty --> **
* First Download all the files required [from the kernel thread first page of whichever one you want to install]
* Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)... select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
* Now when screen gets black.. immediately press and hold volume down+home button+power button..
you will see a page saying "Warning"
A custom OS can cause critical problems in your phone and installed applications.. and it will say some more in next paragraph..
Dont worry about it.. Now press "Volume up" to continue to odin mode..
* you will see ODIN MODE written on top of screen in red..
Now make sure you are connected to your pc through usb cable and pc is logged in and open odin file..
*NOTE: In Odin you will see a yellow/blue color in one box below "ID:COM" section.. If you are not seeing yellow/blue restart your mobile and do same process from step 2. also restart your pc if its still not showing yellow. If it is showing then good.
* Now select "PDA" button under "Files [Download]" section.. A new window to browse files will get opened.. Locate the file boot.tar/boot.tar.md5 file you want to install.. select "boot.tar.md5"/"boot.tar" file..
* Now remember!! Only "PDA" "Auto Reboot" "F. Reset Time" options should be selected..
* Now you are ready to flash through odin.. Just press "Start" button.. and wait around 1 minute until odin finishes and the "yellow" box should show green... It will usually finish within 15 seconds to be precise..
* Now enjoy your brand new stock kernel.. Hope this helps you!!INSTALLATION PROCEDURE FOR KERNELS THROUGH KERNEL FLASHER TOOL[MAI77 METHOD] IN CWM:Difficulty --> *
* First Download all the files required ["boot.img" from the kernel thread first page of whichever one you want to install] and kernel flasher tool
* Copy these files inside SDCard.. boot.img (kernel), KernelUpdate.zip (Kernel Installer tool), CWM.zip (CLOCKWORKMOD)
Note: Don't keep these files inside any "FOLDERS".. Just copy it to SDCard root (parent) folder (Outside of all folders)..
* Switch off your mobile.
After a small vibration (switch off confirmation) PRESS and HOLD 3 BUTTONS (VOLUME UP+HOME BUTTON+POWER BUTTON)
when samsung galaxy logo appears, release the 3 pressed keys..
* After few seconds.. You will see Android system recovery (red text with 4 options lines)..
Select "apply update from sdcard"
Note: (Volume up+down for "scrolling" through options or selection of files, home button for "select" any option.. in CWM only: power button for "back" option)
Then Select "CWM.zip".
* ClockworkMod Recovery v5.0.2.6 is loaded now.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Scroll and Select "KernelUpdate.zip" and select "Yes"
Wait till the menu appears again.. Now Go back
* Select "Reboot system now" and you have successfully installed Kernel.NOTE: THIS IS A GENERAL METHOD.. SHOULD WORK FOR MOST OF THE KERNELS.. BUT IF THERE WAS ANY PROBLEM LET ME KNOW.. I WILL EXCLUDE IT FROM THIS GUIDE.. IF YOU CANT UNDERSTAND INSTRUCTIONS IN KERNEL THREADS THEN ONLY TRY THIS.. YOU CAN CHOOSE TO USE ANY OF 3 INSTRUCTIONS TO INSTALL.. I HAVE WRITTEN THIS ASSUMING YOU ARE ON STOCK KERNEL/ YOUR KERNEL DOESNT HAVE CWM INBUILT. If it has.. then ignore stock recovery instructions mentioned in above instructions.. and directly start from CWM instructions..
CLICK HERE TO GO TO FIRST POST
How to deodex a stock rom in easy way using DSIXDA Kitchen
SPECIAL Thanks to dsixda Recognized Developer / Retired Senior Moderator who has made an all in one ROM kitchen. So thanks to him there are many custom roms are there in xda.
Difficulty --> **** IF YOU ARE NEW TO PC & ANDROID. This is not for you. If you are good with either one then you can try this.
PREPARATIONS:I Recommend you to use linux if you have it.
Kitchen by Dsixda [KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
You need to have java installed in system to use the kitchen. All the steps for how to setup in windows/linux/mac has been explained well by dsixda in thread link. So i am not going to explain it here again. I assume your kitchen is set up and you are ready to work.
Make a backup in cwm and transfer the system.rfs.tar or system.ext4.tar file and boot.img file inside /sdcard/clockworkmod/backup/"dateofbackup"/ into PC.
Now go to the "/dsixda-Android-Kitchen/" folder and you should see these in that folder:
3 files & 3 folders it should contain:
- menu(file)
- Readme(file)
- .gitignore(file)
- original_update(folder)
- tools(folder)
- scripts(folder)
For Windows users--> Now open command prompt (If you installed Cygwin, then click on the Cygwin shortcut on your desktop to start it) and make sure you get to the path of that folder.. Ex. if folder is in c:\cygwin\home\"username"\dsixda-Android-Kitchen.. Then type this in command prompt..
Code:
cd dsixda-Android-Kitchen
Note: the capital letters should be in capital only when you type it... Note: Dont use space in folder names as cygwin wont work properly with space in folder names.
Or For Linux Users--> Now open terminal(Use CTRL+ALT+T). and make sure you get to the path of that folder.. Ex. if folder is in /home/"username"/Desktop/dsixda-Android-Kitchen.. Then you will be at /home/"username"/ . So type this in terminal.
Code:
cd Desktop/dsixda-Android-Kitchen
Note: the capital letters should be in capital only when you type it.
Now find that system.rfs.tar or system.ext4.tar file and boot.img file and paste it inside original_update folder. You will also find a file "put_rom_here_" Please ignore that file. Its just to tell you he has created that file.
Ok.. Now that you are at the right path.. just type ./menu in terminal or command prompt. From now on i am just going to say type this. It means you should type that and press "enter" to execute the command. If a menu didnt appear then type
Code:
pwd
You should see in which directory you are currently in. Try to get to the folder where kitchen folder is. Or follow steps again to get to there.
Now then, you should see this menu:
Code:
============================================================
Android Kitchen 0.214 - by dsixda (xda-developers.com)
============================================================
> MAIN MENU
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Zipalign all *.apk files to optimize RAM usage
6 - Change wipe status of ROM
7 - Change name of ROM
8 - Show working folder information
0 - ADVANCED OPTIONS
00 - LEGACY OPTIONS (old and rarely used)
99 - Build ROM from working folder
u - Kitchen Info/Update/Donate
x - Exit
Enter option:
Enter option: 1
Press "Enter"
[CODE}Available ROMs:
(1) system.rfs.tar
Enter selection number (default=1, cancel=0, r=refresh):1[/CODE]
It will ask you this:
Code:
The new working folder will be named WORKING_111212_132324
Change the name (y/n)? (default: n):y
Give a name if you want to identify it easily next time.. for ex. i gave this "Enter a new name (using this prefix): WORKING_DDLJ1" as it is from DDLJ1 firmware update.. you can choose not to give name.
Now it will ask this:
Code:
Would you like to view this ROM's info (y/n)? (default: y):y
Give y as yes as i gave.
It would appear like this if it is stock roms backup:
Code:
Working folder information
Android OS version : 2.3.6
Device : GT-S6102
Model : GT-S6102
ROM Name : GINGERBREAD.DDLJ1
CSC version : S6102ODDLJ1
Rooted (Superuser app + su) : NO
Rooted (unsecured boot.img) : UNKNOWN
BusyBox installed : NO
BusyBox run-parts support : UNKNOWN
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
Press Enter to continue
Now press "Enter" to continue.
Setting up working directory complete.. You can close it anytime if you want when you are at main screen just type x and press "Enter". You can open it again and continue without making the above steps again..
Enter option:0 in main menu for "Advanced options"
Enter option:11
It will show like this:
Code:
NOTE: Reversing the de-odexing process by getting back the odex
files ('re-odexing') is not supported in the kitchen and would
be impossible to implement.
----------------------------------------------------------------
Found 23 *.odex files in system/framework
Found 110 *.odex files in system/app
Enter a choice:
bb = Back up both folders (do first!)
v = Set Android OS version (Current API level = 10)
IMPORTANT: Ensure you set the correct API level
f = Deodex /system/framework
a = Deodex /system/app
b = Deodex both folders (recommended)
s = Deodex a single file
x = Exit
?
Now type bb and press enter. (For safety, backup apks.. you can skip it if you want) Press "Enter" to continue.
Now type v and
Code:
Change the current API level (y/n)? (default: n):y
Please enter the new level number (currently: 15): 10
Press "Enter to continue.
Now type b to deodex your rom. Press "Enter" when this is asked,
Code:
Enable logging to file (y/n)? (default: y):
It will take some time depending upon your computer configuration. So take a small nap It takes 20 minutes in mine usually.
At the end if its successful.. you should see this:
Code:
Finished system/app
A summary of the deodexing has been logged in deodex_111212_133710.log
0 *.odex files remain in system/app
0 *.odex files remain in system/framework
Press Enter to continue
Now press "Enter" to get back to "Advanced options"
Now to make this as cwm flashable zip.. Then type 99 and press "Enter"
[CODE}Select a build option:
Number (default: 1):1
Would you like to optimize the APK files by zipaligning them (y/n)? (default: y):y
Use updater-script in ROM's ZIP file (y/n)? (default: y):y [/CODE]
Now it will show this:
Code:
An updater-script has been created under META-INF/com/google/android of
your working folder. Please review it and make any necessary changes. An
update-binary has also been added.
DO NOT delete any of the files under META-INF/com/google/android.
Proceed with the change (y/n)?
y = Proceed; updater-script and update-binary will be used in the ZIP
file; update-script will remain in working folder.
n = Cancel; updater-script and update-binary will be deleted and not
used.
? (default: y):
Now go to that "META-INF/com/google/android." folder.. And replace the "updater-script" with the file i have given in the attachment to this post. rename the "updater-script.txt" file i have given to "updater-script" and delete "update-script" file. Now after replacing the file type y in menu.
It will ask this:
Code:
It is recommended that you sign your ROM.
Sign it (y/n)? (default: y): y
The new ROM will be named GT-S6102_signed_111212_141640.zip
Change the name (y/n)? (default: n):y
and type new file name whatever you want and press enter
You will find the zip file inside OUTPUT_ZIP/"given name".zip
Now its ready to flash the zip file in CWM.
I will write about other options if any users/readers ask me to write it.. otherwise i may update it when i feel there is a need for that.
CLICK HERE TO GO TO FIRST POST
Miscellaneous section
THREAD TITLES CONFUSING? ITS EXPLAINED HERE!Difficulty --> *
[TAGS] --. Use these below tags on your title, So that people can identify it more easily and what the thread is for! Add it in front of the thread for better recognition of thread purpose.
[SOLVED] - for issues that have been fixed or [Q] that have been answered THIS IS A MUST TAG FOR SOLVED THREADS! IT WILL SAVE LOTS OF TIME FOR EVERYONE! PLEASE DO THIS WITHOUT FAIL ALWAYS!
[Q] or [QUESTION] - All Questions thread should have this.
[REQ] - Requests topics for ROM ports, INFO, THEME, MOD, etc.
[TUTORIAL] or [GUIDE] or [HOWTO] - How to do or Guides for some task or info for users/devs.
[UITIL] or [UTILITY] or [TOOL] -- Any kit or tool made for some specific task.
[APP/ 2.2+] -- Apps thread which contains apps made / ported / modded. 2.2+ such tag is also a must which tells what android os or above versions are supported.
[ROM] / [KERNEL] -- As name suggests its a rom development or kernel development thread.
[DEV] -- Developers related thread
[MOD} -- Modded ROM/KERNEL/APP etc thread
[ROOT] or [CWM] -- Rooting thread or root related to thread. CWM related thread.
[AROMA] -- Tool used in recovery. This means the thread for any ROM ? KERNEL ? OTHER WORKS has aroma to flash it.
[TWEAK] -- Tweaks to boost system performance speed etc thread.
[WIP] -- Work In Progress thread.
Also, please do add tags to your threads. See "TAGS" button above your "Quick reply option".. Now see right end of that line to find "EDIT TAGS" button. Click on it and words there.
Code:
Thread owners and others should add relevant words there
So that the thread gets added to searches which have those words
WHY GIVE THANKS? THANKS METER EXPLAINED!Difficulty --> *
Why to Give Thanks?
Giving thanks is important. It lets people know that their work or answer is appreciated. It is a faster method of feedback than posting a reply like "Thanks for your answer!" You must have made one post to give thanks,
You get 8 thanks per day, and they renew after 24 hours or so. Each thanks is independent of the others, so if you give someone a thanks at 3, and then another at 4, those will renew at 3 and 4 the next day. If you run out of thanks, then save that page in a new tab and give thanks later when you have one available. (Or if you are an app user then you can thank them through the app "Just tap on the post and touch thanks button on pop up bar which appears") If you use them all every day you are doing it correctly.
Thanks Meter:
You will see that everyone here has a Thanks Meter above their avatar.
Here are the counts needed to get to the next bar.
1st bar - 26
2nd bar - 51
3rd bar - 101
4th bar - 201
bug here, never gets to 5 bars, probably 501 if fixed.
6th bar - 1001
7th bar - 2001
8th bar - 5001
9th bar - 8001
10th! - 10000+
Not that thanks are an indication of a user's status or stature on XDA. Thanks don't really count for anything other than as a potentially wildly inaccurate measure of a member's ability to answer your question correctly. Some of the most important people here have a lot fewer thanks than you might guess. But it is a nice gesture to hit thanks button to those who helped you as they are not gaining anything in return!
STARS, USER TITLES: JUNIOR, MEMBER, SENIOR MEMBER........? READ TO KNOW MORE!Difficulty --> *
0 to 29 posts - Junior Member
30 to 99 posts - Member
100 + posts - Senior Member
Here is what our Senior Moderator said,
juzz86 said:
There are Junior Members, Members, Senior Members first. These make up the vast majority of XDAs userbase.
Recognised Contributors are nominated by other users and/or Mods/Developers. They are recognised for their contributions which are not specifically Development, such as detailed guides, one-click utilities and other tools/mods.
Recognised Themers are also nominated by users/Mods/Developers, for their work themeing custom ROMs and providing standalone themes for flashing.
Recognised Developers are nominated and approved by the Developer Committee, for their work in Development whether it be ROMs, Root methods, bootloader unlocks etc.
Elite Recognised Developers are again assessed by the Developer Committee, and are deemed to have gone above-and-beyond in providing knowledge/hacks/tools/apps/ROMs for the XDA community.
Forum Moderators are appointed by the Moderator Committee, after submitting an application (see the 'sticky' at the top of this forum - currently applications are not open). They are the first-line of keeping the forums tidy, friendly and orderly.
Senior Moderators are the next step up the ladder, providing site-wide support for Forum Mods and looking after the nitty-gritty issues, as well as areas of XDA not policed by FSMs, such as the Marketplace.
Administrators are next. There are several Admins - each look after a specific part of XDA such as the Portal, the Members and the User Experience of XDA as a whole.
At the top is Mike Channon, who is overall Forum Administrator.
Other titles you may come across:
Moderator Committee - sits on the Mod Committee
Developer Committee - as above, but for Developer Committee
XDA Newswriter - publishes articles for the Portal (front page)
Retired xxxx - have since officially 'left' their XDA position
Hopefully that clears most of them up for you
Contrary to what a lot of people expect, the thanks-meter does not figure at all in determining a users tag.
Click to expand...
Click to collapse
Wondering what those stars below the thanks meter mean?
It means that they've donated money directly to XDA.
A star = €10 euro donation.
A star with 10 written within it = €100 euros, as it represents 10 individual stars.
XDA/TAPATALK APP IMAGE UPLOADING PROBLEMS?? Difficulty --> *
Use Imgur Mushroom app.. its available at play store..
Its app size is very small.. Its a great app for multiple pictute uploads at once..
Whatsmore u can configure prefix and suffix text in settings to add [img] and [/img]..
After uploadingthe pics, it will save all links with prefix and suffix code in clipboard. ready made for you to paste it in the desired post using the XDA/TAPATALK app..
So all u need to do is paste it in post.. very easy and handy.. How to do it? Instructions below!
open imgur mushroom app. Select button right side to upload button which has this "..." button.
now select "settings" in the newly opened pop up menu.
now scroll down and select "output type" in URL settings section.
select "URL to direct image"
select "prefix text" and add [img]
select "suffix text" and add [/img]
now go back and select "pick" button and choose your pics to upload. Alternatively you can multi select in a file browser and share them to this app to upload too! Hope this helps!
MAKE YOUR THREAD/POST NEAT BY USING BBCODE [Bulletin Board Codes]: Difficulty --> *
You see in many Threads and posts people using something to make it look cool / formatted to make it more readable?
And you wish to make your threads/posts the same way??
Then look at this link provided by XDA.. I know many wont know about this..
BBCODE EXPLAINED WITH EX. BY XDA.. CHECK THIS LINK
I will add other info that are not informed there soon..
BATTERY DRAIN?? READ THESE TIPS TO AVOID IT! Difficulty --> *
Are you using live wallpaper? it takes more battery!
Go to Settings-->Accounts and Sync-->Auto-sync option-->uncheck it to save more battery.
If you keep using 3g/wifi it will use more battery.. Use 3g only when u download something..
If you are using widgets, it does drain battery faster.. If you want your battery to last longer, remove them or keep it to minimum 1 or 2. I dont use any widgets.
You have to pay attention to your apps running in the background. Try "Quick system info pro" or "ES Task manager" or "some other apps which shows detailed info on processes running. Stop those processes.
If you are using too many notifications features types of apps it will drain battery as they run in the background all the time..
Keep the screen brightness to as low as possible and readable still. Brightness does takes battery a lot.
Playing games does drain battery faster.
If you have custom kernel, and keep minimum freq higher then it will drain faster too
When u sleep at night and wake up at morning how much battery u lose? I loose around 1 percent.. If its more than 2-10% may be your deep sleep feature is not working.. Check it with CPU SPY app available at play store.
[DUOS ONLY]Do you keep both sims alive? I switch off 1 in sim manager.. Do it if you don't need it all time..
Inspired by a.cid and mf2112 threads.
Enable Whatsapp *AUTO DOWNLOAD IMAGE OPTION* in new versions [TRICK] (2.9.**** versions and above)Difficulty --> *
If you have lost "Auto-download images" option.. Then you are not able to disable the auto download of images. So, to get back that option in Settings-->Chat Settings. You need to do these steps below:
Note: Make sure you have a working Whatsapp already before attempting this. That is you should have already passed the verification process etc and able to chat with others.
Step 1 : Make sure you have "Ticked" option "Unknown sources" under Settings-->Application Settings.
Step 2 : Download this old version Whatsapp and transfer it to click on the downloaded file. It will ask "Replace application"
Press "OK". Then, Press "Install" button. After install press "done".
Step 3 : Now, switch on "Airplane Mode" to "ON" by lidroid toggle or in Settings-->Wireless & network settings--> Flight mode "ON"
Step 4 : Go to Settings-->Date & Time.. Change date to any date/ November/ 2012. Now, open the Whatsapp.. You should see a old Whatsapp.
Inside Whatsapp, Go to settings-->Chat settings and now turn off "Auto-download mages" option by "unchecking" the tick box.
Step 5 : Now, install the new Whatsapp if you have a backup of the app and turn off "Airplane mode" and now you can also update from play store if you dont have a backup of latest version of Whatsapp.
Now open the new Whatsapp and see the option "Auto-download image" option.
{
"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"
}
CLICK HERE TO GO TO FIRST POST
Useful links to threads/guides section
NOTE: I am not adding any SGY forum threads here.. as we all can look into it easily.. I am adding only other forums thread links of XDA which are very useful to us. So please dont ask me to add SGY forum thread links here. And if you find any useful threads which are not similar to already mentioned thread.. Then PM me the link.. I will add it if its good. Thank you for reading!Thread Titles with links and info about it are below:
****XDA SITE RELATED THREADS****[All XDA Members] Requests to Moderators and Admins --> Rather than sending a PM to an individual Moderator, please see this thread in need of Moderator or Admin assistance. They will all be monitoring this thread, and someone will reply without much delay.
XDA Android App - Problems / Bugs / Feature Requests etc. --> Report any faults you find with XDA app in this thread. You can also ask for new features, but cannot promise they will ever be delivered.
SPAM Users --> Any user Spamming in forums / threads? If you feel yes, then do go to this thread and report the user. Please give direct link to the users profile/posts which were spam so that it will help moderators.
[HOW TO]Make The Most Of The XDA App --> This is for all of you who use the app instead of desktop, but may not know how to do certain things.
I Will Post Your Question In The Dev Thread If.. --> Newbies not able to post in dev thread? Some report you want to get it there? Then check this thread to do exactly that!
Help Your Threads Get More Search Hits with Better Titles and Thread Tags! --> I have noticed that many threads do not have thread tags so I think most users don't know about them. This only works with
the XDA website, not the XDA app. Please read this thread to know more about tags which is a very useful method to get your thread popular!
Time Frame/Tell your story here on xda![Archive] --> Where we could talk about our years here at XDA. Lets see who is the oldest and what we have given to this forums.
Share your sig code please --> Very helpful to make your Signature look neat. Read this thread to make your signature better or if you have cool signature then post there.****GENERAL INFO THREADS****[MOD][2.56] AROMA Installer :: 121004-031 :: Open Source --> The World's First ANDROID Touch And Customizable ROM/KERNEL/MODS Installer
List of devices: ARMv7, ARMv6, ARMv5 --> I found a really nice thread that will maybe, help some developers who need to port Roms or for another Reason.
[v6.13] Online Nandroid Backup / Nandroid Backup without re-booting
[HOW-TO] Set up SDK/ADB on Ubuntu 11.10 | 32 & 64 bits
[TUTORIAL]How to make your own Live Wallpaper
[Tutorial/How-To][GB] Make Your Own Custom Rom & Kernel (Last Updated 30/07/2012)****ROM RELATED/INFO THREADS****
ROM DEVELOPMENT THREADS:
[HOW TO] Beginners Guide to Android ROM Development
[Guide]Complete Android ROM development and essential tutorials ~~ By Nero Young ~~
[KITCHEN] Android Kitchen, v0.213 [Linux / Mac / Windows]
[Ultimate Guide][Part 10 released][12/11/2011]Android App Development - From Scratch
ROM MOD THREADS:
[UTILITY] Android Utility - [apktool|dex2jar|smali|more][Mac & Linux][Feb13, 2012]
[MOD][HOW-TO]To disable signature checks
[GUIDE] How to add TABS to Settings with swipe gesture... \m/
[GUIDE] ICS Style 'Settings.apk' - Make it yourself !! !!
[UTIL][Sept 2 2012] Apktool v1.5.0 - a tool for reverse engineering apk files
[IDE][M10] Virtuous Ten Studio - The next level of editing apps
[KITCHEN][01/22] UOT Kitchen (Ultimate Online Theme Kitchen) version 4.0
[MOD][15 Toggles] How to mod Lidroid framework
[APP][DEV] Update me [ROM MAKER] - 2.0.3 - PUSH NOTIFICATION - (updated 2012-09-13)****KERNEL RELATED/INFO THREADS****
KERNEL DEVELOPMENT THREADS:
[KITCHEN]Android Kernel Kitchen 0.2.3 (Linux / Windows)
[Tutorial] Building Your First Kernel
HOWTO: Compile your own kernel from source (WIP)
[Tutorial] How to compile a kernel module outside the kernel
KERNEL MOD THREADS:
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
[KERNEL MODULE] Extra modules pack v0.1.3 (feat. overclock) [OMAP4 kernel 3.0.8]****RARE/COOL APPS THREADS****[APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer!
[APP][DEV] ZipInstaller 2.4.2 for CWM-based + TWRP + 4EXT Recoveries
[APP][2.1+] Gidder - Git server for Android
[APP/5 NOV/2.2+]Turn screen off while MHL/HDMI mirroring WITH TOUCHPAD! [v1.96B11]
[APP][2.1+] FTP Server Ultimate - FTP, SFTP, FTPS server with multi-user, no-root
[App] WifiKill - disable internet for network hoggers (Android 4.x) [31/10/2012]
[App]Mediafire App for Android
[App][2.2+]LauncherWP8[6nov][v1.1.1]
[APP 2.2+] Android Tuner [BETA TESTING]
[APP]DroidSheep : ARP-Spoofing App for Android****MISCELLANEOUS THREADS****[TWEAKS][SCRIPTS] Collection of 'em all - build.prop; init.d; etc.
☠ [Add-on][Tweaks\\Mods]█ PIMP MY ROM █ v2.1.2 {Any Device // Any Rom}[AROMA][WIP] ☠
[Tool][Windows Only][Root] Android Reverse Tethering 2.30 --> surf on your phone using the ADSL of your PC.This work only for rooted users !
[ICON PACKS] mrFenyx's Icons - 8 packs, 800+ Icons, more to come
[Rooted][Guide]Wifi Reverse Tether - Windows and Ubuntu - Ad Hoc Networks CLICK HERE TO GO TO FIRST POST
Well, even though there are 2 kernel guides in our section.. Both are not complete.. So i thought of writing this.. a complete guide to make a kernel.
So, i'll keep updating this post as and when i get time to make it as good as possible..
Files Required:
You need to have Ubuntu or any other Linux distros.. But i recommend Ubuntu 11.10 32 bit as I'm using this version.
Kernel source from http://opensource.samsung.com . Search for 5360 and download "GT-S5360_GB_Opensource_Update3.zip"
Download Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/
Note: It should be Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2. Extract this file & you need to extract the file you got again to get "arm-2009q3" folder.
Download mkbootimg_src.zip from http://d-h.st/xnT
split_bootimg.pl is a perl script required to extract ramdisk from boot.img file. Or use dsixda or championswimmer's kitchen to extract it.
Get ncurses-5.9 lib if you want to work with menuconfig..Link
stock "boot.img" to extract ramdisk for your kernel.
Now that we have all the files required. Lets move on to next step of creating a Build Environment.
Build Environment Setup:
Make a folder. I'll call it "Kernel" folder here. You can name it whatever you want. Now, move the "arm-2009q3" folder inside this "kernel" folder. Extract mkbootimg_src.zip file and move "mkbootimg_src" folder inside "kernel" folder. Move "split_bootimg.pl" file under "kernel" folder too.
CLICK HERE TO GO TO FIRST POST
nice initiative but dont repeat any tuts which we already hav.. good luck!
hell_lock said:
nice initiative but dont repeat any tuts which we already hav.. good luck!
Click to expand...
Click to collapse
lol.. i know mate.. thats y i didnt write till today even though i wanted to write.. see the index page.. almost all are my own findings.. but whenever if i added from others.. then i will add credits as always..
do tell me / crrect me if i am wrong anywhere lol
nice guide...waiting for guide on building custom rom...
Sent from my GT-S5360 using xda app-developers app
anmolsharma1293 said:
nice guide...waiting for guide on building custom rom...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
My sign has it already..
Sent from my GT-S5360 using XDA
Hi, maybe you would like to incorporate my tool(AIOlog) in the retrieving logcat using computer as it works for Windows out of the box(provided that the driver is installed)
wcypierre said:
Hi, maybe you would like to incorporate my tool(AIOlog) in the retrieving logcat using computer as it works for Windows out of the box(provided that the driver is installed)
Click to expand...
Click to collapse
OK.. thanks for the heads up.. I will see.. I don't know about your tool yet.. so I have to see how it works.. and I still have to write about PC log too..
Thanks for the heads up..
Sent from the MUST have app!
nitubhaskar said:
OK.. thanks for the heads up.. I will see.. I don't know about your tool yet.. so I have to see how it works.. and I still have to write about PC log too..
Thanks for the heads up..
Sent from the MUST have app!
Click to expand...
Click to collapse
Basically for now its more or less the same as the ones in the market, but if you try the latest dev version, it has multiple device support(able to do logging even if there's more than one device, usually the logging would fail if there's more than one device) and many other features that are to be implemented
:good: :highfive: