Database Info

[UTIL] Full Auto A2SD - A2VD

Apps 2 Virtual Disk 0.53b
For those of you that are wondering "What is this guy smoking?" (which I assume is all of you), this is an automatically re-sizing virtual apps 2 SD ext3 partition. It is stored as an image file on your existing Fat32 partition.
I have done my best to make this as idiot proof and bug free as possible but I always appreciate constructive criticism. Please be kind, I haven't had access to a computer while writing this so it was written entirely on my G1. Therefore I expect that it will have a few bugs.
This barrows very heavily from Cyanogen's work so please thank him for making this possible.
Installing
To install the utility just download the file on your phone, open your terminal emulator and run:
Code:
su
sh /sdcard/download/a2vd-0.53b.zip
It does the rest.
Please note, this is NOT a zip file! It is a shell script. XDA won't let you post any file this big unless it's a zip file. (Can we get an Admin on this?) Good thing linux doesn't give a crap about file extensions.
Once you reboot your phone the utility will create the virtual partition, move over your apps, then re-size the partition to have 15 MB of free space. Please note, it will reboot 3 - 4 times during the first boot.
This should run on any rom that executes /system/bin/a2sd during boot.
It has been confirmed to work on Cyanogen 3.5.2 and higher.
Automatic Resizing
The partition will automatically re-size so you don't have to guess how big you need to make it. Now you can take a bite out of crime, in stead of your Fat32 partition. ;-)
If you run low on space just reboot your phone. If the free space on your virtual partition is less than 10 MB or more than 20 MB it will be re-sized to have 15 MB of free space. Please ignore the fact that free space may be listed as 13 or 14 MB, as far as I can tell this is an issue with the OS, the readout becomes more accurate as the partition gets bigger.
Disabling the Partition
If you wish to boot up with the Apps 2 Virtual Disk partition disabled simply open up your terminal emulator and run:
Code:
su
a2sdoff
You can also remove the SD card while the phone is off.
This is useful if you need to transfer files over USB cable.
Automatic backup
If you boot with the partition disabled the utility will backup some system settings so your apps and widgets will all still work when you re-enable the partition. It will also maintain a separate launcher profile for when you boot with the partition disabled. Now you don't have to stare at a desktop full of broken icons every time you need to transfer files to your computer.
Upgrading to a New Rom
Transitioning to a new rom can break some of your apps and widgets. To prevent this follow this procedure:
1. Place your new update.zip file on the root of your SD card.
2. Open terminal emulator and run:
Code:
su
a2sdoff -u
This will reboot your phone, prepare the backups, and take you to recovery.
3. Flash your new rom. (If you exit recovery without flashing you must re-run "a2sdoff -u" before attempting another flash)
4. Boot up your new rom, open terminal emulator and re-install Apps2VD.
Okay, you can start downloading now.
Thank you for your support and enjoy!
As a side note, If you install this on a phone that already has a traditional Apps2SD partition it will NOT copy over your apps. I'm working on it but until then you'll have to either just deal with it or copy them you self.
Edit: Download has been removed due to security concerns. Will re-upload when solved.

Sweet !....so basically it allows app2sd without an ext partition ? so just a fat32 partition is gud enough right ?

this is really intriguing, but i think i'm gonna hold off until some brave souls try it out with some feedback

Daneshm90 said:
Sweet !....so basically it allows app2sd without an ext partition ? so just a fat32 partition is gud enough right ?
Click to expand...
Click to collapse
Exactly! In fact, it requires nothing more than downloading and typing in one command.

narcopolypse said:
Exactly! In fact, it requires nothing more than downloading and typing in one command.
Click to expand...
Click to collapse
Aight im nandroid'd...n ready to test lol...will post results

So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?

miketaylor00 said:
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
Click to expand...
Click to collapse
Didnt work on xRom....kept bootloopin the first bootscreen

grandomegabosses said:
this is really intriguing, but i think i'm gonna hold off until some brave souls try it out with some feedback
Click to expand...
Click to collapse
I've been running this build for 4 day and previous alpha builds for over a month.
So have all of my friends.

miketaylor00 said:
So what is the plus side of using this? Is this just a tool for people who can't or don't have an ext partition? Do you know how it compares performance wise?
Click to expand...
Click to collapse
Performance is identical. The primary reason I built this is to have an automatically re-sizing apps partition. And the ability to boot disabled without breaking all of my widgets.

narcopolypse said:
I've been running this build for 4 day and previous alpha builds for over a month.
So have all of my friends.
Click to expand...
Click to collapse
hmmm i might try it later tonight or maybe tomorrow. after reading some more, i've gotten a little bit more confidence.

narcopolypse said:
Performance is identical. The primary reason I built this is to have an automatically re-sizing apps partition. And the ability to boot disabled without breaking all of my widgets.
Click to expand...
Click to collapse
It seems suprising to me that an image file on a FAT32 partition would perform the exact same way as an ext partition. I guess I will have to find out for myself
If this really does work and perform well, this could be google's solution to allow non rooted phones the ability to free up memory on their phone.
Either way, thanks for taking the time to do this.

Daneshm90 said:
Didnt work on xRom....kept bootloopin the first bootscreen
Click to expand...
Click to collapse
Yes, it will. And it would probably have a similar problem on later Cyanogen builds. You will have to modify the a2sd file to tell it not to automatically create apps2sd.

Daneshm90 said:
Didnt work on xRom....kept bootloopin the first bootscreen
Click to expand...
Click to collapse
It is supposed to reboot 3 - 4 times during the first boot.

this is really interesting, thank you for this. earlier today i made a modified a2sd script that makes the a2sd look for dev/block/mmcblk0p4 (fourth partition) and since there is none cyanogen's apps2sd will not be created. also in the file is a modified userinit.sh and user.conf that point to dev/block/mmcblk0p2 instead of 0p3 so that if you wanted to use this and only have a fat32 partition and linux-swap partition you could still get the benefits of it. saw this thread and thought this would be a place where these files could be used.
edit: was just thinking, does this overwrite the a2sd script? either way the modded userinit.sh and user.conf can still help.

david1171 said:
this is really interesting, thank you for this. earlier today i made a modified a2sd script that makes the a2sd look for dev/block/mmcblk0p4 (fourth partition) and since there is none cyanogen's apps2sd will not be created. also in the file is a modified userinit.sh and user.conf that point to dev/block/mmcblk0p2 instead of 0p3 so that if you wanted to use this and only have a fat32 partition and linux-swap partition you could still get the benefits of it. saw this thread and thought this would be a place where these files could be used.
edit: was just thinking, does this overwrite the a2sd script? either way the modded userinit.sh and user.conf can still help.
Click to expand...
Click to collapse
Yes this does replace /system/bin/a2sd and it stops checking for 0p2. It is based entirely off Cyanogen's a2sd that is used in every new rom out there and should be compatible with all of them.
Has anyone tested this yet? Which roms does it work on?

How does this work with mounting your phone on your computer? Like when you want to put music on. Can you do it the same way or do you have to shut your phone down and use a SDcard reader? Because I thought the was the main reason for not using fat32 for A2SD.

miketaylor00 said:
It seems suprising to me that an image file on a FAT32 partition would perform the exact same way as an ext partition. I guess I will have to find out for myself
If this really does work and perform well, this could be google's solution to allow non rooted phones the ability to free up memory on their phone.
Either way, thanks for taking the time to do this.
Click to expand...
Click to collapse
probably the wouldn't use it as you should be able to extract files from the img file

narcopolypse said:
It is supposed to reboot 3 - 4 times during the first boot.
Click to expand...
Click to collapse
Lol, no i tried again rebooted like 20 times so i gave up n nandroid'd.

speoples20 said:
How does this work with mounting your phone on your computer? Like when you want to put music on. Can you do it the same way or do you have to shut your phone down and use a SDcard reader? Because I thought the was the main reason for not using fat32 for A2SD.
Click to expand...
Click to collapse
That would be my concern as well. I don't see any way around this, though I'm not a dev by any means.

alritewhadeva said:
probably the wouldn't use it as you should be able to extract files from the img file
Click to expand...
Click to collapse
I'm sure they could make the img file only accesible by the sytem.

[RECOVERY]CWM-Based Recovery 5.0.2.8 For P999(Internal & External SD)

The image was provided by Mr Rusty over on the P990 thread and i asked him if we can have an update..well he gladly helped out so don't forget to thank Mr Rusty over on his Thread..
I repacked and added a script that you will just run in order to flash this CWM version..(Thanks to Russ for the script)
From his Thread:
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Click to expand...
Click to collapse
BIG Credits goes to Koush as well for his great work for innovating the CWM..
Get it Here: CWM 5.0.2.8 For P999 or from Here
Instructions on HOW to use/WHAT to do:(For Windows)
- Once you have downloaded the Package from the link Above..extract it to a Folder..
- Inside the folder all you have to do is look for the flash-recovery_xp.bat file..
- now turn your G2x OFF..
- remove the BATTERY and make sure your G2x is not connected to the PC via USB
- Press the VOLUME DOWN button together with the VOLUME UP..
- now CONNECT the USB Cable..
- If by all means Windows prompts for a new DEVICE you have to install the APX drivers from here(extract the package and manually install from this source)..
- Else if windows does not prompt OR you are already done installing the APX drivers you can now proceed on Running the flash-recovery_xp.bat by double clicking it..
- Choose 1 and Then press Enter..Wait for a few seconds till it prompts you that the FLASH was successful..IMHO you ought to wait another 5 more seconds after the prompt for not to have issues..
- After that Reboot into CWM by Pressing Power Button together with VOLUME DOWN til you see the LG Logo with waves..upon seeing that now release the buttons and wait for the CWM menu..
For Linux/Ubuntu Users:
- Download the Package
- Extract the folder somewhere
- Now turn your Phone OFF and DO NOT plug the USB cable yet..
- Now while Phone is OFF press VOLUME UP and DOWN together and now PLUG the USB cable in..keep them held together throughout the process..
- Run the Terminal and locate the Directory on where the Files are located..
- Type the ff:
Code:
chmod +x flash-recovery.sh
./flash-recovery.sh
- Once DONE you can now reboot..
FAQ:
Q: I am getting NVflash errors?
A: You might be on a BAD Cable or either way upon installing the drivers do a reboot..also DO THIS ON WINDOWS XP..on Windows 7 there are circumstances that the device is not recognized properly..also make SURE your unit is a P999 or P999DW(my unit is P999DW and touch WORKS!!) and not P990 or SU660..
Q: My device is not Recognized?
A: You have to download the APX drivers from one of the instructions above
Changelog: Github Source
Thanks and also vote for the page..

Seems the Chinese are on to this files too..lolz..

Thank you!! It flashed perfectly, no issues here.
Troy.

thegreenfamily04 said:
Thank you!! It flashed perfectly, no issues here.
Troy.
Click to expand...
Click to collapse
Glad it worked??

So internal and external mounting are all fine with this one?
Sent from my LG-P999 using xda premium

Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium

Just flashed it with no problems , when are we getting the touch CWM? Now that will look sexy

thy for your work. coming from ClockworkMod 5.0.2.0 what are the differences / improvements? could someone explain please?
thanks in advance

Just an update: I flashed a MIUI rom (Look in my sig) used the "Nullifier 2.0" (Double wipe) and flashed the current Trinity Kernel all with no issues
Phone is running GREAT now! Thank you once again
Troy.

Волк said:
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.

Im getting a nvflash error when trying to install the new clockwork.
It says check apx driver and usb cable. The drivers are already installed so Im thinking its the usb cable, but not sure.

MWBehr said:
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Click to expand...
Click to collapse
the recovery's on a different partition, might make it a pain in the ass to access the touch drivers...
or he might just like the o2x more (everyone likes those Europeans more than us anymore)

Touch Recovery
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.

mustangtim49 said:
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
Click to expand...
Click to collapse
It's all in the ram disk. Just swap out the vold.fstab in the ram disk. Recovery images are simply boot.imgs.

Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.

Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
http://db.tt/rEpbpRfA here you go. Really interested on what you can do with it
Sent from my LG-P999 using Tapatalk

Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
that might work. Id try it out myself if i didn't f up my Linux install...
Nvidia graphics got the best of me there too
Sent from my LG-P999 using Tapatalk

Works as advertised! Thanks!

works great! thanks!

So, my idea worked? I'm not at home and since I'm a collision tech by trade, my boss don't like me playing with my phone. Volk, if you read this pm me and fill me in if you can. Thanks brother.
[email protected]

[TOOL] G2X Cleanup Batch *** WARNING *** WILL FORMAT INTERNAL SD

If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.

was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.

The zip file seems to be corrupt. Could you re-upload plz

worked great on my end, no problems.

khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .

wow this method really blaze hellfire much thanks to your( you) & (rom dev)

Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.

so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA

mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.

MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .

thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed

So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA

mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid

dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA

Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium

It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.

[TUT]Get whirleyes BMM 0.3.2 working on our a2 [OUTDATED]

THIS TO INFORM YOU THAT NONE OF THE STEPS ARE REQUIRED FOR 0.3.4. I AM JUST KEEPING THIS FOR INFORMATION AND THE WARNINGS AND OTHER POSSIBLE ISSUES YOU MIGHT FACE. AND AS A GENERAL DISCUSSION FOR BMM.
Hey everyone, whirleyes updated and released his amazing recovery.. It allows you to multiboot and has ton of more amazing tools..
Go here for original thread he posted in the razr forum.. http://forum.xda-developers.com/showthread.php?t=2005187
well, its tested and made only for razr, but theres a simple way to get it working on our Atrix 2.. here is how you can do it..
Before You Get Started, Here is an
IMPORTANT NOTE: DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED AND WARNED.
1) Download and install BMM from google play https://play.google.com/store/apps/details?id=com.projectlense.bootmenu.manager
2) Our phone does not have a partition for internal storage.. so we use the data partition for it.. To do so, just open a root browser like root explorer and navigate to /etc/bmm/conf
3) Open "recovery.fstab" with a text editor
4) The last line will be something like this
/int vfat /dev/block/mmcblk1p25
5) just change 'vfat' to 'auto' and 'mmcblk1p25' to 'userdata' (its the same though..)
so that it looks like this
/int auto /dev/block/userdata
and of course save it and close it..
6) Done.. you are good to go.. Happy Multi Booting..
Just some tips
On your first reboot, tap the android, go to settings-->System_2-->Partition setup and tap on ACTIVATE. This formats cdrom partition to ext2.
Now go back 2 two steps, and select any other system(3-6). choose Partition setup, tap on system.img, tap on Create, select the size, create it. go back and do the same with data.img and cache.img.
Once thats done, go back and select recovery, select switch system. choose your system that you created the images for, the colour will change, install any custom rom.. Enjoy!!
NOTE: BMM stores the images in internal memory(/int/clockworkmod/virtual/system_(num)). Since we dont have emmc partition and are using the data partition for /int, doing a factory reset will wipe it out and you will lose all your other roms.. So be carefull..
NOTE 2: USE ONLY SYSTEMS 3 TO 6 FOR CUSTOM ROMS.. SUSTEM 2 IS CDROM PARTITION.. YOU ACTIVATE IT ONCE AND DONE.. DONT TOUCH IT AGAIN.. ITS ONLY 12MB..
IMPORTANT NOTE: DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED.

We already know we can use bootmenu manager.
And, as i know, we don't have to do anything to run this app correctly.

brianmoyano said:
We already know we can use bootmenu manager.
And, as i know, we don't have to do anything to run this app correctly.
Click to expand...
Click to collapse
you are talking about the older version, i.e, 0.2.7. for that, you dont have to do anything.. this one is to run the latest version 0.3.2..
and using this, you can have not just two, but 4 systems + stock..

Ravikirancg said:
you are talking about the older version, i.e, 0.2.7. for that, you dont have to do anything.. this one is to run the latest version 0.3.2..
and using this, you can have not just two, but 4 systems + stock..
Click to expand...
Click to collapse
Oh, ok. Sorry then. I didn't know that.

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
Thanks for this! I can say that version 0.3.2 is an amazing improvement over 0.2.7
@everyone - go thank whirleyes for his awesome app!
edit: link in original post
@OP - can you confirm that it would be possible to actually install up to 4 roms at once on the atrix 2? What other partitions does Bootmenu utilize for this?

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
On which ROM did you try this? I guess it would be a bit different to get it working on the chinese jb leak as it does have internal storage enabled
Sent from my ME865 using xda premium

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
shardul1994 said:
On which ROM did you try this? I guess it would be a bit different to get it working on the chinese jb leak as it does have internal storage enabled
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
Tried on the jb itself.. The hktw rom emulates internal storage at /data/internal_sd its not a separate partition.. Tried using that.. But for some reason I couldn't get it.. Feel using data partition is better.. Btw, I am currently on the jb Wang posted..
Sent from my ME865 using Tapatalk 2

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
snowplow said:
Thanks for this! I can say that version 0.3.2 is an amazing improvement over 0.2.7
@everyone - go thank whirleyes for his awesome app!
edit: link in original post
@OP - can you confirm that it would be possible to actually install up to 4 roms at once on the atrix 2? What other partitions does Bootmenu utilize for this?
Click to expand...
Click to collapse
That depends on the amount of space you have left on /data. If are having a retail a2, flash the JB leak and you should get 6 GB for /data..
Sent from my ME865 using Tapatalk 2

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
Ravikirancg said:
Hey everyone, whirleyes updated and released his amazing recovery.. It allows you to multiboot and has ton of more amazing tools..
Go here for original thread he posted in the razr forum.. http://forum.xda-developers.com/showthread.php?t=2005187
well, its tested and made only for razr, but theres a simple way to get it working on our Atrix 2.. here is how you can do it..
1) Download and install BMM from google play https://play.google.com/store/apps/details?id=com.projectlense.bootmenu.manager
2) Our phone does not have a partition for internal storage.. so we use the data partition for it.. To do so, just open a root browser like root explorer and navigate to /etc/bmm/conf
3) Open "recovery.fstab" with a text editor
4) The last line will be something like this
/int vfat /dev/block/mmcblk1p25
5) just change 'vfat' to 'auto' and 'mmcblk1p25' to 'userdata' (its the same though..)
so that it looks like this
/int auto /dev/block/userdata
and of course save it and close it..
6) Done.. you are good to go.. Happy Multi Booting..
Just some tips
On your first reboot, tap the android, go to settings-->System_2-->Partition setup and tap on ACTIVATE. This formats cdrom partition to ext2.
Now go back 2 two steps, and select any other system(3-6). choose Partition setup, tap on system.img, tap on Create, select the size, create it. go back and do the same with data.img and cache.img.
Once thats done, go back and select recovery, select switch system. choose your system that you created the images for, the colour will change, install any custom rom.. Enjoy!!
NOTE: BMM stores the images in internal memory(/int/clockworkmod/virtual/system_($num)). Since we dont have emmc partition and are using the data partition for /int, doing a factory reset will wipe it out and you will lose all your other roms.. So be carefull..
Click to expand...
Click to collapse
Hmm good one u stole my opportunity to post this
but bro what are u dual booting I am scratching my head since the custom rom I made myself from jb leak is all good but just does not identify apk files
Ahaha just hilarious problem please pm me if u can help
Sent from my ME865 using xda app-developers app

I don't see the bmm folder :?

Ravikirancg said:
4) The last line will be something like this
/int vfat /dev/block/mmcblk1p25
Click to expand...
Click to collapse
I'll try to automate this by determining devices type. (ro.product.board)
But still hard for me to give edison full support because some part is still hardcoded for spyder.
Just don't use firmware flashing function.
Flashing boot.img theoretically should be OK. Don't play with CID ~
I'm not responsible if anything goes wrong, I have no idea how it will behave on edison.

whirleyes said:
I'll try to automate this by determining devices type. (ro.product.board)
But still hard for me to give edison full support because some part is still hardcoded for spyder.
Just don't use firmware flashing function.
Flashing boot.img theoretically should be OK. Don't play with CID ~
I'm not responsible if anything goes wrong, I have no idea how it will behave on edison.
Click to expand...
Click to collapse
WHOA!! So I just escaped a possible brick!
I was on the official JB leak and was experimenting with kexec(with the files meant for ICS).. and that used to mess up my CID.. luckily, I had bmm installed and had a backup of my CID(not through bmm)..
well, bmm automagically found out that my CID was messed, and bypassed it.. later I flashed my CID and luckily, everything was fine..
So, in short,
1) Bypassing CID works.. :good:
2) Flashing CID works.. :good:
maybe you already know this, but just wanted to say, using kexec on official JB update might mess up CID.. I guess this is moto's work..
so you guys with razrs be careful..
glad to see you around..

brianmoyano said:
I don't see the bmm folder :?
Click to expand...
Click to collapse
It will be in /system/etc/

Ravikirancg said:
It will be in /system/etc/
Click to expand...
Click to collapse
It isn't showing there for me either - trying a reboot and maybe a reinstall of the program.
EDIT - Well, that was silly - after installing from the Play Store you need to click on the icon and install it a second time? Huh.
So, I have a question - when we're creating the partitions for system, data and cache how large would you recommend we make them?

Ravikirancg said:
WHOA!! So I just escaped a possible brick!
I was on the official JB leak and was experimenting with kexec(with the files meant for ICS).. and that used to mess up my CID.. luckily, I had bmm installed and had a backup of my CID(not through bmm)..
well, bmm automagically found out that my CID was messed, and bypassed it.. later I flashed my CID and luckily, everything was fine..
So, in short,
1) Bypassing CID works.. :good:
2) Flashing CID works.. :good:
maybe you already know this, but just wanted to say, using kexec on official JB update might mess up CID.. I guess this is moto's work..
so you guys with razrs be careful..
glad to see you around..
Click to expand...
Click to collapse
There are a lot of issues with kexec and this phone, and why we never did any "real" work with it, once it was fully developed. There are other issues with kexec and this phone, but it really is not something I would put anymore time into, with this phone. Motorola has really done some very nasty things to this phone and continuing the evil with Atrix HD and making that phone even more locked down than this one.
There is really no reason to have a kexec kernel other than to say you made one. We have a form of OC and we have custom opensource roms, so kexec and kernels really are not needed on this phone.
P.S. kexec on this phone can be very dangerous as you will load the "stock" moto kernel during the bootloader check, then once booted kexec will unload that "stock" kernel and load the new one, but I warn you that if the ROM is not built to handle the kernel disastrous consequences can and will occur.

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
Tried installing BMM and I got this... also can't find /etc/bmm/conf with root explorer.
Sent from my MB865 using xda app-developers app

fran7382 said:
Tried installing BMM and I got this... also can't find /etc/bmm/conf with root explorer.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Don't reboot your phone. Because you're going to run into bootloop.

Ravikirancg said:
Hey everyone, whirleyes updated and released his amazing recovery.. It allows you to multiboot and has ton of more amazing tools..
Go here for original thread he posted in the razr forum.. http://forum.xda-developers.com/showthread.php?t=2005187
well, its tested and made only for razr, but theres a simple way to get it working on our Atrix 2.. here is how you can do it..
1) Download and install BMM from google play https://play.google.com/store/apps/details?id=com.projectlense.bootmenu.manager
2) Our phone does not have a partition for internal storage.. so we use the data partition for it.. To do so, just open a root browser like root explorer and navigate to /etc/bmm/conf
3) Open "recovery.fstab" with a text editor
4) The last line will be something like this
/int vfat /dev/block/mmcblk1p25
5) just change 'vfat' to 'auto' and 'mmcblk1p25' to 'userdata' (its the same though..)
so that it looks like this
/int auto /dev/block/userdata
and of course save it and close it..
6) Done.. you are good to go.. Happy Multi Booting..
Just some tips
On your first reboot, tap the android, go to settings-->System_2-->Partition setup and tap on ACTIVATE. This formats cdrom partition to ext2.
Now go back 2 two steps, and select any other system(3-6). choose Partition setup, tap on system.img, tap on Create, select the size, create it. go back and do the same with data.img and cache.img.
Once thats done, go back and select recovery, select switch system. choose your system that you created the images for, the colour will change, install any custom rom.. Enjoy!!
NOTE: BMM stores the images in internal memory(/int/clockworkmod/virtual/system_(num)). Since we dont have emmc partition and are using the data partition for /int, doing a factory reset will wipe it out and you will lose all your other roms.. So be carefull..
NOTE 2: USE ONLY SYSTEMS 3 TO 6 FOR CUSTOM ROMS.. SUSTEM 2 IS CDROM PARTITION.. YOU ACTIVATE IT ONCE AND DONE.. DONT TOUCH IT AGAIN.. ITS ONLY 12MB..
Click to expand...
Click to collapse
Hi Ravikirancg,
I have a question with regards to your CM10.1 and the patch. I have an A2 AT&T running BMM 0.3.2 and SCV7 1st partition and ICS stock in 2nd partition. I am planning to flash CM10.1 in 2nd partition, my question is do I have to wipe system, cache and data or just the cache and data.
My apologies for posting this question here as I dont have access to post in dev forum .
Also I do not want to brick another A2

Re: [TUT]Get whirleyes BMM 0.3.2 working on our a2
brianmoyano said:
Don't reboot your phone. Because you're going to run into bootloop.
Click to expand...
Click to collapse
I can install it from the play store but when I open the app and run the installer I get that error and it prompts me to uninstall the app.

fran7382 said:
I can install it from the play store but when I open the app and run the installer I get that error and it prompts me to uninstall the app.
Click to expand...
Click to collapse
Yes, i was in the same situation. And has to reflash again the Jellybean fxz because i don't knew how to solve it.

[DEV]Wkparks bootloader improvements

First, I don't offer here anything cause I still wasn't able to compile a working u-boot.
Things I could add in theory would be:
Boot scripts (we could add a script on the sd that is run before kernel is loaded into ram)
More boot menu options like download mode or a second boot partitions for dual boot
Disable the mmc: booti line which is shown when voting unsigned images
Another splash image instead of the silver lg logo
Another image instead of the download mode image
...
Tell me other ideas
It would be great if somebody would try to compile the wkparks boot loader without any change and tell me if it boots.
@mods if this thread isn't at right section here just move it
Sent from my LG-P920 using xda app-developers app

i'm not developer yet but I think duel boot options will be great :thumbup:
Sent from my LG-P920 using xda app-developers app

If you can fix the rebooting issue, everything else will be a good addition.

It would be great if you can fix the battery charging when the phone is switched off.

Good idea, the last version of bootloader has too many errors.
Problems for example:
Problems when you charge and reboot the phone, and it isnt power on.
Problems with power off charge.

It would be great if the shutdown can be fixed.
Having dual/multi-boot directly from the bootloader would be wonderful if we can boot any partitions/boot image on the external SD card!

Berni, did you ask wkpark for help?

Is it possible to modify the u-boot (which loads after x-loader and before kernel) by adding two options , each one for a separated kernel ?? And of course each kernel has its own partitions (system , data and cache ) .
We need a good C programmer to handle this , how are you with C ? (I only can read , but didn't try to write code ) .
The good thing is that O3D is unbrickable , so you can test as much as you can .
By the way ,,
I have Galaxy Nexus , and it has one partition for data and user data(Videos , photos ..etc) (there are /data , /data/media) . and want to dual boot using the internal storage (cause Galaxy nexus doesn't have SD Card) .
So is it possible to partition it ??
P.S :
This may help you :-
http://forum.xda-developers.com/showthread.php?t=2204705
Sent from my Galaxy Nexus using xda app-developers app

$Parker said:
Is it possible to modify the u-boot (which loads after x-loader and before kernel) by adding two options , each one for a separated kernel ?? And of course each kernel has its own partitions (system , data and cache ) .
We need a good C programmer to handle this , how are you with C ? (I only can read , but didn't try to write code ) .
The good thing is that O3D is unbrickable , so you can test as much as you can .
By the way ,,
I have Galaxy Nexus , and it has one partition for data and user data(Videos , photos ..etc) (there are /data , /data/media) . and want to dual boot using the internal storage (cause Galaxy nexus doesn't have SD Card) .
So is it possible to partition it ??
P.S :
This may help you :-
http://forum.xda-developers.com/showthread.php?t=2204705
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Adding a second boot partition is pretty easy
Sent from my LG-P920 using xda app-developers app

berni987654321 said:
Adding a second boot partition is pretty easy
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
If I used parted and mkpartfs I can partition it ? No special thing for data/media ??
And of course editing init.rc .
I just need to make three partition (system , data , cache) , if I follow your dual boot method will it work ?? (And of course another kernel) .
Thanks
Sent from my Galaxy Nexus using xda app-developers app

$Parker said:
If I used parted and mkpartfs I can partition it ? No special thing for data/media ??
And of course editing init.rc .
I just need to make three partition (system , data , cache) , if I follow your dual boot method will it work ?? (And of course another kernel) .
Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
In theory yes
Sent from my LG-P920 using xda app-developers app

adri_360 said:
Good idea, the last version of bootloader has too many errors.
Problems for example:
Problems when you charge and reboot the phone, and it isnt power on.
Problems with power off charge.
Click to expand...
Click to collapse
I too would like if the problem was solved when you charge and reboot the phone, and it isnt power on and problems with power off charge.
I have contacted several times wkpark, but I have never bothered to reply.
I wonder: is it really so difficult to fix this problem? you could not copy part of the u-boot.img ics30a stock and put it in the u-boot.img of wkpark?

because no one answers ? : Confuso: