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
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..
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.
playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse
barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5
munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5
I am at my wits end right now. I can see my phone on com3 when it is booted up all the way, but it will not see it when in download mode. I erroneously flashed this file earlier, forgetting I did not have a regular GSII: I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar.md5
What other information would help diagnose this problem?
I currently have stock EL26 installed.
Alternatively, is it safe to install CM9 from this recovery? Seems to me I should resolve this first..
edit: I do not have an unrecognized device, I have tried more than one usb cable and port
Try this:
Redownload the drivers for the phone, install them and let your cpu reset. See if Odin sees your phone then.
I know with my GT10.1 it takes a few seconds more for Odin to see it so... But my ET4G pops up pretty fast.
The EL26/CWM is the kernel/recovery that you want to use when your flashing CM9 Alfa 5 and below.
But like you said... You may want to figure out why Odin isn't seeing your phone when it's in download mode.
Also... Do you have Kies installed on your cpu??? It'll cause problems with Odin to.
Have you tried Mobile Odin for what you want to do. I do almost everything involving CM and flashing with it. Works like a charm.
Sent From My Galaxy Class Star Fighter...
How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium
fryingpan0613 said:
How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
WoW... He just edited his post as I was replying... Doesn't flashing an international tar mess up the bootloader??? I'm really not to sure where you go next.
If his phone still boots up okay couldn't help still use Mobile Odin and flash the right setup.
What was that old school Saturday morning psa... "Reading is fundamental" or something like that.
Sent From My Galaxy Class Star Fighter...
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.
hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.
Click to expand...
Click to collapse
Unfortunately my friend, I think you are hosed. The international PIT file is exceptionally different from the one we use for our phone. I don't remember the specifics but basically it remaps your partitions and causes USB to not work correctly. Your best bet is to try a JTAG service. I've heard MobileTechVideos.com is pretty well rated.
Sorry!
My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Edit: ok I take it back, mass storage is not working either. also, I am definitely willing to buy Mobile Odin if anyone has any ideas.
hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Click to expand...
Click to collapse
Not getting on you m8 but... Flashing a rom for another device even if it's the same model is really really bad. Like rwilco said, yes the International GS2 and our ET4G's are the same devices but there software is very different.
hilo4321 said:
My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Click to expand...
Click to collapse
Well... Like you said, most likely you will not be able to make any changes as in roms, kernels or things like that. And if you have any hardware issue you won't be able to get any support from Sprint. And you sure as hell won't be able to receive any OTA's from Sprint or Samsung.
Can you do something for use... Go to "Settings" then "About Phone" and under "Model Number" & "Baseband Version" and tell us what it says there.
I'm not really sure this would/can help you but if your phone still boots and runs you maybe able to Odin the right tar file and see if that fixes it. I mean it could work but I really doubt it. And what's the worst that could happen... It could brick it, then you could file an insurance claim... Just saying...
Where did you get the file from that you flashed??? Most likely not from this (ET4G) forum, should have read up a bit more before you started messing around with flashing roms again. Some things aren't easily fixable.
Sent From My Galaxy10.1 Class Starship....
I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
My baseband is S710.10 S.EK02 with standard model number sph d710.
I believe it came from the android forums, but like i said it was in the SGII area.
What tar file would I be looking for?
Doing some research m8... Give me a few mins....
Make sure you have Mobile Odin installed.
Sent From My Galaxy Class Star Fighter...
hilo4321 said:
I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
Click to expand...
Click to collapse
Ok... Yes you are my friend!!!! But I fear we are not completely out of the woods as of yet. You still have the "no Odin in download" thing still. And that could still be an issue, but at least your back up and running.
hilo4321 said:
My baseband is S710.10 S.EK02 with standard model number sph d710.
Click to expand...
Click to collapse
This is telling me that your on an older baseband... I'm running CM9 and my baseband reads "EL29" which I think is the most resent/updated baseband. I don't want to scare you but I really wish a dev would jump in here and shed some of there wisdom. (I'm almost to the point where I'm winging it.) But I feel we need to get your baseband to EL29.
hilo4321 said:
I believe it came from the android forums, but like i said it was in the SGII area.
Click to expand...
Click to collapse
From now on promise us you'll just use this site and forum for all of your download needs.... Please.
hilo4321 said:
What tar file would I be looking for?
Click to expand...
Click to collapse
Try this post... http://forum.xda-developers.com/showthread.php?t=1433101
Follow the instructions for the Android Install, about halfway down in the first post.
Sent From My Galaxy10.1 Class Starship....
Oh sweet Jesus, I promise.
Now when I do this will this wipe everything? I'm not terribly clear on that. Seems to me that it will.
I really appreciate the help man.
There are 2 different versions... One will wipe everything and one will leave all of your user data intact.
And like I said, I'm not a 100% sure this will fix it but I think we are moving in the right direction.
And not a problem... It's helping me learn more about what goes on inside our devices.
I am still a little worried about your bootloader though. If that was jacked up by flashing the wrong rom I don't know if this will fix it.
Question, when you hook up your device to your cpu when it's booted up are you still able to do things like transfer files and such???
Sent From My Galaxy10.1 Class Starship....
I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.
hilo4321 said:
I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.
Click to expand...
Click to collapse
That's great brother.... I'm really glad I could help ya get up and running to the point where you can a least have a use able device.
Sent From My Galaxy10.1 Class Starship....
EL29 was the last version of Gingerbread put out. You'll be able to use mobile Odin to flash stuff but you'll never get the USB to recognize in DL mode. I think jtag might be the only way to restore complete functionality.
---------- Post added at 11:42 PM ---------- Previous post was at 11:36 PM ----------
For now you'll be alright as long as you can get into recovery mode fine then you can flash modems in there(since mobile Odin can't flash them for our phone).
Your baseband (modem) should not matter and changing it won't have any affect on your problem. Good luck and let us know how out turns out.
Solved
I am posting now in case someone comes upon this post down the road.
I am now running cyanogen 9 on my e4gt. This thread saved me, as I was finally able to get odin to work. With that, I was able to flash a new recovery onto my phone (I used StockCWM-EL26). Then once I got that on there I flashed over to the Beta 1 build of Cyanogenmod for e4gt.
I'm sorry I can't be more clear or provide links, it took me a lot of crawling around the forums to figure this out. Perhaps someone more knowledgeable than I can clean up/expand my post. Let me tell you though, it feels really good to get this thing running smoothly again.
If you have any questions I'll try to help.
Good luck, idiot!
That's awesome dude. Remember stay in this forum :beer::thumbup:
sent from MY BAD A$$ ET4G
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.