To whoever can help me -- I'm trying to use kexec to install CM10 on my SGS3, but i've been hearing that when you hard-reboot your phone, AKA battery pull/death, or using the power button, you go right back to the recovery. This isn't a problem, as long as I don't have to re-flash CM10 every time I boot, or I have no choice but to go to the stock ROM. I'd like to be able to either boot to the CM10 or go to my currently flashed version of CM10 from the recovery.
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Bumping... could really use help here.
Just reboot from recovery and it will bootloop a couple times then boot up.
DonSagiv said:
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Click to expand...
Click to collapse
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
lazarus2405 said:
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
Click to expand...
Click to collapse
In which cases would someone lose kexec and need to reinstall it?
Zalithian said:
In which cases would someone lose kexec and need to reinstall it?
Click to expand...
Click to collapse
When u flash back to stock.
droidstyle said:
When u flash back to stock.
Click to expand...
Click to collapse
Or any rom.
jaymattt said:
Or any rom.
Click to expand...
Click to collapse
not necessarily...if your flashing a custom rom/kernel like beans custom stock, cm10, paranoidandroid, aokp, or imosyeons Touchwiz leankernel, kexec is always there...kexec is built into the kernel, cwm 6.0.1 is compatible with kexec.
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
droidstyle said:
Just reboot from recovery and it will bootloop a couple times then boot up.
Click to expand...
Click to collapse
Thanks! CM10 works beautifully on here.
droidstyle said:
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
Click to expand...
Click to collapse
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link. There is also a kexec twrp 2.2 recovery but it didn't work for me.
piiman said:
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link.
Click to expand...
Click to collapse
yea i know, thats what I used in reference to my previous post.
droidstyle said:
yea i know, thats what I used in reference to my previous post.
Click to expand...
Click to collapse
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Triskite said:
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Click to expand...
Click to collapse
let this thread die....there is no need to use anything kexec. stick to cwm 6.0.1.0 or 6.0.1.2
Related
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
flameinthefire said:
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
Click to expand...
Click to collapse
Sounds like an bootloop, just odin back to stock and try again.
If you remove the battery and turn it back on, will it boot into recovery?
power+vol up+home button
Karl said:
power+vol up+home button
Click to expand...
Click to collapse
yes it turns back on but i have unlocked it and its on twp recovery which rom would work with it?
i tried flashing mr beans rom that didnt work beacuse i am on twp recovery and i tried flashing synergy rom that didnt work either so wat should i do. since i unlocked the phone can i still do odin? or will that brick my phone
guys please help!
flameinthefire said:
guys please help!
Click to expand...
Click to collapse
is there any rom that i can use for my unlocked s3
flameinthefire said:
guys please help!
Click to expand...
Click to collapse
Someone already told you what to do. Find a stock ROM, boot up Odin and flash.
the roms you tried work with TWRP... ive used TWRP since release
Karl said:
the roms you tried work with TWRP... ive used TWRP since release
Click to expand...
Click to collapse
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Locked or unlocked phone shouldn't matter as far as the Rom is concerned, it's been stated many times that the kexec kernels will boot fine on an unlocked phone. I would suggest starting fresh, stock ODIN, root, unlock, then flash CWM 6.0.1.0 with ez recovery and go from there.
Some people are not having any issues with the touch recoveries and others are, in my experience the CWM recovery has been the most stable and I could really care less about "touching" my recovery, buttons do the same thing. Just my 0.02
Sent from my Galaxy S III using Xda Premium
feel like an old man hearing these stories......we all know them...when we first started out flashing and **** went wrong....freak outs..panics....sweating..pacing..anger....regret.........BUT then you work through them and look back and say "**** that was easier than I thought"....and we come across them again without panic or hesitation........................dude relax........
1-grab a stock image...chose anyone you want in these forums..some are even prerooted.....i personally got competely back to stock
2-i use the one click root method..so root
3-flash cmw...any version you want as long as it is made for your model phone.....you can use e-z recovery app from market
4-MAKE A ****ING BACKUP!!! very important...
5-download e-z unlock from the play market..use...and done..now you are stock, rooted, unlock bootloader......if you plan on flashing cm10 or aokp or aosp....please make sure to read the thread "how to backup your imei" before flashing any of those roms.............boom goes the dynamite:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh:.............................
King_tee said:
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Click to expand...
Click to collapse
Kexec roms don't but synergy should have. I use twrp and Synergy no problem. There isn't anything special that has to be setup for an unlocked bootloader.
Op you should be able to flash any non kexec rom. Did you do a wipe factory reset? If not you may want to give that a try
Rom: cm9
Cwm: 6.0.1.0 trying to get to 5.0.x in order to flash rom
xr1charxx said:
Rom: cm9
Cwm: 6.0.1.0 trying to get to 5.0.x in order to flash rom
Click to expand...
Click to collapse
Heimdall. See the second post in the oneclicks link in my signature.
Don't forget to read the OP for instructions.
bhundven said:
Heimdall. See the second post in the oneclicks link in my signature.
Don't forget to read the OP for instructions.
Click to expand...
Click to collapse
Second post only has kernels.
I'm lost. Haha.
xr1charxx said:
Second post only has kernels.
I'm lost. Haha.
Click to expand...
Click to collapse
You want to know how I know you cant read....because had you clicked on this link.
eollie: AntonX's BwaT + Stock Rom
Stock KJ6 + Antonx-One-Click.jar
You would have known it wasnt just a kernel...but then again reading is fundamentally hard on xda.
l
eollie said:
You want to know how I know you cant read....because had you clicked on this link.
eollie: AntonX's BwaT + Stock Rom
Stock KJ6 + Antonx-One-Click.jar
You would have known it wasnt just a kernel...but then again reading is fundamentally hard on xda.
Click to expand...
Click to collapse
I don't need stock rom I'm trying to flash Codename Android 2.0 which needs ICS and 5.0.2.x and that one click gives stock rom
how do i update to cm9 and staying on 5.0.2.x recovery
can i just update to cm9 then codename android without rebooting?
back to back flashing ?
xr1charxx said:
l
I don't need stock rom I'm trying to flash Codename Android 2.0 which needs ICS and 5.0.2.x and that one click gives stock rom
how do i update to cm9 and staying on 5.0.2.x recovery
can i just update to cm9 then codename android without rebooting?
back to back flashing ?
Click to expand...
Click to collapse
You can't update to cm9 and stay on 5.0.
Unlike most samsung phones, we do not have a functional recovery partition.
Even though we do have a recovery partition, and you can flash the recovery.img there, the bootloader will not even notice it.
It will just boot the kernel with the kernel command line argument: bootmode=2
In this mode, a stage1 init has to check if we are booting to: recovery, low power mode (charging), or normal boot (possibly with ota upgrade).
So in a nut shell, you upgrade to cm9, you get whatever recovery comes with cm9.
If you want to flash another cm9/ics based rom after that, just flash it (factory reset/wipe data, of course!). No need to go back to 5.0 recovery.
If however, your IMEI is screwed up or you have a specific reason to go back to gingerbread, use the oneclick that eollie mentioned. Flash it twice to get bootloaders. And then you can go back to cm9 by just 'factory reset/wipe data' and flash cm9 or whatever ics rom you wish.
I tried the one clicks but I end up having 6.0 cwm and no bootloader
xr1charxx said:
I tried the one clicks but I end up having 6.0 cwm and no bootloader
Click to expand...
Click to collapse
That didn't make any sense. If you don't have a bootloader, how do you know what cwm you have?
i guess i do have boot loader.
im on CM9. cwm 6.0.1.0 and all i want to do is install this rom.
[TUK's ROM][Hybrid]Codename Android 2.0
http://forum.xda-developers.com/showthread.php?t=1799192
can you please tell me how? :crying:
ive tried one clicking to stock then once clicking Antonx kernel.
but once i go to CM9 i get cwm 6.0 and when i try to once click the AntonX: Basic with a Twist SGS4G KJ6 1.1.0 i get boot loop.
and the eollie: AntonX's BwaT + Stock Rom link is broken.
Sorry about that I changed the link and thought it was the same. This is the correct link.
https://dl.dropbox.com/u/10373328/Stock KJ6 + root-One-Click.jar
so i go back to stock or can i just one click this from my CM9 cwm 6?
http://forum.xda-developers.com/showthread.php?p=2031989
xr1charxx said:
so i go back to stock or can i just one click this from my CM9 cwm 6?
Click to expand...
Click to collapse
Please read some more and understand what one clicking means. You could have cwm 3.x.x.x and if you flash the heimdall one clicks it will change to the current cwm for bml.
ive tried everything and i guess i have bad luck cuz i get boot loops or stuck on boot screen
:[
Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.
So far I've tried installing the latest CyanogenMod 11, CarbonRom, and Paranoid Android with the same errors after each factory reset/dalvik wipes. Finally had to go back to CM 10.2.0 stable. Help!
Tried all the getprop/batch script edits, even tough they all list SGH-I727 compatible. I don't know what else to do.
Installing through CWMR Touch v5.5.0.4, with the .zips on the phone. Don't know anything about ODIN, sadly.
Radio: I727UCMC1
Kernel: 3.0.89-cyanogenmod-g53452f3
[email protected] #1
I am running on T-Mobile, however, as I have switched carriers. Would this be an issue? I'm not so sure, since I am running 10.2 with minor issues.
Please & Thanks for your suggestions!
no ones really going to help you unless you do some reading first, maybe you did but i dont think so since ur still on cwm v5.5.0.4 and you dont know anything about odin, odin is ur friend.
start here, its the sticky just above your post
Alright, I'll investigate ODIN. I think I did use it to flash the CWM I have now, but I'll try and flash current to CWM 6.41.
Impact Blue said:
Alright, I'll investigate ODIN. I think I did use it to flash the CWM I have now, but I'll try and flash current to CWM 6.41.
Click to expand...
Click to collapse
You could flash the latest CWM from the current CWM you have. Try Philz CWM found here:
http://forum.xda-developers.com/showthread.php?t=2557024&page=7
vincom said:
no ones really going to help you unless you do some reading first, maybe you did but i dont think so since ur still on cwm v5.5.0.4 and you dont know anything about odin, odin is ur friend.
start here, its the sticky just above your post
Click to expand...
Click to collapse
Great! Used your sticky to flash the new CWM through ODIN, currently installing the new Paranoid Android ROM.
You are awesome, vincom. Thanks for all your hard work/contributions!!
vincom said:
no ones really going to help you unless you do some reading first, maybe you did but i dont think so since ur still on cwm v5.5.0.4 and you dont know anything about odin, odin is ur friend.
start here, its the sticky just above your post
Click to expand...
Click to collapse
raj3366 said:
You could flash the latest CWM from the current CWM you have. Try Philz CWM found here:
http://forum.xda-developers.com/showthread.php?t=2557024&page=7
Click to expand...
Click to collapse
That's exactly what I did! Thank you--going through my initial boot with PA. WOW, it's been awhile.