Develop Bugs

[Q] We Can Now Dual Boot With Boot Manager App!!!

Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Update: I'm now running 2 AOSP roms Kushdeck's 1.3b2(main rom) and SalvageMod 1.4 and a Sense rom SynergyRls1 and haven't noticed any major issues. Gps works on each rom as well as 4g. Synergy does have some lag and for this reason took some patience and a little longer to initially set up but it works decently for running off of an sdcard. On a side note I've heard claims that Synergy does have some lag issues running normally.
I plan on ordering a better sdcard with a faster class rating such as class 4 or 6 so hopefully this will decrease lag but overall I'm very impressed with Boot Manager. If nothing else this gives you a chance to test drive roms without having to go through the whole process of replacing your daily driver.
PLEASE READ: I've reached out to one of the developers of this app who's from XDA and asked for his help in answering the problems some of you are having. I wish I could help more especially since this a paid app and you guys deserve to have an app that work. Below are the links to email support through the app website as well as the one of the developers Conap who's from XDA. Maybe if they receive enough emails they will shoot over to this thread to help.
Sorry I can't help more. All I can do is verify that it's working on my Evo but don't have enough advanced skills to do a lot more.
App Support Address: [email protected]
Conap Contact (One of the Devs from XDA): http://forum.xda-developers.com/member.php?u=2468293 (I just pm'd him)

aerajan said:
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Click to expand...
Click to collapse
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.

mattykinsx said:
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
Click to expand...
Click to collapse
Yea that's a good point. I'm running Kushdeck's 1.3b2 gb aosp as my main rom and didn't even think of that.

https://market.android.com/details?id=com.drx2.bootmanager

Alright, this looks really great. Love the idea. Just wondering for those who have it, since there are different kernels associated with each ROM (going from CM to Synergy) would you have to go back in and wipe battery stats? Also, would vipermod carry from ROM to ROM or would you need to set it up for every ROM?
How much room on the SD card would you need to boot 5 ROMS?
edit: quite a bit of room, have over a gig on sd card and can't load synergy. Have to do some cleaning later. Wish it could import nands, that would rock.
edit 2: cleared room, installed synergy on slot 1, rebooted, hanging on evo 4g screen..... bah

Im trying this now. I have Mikg as my phone rom and installing miui as a test. Will report back when I do some testing on kernals and battery life.

I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App

i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.

yeah crazy... stuck in splash screen sooooo yay no bueno thus far...

locoboi187 said:
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
alaman68 said:
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
Click to expand...
Click to collapse
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
jbrawley1 said:
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
Click to expand...
Click to collapse
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.

It takes a while. Since it's booting from your sdcard it's not quite as fast the first time as when you normally flash a rom. Mine stayed on splash screen for a little while to the first time I rebooted. Also try another rom just to see if that works for you.

aerajan said:
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
Click to expand...
Click to collapse
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App

Omfg will download and test this out ASAP and report back results!!
Sent from my PC36100

locoboi187 said:
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Ext 2 because it's compatible with more roms.

aerajan said:
Ext 2 because it's compatible with more roms.
Click to expand...
Click to collapse
still no go, error building the boot
Sent from my PC36100 using XDA Premium App

Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Also if you go back to OP I've posted links to email support or one of the devs who's from XDA. I pm'd him personally asking if he's willing to shoot over here and try to help. If you get the time send him a PM. Maybe if enough people from here contact him he will help.

aerajan said:
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Click to expand...
Click to collapse
Thanks
Sent from my PC36100 using XDA Premium App

It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).

pottyvick said:
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
Click to expand...
Click to collapse
I wonder what steps the other guy took to get it working on his evo
Sent from my PC36100 using XDA Premium App

well... ive gotten this to work with Miui as main rom, and Synergy Kingdom port 7/23 but confirmed i dont believe that synergy rls 1+God Mode ive tried tons this wont work...
pretty cool you can switch between aosp and sense pretty easily i like this lots hope in the future it becomes more stable and compatible!

[Q] bootloader bypass?

I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097

masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.

how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?

RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App

crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community

littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it

crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.

Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium

Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.

eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium

eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App

crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d

If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/

Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.

crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.

Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.

Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....

mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.

Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.

mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..

Touch Recovery

team win touch recovery ported to defy finally! you can finally save your physical buttons!! thanks to epsylon for getting in contact with them
I tested it on bravo, and it works great! I flashed the zip in recovery and rebooted into recovery.
http://www.teamw.in/project/twrp2/91
*not finding my nandroids though - probably because they're cwm backups lol
keep yourself posted by looking at the thread: http://forum.xda-developers.com/showthread.php?t=1585927

thanks
syllogyking said:
team win touch recovery ported to defy finally! you can finally save your physical buttons!! thanks to epsylon for getting in contact with them
I tested it on bravo, and it works great! I flashed the zip in recovery and rebooted into recovery.
http://www.teamw.in/project/twrp2/91
*not finding my nandroids though, but hopefully that'll be fixed soon.
keep yourself posted by looking at the thread: http://forum.xda-developers.com/showthread.php?t=1585927
Click to expand...
Click to collapse
you can raise it for the motorola device bravo...

syllogyking said:
team win touch recovery ported to defy finally! you can finally save your physical buttons!! thanks to epsylon for getting in contact with them
I tested it on bravo, and it works great! I flashed the zip in recovery and rebooted into recovery.
http://www.teamw.in/project/twrp2/91
*not finding my nandroids though - probably because they're cwm backups lol
keep yourself posted by looking at the thread: http://forum.xda-developers.com/showthread.php?t=1585927
Click to expand...
Click to collapse
Excellent, thanks for sharing it, works perfect, but why does it have to be so ugly??
No more touch to physical buttons, we have to press them to much to do some things, some times I thougt they were going to break using them all the time.
I hope for next release to see a better UI at least!!

It works great. Nandroids with this are in new location and format. Use custom recovery to use old Nandroids. The major problem is Wipe Data/Factory Reset is it also formats sd-ext partition. I wiped 10 gigs of music last night....dammit. Just a warning if you prefer data on sd-ext for safety.
I don't like to use fat filesystems if I don't have to. Win 7 has corrupted my sdcard a few times now.
I really like the multi zip flashing. If you flash 2-4 zips an install, you'll love it too.

This was the only recovery option for the kindle fire for a long time, so I can also share that there are theme options to help a little with the "ugliness", just check the link below.
http://forum.xda-developers.com/showthread.php?t=1489088
Sent from my Kindle Fire using xda premium

feistygoat10 said:
This was the only recovery option for the kindle fire for a long time, so I can also share that there are theme options to help a little with the "ugliness", just check the link below.
http://forum.xda-developers.com/showthread.php?t=1489088
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Thanks God there are themes, I saw that option in the recovery but I didnt know what to do, this is the most ugliest application ever seen made !!
At least is something we need!

Heads up....The Kindle Fire themes aren't designed and formatted properly for our screen size, you'll be missing important selections if you install one. It sucks cause that ICS Blue one looks awesome.
It shouldn't be too hard to merge into the default theme if anyone wants too. Mainly just replacing the stock images with the theme's images and editing the ui.xml for proper font color. Maybe more, but I haven't looked too deep at Touch Recovery Themeing yet. Now that we have Bravo ICS, I have other projects I'd rather do...like start MIUI V4 from scratch....its gonna be a pain in the ass since I can only reference from other devices.
Has anybody tried Touch Recovery with Multiboot yet? Honestly, I'm a bit nervous to try since I'm not sure if the two are compatible.

skeevy420 said:
Heads up....The Kindle Fire themes aren't designed and formatted properly for our screen size, you'll be missing important selections if you install one. It sucks cause that ICS Blue one looks awesome.
It shouldn't be too hard to merge into the default theme if anyone wants too. Mainly just replacing the stock images with the theme's images and editing the ui.xml for proper font color. Maybe more, but I haven't looked too deep at Touch Recovery Themeing yet. Now that we have Bravo ICS, I have other projects I'd rather do...like start MIUI V4 from scratch....its gonna be a pain in the ass since I can only reference from other devices.
Has anybody tried Touch Recovery with Multiboot yet? Honestly, I'm a bit nervous to try since I'm not sure if the two are compatible.
Click to expand...
Click to collapse
I alredy tried, I dont see some buttons, I knew this could happen because I saw it looked very different!

I can't seem to get this installed on my Bravo. I'm kind of confused of what steps I need to take. I had cwm recovery on there from when Bandroidx was around. I understand now, that his is efforts can't help me here. I tried to use cwm to install twrp but now it seems as though I've lost any custom recovery. Any suggestions or a direction to head?
Thanks guys.

dynojunkee said:
I can't seem to get this installed on my Bravo. I'm kind of confused of what steps I need to take. I had cwm recovery on there from when Bandroidx was around. I understand now, that his is efforts can't help me here. I tried to use cwm to install twrp but now it seems as though I've lost any custom recovery. Any suggestions or a direction to head?
Thanks guys.
Click to expand...
Click to collapse
download the flashable .zip file from this site: http://www.teamw.in/project/twrp2/91
put it on your sd card.
hopefully you're actually using Clockwork Mod recovery and not bandroidx's Bootstrap recovery method - that's obsolete. When you get to CWM (reboot phone, when LED turns blue press the volume down button), go down to install zip from sd card, choose zip from sd card, find the TWRP file, and select yes to flash. no need to wipe afterwards, just reboot your phone. When LED turns blue again, and you press volume down button, you should enter TWRP recovery.
I don't know if it's still the case, but the last time I checked (first release) it was pretty buggy. I just stick with the tried and true CWM.

syllogyking said:
download the flashable .zip file from this site: http://www.teamw.in/project/twrp2/91
put it on your sd card.
hopefully you're actually using Clockwork Mod recovery and not bandroidx's Bootstrap recovery method - that's obsolete. When you get to CWM (reboot phone, when LED turns blue press the volume down button), go down to install zip from sd card, choose zip from sd card, find the TWRP file, and select yes to flash. no need to wipe afterwards, just reboot your phone. When LED turns blue again, and you press volume down button, you should enter TWRP recovery.
I don't know if it's still the case, but the last time I checked (first release) it was pretty buggy. I just stick with the tried and true CWM.
Click to expand...
Click to collapse
Thanks for your response. Well, I thought I was using cwm but now im doubting it because I followed bandroidx's thread so I must've used his method because there wasn't any other choice at the time.
So, if that is the case... then I need to flash a true cwmr? If so, where can I find instructions to that process? I've been trying to find it but everything says to flash through recovery but how if what I have is incorrect?
Thanks, major props to all of you.
Sent from my MB520 using XDA

Use the defy 2nd init app to flash the recovery on your phone. Search the bravo forum for the thread. I think josuearisty posted it in Bravo General. Yeah, it sounds like you were using bootstrap, which explains why you weren't able to flash.
Sent from my MB520 using Tapatalk 2

syllogyking said:
Use the defy 2nd init app to flash the recovery on your phone. Search the bravo forum for the thread. I think josuearisty posted it in Bravo General. Yeah, it sounds like you were using bootstrap, which explains why you weren't able to flash.
Sent from my MB520 using Tapatalk 2
Click to expand...
Click to collapse
+100 to that
Click here to go to 2nd-init Defy Thread
Download is in that thread's attachments.
I also tried out JetAudio (saw your post in Defy last night) and thought it was GREAT. Many audio options, FOLDER VIEW, clean layout. I didn't like the little 4x1 widget and the fact that I can't change folders easily (my 2 main reasons for using Mort Player), but the awesome effects make up for it.
No love from those Defy users -- Poweramp Fanboys

skeevy420 said:
+100 to that
Click here to go to 2nd-init Defy Thread
Download is in that thread's attachments.
I also tried out JetAudio (saw your post in Defy last night) and thought it was GREAT. Many audio options, FOLDER VIEW, clean layout. I didn't like the little 4x1 widget and the fact that I can't change folders easily (my 2 main reasons for using Mort Player), but the awesome effects make up for it.
No love from those Defy users -- Poweramp Fanboys
Click to expand...
Click to collapse
Thanks for the link!! So simple, lol. Major props and thanks for answering these n00b questions. Happy to see Bravo getting some love. So happy to be rocking ICS now.
I should be getting a new phone this weekend too so I'm up for testing anything on here and learning more than what I know now.
Thanks again!
Sent from my MB520 using XDA

skeevy420 said:
+100 to that
Click here to go to 2nd-init Defy Thread
Download is in that thread's attachments.
I also tried out JetAudio (saw your post in Defy last night) and thought it was GREAT. Many audio options, FOLDER VIEW, clean layout. I didn't like the little 4x1 widget and the fact that I can't change folders easily (my 2 main reasons for using Mort Player), but the awesome effects make up for it.
No love from those Defy users -- Poweramp Fanboys
Click to expand...
Click to collapse
Lol. It's always a subjective decision when it comes to music players. Jet just suits me and I've been using it on my pc for a while. Haven't tried Mort.
Sent from my MB520 using Tapatalk 2

syllogyking said:
Lol. It's always a subjective decision when it comes to music players. Jet just suits me and I've been using it on my pc for a while. Haven't tried Mort.
Sent from my MB520 using Tapatalk 2
Click to expand...
Click to collapse
True that. Currently trying out PowerAmp for the first time, clean interface and a decent trial period..... Probably gonna try PlayerPro as well for its DSP pack and video support.
My only real gripe with Jet is the 20 second limit on some of the features\effects. Should at least be a minute or two so you know if they're worth buying the full version for.
Mort's great if you have a ton of music already sorted in folders by Main Folder>Artist>Album>Track like all mine are (and you're too lazy to fix id3 tags). Especially handy if you download by the discography.... My only complaint with it is that the reverb effects don't work with the Bravo, but I don't use them (pc or phone or any music app ever). I'd like an ICS dark styled holo theme for it, but the ones it comes with are good enough and somewhat customizable.
Mort also has a PC\Mac version available, but I've never used it since I use Linux.
Mort Player Official Site if you're interested.
Hopefully Touch Recovery gets better with time. I'd use it full time, but the Wipe Data\Cache wipes sdext as well; and I use sdext for my music and files I don't want getting corrupted on fat32 -- worst choice of filesystem for sdcards imho -- we should at least be able to use the sdcard as ext2\3.... (At least some part of all this was about Touch Recovery)

[RECOVERY] Clockwork-Recovery-Standard-v6.0.1.5

This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager

Thanks dude!

Here is the touch version of 6.0.1.5 http://d-h.st/1Kk. I built this last night using the recovery builder found here http://builder.clockworkmod.com/ with the 6.0.1.0 version as a base.
EDIT/ I FORGOT TO MENTION. I AM NOT RESPONSIBLE FOR ANYTHING WORKING OR NOT WORKING WITH THIS RECOVERY. I ASSUME NO RESPONSIBILITY FOR BROKEN DEVICES. USE AT YOUR OWN RISK. THANK YOU

myepicyear said:
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Click to expand...
Click to collapse
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?

Yes it has that option
Sent from my Galaxy Nexus using xda premium

TransWarp said:
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Click to expand...
Click to collapse
Yes, this version includes both tar and dup (data blob) backup formats. Tar formatting was re-added in 6.0.1.2.
So you can have either quick, large backups; or slower, slimmer backups with this version.
There's also an interesting adb sideload option as well. Not useful for most casual users, however, the more adventurous users will have a purpose for it from time to time.

10characters

FrostyF7 said:
Thanks dude!
Click to expand...
Click to collapse
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:

myepicyear said:
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.

ezeuba said:
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
Click to expand...
Click to collapse
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick

myepicyear said:
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
Click to expand...
Click to collapse
Top notch response. Thanks...
---------- Post added at 05:30 AM ---------- Previous post was at 05:22 AM ----------
One question. How does the sideload thingy work? What's it all about?

Anytime

myepicyear said:
Anytime
Click to expand...
Click to collapse
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.

crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
The same way you installed twrp? Boot into fast boot mode and fastboot flash recovery name-of-recovery.img. Replace name of with the actual name of the image. Or you could download and install flash GUI and flash the image through the app.
Sent from my Galaxy Nexus

crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?

myepicyear said:
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
Click to expand...
Click to collapse
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app

crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Definitely try to learn fast boot man. The toolkits are cool, but a minor mistake can make using one a nightmare. If you learn fastboot, you will always be able to fix your device. Plus it is the proper and preferred method for flashing a recovery, radio, or bootloader. It is an invaluable tool for for flashing.
Sent from my Galaxy Nexus using Tapatalk 2

crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm happy to be able to help man.
If you want a quick fix until I have some time to more time to explain fastboot thoroughly, I can do that for the moment.
The toolkit that mkskip has put together for everyone is very handy. It is basically like having all the essential tools, like fastboot, installed for you in their most lean form, without needing the whole android SDK installed. It also gives you a logical interface to interact with all that stuff. The toolkit installs all these tools within a folder on the root of your C drive. If you go to the root of your C drive, you'll see that folder, which is called 'Galaxy Nexus Toolkit'(or something). If go inside that directory, there's a folder called put imgs to flash here. There are several ways to do things in the toolkit folders, but basically, this is one folder you can insert imgs in to fastboot flash them.
Let me know if you're with me so far. I'm going by my memory of all this stuff because I don't use toolkits or Windows anymore. I can guide you through this, and during the process, hopefully broaden your understanding of fastboot at the same time. I'll need you to do some searching of your own during the process, or it wont make any sense at all, but I can definetly guide you through.

There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".

063_XOBX said:
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
Click to expand...
Click to collapse
Dude, I'm not stupid. I'm trying to explain it in a way he is already familiar with.
Jesus.

[Solved] Files needed to fix phone (looking for "bootanimation" and others)

*******************************************************************************************************************************************************************************
SOLUTION FOUND, much thanks to @DocHoliday77
See here for "bootanimation", "bootsamsung", and "bootsamsungloop" files or bottom of this post.
I unziped and I copied "bootanimation" to /system/bin and changed the permissions, I only needed the "bootanimation" file, I had to change permissions to rwe-re-re, other combinations might work/be better. If someone needs to use the other two files, they go in /system/media
Again, credit to @DocHoliday77 for the files!
*******************************************************************************************************************************************************************************
Hey everyone,
So, I tried changing my boot animation, and now I don't have any (it's just a black screen with the original sound)
(I'm on Candian Telus, with 4.4.2)
Basically what I'm asking/looking for is someone to attach a couple files off there phone so I can replace the ones that were altered through this tutorial, and hopefully get a boot animation back.
I'm not 100% sure if I need all of these, or if I may need more, but I have a pretty good idea of what was likely altered:
/system/bin/bootanimation (the extension-less file, this is one that I'm positive that got altered)
/system/bin/samsungani (possibly just and additon fr tutorial, unsure if needed. Information on if others have it would be awesome)
Any information on my situation would be amazing!

Have you tried factory reset (you'll lose data this way)?
Can you flash your ROM again (data will be wiped though)?

OKAstro said:
Have you tried factory reset (you'll lose data this way)?
Can you flash your ROM again (data will be wiped though)?
Click to expand...
Click to collapse
No, I haven't tried either. I'm trying to avoid losing any data, if possible.
Also, I'm not sure if it will fix the problem since the files have been altered directly. (I'm not sure if it will just reset with the file it has now or not)
Any thoughts?

Factory resetting won't help since boot animation is on /system.
If you can't find them here you can always copy them from a stock rom.
Make sure the binary file is from the same build as your current rom. It might not matter, but it just might.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Factory resetting won't help since boot animation is on /system.
If you can't find them here you can always copy them from a stock rom.
Make sure the binary file is from the same build as your current rom. It might not matter, but it just might.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm really hoping someone is nice enough to copy and paste their bootanimation file in here, but I doubt it'll happen...
Any tips/ideas on how to go about copying from a stock rom? (I'm new to a lot of this stuff, so I'm unsure of how to go about this)

you can search on google and download boot animations.
but like doc said , ' make sure is from same build cause it might just matter. i DL cm 10.1 from internet and works great .
just a thought.
err on the side of kindness

@mrrocketdog
It's not so much a boot animation itself that I'm having trouble with, but the actual system file called "bootanimation".
I believe when I tried to install a custom animation I/the files from a tutorial I was using altered it, and now it doesn't work whatsoever.
If you know of any boot animation tutorials/files that could fix this though that would be sick!
Either way thanks for the input!

You can try these if you like. I'm running Likewise rom right now, but they should work fine for you.
http://forum.xda-developers.com/attachment.php?attachmentid=2969141&stc=1&d=1413149765

Solved
DocHoliday77 said:
You can try these if you like. I'm running Likewise rom right now, but they should work fine for you.
http://forum.xda-developers.com/attachment.php?attachmentid=2969141&stc=1&d=1413149765
Click to expand...
Click to collapse
I love you. At first it didn't work but I changed some permission and now it's back to stock! Thank you sooo much!
Not to to add further trouble, but to prevent any future mishaps, could you point me in the right direction to getting a custom boot animation running?

maybe here..
http://forum.xda-developers.com/showthread.php?t=2843830
if you use search a whole lot pops up.
good luck. :thumbup:
err on the side of kindness

There should be a thread(s) in the Themes and Apps section. I wouldn't use any not confirmed or made for the S3 though. And I wouldn't mess with that binary file either. (Unless specifically told to do so in one of our threads.) Any we have here should work fine just using the actual animation files.
Some threads may also have a return to stock zip file you can flash in recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

think thats o.k. doc ? so maybe be REAL FREAKIN CAREFUL.
err on the side of kindness

Alright guys, sounds like a plan. I'll make sure to be a whole lot more careful this time around! Thanks a bunch!

mrrocketdog said:
think thats o.k. doc ? so maybe be REAL FREAKIN CAREFUL.
err on the side of kindness
Click to expand...
Click to collapse
Are you referring to the one you linked to? To be perfectly honest I wouldn't try it. It was for the HTC One, right? I just don't know enough about HTC devices. It might be safe to use the animation, but it may just not work. (I doubt there'd be much danger of a hard brick though, but better safe....)
Sent from my SAMSUNG-SGH-I747 using Tapatalk

yup, thats the one. i forget sometimes : READ READ READ. thanks for double checking behind me. will be more careful in future. dont want to cause xtra problems !!!!!!
err on the side of kindness

No problem. It could be perfectly ok to use, but since I don't know, I consider it a higher risk is all. Another thing to consider is if it's dpi is different the images probably wouldn't display correctly.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

@DocHoliday77
So after a while of researching I was thinking of downloading CyanogenMod, and the using that to do boot animation stuff, thoughts?

As long as it's from the S3 versions of cm, I believe it would be safe to try. Probably the worst that might occur would be no animation, like you already experienced. I don't use CM though, and don't really mess with the boot animation much to begin with, so it is possible it wouldn't work as expected, I'm just not sure on that. But it should be simple enough to get back to the stock animation with the files I posted before.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Yeah, I guess that's really the worse that could happen, I've made a backup of my stock ROM so I should be able to go back if needed. Again, thanks for all the help!