Database Info

[ROM] Adlxmod F4D "Froyo for Defy" v2.03

[Patch] Adlxmod.F4D.2.03-patch
This patch includes previous Adlxmod.F4D.2.02 patch, plus:
- Semi-transparent pulldown bar
- Updated: Google Maps 5.2
- Updated: Market 2.3.4
- Latest Cyanogen APN list (February 06, 2011)
- Fixed notification texts not always white in the DarkBar version (only applies to Adlxmod.F4D.2.03-DarkBarOnly patch)
- Note 1: This patch will restore the white notification bar. Download the new DarkBar patch to switch again to a Black bar.
- Note 2: This patch will automatically wipe the Dalvik cache, so the first reboot will take some more time (can take >5 min depending if you have many apps installed) - Don't freak out.
New Notification bar patches:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
[Patch] Adlxmod.F4D.2.02-patch
This patch includes previous Adlxmod.F4D.2.01 patch, plus:
- BlurHome selectable: You can switch to BlurHome if you like it
- Added: Adobe Flash 10.1.106.16
- Updated: Market 2.3.2
- Updated TitaniumBackup 3.7.1
- Added: Copy to Clipboard
- Added: Shrinkpipe
- Removed BlurUpdater.apk
Base rom Adlxmod "Froyo for Defy" v2.0:
- Based off UK 3.4.2-117 Froyo leak
- Fully Deodexed by me -> Theme ready
- Optionally a dark notification bar patch can be installed, see below. White patch also provide to get back at it.
- Rooted, Recovery installed
- Phone can be used with no SIM
- Includes Motoblur, but it can be skipped
- Many language supported: Spanish, English, French, Portuguese,...
- Camera flash IS working and synced
Added:
- LG Optimus 2X ringtones (some literal in chinese)
- Adlxmod splash (installed on 1rst boot, will appear on 2nd boot)
- HTC_IME Keyboard para Froyo!
- Gingerbread Keyboard
- Android Terminal Emulator
- Wireless (Wifi & Bluetooth) Tethering
- Busybox fully installed
- AOSP Email App
- Titanium 3.6.7.1
- LauncherPro 0.8.3
- Tenfar Recovery
- 3D Gallery (my mod)
- Overclock support (phone won't be OCed by default)
- SetCPU (free from XDA, please donate on the Market)
- Milestone Overclock
- Added in /system/xbin: rwsystem/rosystem, wpa_cli, zipalign, strace, ssh, sqlite3, dexopt-wrapper, tcpdump, fix_permissions, iptables,...
- Extensive APNs list (Cyanogenmod)
- Ad-Blocking
- AOSP Eclair icons & lock screen sliders
Updated:
- Market 2.2.11 + Market Fix (Paypal shows up for example)
- Google Maps 5.1.0
- Adobe FlashPlayer 10.1
Download these files:
Chinese sbf : Defy_2_2_CN.zip
Rom's Nandroid: Adlxmod.F4D.2.00.zip
Boot+Devtree : Tmo_2.2.1-3.4.2-107-boot-devtree-ONLY.sbf
SuperOneClick : SuperOneClickFor2.1.zip
(this link included Tenfar Recovery with an installer) -> use this one.
Latest Adlxmod Froyo for Defy patch: Adlxmod.F4D.2.03-patch-signed.zip
Optional files you may need:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
- Patches for fixing signal/baseband, 2g/3g
- Alternative languages (like PortugueseBR,...) for Swype: see here
Instructions: Please READ-RELAX-READ-FOLLOW
First of all, check CAREFULLY in which case you are:
Case 1:
If you come from a US T-Mobile Defy with the 3.6.90 update
If you have already flashed a non-downgrabable sbf (2.51 or 3.4.2).
Case 2: If you are not in case 1.
Due to Motorola Defy having a locked bootloader at the time of doing this rom, the flashing process is quite complex, so READ AND FOLLOW it VERY CAREFULLY, or you will end with a non booting phone. If it is the case, you should restart again the whole procedure from the beginning.
I recommend you print the whole procedure, and check every step as you do them.
PLEASE READ EVERY SINGLE STEP BEFORE STARTING IT AND FOLLOW THE ORDER CAREFULLY.
If you don't respect the steps and order, the result can be unpredictable.
Only run the steps that apply for your case!
This Rom is a Nandroid backup of system to be restored over the phone:
Unzip the rom file, and place the 2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar folder into the SD:/goapkrev/backup/ folder. If SD:/goapkrev/backup/ doesn't exist you have to create it. It should look as follow:
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/system.img
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/nandroid.md5
Start with FULL battery! (cases 1 & 2)
Be sure your phone's battery is charged 100% before starting.
Wipe all (case 2 ONLY)
Boot your Defy into Stock Recovery (Power + Volume Down button)
Tap in the bottom right corner of the screen to get into the menu
Select Wipe Data, then press OK
Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
Flash Chinese sbf, root, install recovery (case 2 ONLY)
!! WARNING !! Be sure you are in case 2 before you follow! If you are in case 1, read instructions again!
Connect the phone via USB to your computer
Flash Chinese Froyo sbf using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
After flashing the phone will reboot. As we have wiped, it should boot correctly into the Chinese rom.
At the Chinese Motoblur login screen:
Select English language
Press Menu -> Skip Motoblur setup
Root, Install recovery (case 2. also case 1 if you have never rooted & installed recovery)
Go to Settings, Applications, Development -> Enable USB Debugging Mode
Root the phone using the provided SuperOneClick
Don't reboot yet. Run the "Install Recovery.bat" in the same SuperOneClick folder.
This will copy Tenfar Custom bootstrap recovery to the phone and reboot it.
Power up the phone again & wait until it boots.
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Install Recovery System", when Asked for Superuser permissions, give them and wait until it says "Install Success!"
Reboot into Custom Recovery & Flash Rom (case 1 & 2)
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Recovery Boot"
In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
Here you can also flash the patches you want to install (Apply zip from sdcard)
Get back to the recovery main menu, and WIPE ALL
(case 1 ONLY) Reboot. End.
Flash boot&devtree (fixes cam flash) (case 1 & 2)
Reboot. /!\ While the phone powers off and on again, maintain the "Volume UP" button pressed!!
Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Connect the phone via USB to your computer (if it was unplugged)
Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
End. Enjoy your Adlxmod Froyo for Defy!
Once you have correctly done the process, you may want to flash some option patches. Just go into Recovery mode and flash the zip you need from the optional patches.

Phew what a detailed protocol. Thank you so much will try it tomorroow
Sent from my MB525 using XDA App

Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Update0: You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
I'm trying to start over, but I can't get anywhere except Stock recovery (which doesn't respond to any commands on the OK Button - wierd) and the USB Bootloader, which doesn't help because if I go through the whole process without doing the factory reset, I can't get to Tenfar's recovery boot after flashing the devtree only sbf - I just get a blank screen.
So I'm pretty much effed.
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Update3: I am going to try a different ROM entirely and maybe I can get a working phone before work tomorrow...
Update4: Yeah, your instructions were backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.)

THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!

will try it rite now, coming from chinese sbf, never flashed 2.51. will post feedback tomorrow.

Darkcaptain said:
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
Click to expand...
Click to collapse
hmm good question dude dark bar would look awesome going to try it as im board let you know if it works
edit tried it, it works but imo doesn't suite stock rom

rob-t said:
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Click to expand...
Click to collapse
If you haven't flashed any UNdowngrabable rom, you should be able to flash this one. After flashing this rom using my procedure, you will NOT loose downgradability. In other words, yes, my rom is downgradable.
rob-t said:
You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
Click to expand...
Click to collapse
If you land in Tenfar recovery you haven't followed my instructions that say:
- Press "Recovery Boot". /!\ Phone should now reboot. While the phone powers off and on again, maintain the "Volume UP" button pressed!!
- Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Click to expand...
Click to collapse
That means that, anyway you land in Tenfar recovery, just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf.
If you get a non-booting device at some step, try to just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf at this step.
rob-t said:
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Click to expand...
Click to collapse
Well, Stock Recovery is a bit tricky to use... In my particular case I use the vol up/down to select menu entry, and I tap on [ok] (I usually have to tap several time to have the [ok] actually do something. Once it starts, yes, the Wipe is very slow! Like 1-2 minutes.
rob-t said:
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Click to expand...
Click to collapse
That is weird... Anyway I'll double check later, but it's what I have written on my notes, and I've followed my notes a lot of times, so I guess this order worked for me at least.
rob-t said:
Update4: Yeah, your instructions are backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.) PM me when you fix your instructions and I'll remove this.
Click to expand...
Click to collapse
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.

adlxdum said:
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
Click to expand...
Click to collapse
ill give that ago running uk 2.2

Nice rom, will feedback you...

can confirm that if you already running 2.2 all you need to do is run the nadroid back up and all should be good btw dude nice rom

First of all thanks for this rom! I am expecting my Defy over the mail by monday or tuesday and up till now this rom is the most appealing.
I have one question. How do you prevent motoblur installation? Is that simply a matter of skipping at first boot? Do you have plans to make a deblurred version of your rom?

coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.

that happened to me pulling the battery sorted it and it booted fine after that

i think native boot+devtree would be better, so here it is.

racca said:
i think native boot+devtree would be better, so here it is.
Click to expand...
Click to collapse
I also had this one, but as the US one was working correctly I sticked with it. I have posted what I have tested.

Boot loop in Motoblur Animation?
fabianowerner said:
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
Click to expand...
Click to collapse
If you have Boot loop in Motoblur Animation, please try this:
- Boot your Defy into Stock Recovery (Power + Volume Down button)
- Tap in the bottom right corner of the screen to get into the menu
- Select Wipe Data, then press OK
- Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
- Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
Then reboot. How does it go?

adlxdum said:
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Click to expand...
Click to collapse
Thanks, yeah I was coming from Eclair 2.34, so I should be downgradable. Can confirm that the camera works fine on this ROM.
Sadly, I have the dreaded "Unable to open connection to server" problem with Android 2.2 so no more exchange email.
Update: Ran a quadrant benchmark on my phone with this ROM, got 1299, so pretty good! I haven't removed any apps, and also added SetVsel and DroidWall. Overclocking in SetVsel was set to: 1000mhz/52 600mhz/36 300mhz/26. About the same speed as I had going in Eclair.

Missing WIpe!
There was a missing step (to Wipe all) in my instructions, sorry. It's fixed on the first post.
- In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
- Get back to the Recovery Menu, and WIPE ALL once more.
Click to expand...
Click to collapse

Hmmm, I'm not sure having both email apps installed is a good idea. Once you get past setup in either app (took about 20 tries but finally it connected to the server and completed setup), either app will both force-close as soon as they are launched. Were you actually set up an exchange account during testing of this rom?

Will give this a try, Is market working?
also can i flash the data.img from my backup to restore my apps and data?

[EXPERIMENTAL] MultiROM v19 (discontinued)

This project is now discontinued and will recieve no further updates nor support.
First of all, thanks petter (https://github.com/havlenapetr), Czech Samsung Galaxy developer, for idea and source codes.
What do I mean?
You have one ROM in internal memory as usual, and another one in folder on SD card ext partition. You can easily switch between them - just move rom from ext partition to some backup folder.
See guide in second post
How is it done?
Lets look on how android boots - its (roughly) like that:
1. Bootloader - forks between recovery, fastboot and normal boot
2. Linux kernel - Unpacks its initrd, loads drivers and many more things, not important now
3. Init - kernel runs this program, which mounts android partitions, sets correct permissions to files, starts services, and in the end, starts android itself
4. Android - Dunno much about it yet, anyway not important now​
So, what we need to do is mount something else than internal memory in init. Init parses & runs simple scripts, which makes it simpler to mount sdcard folders.
We need to add mknod and bind mounting to init binary. Unfortunately, we dont have sources of init modified by LG (that thing is three(!) times larger than init compiled from AOSP, what the hell is in there?!). That is solved by running modified init, which parses "preinit.rc" with mounts and then runs LG init.
Commit: https://github.com/Tasssadar/init/commit/aa3604ca90f5ef9b688fdc2e3cc865aa29a54809
preinit.rc: https://github.com/Tasssadar/init/blob/b4e701e8bc4831fadbefa64be48300139dcc2023/ramdisk/preinit.rc
This would be all, if original LG init would not remount /system and /data from internal memory. Also, nearly every ROM has different init.rc, and wont boot without it.
To solve this, I created "import_boot" command in init, which copies *.rc files and LG init from ramdisk(well, its only folder with these files extracted from ramdisk for now) on sdcard ext partition. This command also puts comments out every line with mount /data, /system or /cache in init.rc file, so LG init wont remount them.
Commit: https://github.com/Tasssadar/init/commit/dc3fa50d65d1221a4fb819d8ee616765ee043e83, https://github.com/Tasssadar/init/commit/f7bc141b1e4b7d214e49d4bb005c71237231436c and https://github.com/Tasssadar/init/commit/1cde6b6a093d4ac1f961e610c5229605bc517b52
Format of ROM on ext partition:
All files from paritions in internal memory copied to sd ext partition with preserved owners and permissions(!).
So, when I copy data, I do "cp -r -p /data/* /sd-ext/multirom/rom/data/" (I suggest to run this via adb shell while in recovery).
Currently, I mount /system, /data and /cache from sdcard. If one or more of these folders does not exist, its equivalent from internal memory is used.
It would be nice to have *.img files from nandroid backups instead of this, but as far as I know, they cant be just mounted.
As for *.rc files, I put them into /sd-ext/multirom/rom/boot folder. I would like to just copy boot.img and extract files in init, but I did not find way to extract it when I have hardly STL usable in init. I'd like to use kernel's internal decompressor, but I dont know how.
Limitations
- Both ROMs must be compatible with one kernel - kernel is already loaded in init
- ROMs must be for same baseband, obviously
- Kernel modules(wifi, for example) of both ROMs must be compatible with one kernel. That can be easily solved by copying modules from one ROM to another, though.
- It will be slower than internal memory.
Integration with recovery
Definitely possible & usefull. This is integration in my modified AmonRa recovery: https://github.com/Tasssadar/Amon-R...mmit/bd0232f7379993c296b0223973b81e8c55dc3ee2
Security risk
/system on sdcard can't be mounted read-only - I'd have to mount whole sdcard read-only. This is possible security hole, but you cant do much without root anyway, because of permissions. And if you have root, it does not matter if its read-only or not.
Conclusion
So, it is possible to have dual-boot. You can use it to develop ROMs(you can directly edit data in /data and /system), as backup ROM when you are testing something in internal memory which does not boot, and you need to call someone or when our devices will be so old that bad blocks in internal memory wont allow us to boot
But, as you can see, It is not something that average user could do, at least not yet. Maybe I could modify recovery to do everything for the user (copy data from /system, /data and /cache, extract *.rc files from boot) and create some flashable ZIPs which would modify the init.
But there are some problems - some ROMs may not be compatible with this and there are multiple recoveries out there, but theres not single one which is only for our phone - both AmonRa and ClockworkMod are developed for wide range of devices. Yes, both of them can be modified, but I doubt they creators would accept such inflexible and device-specific thing.
What do you think, is it worth it?
Tested ROMs (first one is in internal memory, second one is on SDcard)
Working:
Megatron and stock v10a ROM - stock rom is slow
Megatron and devoid #froyo-final - like ten times faster than stock xD
LightRom(2.2.2) and devoid #froyo-final (and vice versa)
Megatron and Megatron - both ROMs can have a2sd
Megatron and Mik's CM7 6.5.8 - since v2
Gingerbread 2.3.4 from Optimus Net and CM7 6.6.1 (thx eduardogouveia for testing)
Stock 2.2.2 and CM7 6.5.8 (thx eduardogouveia for testing) - if you have ext4 partition, you need custom kernel for stock ROM.
.void 2.3.4 and stock V20B (thx diazneoones for testing)
CM7 6.5.8 and .void 2.3.4 (thx diazneoones for testing)
CM7 nightlies and Lupohirp's СM9 (thx aquapp for testing)
Not working
None found yet, but when CM7 is on sdcard, it looses root. Trying to figure out why. - fixed in v10
PS: I hope I explained it correctly, not exactly good at this. Do not fear to ask, if you don't understand something.

OK, here goes guide for average user. This is still highly experimental feature, keep that in mind. Backup, backup backups and backup them to PC, read whole guide first, I am not responsible for your bricked phone etc.
GUIDE:​1. Requirements
Ext4/Ext2/Ext3 partition on SDcard big enough to hold all files from /system and /data, which is from 170mb to 400mb (depends on ROM and apps installed), so I think 512mb partition is minimum (if its 90% or so free).
Modified recovery. Only AmonRa and CWM version is available at this time, TeamWin is coming "soon". You can find flashable zip at the bottom of this post, flash it before you proceed to next move. If something goes wrong, you can restore your recovery with zips from here.
Kernel with ext2/3/4 support, which is basically every but stock
Both ROMs you wanna use must be compatible with same kernel. See Limitations in previous post
2. MultiROM instalation
- Via MultiROM Mgr application
I recommend you do nandroid backup before installing via this app.
Download MultiROM Manager (link at the bottom of this), tap to "Tap to install via this app" and wait. As simple as that. Mgr will also install recovery for you (It will ask you which one, you can select AmonRa, CWM and none). App can check & install update, too.​- Via recovery
Just download multirom.zip at the bottom of the post, make nandroid backup and flash it. Your current ROM will be the one in internal memory, we will setup the one on the SDCard in next move.
Now, try to reboot the phone (boot will take little longer, because it has to mount ext partition). If it boots up correctly, then its OK - your ROM is supported. If not, then restore your nandroid backup and post your ROM name here, maybe I'll try to make it working.​
3. Setup ROM on the sdcard
Make nandroid backup (I am not kidding, you will need this one), flash ROM which you wanna to have on SDcard, do the first boot (because it will create dalvik-cache, and you dont wanna do that when its already on sdcard) and reboot to recovery again.
Go to "MultiROM options" menu and select "Create from current ROM". It will do everything for you (it takes time, though). ROM on the sdcard is placed in /sd-ext/multirom/rom/, backups are in /sd-ext/multirom/backup/.
Restore nandroid backup from beggining of this step and reboot. Wait until Boot manager shows up, and select SDcard as boot location. ROM from sdcard should boot. If your ROM from internal memory boots or if its stuck, something got wrong and you should restore from backup.
4. MultiROM recovery menu description
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
Create from ZIP file - see http://forum.xda-developers.com/showthread.php?p=22194117#post22194117
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Flash ZIP - flash ZIP file to ROM on SD card, for example gapps.
5. Config file:
It is recommended to use Multirom Manager(see bottom of this post) to change config file.
File itself is placed on sdcard and its name is multirom.txt. Description of its contents is in this post(post is updated if something changes): http://forum.xda-developers.com/showthread.php?p=20045183#post20045183
6. Key bindings:
Since v11, you also can control MultiROM via touchscreen.
Anywhere: Hold Power button to shut down the phone
While on main screen:
VolUp/Down - list between actions
Menu - Confirm action
Back - Reboot to recovery
Power button - Sleep mode
While playing tetris
VolUp - return to main screen
VolDown - pause
Menu - move the piece to left
Home - hard-drop
Back - rotate piece
Search - move the piece to right
FAQ:​Q: It is slow!
A: Its sdcard. It just is slower than nand memory.
Q: It does not work with my ROM
A: Post your ROM combination here, maybe I'll see to it.
Q: When do I need to reflash?
A: When you flash new ROM or do something which rewrites boot partition. Most (if not all) kernels are using Koush's AnyKernel, so they should not cause any problems.
Changelog & Download:​(Always flash newest version)
Uninstaller: http://www.mediafire.com/?3eco51f2t0at77o (info here)
Changelog AND DOWNLOAD LINKS have moved to github: http://tasssadar.github.com/multirom/
Recoveries
AmonRa - based on 3.06: http://www.mediafire.com/?ld9g81igvze7na0 (9th March 2012 21:57)
AmonRa - based on 2.2.1: http://www.multiupload.com/7Y5HHNEPOT (20th October 2011 22:29)
CWM: http://www.mediafire.com/?6rfw0qbrddzq5d8 (9th March 2012 21:57)
TWRP: http://www.mediafire.com/download.php?o8kphxmfk9l01tl (21st October 2012 23:49)
MultiROM Manager app
http://forum.xda-developers.com/showthread.php?p=20610052#post20610052
(Always use newest version)
v24 - http://www.mediafire.com/download.php?1xy52tamzepibrx (TWRP support)
v21 - http://www.mediafire.com/?u9c3bmfbtf57dtm (Add charger settings)
v18 - http://www.mediafire.com/?g1lpsp66jc1cb1b (Add boot location settings)
v17 - http://www.mediafire.com/?l1li51sseaisz5j (Add brightness setting)
v15 - http://www.multiupload.com/B65WPFMFXP (Show & reset tetris high score)
v14 - http://www.multiupload.com/FWB5UBSMO1 (Updater now also check for app update, some minor fixes)
v13 - http://www.multiupload.com/NYYBX9CAFD (Update translations, add support for optimus V - http://forum.xda-developers.com/showthread.php?p=20657898#post20657898)
v11 - http://www.multiupload.com/1L3294ZAU7 (Fix mount issues on some roms, add menu to main screen, add link to xda)
v10 - http://www.multiupload.com/B3AVSFKDOW (Create /sd-ext/multirom folder on install)
v9 - http://www.multiupload.com/WW7TUNP7RY (read http://forum.xda-developers.com/showthread.php?p=20624306#post20624306)
v8 - http://www.multiupload.com/6OD7RQ74OE
v7 - http://www.multiupload.com/DJKMUGIVJ0

Something like this have the Xperia series. Maybe u find something u can use there.
Sent from my LG-P500 using XDA App

so this means we can test roms without replace current ??

Yes. Is my english so bad or you just don't read what I wrote?

Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
For the last time,you're speaking english perfectly p)

how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....

*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.

eduardogouveia said:
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
Click to expand...
Click to collapse
[dev] means this is not something ordinary. Don't know what it is, don't mess with it.
Tasssadar said:
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
Click to expand...
Click to collapse
Don't worry, you'll get more "hao cán i flush this into ma phones?" questions, good luck.

sounds like fun
thanks for bringing it for optimus one
but i have one question for you
I think in future kernel changing will also possible
because if we can flash kernel then we can make it to change
right?

Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
Maybe you just helped us with boot manager app
Sent from my LG-P500 using xda premium

I read the post but since the download you have is of a amonra recovery modified by you,i thougt that was a regular zip and only then make by abd the tutorial,thats why hi also ask a more friendly use because i now its not for averager use no need to get obset however im still happy hi was searching for that so hi dont mind waiting you make it more simple... sorry if that ofend you or franco lol we have to learn and its very hard now how to develop without having the proper nowledge like you all devs have and hi respect every dev even of he just make a simple app,by the way just dont send me to school lol where could i learn the bases to umderstand how to program java and then develop im asking this because all books hi find rekire previous nowleged of some progaming could some dev. Pointing me somewhere where i could learn and please dont be rude im just asking because i just dont love i want and hi will learn...
And baking to the thread what you find for me is one of the best and most important for our phones thanks a lot now just wainting a day everybody could use your work thank you
Sent from my LG-P500 using XDA Premium App

So your main question is: "Is it worth it?"
I would say, "Hell yeah it is!" but then again I do not have the know-how to pull something like this off.
If you decide to go ahead with it, I wish you the best of luck =P

I just modified Koush's AnyKernel so that it can modify ramdisk's content, so it is possible to install it with .zip file via recovery. I will add some modified version of CWM & AmonRA, create some walkthrough video and write some guide soon(c).
By the way, that kernel which is in devoid #froyo-final cant mount ext4 partition in init, dunno why, I'll look into it after raid.
EDIT: wtf, it just works now, and I did nothing Oo
EDIT2: Changes commited, now It can installed/controlled only by flashable ZIPs and recovery(well, only my modified AmonRa recovery for now). I'll do the rest soon, but I dont know when - maybe tomorrow (oh my, it is today actually already), maybe next month.

Flashable zips and guide added, see first and second post.

keep going I wanted something like this waiting when it can boot stock<froyo> and cm7....
thanx

gingerbread test
well i try with V20C,2.3.4 port(both with a2sd)and didnt woork after flash multiromv1.zip,when reobooting always return to recovery,so in recovery i go to multirom options and says no multirom folder so i start to think a2sd imcompatibelity,so i grab 2.3.3 V20G without changes oficial as lg give us but the results where the same no a2sd problem....
well later i will flash oldbaseband and try one of your combinations but i think its not compatible with gingerbread.....

I think I found it - on GB, there is "on fs" trigger in init.rc, which has only mounts in there, but I need to comment them out - all of them, so "on fs" trigger is empty, and init parser cant handle that. Will update soon.

Ok i will remain in new baseband to try when you update your exclente work...
Sent from my LG-P500 using XDA Premium App

v2 released, I have tested it with CM7 6.5.8, problem with stock GB should be the same as with CM7.

[ROM][DISCONTINUED] Huawei U8836D / Ascend G500 Pro (MT6577) custom ROMs (ICS)

Hello everyone!
In this thread you'll find all my custom ROMs for Huawei U8836D / Ascend G500 Pro (MT6577) smartphone (also known as Huawei Shine). Please be sure to read this carefully in order to avoid unnecessary questions.
Do not mirror my files, as I will always make sure links are working. :fingers-crossed: Instead, please share the link to this thread.
Review of Huawei U8836D:
Huawei U8836D / Ascend G500 Pro / Shine (Dual SIM with 3G support)​
Tutorials and Frequently asked questions (FAQ):
For tutorials jump into post #2.
For frequently asked questions (FAQ) jump into post #3.​
Version history (including download links):
V1.0MOD (02-10-2012):
Based on official Android 4.0.4 ROM (Huawei release: U8836DV100R001CHNC00B600SP19 ; Stock kernel 3.0.13)
Custom changes:
Removed all Chinese applications (Chinese IME, Huawei app store, etc)
Added reboot to recovery option to power menu
Enabled MediaTek EPO and A-GPS settings under Location services menu
Enabled Speech category (Voice search and TTS output) under Language & input menu
Fixed the bug related to the association of caller identification (CID) with contacts, due to country code prefixes
Integrated the latest version of Google apps
Added ES File Explorer (v1.6.2.1) and ES Task Manager (v1.3.1)
Rooted (no need to root phone with third party applications) with SuperUser application (v3.1.3) and su binary (v3.1.1)
Busybox (v1.20.2) installed
Added battery percentage (in steps of 1%) display
Changed notification LED color to blue instead of green
Updated APN list (apns-conf.xml)
Added AdFree hosts to system hosts file (blocks ads in several applications or games, for example Angry Birds)
Added stock ICS LatinIME and dictionary pack
=> Download link
=> MD5 sum: 3b547d0f6b643b168b02468c4c55b6fd​
V2.0MOD (20-10-2012):
Based on official Android 4.0.4 ROM (Huawei release: U8836DV100R001CHNC00B600SP25 ; Stock kernel 3.0.13)
Custom changes:
Added some build.prop tweaks to improve pictures and video quality, increase touch responsiveness and improve battery life
Updated ICS LatinIME and dictionary pack
Updated Google Play Store (v3.9.16)
Updated Street View on Google Maps (v1.8.1.2)
Updated Huawei Mobile Partner internal disk with the latest HiSuite software and Google ADB drivers
Added support for the following languages: Arabic, Bengali, German, Spanish, Farsi, French, Hindu, Indonesian, Italian, Malaysian, Dutch, Portuguese (Portugal and Brazil), Russian, Thai, Turkish, Urdu, Vietnamese and Chinese (traditional and simplified)
=> Download link
=> MD5 sum: 1d5a43add7745958d33484f344cfa46f​
V2.1MOD (16-12-2012):
Custom changes:
User customize-able installation based on AROMA installer
Included script to automatically disable internal sdcard if extended userdata partition is detected (be sure to read post #4)
Included JB LatinIME (with predictive swipe) and dictionary pack
Updated Google Play Store (v3.10.10)
Updated Google Play Services (v2.0.12)
Updated Gmail (v4.2.1)
Updated YouTube (v4.2.16)
Added support for the following languages: Czech, Hungarian, Polish and Greek
Unlocked hidden features under Developer options menu
Fixed bootloop when factory reset was done under Android system
=> Download link
=> MD5 sum: 331e8763eddf7c2ac1ce0f1020ca1bbd​
V2.2MOD (28-12-2012):
Custom changes:
Fixed SystemUI crash when system language was set to Czech or Greek
Corrected date format entries for Czech and Greek languages
Fixed non-working light sensor reported by some users
Disabled built-in virtual disk drive
Updated APN list (apns-conf.xml)
Updated TZ data (timezone data)
Updated Google Maps (v6.14.2)
=> Download link
=> MD5 sum: 193d5087d0731f318bf514aee2fbaec7​
V3.0MOD (18-02-2013):
Based on official Android 4.0.4 ROM (Huawei release: U8836DV100R001C10B600SP12 ; Stock kernel 3.0.13)
Custom changes:
Added all fixes / modifications as in previous releases
Integrated the latest version of Google apps
=> Download link
=> MD5 sum: d9a3f828e605b2115aee7030009b1745​
GPL compliance:
Kernel 3.0.13 source code
Link to tarball from Huawei website
Link to github repo
Credits:
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery, as well to all contibutors
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Please don't just leech the files and go away. You can easily say thanks just by pressing "Thanks" button.
Feel free to post your comments. I hope you all like it!

Tutorials
How to enter into recovery mode:
With Huawei U8836D completely turned off, press and hold VOL. UP key and turn on the phone. The phone will vibrate and after the splash logo appears, all keys should be released.​
Navigation under recovery mode:
Stock recovery mode: As soon as the splash logo disappears, an image with a triangle and an Android will appear and BACK key must be pressed in order to access menu options. Navigation is made using VOLUME keys (navigate up with VOL. UP and navigate down with VOL. DOWN) and MENU key to apply the action.
Custom recovery mode: As soon as the splash logo disappears, ClockworkMod Recovery menu will appear. Navigation is made using VOLUME keys (navigate up with VOL. UP and navigate down with VOL. DOWN) and MENU key to apply the action.​
How to flash custom recovery:
Download Huawei U8836D custom recovery and follow this MT657x flashing tutorial.
Warning: the package includes preloader, but there's no need to flash it. Make sure that you select only recovery to be flashed.​
Flashing a new custom ROM via the SD card method (update.zip):
Read this guide to know more about ClockworkMod Recovery and how to flash a custom ROM.​

Frequently asked questions (FAQ)
Question: I can't install your custom ROMs. Why? What am I doing wrong?
Answer: First of all you have to flash a custom recovery into your phone and then you are able to install my custom ROMs. Read the tutorials on post #2 to know the procedures.​
Question: I wanted to try one of your custom ROMs. Will I loose all my data after installing it?
Answer: Yes, you will loose all your data... unless you create a backup to restore after installing the ROM. There are two recommended ways to create backups of your userdata:
Doing the backup under custom recovery mode: navigate to backup and restore menu.
Using Titanium Backup to create a backup of your favourite applications.
Question: Can I fully revert to factory settings?
Answer: Sure, just download the stock update.zip and install it from recovery.​
Question: In phone specifications it's stated that it has 4 GB of eMMC, but only approximately 700 MB are available for internal storage... Can you explain me the reason for that?
Answer: The phone has indeed 4 GB of eMMC. Part of it is used by system and cache partitions, while the rest of the size is divided into internal storage (approximately 700 MB) and an internal sdcard partition (approximately 2 GB). If you find that an internal sdcard partition is useless (and have a big external sdcard), you can extend userdata partition (internal sdcard partition completely disabled). Jump into post #4 to learn how to apply that mod.​
Question: Somehow I have got invalid IMEI numbers. How do I restore my phone's IMEI numbers?
Answer: Read this tutorial. Don't forget to say thanks to its author.​
Question: Does my phone really have two IMEI numbers?
Answer: Every dual SIM smartphone based on MT65xx SoC has two IMEI numbers. Some just don't display both numbers on dialler when you type code *#06#, but if you go into Settings / About phone / Status / IMEI information you'll see the IMEI set for both slots.​
Question: How can I access hidden MediaTek engineering mode?
Answer: From phone's dialler type code *#*#3646633#*#*.​
Question: Are your custom ROMs patched to fix Android's master key (bugs 8219321 and 9695860) vulnerabilities?
Answer: No, but the solution to that is pretty simple:
Install Xposed framework (instructions on the support thread)
Install Master key dual fix module (instructions available also on it's support thread)
To check if system is vulnerable you can use one of the following apps:
SRT AppScanner
Bluebox Security Scanner
All credits to rovo89 for the amazing Xposed framework and also to Tungstwenty for the Master key universal fix.​
Question: I don't have this phone, but mine is also based on the same MT6577 SoC. Can I still flash your recovery and install your custom ROMs?
Answer: Even though your phone is based on the same SoC, there may be differences in other hardware components. It is not likely that recovery and ROMs will work on your phone so you may risk to brick it.​

Huawei U8836D internal memory re-partition
Initial notes:
Make sure that you have a full nandroid backup of your current ROM. If not, boot into recovery mode and make one. This is very important if you want to restore userdata after internal memory is re-partitioned.
Also make sure that you have a backup of your internal sdcard because it will be fully erased and disabled.
Warning: the package includes preloader, but there's no need to flash it. Make sure that your selection is according to the screenshot bellow.
Instructions:
Copy disable_internal_sdcard.zip to external sdcard (read note bellow)
Shutdown the phone
Open SP Flash Tool v3.1222.00 (or higher) and load the scatter file
Flash MBR, EBR1 and RECOVERY as shown on the next image (read flashing tutorial first):
{
"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"
}
After flashing is complete, boot into recovery mode and format /data
Optionally, if you want to restore previously saved userdata, go to nandroid backup / restore and restore data (advanced restore feature)
Install disable_internal_sdcard.zip file through recovery mode (read note bellow)
Reboot your phone and enjoy your extended userdata partition
Important update: All the new ROM updates which include AROMA installer also include a script to automatically disable internal sdcard if extended userdata partition is detected. Dismiss the part of the instructions that refers to the installation of disable_internal_sdcard.zip file. All the rest of the procedure is still valid and must be done before installing the ROM. That said, if you are going to apply this modification, you must re-install the ROM.
Please also note that this mod should only work with my custom ROM installed. Be warned and please do not blame me if you run into some problem while applying the mod over stock or any other custom ROM

Thanks Bruno for the recovery image. I will get it flashed when I am back home.
I have noticed that actual phone reception signal levels are lower than my W3+ Thl phone. Have you noticed any difference in signal levels where you are against your ZTE 970? It may be just the algorithm they use on this one.
I love the tricolour led but lack of tts settings is a little annoying. Overall, I am very pleased with it so far though.

Thanks Bruno - I look forward to some custom ROMs - I'd managed to dump the entire original ROM last week having made a scatter file then add Gapps but nothing else. I'm completely new to modding and happy to do any testing etc. My phone had the original factory ROM.
Yes the signal reported does seem on the low side. The battery drain does seem a little high as well so far even when not constantly playing with it!!) - wonder if the CPU governor is set properly?
Edit - gave the phone a good full charge overnight - before using it today and down to 90% after 12 hours - with little/no use - so about normal for a smartphone. Probably hadn't charged it fully before!!

Thanks Bruno, my phone is at this time only paperweight, so I am waiting impatiently for your ROM.

Thanks for the recovery img Bruno.
For those of you who want to install the Huawei HiSuite app on your phone and desktop but can not get a link from the Huawei site here, I have uploaded it to 4Shared and you can download it from this folder here.This suite allows some syncing to be done and some backups etc. Full details on the Huawei website.
EDIT:
Bruno, not quite sure what happens but after flashing your custom recovery and testing it, I reboot and the original recovery returns! Just to make sure that I was not going mad, I flashed the custom recovery image again. I can use it, I have even done a back up of the system but after running the phone and a reboot, the original recovery returns again.
Is there anything to resolve this, are you having same problems? This is really strange.
EDIT:
From MSprecher
The custom recovery is allways overwritten by the stockrecovery when booting the phone. This can be avoided by rebooting from within the CustomRecovery right after having flashed it. There should be an extra-option after the reboot-command in CWM-Recovery to avoid this.
Enjoy Matthias

neveceral said:
Thanks Bruno, my phone is at this time only paperweight, so I am waiting impatiently for your ROM.
Click to expand...
Click to collapse
Please be patient. I plan to release the first version during this week. :fingers-crossed:
Sathelp said:
Bruno, not quite sure what happens but after flashing your custom recovery and testing it, I reboot and the original recovery returns! Just to make sure that I was not going mad, I flashed the custom recovery image again. I can use it, I have even done a back up of the system but after running the phone and a reboot, the original recovery returns again.
Is there anything to resolve this, are you having same problems? This is really strange.
Click to expand...
Click to collapse
Yes, that happens with the stock ROM installed and the workaround for now is the one Matthias already told you. With my custom ROM installed that will not happen.

Thanks, the option to allways use custom recovery does appear and you have to confirm this option before first reboot. Thanks guys.

Bruno it will be great (i don't know if it is possible) if the new rom could aggregate the memories, i mean the same you did on the ZTE, putting the same storage for programs and the only sdcard is the external.

Yes, I plan to release the same extended userdata mod as I did for V970, but not integrated into the ROM, so that users can choose want they want.

Btw, i found now in my small experience with the device two problems:
- Some apps can't be installed (Asphalt 7, Sports Tracker, WorldMate, etc.) which were working in my previous Gsmart G1345. Is it due to the Mtk CPU??
- Comparing again the two devices, this one has a worse GPS, much more inaccurate and very slower in getting signal.
Lets wait for your fantastic Rom, Bruno.

Crake you are right, I cannot install profile scheduler+ or EasyProfiles Pro due incompatibility. DualSIM?

No, that is a problem of permissions. It will be working on the custom ROM, don't worry.

Sathelp said:
I love the tricolour led but lack of tts settings is a little annoying. Overall, I am very pleased with it so far though.
Click to expand...
Click to collapse
I have already enabled Speech category (Voice search and TTS output) under Language & input menu, so you'll be able to access TTS settings.
By the way, I will release the first custom ROM today. It will not support any additional language other than the default ones - English and Chinese (Traditional and Simplified) because I don't have time right now to do it. The support for more languages will only be included in the next version. Hope you all understand!

awesome!!
u know I have been waiting for a rom for this phone u8836D from day one, because i messed it up on the day i received it, especially replacing the system folder files etc.. just pain in the bum to not have a rom (even stock rom) handy. And it's been endless waiting...
when your first post came up, I opened your shared folder for like a million times to try to find the rom, but just recovery img there, i thought I missed something maybe and read all your posts another million times...
Now just 10 mins ago, it appears in that lovely folder just like a magic...
Will let you know how I go...
i haven't learned my lessons from my last 5 Android phones...all I want now is just clean system with google services on...
When we get that, we star talking optimization and who's ass is more sex lol

Okay, I have just uploaded the first custom ROM for U8836D into my 4shared folder.
Please read what are the fixes / modifications that I've made over the stock ROM on the third post of this thread or in the readme.pdf that's inside the .7z file.
Enjoy! :fingers-crossed:
EDIT: I forgot to say that this ROM clears all userdata, so make a backup first using Titanium Backup, for example. But please note: do not restore any contact / messages database. Let Android create it from the scratch or else, if you restore everything the CID bug will be there again!

So how do I restore (and backup) sms, contacts and call logs to avoid CID bug?

Simple: you don't restore. Just sync the contacts again with Google (or Exchange), let the database be built from scratch and that's it. It's either that or having the nasty CID bug back...

🔥 READ ME FIRST [FAQ][HTC][PICO/EXPLORER][a310e]🔥

"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]
0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1
0„30†2Moved by touch0160†640„30†3Inc.
0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨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/

i9003 Flashing Tutorial (Gingerbread DDLF2 and Others)

Samsung Galaxy SL i9003 Full DDLF2 Performance and Battery Duration Guide (Clean Flashing; Rooting; Custom Kernel and ClockWork Mod Recovery)
Greetings everyone!
As promised i've updated this tutorial (sorry for the 6 Months delay).
Download this Tutorial (*.pdf File) http://www.mediafire.com/view/ay0kfbtcd2ap6dm/rgxHost_i9003_DDLF2_Complete_Tutorial.pdf
Device: Samsung Galaxy SL i9003
ROM(s): Full DDLF2 (XWKPG or XXKPE) (Note that Deodex file won't Work for XWKPG or XXKPE)
Target: Get Best Battery Duration; Good System Performance and Less Bloatware as Possible. (Including EXT4 for some Extra Performance)
Using: Universal ClockWork Mod Recovery and Custom Kernel (By BCK)
Log:
* Fixed some improper steps;
* Added some recommended aplications and tips that can enhance the performance and fix some system bugs (i.e: Preventing the Full RAM Crash and Restart issue);
* Added Links for XWKPG or XXKPE ROMs wich seem to be unavailable elsewhere.
* Changed the Tutorial Method to work with almost every Rom while supporting DDLF2 Rom (Including How to Perform a Clean Install / Flash)
[Special Thanks to]:
"XDA_Bam": (For his simplest combined CWM + CF-ROOT and Kernel file. Made everything a lot easier).
"sgatechwork": For the Best Gingerbread Rom cooked for our i9003. (And if i'm not mistaken he also owns the credit of the Deodexing Files)
[To Download Before Proceeding]
:: Your Gingerbread Stock Rom ::
DDLF2 FULL (Original Thread): http://forum.xda-developers.com/showthread.php?t=2329200
Mirror Link: http://www.mediafire.com/download/u96833iufz64auo/DDLF2_Full_(PIT,BOOTLOADER,PDA,PHONE,CSC).zip
[DDLF2 DEODEX] (Mirror Link): http://www.mediafire.com/download/m44e62zsryvcvlo/Deodex_DDLF2_Cwm.zip
[DDLF2 Delete Unwanted Files]: (Mirror Link) http://www.mediafire.com/download/h2aby5sf3pyhpt5/DeleteUnwantApp_Cwm-New.zip
Other Roms
XWKPG (Mirror Link): http://www.mediafire.com/download/27006o6h38kecc2/I9003XWKPG_I9003DBTKP2_DBT.zip
XXKPE (Mirror Link): http://www.mediafire.com/download/72ah13hizi7aok6/XXKPE.zip
:: BAM Universal CF-Root (Incl: CWM + CF-ROOT + Custom Kernel) ::
Original Thread: http://forum.xda-developers.com/showthread.php?t=1355675
Mirror Link: http://www.mediafire.com/download/5ejxf1xznub8eaz/PDA_BCK_CWM_universal_beta15.tar
Note: Since i couldn't get some links for original threads, Files and/or ROM's i'm providing my own links for them.
If by some reason i may be violating any terms, please let me know by sending me a message indicating wich file or files are causing any problem, and or to wich thread(s) they should be pointing to.
Furtherwards the files i'm providing were downloaded from the original sources including Sammobile. (wich sometime get their links unavailable). They are EXACTLY the same as their source and are intended to be kept that way.
[WARNING]
By proceeding with the following tutorial you aknowledge that i will not be held responsible if your device gets bricked or gets any other sort of damage.
Although the intent of this tutorial is to help people out and have the most for their devices. Just proceed accordingly.
Always Remember to:
- Make a Backup of your EFS;
- Never mess up with ODIN checkboxes;
- Never Unplug your device whenever it is flashing;
- Have ClockWork Mod Recovery (or TWRP Recovery) so you don't end up without knowing how to restore your device;
- Read all the steps carefully.
TUTORIAL
[BEFORE PROCEDING]
Note: If you Miss your device Drivers Please Install Samsung Kies First.
1. [BACKUP YOUR EFS FOLDER]
For Best Results Create a EFS Backup as: *tar / *.tar.gz / *.img / and a direct copy of the EFS Folder.
Thread on how to Backup and Restore your EFS: http://forum.xda-developers.com/showthread.php?t=2329937
Note: There are some application at Google Play that can also do it for You. (i.e: Galaxy SL Unlock or GSII_Repair, etc)
2. [BACKUP YOUR SD CARD]
Formatting your External SDCard is important, but not required.
Therefore you may not perform a Backup but removing SDCard before Flashing is advised.
[FLASHING THE ROM]
Note: This guide refers methods for "ClockWork Mod Recovery" (CWM)
1) Remove your SDCard (if you've not done it already)
2) Reboot Into CWM or TWRP Recovery (If you don't have it search for the Proper Recovery for your Device)
Booting into "Recovery"
(Press and Hold) Vol. Up + Home Button + Power Button (Release after the 1st Logo is Shown)
3) Under CWM Recovery Select under the following Menus:
<"Main Menu"> :: "Wipe Cache Partition"
<"Advanced"> :: "Wipe Dalvik Cache" (then return to 1st Menu)
<"Mounts and Storage"> :: "Format Cache"
<"Mounts and Storage"> :: "Format Data"
<"Mounts and Storage"> :: "Format System"
<"Mounts and Storage"> :: "Format DataData"
<"Mounts and Storage"> :: "Format SDCard"
<"Mounts and Storage"> :: "Format EMMC"
4) Return to Main Menu and Perform a "Factory Reset".
5) Remove USB Cable and Reboot your device into "Download Mode".
Booting into "Download Mode"
(Press and Hold) Vol. Down + Home Button + Power Button (Release only when it Loads under "Download Mode")
6) Open Odin
7) [ODIN] Under [PIT / OPS] Load your "*.pit" File (i.e: "latona_20110114.pit")
8) Restart Your Device. Once You Get the "Black Screen", Remove the Battery and Boot into CWM.
9) [ODIN] Load Rom Files
Note:If you come from other a Custom Rom, you may have to Flash Original Firmware 1st.
Note: Always Double Check if you're Loading the Files (Bootloader, PDA, Phone/Modem and CSC) in the proper Place.
Note: While the operation is running Do NOT Remove your USB Cable or Disconnect Your Battery untill you see the "PASS!" message on the top left corner.
Note: To prevent Flash Failures; always use High Quality USB Cables; and before pressing Start Put down your device and don't touch it untill the operation is complete!
You may check Loaded Files example bellow (for Full DDLF2 ROM).
i.e:
[BootLoader]: "APBOOT_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5"
[PDA]: "CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5"
[Phone]: "MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5"
[CSC]: "GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5"
10) [ODIN]
Note a) If you come from Ice Cream Sandwich, Jelly Bean or KitKat (Custom) Roms; it is advised to select "Re-Partition" Checkbox.
Note b) Make sure you have not Selected/de-Selected any Checkboxes (except the one refered at "a" above).
Never change anything if you don't have no idea what they are for.
Specially "Phone EFS Clear". This will literally kill the ability to use your device as a Phone.
Also note that Only a Box or Samsung Service can restore your IMEI if this ("Phone EFS Clear") happens to be Selected.
11) Now that you've Double Checked Everything put Down your Device, Press "Start" and Read the Next Step.
12) When your device completes the procedure above, wait for it to load the 2nd Boot Logo (Usually Animated).
Note that the device may load automatically under recovery to Access, Install and Configure CSC.
If it doesn't then: once the 2nd Logo Starts, count to 3, remove your Battery and Boot your Device under Recovery (Not CWM at the Moment - Reason found Bellow).
This will make sure that the CSC is Installed and Properly Configured (Except if there are any issues with your device, or if you've skipped any of the operations mentioned above).
Note: If you've Flashed Stock Firmware: Know that after you Flash Stock Firmware You lose "ClockWork Mod Recovery". Therefore you must flash it again.
So let's Flash CWM with CF-Root and Custom Kernel (ClockWork Mod Recovery; with Root Permissions and Custom Kernel).
[FLASHING CWM, CUSTOM KERNEL AND ROOT THE DEVICE] (1 File Steps)
1) Remove USB Cable; Power Off your Device and Boot into "Download Mode".
2) Connect your USB Cable, Reset Odin Settings and Under ["PDA"] Load the Following File: "PDA_BCK_CF-root_universal_beta15rc8.tar"
Thread for PDA_BCK_CF-Root_universal: http://forum.xda-developers.com/showthread.php?t=1355675
3) Put Down your Device and Press Start.
4) Once Completed you now have (A rooted Device with Custom Kernel and CWM Recovery).
Your device shall Reboot into CWM Recovery; if it doesn't Reboot it into Recovery and Perform a Factory Reset Again.
Just to clarify: By Performing this "Factory Reset" (Again) you prevent some Errors like:
- Phone Lagging (Specially While Sliding Between Application Pages)
- Getting some configs from previous flashing
Although some sort of lagging will always be present sometimes.
Remember that this is not an ICS, JB or KK Rom nor LoLaTiOn GingerBread that runs ultra fast!
Those Roms are freaking Good (besides some bugs here and there) and i could only recommend them if you use your phone in a "Always Connected to Charger" State.
i.e: your Car as a Multi Functional Stereo; Mp3 Player; GPS and Phone.
Still You will Kill for sure your Battery! (Eventually... Mine Got Fat! Too Much Fast Food (i mean Fast Roms! =) )
P.S: No disrespect for their work wich i apreciate so much. (I'm sure you understand what i mean)
[REMOVING BLOATWARE] [Deodexing] (ONLY For DDLF2)
There are some different ways to accomplish this.
I'm pointing 2 easiest ways, since i didn't get into Deodexing (for Experts) myself.
Remember: This Deodexing tutorial is only for DDLF2 ROM !!! (Wich i USe by the way)
1st Method:
Download "DeleteUnwantApp_Cwm-New.zip" copy to your SDCard and Flash Under CWM Recovery.
This will delete some pre-selected applications. Maybe the safest method for completely inexperienced people.
2nd Method:
1) Copy "Deodex_DDLF2_Cwm.zip" to your SDCard
2) Boot your Device into Recovery (You can now use CWM Application to do it)
Note: Within the application you can boot either to Recovery or Download Mode.
3) Under CWM Recovery Select: Flash ZIP from SDCard; Go to the Folder where you've previously copied "Deodex_DDLF2_Cwm.zip"
Select it and flash it.
4) After it completes the operation, reboot your device and Install "ES File Explorer". (Found on Google Play)
Note: Or just open your favourite File Explorer. Although i made this tutorial for specific applications. (Including "ES File Explorer")
Reason: The applications i mentioned don't give me issues... (Errors or Bugs), and they are extremely usefull somehow and/or fast (with the lowest resource consumption as possible).
5) On the Top Left Corner you have a "List" Button.
- Enable: "Root Explorer" and press that Label Text to pop-up some extra options.
- Select: Mount R/W
- Set "/system" as RW (After you remove undesired applications Place it back under RO)
Note:
"RW" Stands for: "Re-Writable"
"RO" Stands for: "Read Only"
6) Go back to the "List" Button and Select "Library" > "APP"
7) On the Top Click where you see "User Apps", and select: "System Apps"
8) Remove the Applications that you don't use.
Note that not everything can or shall be removed! Some are part of the system itself.
Best thing to do is to note down the application names that you dont like.
Here's a List of some Applications you can Safely Remove:
- Google Maps;
- Talk;
- Gmail (Email Apk);
- Layar;
- Calculator;
- Samsung Apps;
- ThinkFree Office;
- *Youtube;
Note: I wouldnt remove "youtube" if you will youse it later. If you remove it and try to install Youtube from the Market (at least with DDLF2 Rom) the system will Crash on Minimize Video and Reboot.
Other Custom ROMs by some unknown reason run YouTube Perfectly.
9) Removing Several System Applications at Once:
- Press and Hold one of the Applications you want to remove (This will Enable Multiple Selection);
- Then Select the others;
- Press the Garbage Bin on the Bottom ("Uninstall")
- Confirm that you wish to Uninstall and Wait for the Application to Complete.
- Skip Errors / Force Close(s)
Note: It is possible that the device Restarts during this operation.
If so, re-check the application you want to Uninstall.
10) Once Completed Restore "/system" to Read Only ("RO").
On the Top Left Corner you have a "List" Button.
- Go to: Tools.
- You may leave Root Explorer Option Enabled if you prefer that way.
- Press "Root Explorer" Label Text to pop-up the extra options.
- Select: Mount R/W
- Set "/system" as RO
11) Done! ...or if you want to go further into perfecting...
12) The following steps are not necessary... Personally i do them anyway just to ensure the system will Work Properly without the Applications i've Removed.
- Reboot Under CWM and Perform a "Factory Reset"
- Reboot to System and Test Everything.
[PREPARING YOUR SYSTEM FOR EVERYDAY USE] + [INSTALLING RECOMMENDED APPLICATIONS] + [TWEAKING THE DEVICE]
"Some Information" ("Installing Tweaking Applications")
Like mentioned before this tutorial aims for a balance between Performance and Battery Duration.
As some of you already know Gingerbread is amazing for Battery Duration, although it's not the fastest Rom and unfortunly it has also a terrible Task Manager.
Therefore i'm including some applications to tweak your device so you can achieve the balance that you can't find in any other Custom Rom.
i.e: Cyanogen based Roms who Consumes a Lot of battery.
"Applications List" ("Installing Tweaking Applications")
Im not going to talk about every single one as this tutorial aims mostly for Performance and Battery Duration.
Bellow you'll find a brief description of some things you can do with the following applications.
- "CPU Master Pro" (Not Free - Unfortunely) or Similar Application that can set CPU Frequency Profiles like (Charging; Screen Off; In Call; Low Battery and Temperature Over-Heat)
- "SGS Tools" (Mostly for advanced users) This application can Remove Boot Sounds; and fix your GPS Location so it locates faster. Has also a ".prop" Editor, and some aditional advanced features in there! Just Freaking usefull!
- "Twilight" (Screen Dimmer) (Red Light Dimmer; with Profiling Options. Very Good and Free Application)
- "Busybox" or "Busybox X" (Not 100% necessary, but Recommended. Some applications require their installation)
- "ES File Explorer" (For me the Best File Explorer. Fast; Usefull; Visually Pleaseant)
- "Task Manager" (To Improve your device Performance. Your device seems not to reboot anymore when it uses all ammout of RAM. You simply won't let it happen!)
- "Nemus Launcher" (Fast Fast Launcher! With low Resource Consuption)
- "XDA Free" (Your Favourite Forum Application! Where you can rate and thank this thread wich gave me some hours of work; post your questions (read Forum Rules 1st is Important); ask for support; make new buddies; etc...)
"Setting Up Applications"
CPU Master Pro: (Paid)
Ok this will be "al gusto" (configured the way you prefer), but i'm going to point some of my own tips.
If you want to do further research follow this thread: http://forum.xda-developers.com/showthread.php?t=1767797
If you want to take a shotcut...
Then here's some resumed info. (So you can manage your profiles perfectly).
:["Scalings"]:
"Scalings" manage the CPU Behaviour.
Therefore they will help you get the most performance and battery duration.
There are several scalings (including custom Scalings), but i'm going to point out the one's who can really make some havoc and productive effect for the everyday user.
["Smartass v2"]: Is the balance between Battery Duration and Performance.
["Performance"]: Gets the most response as possible.
["Conservative"]: Usefull whenever you need to use your device for longer periods, and/or when you don't have a charger nearby for a long time.
"Setting up CPU Master Pro" Profiles
Open the app Go to Profiles Tab:
The Profiles bellow are the ones who can save some severe battery duration.
Set these profiles "Screen Off" and "In Call"
"Screen Off"
Min Freq: 300 Mhz
Max Freq: 300 Mhz
Scaling: "Conservative" or "Smartass v2"
Note: If you need your device to wake up faster change Max Freq. to: 600 or 800 Mhz.
Both work pretty well, they just differ on battery duration and wake up response.
"In Call"
Min. Freq.: 600 Mhz
Max. Freq.: 600 Mhz
Note: If you go Bellow 600Mhz you may end up in making a longer phone call since your device wont respont so fast. (Usually Lagging)
- Memmory Manager (JRummy) (Partially Free)
- Open the Application and set it to "Moderate" (Higher Values can Crash the System).
- Set it to "Apply on Boot"
Note: The after this i never had the "Full Ram Bug (Crash and Restart) issue anymore."
Note: This application has more usefull features although under the paid version only.
Either way you will notice a better performance just by changing to Moderate.
[OTHER] Script to Increase Battery Duration
Info: This thread bellow will something similar to the CPU Master Pro Profiles.
If you cannot find a better solution for CPU Master Pro Application, then you might want to try this. (Follow the thread link bellow)
Original Thread: http://forum.xda-developers.com/showthread.php?t=2371715

Extended thanks for the pdf format.
Keep it up.

No worries.
Im glad i could help. :thumbup:
Sent from my GT-I9003 using XDA Free mobile app

Thank!
hi rgxHost,
i help my wife to upgrade to XXLE4 (Straight from Froyo) and stuck without rooting the phone (flashed but with wifi error).
she encounters video playback problem (not as smooth as Froyo, some ugly scene transitions).
i want to go back to Froyo, but could not find any installation files anymore (all dead links).
i guess i will try to mess with DDLF2.
Thanks for the guide.

Hello,
Im very sorry for repplying just now.
Within so many threads, I completely lost track on this one.
Links from Sammobile are usually dead, but if you ask them they make the links alive for you.
Froyo is not what you're Looking for due to compatibilities. (Applications, Performance, Bugs, etc).
for Performance:
DDLF2 Properly Tweaked, will give you tons of battery duration, device performance, but lacking the use of newer applications.
Custom Rom will do the Opposite. If you go for a Custom Rom.
Go for Nameless Rom. But make a variety of "efs" Backups. To prevent imei losses.
If you Experience YouTube crashes on DDLF2:
1) Root your device;
2) Install ES File Explorer;
3) Under the menu Click, "Root Explorer"; and make "/" and "system" re-writable. ("rw").
4) Go to the Following Path:
/system/framework or /system/apps
5) Long Press YouTube Icon (So you can select: "Uninstall"). Fully Uninstall YouTube (All Installdd Versions).
6) Set the File Explorerto Read Only Again and Restart the Device.
7) Install YouTube from Google Play and You are Good to Go.
Note:
If you still have issues there's a slight chance that your Custom Kernel could be causing such Issue.
Simply Flash a Different Custom Kernel for your Device. (i9003)

ok successfully flashed without CSC (DDLF2) 'cause i was not able to extract CSC file.
ROM works very good. I think it is faster then CM11 I had before.
is there any sense to flash XWKPG or XXKPE? what for? I have my native language on DDLF2 and Region settings so..
could You give me some piece of theory?
Thanks hitten to the OP!
---------- Post added at 12:18 AM ---------- Previous post was at 12:11 AM ----------
one more question..
Is it necessary to deodex this rom to gain ability to remove bloatware?
I didn't do so on the other devices before (they were newer ones) - only root and Solid Explorer with root rights.

All download links are dead...