Related
[NOTICE] THIS THREAD CONTAINS TWO GUIDES:
[POST #1] Fresh out of box Galaxy S 4G [SOLVED]
[POST #2] Heimdall One-Click For Dummies
[Note: You can use this guide where applicable - look for the bold section headers that pertain to the state of your device and go from there.]
--------------------
What I have on it fresh out of the box:
o To determine what you are currently running - Go to [App Drawer], [Settings], [About phone]:
-Model number: SGH-T959V
Firmware version: 2.2.1
Baseband version: T959VUVKD1
Kernel version: 2.6.32.9
Build number: FROYO.VUVKD1
o If your phone information is different than above (i.e. KB5) - this guide will work as long as Kies mini will recognize your phone. Kies mini WILL NOT recognize ROOTED devices.--------------------
What can I do:
-Upgrade to GB 2.3.6
-Back up efs Folder (Important!)
-Root
-Flash Custom Kernel (to obtain CWM)
-Flash Custom Rom
-Flash Custom Tweaks (cautiously as most custom ROMs have tweaks built in)
-Flash Custom MOD's.
--------------------
What should I know first:
-What is a ROM: Literally it stands for Read Only Memory, in this case referring to the phone's internal memory where your firmware/apps are stored. It is what you see and use when you are on your phone.
-What is a Kernel: The bridge between applications and actual data processing done at the hardware level. The kernel helps the ROM talk to the Hardware.
-What is the efs file: “This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more.” (from XDA article)
-What is rooting: Allows you to make changes to your Android system, as well as enable you to use features that are otherwise locked away. (from Samsung Galaxy S 4G Wiki)
-ClockworkMod / CWM: A custom recovery allowing you to perform several advanced recovery, restoration, installation and maintenance operations that aren’t possible with stock recovery. (from here)
> > You can find more applicable definitions here < <.--------------------
Going from Stock Froyo (Firmware version: 2.2.1) to Stock GB (Firmware version: 2.3.6):
NOTES
* * I chose to go from Stock Froyo to Stock GB using Kies mini. This gives me the GB Bootloaders that I need to make it easier to flash a custom kernel and custom ROM’s.
* * Having GB already on the phone allows us to download SGS Kernel Flasher (must be rooted to use) from the app market to flash a custom kernel that will give me CWM5 and Voodoo Lagfix.
* * Also if anything screws up (i.e. IMEI), I can just take my phone back to where I bought it and get another one as this has happened to many… and fixes for it are not clear and work randomly but not for all. And unfortunately peoples phones have screwed up updating the way T-Mobile and Samsung tell you to update.o How to check your IMEI:
-Go to [App Drawer], [Settings], [About phone], [Status].
-Towards the bottom you will see [IMEI].
o Let's get started:
-Download Kies mini if you do not already have it. When you follow this link you will see two tabs - 'Manuals' and 'Software ' - click [Software] and download.
-Make sure your phone is charged.
-Double check that USB Debugging is not enabled. Go to [Settings] > [Applications] > [Development] and UN-Check [USB debugging].
-Start Kies mini on the computer.
-Make sure phone is not connected to computer yet.
-In USB Settings on my phone I select [Kies (Firmware update)] if it is not set to ask every time.
-Plugged in phone, let device drivers install on computer. You will see a notification on your computer when complete.
-Then Kies mini will recognize the phone.
-Hit [upgrade] and wait.
-Phone will eventually reboot. Check your IMEI.
--------------------
I am on Stock GB (Firmware version: 2.3.6) now what:
NOTES
* * Some have learned the hard way the importance of making a back up of the efs folder on your phone. The efs folder contains important information about your phone and in the event any of the files in the folder are corrupted there is NO clear and concrete fix without a back up!
* * I use Super Managero Now let's back up our efs folder:
-Open Super Manager on your phone and go into [File Manager].
-Select [Back up level folder] twice.
-Scroll down and look for your folder called [efs].
-Long press the folder and select [copy].
-Now look for [sdcard] and select.
-Now select the clipboard (or press menu, then paste) to paste to your sdcard.
-Now copy over to your computer for safe keeping.
o It is time to Root [CREDIT and THANKS TO SHORTFUSE FOR SUPERONECLICK]:
-Download the current version of SuperOneClick (as of 05/02/12 is SuperOneClick v2.3.3).
-Extract the contents of the .zip where you can find it on your computer.
-Open the SuperOneClick folder you just extracted.
-Make sure phone is in Debugging Mode. Go to [Settings] > [Applications] > [Development] and check [USB debugging].
-Connect your phone to your computer.
-Open SuperOneClick.exe. You DO NOT need to change any settings!
-Either [Donate Now] or select [Donate Later].
-Click [Root] and wait and keep waiting.
-Ahhh, Rooted!
--------------------
I am on Stock GB (Firmware version: 2.3.6), I have an efs backup and rooted now what:
NOTES
* * I need a custom kernel to give me CWM and Voodoo Lagfix.
* * The purpose of the custom kernel is to give us CWM to flash a Custom ROM. When we flash the Custom ROM - the Custom ROM will overwrite the kernel we flash now with the kernel included with the ROM.
* * Do NOT extract the contents of .zip files. When flashing - we flash the .zip.o Let's get started:
-Go to market, download and install SGS Kernel Flasher
-Download your choice of kernel from the Galaxy S 4G Android Development section to the root of your sdcard. Links provided below.
o Kernel Recommendations as of 05/02/12:
-Basic with a Twist SGS4G KJ6 1.1 rc1 (thanks to AntonX )
-Bhundven's Subtly Modified Stock with CWM5 + Voodoo Lagfix (thanks to bhundven)
o Let's flash the kernel:
-Open the SGS Kernel Flasher app.
-First select [backup kernel].
-When it if finished you will still be on the same screen and it will see a green vertical bar at the bottom of the screen next to - Backed up as.....
-Now select [choose kernel] and a file manager will appear.
-Select [parent directory] and you will be on the root of your sdcard.
-Navigate to the bottom and find the kernel .zip file you copied over.
-Once selected you will be back at the main screen of SGS Kernel Flasher.
-Select [flash kernel].
-The kernel will flash and your phone will reboot.
-You will hear Linda speaking on the Galaxy S 4G boot screen (only if this is your first time flashing a custom kernel).
-Wait and wait some more! She will keep talking to you!
-Eventually the phone will reboot.
--------------------
I am on Stock GB (Firmware version: 2.3.6), I have an efs backup, Rooted and have custom kernel with CWM now what:
NOTES
* * Now it is time for the Custom ROM!
* * Do NOT extract the contents of .zip files. When flashing - we flash the .zip.o Let's get started:
-To make it easy for you to access CWM Recovery without having to do the button combination - You can download Quick Boot (Reboot) here: QuickBoot.apk (link is courtesy of FB)
o How to navigate in CWM Recovery - TWO Methods:
-Using Side Buttons:
-To navigate up and down - use the Volume up and down buttons.
-To select - use the power button.
-Using Soft Keys:
-To navigate down - use the [menu] soft key (first soft key).
-To navigate up - use the [home] soft key (second soft key).
-To Go Back - use the [back] soft key (third soft key).
-To select an option - use the [search] soft key (fourth soft key).
o First things First - Nandroid Back Up:
-In CWM Recovery - Navigate down to [backup and restore] and select.
-Then select [backup]. This will take a bit so wait until it is finished.
-Now you have a Nandroid backup (which also gives you another backup of your efs folder) and you will be back at the main screen of CWM Recovery.
NOTES
* * If you decide to try a different ROM other than the suggested ROM's below - please be aware there are Gingerbread-based ROM's and FROYO-based ROM's. At this point in the guide - you MUST select a Gingerbread-based ROM to flash.o Custom Gingerbread ROM Recommendations as of 05/02/12:
-Follow install directions labeled 'ROM's WITH SGS4G CWM ROM Installer'
-Valhalla - BlackEdition (thanks to RaverX3X) --- last update 02/08/2012
-Valhalla Black FB Edition (Build 3) (thanks to RaverX3X & FB) --- last update 04/29/2012
-Unnamed ROM (thanks to RaverX3X) --- last update 03/22/2012
-SCOMv4.4 and Floyd Edition (thanks to erikmm) --- last update 04/28/2012
-icbinb 2.3.7_v2 (thanks to dsexton702) --- last update 02/25/2012
-Follow install directions labeled 'ROM's WITHOUT SGS4G CWM ROM Installer'
-Valhalla Final (thanks to Whitehawkx) --- last update 12/12/2011
-Octane-V3.0 XPLOD NO CIQ EDITION (thanks to RaverX3X) --- last update 12/10/2011
o Let's get started:
-Download your choice GB ROM from your computer. Make sure the downloaded zip looks right (mainly size – I have had to try downloading two or three times to get the full zip for some reason).
-Copy [<< Name of Custom ROM you chose here >>.zip] to the root of your sdcard.
-Open [Quick Boot (Reboot)] and select [Recovery].
-If it is the first time using Quick Boot (Reboot) - you will need to allow superuser permission if this is the first time using the app.
-Your phone will reboot and you will be in CWM Recovery.
o Now let's finally flash the Custom ROM:
NOTES
* *A note before flashing - The steps to actually flashing the Custom ROM's change as new methods become available. As an example - SGS4G CWM ROM Installer by FB is now used when flashing newer ROM's.
* *FB's SGS4G CWM ROM Installer gives us a nice GUI (graphical user interface) when flashing ROM's. Thank you FB!
* *I will do my best to keep this guide up-to-date with the correct steps to flash the Custom ROM's recommended in this post - however if you notice something has changed - please PM me and let me know so I can up the guide!
* * [DIRECTIONS] ROM's WITH SGS4G CWM ROM Installer * *
-After the Nandroid Backup you should be on the main screen of CWM Recovery - navigate down to [install zip from sdcard] and select.
-Then select [choose zip from sdcard].
-Navigate down towards the bottom of the list that appears and you should see [- << Name of ROM you want to install >>.zip]. Select it.
-Navigate down to [Yes - Install << Name of ROM you want to install >>.zip] (sometimes the name of the ROM will be cut off due to the length of the name).
-Select the ROM and wait. The SGS4G CWM ROM Installer will appear and guide you from here.
-Being new to flashing - select [Quick] install when prompted.
-When SGS4G CWM ROM Installer is finished - your phone should reboot into your NEW CUSTOM ROM!
-In the event your phone does not automatically restart after SGS4G CWM ROM Installer is finished - select [***** Go Back *****] until you are back to the main CWM Recovery screen and select [reboot system now].
-Go to App Drawer, [Settings], [About phone], [Status] and check your [IMEI].
* * [DIRECTIONS] ROM's WITHOUT SGS4G CWM ROM Installer * *
-After the Nandroid Backup you should be on the main screen of CWM Recovery - navigate down to [install zip from sdcard] and select.
-Then select [choose zip from sdcard].
-Navigate down towards the bottom of the list that appears and you should see [- << Name of ROM you want to install >>.zip]. Select it.
-Navigate down to [Yes - Install << Name of ROM you want to install >>.zip] (sometimes the name of the ROM will be cut off due to the length of the name).
-Select the ROM and wait.
-When installation is finished - select [***** Go Back *****] until you are back to the main CWM Recovery screen and select [reboot system now]
-Once rebooted into your new ROM - let you phone sit for 10 minutes to allow time for your caches to build.
-After 10 minutes - long press the power button and select [Recovery].
-In CWM Recovery - navigate to [wipe data/factory reset] and select.
-Then navigate to [Yes --delete all user data]
-When factory reset is complete - reboot and ENJOY!
NOTES
* * Most Custom ROM's will be de-bloated - meaning a lot of the stock apps you may or may not be accustomed to are removed.
* * If you would like to re-install a stock app that is not in the Custom ROM you just flashed - Follow this link - Stock GB 2.3.6 APK Repository, download the APK you want to install and follow the directions in the first post of that thread.--------------------
[TWEAKS] I am on Stock GB (Firmware version: 2.3.6), I have an efs backup, rooted, have Custom Kernel with CWM and have a Custom ROM now what:NOTES
* * Now you can flash tweaks if you so desire!
* * Do NOT extract the contents of .zip files. When flashing - we flash the .zip.
* * Take note - Most Custom ROM's have tweaks built. As an example - icbinb 2.3.7_v2 has Universal Adrenaline Shotv14-1 cache scroll tweak built in. Read the first post of the Custom ROM thread you choose to determine what tweaks are built into the ROM.
* * Flashing more than one Tweak does not give the benefits of both Tweaks. The Tweaks are generally written to overwrite most of the settings that may already be on the phone. So - Pick a tweak and try it for a couple of days. And if you would like to try a different tweak go for it.
* * If you are on icbinb 2.3.7_v2 - To make it easy for you to access CWM Recovery without having to do the button combination - You can download Quick Boot (Reboot) here: QuickBoot.apk (link is courtesy of FB).
* * If you are on Valhalla - BlackEdition - You are now able to access CWM Recovery by holding down the power button. [Phone options] will open and you can select [Recovery] to easily access CWM Recovery.o Custom Tweak Options as of 03/02/12:
-Universal Adrenaline Shotv14-1 cache scroll tweak (thanks to dsexton702)
-A.S shot v15(beta) (thanks to dsexton702)
-Lightning Zap (thanks to thomas.raines) -- now using SGS ROM Installer
-ThunderBolt! v2.6.1 (thanks to pikachu01)
o Let's get started:
-Download the Tweak you have decided to try.
-Copy [<< Name of tweak you chose here >>.zip] to the root of your sdcard.
-Reboot into Recovery (refer to notes above depending on which Custom ROM you are using)
-Scroll down to [install zip from sdcard] using the methods previously given, then select [choose zip from scard].
-Go to bottom and find the name of the tweak you copied over and select it.
-Scroll down and select [Yes - Install << Name of tweak you chose here >>.zip].
-White letters will scroll and eventually say [Install from sdcard complete].
-Lightning Zap will now start SGS ROM Installer. Follow prompts. Select [Quick] Install.
-When finished select [*****Go Back*****].
-Then select [reboot system now].
-Let your phone sit for 10 minutes before using - most tweaks wipe your Dalvik Cache, which in turn, will rebuild itself properly by letting your phone sit. You may experience minor problems, lags, etc if you skip this step.
NOTES
* * To see the full benefits of most Tweaks - You need to give the Tweaks a day or two to settle in - or 'Soak In' as you will hear in the forum.--------------------
[MODS] I am on Stock GB (Firmware version: 2.3.6), I have an efs backup, rooted, have Custom Kernel with CWM and have a Custom ROM now what:NOTES
* * Now you can flash MOD's if you so desire!
* * Do NOT extract the contents of .zip files. When flashing - we flash the .zip.
* * If you are on icbinb 2.3.7_v2 - To make it easy for you to access CWM Recovery without having to do the button combination - You can download Quick Boot (Reboot) here: QuickBoot.apk (link is courtesy of FB)
* * If you are on Valhalla - BlackEdition - You are now able to access CWM Recovery by holding down the power button. [Phone options] will open and you can select [Recovery] to easily access CWM Recovery.o Custom MOD Options as of 03/02/12:
-Camera MOD's - These need to be flashed in the order given below (thanks to dsexton702)
-FLASH FIRST - Camera-Mod (go to the bottom of the post and download Camera-Mod.zip)
-FLASH SECOND - Bravia engine for Better picture taking and video recording
-Scrolling Cache Tweak (go to the bottom of the post and download Scrolling-Cache-Tweak.zip) (thanks to dsexton702)
o Let's get started:
-Download the MOD you have decided to try.
-Copy [<< Name of MOD you chose here >>.zip] to the root of your sdcard.
-Reboot into Recovery (refer to notes above depending on which Custom ROM you are using)
-Scroll down to [install zip from sdcard] using the methods previously given, then select [choose zip from scard].
-Go to bottom and find the name of the MOD you copied over and select it.
-Scroll down and select [Yes - Install << Name of MOD you chose here >>.zip].
-White letters will scroll and eventually say Install from sdcard complete.
-When finished select [*****Go Back*****].
-Then select [reboot system now].
-Let your phone sit for 10 minutes before using - most tweaks wipe your Dalvik Cache, which in turn, will rebuild itself properly by letting your phone sit. You may experience minor problems, lags, etc if you skip this step.
THANKS bhundven FOR MAKING THE KJ6 HEIMDALL ONE-CLICK
AVAILABLE TO THE SGS4G COMMUNITY
- STEP BY STEP GUIDE FOR KJ6 HEIMDALL ONE-CLICK -
WITH BOOTLOADERS AND WITHOUT BOOTLOADERS
----------------------------------------------------------------
o Who should use this guide and do I need Bootloaders:
This guide can be used when wanting to upgrade your phone to Gingerbread from Froyo:
----> Follow Directions for Flashing WITH BOOTLOADERS
This guide can be used if you flashed a ROM made for a different model phone (i.e. Vibrant):
----> Follow Directions for Flashing WITH BOOTLOADERS
If you don't know what Froyo is or do not know what ROM you currently have - to be safe:
----> Follow Directions for Flashing WITH BOOTLOADERS
This Guide can be used after flashing a Custom Gingerbread ROM and wanting to return back to Stock Gingerbread ROM:
----> Follow Directions for Flashing WITHOUT BOOTLOADERS
This Guide can be used between flashing Custom Gingerbread ROM's to lesson probabilities of problems:
----> Follow Directions for Flashing WITHOUT BOOTLOADERS
----------------------------------------------------------------
START HERE - - WHETHER FLASHING WITH BOOTLOADERS OR WITHOUT BOOTLOADERS - - START HERE----------------------------------------------------------------
IMPORTANT NOTES BEFORE YOU BEGIN:
* * When using Heimdall or ODIN - Designate USB Ports on your computer for each flashing program. Have one USB Port that you only use Heimdall for. Have one USB Port you only use ODIN for. This does not mean you cannot use the designated USB Ports for other functions NOT related to your phone. This is only for flashing with Heimdall and ODIN.
* * Always use a USB Port that is directly connected to your computer - NO USB Hubs or add-on Ports.
* * If possible - Start with a USB Port you have never plugged your phone in to. By doing this you will reduce your probabilities of running into problems.
* * If you have used your phone on every USB Port and/or have no idea where all you have plugged your phone into or used ODIN or Heimdall with - Download [usbdeview-x32.zip] for 32-bit operating systems or [usbdeview-x64.zip] for 64-bit operating systems. Uninstall anything you see that has Samsung and Android related.----------------------------------------------------------------
o Let's get started:
Go to the following thread: [The T959V Heimdall One-Click Collection] <---- Link
Look for [Download T959VUVKJ6 Stock UVKJ6] - After flashing this download you will have Pure Stock KJ6 Gingerbread. Ideal if you need to return phone for warranty purposes.
Start the download, create a folder on your [C:\] Drive naming it [Android] and save [T959VUVKJ6_STOCK-UVKJ6-One-Click.jar] to [C:\Android].
While the file is downloading follow this link: [Verify Java Version] <---- Link
Click [Verify Java version].
{
"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"
}
Hopefully you will see the following:
If you do not - update to the latest version of Java.
Now you should have [T959VUVKJ6_STOCK-UVKJ6-One-Click.jar] saved on your computer at [C:\Android] and you should have the current version of Java installed on your computer.
----------------------------------------------------------------
o Time to flash:
Go to the newly created folder - [C:\Android] - where you saved [T959VUVKJ6_STOCK-UVKJ6-One-Click.jar].
You will see [T959VUVKJ6_STOCK-UVKJ6-One-Click.jar]. Inside the window - Hold down shift and right-click. In the menu that appears - select [Open command window here].
The Command Prompt window will open and you will be at [C:\Android]. Type [java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar] and press [Enter] on your keyboard.
It will pause, say [false] and run some commands.
* * If you receive the error shown below - ['java' is not recognized as an internal or external command, operable program or batch file.] - you do not have Java set as a System Path Variable.
* * Directions to fix this error are at the very end of this post.
If you do not [Microsoft Visual C++ 2010 Redistributable Package (x86)] already installed on your computer - a window will open prompting you to install. Check [I have read and accept the license terms] and push [Install].
While [Microsoft Visual C++ 2010 Redistributable Package (x86)] is installing - have your USB cable plugged into your designated Heimdall USB Port.
Pull the battery from your phone. Then put it back in - also putting the back cover back on.
Hold down the [Volume Down/Up] buttons on the left side of your phone. While holding both [Volume Down/Up] buttons plug in the USB cable into your phone. You should see the first image below for Download Mode - however you might see the second image instead - also Download Mode - if you are recovering your phone from a bad flash:
You should now be in Download Mode.
After [Microsoft Visual C++ 2010 Redistributable Package (x86)] is finished installing - Click [Finish].
You will again see the command prompt window. At the bottom of the window you should see [Installing drivers] and a pop up prompting you to put your phone into Download Mode -- which you should already be in Download Mode if following the guide .
Select [OK] and Zadig will open prompting you to install the necessary drivers to flash the One-Click.
In Zadig - Select [Options], then [List All Devices].
You will see [USB Receiver (Interface 0)]. Click your mouse where that appears and a drop-down menu will appear. Select [SAMSUNG USB Composite Device] and it will populate the box.
Now select [Reinstall Driver].
A window will appear - [Installing Driver...] - when completed you should be notified [The driver was installed successfully]. Select [Close].
Close the Zadig window, Heimdall One-Click 1.3.1 window will open and it will say [Connected] with a green highlight in the lower right corner.
Click [Flash] and Wait.
When Heimdall One-Click is finished working - your phone will reboot and run some code - then reboot again. You will see the T-Mobile splash screen and hear the T-Mobile jingle. Now wait again.
When finished - you will boot into your freshly flashed Stock Gingerbread ROM - allow your phone to sit for ten minutes to properly build caches..
[*]If you are upgrading from Froyo to Gingerbread - You will reboot into a Rainbow Like Screen because you still need to Flash Bootloaders. You are OK and this is normal. Proceed to ADDITIONAL STEPS ONLY FOR THOSE NEEDING TO FLASH BOOTLOADERS in the box below.
If you are flashing Bootloaders - Continue with directions in the box directly below.
----------------------------------------------------------------
* * START - ADDITIONAL STEPS ONLY FOR THOSE NEEDING TO FLASH BOOTLOADERS - START * *
Leave Heimdall One-Click running.
Unplug USB cable from phone. Pull the battery from your phone. Then put it back in - also putting the back cover back on.
Hold down the [Volume Down/Up] buttons on the left side of your phone. While holding both [Volume Down/Up] buttons plug in the USB cable into your phone. Your phone will be back in Download Mode.
Heimdall One-Click will once again say [connected]. This time you are able to put a check mark next to [Flash Bootloaders]. Check the box.
A window will appear warning you that [Flashing Bootloaders is Risky]. Select [Yes] and the window will close.
Now select [flash] one more time and wait.
When Heimdall One-Click is finished - your phone will reboot, you will see code run on your phone screen, then reboot again into the ROM - allow your phone to sit for ten minutes to properly build caches.
* * END - ADDITIONAL STEPS ONLY FOR THOSE NEEDING TO FLASH BOOTLOADERS - END * *
----------------------------------------------------------------
CONTINUED DIRECTIONS FOR FLASHING WITHOUT BOOTLOADERS AND WITH BOOTLOADERS
Enjoy! Hit Thanks Below!
----------------------------------------------------------------
o When you are finished with Heimdall One-Click - your phone will now be running:
Firmware version: 2.3.6
Baseband version: T959VUVKJ6
Build number: GINGERBREAD.VUVKJ6
----------------------------------------------------------------
o Directions to ADD Java as Path Variable:
You first need to find the folder on your computer containing [java.exe]. For me - [java.exe] is in [C:\Program Files (x86)\Java\jre7\bin]. The location of this file is dependent on where you installed Java.
Once the [java.exe] is located - notate the EXACT path [i.e. C:\Program Files (x86)\Java\jre7\bin] where the file is located.
Open [System Properties] on your computer. How to open [System Properties] is dependent on your Operating System. However - you can access [System Properties] on most Windows machines by Right Clicking on [Computer] and selecting [Properties]. Please do a Google Search if you are unaware as to the method to access System Properties.
In [System Properties] - select the [Advanced] tab, then select [Environmental Variables...].
In [Environmental Variables...] - under [System variables] look for [Path] and double-click.
In the window that opens - move to the very end of the text in [Variable value:] and add the path of the folder containing [java.exe] separated by a semi-colon. For me - I added [;C:\Program Files (x86)\Java\jre7\bin\] - no spaces.
Select [Ok] to all the windows you have since opened to make this change.
You will need to close the previous [Command Prompt] window you opened when you received the error and open a new [Command Prompt] window.
Staying away from odin is probably a good idea. It's how I learned and if you know how to use it fast. Maybe not the best for noobs but I still prefer it.
Hopefully noobs actually read this one!
But man I used to love Odin. I never could understand how so many people could mess up Odin, seemed pretty foolproof to me.
Sent from my LG-P999 using xda premium
95Z28 said:
I never could understand how so many people could mess up Odin, seemed pretty foolproof to me.
Click to expand...
Click to collapse
I think they do not read enough (i.e. where to put what, what to check and not check) and aren't patient enough to let it finish (because it can sit for awhile and make you think it is frozen).
Sucks that your phone got stolen. Don't know if would have helped or not but Lookout is a great app. Virus scan as well as phone locator. Free on market.
hechoen said:
Sucks that your phone got stolen. Don't know if would have helped or not but Lookout is a great app. Virus scan as well as phone locator. Free on market.
Click to expand...
Click to collapse
I had it on my phone for a looong time. But kept flashing, have never lost or had a phone stolen and it didn't make it back on.
Nice work lumin30
Sent from SGH-T959v using XDA premium
JuLes' MostWanted
°Developer in training
°Here to answer questions and help others.
°keep the forum in order.
JuLes' MostWanted said:
Nice work lumin30
Click to expand...
Click to collapse
Thanks JuLes'!
lumin30 said:
Thanks JuLes'... but was it necessary to quote the OP? Will you edit that post and delete the OP part please. Thanks.
Click to expand...
Click to collapse
I just did that to piss someone off
Sent from SGH-T959v using XDA premium
JuLes' MostWanted
°Developer in training
°Here to answer questions and help others.
°keep the forum in order.
bump
10 chars
how do i flash the kernel
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
do i just put the .zip on the sd and go to recovery wipe cache and davlik cache
What ROM are you running?
If u are on a GB ROM and rooted you can just download SGS Kernel Flasher from the market or you can flash the .zip in CWM.
If you read this guide you will learn how to do what you need to your phone without using ODIN or Heimdall.
Good luck.
Thanks for a simple and logical explanation of the process. I upgraded to GB 2.3.6 using Odin and it works great. Now I'm ready to take the next step, but I have one question.
When I upgraded to the stock ROM, all my programs, screens, contacts, settings, etc. were intact just as they were in Froyo. If I flash a custom Kernel and ROM, will I have to reinstall programs, set up email accounts again, etc.?
...........
It depends what ROM you flash but yes you will likely lose your apps and data - which is often a good idea anyways to prevent conflicts with the new ROM.
You can use something like Titanium Backup to back up ur apps and data if you want. Though read up on the best ways to do that. Most apps have within them backups. That is what I generally do. I have found fresh installs of the apps themselves are best. And restoring settings and data within the app itself works well.
If you need more help please don't hesitate to ask.
Edited. Sometimes in a long thread people may not be sure what you are responding to, hence the OP quote.
No problem. Let me know if you need any help.
I am stock gingerbread but rooted
Sent from my SGH-T959V using XDA App
Since you are on stock GB and rooted - find the section in the OP of this thread that says what to do with your phone on stock GB and rooted. It will talk about SGS Kernel Flasher.
{
"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"
}
HYPERION 7
The fastest and smoothest ROM for Samsung Galaxy Young GT-S5360 yet
With its easy-to-use interface, amazing features, and rock-solid stability, Hyperion leaves others behind.
And even as others try to catch up, the features built into Hyperion keeps your device years ahead.
Before you download, please read THIS
Elegant and intuitive interface.
The simple, beautiful Home screen is the easiest place to start.
From the home screen to every built-in apps in the system, navigation is fast, fluid and effortless.
Everything you touch is easy, intuitive, and fun.
Amazing features and built-in apps.
An ever-expanding collection of features and built-in apps make Hyperion even more powerful, innovative, and fun to use.
Here are just a few.
Would you like to donate?
Save your money for more important matter!
I accept "Thanks" donation!
Fast, simple and easy
If you love Hyperion and wants to support the project
Rate the thread 5 stars
Features and screenshots
NOTE:
... and we are back! If you read on 1st post, you probably not reading this. If you don't get me, click HERE
HYPERION 7 HIGHLIGHTS
PERFORMANCE TUNING
Full GPU (Graphic Processing Unit) rendering for faster, smoother and more responsive system performance
Disabled Journalism (File caching) for faster file read/write
Advanced radio controls for maximum battery saving
ADDITIONAL PERFORMANCE TUNING
IPv4 and TCP Stacks tweak
Secure WiFi Profiling
ISP Restriction tweaks
VPN Support
NOTE:
All above performance tuning are certified real by Hyperion Private Testers and not just written there just to say we updated something.
PERFORMANCE TUNING HIGHLIGHTS
Hyperion Core now fused with Adrenaline Engine for blazing fast performance - Tweak developed by ImbaWind- LINK
NetForks tweak for turbo charged internet browsing experience - Tweak developed by DroidFolks- LINK
FEATURES
UNIQUE FEATURES
No SMS Bug
No false Android version
No copy-pasted app from other ROMS
No paid apps edited to look like a new tweak or mod
No useless features
BASIC FEATURES
De-Odexed
Zipaligned
Recompressed APKS
Optimized APK Images
Rooted
BusyBox and BusyBox run-parts support
Apps2SD enabled
ADVANCED FEATURES
EXT4 File System Support
CIFS
Swap Support
BaCeM Tweak
UnderVolt Support
Firewall Support (DroidWall Open-Source Project)
ENHANCEMENTS
Mobile BRAVIA® Engine
xLOUD™ Sound Enhancement Technology
SRS Wow™ HD Sound Enhancement
Beats™ Audio Enhancement
OTHER ENHANCEMENTS WORTH MENTIONING
Modified PlayStore app
No market restrictions
No auto-update
No useless features
Mother of all HOSTS - more than 27,000 servers blocked
Blocks ADs
Blocks banners
Blocks 3rd party cookies
Blocks 3rd party page counters
Blocks web bugs
Blocks hi-jackers
Blocks phising sites
Blocks Malwares
Blocks Spywares
Blocks Trackers
Blocks un-authorized application connection
WHAT MAKES HYPERION UNIQUE
Savie's special kernel for Hyperion (Savie for Hyperion Project)
UNIQUE FEATURE
No false frequency reading
BASIC AND ADVANCED FEATURES
System-App replacer - I love you savie for this!
All-In-One modules
22 Powerful Governors
5 I/O Schedulers
Supports EXT 2/3/4 File System
Supports UnderVolting and UnderClocking
Supports CIFS (Remote Server-Client file access via Internet)
Hyperion Home - Xperia S Launcher originally modified for Gingerbread by ra3al - LINK
UNIQUE FEATURE
Not a paid app - We know how to code so we don't rely on paid apps.
BASIC AND SUPER LAME FEATURES :laugh:
Desktop layouts: Dock only, 4 Corners, Dock + 2 Corners and Dock + 4 Corners
Iconpack Support: Launcher Pro (Plus) icon packs, ADW Launcher icon packs and Go launcher icon packs
Custom desktop and App drawer row and column grid sized
Desktop folder support
App drawer sort methods: Own icon sort, Alphabetical, Most used and Recently Installed
Settings backup and restore function
Network Unlocker - Modified Galaxy Toolbox v1.0 by Doky73 - LINK
Modified for Hyperion
Remove carrier lock (Unlock)
Restore carrier lock (Re-lock)
Remove bin count (kernel flash count via odin)
NOTE:
The purpose of editing is to keep the sdcard structure tidy and to make sure there is no oddity in Core > Tools for menu items. Launcher and bml15 backups are stored in Hyperion folder in sdcard.
Installation and downloads
DOWNLOAD
Hyperion 7 Golden Master Final
Filename: HYPERION.7-GM.FINAL.zip
Size: 119.31 MB (125109981 bytes)
Uploaded By: CarlDeanCatabay
Uploaded On: 2012-11-13 12:29:45
MD5 Sum: c8a0b092b53165db700943ba72b885d3
File Desc: Hyperion 7 Golden Master Final Public Build
Virus Status: OK (Clean)
To all Hyperion users,
I got a message from our moderator regarding reports that Hyperion 7's zip package contains root explorer which is a paid app. During testing I added RootExplorer to make debugging init.d scripts easier. Due to excitement and demand for the new build, I forgot to remove RootExplorer and accidentally uploaded a zip package that contains this paid app. Starting today, link to Hyperion will be disabled until a new build is ready. Sorry for the inconvenience and my apologies to Speed Software Developers.
Thanks and Regards,
Carl
INSTALLATIONFlash Hyperion using STOCK RECOVERY
Go to recovery by pressing the HOME button + VOLUME UP key and the POWER BUTTON
Select WIPE DATA/FACTORY RESET
Select WIPE DATA/FACTORY RESET
Select APPLY UPDATE FROM SDCARD
After installing, reboot your phone
Flash Hyperion using CWM (ClockWorkMod) RECOVERY (UPDATED: 10/24/2012 11:13 AM Arabian Standard Time)
Go to recovery by pressing the HOME button + VOLUME UP key and the POWER BUTTON
Select MOUNTS AND STORAGE
Mount /system
Mount /data
Mount /sdcard
Select WIPE DALVIK-CACHE from Advance and Debugging
Select WIPE BATTERY STATS from Advance and Debugging
Select WIPE DATA/FACTORY RESET
Select WIPE CACHE PARTITION
Select INSTALL ZIP FROM SD CARD
Select SELECT ZIP FROM SD CARD
After installing, press the power button to go back and select REBOOT SYSTEM NOW
NOTES
First boot may take from 1-2 minutes or longer
The first screen you will see is the setup wizard.
The blue circle on the right corner of the status bar indicates that the system is busy (performing media scan, staring services etc etc).
In some cases (if flashed via CWM), the status bar might remain in "busy mode" until you restart your device.
HOW DO YOU KNOW YOU'RE STUCK IN BOOT LOGO? -IF IT STAYS THERE FOR MORE THAN 10 MINUTES. IF THAT'S THE CASE, TRY RE-FLASHING THE ROM OR FLASH STOCK ROM FIRST VIA ODIN BEFORE HYPERION :highfive:
Installation Troubleshooting Guide
INSTALLATION TROUBLESHOOTING GUIDE
In the past days, as we have observed, there had been installation issues for new and existing users. We know how annoying it is to get a bootloop, installation aborted and many installation related problem, so here you go, I will put every single scenario that had been reported and the best solution to install the best (according to users) rom when it comes to performance and style :victory:
Whenever I flash a new build, I have this "one-shot-install" method I am keeping. This one works whether you are jumping from one kernel to another. The one-shot-install step is:
Flash stock via Odin (Recommended)
Format SD Card to remove any unwanted files, orphaned data from previous ROM and of course, junk files.
Copy Hyperion zip package to sd card
Reboot to CWM using TempCWM if you are on stock ROM, or the built in CWM from savie's kernel if you are a previous Hyperion user and skipped flashing stock via Odin
Go to Mounts and Storage and mount /system, /data, /cache and sdcard
After mounting, Go back to main menu using the power button
Navigate to Advance (Advanced and Debugging)
Select Wipe dalvik-cache -this helps you avoid bootloops
Select Wipe batterystats -this ensures your battery gauge gets re-calibrated on first boot
After doing wiping dalvik and battstats, Go back to main menu using the power button
Select Wipe data/reset
Select Wipe cache
After doing data and cache wipe, select install update from sdcard
Select zip from sd card
Select Hyperion zip pacakage and install
Wait for the system to complete installation, it will take 2-5 minutes (maximum) to complete installation
Reboot your device
BELOW ARE THE REPORTED SCENARIOS AND POSSIBLE CAUSES WHY INSTALLATION FAILS COMMON FAILED INSTALLATION SCENARIO(S)
SCENARIO 1:
"I flashed Hyperion after flashing stock rom via Odin but every time I use Temp CWM and try to flash Hyperion, it goes back to stock recovery. No error is shown on recovery"
CAUSE OF ISSUE:
Incomplete download.
HOW TO AVOID:
Use a MD5 Sum checker. You can ask our dear friend Google for any md5 sum checker, it's free and it is usually less than 1 MB to download. Always make sure your zip package is intact and complete.
QUICK GUIDE TO CHECKING MD5 SUM:
Open your MD5 checker
Select the Hyperion package you downloaded
Paste the MD5 sum value from the download page in DevHost (MD5 Sum: c8a0b092b53165db700943ba72b885d3)
If it matches, then that means the zip package you have is intact and completeSCENARIO 2:
"I can't flash Hyperion via stock or CWM, it shows installation aborted"
CAUSE OF ISSUE:
Bad or damaged zip package
HOW TO AVOID:
Check the md5 sum and make sure your zip package is not damaged. If it is damaged, md5 checker will show you MD5 Hash Sum mismatch.SCENARIO 3:
I flashed Hyperion but nothing happened, I still have stock rom or previous custom rom
CAUSE OF ISSUE:
/system, /data, /cache partitions were not mounted in CWM prior to installation
HOW TO AVOID:
Super duper hyper mega easy; Go to Mounts and Storage and make sure they are all mountedBOOT LOOP SCENARIO(S)
SCENARIO 1:
"I am using a custom rom and I flashed Hyperion on top of it without flashing stock via Odin. After flashing, my device goes to endless boot loop. My previous custom rom includes a custom kernel"
CAUSE OF ISSUE:
Custom kernel (boot.img) from previous ROM
HOW TO AVOID:
The safest way to install a custom rom (in this scenario, Hyperion) on a device running a different custom rom with custom kernel is to revert back to stock rom first because jumpring from one kernel to another will surely cause boot loops. That is why we always recommend flashing stock rom first before flashing Hyperion.STUCK AT BOOT LOGO SCENARIO(S)
SCENARIO 1:
"I am using a custom rom with repencis kernel or merruk kernel prior to flashing Hyperion. After flashing Hyperion, I am stuck on boot logo (the samsung galaxy y blah blah screen)."
+
Same scenario above but; "I flashed stock rom via odin, but every time I do wipe data/factory reset and wipe cache, it shows me error mounting rfs blah blah"
CAUSE OF ISSUE:
Both repencis and merruk are known to convert your device's File System (FS) to EXT4. If your device's file system is EXT4 and not RFS (Robust File System), flashing Hyperion will fail, but boot.img (kernel) will be flashed.
SYMPTOMS OF EMMC FORMATTED TO EXT4:
CWM cannot mount /system but all partitions can be mounted
Stock recovery cannot do data and cache wipe
HOW TO AVOID/FIX:
Given your phone is already formatted to EXT4, there is nothing you can do but to repartition your device's EMMC (the chip where we install the device's OS) using Odin.
But remember I have written "but boot.img (kernel) will be flashed"? This will help you in solving this kind of issue.
Please keep in mind that this issue is not a problem with Hyperion rom, if CWM and Stock recovery cannot mount your /system partition, no custom rom can be successfully installed on your device.
Now this is the work around . . .
Since boot.img will always be flashed, that means if the kernel on the rom you are installing have CWM installed, then you will have CWM as recovery.
Now that's a good news because your default recovery now is CWM, and you can use it to format partitions back to its default file system. Follow the steps below:
Remove the battery of your device
Press the recovery key combination to boot into recovery
If you are lucky, you will be able to reboot to CWM (given you flashed Hyperion)
Once you are in recovery, Go to mounts and storage and format /system, /data and /cache
Once format is successful, reboot recovery using the "Reboot recovery" option
After rebooting recovery, mount the partitions and try flashing Hyperion again.
Wireless and Networking Troubleshooting Guide
WIRELESS AND NETWORK TROUBLESHOOTING GUIDEWIFI ISSUE(S)
WIFI ISSUE 1:
WiFi gets disconnected once phone is locked or the display turns off
CAUSE OF ISSUE:
Okay, don't panic. This is not a bug. This behavior is the one responsible why you save battery even if you don't turn off your WiFi radio and this is called WiFi Sleep Policy.
HOW TO AVOID:
Currently Hyperion have 3 WiFi policies available in Settings Tab > Wireless and Network > WiFi Settings > Advanced > WiFi sleep policy.
WiFi Sleep Policies:
When screen turns off - if selected, wifi will turn off automatically when the screen turns off (obviously)
Never when plugged in - if selected, wifi will not turn off automatically when connected via AC or USB port and is getting power from either AC or USB.
Never - if selected, wifi will never turn off automatically - default setting in stock roms
WIFI ISSUE 2:
WiFI cannot connect to any wireless hot spot and/or wireless networks
CAUSE OF ISSUE:
Still UNKNOWN. The dev team are thinking that only production specific GT-S5360 devices are affected with this issue.
Based on user feedback, we are in conclusion that the following might be causing the problem:
Savie's special built kernel for Hyperion
Netforks Tweak
Mother of Host
HOW TO AVOID:
Currently, we have the following fix but not all or even none of the below suggestion may fix the problem depending on your SGY.
A simple reboot will fix the WiFi connection problem
Flashing your device's radio image (baseband) via Odin will fix the problem
Removing NetForks tweak will fix the problem
Removing Mother of Host may fix the problem
QUICK GUIDE TO FLASHING BASEBAND
Open Odin and locate the firmware files for your device
Connect your device to computer using USB Data Cable (USB Cable)
On the PHONE field, locate the MODEM file for your device
Click start to start flashing BASEBAND
NOTE:
You will only flash the PHONE file
QUICK GUIDE TO REMOVING NETFORKS TWEAK
Using root explorer, navigate to system/etc/init.d
Delete 04netforks_tweak
Using root explorer, navigate to data/
Delete droidfolks folder
Reboot your device
INTERNET ISSUE(S)INTERNET ISSUE 1:
Cannot open websites and or cannot surf the web
CAUSE OF ISSUE:
Mother of all Hosts
For some reason, most of the website that can't load on any browser are website like mediafire, 4shared and other file hosting sites which what they have in common are ADs, Popups, Counters and Surveys. Since MOH is blocking these type of web activities, some webpages may not load. Specially those sites that are configured not to load when their advertisements are disabled by either the browser or internet connection.
HOW TO AVOID: Thanks to Dr.oidbio for pointing this out
OPTION 1
Using root explorer, navigate to system/etc
Replace hosts file with any hosts file from stock or other custom roms
Reboot your device
OPTION 2:
Using root explorer, navigate to system/etc
Open hosts file with text editor and edit the content
Delete everything except
Code:
[LEFT]#
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
::1 localhost
127.0.0.1 local[/LEFT]
Reboot your deviceCONFIRMED WORKING FIXREPORTED BY: AlvaroOrduna
Therefore, I set to work and I solved the Wifi issue (obviously with your helpful guides). So that I wanted to share with you the procedure to solve the problem. Here are the steps I took:1. Delete 04netforks_tweak from system/etc/init.d
2. Delete droidfolks folder from data/
3. Edit the hosts file in system/etc deleting all except:#
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
::1 localhost
127.0.0.1 local4. Reflash baseband via Odin
It should be mentioned that I do these steps on flashing zip. I mean, I edit the ROM in the computer and then I install it following the steps in INSTALLATION TROUBLESHOOTING GUIDE. Everything else works fine, but in the future I will continue to watch to see how the phone behaves. If something goes wrong and you do not mind, I will report it.
Attribution-NonCommercial-NoDerivs 3.0 Unported (CC BY-NC-ND 3.0)
Disclaimer
The Commons Deed is not a license. It is simply a handy reference for understanding the Legal Code (the full license) — it is a human-readable expression of some of its key terms. Think of it as the user-friendly interface to the Legal Code beneath. This Deed itself has no legal value, and its contents do not appear in the actual license.
Creative Commons is not a law firm and does not provide legal services. Distributing of, displaying of, or linking to this Commons Deed does not create an attorney-client relationship.
This is a human-readable summary of the Legal Code (the full license). Disclaimer
You are free:
to Share — to copy, distribute and transmit the work
Under the following conditions:
Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
Noncommercial — You may not use this work for commercial purposes.
No Derivative Works — You may not alter, transform, or build upon this work.
With the understanding that:
Waiver — Any of the above conditions can be waived if you get permission from the copyright holder.
Public Domain — Where the work or any of its elements is in the public domain under applicable law, that status is in no way affected by the license.
Other Rights — In no way are any of the following rights affected by the license:
Your fair dealing or fair use rights, or other applicable copyright exceptions and limitations;
The author's moral rights;
Rights other persons may have either in the work itself or in how the work is used, such as publicity or privacy rights.
Notice — For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page.
Developer Conditions:
Any ported version of this rom for any device must be released under the name "Hyperion" or any name as long as "Hyperion" is present.
Ported version must have the same logo in Settings > System.
A link to this thread is required.
Hyperion Project in HTC Mania
Preview - Work In Progress
"Do you even know how to theme apk?"
Hyperion 7.x with Hyperion Home 2.x
The Dev Team
The Hyperion Project 2012Devs I thank the most on this project:
b16h22 - Father of EVO-X; the grand daddy of Hyperion
savie - the guy behind Hyperion's Core Power - Savie For Hyperion (SFH) KernelOther Devs and their contributions:
ra3al for his amazing work on XPERIA S Home Launcher with Settings | 0.9.2c
DroidFolks for Netforks Tweaks for all Android 2.3.6 - 4.1.2 devices
Hyperion 7.x Pre GM
NOTHING NEW, JUST THIS:
More smoother UI - Project Butter Hyperion style | Speed and stability will always be a priority and not eye candy :angel:
Tamed Mother of all Host - not sure though if it's Grandma Host on this package, but who cares? Host file is less agressive now and this will solve problems with sites (specially file sharing sites) not loading.
UPDATED
Graphics driver for smoother gaming experience.
Some libs and *I think some modules as well.
ADDED
Sound Theme - Linda Sounds Mod (the most complete set).
FIXED
WiFi Issues - caused by Multi-CSC mod that affects WiFi banding depending on the market where your device was officially released. In future I might include CSC + WiFi CSC editing so you can take control of WiFi banding (device <-> router connectivity).
Tick/Untick bug in some checkbox item(s) in settings - might also be region related problem.
Most black text over dark background (some are still present because they don't depend on framework/SystemUI)
BACK FROM THE DEAD
I know you missed the good old TouchWhiz Launcher, so here it is, old guy new look
WHAT'S IN IT:
Holo style dock, home and app drawer buttons
9-12 home screens
5-icon dock support
Grid and List view in App drawer
Support AppShare in app drawer
Random icon background support (currently list view only)
Opacity tweaked to match the overall transparency of UI
DEFAULT CONFIG:
3 Home screens
1 Widget: Google search + voice
4 shortcuts on default home screen
5 icons in dock
App drawer icons arranged alphabetically
App drawer in grid view
DOWNLOAD
Filename: HYPERION-7.x.zip
Size:114.63 MB (120203331 bytes)
Uploaded By:CarlDeanCatabay
Uploaded On:2012-11-30 02:34:16 MD5
Sum:5f37a325cffc4c5f409eaba2e5825d76
File Desc:Hyperion 7.x Pre GM Build
Virus Status:OK (Clean)
Note: Use virus status as a reference, rescan with your own Anti-Virus.
TRANSLATING HYPERIONTOOLS YOU NEED:
Any apk tool for decompiling and recompiling like APK Tools, APK Manager and APK Changer Alpha 11 - APK Manager and APK Changer Alpha 11 are the one I'm using. Take note, it's alpha 11, not the latest version of APK Changer.
Notepad++ - a GNU editor you can download from HERE
WHERE TO GET THEM:
APK Multitool - http://apkmultitool.com
APK Changer - http://forum.xda-developers.com/showthread.php?t=1189971
APK Tools - I don't know where to get it. Ask dear Google.HOW TO SETUP YOUR TOOLS:
I advice you use APK Changer as it has an automated setup where you can configure this tool as you install it.
Follow the installation/setup steps for the tool of you choice
After that look for C:\Users\<User>\apktool\framework folder. Ex: C:\Users\Carl\apktool\framework
Take framework-res.apk and rename it to 1.apk
Take twframework-res.apk and rename it to 2.apk
Copy 1.apk and 2.apk to C:\Users\<User>\apktool\framework
HOW TO TRANSLATEPREPARE APKS
In this example, we will modify Settings.apk and translate it to Spanish language.
Take Settings.apk from stock ROM that supports Spanish and rename it to Settings-ES. If your language is not Spanish, then of course you need to take Settings.apk from stock rom for you region which support your language.
Take Settings.apk from Hyperion. You don't need to rename it. Leave it as it is.
DECOMPILE APKS
Once you have all the needed APKS for modding, place it inside the folder designated by the tool you're using for decompiling. In this example I am using APK Changer, so I will put Settings.apk and Settings-ES.apk to C:\Apk-Changer_alpha11\place-files-here-for-modding folder
Open your tool, in this case it is APK Changer. If you installed this already prior to preparing APKS, then you should have the main menu where you have the option to decompile/compile.
Decompile both Settings-ES.apk and Settings.apk
TRANSLATE/ADD ADDITIONAL LANGUAGE TO APK
After decompiling apk, look for the "values" folder inside the decompiled APK. In this case I use APK Changer so I will navigate to C:\Apk-Changer_alpha11\out\Settings\res
You should to the same for Settings-ES and open it in another folder so you can view both folders side-by-side
You can simply take "values-es" folder from Settings.apk and copy it to Settings\res
After copying folder, open Settings\res\strings and add the values present in Settings.apk's res\values\strings.xml to "values-es" folder.
After that, compile your APK and now you have a translated version of APK.
Do this for every app you want to be translated.
OF COURSE MOST OF US ARE LAZY AND ONLY KIND ENOUGH TO TRANSLATE, SO I'LL POST HERE THE FILES YOU NEED TO EDIT AND TRANSLATE AND IF I HAVE TIME AND I AM NOT FEELING LIKE A LAZY MONKEY, I WILL BE THE ONE TO COMPILE THE APK FOR YOU.NOTE:
Only strings.xml and arrays.xml values needs translation. You only need to translate values inside
Code:
<string name="[COLOR=Red][B]alert_mesage_recipients[/B][/COLOR]">[COLOR=SeaGreen][B]Alert message recipients[/B][/COLOR]</string>
<string name="[COLOR=Red][B]text_you_should_not_translate[/B][/COLOR]">[COLOR=SeaGreen][B]Text you should translate[/B][/COLOR]</string>
Example:
<string name="alert_mesage_recipients">Alert message recipients</string>
You will translate "Alert message recipients"
You should NOT translate "alert_mesage_recipients"
Translated example:
<string name="alert_mesage_recipients">Alerta destinatarios del mensaje</string>GET FILES HERE
SETTINGS.APK
CarlDeanCatabay said:
Yes. To check that, navigate to:
/sd-ext/ using root explorer, you will see there:
app
app-private
dalvik-cache
lost+found
To check if deep sleep is working, navigate to:
Settings > Core > CPU States
NOTE:
Deep Sleep starts when phone is idle, if your phone is running for 2-4 minutes from boot, in some cases you will not see deep sleep state in cpu states info. That is normal.
Click to expand...
Click to collapse
i dont know anything abt a2sd plz can u tell me after making the partition what should i do so all the apps and dalvik cache is installed in the partition thanks quick reply will be appreciated
btw i am loving this rom
and is there any way the to change the status bar toggles order
CarlDeanCatabay said:
Yes. To check that, navigate to:
/sd-ext/ using root explorer, you will see there:
app
app-private
dalvik-cache
lost+found
To check if deep sleep is working, navigate to:
Settings > Core > CPU States
NOTE:
Deep Sleep starts when phone is idle, if your phone is running for 2-4 minutes from boot, in some cases you will not see deep sleep state in cpu states info. That is normal.
Click to expand...
Click to collapse
alright.thanks
@CarlDean : No Statusbar tweaks and Widget button, so how do we edit stat bar and add or remove some toggles on 14 toggles?
Solehria said:
i dont know anything abt a2sd plz can u tell me after making the partition what should i do so all the apps and dalvik cache is installed in the partition thanks quick reply will be appreciated
btw i am loving this rom
and is there any way the to change the status bar toggles order
Click to expand...
Click to collapse
Ooops! Seems like I forgot to put QuickToggle in Settings > Parts. I'll create a patch and will attach it here later. Sorry about that, I was too excited to release the ROM
CarlDeanCatabay said:
Based on yowskee's test, RAM usage is about 130-140 MB and he can play Zenonia 4 at 170MB used at most. But i need others to test that.
Click to expand...
Click to collapse
You made my day downloading & flashing
CarlDeanCatabay said:
Ooops! Seems like I forgot to put QuickToggle in Settings > Parts. I'll create a patch and will attach it here later. Sorry about that, I was too excited to release the ROM
Click to expand...
Click to collapse
plz can u tell what i have to do about a2sd after making a partition
if possible add stat bar tweaks...i dont want to see AM and PM on clock
plz people help me what should i do after making the partition
Please, have present the Kernel Savie #73 not run in all model S5360. In variant S5360X not worked.
Solehria said:
plz people help me what should i do after making the partition
Click to expand...
Click to collapse
Please follow the instructions in my Link2SD for dummies on how to partition your SD Card.
"Those, who fail to read history are bound to repeat its mistakes"
People here have and did and will fail to read the things here and many did and many probably will have to lose their devices. You don't have to lose a device to get knowledge inbetween your ears.You don't have to be stupid. You surely can learn from your mistakes. But There's a better way. You can learn from others mistakes. This thread is a compilation of such mistakes ,that I personally have done and many others ,who did and their solutions aka The easy ways.
So, officially I congratulate you for finding this thread and reading Upto here. So, even if you don't read the whole thread, these are the main stuff you must know is
1. Rooting is a dangerous process -done by developers only. If you did root your device, you assume full responsibility for your device. So, if you can't think like one of the developers at least partly, I suggest you don't root your device ,coz when you mess up, the one who deviced the procedure or Rom will not help you. And everything you find here is in "AS IS " tag.
2.If you have rooted, next thing you must do is backup-
Go to recovery,
go to backup and restore
click backup.
I find it strange that this is not included in the root procedure. This surely would've helped a lot of Picos out there.
3.NEVER DO A RUU
-It unanimously holds the number ONE title for the major causes of bricking of Picos.
Trust me -Surely you can save your device, without the ruu. And with ruu, you're bound to fail without proper knowledge and research.
The only time you are suggested by experts to do a ruu is when you have already done a ruu "and" bricked it.
4. Overclocking here may cause burnt nand. -know what Rom you're using-it may have built in-overclock .
However, overclocking doesn't necessarily produce burnt-nand for all devices.
5.Finally, Not all answers you receive in the question and answer thread are good. Some answers will kill your device. So please judge the credibility of the answerer before you follow the answers. Generally, you could track back their previous answers and their working. Thanks meter is a good source of credibility -but not always -Not all who have big thanks record are helpful neither are they knowledgeable-There are spammers, who trick people into giving thanks.Do your home work before you trust a stranger. Recognized developer title is a good source of credibility.
The above five should save you a lot of trouble.
Ever in trouble? Drop by and read.
Do your googling,if you don't understand anything here.Have a great time !
Re: [faq][newbies only][mini edition]
��To start, this thread is only for newBies,who have rooted thier Rom and have a custom recovery. If you haven't, click here
Alright, this thread aims to answer all the frequently asked questions by newBies. The section this thread aims to answer will consist mostly of custom Roms especially cyanogen.
To start, we'll start with basics
Our phone consists of the following five partitions
1.Boot/kernel
2.Recovery
3. System/Rom
3.1What's not working
3.2 Latest links
4. /cache- error /last log
5.Data
5.1Scripts
6.Common issues after flashing Rom, scripts/GAPPS/PLAY STORE /
Ram
7. USB and CPU ,screen and power button-2/7/13
8. About developers and members
9. ��Burnt nand*recovrecovery 25/6/13 *��
10. STILL CAN'T FIND THE ANSWER ��
10.1LOGCAT
10.2ADB
11.MINI TIPS AND TRICKS
11.1CM9/10 themes
11.2.FONT CHANGING AND language तदधा ಥಮು support adding
11.3.DID YOU KNOW?
12. Recommended apps
13. BATTERY LIFE AND PERFORMANCE
14 .http://forum.xda-developers.com/showthread.php?p=38098604
BUILD. PROP TWEAKS
We'll discuss the faq in each.
All links are here
Index:
http://forum.xda-developers.com/showthread.php?t=1754876
This is the best link you'll ever have
Thanks hrkh83
Guides
http://forum.xda-developers.com/showthread.php?p=36057579
Guides for everything
Thanks hpsgill
Make yourself useful by akshat
Seen it before,
Just read this now
http://forum.xda-developers.com/showthread.php?p=37805872
Stock Roms instead of bricking ruu
tk immortal yash
http://forum.xda-developers.com/showthread.php?p=39101954
Re: [faq][newbies only][mini edition]
/BOOT(4 MB Max )
1.what does this partition contain?
It contains your kernel
2.what is kernel?
It's a in betweener between ROM (/system ) and your hardware.
Basically, a software, which connects the main software (your Rom gui) and the hardware
3 .what is the stock kernel version?
2.6
4. Is there a update available?
Yes. You can update it to 3
3.4 is currently being worked on
5.what are advantages of kernel 3 ?
Nothing much that you can feel
Basically related to stability, security, and future Android Os updates can easily be done for a310e
5.where are the links to kernel 3 ?
Look down
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
With cm9
1.Firewall
2.USB tethering
3. Wi-Fi hotspots
4.Vpn
Anything related to iptables
With cm10
Known issues
Ext4 cannot be mounted?
Temple run 2 and subway surfers reboots*fixed in overclocked kernel *burnt nand *
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. I wanna make my own kernel?
Special thanks to bhargz16
http://forum.xda-developers.com/showthread.php?t=2114594
10.Is there a overclocked kernel?
Yes
http://forum.xda-developers.com/showthread.php?p=38098604
11. How to Flash kernel? Do I need to clean install?
No need to clean install
Copy zip to root of /SD card
Go to recovery
Install zip from SDcard
Choose the correct zip
Install
Reboot
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/Recovery(5 MB Max )
First thing to do after root is to make a nandroid backup.
Go to backup and restore and select backup
1.what is this partition?
It contains your recovery
2.what is recovery?
It's a specialized partition for Android, which is used when something goes wrong.
We use it to change (flash) Roms, change kernels and mostly everything in xda. Make nandroid before you mess up
3. What are the recoveries available for a310e ?
1 .yannou90 (cwm5) recovery
2.Twrp 2 .3 by cute prince
3. twrp 2.2 by oblikas
4.cwm6 by sakindia
5.*OFFICIAL *The latest TWRP by bhargz16( http://forum.xda-developers.com/showthread.php?t=2123503 )
6.cwm6 by nihar.g
Links .check index link in top post
4. Are all of them stable?
The 1 and 5 are pretty stable.
What's not working:
cwm6 by sak let me down big time .
http://forum.xda-developers.com/showthread.php?p=38734554
Except 1,all other recoveries will not show charging animation, when you are charging your phone after switching it off ~instead of charging animation ~you'll be going to recovery
twrp official - some problems with ext4 partition has been reported and also reported to have been fixed. -I never had the problem before and after and I recommend this one 2.5 present here in xda.
twrp cute prince has issues restoring backups (problem with symlink )
5.what's the difference between them?
cwm5 - complete backups of all partitions
twrp - support compressed backups /file manager and other great things
cwm6 - your SD ext partitions will not be fully backed up during subsequent backups,but only the changed files greatly reducing the size of subsequent backups
6. Can you explain more about cwm ?
http://forum.xda-developers.com/showthread.php?p=38100620
7. Recommended apps.?
Recovery file manager aroma 1.8
8. How to flash a recovery?
Two methods described in detail in link above by bhargz16 ~ fast boot
Flash from phone:
Required:
Flash_image binary
You can flash any recovery
From terminal using
Code:
su
flash_image recovery /sdcard/recovery.img
You need recovery.img (renamed like that ) present in /sdcard itself
9. Error while restoring .Androidsecure /sdext ?
http://forum.xda-developers.com/showthread.php?p=39874898
10. Cannot go to recovery /burnt recovery /unable to flash recovery?
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/SYSTEM (235 MB Max )
1.what is it?
Here's where your Rom resides
Any cyanogen /ever/miui roms all go here
2. What are system apps
Any app in /system /app is system app and they have special permissions
2.1 how to make a app system app?
Uninstall the app with titanium backup and copy it's apk to system/app(normal delete apk will not delete. Dex and lib files ) ~reboot ~
Some apkS need it's library file also in /system /Lib (copy from /data /Lib to /system /lib )
3.what is binary?
These are executable ~very important files in /system /bin. (or /xbin in recovery)
Your root su is here
4. What are the roms available?
Many roms are available in xda
Main line ones are
CYANOGEN 7
CYANOGEN 9
CYANOGEN 10
Cyanogen 10.1
Miui
5.What is cyanogen 7 ?
It's a cyanogen version of gingerbread
9 is ics
10 is jelly 4.1
10.1 is jelly 4.2
5.1 what's the development going on?
cm7 *camera was unable to be fixed *development stopped
cm 10*active development now *
cm 10.1 *thread closed *
6. How to install a new Rom? Cyanogen for example?
Download the latest build. Zip and put in the root of /sdcard.
Go to recovery
Factory reset data
Wipe cache
Wipe dalvik
Wipe SD ext
Choose install zip from /sdcard and choose the build. Zip
Wait
Reboot
Go back to main ^|^
The nothing really bugs list
Welcome to THE "NOTHING REALLY" BUGS™
This is the official nothing really bugs Pico web post at xda. Its name implies that the bugs present are really nothing to some people. But to the rest, it may bother a lot. So, this post.
Here you'll find most of the nothing really bugs. All statements having "Nothing really " in bugs list directs here. This is to inform new flashers of what they'll get and what they won't. To make the facts clear,so that you won't have to flash every Rom to find out all the nothing really™ bugs. After all, this is a newbie friendly thread.
Please note that though every effort has been taken to ensure an exhaustive list of all the bugs .Some may not have been stated here .If you do find a bug, which isn't stated here, please feel free to mention it here and I'll add it after being personally confirmation by me or two to three renowned senior member witnesses. Further more, some bugs here may have been fixed. You can take a look at the last edited day of this post to make sure this post is up to date. And you can mention it here,if any of the information found here is wrong.
1.What doesn't work in cm10 4.1 Jelly beans ?:
1video (video recording with some third party apps~Skype video messaging, zoom camera ,camera magix and a lot more)(S. ucam works fully)
2Bluetooth headphones can't be used during call(try using sound about )✘
2.1 Bluetooth stereo headphones ✘
3vsync
4.stock camera force close often and unstable (S. Camera 360/ucam)
5.Wi-Fi unable to turn on ~from settings /notification bar. (s:Flash kernel 2.6)
6.burnt nand
7. Wi-Fi direct (native )causes reboot. (S. 3Rd party app ~fast file transfer)
8.some VOIP~{ex:gtalk(even after normal gapps),and many more}
9.Most streaming video{not flash, but those, which open in mx} doesn't work. Most TV apps don't work (not flash using tv apps)
10. mobile data may fluctuate for some(timedo app to turn on and off airplane mode for every hour)
11. calls robotic call for some
http://forum.xda-developers.com/showthread.php?p=32997468
12. Unofficial adobe flash is flickering too too much. (Only Firefox actually works with flash..which flickers unbearably ~the rest don't even work )
13. Headphones volume control during in call✘
14.USB tethering (native)✘
15. Wi-Fi hotspots work only as open source ✘
16.Bluetooth A2dp streaming ✘
17.Firewall rules don't stick, when put in init.d. Somehow the Rom process overtakes the firewall rules during boot and during some process. My intuition directs the blame at bandwidth controller| throttle service~|Data usage settings|which wasn't implemented properly, but using dirty hacks
18. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting. (s.flash kernel 2.6 with USb mass storage fix here. )
19. Multi mount SD app doesn't work [s.flash kernel 2.6]
OTHERS
1. Battery drain
2.Phone heating
3.WiFi toggle
Total :22[Because, I used this Rom for a long time,so the large number]
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
2.What doesn't work in cm9 ?
forum.xda-developers.com/showthread.php?p=35756952#post35756952
2VIDEO PLAYBACK doesn't work as well as stock
3 Wi-Fi toggle in latest RomS
4 Bluetooth stereo headphones ✘
Experienced by some:
A. Encryption doesn't work (crypt)✘
B.robot call http://forum.xda-developers.com/showthread.php?p=32997468
C.mobile data flickering
Note: video playback is much better in cm10.
Language rendering is also much better in cm10.
3.what doesn't work in Original HTC STOCK ROM?
A. if you ever click "reset to default" in the Camcorder settings..,all future video recordings will overwrite already taken videos and all previous videos will be lost(use ucam)
B. sending a more than 150MB file on Bluetooth file manager app through Bluetooth will reboot your device.
(use stock transfer)
3.1 what's not working in a rooted stock Rom?
(make a nandroid backup first to protect you)
Optimize storage in storage settings
Factory reset will put you in bootstruck.
4.What doesn't work in cm10.1 ?
Camera and lot more minor/major
Too long list
Will update when usable
5.what doesn't work in cm7 ?
Camera
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
3.Wi-Fi toggle from notification bar /from settings
4. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting.
5. Multi mount SD app not working.
With cm9
1.Firewall
2.USB tethering ✘
3. Wi-Fi hotspots ✘
4.Vpn ✘
Anything related to iptables
With cm10
Known issues
Some partitions [?Ext4] cannot be mounted
*burnt nand *
With latest cute prince kernel [power management fix ]:
Mounting of SDcard on some devices
Multimount SD app
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. Sense4 Roms
1.Burnt nand ~most common ✘
2.Random reboots ✘
3. WiFi direct. ✘
4.Bluetooth headphones ✘
Go back to main ^|^
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
S - probable third party solutions
Solutions for burnt nand -Please go to burnt nand section.
[COLOR="RED"]Welcome to [b]▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀[/B][/COLOR]
Welcome to ▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀
Not sure whether it'll be updated,but galaxyfreak released a app on latest Roms ~ http://forum.xda-developers.com/showthread.php?p=38913186
Why this post ?
Because index has only thread links and sakindia123 never updates op
If he does, then this post will not be updated anymore. Other than that, here are some kernel links as well. Other than the main line ones, the others are not updated. Sense4 links are already present in op and here as well http://forum.xda-developers.com/showthread.php?p=40111838 . Any link that's not present in op will only be updated.
1.what's the latest build on cyanogen 9?
Build 13
http://forum.xda-developers.com/showthread.php?p=36626369
#14*beware of burnt nand *
http://forum.xda-developers.com/showthread.php?p=38770875
2.what's the latest build on cyanogen 10 ?
Build 3.2.2.use with kernel 2.6
http://forum.xda-developers.com/showthread.php?p=38183817
Liverpool fan latest 3.2
http://forum.xda-developers.com/showthread.php?p=38447868
Beta 5~beware of burnt nand ~
Video fix by bhargz*liverpl 4 beta5*
http://forum.xda-developers.com/showthread.php?p=39124906
http://forum.xda-developers.com/showthread.php?p=39090779
Beta6~beware of burnt nand ~
http://forum.xda-developers.com/showthread.php?p=39166124
+
http://forum.xda-developers.com/showthread.php?p=39804373
(Flash this to prevent overclock)
Lock screen fix for both beta 5 and 6 .
http://forum.xda-developers.com/showthread.php?p=39043840
2.1 Aokp build link
http://forum.xda-developers.com/showthread.php?t=2208242
3.what is the latest build on cyanogen 10.1 ?
Alpha 3
http://forum.xda-developers.com/showthread.php?p=38094629
Alpha 4
http://forum.xda-developers.com/showthread.php?p=38325531
4.what's the latest build on kernel?
Old Kernel 3
http://forum.xda-developers.com/showthread.php?p=36572115
Kernel 3 v2 only for sense
http://forum.xda-developers.com/showthread.php?p=38466559
http://forum.xda-developers.com/showthread.php?p=39730163
Kernel 3 v2 for cm10
http://forum.xda-developers.com/showthread.php?p=39737920
http://forum.xda-developers.com/showthread.php?p=39804373
5. Is there a overclocked kernel?
http://forum.xda-developers.com/showthread.php?p=38098604
kernel 2.6=garudav5kernel
6. Kernel 2.6 for JB ?
http://forum.xda-developers.com/showthread.php?p=37649737
http://forum.xda-developers.com/showthread.php?p=36303556
7. Kernel 2.6 for ics?
http://forum.xda-developers.com/showthread.php?p=35797210
http://forum.xda-developers.com/showthread.php?p=36526379
http://forum.xda-developers.com/showthread.php?p=37550173
8. Side effects and solution of using kernel 2.6 on a kernel 3 based Rom:
http://forum.xda-developers.com/showthread.php?p=39452607
Basically, USB storage may not work.
To, make it work, Flash the fix attached with this post(don't remove battery @ any stage:sly-tested on my twrp 2.4.4 with cm10beta5.May not work with ics.
Alternatively, you can use multi mount SD app /root tool box lite app.
Attached zip md5: 8216eaf4a357b9cddc5cfd29b8d05a50
Attached zip sha-1: 408a075479745fe1713f8c55a968801f7f6160dd
Some more links :
http://forum.xda-developers.com/showthread.php?p=40964578
Super wipe zip
http://forum.xda-developers.com/showthread.php?p=38338418
Nand recovery procedure:
http://forum.xda-developers.com/showthread.php?p=38098622
tk to akshatshenoy.
Flashing an older ruu:
Not recommended @ any stage
http://forum.xda-developers.com/showthread.php?p=38694608
Even if it works,you might have problems data, battery drain etc.. if you Flash a wrong radio
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
http://forum.xda-developers.com/showthread.php?p=40035607
How to install kernel? Clean?
http://forum.xda-developers.com/showthread.php?p=38098513
QUESTION NUMBER 11 ABOVE
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/DATA (150 MB )
1.WHat's this?
It is the internal memory
2.Why is it important?
Because this is the place where all the apps go
No /data = no more apps
3.what's our available internal memory?
150 MB
User available 90 MB
4. Any way to increase internal memory?
By scripts
5 .Recommended apps to diagnose application not installed
Diskusage app
Log cat
6. What does a app contain?
App when installed splits into apk dex,and data(lib+data) files
Go back to main ^|^
Re: [faq][newbies only][mini edition]
SCRIPTS
Before we start, a app when installed takes space as three parts.
They are apk,dex and data (lib+app data)
All scripts work by symlinking
1. What are the scripts available for our explorer?
Partial scripts
A.Link2SD app
Moves apk,dex,lib~doesn't move app data
B.Root data2SD app
Need ext partitions
Moves application data2 ext
Full scripts--Need init.d support able to move fully /partially as per requirements
Links available in index
1.Mount2SD
Download from play store or from here check index
Famous for it's stability and frequent updates
Issues +
2. Int2ext
As per script, moves partially /fully .
Has a large user base
issues ++
3.s2e
Moves fully.
Issues +++
NO official version for jelly beans.
4.a2sd darktremor
Issues ++++
However works pretty well with stock Rom and jaggy Rom
Discontinued
5.ungaze script
Issues +++++
I don't recommend it.
Why not?
Because
http://forum.xda-developers.com/showthread.php?p=33750812
http://forum.xda-developers.com/showthread.php?p=31915607
1.1 mount2SD doesn't work? Script not executed fully @ boot?
Flash kernel 2.6 from above and you should be good to go.
2. How do I increase internal memory (literally ) from 150 MB to 2GB(for example SD ext )?
Use mount2SD reverse mount
Use int2ext
Side effects:
As per Android rules, 10% of internal memory will be unavailable
So, 200 MB out of 2GB SD ext will be unavailable
Mount2SD also has normal moving methods ,which will make Android think you'll have 150MB but you can fill up 2GB inside of 150 MB (Here 10% would mean 15 MB)
3. I installed d2ext/similar ,I'm not able to install more apps ,even though I have more SD ext space?.
A. First make sure you don't hit 10% data limit described above
B. Use diskusage app to determine,which partitions are full
For example- some scripts don't move dalvik and so dalvik will fully accumulate in /data creating no space.
C. Fix permissions from recovery, wipe cache and dalvik and reboot.
4. My Rom doesn't have init.d support /I'm using stock Rom?
Check index
You can add init.d support by
Flashing custom kernel (cranium)
Flashing scripts to make init.d support (or pimp my Rom app[not tested])
5. Where to add scripts before flashing Rom?
Add it in /system/etc/init.d (permissions are rwx rwx rwx ,if you're adding this in recovery after flashing )
For mount2SD add configurations folder in /data/m2sd.
6. How to migrate from link2SD to mount2SD?
http://forum.xda-developers.com/showthread.php?p=38840247
7. Is there a full script so that I can use both my internal memory and SD ext?
A bit complicated, but this what I use...
Configure mount2SD
To move both apk and dalvik
Don't move data.
Then open titanium backup to move app data
@First move one app data to create data2SD directory.. then you can batch move whatever apps you think fit.
But please make sure you have at least 10 to 30 MB in /data and in/SD ext (SD ext not necessarily ) before a nandroid backup. Otherwise restoreS will not work.
Go back to main ^|^
Re: [faq][newbies only][mini edition]
Common issues with scripts:
0. Device stuck @ HTC logo with 4 error icons on all four corners
Since you flashed an ruu and failed user data fail etc.
Unlock bootloader if possible
Flash twrp recovery again
Code:
fastboot flash recovery.img
Then go to recovery with this command
Code:
fastboot boot recovery
Now that you're in recovery wipe everything, format everything .
If flashing failed /you can't enter recovery, do this keeping twrp recovery.img in /SDcard
Code:
fastboot boot /sdcard/recovery.img
Do cute prince recovery procedure shown in burnt nand section
Flash erase mtd3 as well
Now Flash your Rom and boot
If it doesn't boot, repeat the whole procedure above and now
Do ruu.
If all the above failed,
http://forum.xda-developers.com/showthread.php?p=39181288
Read the above thread fully. That's the last resort.
Moral : Don't ever Flash an RUU (if you haven't already )
You can Flash stock Rom ~safer
1. Device struck in HTC logo
Wait for 15 minutes
Try pulling out battery and reboot
Update busybox and try installing scripts again
Convert your partition to ext3
Change your kernel to 2.6
2. Mount2SD ~apps update after every boot?
Turn cache off in app
Turn safe mode off
Clear cache and dalvik ~fix permissions ~reboot
Common issues after flashing:
1. I get status 7 error?
Open archive with Bluetooth file manager and check archive integrity
Try different compression method(thanks hpsgill)
Delete system apps
2. I get status 0 error?
Update binary used is different
Exchanged update binary from a working zip to this one
Other errors can be cured by changing recovery .
http://forum.xda-developers.com/showthread.php?p=38469360
Common issues after flashing Rom:
1. Always do a clean install
To wipe everything except /sdcard.
Even in /sdcard delete Android /data after backup
2. No I won't listen. I want to do you a dirty install. Show me how?
Your choice
http://forum.xda-developers.com/showthread.php?p=35903694
3. I get force closes of all apps?
Dalvik problem.
Clear cache and dalvik cache and reboot
4.I get force close of a specific app?
If it's a paid app, then you need to change your Android id to your original Id with Android id changer /titanium backup
Not a paid app?
Clear cache and data of that app and reboot
Fix permissions
5.reboot after reboot?
Thanks bhargz16
Kernel problem. Change kernel
GAPPS:
1. This gapp always force closes?
A. If it's a gapp found on play, just uninstall that gapp from system using titanium backup and then reboot and install from play store.
B.if not found on play, then try flashing a different gapps version from goo.im .
Make sure you have enough space on /system and on /cache before flashing and then flash. If not delete unused apps like stock keyboard ,etc
2. RPS5~AEC0/927/any other error while downloading apps from play?
A. Clear data cache of play store app
Reboot
B. Clear data of google services framework
Reboot
C. Remove your google account and re add it. Reboot.- this worked for me.
3. All my apps are missing from installed apps in play?
Wait for some time,if you've flashed a new Rom
Clear data and cache of play store
Reboot
Download app eric market fix *use @ your own risk *
Repeat the solution of questions 2.
Go back to main ^|^
Part 2 on next page :thumbup:
Re: [faq][newbies only][mini edition]
CPU:
1.Can you overclock?
IMO,
All overclocking burns nand.
It's just a matter of sooner /later.
Read this post before attempting anything
http://forum.xda-developers.com/showthread.php?p=38445346
Burnt nand recovery procedures here ~~the third post below this post
http://forum.xda-developers.com/showthread.php?p=38098622
The links below are old. All latest Roms come with overclocked burning kernels.
cm10:
http://forum.xda-developers.com/showthread.php?p=38189883
cm10.1:
http://forum.xda-developers.com/showthread.php?p=38336080
gpu oc
http://forum.xda-developers.com/showthread.php?p=38331698
cpu oc
2. Governors ~what are they?
As the name says they govern when the cpu should go to higher speed and when they should sleep
Performance governor always keep your phone at Max
Powersave keeps your cpu always at low
USB :
1. Flashed kernel 3 and USB doesn't work.?
Flash kernel 2 back.
2. I want to know how to fix USB +kernel 3?
Don't know
3. Can I have usb otg ?
No, not yet.
SCREEN AND POWER BUTTON and soft keys:
1.SCREEN turns on after turning off ?
A. Some apps are trying to make screen on. After screen turns on, go to settings immediately and open running applications, you may be able to find the culprit. It's probably the app, which is restarting. Some apps like lock any app screen etc. Logs could be helpful.
B. Some users reported it could be a hardware problem -look below for power button issues.
C. Some users reported it could be a script problem (rare )
2. My home screen button and /or search buttons doesn't work?
A. Did you do a dirty install of new Rom
Clear cache and dalvik and fix permissions and reboot
B. Copy com.Android.providers.settings /databases from your previous nandroid backups(use yaffs file manager /nandroid manager)and paste it in it's respective location now (paste it using file manager in recovery )
C. If that doesn't work, clean install again
Tech savvy? ~search for device provisioned 1 in cyanogen forums
http://forum.xda-developers.com/showthread.php?p=38633404
3. Power button doesn't work properly ?
A. If it's not a software problem(try the above solution first),then you broke it.
If you broke it, avoid using the power button anymore-use attached scripts indeed.
There are apps in market to simulate power keys.
Or
http://forum.xda-developers.com/showthread.php?p=38633404
Go back to main ^|^
Re: [faq][newbies only][mini edition]
Miscellaneous topics:
Subject to change without prior notification
Developers:
1. Who are the developers that make these roms?
1. Cute_prince
2.sakîndia123
3.derefas
4.lirokoa
5.liverpool fan
6.bhargz16
7.nihar.g
8.ngolralph
And many others. The above are the developers of the roms that I used and present in no order.
2. Why doesn't sakindia123 update the OP ?
Disclaimer: Since it is one of the most faq by newbie,I'm forced to discuss here. I personally do not know sakîndia. If you still want more info, contact senior member hpsgill
You see.. He does nothing without reason. If he doesn't, then the last build present in op will be more /less equal to the latest build. There are other reasons ,which if I had to speak of them all, time wouldn't let me and I would have to deal with flaming members and mods and deleted posts and locked threads . Furthermore that question is well out of the scope of this thread. You are instructed not to ask this question any where.
YOU HAVE BEEN WARNED.
3. How can I contact these developers?
You can by studying Android development and codes, bccms,404s,tr2s and then talking to them. You'll have better luck talking with non recognized developers than the rds.
And try discussion threads .
4. Why doesn't a developer answer my question? (I'm being polite here)
Because the developer doesn't know the answer
w.r.f to http://forum.xda-developers.com/showthread.php?p=38095857
Or your question has already been answered. Try searching for your question at the least 10 pages back.
or your question is too silly to answer
Or your question is not seen ,because they don't have time .
5. Why do they do this ?
For passion of development, addicted, and for learning purposes.
So, that means they don't work for you. They don't help you. They do what they want.
6. I feel a emptiness around forum members. Was there a developer who worked here, yet left without goodbye?
Well not sure about goodbye, but yes his name is jaggyjags.
sakIndia123 came only late and his first work his cranium kernel, which he abandoned like it was nothing.. buried it along with jags. Cruel things did happen before you were here.
Go back to main ^|^
Members:
1. Why won't members answer my question?
Again, thanks to bhargz16
http://forum.xda-developers.com/showthread.php?p=38095857
Or question has already been answered over and over again. Try searching for your question and read at the least 10 pages back.
Or they don't want to help you
Or may be you aren't polite
Or they want thanks
2. Why do they want thanks?
You see.. you should hit thanks for them in order for them to reply
3. Why hit thanks?
Because they are thankaholics .
This addiction
Some call it want,
For some it's need
Some call it greed
And some call it hunger
And some childish foolishness
Never hit thanks, unless you mean it. Never sell yourself short. Mean it, then hit it.
http://forum.xda-developers.com/showthread.php?p=32867800
My first thread closed by mods
:crying:
Having said that, please do be grateful for what you receive. Hitting thanks is like giving a eternal reputation mark on them rather than just saying it. Saying just makes a temporary mark. Get it. 
4.what is spam?
Spam is going out of topic . It never should be done in dev threads unless thread is dead.
Some do the work of mods pretending to be mods.
5.who are mods?
They are moderators who have power to ban anyone at will (in short )
And they are losing patience
http://forum.xda-developers.com/showthread.php?p=37950595
6.Can I spam here?
Feel free to speak what you want..
7. If I feel something wrong is going on /flaming /threatening, who should I report to?
You can use the report system~that (!) mark over every post. Click it and your issue will be resolved within a hour(probably ).
Go back to main ^|^
[color="red"] [b]
0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1
0„30†2Moved by touch0160†640„30†3Inc.
0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨1
0. What's burnt nand?
It's condition caused by overclocking(oc)[CPU oc ,to be specific. For gpu oc,go to the last part of this post question 10 ] resulting in bad blocks all over your system, data, cache and recovery.
Important: Use diskusage app to determine size. Don't go by phone's inbuilt settings
A case of burned /system partition in cm10 beta6 running overnight:
Uploaded with ImageShack.us
A late case of burnt nand of /data :
Uploaded with ImageShack.us
1 &2:Not applicable anymore. Peace!
3. No one has burnt thier nand*it's just some people think that thier nand is burnt * is this true?
Well, I'm sure, going through the forums and q &a ,I know that people have indeed burnt thier nands and some just by using the overclocked kernel without even overclocking.
Sources:
http://forum.xda-developers.com/showthread.php?t=1847002&page=400
http://forum.xda-developers.com/showthread.php?t=2243719
http://forum.xda-developers.com/showthread.php?p=39985385
http://forum.xda-developers.com/showthread.php?p=39799173
http://forum.xda-developers.com/showthread.php?p=39439861
http://forum.xda-developers.com/showthread.php?p=39428922
http://forum.xda-developers.com/showthread.php?p=39402187
http://forum.xda-developers.com/showthread.php?p=38941663
http://forum.xda-developers.com/showthread.php?p=39216556
http://forum.xda-developers.com/showthread.php?p=38945489
http://forum.xda-developers.com/showthread.php?p=39197918
http://forum.xda-developers.com/showthread.php?p=39169697
http://forum.xda-developers.com/showthread.php?p=38657723
http://forum.xda-developers.com/showthread.php?p=40616272
http://forum.xda-developers.com/showthread.php?p=39331139
But below is a strong correlation with bad block proof between overclocking and burnt recovery. Yes it burns recovery too.
http://forum.xda-developers.com/showthread.php?p=39196574
THE ABOVE LINKED POSTS ARE MOSTLY SOLVED BY ME OR SENIOR MEMBER S, BUT SOME HAVE LOST THEIR DEVICES. IF YOU CAN'T FIND THE ANSWER HERE, I SUGGEST YOU READ ALL THE LINKED POSTS-VARIOUS DIFFERENT METHODS HAVE BEEN EMPLOYED.,WHICH ARE TOO LONG TO EXPLAIN HERE. READ AND READ-YOU'LL FIND.
4. What are the symptoms of burnt nand?
Early symptoms:
You'll notice a strong drop in your free space in /data
Late symptoms:
/data free space is Nil /below 50%of what you saw before
Error in /cache /recovery/log.
Error in /cache/recovery/last log.Not readable.
No apps can be installed
Rom lags like hell
No Rom can be flashed /boots
Previous nandroids ,which are successfully restored before fails to restore now.
Really abrupt and fast restores with twrp
RUU cannot be done ~user data(mtd5) fail. System fail (mtd3)
5. How can I diagnose burnt nand early?
If you suspect burnt nand ,
1.Watch out for free space in /data and watch out for sharp reduction.
2.Download this app Disk Usage and watch out for increase in system data in /data
http://forum.xda-developers.com/showthread.php?p=39464989
3.Make a dmesg and look for these errors
http://forum.xda-developers.com/showthread.php?p=36834988
4.Definitive method is this :
shahrooz_ra said:
hello
is there any linux terminal command for check badblock on nand memory?
Click to expand...
Click to collapse
1.DOWNLOAD THE TERMINAL.ZIP ATTACHED BELOW
2.EXTRACT TERMINAL.ZIP INTO /SDCARD/lol [create a folder named lol[small letters ]in SDcard, if there already isn't one ]
3.Open terminal emulator on your phone
4.type or copy and paste this code and press enter
Code:
su
cp /sdcard/lol/runme.sh /r.sh
chmod 0755 /r.sh
/r.sh
5.if it doesn't work first time, paste twice.
6.If pasting twice doesn't work, type each code one by one -you'll surely get it. Come on-its just 4 lines -type it lazy!
And Now you'll see the number of bad blocks you've got.
You can also Flash the zip below[for which you have to go to recovery ]or execute the attached script badblocks.sh as root.
6. What are the parts affected by burning?
Proved to affect
/Data
/system
/cache
/recovery
Rest is unknown
7. Ok I managed to burn my nand What are the recovery procedures available?
I SIMPLIFIED THINGS HERE BY MAKING A FLASHABLE FLASH_ERASE. ZIP[Code named FLASH_ERASEmadeflashablebyBANNED.zip ] it works with twrp2.5 to flash_erase needed partitions. However not tested fully. Problem? Post here.
Other long procedures:
Cute prince recovery procedure:
http://forum.xda-developers.com/showthread.php?p=36868966
I think Cute prince missed this .Just add this at the end
Code:
./flash_erase -N /dev/mtd/mtd3 0 0
7.1 I GET FLASH ERASE NOT FOUND?
Flash the flash_erasemadeflashablebyBANNED.zip
Derefas recovery procedure:
derefas was the one who actually gave the idea of recovering nand
http://forum.xda-developers.com/showthread.php?p=36867557
Sachin Thomas recovery procedure
Developed lately *can be done on phone itself */if it didn't involve recovery /*
http://forum.xda-developers.com/showthread.php?p=38941897
Recovery recoveriNG procedure (bhargz16)
http://forum.xda-developers.com/showthread.php?p=39198068
8. I can't find my answer here?
Go to official burnt nand discussion thread
http://forum.xda-developers.com/showthread.php?t=2183130
Or you can ask your questions here.
9.can I Flash any other kernel to prevent overclocking?
You can Flash garuda2.6
Link in latest links post page 1.
http://forum.xda-developers.com/showthread.php?p=38098567
Side effects:
http://forum.xda-developers.com/showthread.php?p=39452607
10. Some more links:
Unknown recovery procedure
http://forum.xda-developers.com/showthread.php?p=36836090
MTD status report:
http://forum.xda-developers.com/showthread.php?p=36837173
11. Cannot go to recovery /burnt recovery /unable to flash recovery?
Not sure of the exact command,but will work.
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device [do ruu here, if you haven't been able to enter hboot before]
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
12. GPU OC ?
gpu oc has been reverted along with CPU oc by sak for burnt nand. But may be added later. but not present in cm released on or two months before 9 may13.
12.1 is it safe?
I don't know. CPU oc did provide burnt nand and bad blocks. Gpu oc may also do some things, which may not be seen as of now. I've seen one case complaining that, after using Cyanogen and going back to stock - games started lagging, which did not lag, when he was in stock before. The reliability is doubtful. But not much people go back to stock either -so not much can be said.
12.2 do you recommend it?
"If any provider of any oc removes the "AS IS" tag and take responsibility,if something happens, then I'll probably may use that oc,otherwise count me out".
12.3 How to remove gpu oc ?
Its present in kernel. Flash another kernel. Or modify source and compile yourself.
Present at arch/arm/mach-msm/msm7x27a.c- kernel source.
Try here
Normal [bus, Gpu] is [0,133330000],[160000000,192000000],[200000000,245760000] I think.
13. Was there anyone unable to recover and lost thier device for ever?
AFAIK,
"The lost thier device for ever list RIP "
Ghostking
Hawk378
And May be many more
Legend *:
Attachment list:
***********************************************************VERY IMPORTANT : UNDER CLOCK BELOW 300MHZ ,IF YOU ARE USING ZIPS WHILE SYSTEM IS RUNNING.AFTER THE TESTS, YOU MAY OVER CLOCK AS YOU WISH. ********************************************************************************************
Provided "AS IS"
1- script to detect badblocks by banned.
2-flashable zip to detect badblocks by btfb0
3-Terminal method to detect bad blocks by banned .
4-flashable zip to detect bad blocks by banned.
5- Recovery procedure to delete bad blocks- Made flashable by BANNED.
All zips posted here has readme.txt files inside it-which are self explanatory to that particular zip.
*USE AT YOUR OWN RISK*
Re: [faq][newbies only][mini edition]
I have a question not answered here?
Post your question in the q&a section after making sure that your question hasn't already been asked.
Please use search button on the top right to make sure that your question hasn't already been asked. And it'll help you to find more answers.
Follow detailed instructions here
http://forum.xda-developers.com/showthread.php?p=33608527
And post with logcat increases your chances of resolving the problem
ADB
What is logcat and ADB?
Special thanks to akshat.shenoy
http://forum.xda-developers.com/showthread.php?p=37805872
He'll explain things better
Basics of ADB:
http://forum.xda-developers.com/showthread.php?p=9936674
Partition and wipe SD ext with ADB:
http://forum.xda-developers.com/showthread.php?p=38706881
Re: [faq][newbies only][mini edition]
reserved
Re: [faq][newbies only][mini edition]
MINI Tips and tricks:▶?
1.How can I apply cm9/10 themes?
http://forum.xda-developers.com/showthread.php?p=35530897
Download the zip from here, read instructions there and flash it in recovery
Now you can use any HDPI themes on your Pico
Thanks ngoloralph
2. How do I change fonts?
Download Rom toolbox lite and go to font installer;
A. If you're on stock, the rest is automatic
B.if you're on cyanogen 9/10/11,if you change the droid sans /others as recommended by app, you'll end up in boot loop (possibly because of symlinking of robot sans & droid sans )
In such a case go to preferences and click to overwrite only roboto regular font and everything will be fine.
Take a look
Uploaded with ImageShack.us
3. How do I add a new language support to my device?
Note: no new language gui can be added by this method. This only adds support. Instead of seeing boxes, you may see your language. If you want full language support, you can go to this abandoned thread.?? http://forum.xda-developers.com/showthread.php?p=40890599 ??
Language support can simply be added by adding a Android supported language font file in /system /fonts and give it permissions rw r. r.(font files can be found all over xda )
Step 2. Open system /etc /fallbackfonts.xml...
There should be a lot of font file names there.. just delete a font name that you don't want and add your font file name (the name of the file which you put in /system /fonts)
In there.
Practice makes perfect.
This method however doesn't work /only partly works for complex languages /script like Hindi Arabic etc.
DID YOU KNOW?
1. Long pressing reboot button (in the menu after pressing power key) will get you into safe mode
2. Long pressing power keys and volume keys + and- for more than 30 seconds will reboot your device (tk to hrkh83)
3. Repeatedly pressing certain options(like Android version) in the about menu in settings(on cyanogen ) will take you into different settings (tk liverpoolfan)
Go back to main ^|^
Battery drain
BATTERY DRAIN
Of course, we're gonna talk about drain.
Before we start, I want to disprove some prevalent concepts
1. Battery calibration
It is supposed to increase Battery capacity and increase Battery life and it makes your phone to show the correct Battery on the notification bar.
FALSE
It doesn't do any of those. Calibration is just deleting Batterystats.bin file. That file holds info about how many seconds each apps were running for.typically it's blameometer. It shows the information you see in the battery chart in your settings. Nothing more.
Source: article
2. Cycling your battery life from 0 to 100 and 100 to 0 will typically increase Battery life. Further more you should make sure it comes to zero by turning on the phone,every time it got switched off on it's own.
FALSE AGAIN
Nothing could destroy your Li-On Battery than extreme low voltage. You can be sure that this will destroy your battery life more than anything. During storage it's recommended to keep the battery in cool place with 40%Battery.
So, don't use any battery draining app from market.
Ok, since we took out the false foundation, it's time to put some true working tips to save your battery during usage and it's overall life
1. It's recommended to charge as often as possible ~every time you get a socket. Though not to keep @100 all the time. Overcharging theoretically may damage your battery, but your phone comes with various safety mechanisms to prevent charging after that.
2. Limit the number of apps. Definitely would produce good Battery.
3. Limit the number of apps, that run in background all the time.
Typical example would be facebook.
PERFORMANCE:
4.Disable autostarts for all apps, that you don't use much~using autostart manager.
Disabling autostarts for the clock app will make you get up late. Use common sense.
This alone should drastically improve your performance
5.Use lightweight launchers ~Nova.
Go (any go products) is not advisable
6.Post ICS, Disable media scanner receiver.
You can use elixir app to disable media scanner receiver. This will scan your SDcard over and over again resulting in Battery drain,which is significant, if you use a bigger SD. Use media scanner root to enable and disable.
As far as the usual ones,
7. Disable autobrightness
8. Keep screen @ minimum brightness
9. Disable autorotation
10. Disable location services.
GAPPS:
11. Disable GSF (google services framework ) receivers ~the ones with gtalk on it.
12. Disable auto sync
You can use timedo /timer Android to turn on sync twice /thrice daily.
13. Reduce number of accounts. Better to keep single than three accounts.
14. Good internet connection. Amount of energy taken to re connect is supposed to be far more than amount needed to keep a connection.
15. Undervolt/with underclock
RECOMMENDED APPS:
1.BETTER BATTERY STATS ~free for xda.
2. Onepower guard
I haven't found satisfying results with this app, but still try it out
3.greenIFY
I haven't used this @ all.
4. Any app, that is used to reduce /increase heartbeat sent to google servers.
Well, that's all I've learnt as of now.
Re: [faq][newbies only][mini edition]
Recommended apps section (only free)
Top apps
0. Superuser by koush (Clockworkmod)
1. Titanium backup
2. Efficient backup
3. Floating logcat ~logcat extreme
4. Catlog
5. Aroma file manager (recovery use only)
6 .Es file explorer
6.1 es file explorer v2
7. Yaffs file manager
8. App extractor
8.1 nandroid manager
9. Loaderdroid
10. Xda app
11. Elixir (much useful to disable app components than it's actual use)
12. Android pro widgets(similar to HTC friendstream)
13. Nova launcher
14. Timedo
15. Live logcat lite
16. Rom toolbox lite
17. Screen stand by root(turn off screen without making phone to sleep)
18. Disk Usage
Launcher:
1. Nova
2. Apex
Downloaders:
Loaderdroid
Multimedia players:
Video
mx
bs
qq
Audio
Ttpod
Equalizers
NOOZOXIDE REWIRE PRO
Walkman sound enhancements
Awesome beats
Cyanogen Dsp(better than stock )
Equalizer from market.
Cam/corDer /video recorder:
Camera:
Camera 360
ucam
spycam
Video recorder
ucam
Zoom camera
Camera magix
Browsers:
Fast and server based
Uc browser mini
Opera mini
Opera mobile
uc browser
Puffin browser
Full fledged browsers
Firefox
Dolphin
Google chrome beta
Chrome
KEYBOARDS ?
Touchpal keyboard
mĺ has internet permisn wid emoji
Office apps:
Kingsoft office(better than paid apps)
Zip extractors:
Zarchiver(ant-one)
Screen off(w/wake lock):
Screen stand-by
File managers:
ES explorer
Fx file explorer
Call recorders:
No known call recorders are working.
Stocks:
Personal finance
Superuser:
Superuser by koush ~open source&free
Super su ~made pro free after the release of prior~closed source ~
⇧Go back to main ♠
THE END.
© All rights reserved 2013?
Autoramdisk exchange alpha
MINI ADVANCED SECTION:
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.071 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Update:
I have got it to work and complete
http://forum.xda-developers.com/showthread.php?p=40035607
Old post: too lazy to delete
Present condition:
Hi. I cannot get it to work on HTC Pico yet .It may work on other phones. If someone can, please feel free to complete it provided you give proper credits And you do not make money out of this.
What's this?
It's a procedure (wip) to Flash any kernel without the need to change ramdisk.
As new kernel gets released, you don't need to change ramdisk to suit your Rom.
Automated procedure:
Open any kernel.zip with any zip extractor on your phone
Copy the script below and paste it in updater-script present in meta~inf/com/google/Android
(delete any other things written there. )
Code:
package_extract_dir("bin","/tmp");
set_perm(0, 0, 0755, "/tmp/busybox");
set_perm(0, 0, 0755, "/tmp/unpack-bootimg");
set_perm(0, 0, 0755, "/tmp/mkbootimg");
set_perm(0, 0, 0755, "/tmp/dump_image");
run_program("/sbin/dump_image","boot","/tmp/oldboot.img");
run_program("/tmp/unpack-bootimg", "-i","/tmp/oldboot.img","-o","/tmp");
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/tmp/busybox", "mkdir","/tmp/boot");
run_program("/tmp/unpack-bootimg", "-i","/tmp/boot.img","-o","/tmp/boot");
run_program("/tmp/busybox", "rm","-r","/tmp/kernel");
run_program("/tmp/busybox", "mv","/tmp/boot/kernel","/tmp/kernel");
run_program("/tmp/mkbootimg", "--ramdisk","/tmp/ramdisk.cpio.gz","--kernel","/tmp/kernel","-o","/tmp/newboot.img");
write_raw_image("/tmp/newboot.img", "boot");
delete_recursive("/tmp/newboot.img", "/tmp/boot", "/tmp/oldboot.img", "/tmp/kernel", "/tmp/ramdisk.cpio.gz","/tmp/boot.img", "/tmp/busybox", "/tmp/unpack-bootimg", "/tmp/mkbootimg");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
Download zip files from the source link below
Extract it and copy the bin folder from there to your kernel folder directly.
There should be 3 folders in your kernel folder ~bin folder, meta inf folder, system folder and boot.img
Now compress it and Flash
Note that this is only applicable to change ramdisk. If the boot. Img needs more work than that, it won't work. Essentially, it won't work on sense4 compiled kernels and vice versa
Manual terminal emulator method:
Alright guys, one last tutorial from me making my last mark here .This tutorial is not tested fully and probably never will be due to lack of time. And it will work for sure ~but May have syntax errors.
Credits:
1.trevd for arm executable binaries.
2.Xda university.
Requirements:
1.Any Android 2.3+ rooted
2.Android terminal emulator
3.arm executable unpack-bootimg binary and mkbootimg binaries (find it below )
History:
I wanted to change ramdisk for kernels for a long time on phone itself ~probably for a year or more . But anyone who tried to unpack using normal unzip apps would've noticed that other data.img and even system.img in clockworkmod could be unpacked easily, but not the boot.img and recovery.img. When I searched to unpack, it was easy with computers using the unpackbootimg binary for Linux. Problem was it wasn't cross compatible with our phones . So, I was searching for quite a while,until I found trev on xda university and he had made arm executable binaries for unpacking, repacking. Actually the main reason these binaries were created was for far greater and more advanced purposes i.e. to use apply patch functions in update binary and update script to Flash ramdisk on phone without flashing the kernel itself or vice versa (AFAIK)[ The apply patch functions are used in normal ota updates for any Android phone ]. Anyway I took those binaries to unpack kernels on our phone to change ramdisk. I write this for those, who want to change ramdisk on thier phone, but had no experience in PC whatsoever. And also by doing this, I share the unpack boot image binaries by trevd for Android phone ,so that any advanced member May use it for kernel updater scripts~think about it ~one zip for all cm9/10/10.1. Ofcourse the rest is up to you. Thanks for reading
Procedure:
1.Download the zip given in source below
2.Unpack it
3.Find these two binaries in /system/bin
Unpack-bootimg and mkbootimg
4.Copy them to /system/bin and give them full execute permissions in es explorer and read/write permission for user.
5.For easy remembrance,say, b1.img is your original boot image for your Rom(and Android,say cm10 ) and b2.img is the new kernel released for cm10.1
6.You want to change the ramdisk ofb2 cm10.1 to cm10 ,so that you can Flash the new kernelb2 for your cm10
7.Create new folder in SDcard named boot and put both b1.img and b2.img there
8.Open terminal.
9.type the following code one by one
Code:
su
cd /sdcard/boot
mkdir /sdcard/boot/b1
mkdir /sdcard/boot/b2
unpack-bootimg -i /sdcard/boot/b1.img -o /sdcard/boot/b1
unpack-bootimg -i /sdcard/boot/b2.img -o /sdcard/boot/b2
rm /sdcard/boot/b2/ramdisk.cpio.gz
mv /sdcard/boot/b1/ramdisk.cpio.gz /sdcard/boot/b2/ramdisk.cpio.gz
mkbootimg --kernel /sdcard/boot/b2/kernel.img --ramdisk /sdcard/boot/b2/ramdisk.cpio.gz --base 12C00000 -o /sdcard/b2new.img
rm -r /sdcard/boot
Note: the last rm command will delete all your old kernels ~don't execute it, if you don't want to have it deleted.
10.Now you have new kernel boot image with your ramdisk in /sdcard/b2new.img
11.Put it back in the zip with it's modules and
12. Flash
13.Hoping it'll work.
14.That's the end.
Source and binaries here:
http://forum.xda-developers.com/showthread.php?p=36931024
For dream and Sapphire models, you can use the binaries created by koush ~ which is found in his github ~any kernel project.
I'll probably be leaving soon
Kind of feel like working for xda. I guess sak and others would probably feel like it later. It's been great while it lasted. So this is probably my last project. If I did have some extra hardware during this period, things May have been different. It's good, while it lasted.
"The fantasy of a dream is that, it's still a dream, when it becomes reality, then it's no more a dream and the fantasy is lost. "
「Good bye xda」
So long:angel:
Re: [faq][newbies only][mini edition]
one more
The Infamous BUILD.PROP Tweaks :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
from
http://www.droidforums.net/forum/droid-4-roms/234899-examining-build-prop-tweaks.html
Guess that'll end this hoax for good.
One thing that was useful for me was this
http://www.modaco.com/topic/347274-guide-making-cm-utilise-both-cache-and-data-for-dalvik-cache/
Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Very nice Thanks for your hard work and good luck
CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).
Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.
Thanks
Thanks
Where are the screenshots?
please add some screenshots.
deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.
Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.
Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.
Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:
Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.
Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work
Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.
Welcome to the official thread for Intex Cloud Tread.
You can discuss anything related to the phone here. (All links are Google Drive and XDA)
Make: INTEX
Model: Cloud Tread
Stock ROM: Android 5.1
Kernel: 3.10.72 (Remember this while looking for ROMs to port)
SOC: MT6591 (The same as MT6592, so you can easily port ROMs)
RECOVERY
Type: TWRP
Version: 3.2.1 EXPERIMENTAL
Kernel: 3.10.72
Supports: MT6591/MT6592
Download (Note: Old backups doesn't' work with this one.)
*Might have a couple of bugs (CPU Temperature doesn't work, ADB Backup doesn't work), but works for backups and restores and flashing and mounting and ADB Sideloads. This is an experimental build. Use with caution.
Type: TWRP
Version: 3.1.0
Kernel: 3.10.72
Supports: MT6591/MT6592
Download New Fixed Version Download (Note: Old backups doesn't' work with this one.)
OLD Version (This was a half-assed port from Excite Prime that Identifies device as Excite Prime and has a lot of other bugs)
Download OLD Version
Instructions:
1. Download and install SP Flash Tools
2. Start it and go to Download tab.
3. Now, in the scatter loading file box open the SCATTER Text you downloaded. (Link below)
4. Make sure the drop down box is selected at Download Only.
5. Untick all boxes except recovery and double click on the location part of the recovery row.
*DON'T PLUG YOUR PHONE IN NOW*
6. Select the recovery you downloaded from here and click the Download button.
7. Now turn the phone off or remove its battery and plug it in.
The necessary drivers should install and wait for a few seconds until a green tick or circle comes on the screen.
There, one custom recovery for INTEX Cloud Tread has been flashed.
SCATTER FILE - Download (You will need it to use with SP Flash Tool)
If you want the STOCK RECOVERY download it from here.
ROOT
Type: SuperSU
Download
Instructions:
1. Copy the file to your SD Card.
2. Press Volume Up+Power to boot into recovery when the phone is off.
3. There go to Install > Select Storage > MicroSD > SuperSU.zip.
4. Un-check Reboot Automatically. (This may clear the dalvik-cache which is recommended but not necessary and might take some time to boot up the first time.)
5. Then Swipe to flash and reboot.
Congratulations! You are now rooted without the annoying KingUser.
XPOSED
Installer: v89 sdk 22
Download
Uninstaller: Download
Instructions:
Flash XPOSED using the same method used to flash SuperSU above.
After flashing Clear Dalvik-cache (Option is on the same screen) and boot into android and install below APK to manage XPOSED
XPOSED APK v3.1.5
Uninstallation Instructions are also the same.
STOCK ROM - Download
Flash with SP Flash Tools.
After flashing stock ROM from the above link, untick all the boxes and tick only the boot image section.
Now download and select this boot image and flash.
This is because the boot image included in the above linked ROM has screen flickering issues.
Intex Cloud Tread Battery and Performance Optimization
First download and flash this "IntexDebloat.zip" file.
It will remove the bloatware that came with the phone. (User uninstallable apps are not included)
Intex Keypad (Which when automatically updates to Mox Keypad is a privacy nightmare) is also removed. Use Gboard or the stock AOSP keyboard in the phone.
Now make sure you are rooted and have xposed installed.
Install these below apps from playstore or apkmirror or from anywhere
1. Greenify
2. Kernel Adiutor
3. L Speed
4. Busybox
5. Powernap 0.7a (optional) (and don't download the newer versions or update from play store)
After installing all of the above follow these tutorials in order.
#BusyBox - Preparing the phone
Open busybox, grant SuperUser permissions and install it. Now you can uninstall the app if you don't need it.
#Kernel Adiutor - Custom Governor Tunings
Disabling MTK Performance Service
This is one of those situations where a good idea is implemented in a not so good way. Performance service can provide you good performance at a very dear cost of battery life and it can also override or worse play along and consume more power with the below tweaks. So you should disable it before attempting these.
Open Kernel Adiutor, grant su permissions and in the sidebar goto build prop tab
There search for ro.mtk_perfservice_support
Change its value from 1 to 0.
Now we are going to tune the Governor.
Believe me when I say this I've been tuning this phone for over two years now with 100s of different configurations and these are the two best configurations for a balance between power consumption and performance.
Option one: Hotplug with rush function and fast sampling rate (My favorite)
Open Kernel Adiutor > CPU tab.
Make sure the governor is set to Hotplug.
Now change the following Governor tunables;
Code:
cpu_down_avg_times=20
cpu_down_differential=1
cpu_input_boost_enable=0
cpu_rush_boost_enable=1
cpu_rush_threshold=98
down_differential=5
sampling_rate=30000
up_threshold=99
This should give you good performance while maintaining good battery life
Option 2: Hotplug with no rush and high sampling rate (This is also good for battery life but a bit low on performance)
Code:
cpu_down_avg_times=20
cpu_down_threshold=20
cpu_input_boost_enable=0
cpu_rush_boost_enable=0
cpu_up_threshold=90
down_differential=5
sampling_rate=73000
up_threshold=97
No matter what you choose your battery life is hugely dependent on what you choose to do with your device. I usually get 5h of *continuous* SOT on auto brightness with these settings on WiFi and browsing. YMMV.
Some people might suggest setting
ignore_nice_load=1 for more battey life as well. But this phone kinda categorizes everything as nice processes and will only run on 1-2 cores @728MHz if you enable that without MTK Performance Service. It did got me more than 7h SOT but it was basically unusable.
Make sure you enable apply on boot on each page you change to make it apply on each boot!
Now go to I/O Scheduler tab.
There change scheduler to noop for internal storage and sd card if you have one.
Also goto settings and change the apply on boot delay to instant.
#LSpeed, Paget96's masterpiece!
Open L Speed, finish the tutorial without enabling anything and do as follows
Sidebar > Main section
Disable Debugging: Enabled
Window Animation Scale: 0.5x
Transition Animation Scale: 0.5x
(Don't change animator duration scale as it will mess up every animations in the device)
CPU Tuner
Don't enable anything in here, we already tuned our governor with our own values in Kernel Adiutor.
Battery
Battery Improvement: Enabled
I/O Tweaks
SD Tweak: Enabled (If you have a SD Card)
I/O Boost: Enabled
Partition Remount: Enabled
Disable I/O stats: Enabled
Don't enable scheduler tuner as we choose noop in kernel adiutor which can't be tuned!
RAM Manager
You will be tempted to change a lot of things here but don't. It will only make it worse. Just change the below settings
Virtual Memory Tweaks: Battery
Cache Reclaiming: 50%
OOM Killer: Enabled
OOM Dump Tasks: Disabled
Also you can do a fstrim as well if you would like to. No probs.
Now go to settings and chage the apply on boot delay to instant.
#Greenify
Install greenify, enable the module in xposed installer and restart. After boot, make sure you wait till L Speed and Kernel Adiutor apply their settings.
Now open greenify, goto its settings, xposed based features and enable the below
Wakeup timer coalescing
Telephony Wakeup
Greenifying System apps
Now go back, select add apps and on the top right corner, select the three dot button and choose Show All.
Now add every app in the phone to greenify. (Don't worry greenify only hibernates app that consumes battery, those who don't consume battery in the background will be shown as background free.)
Don't add the following apps:
Bluetooth
MTK NLP Service
Phone
Phone (System)
Google play Services
Google Play Services (Persistent)
Voicecommand
Download manager
Calendar storage
Play store
Google account manager
com.mediatek.voiceextension
Google backup transport
Google calendar sync
Google contacts sync
Kernel Adiutor
L Speed
Prevent Pocket Dials
Click to expand...
Click to collapse
^These will start again and will consume more battery if you hibernate them.
#Power Nap (Optional)
Only install v0.7a (link above).
It's the basic stuff. Install, enable in xposed installer, open, enable the first option, add L Speed and Kernel Adiutor to it's whitelist. And reboot.
And that's it! Make sure you add any new app you install to greenify. Some say you don't need to hibernate everything, only the rogue apps. But Greenify itself can decide whether it should hibernate an app or not. So that's fine.
This took me a long time to write and more importantly this took me two years of experimentations to find. (Especially the governor tunings). Hope you guys enjoy it.
In addition to this I also recommend using Nova Launcher as the stock launcher is basically adware and follow the usual "don't install every crap-booster-cleaner-app you see" advice to maintain your device.
Device not revealed.
When I start MTK Droid tool, it says,"The device isn't revealed. Connect or reconnect a cable." I waited for like half an hour still the issue persists.
MTK Droid doesn't work that easily with phones newer than KitKat because of an incompatible adb. The solution is to manually replace the adb while MTK Droid Tools is running to make it work.
You can use this script I made that will automate the process and saves you the hassle.
https://forum.xda-developers.com/android/general/fix-impossible-to-start-adb-error-t3582571
Remember: Keep the phone connected with USB Debugging enabled before using the above script.
If it fails, try again it will work. :good:
Ritesh Sachan said:
When I start MTK Droid tool, it says,"The device isn't revealed. Connect or reconnect a cable." I waited for like half an hour still the issue persists.
Click to expand...
Click to collapse
Bump! :highfive:
Yes it did work, but on running mtk droid tools the icon on the bottom left corner shows yellow colour. So to fix that I clicked on the ROOT option next to the ADB Terminal option. I granted the access through my phone. Few seconds later the icon turns green for few milliseconds and it quickly turns into red colour saying "CONNECTION LOST." Even though my device was connected with USB Debugging ON. HELP ME.
You cant use MTKDroid to root the phone. Try with TWRP and SuperSu.zip
Now even after rooting MTKDroid will report that the phone is not rooted.
That's another security feature of Android. The adbd interface will work on non root mode even after rooting. You have to install adbd insecure apk (paid on google play, but available for free here on its XDA thread) by chainfire to change it to root mode.
Link to adbd - https://forum.xda-developers.com/showthread.php?t=1687590
Adithya FRK said:
Welcome to the official thread for Intex Cloud Tread.
You can discuss anything related to the phone here. (All links are Google Drive and XDA)
Make: INTEX
Model: Cloud Tread
Stock ROM: Android 5.1
Kernel: 3.10.72 (Remember this while looking for ROMs to port)
SOC: MT6591 (The same as MT6592, so you can easily port ROMs)
RECOVERY
Type: TWRP
Version: 3.1.0
Kernel: 3.10.72
Supports: MT6591/MT6592
Download
Instructions:
1. Download and install SP Flash Tools
2. Start it and go to Download tab.
3. Now, in the scatter loading file box open the SCATTER Text you downloaded. (Link below)
4. Make sure the drop down box is selected at Download Only.
5. Untick all boxes except recovery and double click on the location part of the recovery row.
*DON'T PLUG YOUR PHONE IN NOW*
6. Select the recovery you downloaded from here and click the Download button.
7. Now turn the phone off or remove its battery and plug it in.
The necessary drivers should install and wait for a few seconds until a green tick or circle comes on the screen.
There, one custom recovery for INTEX Cloud Tread has been flashed.
SCATTER FILE - Download (You will need it to use with SP Flash Tool)
If you want the STOCK RECOVERY download it from here.
ROOT
Type: SuperSU
Download
Instructions:
1. Copy the file to your SD Card.
2. Press Volume Up+Power to boot into recovery when the phone is off.
3. There go to Install > Select Storage > MicroSD > SuperSU.zip.
4. Un-check Reboot Automatically. (This may clear the dalvik-cache which is recommended but not necessary and might take some time to boot up the first time.)
5. Then Swipe to flash and reboot.
Congratulations! You are now rooted without the annoying KingUser.
XPOSED
Installer: v87 sdk 22
Download
Uninstaller: Download
Instructions:
Flash XPOSED using the same method used to flash SuperSU above.
After flashing Clear Dalvik-cache (Option is on the same screen) and boot into android and install below APK to manage XPOSED
XPOSED APK v3.1.1
Uninstallation Instructions are also the same.
Recommended and tested Mods:
Ultimate Performance MOD by sohamsen (Tweaks - Flashable with TWRP)
BootManager (XPOSED Module)
GravityBox [LP] (XPOSED Module) (Requires dalvik-cache to be cleared after changing settings to avoid SystemUI crash)
Zeus Contextual Expanded Status Header (XPOSED Module)(Requires dalvik-cache to be cleared after changing settings to avoid SystemUI crash.
Android O (Oreo) Boot Animation by -CALIBAN666-
I made a flashable ZIP here. In case you want the stock animation back, flash this.
If you did encounter a SystemUI crash after enabling some XPOSED module you can boot into twrp and Deleting the folder 'conf' from /data/dev.robv.android.xposed.installer to disable the XPOSED modules without uninstalling it altogether.
Thanks: rovo89 for XPOSED for Lollipop.
If this guide has been helpful for you, please hit thanks.
Click to expand...
Click to collapse
Awesome work Adithya ..have been looking for custom recovery for quiet long....and your twrp worked like a charm..Thankyou....just need to point u out that supersu link is not working....keep-up the good work,will be looking forward for new custom roms for intex cloud tread from u.
jackquest said:
Awesome work Adithya ..have been looking for custom recovery for quiet long....and your twrp worked like a charm..Thankyou....just need to point u out that supersu link is not working....keep-up the good work,will be looking forward for new custom roms for intex cloud tread from u.
Click to expand...
Click to collapse
Thanks for pointing that out. I will fix it as soon as possible. Also updated some extra info about the tweaks.
i have used this boot animation (Android O (Oreo) Boot Animation by -CALIBAN666- ) ....its working perfect...thanks ... if possible upload stock rom to flash with sp flash tools(in case if phone brick) . i have tried mtk tools to backup and your zip" [FIX] 'It is impossible to start ADB' or 'Phone not revealed' error in MTKDROID Tools" ... no success ...cannot get root in mtk tools though my phone is rooted.
That is a safety measure. Install adbd insecure to enable root interface.
jackquest said:
i have used this boot animation (Android O (Oreo) Boot Animation by -CALIBAN666- ) ....its working perfect...thanks ... if possible upload stock rom to flash with sp flash tools(in case if phone brick) . i have tried mtk tools to backup and your zip" [FIX] 'It is impossible to start ADB' or 'Phone not revealed' error in MTKDROID Tools" ... no success ...cannot get root in mtk tools though my phone is rooted.
Click to expand...
Click to collapse
Stock ROM link added.
Adithya FRK said:
That is a safety measure. Install adbd insecure to enable root interface.
Click to expand...
Click to collapse
after install [2014.11.10][ROOT] adbd Insecure v2.00 i got root access on mtk tools though weird its not showing my imei numbers its button is gray...block map create scatter is gray
when i hit backup its trying to store preloader and other files on phone then error no space on phone ...only 1 file on comuputer backup its system...any way i got that repair mobile stock rom before its posted ,was not sure if its tested and safe to flash if needed
Before doing anything, please do a readback using SP Flash Tools. The scatter file is in the #1 post.
EDIT: MTKDroid never worked for me too, apart from making the scatter file.
Adithya FRK said:
Before doing anything, please do a readback using SP Flash Tools. The scatter file is in the #1 post.
EDIT: MTKDroid never worked for me too, apart from making the scatter file.
Click to expand...
Click to collapse
Thanks for the advice ,got my readback using sp tools.
Just a suggestion, TWRP is extremely good with backups. If you just want the stock ROM, goto TWRP>Backup>Tick all except data and cache. The backup size should be around 1.6 GB.
Note: SuperSU and Boot animation are in the system partition so that will also be in the backup.
Adithya can u edit EBR files ..in our phone EBR 1 is too small ....i know the method ..though not a geek to do it.
hope this link will help u even getting new roms to intex cloud tread ....... http://www.droidgyan.com/development/
jackquest said:
Adithya can u edit EBR files ..in our phone EBR 1 is too small ....i know the method ..though not a geek to do it.
Click to expand...
Click to collapse
To be fair, I am not really a geek myself. I did this because I was so desperate to get a recovery.
The EBR records doesn't seem to be too small (I got 171 apps installed) and still says I can have more.
You should try SD Maid Pro it really is a great app to clean the remains if you are rooted, you might get more space that way.
Still, it's good to learn something new and might be useful in the future if you could share how to modify the partition size.
EDIT: I can't really work on my phone now. It's kind of my day to day phone.
just go to the link http://www.droidgyan.com/development/ everything /lots of information for MTK chipset.
Updated.
Warnings about powersave governor added. (Post #2)
Next post will be about saving battery without radically affecting performance using SetCPU.