Database Develop

New to Android or NAND?

I'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
​
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.

thank you this was very helpful

inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...

yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a

jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?

staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.

when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?

Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?

Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!

Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.

staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?

Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them

so really it doesn't matter how big the card is? do they all have to be formatted to fat32?

Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.

Hey guys...I will try my best to get that video up today. I am about to start recording it.

Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.

stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.

im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.

gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?

If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...

[BOOTSTRAP] Custom Safestrap v1.08f Released - 4-16-2012

Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u

i need this about 6 hrs ago lol.

Quite useful mate cheers.
=smc

Thank you so much for sharing this file. Your work is greatly appreciated.

This is a nice little(big)addition to safestrap! Thanks for adding it in!

I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!

Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.

TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.

I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium

Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.

redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium

Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!

ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium

Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^

orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???

@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.

I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.

This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!

Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.

Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!

[Q] Galaxy ACE S5830 needs the kiss of life. Help needed.

My Samsung Galaxy ACE S5830 needs the kiss of life, so as to return to the 21st century.
It has slow responses and quite often freezes and messes up with my nerves.
It currently runs on a 2.3.5 android version.
I want to root it, take a backup, increase ram by creating a partition in my new sd card and install a light custom rom (like MIUI). For this purpose, I just bought a very fast Kingston 32GB, class 10 U3, sd card with theoretical 90MBs read and 80MBs write speed. I think that will suffice.
I am a simple user and I need basic functions. My main issue is to get a faster response from the phone. I don’t play games and I am not a major fun of social media. I just want to want to use it mainly as a phone, for calls, messages, Viber, and some extra facilities like emailing, web browsing, watching some videos online (news and youtube), occasional photos, listen to music, and install a GPS program like Sygic.
I’ve already read a lot about the whole process, but as I’m doing it for the first time in my life I want to make sure that I got it right. And I have a few ambiguities.
Please advise or freely suggest if any better/easier method is available.
1. Rooting.
I decided to use Kingo Root. So, I need to download Kingo Root to my pc and connect the phone (having enabled USB debugging) and just press Root. Then check if rooting is successful with Root Checker. Then download and install SuperSU app. And I’m done.
Do I need to unlock my bootloader, too?
2. Backup.
a) Take an image of the existing ROM.
Download and install ROM Manager, flash ClockworkMod Recovery and update. Boot in to recovery by using ROM Manager or manually by pressing simultaneously UP+POWER+HOME buttons. Then go to Backup and Restore and take a backup image. Right?
b) Backup apps and messages.
I want to take just 2 backups here, my text messages and my Viber messages. Do I use Titanium or something else? My contacts are already synchronized with Google. If I use a MIUI stock rom do I need to take a backup of my contacts too?
3. Increase phone's RAM
I think now is the right time to increase the phone’s RAM. Do I need to partition it with CWM? Or I just use an app like Ram Expander? Do I do both? I mean firstly partition the sd to the desired size and then use Ram Expander? None of the above? What do you suggest? I have read some other possible solutions like using INT2EXT+ after partition. And when I download a new app how will the phone know where to store it, in phone’s RAM or in sd card?
The key factor is speed and efficiency.
I’ve also read that “Even though the Internal Storage would read 2GB (or whatever is your partition size), the apps would still use some amount of REAL INTERNAL Storage for data, hence you need at least 100MB REAL Internal Memory for every 500MB SD-EXT memory.” Is this true? And if so, since I believe the Galaxy ACE S5830 has about 150 MB RAM the most I can actually get is 750 MB RAM?
It is important to get as much RAM as possible because I’ve read that Sygic (the GPS Navigator app) needs to be installed in phone’s RAM to work properly and it is about 700MB.
4. Install Stock ROM
Finally, the time has come to install a new stock rom. I am thinking about MIUI 6. I like its interface and I’ve heard it is light and fast. Any better suggestions? Can I do it in my phone?
My problem here is this, is MIUI a fully functional stock rom, which means I just download it and flash it or is it a “port rom” which means I have to previously install some android 4.4.x base rom? I have read in some article that is needs a compatible android rom to lean on before installing. Is that so?
Here I am stuck, I can’t decide how to proceed and I need your help.
Sorry, if the post is too long.

Hi there, long time galaxy ace user and MIUI lover here.
1. For rooting my device, I just flashed a zip in recovery mode. Can't find the link to that thread.
2. Yes, backup is very important right after rooting, especially for beginners.
As for sms backup, I recommend using SMS backup and Restore, which can be downloaded from the market. I haven't used viber, so I don't know which app would be the best for backing it up, but you can try Titanium backup. For contacts, you can sync them as long as you flash a g-apps package and sign in with the same google account. To be sure, you can try exporting your contacts to your sd card and import it later on (.vcf)
3. I did not even increase my phone's ram via swap, Even with a tiny ram, Miui on top of Cm7 is pretty fast and can handle any basic task such as browsing, youtube videos, music, calling, camera, camcording and messaging with minimal stutters. (I don't play games btw)
4. If you are a simple phone user just like me, who only need some calls, sms and browsing functionality, the best bet would be to use MIUI builds based on gingerbread (CM7). I found that MIUIv4 builds (ICS and JB) are poorly optimized for our device. Also, there are currently no MIUI v5 or v6 builds for armv6 devices.
My personal recommendation is: MIUIXXX http://forum.xda-developers.com/showthread.php?t=1908444 which comes with FireKernel OC.
I use Gabreek's Miui v5 theme, which you can find it on his thread http://forum.xda-developers.com/showthread.php?t=2280553 In my opinion, his v5 theme is the best, because of LOTS of app icons and the overall feel.
Also, be sure to flash a g-apps package for gingerbread after flashing the rom.
MIUI v4 snapseries build is too unresponsive for me, and missing some features like screen off animation. http://forum.xda-developers.com/showthread.php?t=1879323
MIUI v4 JB by msnnsm is also good, but consumes lots of ram http://forum.xda-developers.com/showthread.php?t=2054460.
TL;DR: flash an miui gb rom. It is the best in terms of stability and speed.

Thanks for your prompt answer and suggestions my friend. I will follow them all.
One question please, which is the most important query for me:
After I have made all the preparations (root and have taken a backup image with CWM, messages, etc.), what is the next step?
a) I need to install and flash the phone with a CM7 first and then install and flash MIUIXXX?
or
b) I just flash MIUIXXX straight away?
Also, I am not sure I understood correctly, Gabreek's Miui v5 (which is now updated to v6) is an alternative MIUI rom or a theme? Because I have downloaded it and it is a zip file not an .mtz file.
I am sorry if these sound like very noobish questions but I want to make sure that I understand what I am doing before I actually do it.
Thanks again for your help.

tommycr7 said:
Thanks for your prompt answer and suggestions my friend. I will follow them all.
One question please, which is the most important query for me:
After I have made all the preparations (root and have taken a backup image with CWM, messages, etc.), what is the next step?
a) I need to install and flash the phone with a CM7 first and then install and flash MIUIXXX?
or
b) I just flash MIUIXXX straight away?
Also, I am not sure I understood correctly, Gabreek's Miui v5 (which is now updated to v6) is an alternative MIUI rom or a theme? Because I have downloaded it and it is a zip file not an .mtz file.
I am sorry if these sound like very noobish questions but I want to make sure that I understand what I am doing before I actually do it.
Thanks again for your help.
Click to expand...
Click to collapse
It's completely fine to flash miuiXXX right away (B)
gabreek's is another MIUI rom, but bluetooth is not working in his v6 build. The theme file (mtz) is somewhere in the bottom of the post, below some useful tips and just above the credits part of his post

Thanks again for your help.
I also thought the same, but I wanted to make sure.
I have already rooted my phone and I am in the process of taking various backups.
I will try the rom you have recommended and I will revert to report.
I think I owe you as much.
Btw do you know if Themer works in MIUI? It's quite an impressive app to have.
Cheers

as far as i know, themer does not work.
Also, MIUI comes with its own theme engine, and you can download online, which is very nice.
Remember that when Applying themes, do not include lockscreen (uncheck lockscreen) . Lockscreens from the Theme app are meant for HDPI device, and you won't be able to unlock your phone if you apply them. If you accidentally get stuck on the lockscreen, press volume up and back button at the same time. It will unlock your phone.
There are a handful of themes ported to MDPI which you can use over here: http://forum.xda-developers.com/showthread.php?t=1428940

So far, so good, I have not experienced any major problems.
2 more things to ask if you dont mind.
a. Where do I get the gapps file to flash from? Is is a specific file for our rom (MIUIXXX) or any gapps file will do?
b. Can I add an extra language, in the android keyboard or do I have to use an app for this? Or even better in the system itself. I am from Greece and I would find it very convenient in some tasks of the phone. I mean since it is essentially a MIUI rom and MIUI has the greek language in its official roms, there must be a way that this can be done.

tommycr7 said:
My Samsung Galaxy ACE S5830 needs the kiss of life, so as to return to the 21st century.
It has slow responses and quite often freezes and messes up with my nerves.
It currently runs on a 2.3.5 android version.
I want to root it, take a backup, increase ram by creating a partition in my new sd card and install a light custom rom (like MIUI). For this purpose, I just bought a very fast Kingston 32GB, class 10 U3, sd card with theoretical 90MBs read and 80MBs write speed. I think that will suffice.
I am a simple user and I need basic functions. My main issue is to get a faster response from the phone. I don’t play games and I am not a major fun of social media. I just want to want to use it mainly as a phone, for calls, messages, Viber, and some extra facilities like emailing, web browsing, watching some videos online (news and youtube), occasional photos, listen to music, and install a GPS program like Sygic.
I’ve already read a lot about the whole process, but as I’m doing it for the first time in my life I want to make sure that I got it right. And I have a few ambiguities.
Please advise or freely suggest if any better/easier method is available.
1. Rooting.
I decided to use Kingo Root. So, I need to download Kingo Root to my pc and connect the phone (having enabled USB debugging) and just press Root. Then check if rooting is successful with Root Checker. Then download and install SuperSU app. And I’m done.
Do I need to unlock my bootloader, too?
2. Backup.
a) Take an image of the existing ROM.
Download and install ROM Manager, flash ClockworkMod Recovery and update. Boot in to recovery by using ROM Manager or manually by pressing simultaneously UP+POWER+HOME buttons. Then go to Backup and Restore and take a backup image. Right?
b) Backup apps and messages.
I want to take just 2 backups here, my text messages and my Viber messages. Do I use Titanium or something else? My contacts are already synchronized with Google. If I use a MIUI stock rom do I need to take a backup of my contacts too?
3. Increase phone's RAM
I think now is the right time to increase the phone’s RAM. Do I need to partition it with CWM? Or I just use an app like Ram Expander? Do I do both? I mean firstly partition the sd to the desired size and then use Ram Expander? None of the above? What do you suggest? I have read some other possible solutions like using INT2EXT+ after partition. And when I download a new app how will the phone know where to store it, in phone’s RAM or in sd card?
The key factor is speed and efficiency.
I’ve also read that “Even though the Internal Storage would read 2GB (or whatever is your partition size), the apps would still use some amount of REAL INTERNAL Storage for data, hence you need at least 100MB REAL Internal Memory for every 500MB SD-EXT memory.” Is this true? And if so, since I believe the Galaxy ACE S5830 has about 150 MB RAM the most I can actually get is 750 MB RAM?
It is important to get as much RAM as possible because I’ve read that Sygic (the GPS Navigator app) needs to be installed in phone’s RAM to work properly and it is about 700MB.
4. Install Stock ROM
Finally, the time has come to install a new stock rom. I am thinking about MIUI 6. I like its interface and I’ve heard it is light and fast. Any better suggestions? Can I do it in my phone?
My problem here is this, is MIUI a fully functional stock rom, which means I just download it and flash it or is it a “port rom” which means I have to previously install some android 4.4.x base rom? I have read in some article that is needs a compatible android rom to lean on before installing. Is that so?
Here I am stuck, I can’t decide how to proceed and I need your help.
Sorry, if the post is too long.
Click to expand...
Click to collapse
Hi There,
To Root Your Device See The XDA's post.
Take The Backup of Current Rom Using CWM recovery or ROM Manager would do this too.
Then inorder to Increase Memory On Your Device By Partitining the SD Card.
Check My Guide over it in Galaxy Ace Development Section or General Android Dev Section.
If Helped Click Thanks

Hi,
1.
Try always to have on your sdcard a backup or a ROM that works ok.
Probe this a few times to be sure you can return anytime to the previous step.
2.
Take a notepad and make a change log with steps you made, so you can return to the previous step if something is not working ok.
3.
Try first to understand what you want to do, to be sure that you will not commit an error.
Try to learn from the mistakes of others.
It will be much easier for you.

Virgin Mobile Help

I have one of the Virgin Mobile models that has the smaller memory. I have been looking through these forums looking for a way to clear up the memory. It looks like there is simply not enough progress on this phone currently. What I would really like is a basic ROM replacement that does not have any of the HTC crap in it to make it leaner and use less space. Am I right that I need to wait for future developments? I just want to make sure I am not missing something. Is there any way to free up more space right now with existing hacks? I see lots of different posts in here, and when I think I am on to something, I read that it does not work on the Virgin Mobile phones, so I am getting confused. I was hoping somebody who knows my phone really well could hold my hand and tell me exactly what I can do to get some more free space. I am familiar with a lot of the tools, and have rooted and installed recovery on my Kindle Fire, and on my Ouya. I have rooted an old LG phone, but that was cake compared to what I am reading for this phone! Thank you!

Probably the best you can do for now would be to flash a write protection removed kernel, remove as much uneccessary HTC and carrier bloat as possible, and then use an app from the Play Store called System App Manager to turn most of the apps you install into system apps, thereby using unused space on /system instead of your internal storage. My advice is to make a TWRP backup before converting any apps, because some apps will not act right after being moved to /system, so just do a process of elimination/trial & error until you figure out which apps can be moved without causing problems. When you figure out which apps act up, restore your backup and re-do the process without converting the unruly apps.
You also might want to flash Raptor Rom, as it's probably the smallest rom available, leaving tbe most empty space for those apps you move. Someday we'll get a rom/kernel that will allow the moving of apps & thier data to an sd partition, till then this is probly your best bet.
sent from a device

huggs said:
Probably the best you can do for now would be to flash a write protection removed kernel....You also might want to flash Raptor Rom, as it's probably the smallest rom available
Click to expand...
Click to collapse
Great! Can anybody point me in the right direction for some good/updated directions on performing each of these? Thank you!

jrburke99 said:
Great! Can anybody point me in the right direction for some good/updated directions on performing each of these? Thank you!
Click to expand...
Click to collapse
Firstly, if you haven't done so already: Follow this
Then go grab the download from whatever kernel you want to use thread or grab RaptorROM here. RaptorROM already includes a version of @Pattyboi's kernel, but you can always flash the newer kernel (which he put up last night?) on top.
Drop whatever files you plan on flashing onto the phone, or the sdcard. Reboot into TWRP (volume down and power button when phone's off then select Recovery), tap install, find the .zip or .img to flash, tap, then Swipe to Install/Flash

[Q] Some questions before I purchase a Desire 510

Hello, all! Just joined up to post a few questions. Every Android phone I have owned has been rooted and a custom ROM installed, so I am no stranger to all this. I'm finally getting around to replacing my ancient Motorola Triumph (Virgin Mobile USA) and for cost reasons I am seriously considering the Desire 510. I'd love to get the Desire 816 but that's out of my current price range Anyway, I have been reading the posts here and over at Android Forums dot com and I am confident that I will have no problems with the 510 should that be the phone I end up purchasing. But I've got several questions before I make a final decision.
1. Can anyone tell me (or how can I find out) if the 510 from Virgin Mobile USA is the 32-bit or 64-bit phone? I wasn't able to find much information except something online (unrelated to Virgin Mobile) that says the U.S. version is 32-bit while all other countries get the 64-bit. Since that information is now several months old can anyone confirm that it still holds true, or is there a possibility that 64-bit devices are now available in the U.S.?
2. If the Virgin Mobile USA version is indeed 32-bit, is there anywhere I can get a 32-bit ClockworkMod recovery? I see a post here for a 64-bit CWM but couldn't find mention of 32-bit anywhere. Nothing against TWRP, just that I have been using CWM since Day 1 of rooting and that's what I'm comfortable with. Also, before flashing a new recovery, how do I go about making a backup of the stock recovery.img? I imagine there's a way to rename it (i.e. recovery-stock.img) or copy it to my PC for safekeeping, but I'm not very familiar with Android SDK. (My current phone does not need SDK for anything. Simply plug in, copy new recovery where it needs to be, and reboot.)
3. What, exactly, is the write protection that I have seen mentioned all over the place? Correct me if I'm wrong, but it *SOUNDS* like rooting and/or installing a custom recovery and/or installing a custom ROM essentially cuts off SD card access until a "fix" is applied. So if anyone can offer a simple explanation or a link to some information, that would be fantastic.
4. Taking #4 into mind, what do I need to consider in choosing a kernel? If it matters, I have been looking mainly at CurbThePain's RevMod, but also LarryBoyG's RaptorRom GPE v2 and shinru2004's Unofficial CM11.
I know that's a lot of questions all in one place but I figured I'd start somewhere. Any and all answers are appreciated, and any questions for me will be answered in as timely a manner as I can. Thanks in advance for any info you guys are able to provide me.
EDIT:
5. Supposedly this phone has 8GB of internal memory but all the screenshots I see say it has 4GB, and most of that is taken up by the operating system. I was just reading the reviews on virginmobileusa.com and almost every single one of them is negative, focusing on the fact that nobody can download more than a few apps before the phone runs out of memory. What's the official internal storage for OS and apps, 4GB or 8GB, and how does the memory look after a custom ROM is installed?

Some answers before you purchase
GKNByNW said:
Hello, all! Just joined up to post a few questions. Every Android phone I have owned has been rooted and a custom ROM installed, so I am no stranger to all this. I'm finally getting around to replacing my ancient Motorola Triumph (Virgin Mobile USA) and for cost reasons I am seriously considering the Desire 510. I'd love to get the Desire 816 but that's out of my current price range Anyway, I have been reading the posts here and over at Android Forums dot com and I am confident that I will have no problems with the 510 should that be the phone I end up purchasing. But I've got several questions before I make a final decision.
1. Can anyone tell me (or how can I find out) if the 510 from Virgin Mobile USA is the 32-bit or 64-bit phone? I wasn't able to find much information except something online (unrelated to Virgin Mobile) that says the U.S. version is 32-bit while all other countries get the 64-bit. Since that information is now several months old can anyone confirm that it still holds true, or is there a possibility that 64-bit devices are now available in the U.S.?
2. If the Virgin Mobile USA version is indeed 32-bit, is there anywhere I can get a 32-bit ClockworkMod recovery? I see a post here for a 64-bit CWM but couldn't find mention of 32-bit anywhere. Nothing against TWRP, just that I have been using CWM since Day 1 of rooting and that's what I'm comfortable with. Also, before flashing a new recovery, how do I go about making a backup of the stock recovery.img? I imagine there's a way to rename it (i.e. recovery-stock.img) or copy it to my PC for safekeeping, but I'm not very familiar with Android SDK. (My current phone does not need SDK for anything. Simply plug in, copy new recovery where it needs to be, and reboot.)
3. What, exactly, is the write protection that I have seen mentioned all over the place? Correct me if I'm wrong, but it *SOUNDS* like rooting and/or installing a custom recovery and/or installing a custom ROM essentially cuts off SD card access until a "fix" is applied. So if anyone can offer a simple explanation or a link to some information, that would be fantastic.
4. Taking #4 into mind, what do I need to consider in choosing a kernel? If it matters, I have been looking mainly at CurbThePain's RevMod, but also LarryBoyG's RaptorRom GPE v2 and shinru2004's Unofficial CM11.
I know that's a lot of questions all in one place but I figured I'd start somewhere. Any and all answers are appreciated, and any questions for me will be answered in as timely a manner as I can. Thanks in advance for any info you guys are able to provide me.
EDIT:
5. Supposedly this phone has 8GB of internal memory but all the screenshots I see say it has 4GB, and most of that is taken up by the operating system. I was just reading the reviews on virginmobileusa.com and almost every single one of them is negative, focusing on the fact that nobody can download more than a few apps before the phone runs out of memory. What's the official internal storage for OS and apps, 4GB or 8GB, and how does the memory look after a custom ROM is installed?
Click to expand...
Click to collapse
Hello GKNByNW,
1. Only one person on here said they have a 64-bit model that they bought in the U.S. from Cricket. You can probably ask the salesperson when you purchase it, but I think it's highly likely that the device you are going to buy will be 32-bit.
2. I don't know of a CWM for the 32-bit model. I was the same way. CWM was the only recovery I was used to. The first time I used TWRP was with this phone. I think you should try TWRP. I like it a lot. I have never used CWM Touch, but I'm sure TWRP may be like that. It is very user friendly. I don't know how you would go about making a backup of your stock recovery, but you should be able to use this one. It works great for my Boost phone. You may need to get familiar with adb and fastboot if you are not already. I don't know if we can just copy the recovery to where it needs to be, but most of us have been fastboot flashing it.
3. Write protection was included with Android KitKat. It has nothing to do with modding the phone. Google restricted some access to the sdcard, I believe for security reasons. When you flash a write-protect removed kernel, you can delete system apps, make changes to build.prop and make other changes. If you do not have a write-protect removed kernel, you can delete system apps, but when you restart the phone, they will return. You can also make changes to build.prop but when you restart they will not stick. I'm not sure of all of the things that will not stick if you have the stock kernel but those are a couple. Here is some more information: http://www.androidcentral.com/kitkat-sdcard-changes and https://source.android.com/devices/storage/index.html.
4. There are currently 2 kernels that most people use: Modded Desire 510 Kernel v2.6.1, which is tuned more for stability and Rhinstone-kernel, which is tuned more for performance. I haven't tried RevKernel and it hasn't been updated in a while, but you can check it out. Definitely check out the ROMs we have available and read through some threads to see which you like best.
5. The phone has 8GB internal, but we can only use ~1GB in the /data partition. I guess ~5GB is used for Android and Sense, since ~2GB is used for the /system partition. Check out this Storage Truth: https://goo.gl/photos/tCD1P26QTXM7my2r7
It's kind of weird, but this is the Storage Truth from my wife's phone, which has never been modded, and she has Cricket:
https://goo.gl/photos/uijoVA8Bk8tCtwe3A
She can still only use ~1GB, but I wonder why it shows ~4GB for the /data partition and only ~1GB for me.
After app updates and after you download a couple of apps the storage gets full, quick. The custom ROMS free up a lot of space. On a Jelly Bean based phone I had, without the sdcard restriction, I was able to integrate pretty much all of my apps on /system and have tons of room left over in /data. So I had so much space for apps and that phone didn't have as much "space" as this one has. On this one we're not so lucky. If you integrate the Google Play Store, Google Play Services, and the Gallery you will get force closes. There are more apps that will cause force closes if you integrate and delete them, but those are the main ones. You can delete the lockscreen with no issues, if you prefer the AOSP one. You can use Aparted and Link2SD to free up space. This method will allow you to download apps to your heart's content. Check out this thread to find out how to do that.

honestly,id skip the 510 and go for the 816 any day of the week. even if its more expensive,if i would have checked this thing out before i bought it after breaking my moto g,i would have bought a new moto (cricket dosent carry the 816)

blaqueknight said:
Hello GKNByNW,
1. Only one person on here said they have a 64-bit model that they bought in the U.S. from Cricket. You can probably ask the salesperson when you purchase it, but I think it's highly likely that the device you are going to buy will be 32-bit.
2. I don't know of a CWM for the 32-bit model. I was the same way. CWM was the only recovery I was used to. The first time I used TWRP was with this phone. I think you should try TWRP. I like it a lot. I have never used CWM Touch, but I'm sure TWRP may be like that. It is very user friendly. I don't know how you would go about making a backup of your stock recovery, but you should be able to use this one. It works great for my Boost phone. You may need to get familiar with adb and fastboot if you are not already. I don't know if we can just copy the recovery to where it needs to be, but most of us have been fastboot flashing it.
3. Write protection was included with Android KitKat. It has nothing to do with modding the phone. Google restricted some access to the sdcard, I believe for security reasons. When you flash a write-protect removed kernel, you can delete system apps, make changes to build.prop and make other changes. If you do not have a write-protect removed kernel, you can delete system apps, but when you restart the phone, they will return. You can also make changes to build.prop but when you restart they will not stick. I'm not sure of all of the things that will not stick if you have the stock kernel but those are a couple. Here is some more information: http://www.androidcentral.com/kitkat-sdcard-changes and https://source.android.com/devices/storage/index.html.
4. There are currently 2 kernels that most people use: Modded Desire 510 Kernel v2.6.1, which is tuned more for stability and Rhinstone-kernel, which is tuned more for performance. I haven't tried RevKernel and it hasn't been updated in a while, but you can check it out. Definitely check out the ROMs we have available and read through some threads to see which you like best.
5. The phone has 8GB internal, but we can only use ~1GB in the /data partition. I guess ~5GB is used for Android and Sense, since ~2GB is used for the /system partition. Check out this Storage Truth: https://goo.gl/photos/tCD1P26QTXM7my2r7
It's kind of weird, but this is the Storage Truth from my wife's phone, which has never been modded, and she has Cricket:
https://goo.gl/photos/uijoVA8Bk8tCtwe3A
She can still only use ~1GB, but I wonder why it shows ~4GB for the /data partition and only ~1GB for me.
After app updates and after you download a couple of apps the storage gets full, quick. The custom ROMS free up a lot of space. On a Jelly Bean based phone I had, without the sdcard restriction, I was able to integrate pretty much all of my apps on /system and have tons of room left over in /data. So I had so much space for apps and that phone didn't have as much "space" as this one has. On this one we're not so lucky. If you integrate the Google Play Store, Google Play Services, and the Gallery you will get force closes. There are more apps that will cause force closes if you integrate and delete them, but those are the main ones. You can delete the lockscreen with no issues, if you prefer the AOSP one. You can use Aparted and Link2SD to free up space. This method will allow you to download apps to your heart's content. Check out this thread to find out how to do that.
Click to expand...
Click to collapse
pattyboi:) said:
honestly,id skip the 510 and go for the 816 any day of the week. even if its more expensive,if i would have checked this thing out before i bought it after breaking my moto g,i would have bought a new moto (cricket dosent carry the 816)
Click to expand...
Click to collapse
Thanks for the replies, guys. I'm sorry for taking so long to get back and respond. Anyway... Yes, pattyboi, I am in total agreement. After reading reviews on Virgin Mobile USA's website and Amazon, I am definitely NOT going for this phone. Virgin no longer carries the 816 though it is still available new through retailers on Amazon, but the $180 price tag is a bit more than I want to spend on a phone right now. The other phone I had considered was the Samsung Galaxy Core Prime but it looks like that is only available for their Data Done Right plans, unless I am misunderstanding something. I don't really get what the whole Data Done Right thing is. It looks to be cheaper than my current plan ($45/mo. for unlimited talk/talk/1GB data) but I think Data Done Right is only for multiple lines. Also, I looked up the Galaxy Core Prime a couple weeks ago and it doesn't look like there's much information yet in regards to rooting and custom ROMs for that particular phone, so I might want to wait a while.