Related
This is meant to be a dev thread, not an end-user thread. Please keep this on-topic. End-user support and VM670 development are off-topic.
For the more user and Optimus V (VM670) oriented thread please check in here:
http://forum.xda-developers.com/showthread.php?t=1176888
If you are working on porting the phone to the VS660, LW690, US670, or MS690 with the eventual goal of inclusion in the IHO repository please check in here.
I'm trying port this for the ms690. I'll admit it's a bit over my head but I have a rooted and flashed M and a rooted but stock M at my disposal and a working android development environment.
My rom is compiling now after fixing the typo in the mms_config.xml. I would like to help get the proper changes in the IHO repo if I get this working, but I have absolutely no idea how all that works.
I'll update here if I get my rom compiled and let ya know how it runs. Anyone know how long it should take to completely compile a rom error free? I'm running 2 dual core xeons at 2ghz... This is a long compile for a >100MB file, heh.
Has anyone successfully ported using Ubuntu 11.xx on a 32 bit, vmware setup? I got it to work with wubi, but that messed up my windows. Can you run Ubuntu off of a thumb drive but use your hard drive for storage?
Sent from my LG-VM670 using XDA App
1. I thought you couldn't successfully compile on 32 bit since 2.2
2. Setting up a development environment in vm? or on a flash drive? Do you really deserve that kind of punishment?
I guess you could build on a persistent usb but but it sounds scary to me. I don't know if you could properly mount a drive in live usb, seems like you would need your build folder on a hdd or a 32gig flash.
Backup your stuff and throw on an ext partition. Your building will be easier in a native environment and a clean windows install never hurts.
My compile is stopped. I've been poking around and I don't think I'm gonna figure this out like all the other BS I've figured out.
GRRR this is ****ing stupid, tried to post my error but the forum thinks that xxx.xml is a web address and wont let me post cuz I don't have enough posts. If anyone can help me shoot me a PM I'm not gonna spam the forums to get my posts to post a ****ing error log. If I ever met a spammer I would kick him in the nuts for all the bull**** I have to deal with because of the crap...
pbailey212 said:
Has anyone successfully ported using Ubuntu 11.xx on a 32 bit, vmware setup? I got it to work with wubi, but that messed up my windows. Can you run Ubuntu off of a thumb drive but use your hard drive for storage?
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
I use a 32-bit version of whatever the LTS version is with VirtualBox. 10.04?
Sent from my LG-VM670 using XDA App
blarfiejandro said:
I use a 32-bit version of whatever the LTS version is with VirtualBox. 10.04?
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
I was thinking about downgrading Ubuntu and trying it, I'm on Ubuntu 11.xx now. I would like to keep the vmware setup, I like just minimizing vmware to go back and forth to windows. Plus everything's transferable between the 2 os'
Sent from my LG-VM670 using XDA App
Update: Its creating the zip file now, I just needed to up the ram available to vmware, I wish I would have tried that a week ago, thanks for hearing me ***** and moan about this
pbailey212 said:
I was thinking about downgrading Ubuntu and trying it, I'm on Ubuntu 11.xx now. I would like to keep the vmware setup, I like just minimizing vmware to go back and forth to windows. Plus everything's transferable between the 2 os'
Sent from my LG-VM670 using XDA App
Update: Its creating the zip file now, I just needed to up the ram available to vmware, I wish I would have tried that a week ago, thanks for hearing me ***** and moan about this
Click to expand...
Click to collapse
I had problems setting up a good build environment with 11.04, but 10.10 64 bit with VMware works great for me on Windows 7 64 bit.
EDIT: I forgot to mention that if anyone want to try my Optiums Cricket version they can grab it here: http://www.mediafire.com/?vcfc5jtwncsxkzg
I don't own a OC, I built it for a friend. He tells me that GPS, BT, and MMS are not working.
So I got my very own zip file, backed, wiped flashed, my phone told me It was "bad" so I went and restored my backup it said bad md5, I thaught no big deal, I keep a couple backups handy, all 3 of them said bad md5. I restored them before just fine, I don't know what's going on, I should just give up, but I'm stupid and enjoy a challenge. I guess I will start completely fresh again. "Goin back to compile"
Sent from my LG-VM670 using XDA App
somedood81 said:
I'm trying port this for the ms690. I'll admit it's a bit over my head but I have a rooted and flashed M and a rooted but stock M at my disposal and a working android development environment.
My rom is compiling now after fixing the typo in the mms_config.xml. I would like to help get the proper changes in the IHO repo if I get this working, but I have absolutely no idea how all that works.
I'll update here if I get my rom compiled and let ya know how it runs. Anyone know how long it should take to completely compile a rom error free? I'm running 2 dual core xeons at 2ghz... This is a long compile for a >100MB file, heh.
Click to expand...
Click to collapse
It'll probably take a couple of hours to compile. The easiest way to get everything included is to file a pull request on Github. Keep in mind I'm not going to accept any applications (so that rules out the real popular MMS patches floating around for the C and M). Most of the stuff for the M is already in the tree, I believe...
Some of the other stuff like cnd probably won't get fixed /just/ yet, but I'll rename the keymap file. What else did you have to change?
pbailey212 said:
So I got my very own zip file, backed, wiped flashed, my phone told me It was "bad" so I went and restored my backup it said bad md5, I thaught no big deal, I keep a couple backups handy, all 3 of them said bad md5. I restored them before just fine, I don't know what's going on, I should just give up, but I'm stupid and enjoy a challenge. I guess I will start completely fresh again. "Goin back to compile"
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
Someone mentioned that IHO wasn't computing checksums properly in the general dev thread. Try using another recovery and/or making sure your build box isn't on its way out?
Anyhow I'm using a 32-bit Ubuntu 10.04.3 VM to build everything and it works just fine for me (definitely need to throw some more RAM at the machine tho).
blarfiejandro said:
It'll probably take a couple of hours to compile. The easiest way to get everything included is to file a pull request on Github. Keep in mind I'm not going to accept any applications (so that rules out the real popular MMS patches floating around for the C and M). Most of the stuff for the M is already in the tree, I believe...
Some of the other stuff like cnd probably won't get fixed /just/ yet, but I'll rename the keymap file. What else did you have to change?
Click to expand...
Click to collapse
I had to fix a typo on a tag in the mms_config.xml, I think using the cnd from the V was a no no, so i commented out the cnd in the build. There was an extra space in a string in an xml file I can't remember that needed removed. Other than that I just put in the ko files and the gps libs and it was building fine.
I fixed the last error I had which was about 2.5 hours into the build and started the compile over... Then my workstation shut down. It refuses to even post. Tried a new video card to no avail. Dual xeon running rambus ram, LOL. Don't have any parts laying around for it other than drives and video cards.
My port is kind of stalled at the moment, heh.
Just thinking out loud:
Has anyone done a build for the MS690(Metro version)?
Is the "LG Optimus One, P500, > Optimus V Android Development" thread for all Optimus phones? Or just the V?
I was working on the ms690 b4 my linux box died. There are a couple of us working on it.
somedood81 said:
I was working on the ms690 b4 my linux box died. There are a couple of us working on it.
Click to expand...
Click to collapse
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
BobZhome said:
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
Click to expand...
Click to collapse
That was the last error I was working with actually. Don't know if I had it fixed.
The op m can't use CWM recovery. We have 2 custom ones, joneidys recovery and getitnowmarketing recovery.
somedood81 said:
That was the last error I was working with actually. Don't know if I had it fixed.
The op m can't use CWM recovery. We have 2 custom ones, joneidys recovery and getitnowmarketing recovery.
Click to expand...
Click to collapse
Can't use CWM? All other Optimus phone do!
Sent from my VM670 using Tapatalk
I don't know the details of why, here is a thread on it:
http://androidforums.com/optimus-m-all-things-root/352401-do-not-use-clockwork-mod-rom-manager.html
It would be cool if someone could figure out the problem and fix it...
BobZhome said:
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
Click to expand...
Click to collapse
Sounds like you need to have the proper MMS overlays in the device folder. Maybe.
blarfiejandro said:
Sounds like you need to have the proper MMS overlays in the device folder. Maybe.
Click to expand...
Click to collapse
The overlay/MS690/packages/apps/Mms/res/xml/mms_config.xml has a bad string.
Profile<string/> needs to be changed to Profile</string>
I posted a comment on your git.
I compile my 0.1 kernel and trying an other MS690 build.
Blarf, can you look at these two pastebin to see if you see anything wrong.
There are problems with my LW690 builds, wifi produces an error and camera is broken.
wifi - http://pastebin.com/hMmhH9Bk
camera - http://pastebin.com/ukSGQaWz
Bluetooth wasn't working and when I used the MS BT file it worked, do you think by using the MS BT in the LW is giving me the wifi problem?
Thanks for the help,
Bob
Basically, does Heimdall support this phone? I have a Mac/Ubuntu, and dislike having to use someone else's computer to flash stuff that isn't flashable with cwm.
Sent from my Herculean Juggernaut.
Not yet, but I asked in another thread (an OS X thread asking the same thing) for someone to post a USB log of ODIN attaching to the device. Actually, a full log of it attaching and also updating would be useful but probably large. Since log data like that is plain-text and very repetitive, it would probably compress well.
Also, I've opened an issue at the Heimdall github (issue #29). I can't post a URL because my XDA account is too new, but I've poked around in the code and it should be straighforward to implement (Benjamin did a pretty good job making it readable).
I'm going to try to do that implementation once I have the data.
Thanks for replying.
Sent from my HëЯ¢ú1ëλN júGGëЯNλú＋!
Here is something that would be really awesome
http://forum.xda-developers.com/showthread.php?t=1347899
Sent from my SGH-T989 using Tapatalk
GBGamer said:
Thanks for replying.
Click to expand...
Click to collapse
No worries! Actually, I completely feel your pain; I run Ubuntu on my desktop and laptop at home, on my workstation at work, and my work laptop is a Mac. The biggest reason I'm asking for USB logs is that I just can't stand going through the motions to set up Windows & ODIN myself
Perhaps a bit lazy and loser-y, I suppose, but I'll redeem myself if I get Heimdall working, for sure.
billydroid said:
Here is something that would be really awesome
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
Definitely!! But we still need ODIN/Heimdall for CWM recovery in a softbrick situation, right? If we just want to root, I think there are a couple one-clicks reported to work... but for ROM development you definitely want an easy recovery mode, just in case.
droidjaggers said:
Definitely!! But we still need ODIN/Heimdall for CWM recovery in a softbrick situation, right? If we just want to root, I think there are a couple one-clicks reported to work... but for ROM development you definitely want an easy recovery mode, just in case.
Click to expand...
Click to collapse
Right we do. But that mobile Odin is simply awesome.
Sent from my SGH-T989 using Tapatalk
Major thread necro here, but... I actually have news!
Heimdall works on SGH-T989 now. One caveat... it's not the 1.4RC1 that Benjamin is releasing soon, rather, it is a fork. Unfortunately, the first of two contributors who built the required functionality chose to rename almost all the variables and functions, making it a serious pain in the ass to merge the changes back to the mainline Heimdall source tree.
This is the currently working tree: git://github.com/jamiejackson/Heimdall.git
Check it: http://mulad6.blogspot.com/2012/09/getting-heimdall-to-work-with-sgh-t989.html
I just built it and used it to install CWM Recovery on two T989's, and it worked like a champ on the first try, both devices (no "keep trying it because ODIN sometimes screws up"). \m/
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..
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.
*******************************************************************************************************************************************************************************
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!