Develop Bugs

[GSM + CDMA] BeatsleigherRootHelper/Gainer| Gain root acces the easy way, with this!!

Welcome to the original thread, of Beatsleigher's Root Helper!!​
This program is completely free, with no Xtra options for donators...
What this program will do:​Well this program is designed for beginners, and advanced users. It has several modes; If you like to do everything yourself, then Ok, you can. If however you want Windows to do everything, it will.
If you need to setup ADB drivers, then follow the steps, in the ADB -> Help menu!!
List of features:​Several Reboot options,
Backup/Restore
Unlock bootloader (fastboot)
Relock bootloader (fastboot)
Root (ADB+fastboot)
Flash recovery (fastboot)
All-in-one solutions
Complete make over, now using a GUI!
Very explicit detailing of what the program is currently doing!
Install drivers - (USB + ADB/fastboot drivers)
List of ROMs/kernels
Help menus
What's to expect:​In-program E-Mail subscription, to get notified about updates.
Better IE Engine for XDA Link.
Context menus, for faster checking of radiobuttons.
Maybe adding an advert or two. Because I am now slowly but surely needing more money, for phones, so that I can program programs like this, for them.
Maybe re-add the main menu music. But, with music, that is a bit more calming... And not House ^^
A fully functional fastboot menu.
A user experience program, so I can collect feedback!!
Working progressbars.... (-.-")
FAQ:​Q:When installing the drivers, why do I need to change my system configuration?
A:You need to configure your machine, to notice the device, but to leave it alone, instead of looking for, and downloading drivers for it. This just confuses the computer, meaning you can't do anything in the bootloader, because Windows Update doesn't yet have the needed drivers...
Q: Why have you gone over to making a GUI? The batch files, were just fine...
A: I'm going over to making a GUI, because it is easier to use, less work. And I have the option, to just, drag & drop a button, write two lines of code, to make the button functional and then it's just a matter of creating the batch file, converting it to an EXE. Easy as pie. Whereas, with the batch files, to create one more option, you have to write 6 lines of code, then the batch file, and then half of the stuff doesn't work properly, because you didn't debug... If you know, what I mean...
Q: Why are there so many files???
A: This program needs so many files, so it can perform different processes/options/tasks
. But it isn't hard, to find out, what file, does which job
Q: Why is there only a version for windows??
A: I am working on a version, for Mac users, but it will take some time. I'm glad to be nearly finished, with the Windows version
Q: I want to donate to you, but you won't allow it. Why?
A: I don't accept any donations, because I only wrote the program to flash files on to your phone... I don't want to take credit for things, that other people did.
Instead of trying to donate to me, donate to chainfire, ChainsDD, and Kousik Dutta; for creating such brilliant recoverys, Apps (like superuser and ROM Manager) and ROMs...
BTW: If you really want to donate (which you won't ), you can send me some albums ^^ I need house music, to work.. And all my songs/albums have been listened dead -.-
Q: Do you mind if I use this program for commercial use, and post videos(tutorials) on Youtube?
A: As long as you DO NOT create mirrors, and let me know, I'm not that fussed... But then please post the link of the video to me, so that I can tell you if I like the way you did it, or not.
Q: When are you gonna stop talking about things, that don't interrest anyone (the FAQ)??
A: Now, but still thx for reading, other good questions will be posted here, aswell...
Thanks:​Many thanks to Kouschik Dutta for creating the recoveries for near-to all Android phones. Yo the man!
And not to forget the awsome app: ROM Manager ^^
Thanks to my good friend Accendare (baddinski), for creating the splashscreen. I appreciate it much
Thanks to Google, for creating the AOSP, for the great developers, to create even greater ROMs, for us!
Also, thanks to Google, for buying Android, and making suh a (rather) bug-free OS!!
If I forgot anyone, please let me know immediatly!!
Downloads:​
If you want to flash stock firmware, you will need to install this. This contains all the neccessary files/folders you need:
GSM: to be downloaded, by clicking this...
CDMA: to be downloaded here...
Ok, we've done it!! (I've done it...) We've gone out of Alpha.
We beat the beta!
Now, I'm proud to present; Beatsleigher's Root Helper... VERSION 3.0.0.8!!!!!!!!!!!!!!!!!!
Each and every script, has been either re-written, or has just gotten a makeover!!
Everything unneeded, has been removed, It's more compatible, with Windows XP, loading time has gone down!!
I've added a few options, but not that many, to make a big changelog...
To upgrade/update, please, copy ALL the files, you created/copied/moved there, to a safe place, on your hard drive. Then, delete "C:\Beatsleigher_root_helper"
Run the installer (It's contained in an ISO image, so, download PowerISO, should you not ahave an image mounting system...) and done!!
Download here
Screenshots:​View attachment 967846 View attachment 967847
View attachment 967848 View attachment 967849
View attachment 967850 View attachment 967851
View attachment 967852 View attachment 967853
View attachment 967854 View attachment 967855
View attachment 967856 View attachment 967857
View attachment 967859 View attachment 967860
View attachment 967861 View attachment 967862
View attachment 967863 View attachment 967864
If you want to see more, download it
Installer:​The installer will install to your C:\ drive. Some older scripts, are still working with "%homedrive%" so, to make sure, that everything is working, please make sure, that your homedrive is your C:\ drive. Or, if you have a seperate C:\ drive (like me), copy a copy, of the "Beatsleigher_root_helper" folder, to your homedrive. Then it should do the trick. By the tiome, the program is released properly (full) all scripts should be working with "C:\".
Should you have NOT got a C:\ drive, because your homedrive is named differently/you deleted the C:\ partition, see: installation help.
EDIT: The installer has been split in two!! They are both in an ISO image... Once mounted, the secondary installer will run (setup.exe). Just open the virtuall CD-ROM, and run "Install.exe"
Requests:​If you have any requestes (features, etc.), please PM me, or send me an E-Mail!!
Or, visit: This page
Please read!!:​Sorry for not updating this thread, as much, as the GSM thread. If you want to stay up-to-date, then click here every now and then
Changelog:
Version 3.0.0.8:
Full release, no BETA, anymore...
Two installers, instead of one...
All scripts have been re-written or have had a makeover...
Version 2.6.5.7 [Minor 3]:
Some tweaks and additions... Mostly hidden...
Some preparations, for full release.
Next version will be 2.7
Version 2.6.5.5 (BETA) [Minor 2]:
Added some juicy developer features! (Using the ADB shell)
A few options, for n00bs, are in there, aswell...
Added options, to the ADB menu.
Added a complete new form. (Dev. options)
Added a few more scripts. Making the update zise about 6MB, on your HDD
Removed some buggy code.
When navigating, from ADB menu to Dev. Menu, ADB menu closes, but can be re-opened from the "File" menu.
Dev. menu has also got CPU/RAM usage detector!
Download, for more changelog
Version 2.6.5.4 (BETA) [minor]:
Working progressbars (!!!)
ADB menu got a makeover.
Added CPU/RAM usage detection
Added option to enable/disable CPU/RAM usage detection in fastboot menu.
Fixed bug in ADB help menu.
Added options to the m,ain menu...
The rest has been forgotten, or you're ment to download the program, and check for yourself...
NOTE:
If you are interested in downloading this product, please download version 2.6.5.3, install and then download/install 2.6.5.4.
Then you can be rest assured, that everything is working as good, as it should in the BETAphase, of a program
Version 2.6.5.3 (BETA):
Removed bug that caused phone crash, whilst prompting device name.
Cleansed the code.
Removed two un-used forms.
Repaired the menustripbutton.
Added scripts, to update package.
Removed other scripts, from update package.
Compressed some, of the files (drivers, executables)
Using traditional installer, again.
Installation path set to: C:\Beatsleigher_root_helper\
Version 2.6.5.2 (BETA):
Fastboot menu fully working.
Fastboot help menu, is popping up/has been created, though it has no content.
ADB help menu is working/all buttons have a task.
Some unneeded code has been removed.
A complete list of ROMs & kernels is present (CDMA + GSM).
No change in the IE engine...
All messages giving a tone/sound.
Options have ben added to the ADB menu.
New all-in-one solutions for ADB menu.
Scripts have been edited, for more friendliness
More tooltips.
Progressbars still not working ( )
Maximization has been disabled in ALL windows.
Better usage of RAM, whilst opening other exe - files
Version 2.6.5.1 (BETA)
Added update check-support.
Changed file hoster to mediafire (updates coming from there)
Added ADB reboot options.
Fastboot reboot options working.
Added (hidden) features.
Using a proper installer.
Can be installed anywhere on HDD, will work anyway
Two packages are to be downloaded, not one. This ensures, that updates are working, as planned.
(Hidden features will be released, when version is 2.6.5.3 (next update) )
Version: 2.6 D:
Everything you see, down the bottom is working.
You can now flash a recovery via fastboot menu!!
Kernel and ROMs, I have decided, to take them back out. They were a bit buggy...
The size of the EXE itself, has gone up to, ca. 2.4 MB.
Option to flash stock ROM (LTE + GSM) has been enabled, for fastboot.
Looks a bit more friendly
Icons have been added!
You'll have to find the rest out, yourself
Version 2.6C:
ADB menu has been carried on. You are now able to flash a kernel (LTE & GSM)
It will open the Explorer for you, when you need to copy the file!!
LTE menu is finally working!! It had problems opening, due to a minor type-error.
Though the LTE menu is working, you will only be able to use one button, in about an hour. Once I've completed doing the ADB menu...
(See: "What's to expect", for more info's on what's coming!!)
Version 2.6:
New GUI!
Complete new code.
In-program help.
Direct link to thread.
Seperate fastboot and ADB menus!
More explicit details...
Removed the music, that pops up, upon start. (To many house haters )
All batch files converted to executables... (This prevents tampering with the code)
Fully compatible with 64x machines. Doesn't use as much RAM, but therefore shows up as a process.
Installation help:​
Not much can go wrong, when install9ing this program.
Mostly, the reasons, of failure, to use this program, are due to:
Not having a C:\ drive.
Not copying a copy of the root folder, to hamedrive, if C:\ is not the homedrive, of your windows machine.
Tutorial 1:
Problem: I installed the program, but my homedrive is not C:\. I installed to C:\, but I can't use half of the program.
Well, first of all; sorry, for this. I could of said this earlier... I forgot to edit the scripts, to use ONLY the C:\ drive, so it useshalf the C:\ drive, and half your homedrive. But, that's why I posted this tutorial.
It's quick & easy ^^
Tutorial:
Install the program, to your C:\ drive. Close the installer, and re-open it.
Once back in the installer, set the installation path to your homedrive (Where Windows is installed).
Install to that directory, and done
It should now work ^_^
Tutorial 2:
Problem, I don't have a C:\ drive, and the ROM-Full/Less version, isn't available for download... What to do??
This is also no problem!! With a few, simple clicks of your mouse, we will fix this minor problem
Tutorial:
Type following key-combination, on your keyboard; START(WIN)+R.
The "Run" prompt should now pop up.
In the RUN prompt, type: "diskmgmt.msc" and it enter.
Once the disk manager pops up, shrink your homedrive(or, if you have unalocated disk space, which is 3GB or more, right click on that)
Shrink your homedrive, about 3GB. If you can, allocate more space, because you will need quite some space, because of stock ROMs/custom ROMs/kernels and backups.
To shrink, right-click on the partition and select "Shrink Volume". Enter this amount, to shrink: 3072 MB, that should be 3GB. Like I said, feel free to allocate more space.
Now you should see a black field. This is unallocated disk space. Right click on this space and select" Create simple partition" Make sure, you create the exact space, you shrunk, other wise, you will have some unallocated space, on your HDD and this can cause problems, if unnoticed.
Name the partition : C:. Wait, for the Diskman. to create the partition (can take up to 5 Minutes, for that amount of space, depending on size of HDD, CPU clock speed and amount of RAM).
Now, just install Beatsleigher's Root Helper to your C:\ drive and again, to your homedrive. Done! You can now use Beatsleigher's Root Helper.
If you should notice any other problems, please let me know, so I can solve them.
EULA:​Please read the EULA, should you not have, during installation. Or, you are interested in installing the prgram.
There is vital information, in this text document!

This post will be used for announcing updates and changelogs!
The first update, to be announced here, will contain some CDMA kernels and ROMs... They will all get QR-Codes, so you can download them directly on to your Android, if neccesary!
Only use this package to root your phone and flash recovery!!
The other images/ZIPs are on their way!! Before I get told off, for not telling you this.... I am making a package, that will delete all GSM files!
This reduces size, and no one gets confused!!

Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS

player911 said:
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
Click to expand...
Click to collapse
That's a good idea
I'll try and do something like that

player911 said:
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
Click to expand...
Click to collapse
Have done Even though it took a bit longer, to get here... Sorry, about that...
I just kept on forgetting, to update this thread. But it will be different, from now on

[Q] What would you expect, in a good Toolbox??

Hey guys!!
I'm developing a Root Helper (See my signature)
Now I want you, to decide, would you think, would enrichen my Root Helper...
Or, tell me; what do expect, from a good toolbox (My Root Helper...)
What would make you more eager, to use it?
Additions:​
I've taken some notes, and I think all of your ideas are good
And, here is another question: You wanted me, to explain, what which tool does, right?
Well, how would you prefer it? As a messagebox, before the program starts; or as a dialog, that pops up, whilst the program is running?
Or; should I put it as a tooltip?
The choice is your!!! The more you "vote" for whichever option, the higher the chance, I will add that to the program

familyguy59 said:
Hey guys!!
I'm developing a Root Helper (See my signature)
Now I want you, to decide, would you think, would enrichen my Root Helper...
Or, tell me; what do expect, from a good toolbox (My Root Helper...)
What would make you more eager, to use it?
Click to expand...
Click to collapse
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.

thacounty said:
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.
Click to expand...
Click to collapse
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems) -> Have got that done
Automatic updates for the toolbox -> Working on that ^^
Install Rom of choice or one with easy download from the toolbox -> Got that, too
Kernel Options - Advanced user only disclaimer -> It's a good idea, and would fit perfectly, to the ADB shell options ^^
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case) -> That was pretty much, the first thing, I put in, in both versions ^^
Radio updater - Radio of choice -> Also, a very good idea
Thanks, for the answer It's very much appreciated!! ^^

familyguy59 said:
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems) -> Have got that done
Automatic updates for the toolbox -> Working on that ^^
Install Rom of choice or one with easy download from the toolbox -> Got that, too
Kernel Options - Advanced user only disclaimer -> It's a good idea, and would fit perfectly, to the ADB shell options ^^
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case) -> That was pretty much, the first thing, I put in, in both versions ^^
Radio updater - Radio of choice -> Also, a very good idea
Thanks, for the answer It's very much appreciated!! ^^
Click to expand...
Click to collapse
Awesome, guess I should have read through what you had first! Looks like its going to be a great toolbox!

thacounty said:
Awesome, guess I should have read through what you had first! Looks like its going to be a great toolbox!
Click to expand...
Click to collapse
Well, I'm hoping, that it will keep getting better, and better ^^
And, this is one of my priorities; always ask the consumer

What I would like to see in a toolbox is this:
When you click on an option, say, "unlock bootloader" for example, I would like the toolbox to produce a pop-up describing how this is being done, something like: "This option reboots your device into fastboot mode (which you can do yourself by holding volume up and volume down and then pressing and holding power), and then issues the following command from a command prompt: fastboot oem unlock. This will produce a prompt on your device which you will have to accept or decline." etc. etc.
I would like to see this for everything option available in a toolbox, e.g., flashing a ROM, flashing a kernel, wiping, etc., etc..
This is the only way that we help people learn anything. If we just made everything 1-click, with no explanations, we are breeding ignorance, lack of knowledge, lack of troubleshooting ability, and lack of desire to learn... and a proliferation of "OMG I haz briked my fone" threads.

I agree with efrant. It should be informative and educational as well as functional. Possibly, though, to make it less annoying, make the popups appear only on first use of each of the commands. Also, perhaps make an option to just show all the information at once on demand.

FredFS456 said:
I agree with efrant. It should be informative and educational as well as functional. Possibly, though, to make it less annoying, make the popups appear only on first use of each of the commands. Also, perhaps make an option to just show all the information at once on demand.
Click to expand...
Click to collapse
Well, in my opinion, there is explanation, enough. But that is probably just a personal matter. There are options, to wipe, flash etc...
Sent from my Galaxy Nexus using XDA

efrant said:
What I would like to see in a toolbox is this:
When you click on an option, say, "unlock bootloader" for example, I would like the toolbox to produce a pop-up describing how this is being done, something like: "This option reboots your device into fastboot mode (which you can do yourself by holding volume up and volume down and then pressing and holding power), and then issues the following command from a command prompt: fastboot oem unlock. This will produce a prompt on your device which you will have to accept or decline." etc. etc.
I would like to see this for everything option available in a toolbox, e.g., flashing a ROM, flashing a kernel, wiping, etc., etc..
This is the only way that we help people learn anything. If we just made everything 1-click, with no explanations, we are breeding ignorance, lack of knowledge, lack of troubleshooting ability, and lack of desire to learn... and a proliferation of "OMG I haz briked my fone" threads.
Click to expand...
Click to collapse
Basically this. Some guide that pops up and tells step by step what the manual commands are. 1clicks perpetuate noobs, redundant threads and nerd rage.
zippity doo da.

Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.[/QUOTE]
All of the above plus the option to relock bootloader and restore the phone using a stock image incase it needs to be returned for warranty

niallmcg said:
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.
Click to expand...
Click to collapse
All of the above plus the option to relock bootloader and restore the phone using a stock image incase it needs to be returned for warranty[/QUOTE]
Dang dude. He will need a toolkit for the toolkit. And a crew. Lol.
zippity doo da.

EFS backup and restore for those that may be scared of adb and/or lazy.
Since this is a "Samsung" phone, EFS is (too) easily borked for random/inexplicable reasons.

fail safe file manager to copy files to your phone. I've had a couple of times where I thought I transfered gapps over and then realized as i was flashing a rom it was not there. luckily I was able to boot the phone and then transfer the file and do recovery again.

Flukester69 said:
fail safe file manager to copy files to your phone. I've had a couple of times where I thought I transfered gapps over and then realized as i was flashing a rom it was not there. luckily I was able to boot the phone and then transfer the file and do recovery again.
Click to expand...
Click to collapse
FWIW you can transfer files to your phone via adb when you're in recovery.

mudferret said:
FWIW you can transfer files to your phone via adb when you're in recovery.
Click to expand...
Click to collapse
True. I don't like using adb though.

mudferret said:
FWIW you can transfer files to your phone via adb when you're in recovery.
Click to expand...
Click to collapse
What ever happened to being able to mount storage device to PC in recovery? That is missed.

thacounty said:
What ever happened to being able to mount storage device to PC in recovery? That is missed.
Click to expand...
Click to collapse
The Galaxy Nexus does not support USB Mass Storage mode.

Ok. So I got many options, to add
But, @rbiter is right ^^ I'll need a toolbox, for the "toolbox" xD
But no worrys. I'll get it sorted!!

First off I agree with the comments above about extra help menus to guide each step for n00bs. My idea for a toolkit add on if it is even possable, is to be able to customize the themes on different ROMs.. Like to change all ics blue to green or red.. There are more ROMs now that have been blacked out/inverted but the choices of themes are limited..

XtreemDroid said:
First off I agree with the comments above about extra help menus to guide each step for n00bs. My idea for a toolkit add on if it is even possable, is to be able to customize the themes on different ROMs.. Like to change all ics blue to green or red.. There are more ROMs now that have been blacked out/inverted but the choices of themes are limited..
Click to expand...
Click to collapse
Well, there are help menus, for ADB and fastboot ^^
It's easy for n00bs...
I've added fastboot and ADB commands (ADB/fastboot help menus...)
But I'm still waiting for the answer, to my question...

[Guide] All things Iconia A100 (guide to modding) - updated 8.13.13

Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!

Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke

Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.

System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.

Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).

Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.

pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".

Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!

pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).

I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?

Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897

I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.

pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.

Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.

pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?

Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.

pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.

Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.

Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk

It's great to have all this information compiled in one location. Looking forward to your next installment. THX

Help with GNex Toolkit 7.6

Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.

AdelaisAer said:
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
Click to expand...
Click to collapse
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058

gpfnzl said:
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Oh. Sorry about that. Well, my main question is how to back user data up using the toolkit. I see options for applications and nandroid and stuff, but I don't see userdata such as contacts, sync accounts, etc. The most important stuff.
That's my main concern first and foremost. Also, I'm checking the guide right now; thanks.

I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.

gpfnzl said:
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
Click to expand...
Click to collapse
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.

AdelaisAer said:
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
Click to expand...
Click to collapse
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.

gpfnzl said:
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
Click to expand...
Click to collapse
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...

AdelaisAer said:
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
Click to expand...
Click to collapse
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
back your sd card up to PC, from memory i think the unlock part wipes your phone

gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png

I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app

ttahatt said:
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh. Derp. Well, I edited my post before yours, and I saw it has two images in it (one of them is radio) and a zip file. So yeah, I guess that contributed a lot to my confusion.
Also, I think my phone is still locked. I have done literally nothing to it yet.
Also, I want to flash it because it's currently in a Rogers/Samsung-type OS, where updates aren't pushed because it takes them months to get the A-Okay, for whatever reason. I want to flash it to the Google-line so I can get regular updates without waiting. :S

AdelaisAer said:
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
Click to expand...
Click to collapse
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Plug your phone in to pc....reboot your phone into fastboot (vol+/vol- and power) see if drivers install (should see bottom right hand side of computer)

gpfnzl said:
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Click to expand...
Click to collapse
My goal is to back my contacts and app data up, and then flash my phone with the new factory os that I got from Google Developer. :S But this whole guide is ajfkjsdkjfksjfkwejfkjsdkjfakw. Also, sorry for ranting. >___<;
See, if Samsung had just pushed updates to Canadian Android phones in the first place like normal people, I wouldn't be here. But instead, they hold onto updates until they (and Rogers) can stamp their names all over it and then takes a few more months just to approve it a second time, for whatever reason. :S
Instead, I have to come here, try to do this whole thing, and then install that factory Google-line OS so I can get regular updates.
Go look in the Rogers community forums - nothing but threads complaining about it. I'm one of very few who actually came to a forum like this.

OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Alright, will do.
Also, sorry if my replies get a bit slow now - eating.
EDIT: Ugh, this is getting reaaly confusing now. o-o; Especially the part where you make a backup of the phone build. @[email protected];

When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.

gpfnzl said:
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
Click to expand...
Click to collapse
Alright. Thank you. :3
So far, I synced my contacts, browser, etc. up with my Google+ account, so that's backed up, and I can go into fastboot no problem and have the toolkit detect it.
I just wanna make sure that there's nothing else that needs backing up (if there is, then what do I backup, and how?), and then just flash my phone with the new 4.1.1, and be done.
Also, thank you so much for actually putting up with me. A lot of people would normally be rather mean/hateful towards new-comers like me, so thank you.
EDIT: Why must this be so complicated... @[email protected] Curse you, Samsung.

Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.

gpfnzl said:
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
Click to expand...
Click to collapse
Er, how do? o-o;

Plug your phone into your PC
open *my computer* select the *galaxy nexus*, select *internal storage* and copy every thing to your computer.
unlock your lock screen on the phone or your computer wont see the internal storage

[GUIDE][All-In-One]LG Optimus Me P350

So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide​
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit

great guide good job

Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!

to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy

antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...

Updated adding unyaffsmbn tool... Thanks antdking!

Added Volume tweak for speaker to sound harder.

Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me

dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:

Guys We have got Official Support From XDA Please Move This Thread To Our Device Section

Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183

Great Guide Man! Thanks a lot.