"Those, who fail to read history are bound to repeat its mistakes"
People here have and did and will fail to read the things here and many did and many probably will have to lose their devices. You don't have to lose a device to get knowledge inbetween your ears.You don't have to be stupid. You surely can learn from your mistakes. But There's a better way. You can learn from others mistakes. This thread is a compilation of such mistakes ,that I personally have done and many others ,who did and their solutions aka The easy ways.
So, officially I congratulate you for finding this thread and reading Upto here. So, even if you don't read the whole thread, these are the main stuff you must know is
1. Rooting is a dangerous process -done by developers only. If you did root your device, you assume full responsibility for your device. So, if you can't think like one of the developers at least partly, I suggest you don't root your device ,coz when you mess up, the one who deviced the procedure or Rom will not help you. And everything you find here is in "AS IS " tag.
2.If you have rooted, next thing you must do is backup-
Go to recovery,
go to backup and restore
click backup.
I find it strange that this is not included in the root procedure. This surely would've helped a lot of Picos out there.
3.NEVER DO A RUU
-It unanimously holds the number ONE title for the major causes of bricking of Picos.
Trust me -Surely you can save your device, without the ruu. And with ruu, you're bound to fail without proper knowledge and research.
The only time you are suggested by experts to do a ruu is when you have already done a ruu "and" bricked it.
4. Overclocking here may cause burnt nand. -know what Rom you're using-it may have built in-overclock .
However, overclocking doesn't necessarily produce burnt-nand for all devices.
5.Finally, Not all answers you receive in the question and answer thread are good. Some answers will kill your device. So please judge the credibility of the answerer before you follow the answers. Generally, you could track back their previous answers and their working. Thanks meter is a good source of credibility -but not always -Not all who have big thanks record are helpful neither are they knowledgeable-There are spammers, who trick people into giving thanks.Do your home work before you trust a stranger. Recognized developer title is a good source of credibility.
The above five should save you a lot of trouble.
Ever in trouble? Drop by and read.
Do your googling,if you don't understand anything here.Have a great time !
Re: [faq][newbies only][mini edition]
��To start, this thread is only for newBies,who have rooted thier Rom and have a custom recovery. If you haven't, click here
Alright, this thread aims to answer all the frequently asked questions by newBies. The section this thread aims to answer will consist mostly of custom Roms especially cyanogen.
To start, we'll start with basics
Our phone consists of the following five partitions
1.Boot/kernel
2.Recovery
3. System/Rom
3.1What's not working
3.2 Latest links
4. /cache- error /last log
5.Data
5.1Scripts
6.Common issues after flashing Rom, scripts/GAPPS/PLAY STORE /
Ram
7. USB and CPU ,screen and power button-2/7/13
8. About developers and members
9. ��Burnt nand*recovrecovery 25/6/13 *��
10. STILL CAN'T FIND THE ANSWER ��
10.1LOGCAT
10.2ADB
11.MINI TIPS AND TRICKS
11.1CM9/10 themes
11.2.FONT CHANGING AND language तदधा ಥಮು support adding
11.3.DID YOU KNOW?
12. Recommended apps
13. BATTERY LIFE AND PERFORMANCE
14 .http://forum.xda-developers.com/showthread.php?p=38098604
BUILD. PROP TWEAKS
We'll discuss the faq in each.
All links are here
Index:
http://forum.xda-developers.com/showthread.php?t=1754876
This is the best link you'll ever have
Thanks hrkh83
Guides
http://forum.xda-developers.com/showthread.php?p=36057579
Guides for everything
Thanks hpsgill
Make yourself useful by akshat
Seen it before,
Just read this now
http://forum.xda-developers.com/showthread.php?p=37805872
Stock Roms instead of bricking ruu
tk immortal yash
http://forum.xda-developers.com/showthread.php?p=39101954
Re: [faq][newbies only][mini edition]
/BOOT(4 MB Max )
1.what does this partition contain?
It contains your kernel
2.what is kernel?
It's a in betweener between ROM (/system ) and your hardware.
Basically, a software, which connects the main software (your Rom gui) and the hardware
3 .what is the stock kernel version?
2.6
4. Is there a update available?
Yes. You can update it to 3
3.4 is currently being worked on
5.what are advantages of kernel 3 ?
Nothing much that you can feel
Basically related to stability, security, and future Android Os updates can easily be done for a310e
5.where are the links to kernel 3 ?
Look down
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
With cm9
1.Firewall
2.USB tethering
3. Wi-Fi hotspots
4.Vpn
Anything related to iptables
With cm10
Known issues
Ext4 cannot be mounted?
Temple run 2 and subway surfers reboots*fixed in overclocked kernel *burnt nand *
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. I wanna make my own kernel?
Special thanks to bhargz16
http://forum.xda-developers.com/showthread.php?t=2114594
10.Is there a overclocked kernel?
Yes
http://forum.xda-developers.com/showthread.php?p=38098604
11. How to Flash kernel? Do I need to clean install?
No need to clean install
Copy zip to root of /SD card
Go to recovery
Install zip from SDcard
Choose the correct zip
Install
Reboot
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/Recovery(5 MB Max )
First thing to do after root is to make a nandroid backup.
Go to backup and restore and select backup
1.what is this partition?
It contains your recovery
2.what is recovery?
It's a specialized partition for Android, which is used when something goes wrong.
We use it to change (flash) Roms, change kernels and mostly everything in xda. Make nandroid before you mess up
3. What are the recoveries available for a310e ?
1 .yannou90 (cwm5) recovery
2.Twrp 2 .3 by cute prince
3. twrp 2.2 by oblikas
4.cwm6 by sakindia
5.*OFFICIAL *The latest TWRP by bhargz16( http://forum.xda-developers.com/showthread.php?t=2123503 )
6.cwm6 by nihar.g
Links .check index link in top post
4. Are all of them stable?
The 1 and 5 are pretty stable.
What's not working:
cwm6 by sak let me down big time .
http://forum.xda-developers.com/showthread.php?p=38734554
Except 1,all other recoveries will not show charging animation, when you are charging your phone after switching it off ~instead of charging animation ~you'll be going to recovery
twrp official - some problems with ext4 partition has been reported and also reported to have been fixed. -I never had the problem before and after and I recommend this one 2.5 present here in xda.
twrp cute prince has issues restoring backups (problem with symlink )
5.what's the difference between them?
cwm5 - complete backups of all partitions
twrp - support compressed backups /file manager and other great things
cwm6 - your SD ext partitions will not be fully backed up during subsequent backups,but only the changed files greatly reducing the size of subsequent backups
6. Can you explain more about cwm ?
http://forum.xda-developers.com/showthread.php?p=38100620
7. Recommended apps.?
Recovery file manager aroma 1.8
8. How to flash a recovery?
Two methods described in detail in link above by bhargz16 ~ fast boot
Flash from phone:
Required:
Flash_image binary
You can flash any recovery
From terminal using
Code:
su
flash_image recovery /sdcard/recovery.img
You need recovery.img (renamed like that ) present in /sdcard itself
9. Error while restoring .Androidsecure /sdext ?
http://forum.xda-developers.com/showthread.php?p=39874898
10. Cannot go to recovery /burnt recovery /unable to flash recovery?
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/SYSTEM (235 MB Max )
1.what is it?
Here's where your Rom resides
Any cyanogen /ever/miui roms all go here
2. What are system apps
Any app in /system /app is system app and they have special permissions
2.1 how to make a app system app?
Uninstall the app with titanium backup and copy it's apk to system/app(normal delete apk will not delete. Dex and lib files ) ~reboot ~
Some apkS need it's library file also in /system /Lib (copy from /data /Lib to /system /lib )
3.what is binary?
These are executable ~very important files in /system /bin. (or /xbin in recovery)
Your root su is here
4. What are the roms available?
Many roms are available in xda
Main line ones are
CYANOGEN 7
CYANOGEN 9
CYANOGEN 10
Cyanogen 10.1
Miui
5.What is cyanogen 7 ?
It's a cyanogen version of gingerbread
9 is ics
10 is jelly 4.1
10.1 is jelly 4.2
5.1 what's the development going on?
cm7 *camera was unable to be fixed *development stopped
cm 10*active development now *
cm 10.1 *thread closed *
6. How to install a new Rom? Cyanogen for example?
Download the latest build. Zip and put in the root of /sdcard.
Go to recovery
Factory reset data
Wipe cache
Wipe dalvik
Wipe SD ext
Choose install zip from /sdcard and choose the build. Zip
Wait
Reboot
Go back to main ^|^
The nothing really bugs list
Welcome to THE "NOTHING REALLY" BUGS™
This is the official nothing really bugs Pico web post at xda. Its name implies that the bugs present are really nothing to some people. But to the rest, it may bother a lot. So, this post.
Here you'll find most of the nothing really bugs. All statements having "Nothing really " in bugs list directs here. This is to inform new flashers of what they'll get and what they won't. To make the facts clear,so that you won't have to flash every Rom to find out all the nothing really™ bugs. After all, this is a newbie friendly thread.
Please note that though every effort has been taken to ensure an exhaustive list of all the bugs .Some may not have been stated here .If you do find a bug, which isn't stated here, please feel free to mention it here and I'll add it after being personally confirmation by me or two to three renowned senior member witnesses. Further more, some bugs here may have been fixed. You can take a look at the last edited day of this post to make sure this post is up to date. And you can mention it here,if any of the information found here is wrong.
1.What doesn't work in cm10 4.1 Jelly beans ?:
1video (video recording with some third party apps~Skype video messaging, zoom camera ,camera magix and a lot more)(S. ucam works fully)
2Bluetooth headphones can't be used during call(try using sound about )✘
2.1 Bluetooth stereo headphones ✘
3vsync
4.stock camera force close often and unstable (S. Camera 360/ucam)
5.Wi-Fi unable to turn on ~from settings /notification bar. (s:Flash kernel 2.6)
6.burnt nand
7. Wi-Fi direct (native )causes reboot. (S. 3Rd party app ~fast file transfer)
8.some VOIP~{ex:gtalk(even after normal gapps),and many more}
9.Most streaming video{not flash, but those, which open in mx} doesn't work. Most TV apps don't work (not flash using tv apps)
10. mobile data may fluctuate for some(timedo app to turn on and off airplane mode for every hour)
11. calls robotic call for some
http://forum.xda-developers.com/showthread.php?p=32997468
12. Unofficial adobe flash is flickering too too much. (Only Firefox actually works with flash..which flickers unbearably ~the rest don't even work )
13. Headphones volume control during in call✘
14.USB tethering (native)✘
15. Wi-Fi hotspots work only as open source ✘
16.Bluetooth A2dp streaming ✘
17.Firewall rules don't stick, when put in init.d. Somehow the Rom process overtakes the firewall rules during boot and during some process. My intuition directs the blame at bandwidth controller| throttle service~|Data usage settings|which wasn't implemented properly, but using dirty hacks
18. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting. (s.flash kernel 2.6 with USb mass storage fix here. )
19. Multi mount SD app doesn't work [s.flash kernel 2.6]
OTHERS
1. Battery drain
2.Phone heating
3.WiFi toggle
Total :22[Because, I used this Rom for a long time,so the large number]
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
2.What doesn't work in cm9 ?
forum.xda-developers.com/showthread.php?p=35756952#post35756952
2VIDEO PLAYBACK doesn't work as well as stock
3 Wi-Fi toggle in latest RomS
4 Bluetooth stereo headphones ✘
Experienced by some:
A. Encryption doesn't work (crypt)✘
B.robot call http://forum.xda-developers.com/showthread.php?p=32997468
C.mobile data flickering
Note: video playback is much better in cm10.
Language rendering is also much better in cm10.
3.what doesn't work in Original HTC STOCK ROM?
A. if you ever click "reset to default" in the Camcorder settings..,all future video recordings will overwrite already taken videos and all previous videos will be lost(use ucam)
B. sending a more than 150MB file on Bluetooth file manager app through Bluetooth will reboot your device.
(use stock transfer)
3.1 what's not working in a rooted stock Rom?
(make a nandroid backup first to protect you)
Optimize storage in storage settings
Factory reset will put you in bootstruck.
4.What doesn't work in cm10.1 ?
Camera and lot more minor/major
Too long list
Will update when usable
5.what doesn't work in cm7 ?
Camera
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
3.Wi-Fi toggle from notification bar /from settings
4. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting.
5. Multi mount SD app not working.
With cm9
1.Firewall
2.USB tethering ✘
3. Wi-Fi hotspots ✘
4.Vpn ✘
Anything related to iptables
With cm10
Known issues
Some partitions [?Ext4] cannot be mounted
*burnt nand *
With latest cute prince kernel [power management fix ]:
Mounting of SDcard on some devices
Multimount SD app
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. Sense4 Roms
1.Burnt nand ~most common ✘
2.Random reboots ✘
3. WiFi direct. ✘
4.Bluetooth headphones ✘
Go back to main ^|^
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
S - probable third party solutions
Solutions for burnt nand -Please go to burnt nand section.
[COLOR="RED"]Welcome to [b]▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀[/B][/COLOR]
Welcome to ▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀
Not sure whether it'll be updated,but galaxyfreak released a app on latest Roms ~ http://forum.xda-developers.com/showthread.php?p=38913186
Why this post ?
Because index has only thread links and sakindia123 never updates op
If he does, then this post will not be updated anymore. Other than that, here are some kernel links as well. Other than the main line ones, the others are not updated. Sense4 links are already present in op and here as well http://forum.xda-developers.com/showthread.php?p=40111838 . Any link that's not present in op will only be updated.
1.what's the latest build on cyanogen 9?
Build 13
http://forum.xda-developers.com/showthread.php?p=36626369
#14*beware of burnt nand *
http://forum.xda-developers.com/showthread.php?p=38770875
2.what's the latest build on cyanogen 10 ?
Build 3.2.2.use with kernel 2.6
http://forum.xda-developers.com/showthread.php?p=38183817
Liverpool fan latest 3.2
http://forum.xda-developers.com/showthread.php?p=38447868
Beta 5~beware of burnt nand ~
Video fix by bhargz*liverpl 4 beta5*
http://forum.xda-developers.com/showthread.php?p=39124906
http://forum.xda-developers.com/showthread.php?p=39090779
Beta6~beware of burnt nand ~
http://forum.xda-developers.com/showthread.php?p=39166124
+
http://forum.xda-developers.com/showthread.php?p=39804373
(Flash this to prevent overclock)
Lock screen fix for both beta 5 and 6 .
http://forum.xda-developers.com/showthread.php?p=39043840
2.1 Aokp build link
http://forum.xda-developers.com/showthread.php?t=2208242
3.what is the latest build on cyanogen 10.1 ?
Alpha 3
http://forum.xda-developers.com/showthread.php?p=38094629
Alpha 4
http://forum.xda-developers.com/showthread.php?p=38325531
4.what's the latest build on kernel?
Old Kernel 3
http://forum.xda-developers.com/showthread.php?p=36572115
Kernel 3 v2 only for sense
http://forum.xda-developers.com/showthread.php?p=38466559
http://forum.xda-developers.com/showthread.php?p=39730163
Kernel 3 v2 for cm10
http://forum.xda-developers.com/showthread.php?p=39737920
http://forum.xda-developers.com/showthread.php?p=39804373
5. Is there a overclocked kernel?
http://forum.xda-developers.com/showthread.php?p=38098604
kernel 2.6=garudav5kernel
6. Kernel 2.6 for JB ?
http://forum.xda-developers.com/showthread.php?p=37649737
http://forum.xda-developers.com/showthread.php?p=36303556
7. Kernel 2.6 for ics?
http://forum.xda-developers.com/showthread.php?p=35797210
http://forum.xda-developers.com/showthread.php?p=36526379
http://forum.xda-developers.com/showthread.php?p=37550173
8. Side effects and solution of using kernel 2.6 on a kernel 3 based Rom:
http://forum.xda-developers.com/showthread.php?p=39452607
Basically, USB storage may not work.
To, make it work, Flash the fix attached with this post(don't remove battery @ any stage:sly-tested on my twrp 2.4.4 with cm10beta5.May not work with ics.
Alternatively, you can use multi mount SD app /root tool box lite app.
Attached zip md5: 8216eaf4a357b9cddc5cfd29b8d05a50
Attached zip sha-1: 408a075479745fe1713f8c55a968801f7f6160dd
Some more links :
http://forum.xda-developers.com/showthread.php?p=40964578
Super wipe zip
http://forum.xda-developers.com/showthread.php?p=38338418
Nand recovery procedure:
http://forum.xda-developers.com/showthread.php?p=38098622
tk to akshatshenoy.
Flashing an older ruu:
Not recommended @ any stage
http://forum.xda-developers.com/showthread.php?p=38694608
Even if it works,you might have problems data, battery drain etc.. if you Flash a wrong radio
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
http://forum.xda-developers.com/showthread.php?p=40035607
How to install kernel? Clean?
http://forum.xda-developers.com/showthread.php?p=38098513
QUESTION NUMBER 11 ABOVE
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/DATA (150 MB )
1.WHat's this?
It is the internal memory
2.Why is it important?
Because this is the place where all the apps go
No /data = no more apps
3.what's our available internal memory?
150 MB
User available 90 MB
4. Any way to increase internal memory?
By scripts
5 .Recommended apps to diagnose application not installed
Diskusage app
Log cat
6. What does a app contain?
App when installed splits into apk dex,and data(lib+data) files
Go back to main ^|^
Re: [faq][newbies only][mini edition]
SCRIPTS
Before we start, a app when installed takes space as three parts.
They are apk,dex and data (lib+app data)
All scripts work by symlinking
1. What are the scripts available for our explorer?
Partial scripts
A.Link2SD app
Moves apk,dex,lib~doesn't move app data
B.Root data2SD app
Need ext partitions
Moves application data2 ext
Full scripts--Need init.d support able to move fully /partially as per requirements
Links available in index
1.Mount2SD
Download from play store or from here check index
Famous for it's stability and frequent updates
Issues +
2. Int2ext
As per script, moves partially /fully .
Has a large user base
issues ++
3.s2e
Moves fully.
Issues +++
NO official version for jelly beans.
4.a2sd darktremor
Issues ++++
However works pretty well with stock Rom and jaggy Rom
Discontinued
5.ungaze script
Issues +++++
I don't recommend it.
Why not?
Because
http://forum.xda-developers.com/showthread.php?p=33750812
http://forum.xda-developers.com/showthread.php?p=31915607
1.1 mount2SD doesn't work? Script not executed fully @ boot?
Flash kernel 2.6 from above and you should be good to go.
2. How do I increase internal memory (literally ) from 150 MB to 2GB(for example SD ext )?
Use mount2SD reverse mount
Use int2ext
Side effects:
As per Android rules, 10% of internal memory will be unavailable
So, 200 MB out of 2GB SD ext will be unavailable
Mount2SD also has normal moving methods ,which will make Android think you'll have 150MB but you can fill up 2GB inside of 150 MB (Here 10% would mean 15 MB)
3. I installed d2ext/similar ,I'm not able to install more apps ,even though I have more SD ext space?.
A. First make sure you don't hit 10% data limit described above
B. Use diskusage app to determine,which partitions are full
For example- some scripts don't move dalvik and so dalvik will fully accumulate in /data creating no space.
C. Fix permissions from recovery, wipe cache and dalvik and reboot.
4. My Rom doesn't have init.d support /I'm using stock Rom?
Check index
You can add init.d support by
Flashing custom kernel (cranium)
Flashing scripts to make init.d support (or pimp my Rom app[not tested])
5. Where to add scripts before flashing Rom?
Add it in /system/etc/init.d (permissions are rwx rwx rwx ,if you're adding this in recovery after flashing )
For mount2SD add configurations folder in /data/m2sd.
6. How to migrate from link2SD to mount2SD?
http://forum.xda-developers.com/showthread.php?p=38840247
7. Is there a full script so that I can use both my internal memory and SD ext?
A bit complicated, but this what I use...
Configure mount2SD
To move both apk and dalvik
Don't move data.
Then open titanium backup to move app data
@First move one app data to create data2SD directory.. then you can batch move whatever apps you think fit.
But please make sure you have at least 10 to 30 MB in /data and in/SD ext (SD ext not necessarily ) before a nandroid backup. Otherwise restoreS will not work.
Go back to main ^|^
Re: [faq][newbies only][mini edition]
Common issues with scripts:
0. Device stuck @ HTC logo with 4 error icons on all four corners
Since you flashed an ruu and failed user data fail etc.
Unlock bootloader if possible
Flash twrp recovery again
Code:
fastboot flash recovery.img
Then go to recovery with this command
Code:
fastboot boot recovery
Now that you're in recovery wipe everything, format everything .
If flashing failed /you can't enter recovery, do this keeping twrp recovery.img in /SDcard
Code:
fastboot boot /sdcard/recovery.img
Do cute prince recovery procedure shown in burnt nand section
Flash erase mtd3 as well
Now Flash your Rom and boot
If it doesn't boot, repeat the whole procedure above and now
Do ruu.
If all the above failed,
http://forum.xda-developers.com/showthread.php?p=39181288
Read the above thread fully. That's the last resort.
Moral : Don't ever Flash an RUU (if you haven't already )
You can Flash stock Rom ~safer
1. Device struck in HTC logo
Wait for 15 minutes
Try pulling out battery and reboot
Update busybox and try installing scripts again
Convert your partition to ext3
Change your kernel to 2.6
2. Mount2SD ~apps update after every boot?
Turn cache off in app
Turn safe mode off
Clear cache and dalvik ~fix permissions ~reboot
Common issues after flashing:
1. I get status 7 error?
Open archive with Bluetooth file manager and check archive integrity
Try different compression method(thanks hpsgill)
Delete system apps
2. I get status 0 error?
Update binary used is different
Exchanged update binary from a working zip to this one
Other errors can be cured by changing recovery .
http://forum.xda-developers.com/showthread.php?p=38469360
Common issues after flashing Rom:
1. Always do a clean install
To wipe everything except /sdcard.
Even in /sdcard delete Android /data after backup
2. No I won't listen. I want to do you a dirty install. Show me how?
Your choice
http://forum.xda-developers.com/showthread.php?p=35903694
3. I get force closes of all apps?
Dalvik problem.
Clear cache and dalvik cache and reboot
4.I get force close of a specific app?
If it's a paid app, then you need to change your Android id to your original Id with Android id changer /titanium backup
Not a paid app?
Clear cache and data of that app and reboot
Fix permissions
5.reboot after reboot?
Thanks bhargz16
Kernel problem. Change kernel
GAPPS:
1. This gapp always force closes?
A. If it's a gapp found on play, just uninstall that gapp from system using titanium backup and then reboot and install from play store.
B.if not found on play, then try flashing a different gapps version from goo.im .
Make sure you have enough space on /system and on /cache before flashing and then flash. If not delete unused apps like stock keyboard ,etc
2. RPS5~AEC0/927/any other error while downloading apps from play?
A. Clear data cache of play store app
Reboot
B. Clear data of google services framework
Reboot
C. Remove your google account and re add it. Reboot.- this worked for me.
3. All my apps are missing from installed apps in play?
Wait for some time,if you've flashed a new Rom
Clear data and cache of play store
Reboot
Download app eric market fix *use @ your own risk *
Repeat the solution of questions 2.
Go back to main ^|^
Part 2 on next page :thumbup:
Re: [faq][newbies only][mini edition]
CPU:
1.Can you overclock?
IMO,
All overclocking burns nand.
It's just a matter of sooner /later.
Read this post before attempting anything
http://forum.xda-developers.com/showthread.php?p=38445346
Burnt nand recovery procedures here ~~the third post below this post
http://forum.xda-developers.com/showthread.php?p=38098622
The links below are old. All latest Roms come with overclocked burning kernels.
cm10:
http://forum.xda-developers.com/showthread.php?p=38189883
cm10.1:
http://forum.xda-developers.com/showthread.php?p=38336080
gpu oc
http://forum.xda-developers.com/showthread.php?p=38331698
cpu oc
2. Governors ~what are they?
As the name says they govern when the cpu should go to higher speed and when they should sleep
Performance governor always keep your phone at Max
Powersave keeps your cpu always at low
USB :
1. Flashed kernel 3 and USB doesn't work.?
Flash kernel 2 back.
2. I want to know how to fix USB +kernel 3?
Don't know
3. Can I have usb otg ?
No, not yet.
SCREEN AND POWER BUTTON and soft keys:
1.SCREEN turns on after turning off ?
A. Some apps are trying to make screen on. After screen turns on, go to settings immediately and open running applications, you may be able to find the culprit. It's probably the app, which is restarting. Some apps like lock any app screen etc. Logs could be helpful.
B. Some users reported it could be a hardware problem -look below for power button issues.
C. Some users reported it could be a script problem (rare )
2. My home screen button and /or search buttons doesn't work?
A. Did you do a dirty install of new Rom
Clear cache and dalvik and fix permissions and reboot
B. Copy com.Android.providers.settings /databases from your previous nandroid backups(use yaffs file manager /nandroid manager)and paste it in it's respective location now (paste it using file manager in recovery )
C. If that doesn't work, clean install again
Tech savvy? ~search for device provisioned 1 in cyanogen forums
http://forum.xda-developers.com/showthread.php?p=38633404
3. Power button doesn't work properly ?
A. If it's not a software problem(try the above solution first),then you broke it.
If you broke it, avoid using the power button anymore-use attached scripts indeed.
There are apps in market to simulate power keys.
Or
http://forum.xda-developers.com/showthread.php?p=38633404
Go back to main ^|^
Re: [faq][newbies only][mini edition]
Miscellaneous topics:
Subject to change without prior notification
Developers:
1. Who are the developers that make these roms?
1. Cute_prince
2.sakîndia123
3.derefas
4.lirokoa
5.liverpool fan
6.bhargz16
7.nihar.g
8.ngolralph
And many others. The above are the developers of the roms that I used and present in no order.
2. Why doesn't sakindia123 update the OP ?
Disclaimer: Since it is one of the most faq by newbie,I'm forced to discuss here. I personally do not know sakîndia. If you still want more info, contact senior member hpsgill
You see.. He does nothing without reason. If he doesn't, then the last build present in op will be more /less equal to the latest build. There are other reasons ,which if I had to speak of them all, time wouldn't let me and I would have to deal with flaming members and mods and deleted posts and locked threads . Furthermore that question is well out of the scope of this thread. You are instructed not to ask this question any where.
YOU HAVE BEEN WARNED.
3. How can I contact these developers?
You can by studying Android development and codes, bccms,404s,tr2s and then talking to them. You'll have better luck talking with non recognized developers than the rds.
And try discussion threads .
4. Why doesn't a developer answer my question? (I'm being polite here)
Because the developer doesn't know the answer
w.r.f to http://forum.xda-developers.com/showthread.php?p=38095857
Or your question has already been answered. Try searching for your question at the least 10 pages back.
or your question is too silly to answer
Or your question is not seen ,because they don't have time .
5. Why do they do this ?
For passion of development, addicted, and for learning purposes.
So, that means they don't work for you. They don't help you. They do what they want.
6. I feel a emptiness around forum members. Was there a developer who worked here, yet left without goodbye?
Well not sure about goodbye, but yes his name is jaggyjags.
sakIndia123 came only late and his first work his cranium kernel, which he abandoned like it was nothing.. buried it along with jags. Cruel things did happen before you were here.
Go back to main ^|^
Members:
1. Why won't members answer my question?
Again, thanks to bhargz16
http://forum.xda-developers.com/showthread.php?p=38095857
Or question has already been answered over and over again. Try searching for your question and read at the least 10 pages back.
Or they don't want to help you
Or may be you aren't polite
Or they want thanks
2. Why do they want thanks?
You see.. you should hit thanks for them in order for them to reply
3. Why hit thanks?
Because they are thankaholics .
This addiction
Some call it want,
For some it's need
Some call it greed
And some call it hunger
And some childish foolishness
Never hit thanks, unless you mean it. Never sell yourself short. Mean it, then hit it.
http://forum.xda-developers.com/showthread.php?p=32867800
My first thread closed by mods
:crying:
Having said that, please do be grateful for what you receive. Hitting thanks is like giving a eternal reputation mark on them rather than just saying it. Saying just makes a temporary mark. Get it. 
4.what is spam?
Spam is going out of topic . It never should be done in dev threads unless thread is dead.
Some do the work of mods pretending to be mods.
5.who are mods?
They are moderators who have power to ban anyone at will (in short )
And they are losing patience
http://forum.xda-developers.com/showthread.php?p=37950595
6.Can I spam here?
Feel free to speak what you want..
7. If I feel something wrong is going on /flaming /threatening, who should I report to?
You can use the report system~that (!) mark over every post. Click it and your issue will be resolved within a hour(probably ).
Go back to main ^|^
[color="red"] [b]
0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1
0„30†2Moved by touch0160†640„30†3Inc.
0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨1
0. What's burnt nand?
It's condition caused by overclocking(oc)[CPU oc ,to be specific. For gpu oc,go to the last part of this post question 10 ] resulting in bad blocks all over your system, data, cache and recovery.
Important: Use diskusage app to determine size. Don't go by phone's inbuilt settings
A case of burned /system partition in cm10 beta6 running overnight:
Uploaded with ImageShack.us
A late case of burnt nand of /data :
Uploaded with ImageShack.us
1 &2:Not applicable anymore. Peace!
3. No one has burnt thier nand*it's just some people think that thier nand is burnt * is this true?
Well, I'm sure, going through the forums and q &a ,I know that people have indeed burnt thier nands and some just by using the overclocked kernel without even overclocking.
Sources:
http://forum.xda-developers.com/showthread.php?t=1847002&page=400
http://forum.xda-developers.com/showthread.php?t=2243719
http://forum.xda-developers.com/showthread.php?p=39985385
http://forum.xda-developers.com/showthread.php?p=39799173
http://forum.xda-developers.com/showthread.php?p=39439861
http://forum.xda-developers.com/showthread.php?p=39428922
http://forum.xda-developers.com/showthread.php?p=39402187
http://forum.xda-developers.com/showthread.php?p=38941663
http://forum.xda-developers.com/showthread.php?p=39216556
http://forum.xda-developers.com/showthread.php?p=38945489
http://forum.xda-developers.com/showthread.php?p=39197918
http://forum.xda-developers.com/showthread.php?p=39169697
http://forum.xda-developers.com/showthread.php?p=38657723
http://forum.xda-developers.com/showthread.php?p=40616272
http://forum.xda-developers.com/showthread.php?p=39331139
But below is a strong correlation with bad block proof between overclocking and burnt recovery. Yes it burns recovery too.
http://forum.xda-developers.com/showthread.php?p=39196574
THE ABOVE LINKED POSTS ARE MOSTLY SOLVED BY ME OR SENIOR MEMBER S, BUT SOME HAVE LOST THEIR DEVICES. IF YOU CAN'T FIND THE ANSWER HERE, I SUGGEST YOU READ ALL THE LINKED POSTS-VARIOUS DIFFERENT METHODS HAVE BEEN EMPLOYED.,WHICH ARE TOO LONG TO EXPLAIN HERE. READ AND READ-YOU'LL FIND.
4. What are the symptoms of burnt nand?
Early symptoms:
You'll notice a strong drop in your free space in /data
Late symptoms:
/data free space is Nil /below 50%of what you saw before
Error in /cache /recovery/log.
Error in /cache/recovery/last log.Not readable.
No apps can be installed
Rom lags like hell
No Rom can be flashed /boots
Previous nandroids ,which are successfully restored before fails to restore now.
Really abrupt and fast restores with twrp
RUU cannot be done ~user data(mtd5) fail. System fail (mtd3)
5. How can I diagnose burnt nand early?
If you suspect burnt nand ,
1.Watch out for free space in /data and watch out for sharp reduction.
2.Download this app Disk Usage and watch out for increase in system data in /data
http://forum.xda-developers.com/showthread.php?p=39464989
3.Make a dmesg and look for these errors
http://forum.xda-developers.com/showthread.php?p=36834988
4.Definitive method is this :
shahrooz_ra said:
hello
is there any linux terminal command for check badblock on nand memory?
Click to expand...
Click to collapse
1.DOWNLOAD THE TERMINAL.ZIP ATTACHED BELOW
2.EXTRACT TERMINAL.ZIP INTO /SDCARD/lol [create a folder named lol[small letters ]in SDcard, if there already isn't one ]
3.Open terminal emulator on your phone
4.type or copy and paste this code and press enter
Code:
su
cp /sdcard/lol/runme.sh /r.sh
chmod 0755 /r.sh
/r.sh
5.if it doesn't work first time, paste twice.
6.If pasting twice doesn't work, type each code one by one -you'll surely get it. Come on-its just 4 lines -type it lazy!
And Now you'll see the number of bad blocks you've got.
You can also Flash the zip below[for which you have to go to recovery ]or execute the attached script badblocks.sh as root.
6. What are the parts affected by burning?
Proved to affect
/Data
/system
/cache
/recovery
Rest is unknown
7. Ok I managed to burn my nand What are the recovery procedures available?
I SIMPLIFIED THINGS HERE BY MAKING A FLASHABLE FLASH_ERASE. ZIP[Code named FLASH_ERASEmadeflashablebyBANNED.zip ] it works with twrp2.5 to flash_erase needed partitions. However not tested fully. Problem? Post here.
Other long procedures:
Cute prince recovery procedure:
http://forum.xda-developers.com/showthread.php?p=36868966
I think Cute prince missed this .Just add this at the end
Code:
./flash_erase -N /dev/mtd/mtd3 0 0
7.1 I GET FLASH ERASE NOT FOUND?
Flash the flash_erasemadeflashablebyBANNED.zip
Derefas recovery procedure:
derefas was the one who actually gave the idea of recovering nand
http://forum.xda-developers.com/showthread.php?p=36867557
Sachin Thomas recovery procedure
Developed lately *can be done on phone itself */if it didn't involve recovery /*
http://forum.xda-developers.com/showthread.php?p=38941897
Recovery recoveriNG procedure (bhargz16)
http://forum.xda-developers.com/showthread.php?p=39198068
8. I can't find my answer here?
Go to official burnt nand discussion thread
http://forum.xda-developers.com/showthread.php?t=2183130
Or you can ask your questions here.
9.can I Flash any other kernel to prevent overclocking?
You can Flash garuda2.6
Link in latest links post page 1.
http://forum.xda-developers.com/showthread.php?p=38098567
Side effects:
http://forum.xda-developers.com/showthread.php?p=39452607
10. Some more links:
Unknown recovery procedure
http://forum.xda-developers.com/showthread.php?p=36836090
MTD status report:
http://forum.xda-developers.com/showthread.php?p=36837173
11. Cannot go to recovery /burnt recovery /unable to flash recovery?
Not sure of the exact command,but will work.
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device [do ruu here, if you haven't been able to enter hboot before]
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
12. GPU OC ?
gpu oc has been reverted along with CPU oc by sak for burnt nand. But may be added later. but not present in cm released on or two months before 9 may13.
12.1 is it safe?
I don't know. CPU oc did provide burnt nand and bad blocks. Gpu oc may also do some things, which may not be seen as of now. I've seen one case complaining that, after using Cyanogen and going back to stock - games started lagging, which did not lag, when he was in stock before. The reliability is doubtful. But not much people go back to stock either -so not much can be said.
12.2 do you recommend it?
"If any provider of any oc removes the "AS IS" tag and take responsibility,if something happens, then I'll probably may use that oc,otherwise count me out".
12.3 How to remove gpu oc ?
Its present in kernel. Flash another kernel. Or modify source and compile yourself.
Present at arch/arm/mach-msm/msm7x27a.c- kernel source.
Try here
Normal [bus, Gpu] is [0,133330000],[160000000,192000000],[200000000,245760000] I think.
13. Was there anyone unable to recover and lost thier device for ever?
AFAIK,
"The lost thier device for ever list RIP "
Ghostking
Hawk378
And May be many more
Legend *:
Attachment list:
***********************************************************VERY IMPORTANT : UNDER CLOCK BELOW 300MHZ ,IF YOU ARE USING ZIPS WHILE SYSTEM IS RUNNING.AFTER THE TESTS, YOU MAY OVER CLOCK AS YOU WISH. ********************************************************************************************
Provided "AS IS"
1- script to detect badblocks by banned.
2-flashable zip to detect badblocks by btfb0
3-Terminal method to detect bad blocks by banned .
4-flashable zip to detect bad blocks by banned.
5- Recovery procedure to delete bad blocks- Made flashable by BANNED.
All zips posted here has readme.txt files inside it-which are self explanatory to that particular zip.
*USE AT YOUR OWN RISK*
Re: [faq][newbies only][mini edition]
I have a question not answered here?
Post your question in the q&a section after making sure that your question hasn't already been asked.
Please use search button on the top right to make sure that your question hasn't already been asked. And it'll help you to find more answers.
Follow detailed instructions here
http://forum.xda-developers.com/showthread.php?p=33608527
And post with logcat increases your chances of resolving the problem
ADB
What is logcat and ADB?
Special thanks to akshat.shenoy
http://forum.xda-developers.com/showthread.php?p=37805872
He'll explain things better
Basics of ADB:
http://forum.xda-developers.com/showthread.php?p=9936674
Partition and wipe SD ext with ADB:
http://forum.xda-developers.com/showthread.php?p=38706881
Re: [faq][newbies only][mini edition]
reserved
Re: [faq][newbies only][mini edition]
MINI Tips and tricks:▶?
1.How can I apply cm9/10 themes?
http://forum.xda-developers.com/showthread.php?p=35530897
Download the zip from here, read instructions there and flash it in recovery
Now you can use any HDPI themes on your Pico
Thanks ngoloralph
2. How do I change fonts?
Download Rom toolbox lite and go to font installer;
A. If you're on stock, the rest is automatic
B.if you're on cyanogen 9/10/11,if you change the droid sans /others as recommended by app, you'll end up in boot loop (possibly because of symlinking of robot sans & droid sans )
In such a case go to preferences and click to overwrite only roboto regular font and everything will be fine.
Take a look
Uploaded with ImageShack.us
3. How do I add a new language support to my device?
Note: no new language gui can be added by this method. This only adds support. Instead of seeing boxes, you may see your language. If you want full language support, you can go to this abandoned thread.?? http://forum.xda-developers.com/showthread.php?p=40890599 ??
Language support can simply be added by adding a Android supported language font file in /system /fonts and give it permissions rw r. r.(font files can be found all over xda )
Step 2. Open system /etc /fallbackfonts.xml...
There should be a lot of font file names there.. just delete a font name that you don't want and add your font file name (the name of the file which you put in /system /fonts)
In there.
Practice makes perfect.
This method however doesn't work /only partly works for complex languages /script like Hindi Arabic etc.
DID YOU KNOW?
1. Long pressing reboot button (in the menu after pressing power key) will get you into safe mode
2. Long pressing power keys and volume keys + and- for more than 30 seconds will reboot your device (tk to hrkh83)
3. Repeatedly pressing certain options(like Android version) in the about menu in settings(on cyanogen ) will take you into different settings (tk liverpoolfan)
Go back to main ^|^
Battery drain
BATTERY DRAIN
Of course, we're gonna talk about drain.
Before we start, I want to disprove some prevalent concepts
1. Battery calibration
It is supposed to increase Battery capacity and increase Battery life and it makes your phone to show the correct Battery on the notification bar.
FALSE
It doesn't do any of those. Calibration is just deleting Batterystats.bin file. That file holds info about how many seconds each apps were running for.typically it's blameometer. It shows the information you see in the battery chart in your settings. Nothing more.
Source: article
2. Cycling your battery life from 0 to 100 and 100 to 0 will typically increase Battery life. Further more you should make sure it comes to zero by turning on the phone,every time it got switched off on it's own.
FALSE AGAIN
Nothing could destroy your Li-On Battery than extreme low voltage. You can be sure that this will destroy your battery life more than anything. During storage it's recommended to keep the battery in cool place with 40%Battery.
So, don't use any battery draining app from market.
Ok, since we took out the false foundation, it's time to put some true working tips to save your battery during usage and it's overall life
1. It's recommended to charge as often as possible ~every time you get a socket. Though not to keep @100 all the time. Overcharging theoretically may damage your battery, but your phone comes with various safety mechanisms to prevent charging after that.
2. Limit the number of apps. Definitely would produce good Battery.
3. Limit the number of apps, that run in background all the time.
Typical example would be facebook.
PERFORMANCE:
4.Disable autostarts for all apps, that you don't use much~using autostart manager.
Disabling autostarts for the clock app will make you get up late. Use common sense.
This alone should drastically improve your performance
5.Use lightweight launchers ~Nova.
Go (any go products) is not advisable
6.Post ICS, Disable media scanner receiver.
You can use elixir app to disable media scanner receiver. This will scan your SDcard over and over again resulting in Battery drain,which is significant, if you use a bigger SD. Use media scanner root to enable and disable.
As far as the usual ones,
7. Disable autobrightness
8. Keep screen @ minimum brightness
9. Disable autorotation
10. Disable location services.
GAPPS:
11. Disable GSF (google services framework ) receivers ~the ones with gtalk on it.
12. Disable auto sync
You can use timedo /timer Android to turn on sync twice /thrice daily.
13. Reduce number of accounts. Better to keep single than three accounts.
14. Good internet connection. Amount of energy taken to re connect is supposed to be far more than amount needed to keep a connection.
15. Undervolt/with underclock
RECOMMENDED APPS:
1.BETTER BATTERY STATS ~free for xda.
2. Onepower guard
I haven't found satisfying results with this app, but still try it out
3.greenIFY
I haven't used this @ all.
4. Any app, that is used to reduce /increase heartbeat sent to google servers.
Well, that's all I've learnt as of now.
Re: [faq][newbies only][mini edition]
Recommended apps section (only free)
Top apps
0. Superuser by koush (Clockworkmod)
1. Titanium backup
2. Efficient backup
3. Floating logcat ~logcat extreme
4. Catlog
5. Aroma file manager (recovery use only)
6 .Es file explorer
6.1 es file explorer v2
7. Yaffs file manager
8. App extractor
8.1 nandroid manager
9. Loaderdroid
10. Xda app
11. Elixir (much useful to disable app components than it's actual use)
12. Android pro widgets(similar to HTC friendstream)
13. Nova launcher
14. Timedo
15. Live logcat lite
16. Rom toolbox lite
17. Screen stand by root(turn off screen without making phone to sleep)
18. Disk Usage
Launcher:
1. Nova
2. Apex
Downloaders:
Loaderdroid
Multimedia players:
Video
mx
bs
qq
Audio
Ttpod
Equalizers
NOOZOXIDE REWIRE PRO
Walkman sound enhancements
Awesome beats
Cyanogen Dsp(better than stock )
Equalizer from market.
Cam/corDer /video recorder:
Camera:
Camera 360
ucam
spycam
Video recorder
ucam
Zoom camera
Camera magix
Browsers:
Fast and server based
Uc browser mini
Opera mini
Opera mobile
uc browser
Puffin browser
Full fledged browsers
Firefox
Dolphin
Google chrome beta
Chrome
KEYBOARDS ?
Touchpal keyboard
mĺ has internet permisn wid emoji
Office apps:
Kingsoft office(better than paid apps)
Zip extractors:
Zarchiver(ant-one)
Screen off(w/wake lock):
Screen stand-by
File managers:
ES explorer
Fx file explorer
Call recorders:
No known call recorders are working.
Stocks:
Personal finance
Superuser:
Superuser by koush ~open source&free
Super su ~made pro free after the release of prior~closed source ~
⇧Go back to main ♠
THE END.
© All rights reserved 2013?
Autoramdisk exchange alpha
MINI ADVANCED SECTION:
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.071 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Update:
I have got it to work and complete
http://forum.xda-developers.com/showthread.php?p=40035607
Old post: too lazy to delete
Present condition:
Hi. I cannot get it to work on HTC Pico yet .It may work on other phones. If someone can, please feel free to complete it provided you give proper credits And you do not make money out of this.
What's this?
It's a procedure (wip) to Flash any kernel without the need to change ramdisk.
As new kernel gets released, you don't need to change ramdisk to suit your Rom.
Automated procedure:
Open any kernel.zip with any zip extractor on your phone
Copy the script below and paste it in updater-script present in meta~inf/com/google/Android
(delete any other things written there. )
Code:
package_extract_dir("bin","/tmp");
set_perm(0, 0, 0755, "/tmp/busybox");
set_perm(0, 0, 0755, "/tmp/unpack-bootimg");
set_perm(0, 0, 0755, "/tmp/mkbootimg");
set_perm(0, 0, 0755, "/tmp/dump_image");
run_program("/sbin/dump_image","boot","/tmp/oldboot.img");
run_program("/tmp/unpack-bootimg", "-i","/tmp/oldboot.img","-o","/tmp");
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/tmp/busybox", "mkdir","/tmp/boot");
run_program("/tmp/unpack-bootimg", "-i","/tmp/boot.img","-o","/tmp/boot");
run_program("/tmp/busybox", "rm","-r","/tmp/kernel");
run_program("/tmp/busybox", "mv","/tmp/boot/kernel","/tmp/kernel");
run_program("/tmp/mkbootimg", "--ramdisk","/tmp/ramdisk.cpio.gz","--kernel","/tmp/kernel","-o","/tmp/newboot.img");
write_raw_image("/tmp/newboot.img", "boot");
delete_recursive("/tmp/newboot.img", "/tmp/boot", "/tmp/oldboot.img", "/tmp/kernel", "/tmp/ramdisk.cpio.gz","/tmp/boot.img", "/tmp/busybox", "/tmp/unpack-bootimg", "/tmp/mkbootimg");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
Download zip files from the source link below
Extract it and copy the bin folder from there to your kernel folder directly.
There should be 3 folders in your kernel folder ~bin folder, meta inf folder, system folder and boot.img
Now compress it and Flash
Note that this is only applicable to change ramdisk. If the boot. Img needs more work than that, it won't work. Essentially, it won't work on sense4 compiled kernels and vice versa
Manual terminal emulator method:
Alright guys, one last tutorial from me making my last mark here .This tutorial is not tested fully and probably never will be due to lack of time. And it will work for sure ~but May have syntax errors.
Credits:
1.trevd for arm executable binaries.
2.Xda university.
Requirements:
1.Any Android 2.3+ rooted
2.Android terminal emulator
3.arm executable unpack-bootimg binary and mkbootimg binaries (find it below )
History:
I wanted to change ramdisk for kernels for a long time on phone itself ~probably for a year or more . But anyone who tried to unpack using normal unzip apps would've noticed that other data.img and even system.img in clockworkmod could be unpacked easily, but not the boot.img and recovery.img. When I searched to unpack, it was easy with computers using the unpackbootimg binary for Linux. Problem was it wasn't cross compatible with our phones . So, I was searching for quite a while,until I found trev on xda university and he had made arm executable binaries for unpacking, repacking. Actually the main reason these binaries were created was for far greater and more advanced purposes i.e. to use apply patch functions in update binary and update script to Flash ramdisk on phone without flashing the kernel itself or vice versa (AFAIK)[ The apply patch functions are used in normal ota updates for any Android phone ]. Anyway I took those binaries to unpack kernels on our phone to change ramdisk. I write this for those, who want to change ramdisk on thier phone, but had no experience in PC whatsoever. And also by doing this, I share the unpack boot image binaries by trevd for Android phone ,so that any advanced member May use it for kernel updater scripts~think about it ~one zip for all cm9/10/10.1. Ofcourse the rest is up to you. Thanks for reading
Procedure:
1.Download the zip given in source below
2.Unpack it
3.Find these two binaries in /system/bin
Unpack-bootimg and mkbootimg
4.Copy them to /system/bin and give them full execute permissions in es explorer and read/write permission for user.
5.For easy remembrance,say, b1.img is your original boot image for your Rom(and Android,say cm10 ) and b2.img is the new kernel released for cm10.1
6.You want to change the ramdisk ofb2 cm10.1 to cm10 ,so that you can Flash the new kernelb2 for your cm10
7.Create new folder in SDcard named boot and put both b1.img and b2.img there
8.Open terminal.
9.type the following code one by one
Code:
su
cd /sdcard/boot
mkdir /sdcard/boot/b1
mkdir /sdcard/boot/b2
unpack-bootimg -i /sdcard/boot/b1.img -o /sdcard/boot/b1
unpack-bootimg -i /sdcard/boot/b2.img -o /sdcard/boot/b2
rm /sdcard/boot/b2/ramdisk.cpio.gz
mv /sdcard/boot/b1/ramdisk.cpio.gz /sdcard/boot/b2/ramdisk.cpio.gz
mkbootimg --kernel /sdcard/boot/b2/kernel.img --ramdisk /sdcard/boot/b2/ramdisk.cpio.gz --base 12C00000 -o /sdcard/b2new.img
rm -r /sdcard/boot
Note: the last rm command will delete all your old kernels ~don't execute it, if you don't want to have it deleted.
10.Now you have new kernel boot image with your ramdisk in /sdcard/b2new.img
11.Put it back in the zip with it's modules and
12. Flash
13.Hoping it'll work.
14.That's the end.
Source and binaries here:
http://forum.xda-developers.com/showthread.php?p=36931024
For dream and Sapphire models, you can use the binaries created by koush ~ which is found in his github ~any kernel project.
I'll probably be leaving soon
Kind of feel like working for xda. I guess sak and others would probably feel like it later. It's been great while it lasted. So this is probably my last project. If I did have some extra hardware during this period, things May have been different. It's good, while it lasted.
"The fantasy of a dream is that, it's still a dream, when it becomes reality, then it's no more a dream and the fantasy is lost. "
「Good bye xda」
So long:angel:
Re: [faq][newbies only][mini edition]
one more
The Infamous BUILD.PROP Tweaks :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
from
http://www.droidforums.net/forum/droid-4-roms/234899-examining-build-prop-tweaks.html
Guess that'll end this hoax for good.
One thing that was useful for me was this
http://www.modaco.com/topic/347274-guide-making-cm-utilise-both-cache-and-data-for-dalvik-cache/
Related
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.
So I created a new thread for this so I can edit the first post for release-info.
This is the old thread:
http://forum.xda-developers.com/showthread.php?t=1133866
Please note that the multiboot-feature will be removed if you update your real system.
The virtual systems will stay on the sdcard so just reinstall the mod and you can boot your virtual systems again
Changelog:
Code:
[B]v0.8:[/B]
- addon.d (Multiboot will be kept on ROM-Update)
- working reboot recovery inside multiboot-rom(will boot directly into the recovery for that rom)
- working reboot into bootmenu inside multiboot-rom
- security-fixes
- TLS-support
- fixed sdcard-problems for NAND-system
[B]v0.7:[/B]
- added integration in touchbootmenu. This is no compatibility-patch - since now multiboot can only be used in combination with touchbootmenu
[B]v0.6.1:[/B]
- fixed some memory-leaks in kernel-module
- fixed stupid bug which prevented creating backups on first start
[B]v0.6:[/B]
- new hook-method with kernel-side code which should be the solution to most rom-problems
- fixed a bug which prevented mounting cache-partition inside recovery
- fixed installer-bug when TouchBootmenu is used on NAND
- reboot to recovery/bootmenu does not work for now. will be fixed in future
[B]v0.5.5:[/B]
- support for Stock-roms with Greenbreadmod
- added version-file(for updater which comes soon)
[B]v0.5.4:[/B]
- fixed problem with install-script
[B]v0.5.3:[/B]
- support for TWRP recovery
- fixed problem with virtual systems with names longer than 9 chars
- don't change 2ndBoot-script for bootmenus with 2ndSystem-support
- show graphical error-message when error was detected and copy log to "/cache/multiboot/error.log"
- experimental support for booting stock-roms
[B]v0.5.2:[/B]
- more configurable(via config-file)
- fixed error-detection. On early errors you will get back to bootmenu
- fix boot-problems for some roms
[B]v0.5.1:[/B]
- fixed crash of GUI when choosing recovery
- fixed bug which prevented creating important images on first boot
- virtual systems now are using nand-backups with real data so you could install backups of virtual systems on NAND
- installer sets default bootmode to 2nd-boot
- added recovery-option for NAND
- patch background-image of virtual recovery so you see if you are flashing real or virtual system
- reboot system if you click "Go Back" in virtual recovery(until I found a solution for going back to multiboot-GUI)
[B]v0.5:[/B]
- better protection against unwanted changes on real partitions(thanks wizwin)
- fix Phone for for GB-kernel(thanks quarx)
- set props so apps can detect if phone started with multiboot or not(for future versions of multiboot-manager)
- reboot into bootmenu/recovery now works
ATTENTION: reboot into recovery will open recovery for REAL system!!!
- added GUI for choosing which (virtual) system you want to boot
[B]v0.4:[/B]
- replacing all references to real system with stub-image(will be automatically created at /sdcard/fsimage/stub.img).
Now the recovery for the virtual system should be completely abstracted and it shouldn't make any changes to the real system
- a PDS-backup will be created and injected because it's needed by android-system and above change removes the reference
[B]v0.3/v0.3.1:[/B]
- moving original system-partition to another location instead of lazy unmount so she will be accessible in 2ndBoot-system and will not be busy
- fixed recovery to improve installer-zip compatibility. MIUI works now
- internal script-changes
[B]v0.2:[/B]
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
[B]v0.1:[/B]
First release
Source:
https://github.com/M1cha/DefyMultiboot
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=1289953&d=1346244428
Installation:
1. Download zip-file and copy to sdcard
2. create 3 filesystem-images in ext3-format and copy them to /sdcard/multiboot/NAME with the names system.img, data.img and cache.img.
Please replace NAME with the folder-name of your virtual system(you have to create this)
You can download ready-to-use images from here:
http://www.multiupload.com/VY3U4IXRO1
2. install zip-file in CWM
Some info:
- The menu-entry "Lastest Recovery" is no longer supported and will affect your real system!
- boot the System-Chooser with the 2ndBoot-option in bootmenu
Bugs:
- Data-Wipe deletes android_secure
Donate:
Developing Multiboot makes much fun and I really like the results but takes much time, so feel free to donate a beer.
Hey,
i have no "Lastest Recovery" but a "Custom Recovery"
Can i install your script or does it not work with this version of the Bootmenu?
Which rom do you have installed?
I will check if it's compatible.
Thanks for the fast answer
i installed the CM7.2 Nightly "cm72-111125.0850-NIGHTLY-Defy"
The nightlys should always have the newest version of bootmenu.
Where you downloaded the nightly? I only could find "cm72-111123.1710-NIGHTLY-Defy.zip".
But generally it would work if you install but the problem is that you will never be able to change your real system because recovery will only make changes to the virtual one.
That bootmenu has 2 recovery-entrys is a lucky thing which I use as trick so I don't need to modify bootmenu
But when bootmenu-integration is done and you have an old version you will have to update bootmenu.
updated to v0.4
See first post for more info
Gonna try this now. I downloaded your empty .img files but how do I create my own img's on Win7? And what do you think is the smallest size I can make them safely to use with MIUI or ICS?
I don't know how you can create the images on windows, sry.
Maybe I can write a little App which does this directly on Android.
I have to admit that the images I uploaded are a little bit oversized.
system needs max 200MB
cache and data depends on your usage.
I would choose a minimum of 100MB for data and cache. If you plan to install many Apps you should make the data-partition over 300-500MB
Doesn't matter, instructions for Linux would do too
Hmm..oversized but no prob downloading because they were empty, only transferring via USB takes time. 200 MB for system and data and 100 for cache sounds good I'll make them myself if you can give me the instructions, I have Ubuntu.
App to do this on the phone itself sounds good, makes it even faster, no transferring from PC Thanks for your work
The Problem is that I can't find a mkfs.ext3-binary for Android
Maybe I'll extract it from another phone which contains this.
But as of now, here are the instructions:
Code:
dd if=/dev/zero of=./system.img bs=1000000 count=200
mkfs.ext3 ./system.img
The number 200 specifies the size in MegaBytes. I hope this will help you so far
Sure does
But like the poster above said, CM7 latest nightiles contain Custom Recovery, Stable Recovery, and Stock Recovery in the Bootmenu option for recovery. So Custom Recovery = Latest Recovery for your tool? I remember it used to say Latest recovery a few months back, dunno when that changed.
Oh, now I unsterstand what he wants to say.
I thought there is ONLY "custom recovery".
But if there are two recovery's it's ok to install. So you can use "Custom Recovery" for your virtual filesystem.
I'm downloading the CM7-source so I can extend and compile bootmenu and everything will be easier.
But with a download-speed of 170KiB/s this will take a long time
How fast is the virtual system? Could it be laggy because it is loaded from the sd-card?
the time from bootmenu to the boot-process itself takes a little bit time sometimes if I'm debugging.
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
m11kkaa said:
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
Click to expand...
Click to collapse
What class brand capacity card do you use?
I'll be trying with miui and ics tonight
Sent from my MB525 using XDA App
I don't know which class my card is because there is no label. It's completely black
But I don't think I have the best one(maybe class 2 or something else?)
An APP for windows to create ext-3 partitions http://forum.xda-developers.com/showthread.php?t=824154
download link: http://www.multiupload.com/SV7SOY33MQ
I have a 8GB class 4 card. Will test it in a few minutes with CM7 as real system and ICS as virtual system. Do you know what happen if I restore a backup in the real system? As far as I know a backup will override the bootmenu, too. Or am I wrong?
Yes, that will override the bootmenu.
But your virtual system stays on the sdcard.
You just need to patch again bootmenu with the downloaded "defy_multiboot_vX".
I'm on CM7 latest nightly and got boot loop when i tried to install Galnet MIUI ICS on virtual system. Could you fix it?
All MT6573 android phones are plagued by low internal memory issue.
This mod works on all MT6573 Stock ROM with Stock Recovery.
Credits (In Aphabetical Order): banjo0917, casacristo, puppet13th, tazzz811, ungaze & others DEV.
Without them sharing their mods/ tools, this KANG would not be here...
BIG Kudos to them...
{
"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"
}
---------------------------------------
Added on July 07, 2012 - Version 2
Added V2 that take advantage of another unused script on Stock ROM, xlog.sh... If your MT6573 phone already have a copy of install-recovery.sh at etc folder, you can use this V2... i think with V2, you can simply install it to all MT6573 android phone without having worrying if there is a copy of install-recovery.sh at /system/etc :fingers-crossed:
Having said that, it is always safe to check with any Root Explorer & make sure you don't have an existing copy of xlog.sh at /system/etc. If there is, then save a copy to your /sdcard/scriptz folder before using V2... :victory:
---------------------------------------
Confirmed MT6573 Android Phone that works with Data2SD mod
CSL Switch Dual II Mi357
Fly IQ260 Blackbird
Spice Mi-350n
Nexian Cosmo Journey A895
Wellcom A90+
Lenovo A60
Spice Mi-350
Alcatel BLAZE DUO OT-918N
i-mobile i695
Nexian Xtreme A899
B63M i can't find the original manufacturer & it seems like this phone is really clone of the clone... real shanzhai model...
Tenq S820
T9199
---------------------------------------
Detail explanation on what this mod do
It uses install-recovery.sh/ xlog.sh (V2) to start up tweaks/ scripts at your /sdcard/scriptz folder. Inside scriptz folder, there are a few tweaks/ scripts that improve your android phone performance. The beauty of this mod is that it works like init.d but it reside on your SdCard instead of /system/etc/init.d
With normal init.d mod, any wrong tweaks, your phone will not boot or goes into bootloop ! With this SdCard Tweakz, anything wrong, just remove your SdCard & your phone will reboot normally. Then you can use any card reader to remove the scripts that causes the error.
To try any other tweaks, open any init.d tweaks with Notepad ++ or equivalent & save it as XX***.sh -> XX digit, *** -> text. For detail explanation on what you can do with SD Tweakz, you can refer to the original post here...
Again, here are the original developers/ modders in alphabetical order...
banjo0917 - Ported his custom ROM to my Mi357, this has leads me to discover that install-recovery.sh can be use on all MT6573 & ungaze SD Tweakz/ Data2SD
bgcngm - his unpack/ repack script leads me to discover unused script at boot.img
casacristo - First to compile ext2.ko so everyone can use ext2 partition on MT6573 with 2.6.35.7 kernel
DooMLoRD - Use/ modded his Easy Rooting Toolkit [v4.0](zergRush Exploit) for this mod
tazzz811 - First to discover ungaze's Data2SD can be use on MT6573
puppet13th - Use/ modded his tool for this mod earlier
ungaze - Data2SD & SD Tweakz mod
xboxexpert - Use part of his interactive script
others DEV - various scripts at scriptz folder mostly ported from banjo's ROM
---------------------------------------
Added on July 11, 2012 - Final Version via ADB
a2sd-mt6573-ext2-ROOT-zergRush-busybox-su.7z
- AIO which includes rooting, auto-install busybox, su, Superuser.apk & ungaze's Data2SD & SD Tweakz
a2sd-mt6573-ext2.7z
- Install only ungaze's Data2SD & SD Tweakz for already rooted mt6573 Android phone. Make sure you have busybox prior to install this or else it will not work...
---------------------------------------
Added on July 21, 2012 - ext4 Test Version
As mention, because of work commitment, i cannot find time to fully test & release this ext4 version...Credits to Banjo0917 for compiling it...
So i'm hoping someone would take over, test it & release the stable version so that all mt6573 users can benefit from it... :laugh: It is actually a fully working version which can also be install over previous ext2 version. Problem is that it works o.k for awhile then the constant FCs...
Files are extracted from Banjo's earlier patch file, he is most active at his Pinoy forum but not here...
You can download his rom here for reference...
You can find his latest rom here...
Any taker...
---------------------------------------
Added on August 26, 2012 - Cronmod INT2EXT
Just got an update from [SCRIPTS]CronMod-A2SD/D2EXT/INT2EXT (updated 08/24)
thanks to croniccorey & mastermind1024, now you have a few more scripts that you can play with, on ur stock ROM... :victory:
INT2EXT Features
INT2EXT
- Mounts /sd-ext to /data
INT2EXT+
- Mounts /sd-ext to /data & leaves /data/data on internal for speed
INT2EXT4
-Mounts /sd-ext to /data & works with EXT 4 filesystem
INT2EXT4+
-Mounts /sd-ext to /data & leaves /data/data on internal for speed
01int2ext+deodex-mm.sh mod by mastermind1024 for deodex ROM & people facing slow system after using INT2EXT+ script. It moves /dalvik-cache back to internal so that your system response better...
Steps for Installation
1) Download AIO-mt6573-Data2sd-ext4-For Testing.7z, extract it to your desktop; scriptz_cronmod.7z , extract it to /sdcard
2) If you have already use previous mods then it is advisable to format ext2 partition first before installation. Double-click start.bat & when it is about to finish & ask Press any key to reboot . . ., just close it
3) Remove 01data2ext4.sh from /sdcard/scriptz folder
4) Copy only one of the script from /sdcard/scriptz_cronmod to /sdcard/scriptz & reboot
Enjoy & don't forget to thank the original DEV...
---------------------------------------
Added on August 30, 2012 - Amarullz Ad2sdx
i've been trying to get this mod to work on stock ROM for the longest time & now it does !
Special thanks to mastermind1024, i couldn't figure out why it doesn't work at the first place, it always shows invalid IMEI for both SIM...
You can follow Amarullz original post here
Same as Cronmod INT2EXT, only one script should be copied to /sdcard/scriptz folder...
A little explanation about the different scripts
1) Ad2sdx mod by Alex-V - moves everything to sd-ext. According to Alex, if the internal data is full with dalvik cache & you still have plenty of free memory left on sd-ext, you can't install anymore apps...With this mod, you can !
2) Ad2sdx mod by casacristo - modded to mount ext2 instead of ext4 originally. This is the original untouched mod that places the dalvik-cache and system application data to internal memory to maintain performance.
3) Ad2sdx mod by haiduongbk - reverse mount sd-ext & data
Enjoy...
---------------------------------------
Added on Sept 24, 2012 - Dark Tremor Apps2sd Version: 2.7.5.3 Beta 04
This is the last version from Dark Tremor AKA Robert Travis Kirton since Jan 2011....
i've been looking forward to his Darktremor 2.8 but sadly it never got release...
After installation, use A2SDGUI to move dalvik-cache to SD-EXT. Also included is FreeSpace to check Ext partition...
For maximum space saving, at ADB shell use command su then a2sd datasd but i must warn you it might FC later on... He did mention he was never a fan of moving the entire /data/data directory to the SD card...
Credits
Darktremor Apps2sd
A2SDGUI
Oleg Krikun FreeSpace
Enjoy... :laugh:
---------------------------------------
Added on Oct 18, 2012 Updated DT_a2sd V2 & cwmr flashable zip
With close to 300 downloads & nobody report back it doesn't work out of the box...
Attached below is V2 that should work without the need to flash dtapps2sd-2.7.5.3-beta04-signed.zip first...
For those who already got cwmr then you can download DT_a2sd cwmr flashable zip here...
---------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
If I would have seen this post before my phone wouldn't have been bricked
Anyway kudos to poster & developers
there are a lot of beginners would like to know how to install this into their MT6573 phone...
well...
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
eventhough there is a How to Install in the MTZ file..
confusing..
---------- Post added at 04:37 PM ---------- Previous post was at 04:18 PM ----------
Auto Installation using ADB
1. Download & install usb driver from the above link if your phone doesn't comes with it.
2. Copy the extracted ADB folder to c:\ drive.
3. Double click Start.bat & all files will be installed.
4. Follow on-screen for instructions.
@sevensaints
First, on your android phone, enable usb debugging... Setting -> Applications -> Development -> put a check mark on "USB debugging"
Typically, when you plug-in your android phone, windows will detect it & will prompt you to install the driver...if it doesn't then follow the steps below...
Go to Device Manager -> double click on the MT65xx Android Phone -> Update Driver -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Next -> Have Disk -> Browse -> to wherever you have extracted the downloaded google usb driver -> android_winusb.inf -> OK -> Next -> Install -> Close -> Close
Whew, i actually replicate the actual step, by step... There is also another auto-installer, Pdanet, you can check it out...
Then double-click SuperOneClick & it will do its job... :victory: Answer yes when ask whether to install busybox
Actually, rooting & installing google sdk usb driver is scattered everywhere on the web & also here at xda...SuperOneClick
@breaky9973
Thanks, breaky9973...It would be great if you could post the model of your MT6573 then others users will benefit from it too... :victory:
I have an i-mobile i695 and I got it succesfully restored (with one minor issue).
Your script works for me but it took me a couple of restarts to be fully initialized on my phone.
guys, thank you so much for your feedback...
@breaky9973
actually, it works right after reboot, the problem is mediatek's mt6573 is kinda of slow while booting up & yes, what you said is correct, it actually needs around 1 to 2 minutes to fully initialized... :silly:
@sevensaints
when i got my android phone, 1st week got it rooted, 2nd week brick it, 3rd week found russian forum to restore it back... :laugh: i presume most users will root their phone once they got their hands on it... Point taken, i have included DooMLoRD's Easy Rooting Toolkit with it now... :good:
As mention before, would appreciate if you guys that has this mod working on your phone to reply with the model of your mt6573 so that other users would benefit from it too...
Thanks...
Hello yuweng,
Just want to confirm this mod works on Nexian A899 based on MT6573 stockrom. because of I used Link2SD before, seem like get problem to increased the internal storage and after factory reset, it works! get it free of 1.3 GB
btw, the start.bat not works under Win7..only works under WinXP.
Thanks! :good:
Thank you so much for your feedback, para_dox77... :laugh:
Actually, best size for sd-ext is 1GB. i've install 200 over games to test & found out that after 1.2 GB of data fill up, after reboot, the launcher screen is not responding, all apps are missing & i have to wait around 3 to 4 minutes then everything show up ! After that, everything is quite responsive. So i guess thats the max. Same as our PC... On top of that, you'll save 500MB of space if you format your sd-ext 1GB instead of 1.5GB...
Both ported scripts are develop & tested on Win7 OS, so my best guest is that you didn't turn off the user account control settings...it'll block whatsoever bat/ exe/ setup file that is trying to run...
Another lesson learn, so guys please delete whatsoever link2sd, a2sd, d2sd & etc that you have or else this mod will not work... :fingers-crossed:
By the way, this mod should be call data2sd or d2sd...You can refer to this post by croniccorey. You can also try his scripts & see if it works on our mt6573...been super busy with work lately so no time for modding...
Hey, this is great! but I am having a little issue. I have a "NEOBOX NEO" phone, and since I was stuck with the stock recovery I could add init.d support but no ext2 support so I was using link2sd with a fat32 partition, but I still had problems with storage. I uninstalled links2sd and formatted the partition to ext2, ran the .bat and it worked, now I have plenty of space and no more annoying low space messages. The thing is, whenever my phone sleeps, when I turn the screen on, it hangs for a while, and then it prompts like 3 to 5 times like it has a new sim card. My guess is that it moved the sim app to the sd and when it sleeps it is not actually reading from the card hence the problem. I haven't done any further testing but I am guessing this would also cause trouble with other apps that need to be running in the background like messaging and whatsapp and basically anything that syncs. And if I am right and that is the problem, then the solution would involve having the phone not to sleep and thus drain the battery very fast. Correct me if I am wrong (and I certainly hope I am because otherwise this seems great and the solution to my problem)
EDIT: it does the "sim thing" not only when sleeping but anytime. specially anoying when listening to music. Anyone with the same/similar issue? the card is a 16gb verbatim HC card class 10. never had a problem with it b4.
Hi jinxie,
I've read alot on generic a2sd mod, data2sd & etc; many users has been reporting problem with class 10...
My suggestion to you is that you remove all scripts except 01data2ext.sh & monitor from there onward...
This is the best part of ungaze's SD Tweakz, just add or remove any old/ new tweak scripts from your SdCard scriptz folder & you phone will be back to normal or even better/ faster with the correct modded scripts... :good:
The other thing is that i change the read_ahead_kb from the original 03tweakz.sh; from 1024 to 8192... You can refer to here for more info... May be it is too high for class 10... Use Notepad ++ & change it to a lower value...
yuweng said:
Hi jinxie,
I've read alot on generic a2sd mod, data2sd & etc; many users has been reporting problem with class 10...
My suggestion to you is that you remove all scripts except 01data2ext.sh & monitor from there onward...
This is the best part of ungaze's SD Tweakz, just add or remove any old/ new tweak scripts from your SdCard scriptz folder & you phone will be back to normal or even better/ faster with the correct modded scripts... :good:
The other thing is that i change the read_ahead_kb from the original 03tweakz.sh; from 1024 to 8192... You can refer to here for more info... May be it is too high for class 10... Use Notepad ++ & change it to a lower value...
Click to expand...
Click to collapse
Thanks for the quick reply! I will try that!
So, update: After trying it yesterday all day, very unstable, rebooted like a ziliion times, and then it looked like finally everything was in place and it started to work fine, so I installed a bunch of apps. Like 5 or 6, usual stuff, facebook, twitter, etc., rebooted, and now it bootloops. removed the card and boots fine of course, but no freaking space. What now? heh
UPDATE:
I decided to do a clean install, and since there is no custom recovery for my device I cant flash zips, I erased all data and flashed the system.img partition again. I also formated both fat32 and ext2 partitions from the sd card. Then I applied your script (prior to that y reduced the read ahead kb you mentioned by half). No luck, same issues. So i deleted all scripts but the data2ext. It runs better, but I still get FCs, it hangs for a few secs, then I lose all connectivity with the "restricted access changed" message, and the new sim detected pops up constantly, so I also get a lot of dropped calls. I also noticed battery drainage, much faster than before, I think it is because of the same connectivity issue since looking for networks does drain a lot of battery.
Apparently, it has to do with data connection, since I have deactivated it and for the past hour I haven't had those problems, but I can't tell for sure, I'll test wifi when I get home.
Thanks so much for the update, jinxie...
AFAICR, some mt6573 has different mtd for system.img...
at adb shell, cat /proc/mtd & see if it is mtd11...
if it is different then i think you have to edit 01data2ext.sh, line 22, 33, 130, 138 to your system.img mtd location...
hope it works out for u... :fingers-crossed:
Added on August 03, 2012 - Earlier original ungaze [mod][mt6573] Data2sd on stock rom Test Version
Attach script is the original script format from ungaze's Data2SD... :fingers-crossed:
Steps
Option 1 - Replace file at SdCard
1) Delete 01data2ext.sh from SdCard scriptz folder
2) Format SdCard ext2 partition
3) Restart & let it settle down
4) Copy this file to your SdCard scriptz folder & restart
Option 2 - Reinstall this mod all over again
1) Format SdCard ext2 partition, factory reset, wipe data
2) Restart & let it settle down
3) Copy this file to & delete 01data2ext.sh -> files -> scriptz folder & run start.bat
I had a record of my tables but I cant find it, but if the mtd was different shouldn't it not work at all? because it does work, I have the internal memory the size of the partition, but it is unstable and slow.
I installed terminal but it FCs so I am installing ADB because I formatted my pc recently so I will tell you in a few minutes.
Btw it seems the SIM card problem only happens when the data connection is active, maybe it has to do with the network changes from E to 3G and H. I haven't been able to disable fast dormancy. The battery consumption showed almost 50% in Cell standby. But it still hangs, FCs and that kind of weir stuff that makes it really hard to use and a challenge to my patience. Thank you for all your help. Is there any other alternative you would recommend for the low storage issue for us the poor ones with stock recovery? Link2sd worked for a while but then memory got full anyways, dont know why because I had almost every app on the SD. I wish I could use a2sdx...
EDIT: yup system is mtd11 :S
my mt6573 will be monster after this
thanks
perfect on b63m..i try casacristo ext2 script..
@loris22
Thank you so much for your feedback, another phone added to the list... :laugh:
@y2yu
Wow, you post reply here & on my other thread, hope you find my KANG useful... :fingers-crossed:
hi
without a custom recovery there are some way to make a2sd work?
Yes, in fact you can ! But it will be quite tedious as you need to manually copy a2sd's files to its appropriate folders, manually set permissions & etc for it to work.... And you will also need bgcngm's MTK-Tools to unpack boot.img...You can refer to here for more info...
Why don't you use my universal cwmr Android Kitchen plugins for porting cwmr to ur MT6573 ?
I've created this thread specially for MT6573 users that are happy with their stock ROM but needed larger internal memory...
Originally, most of these data2sd scripts require some kind of modding to the boot.img or system.img while the one here doesn't require any of that...
Kudos to the original DEVs for these excellent scripts....
yuweng said:
Yes, in fact you can ! But it will be quite tedious as you need to manually copy a2sd's files to its appropriate folders, manually set permissions & etc for it to work.... And you will also need bgcngm's MTK-Tools to unpack boot.img...You can refer to here for more info...
Why don't you use my universal cwmr Android Kitchen plugins for porting cwmr to ur MT6573 ?
I've created this thread specially for MT6573 users that are happy with their stock ROM but needed larger internal memory...
Originally, most of these data2sd scripts require some kind of modding to the boot.img or system.img while the one here doesn't require any of that...
Kudos to the original DEVs for these excellent scripts....
Click to expand...
Click to collapse
THANKS!!
this night i study everything i try to make a working cwmr for alcatel 991!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HYPERION 7
The fastest and smoothest ROM for Samsung Galaxy Young GT-S5360 yet
With its easy-to-use interface, amazing features, and rock-solid stability, Hyperion leaves others behind.
And even as others try to catch up, the features built into Hyperion keeps your device years ahead.
Before you download, please read THIS
Elegant and intuitive interface.
The simple, beautiful Home screen is the easiest place to start.
From the home screen to every built-in apps in the system, navigation is fast, fluid and effortless.
Everything you touch is easy, intuitive, and fun.
Amazing features and built-in apps.
An ever-expanding collection of features and built-in apps make Hyperion even more powerful, innovative, and fun to use.
Here are just a few.
Would you like to donate?
Save your money for more important matter!
I accept "Thanks" donation!
Fast, simple and easy
If you love Hyperion and wants to support the project
Rate the thread 5 stars
Features and screenshots
NOTE:
... and we are back! If you read on 1st post, you probably not reading this. If you don't get me, click HERE
HYPERION 7 HIGHLIGHTS
PERFORMANCE TUNING
Full GPU (Graphic Processing Unit) rendering for faster, smoother and more responsive system performance
Disabled Journalism (File caching) for faster file read/write
Advanced radio controls for maximum battery saving
ADDITIONAL PERFORMANCE TUNING
IPv4 and TCP Stacks tweak
Secure WiFi Profiling
ISP Restriction tweaks
VPN Support
NOTE:
All above performance tuning are certified real by Hyperion Private Testers and not just written there just to say we updated something.
PERFORMANCE TUNING HIGHLIGHTS
Hyperion Core now fused with Adrenaline Engine for blazing fast performance - Tweak developed by ImbaWind- LINK
NetForks tweak for turbo charged internet browsing experience - Tweak developed by DroidFolks- LINK
FEATURES
UNIQUE FEATURES
No SMS Bug
No false Android version
No copy-pasted app from other ROMS
No paid apps edited to look like a new tweak or mod
No useless features
BASIC FEATURES
De-Odexed
Zipaligned
Recompressed APKS
Optimized APK Images
Rooted
BusyBox and BusyBox run-parts support
Apps2SD enabled
ADVANCED FEATURES
EXT4 File System Support
CIFS
Swap Support
BaCeM Tweak
UnderVolt Support
Firewall Support (DroidWall Open-Source Project)
ENHANCEMENTS
Mobile BRAVIA® Engine
xLOUD™ Sound Enhancement Technology
SRS Wow™ HD Sound Enhancement
Beats™ Audio Enhancement
OTHER ENHANCEMENTS WORTH MENTIONING
Modified PlayStore app
No market restrictions
No auto-update
No useless features
Mother of all HOSTS - more than 27,000 servers blocked
Blocks ADs
Blocks banners
Blocks 3rd party cookies
Blocks 3rd party page counters
Blocks web bugs
Blocks hi-jackers
Blocks phising sites
Blocks Malwares
Blocks Spywares
Blocks Trackers
Blocks un-authorized application connection
WHAT MAKES HYPERION UNIQUE
Savie's special kernel for Hyperion (Savie for Hyperion Project)
UNIQUE FEATURE
No false frequency reading
BASIC AND ADVANCED FEATURES
System-App replacer - I love you savie for this!
All-In-One modules
22 Powerful Governors
5 I/O Schedulers
Supports EXT 2/3/4 File System
Supports UnderVolting and UnderClocking
Supports CIFS (Remote Server-Client file access via Internet)
Hyperion Home - Xperia S Launcher originally modified for Gingerbread by ra3al - LINK
UNIQUE FEATURE
Not a paid app - We know how to code so we don't rely on paid apps.
BASIC AND SUPER LAME FEATURES :laugh:
Desktop layouts: Dock only, 4 Corners, Dock + 2 Corners and Dock + 4 Corners
Iconpack Support: Launcher Pro (Plus) icon packs, ADW Launcher icon packs and Go launcher icon packs
Custom desktop and App drawer row and column grid sized
Desktop folder support
App drawer sort methods: Own icon sort, Alphabetical, Most used and Recently Installed
Settings backup and restore function
Network Unlocker - Modified Galaxy Toolbox v1.0 by Doky73 - LINK
Modified for Hyperion
Remove carrier lock (Unlock)
Restore carrier lock (Re-lock)
Remove bin count (kernel flash count via odin)
NOTE:
The purpose of editing is to keep the sdcard structure tidy and to make sure there is no oddity in Core > Tools for menu items. Launcher and bml15 backups are stored in Hyperion folder in sdcard.
Installation and downloads
DOWNLOAD
Hyperion 7 Golden Master Final
Filename: HYPERION.7-GM.FINAL.zip
Size: 119.31 MB (125109981 bytes)
Uploaded By: CarlDeanCatabay
Uploaded On: 2012-11-13 12:29:45
MD5 Sum: c8a0b092b53165db700943ba72b885d3
File Desc: Hyperion 7 Golden Master Final Public Build
Virus Status: OK (Clean)
To all Hyperion users,
I got a message from our moderator regarding reports that Hyperion 7's zip package contains root explorer which is a paid app. During testing I added RootExplorer to make debugging init.d scripts easier. Due to excitement and demand for the new build, I forgot to remove RootExplorer and accidentally uploaded a zip package that contains this paid app. Starting today, link to Hyperion will be disabled until a new build is ready. Sorry for the inconvenience and my apologies to Speed Software Developers.
Thanks and Regards,
Carl
INSTALLATIONFlash Hyperion using STOCK RECOVERY
Go to recovery by pressing the HOME button + VOLUME UP key and the POWER BUTTON
Select WIPE DATA/FACTORY RESET
Select WIPE DATA/FACTORY RESET
Select APPLY UPDATE FROM SDCARD
After installing, reboot your phone
Flash Hyperion using CWM (ClockWorkMod) RECOVERY (UPDATED: 10/24/2012 11:13 AM Arabian Standard Time)
Go to recovery by pressing the HOME button + VOLUME UP key and the POWER BUTTON
Select MOUNTS AND STORAGE
Mount /system
Mount /data
Mount /sdcard
Select WIPE DALVIK-CACHE from Advance and Debugging
Select WIPE BATTERY STATS from Advance and Debugging
Select WIPE DATA/FACTORY RESET
Select WIPE CACHE PARTITION
Select INSTALL ZIP FROM SD CARD
Select SELECT ZIP FROM SD CARD
After installing, press the power button to go back and select REBOOT SYSTEM NOW
NOTES
First boot may take from 1-2 minutes or longer
The first screen you will see is the setup wizard.
The blue circle on the right corner of the status bar indicates that the system is busy (performing media scan, staring services etc etc).
In some cases (if flashed via CWM), the status bar might remain in "busy mode" until you restart your device.
HOW DO YOU KNOW YOU'RE STUCK IN BOOT LOGO? -IF IT STAYS THERE FOR MORE THAN 10 MINUTES. IF THAT'S THE CASE, TRY RE-FLASHING THE ROM OR FLASH STOCK ROM FIRST VIA ODIN BEFORE HYPERION :highfive:
Installation Troubleshooting Guide
INSTALLATION TROUBLESHOOTING GUIDE
In the past days, as we have observed, there had been installation issues for new and existing users. We know how annoying it is to get a bootloop, installation aborted and many installation related problem, so here you go, I will put every single scenario that had been reported and the best solution to install the best (according to users) rom when it comes to performance and style :victory:
Whenever I flash a new build, I have this "one-shot-install" method I am keeping. This one works whether you are jumping from one kernel to another. The one-shot-install step is:
Flash stock via Odin (Recommended)
Format SD Card to remove any unwanted files, orphaned data from previous ROM and of course, junk files.
Copy Hyperion zip package to sd card
Reboot to CWM using TempCWM if you are on stock ROM, or the built in CWM from savie's kernel if you are a previous Hyperion user and skipped flashing stock via Odin
Go to Mounts and Storage and mount /system, /data, /cache and sdcard
After mounting, Go back to main menu using the power button
Navigate to Advance (Advanced and Debugging)
Select Wipe dalvik-cache -this helps you avoid bootloops
Select Wipe batterystats -this ensures your battery gauge gets re-calibrated on first boot
After doing wiping dalvik and battstats, Go back to main menu using the power button
Select Wipe data/reset
Select Wipe cache
After doing data and cache wipe, select install update from sdcard
Select zip from sd card
Select Hyperion zip pacakage and install
Wait for the system to complete installation, it will take 2-5 minutes (maximum) to complete installation
Reboot your device
BELOW ARE THE REPORTED SCENARIOS AND POSSIBLE CAUSES WHY INSTALLATION FAILS COMMON FAILED INSTALLATION SCENARIO(S)
SCENARIO 1:
"I flashed Hyperion after flashing stock rom via Odin but every time I use Temp CWM and try to flash Hyperion, it goes back to stock recovery. No error is shown on recovery"
CAUSE OF ISSUE:
Incomplete download.
HOW TO AVOID:
Use a MD5 Sum checker. You can ask our dear friend Google for any md5 sum checker, it's free and it is usually less than 1 MB to download. Always make sure your zip package is intact and complete.
QUICK GUIDE TO CHECKING MD5 SUM:
Open your MD5 checker
Select the Hyperion package you downloaded
Paste the MD5 sum value from the download page in DevHost (MD5 Sum: c8a0b092b53165db700943ba72b885d3)
If it matches, then that means the zip package you have is intact and completeSCENARIO 2:
"I can't flash Hyperion via stock or CWM, it shows installation aborted"
CAUSE OF ISSUE:
Bad or damaged zip package
HOW TO AVOID:
Check the md5 sum and make sure your zip package is not damaged. If it is damaged, md5 checker will show you MD5 Hash Sum mismatch.SCENARIO 3:
I flashed Hyperion but nothing happened, I still have stock rom or previous custom rom
CAUSE OF ISSUE:
/system, /data, /cache partitions were not mounted in CWM prior to installation
HOW TO AVOID:
Super duper hyper mega easy; Go to Mounts and Storage and make sure they are all mountedBOOT LOOP SCENARIO(S)
SCENARIO 1:
"I am using a custom rom and I flashed Hyperion on top of it without flashing stock via Odin. After flashing, my device goes to endless boot loop. My previous custom rom includes a custom kernel"
CAUSE OF ISSUE:
Custom kernel (boot.img) from previous ROM
HOW TO AVOID:
The safest way to install a custom rom (in this scenario, Hyperion) on a device running a different custom rom with custom kernel is to revert back to stock rom first because jumpring from one kernel to another will surely cause boot loops. That is why we always recommend flashing stock rom first before flashing Hyperion.STUCK AT BOOT LOGO SCENARIO(S)
SCENARIO 1:
"I am using a custom rom with repencis kernel or merruk kernel prior to flashing Hyperion. After flashing Hyperion, I am stuck on boot logo (the samsung galaxy y blah blah screen)."
+
Same scenario above but; "I flashed stock rom via odin, but every time I do wipe data/factory reset and wipe cache, it shows me error mounting rfs blah blah"
CAUSE OF ISSUE:
Both repencis and merruk are known to convert your device's File System (FS) to EXT4. If your device's file system is EXT4 and not RFS (Robust File System), flashing Hyperion will fail, but boot.img (kernel) will be flashed.
SYMPTOMS OF EMMC FORMATTED TO EXT4:
CWM cannot mount /system but all partitions can be mounted
Stock recovery cannot do data and cache wipe
HOW TO AVOID/FIX:
Given your phone is already formatted to EXT4, there is nothing you can do but to repartition your device's EMMC (the chip where we install the device's OS) using Odin.
But remember I have written "but boot.img (kernel) will be flashed"? This will help you in solving this kind of issue.
Please keep in mind that this issue is not a problem with Hyperion rom, if CWM and Stock recovery cannot mount your /system partition, no custom rom can be successfully installed on your device.
Now this is the work around . . .
Since boot.img will always be flashed, that means if the kernel on the rom you are installing have CWM installed, then you will have CWM as recovery.
Now that's a good news because your default recovery now is CWM, and you can use it to format partitions back to its default file system. Follow the steps below:
Remove the battery of your device
Press the recovery key combination to boot into recovery
If you are lucky, you will be able to reboot to CWM (given you flashed Hyperion)
Once you are in recovery, Go to mounts and storage and format /system, /data and /cache
Once format is successful, reboot recovery using the "Reboot recovery" option
After rebooting recovery, mount the partitions and try flashing Hyperion again.
Wireless and Networking Troubleshooting Guide
WIRELESS AND NETWORK TROUBLESHOOTING GUIDEWIFI ISSUE(S)
WIFI ISSUE 1:
WiFi gets disconnected once phone is locked or the display turns off
CAUSE OF ISSUE:
Okay, don't panic. This is not a bug. This behavior is the one responsible why you save battery even if you don't turn off your WiFi radio and this is called WiFi Sleep Policy.
HOW TO AVOID:
Currently Hyperion have 3 WiFi policies available in Settings Tab > Wireless and Network > WiFi Settings > Advanced > WiFi sleep policy.
WiFi Sleep Policies:
When screen turns off - if selected, wifi will turn off automatically when the screen turns off (obviously)
Never when plugged in - if selected, wifi will not turn off automatically when connected via AC or USB port and is getting power from either AC or USB.
Never - if selected, wifi will never turn off automatically - default setting in stock roms
WIFI ISSUE 2:
WiFI cannot connect to any wireless hot spot and/or wireless networks
CAUSE OF ISSUE:
Still UNKNOWN. The dev team are thinking that only production specific GT-S5360 devices are affected with this issue.
Based on user feedback, we are in conclusion that the following might be causing the problem:
Savie's special built kernel for Hyperion
Netforks Tweak
Mother of Host
HOW TO AVOID:
Currently, we have the following fix but not all or even none of the below suggestion may fix the problem depending on your SGY.
A simple reboot will fix the WiFi connection problem
Flashing your device's radio image (baseband) via Odin will fix the problem
Removing NetForks tweak will fix the problem
Removing Mother of Host may fix the problem
QUICK GUIDE TO FLASHING BASEBAND
Open Odin and locate the firmware files for your device
Connect your device to computer using USB Data Cable (USB Cable)
On the PHONE field, locate the MODEM file for your device
Click start to start flashing BASEBAND
NOTE:
You will only flash the PHONE file
QUICK GUIDE TO REMOVING NETFORKS TWEAK
Using root explorer, navigate to system/etc/init.d
Delete 04netforks_tweak
Using root explorer, navigate to data/
Delete droidfolks folder
Reboot your device
INTERNET ISSUE(S)INTERNET ISSUE 1:
Cannot open websites and or cannot surf the web
CAUSE OF ISSUE:
Mother of all Hosts
For some reason, most of the website that can't load on any browser are website like mediafire, 4shared and other file hosting sites which what they have in common are ADs, Popups, Counters and Surveys. Since MOH is blocking these type of web activities, some webpages may not load. Specially those sites that are configured not to load when their advertisements are disabled by either the browser or internet connection.
HOW TO AVOID: Thanks to Dr.oidbio for pointing this out
OPTION 1
Using root explorer, navigate to system/etc
Replace hosts file with any hosts file from stock or other custom roms
Reboot your device
OPTION 2:
Using root explorer, navigate to system/etc
Open hosts file with text editor and edit the content
Delete everything except
Code:
[LEFT]#
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
::1 localhost
127.0.0.1 local[/LEFT]
Reboot your deviceCONFIRMED WORKING FIXREPORTED BY: AlvaroOrduna
Therefore, I set to work and I solved the Wifi issue (obviously with your helpful guides). So that I wanted to share with you the procedure to solve the problem. Here are the steps I took:1. Delete 04netforks_tweak from system/etc/init.d
2. Delete droidfolks folder from data/
3. Edit the hosts file in system/etc deleting all except:#
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
::1 localhost
127.0.0.1 local4. Reflash baseband via Odin
It should be mentioned that I do these steps on flashing zip. I mean, I edit the ROM in the computer and then I install it following the steps in INSTALLATION TROUBLESHOOTING GUIDE. Everything else works fine, but in the future I will continue to watch to see how the phone behaves. If something goes wrong and you do not mind, I will report it.
Attribution-NonCommercial-NoDerivs 3.0 Unported (CC BY-NC-ND 3.0)
Disclaimer
The Commons Deed is not a license. It is simply a handy reference for understanding the Legal Code (the full license) — it is a human-readable expression of some of its key terms. Think of it as the user-friendly interface to the Legal Code beneath. This Deed itself has no legal value, and its contents do not appear in the actual license.
Creative Commons is not a law firm and does not provide legal services. Distributing of, displaying of, or linking to this Commons Deed does not create an attorney-client relationship.
This is a human-readable summary of the Legal Code (the full license). Disclaimer
You are free:
to Share — to copy, distribute and transmit the work
Under the following conditions:
Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
Noncommercial — You may not use this work for commercial purposes.
No Derivative Works — You may not alter, transform, or build upon this work.
With the understanding that:
Waiver — Any of the above conditions can be waived if you get permission from the copyright holder.
Public Domain — Where the work or any of its elements is in the public domain under applicable law, that status is in no way affected by the license.
Other Rights — In no way are any of the following rights affected by the license:
Your fair dealing or fair use rights, or other applicable copyright exceptions and limitations;
The author's moral rights;
Rights other persons may have either in the work itself or in how the work is used, such as publicity or privacy rights.
Notice — For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page.
Developer Conditions:
Any ported version of this rom for any device must be released under the name "Hyperion" or any name as long as "Hyperion" is present.
Ported version must have the same logo in Settings > System.
A link to this thread is required.
Hyperion Project in HTC Mania
Preview - Work In Progress
"Do you even know how to theme apk?"
Hyperion 7.x with Hyperion Home 2.x
The Dev Team
The Hyperion Project 2012Devs I thank the most on this project:
b16h22 - Father of EVO-X; the grand daddy of Hyperion
savie - the guy behind Hyperion's Core Power - Savie For Hyperion (SFH) KernelOther Devs and their contributions:
ra3al for his amazing work on XPERIA S Home Launcher with Settings | 0.9.2c
DroidFolks for Netforks Tweaks for all Android 2.3.6 - 4.1.2 devices
Hyperion 7.x Pre GM
NOTHING NEW, JUST THIS:
More smoother UI - Project Butter Hyperion style | Speed and stability will always be a priority and not eye candy :angel:
Tamed Mother of all Host - not sure though if it's Grandma Host on this package, but who cares? Host file is less agressive now and this will solve problems with sites (specially file sharing sites) not loading.
UPDATED
Graphics driver for smoother gaming experience.
Some libs and *I think some modules as well.
ADDED
Sound Theme - Linda Sounds Mod (the most complete set).
FIXED
WiFi Issues - caused by Multi-CSC mod that affects WiFi banding depending on the market where your device was officially released. In future I might include CSC + WiFi CSC editing so you can take control of WiFi banding (device <-> router connectivity).
Tick/Untick bug in some checkbox item(s) in settings - might also be region related problem.
Most black text over dark background (some are still present because they don't depend on framework/SystemUI)
BACK FROM THE DEAD
I know you missed the good old TouchWhiz Launcher, so here it is, old guy new look
WHAT'S IN IT:
Holo style dock, home and app drawer buttons
9-12 home screens
5-icon dock support
Grid and List view in App drawer
Support AppShare in app drawer
Random icon background support (currently list view only)
Opacity tweaked to match the overall transparency of UI
DEFAULT CONFIG:
3 Home screens
1 Widget: Google search + voice
4 shortcuts on default home screen
5 icons in dock
App drawer icons arranged alphabetically
App drawer in grid view
DOWNLOAD
Filename: HYPERION-7.x.zip
Size:114.63 MB (120203331 bytes)
Uploaded By:CarlDeanCatabay
Uploaded On:2012-11-30 02:34:16 MD5
Sum:5f37a325cffc4c5f409eaba2e5825d76
File Desc:Hyperion 7.x Pre GM Build
Virus Status:OK (Clean)
Note: Use virus status as a reference, rescan with your own Anti-Virus.
TRANSLATING HYPERIONTOOLS YOU NEED:
Any apk tool for decompiling and recompiling like APK Tools, APK Manager and APK Changer Alpha 11 - APK Manager and APK Changer Alpha 11 are the one I'm using. Take note, it's alpha 11, not the latest version of APK Changer.
Notepad++ - a GNU editor you can download from HERE
WHERE TO GET THEM:
APK Multitool - http://apkmultitool.com
APK Changer - http://forum.xda-developers.com/showthread.php?t=1189971
APK Tools - I don't know where to get it. Ask dear Google.HOW TO SETUP YOUR TOOLS:
I advice you use APK Changer as it has an automated setup where you can configure this tool as you install it.
Follow the installation/setup steps for the tool of you choice
After that look for C:\Users\<User>\apktool\framework folder. Ex: C:\Users\Carl\apktool\framework
Take framework-res.apk and rename it to 1.apk
Take twframework-res.apk and rename it to 2.apk
Copy 1.apk and 2.apk to C:\Users\<User>\apktool\framework
HOW TO TRANSLATEPREPARE APKS
In this example, we will modify Settings.apk and translate it to Spanish language.
Take Settings.apk from stock ROM that supports Spanish and rename it to Settings-ES. If your language is not Spanish, then of course you need to take Settings.apk from stock rom for you region which support your language.
Take Settings.apk from Hyperion. You don't need to rename it. Leave it as it is.
DECOMPILE APKS
Once you have all the needed APKS for modding, place it inside the folder designated by the tool you're using for decompiling. In this example I am using APK Changer, so I will put Settings.apk and Settings-ES.apk to C:\Apk-Changer_alpha11\place-files-here-for-modding folder
Open your tool, in this case it is APK Changer. If you installed this already prior to preparing APKS, then you should have the main menu where you have the option to decompile/compile.
Decompile both Settings-ES.apk and Settings.apk
TRANSLATE/ADD ADDITIONAL LANGUAGE TO APK
After decompiling apk, look for the "values" folder inside the decompiled APK. In this case I use APK Changer so I will navigate to C:\Apk-Changer_alpha11\out\Settings\res
You should to the same for Settings-ES and open it in another folder so you can view both folders side-by-side
You can simply take "values-es" folder from Settings.apk and copy it to Settings\res
After copying folder, open Settings\res\strings and add the values present in Settings.apk's res\values\strings.xml to "values-es" folder.
After that, compile your APK and now you have a translated version of APK.
Do this for every app you want to be translated.
OF COURSE MOST OF US ARE LAZY AND ONLY KIND ENOUGH TO TRANSLATE, SO I'LL POST HERE THE FILES YOU NEED TO EDIT AND TRANSLATE AND IF I HAVE TIME AND I AM NOT FEELING LIKE A LAZY MONKEY, I WILL BE THE ONE TO COMPILE THE APK FOR YOU.NOTE:
Only strings.xml and arrays.xml values needs translation. You only need to translate values inside
Code:
<string name="[COLOR=Red][B]alert_mesage_recipients[/B][/COLOR]">[COLOR=SeaGreen][B]Alert message recipients[/B][/COLOR]</string>
<string name="[COLOR=Red][B]text_you_should_not_translate[/B][/COLOR]">[COLOR=SeaGreen][B]Text you should translate[/B][/COLOR]</string>
Example:
<string name="alert_mesage_recipients">Alert message recipients</string>
You will translate "Alert message recipients"
You should NOT translate "alert_mesage_recipients"
Translated example:
<string name="alert_mesage_recipients">Alerta destinatarios del mensaje</string>GET FILES HERE
SETTINGS.APK
CarlDeanCatabay said:
Yes. To check that, navigate to:
/sd-ext/ using root explorer, you will see there:
app
app-private
dalvik-cache
lost+found
To check if deep sleep is working, navigate to:
Settings > Core > CPU States
NOTE:
Deep Sleep starts when phone is idle, if your phone is running for 2-4 minutes from boot, in some cases you will not see deep sleep state in cpu states info. That is normal.
Click to expand...
Click to collapse
i dont know anything abt a2sd plz can u tell me after making the partition what should i do so all the apps and dalvik cache is installed in the partition thanks quick reply will be appreciated
btw i am loving this rom
and is there any way the to change the status bar toggles order
CarlDeanCatabay said:
Yes. To check that, navigate to:
/sd-ext/ using root explorer, you will see there:
app
app-private
dalvik-cache
lost+found
To check if deep sleep is working, navigate to:
Settings > Core > CPU States
NOTE:
Deep Sleep starts when phone is idle, if your phone is running for 2-4 minutes from boot, in some cases you will not see deep sleep state in cpu states info. That is normal.
Click to expand...
Click to collapse
alright.thanks
@CarlDean : No Statusbar tweaks and Widget button, so how do we edit stat bar and add or remove some toggles on 14 toggles?
Solehria said:
i dont know anything abt a2sd plz can u tell me after making the partition what should i do so all the apps and dalvik cache is installed in the partition thanks quick reply will be appreciated
btw i am loving this rom
and is there any way the to change the status bar toggles order
Click to expand...
Click to collapse
Ooops! Seems like I forgot to put QuickToggle in Settings > Parts. I'll create a patch and will attach it here later. Sorry about that, I was too excited to release the ROM
CarlDeanCatabay said:
Based on yowskee's test, RAM usage is about 130-140 MB and he can play Zenonia 4 at 170MB used at most. But i need others to test that.
Click to expand...
Click to collapse
You made my day downloading & flashing
CarlDeanCatabay said:
Ooops! Seems like I forgot to put QuickToggle in Settings > Parts. I'll create a patch and will attach it here later. Sorry about that, I was too excited to release the ROM
Click to expand...
Click to collapse
plz can u tell what i have to do about a2sd after making a partition
if possible add stat bar tweaks...i dont want to see AM and PM on clock
plz people help me what should i do after making the partition
Please, have present the Kernel Savie #73 not run in all model S5360. In variant S5360X not worked.
Solehria said:
plz people help me what should i do after making the partition
Click to expand...
Click to collapse
Please follow the instructions in my Link2SD for dummies on how to partition your SD Card.
Custom rom for Micromax A57 ..NINJA3
***Updated version***
(BASED ON Stock rom 2.3.5)
FEATURES
Added data/app functionality
added xloud and beats audio
new settings mod
Fast remount and mount
fully moded UI
Transparent settings widget
Link2sd and titanium backup were added
New bootanimation and shutdown animation
icecream sandwhich ringtones
walkman as default music player
Rooted with latest su
Busy box added
zipaligned
freed up internal memory
optimized RAM for better performance
Modded settings
new bootanimation added
Increased battery performance
Increased touch responses
Increased camera recording quality
Improved 3G handling performances
Improved proximity sensor
Improved net speed
init.d support
and lots of tweaks
{
"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"
}
DOWNLOAD:cyclops::cyclops::cyclops::cyclops::
Dont forgot to download this update fix...
Update fix
How To Flash This RoM
Use Cwm Recovery to flash This Rom
If you already have Cwm installed then Go on with below steps to install the Rom
0.
Recreate or format Ext2/3/4 partitions if any
1.
Download the Rom Zip
2.
Place the zip In Sdcard
3.
Go to Cwm Recovery
4.
Wipe Data & Cache
5.
Wipe Cache
6.
Select Mounts and Storage>format system>yes
7.
Select Advance>wipe dalvik cache>yes>
8.
Then Flash Rom
9.
After flashing again do wipe data/factory reset..thats it
10.
now again select install zip from sdcard..
11.
And flash the update fix
12.
Reboot the phone
13.
Now enjoy with the new rom
Credit:-
1. Sahil Deep,
2.Violet Edges
2. [URL="https://www.facebook.com/Dhinesh77"]Dhinesh Kumar[/URL] ...:victory::victory::victory::victory:
help
how to flash cwm
navinkumar1892 said:
how to flash cwm
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36056920
any easy way to to flash cwm.. because i dont have any sdk tools
__JOhnny said:
any easy way to to flash cwm.. because i dont have any sdk tools
Click to expand...
Click to collapse
FAstboot method...
and the recovery is here
http://forum.xda-developers.com/showthread.php?p=36056920
Deep inside DD-GB v2 (Custom ROM for Micromax A57 by dinesh77)
Deep inside DD-GB v2
================
There were few friends like Priyank Thakur, 'Deadman Akshay' & Monty Kumar faced..(Serious) Screen OFF (Deep Sleep) issue with DD-GB v2
--I confirm that the raised issue is the Valid problem.... I too faced the same
and has to be verified. In addition I have almost researched on this ROM I have interesting outcomes..please go steady..its really serious for Ninja 3 Development in future.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Success of this ROM:
I congratulate the Develope Dhinesh Kumar (dhinesh77) on successful edition of DD-GB v2
-- Yes this is definitely a Successful Custom GB ROM for Micromax A57 and was got praised by almost all at including me
-- All basic functions working perfect and no issues at all
-- All though no much build prop tweaks added but enough to get us speed and added functionality as there are required init.d tweaks
-- xloud and beats audio: sound enhancements also works up to some extent but personally I want so much insist on that
-- This ROM has got additional framework files from Sony framework to support audio enhancement.
-- You can have good gaming experience on this ROM without adding any additional Tool for the same
-- And several additional Features. For details visit: http://forum.xda-developers.com/showthread.php?p=37207089
-- My overall Experience with this ROM is quite better compared to other custom ROM published till now.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- I saw apps2sd working OK with this ROM
-- apps2sd transfers all apps automatically to apps2sd partition
-- even Titanium backup apps restores in apps2sd partition and TB shows capacity of this partition when it starts
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
However folling are findings that might have stunned me:
========================================
CWM BAckup of DDGB 2 Works ???
-- CWM backup of DDGBv2 is not at all working. Someone try this..
-- When I tried CWMbackup to restore it landed up into bootlop at all 3 times; where as the same time my other CWM backup could restore my device fully..
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Re-Flashing DDGB V2 ROM is an issue for me: Very Amazing observation
-- Some how, I while trying New mods of JT along with several other apps. When I installed many things all together and got a bootloop (somehow)
-- I when failed to load CWN Recovery; tried to flash the DDGBv2 ROM itself. I tried this for 3 times but all 3 times it stuck into booloop.
-- But when I tried to Flash other ROM it worked.... I want to know the reason !!!
Expert Comments on this, Please: Jyothis Thaliath, Sree Atitde Adjstmnt, Dhinesh Kumar, Hardy Ahir, Shashank, Meet and any one who friendly enough on doing things with their devices NOTICE AND COMMENT PLEASE...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Boot Sound has been added but its not working coz, added sound is not in required format. It has to be boot.wav, shutdown.wav and android_audio.mp3 (here Dhinesh have provided all .mp3 files, so no boot sound on reboot or shutdown)
-- Note: No need to add any additional files in library or etc for getting boot audio or shutdown audio as discussed by our friend Panneer.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
'Linux partition' and 'androidswap' thing working with this ROM and got Good Gaming experience with this ROM although it wasn't consistent every time and for that I dont blame this ROM but the Linux partition. I tried all this to play Temple Run 2.
-- I am still confused on this Linux partition whether it works always or sometimes. Lags still there many a times and some times its like a FISH !!!.
-- but the fact was that I created the Linux partition when I was on GINGER XF and i also configured swappaines during that time only.
-- When I tried all method to configure Linux partition with DDGB v2 I could not configure swappines and the error every time was something like " the said partition is busy"
-- To overcome that I rebooted into recovery and tried creating swappines but failed. Why I tried this coz i was successful with this method while giving demo (setting up) this linux partition on Ashish Chopra 's device (a member here) using TV8. Lol but the same method did not work for myself.( Ashish Chopra )
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PLEASE MARK THIS:
Remember Friend DO NOT take my words here as a criticism on DD-GB v2. I also voted this ROM as the best till now and liked it as well. HEre my too much detailed post is to get some underneath hidden facts behind issues occurred with ROM flashing and Backups
Let find out the reasons behind it so that If its a real issue then can be corrected in Next versions of ROMs but our fellow members...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What can be the ISSUE behind all this ????
I had several doubts and at the top of the list is: APPS2SD as Kitchen warns that apps2sd is not compatible with A57
So the Doubt List comprised of following:
1. Apps2SD
2. Added files in /system/Framework in this ROM
3. Added files in /system/bin and /system/xbin
4. 'XLoud function' or 'Beats Audio' functionality and related files in /system
5. Configuration of 'Linux Partition' and the 'androidswap' file in init.d
I really want the Developer and other experts to take this post seriously. Hope we can get something out of it...
Files Attached : Logcat.txt attached (this was after I tried to Flash CWM backup of DDGB V2)
__JOhnny said:
any easy way to to flash cwm.. because i dont have any sdk tools
Click to expand...
Click to collapse
Download and rename it to recovery.img
Place it in Factory_update.zip (by replacing the stock recovery.img)
Now flash the Update.zip in recovery mode.
Done the CWM is no on yr Device on reboot.:good:
VioletR said:
Deep inside DD-GB v2
================
There were few friends like Priyank Thakur, 'Deadman Akshay' & Monty Kumar faced..(Serious) Screen OFF (Deep Sleep) issue with DD-GB v2
--I confirm that the raised issue is the Valid problem.... I too faced the same
and has to be verified. In addition I have almost researched on this ROM I have interesting outcomes..please go steady..its really serious for Ninja 3 Development in future.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Success of this ROM:
I congratulate the Develope Dhinesh Kumar (dhinesh77) on successful edition of DD-GB v2
-- Yes this is definitely a Successful Custom GB ROM for Micromax A57 and was got praised by almost all at including me
-- All basic functions working perfect and no issues at all
-- All though no much build prop tweaks added but enough to get us speed and added functionality as there are required init.d tweaks
-- xloud and beats audio: sound enhancements also works up to some extent but personally I want so much insist on that
-- This ROM has got additional framework files from Sony framework to support audio enhancement.
-- You can have good gaming experience on this ROM without adding any additional Tool for the same
-- And several additional Features. For details visit: http://forum.xda-developers.com/showthread.php?p=37207089
-- My overall Experience with this ROM is quite better compared to other custom ROM published till now.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- I saw apps2sd working OK with this ROM
-- apps2sd transfers all apps automatically to apps2sd partition
-- even Titanium backup apps restores in apps2sd partition and TB shows capacity of this partition when it starts
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
However folling are findings that might have stunned me:
========================================
CWM BAckup of DDGB 2 Works ???
-- CWM backup of DDGBv2 is not at all working. Someone try this..
-- When I tried CWMbackup to restore it landed up into bootlop at all 3 times; where as the same time my other CWM backup could restore my device fully..
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Re-Flashing DDGB V2 ROM is an issue for me: Very Amazing observation
-- Some how, I while trying New mods of JT along with several other apps. When I installed many things all together and got a bootloop (somehow)
-- I when failed to load CWN Recovery; tried to flash the DDGBv2 ROM itself. I tried this for 3 times but all 3 times it stuck into booloop.
-- But when I tried to Flash other ROM it worked.... I want to know the reason !!!
Expert Comments on this, Please: Jyothis Thaliath, Sree Atitde Adjstmnt, Dhinesh Kumar, Hardy Ahir, Shashank, Meet and any one who friendly enough on doing things with their devices NOTICE AND COMMENT PLEASE...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-- Boot Sound has been added but its not working coz, added sound is not in required format. It has to be boot.wav, shutdown.wav and android_audio.mp3 (here Dhinesh have provided all .mp3 files, so no boot sound on reboot or shutdown)
-- Note: No need to add any additional files in library or etc for getting boot audio or shutdown audio as discussed by our friend Panneer.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
'Linux partition' and 'androidswap' thing working with this ROM and got Good Gaming experience with this ROM although it wasn't consistent every time and for that I dont blame this ROM but the Linux partition. I tried all this to play Temple Run 2.
-- I am still confused on this Linux partition whether it works always or sometimes. Lags still there many a times and some times its like a FISH !!!.
-- but the fact was that I created the Linux partition when I was on GINGER XF and i also configured swappaines during that time only.
-- When I tried all method to configure Linux partition with DDGB v2 I could not configure swappines and the error every time was something like " the said partition is busy"
-- To overcome that I rebooted into recovery and tried creating swappines but failed. Why I tried this coz i was successful with this method while giving demo (setting up) this linux partition on Ashish Chopra 's device (a member here) using TV8. Lol but the same method did not work for myself.( Ashish Chopra )
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PLEASE MARK THIS:
Remember Friend DO NOT take my words here as a criticism on DD-GB v2. I also voted this ROM as the best till now and liked it as well. HEre my too much detailed post is to get some underneath hidden facts behind issues occurred with ROM flashing and Backups
Let find out the reasons behind it so that If its a real issue then can be corrected in Next versions of ROMs but our fellow members...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What can be the ISSUE behind all this ????
I had several doubts and at the top of the list is: APPS2SD as Kitchen warns that apps2sd is not compatible with A57
So the Doubt List comprised of following:
1. Apps2SD
2. Added files in /system/Framework in this ROM
3. Added files in /system/bin and /system/xbin
4. 'XLoud function' or 'Beats Audio' functionality and related files in /system
5. Configuration of 'Linux Partition' and the 'androidswap' file in init.d
I really want the Developer and other experts to take this post seriously. Hope we can get something out of it...
Files Attached : Logcat.txt attached (this was after I tried to Flash CWM backup of DDGB V2)
Click to expand...
Click to collapse
Viloet edges first of all i want to convey my thanks for submitting review on DD_GB rom.....
``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
I think the major issue here is phone not booting when tried to reflashing or restoring CWM backup...
This issue is solvable when we perform additional step after reflashing or restoring rom..the step is wipe data/factory reset alone...
After that when we reboot our phone will boot normally...
Next is linux swap error:
``````` `` ``````` ``````` ```````
IN my phone i have created linux swap partition using mini tool.as third partition...However i never configured that partition using any special software like swapper2 & etc..But heavy games r working well like gta3,temple run 2 and so on..
For configuring swap I think we dont want any softwares It will got automatiically working (Solution for testing)
If it not works fell free to post reply...
Regards,
Dhinesh Kumar
VioletR said:
Download and rename it to recovery.img
Place it in Factory_update.zip (by replacing the stock recovery.img)
Now flash the Update.zip in recovery mode.
Done the CWM is no on yr Device on reboot.:good:
Click to expand...
Click to collapse
Way is factory Update zip if not much trouble
Can you do it for us who don't no much about it
Sent from my GT-I9103 using xda premium
:good::good::good: Version 2 Is Really Good
I am on it at present... :angel:
Easy way to FLASH CWM RECOVERY in just 5 minute
Downlaod CWM: A57recovery.img : http://forum.xda-developers.com/showthread.php?t=2073337
Download Recovery Manager : pm me for the link
1. Copy A57recovery.img in SD card root,
2. Now install the recovery manager.apk normally
3. Now open the recovery manager app you recently installed.
4. Click on recovery in app menu.
5. There click on install recovery
6. Then click on the recovery image name of ‘A57recovery.img’
7. Let the app install the recovery. after it done a message will show.
current recovery : unrecognized…. just ignore it.
That’s all now you have installed your recovery
Thanks to violetR
Please press thanks if it helped
VioletR said:
:good::good::good: Version 2 Is Really Good
I am on it at present... :angel:
Click to expand...
Click to collapse
Thanks violet: :laugh::laugh::laugh:
Is it possible for someone to make notification toggle for our device
Where can I get stock ROM and recovery ?It is better while claiming for warranty.
Sent from my GT-S5570 using xda premium
i flash this rom.. Works Good
Btw will you please share Stock ROM
__JOhnny said:
i flash this rom.. Works Good
Btw will you please share Stock ROM
Click to expand...
Click to collapse
Link for stock rom:
`````` ``` ```````` ```````
http://www.mediafire.com/?b1vvdyxdnz6z66k
Note:
U need stock recovery for flashing stock rom..
U can get stock recovery from stockrom.zip itself....
so no problem to switch between roms...
Aniruddhagupte11 said:
Where can I get stock ROM and recovery ?It is better while claiming for warranty.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Link for stock rom:
`````` ``` ```````` ```````
http://www.mediafire.com/?b1vvdyxdnz6z66k
Note:
U need stock recovery for flashing stock rom..
U can get stock recovery from stockrom.zip itself....
so no problem to switch between roms..
small fixes would be great
Great job guys and Thanks for Rom, I am currently running this Rom. I found some problems if u may fix it would be great
-- I am unable to install facebook app in the device, I used to install the updates in the Stock Rom as the stock rom already contains the facebook. So what i have done is taken the stock rom facebook app and installed but unable to update it and even the fruit ninja, etc., It shows device is incompatible.
-- The dialer app. It doesnt show the call time and date. I have tried to replace the dialer with samsung dialer but it doesnt work ( for me ). if there is a app which shows the time and date of the call and from which sim the call comes from. that app would be great like exdialer but with this app it doesn't show what sim the call came from.
-- my humble request to please increase the ear piece volume, i dont know whether it is hardware or software problem. I have tried all the tweaks and apps which are available in market but nothing works.
Please reply me, I am ready to test the ROM, i have once bricked the phone went for hardware replacement also . he gave the hardware part which have damaged lol...
Help !!
dhinesh77 said:
Custom rom for Micromax A57 ..NINJA3
***Updated version***
(BASED ON Stock rom 2.3.5)
FEATURES
Added data/app functionality
added xloud and beats audio
new settings mod
Fast remount and mount
fully moded UI
Transparent settings widget
Link2sd and titanium backup were added
New bootanimation and shutdown animation
icecream sandwhich ringtones
walkman as default music player
Rooted with latest su
Busy box added
zipaligned
freed up internal memory
optimized RAM for better performance
Modded settings
new bootanimation added
Increased battery performance
Increased touch responses
Increased camera recording quality
Improved 3G handling performances
Improved proximity sensor
Improved net speed
init.d support
and lots of tweaks
DOWNLOAD:cyclops::cyclops::cyclops::cyclops::
Dont forgot to download this update fix...
Update fix
How To Flash This RoM
Use Cwm Recovery to flash This Rom
If you already have Cwm installed then Go on with below steps to install the Rom
0.
Recreate or format Ext2/3/4 partitions if any
1.
Download the Rom Zip
2.
Place the zip In Sdcard
3.
Go to Cwm Recovery
4.
Wipe Data & Cache
5.
Wipe Cache
6.
Select Mounts and Storage>format system>yes
7.
Select Advance>wipe dalvik cache>yes>
8.
Then Flash Rom
9.
After flashing again do wipe data/factory reset..thats it
10.
now again select install zip from sdcard..
11.
And flash the update fix
12.
Reboot the phone
13.
Now enjoy with the new rom
Credit:-
1. Sahil Deep,
2.Violet Edges
2. [URL="https://www.facebook.com/Dhinesh77"]Dhinesh Kumar[/URL] ...:victory::victory::victory::victory:
Click to expand...
Click to collapse
My A57 hanged on reboot startup screen and dont working please help asap!!..
pratimdutta said:
My A57 hanged on reboot startup screen and dont working please help asap!!..
Click to expand...
Click to collapse
do you have installed cwm recovery..If yes go to recovery do wipe data/factory reset. done