[Q] [POLL] Which recovery do you use? - Nexus 5 Q&A, Help & Troubleshooting

Hello,
With all the questions and threads going on about lost IMEIs and problems with recoveries, I figured there should be a thread/poll dedicated to which recovery most of the nexus5 owners are using.
I guess it would also be helpful if people post their success rates in flashing/wiping using the said recoveries.
Three available recoveries atm:
1) TWRP official 2.6.3.4
2) CWM official 6.0.4.5
3) CWM unofficial 6.0.4.5 by Playfulgod
I get my nexus tomorrow so I guess I shall post it then

omgbuffguy said:
Hello,
With all the questions and threads going on about lost IMEIs and problems with recoveries, I figured there should be a thread/poll dedicated to which recovery most of the nexus5 owners are using.
I guess it would also be helpful if people post their success rates in flashing/wiping using the said recoveries.
Three available recoveries atm:
1) TWRP official 2.6.3.4
2) CWM official 6.0.4.5
3) CWM unofficial 6.0.4.5 by Playfulgod
I get my nexus tomorrow so I guess I shall post it then
Click to expand...
Click to collapse
Stock recovery...

TWRP 2.6.3.4
I haven't had any problems with this version. But when I had an earlier version (2.6.3.2 maybe?) It took forever to wipe the cache and dalvik. It also borked my cache part after a restore without doing a first boot, this gave me like 3 cache partitions lol. Reflashing cache via fastboot fixed it. Seems the problem is fixed in the new 2.6.3.4 version though.

omgbuffguy said:
Hello,
With all the questions and threads going on about lost IMEIs and problems with recoveries, I figured there should be a thread/poll dedicated to which recovery most of the nexus5 owners are using.
I guess it would also be helpful if people post their success rates in flashing/wiping using the said recoveries.
Three available recoveries atm:
1) TWRP official 2.6.3.4
2) CWM official 6.0.4.5
3) CWM unofficial 6.0.4.5 by Playfulgod
I get my nexus tomorrow so I guess I shall post it then
Click to expand...
Click to collapse
Best of threads are generally frowned on but oh well.
I use twrp 2.6.3.4 for three reasons.
Officially supported by @Dees_Troy
Easy straightforward operation
Was 'early' reported issues with official cwm note I said early once I flashed twrp I've stayed with it.
Sent from my Nexus 5 using Tapatalk

TWRP... ftw!

TWRP
Sent from my Nexus 5 using Tapatalk

voted.. using twrp

PlayfulGod's unofficial cwm. It works well.
Sent from my Nexus 7 using Tapatalk 4

Related

Difference between CWM and TWRP?

On my HOX I have TWRP installed. What is the difference between CWM and TWRP? Don't they do the same thing?
Most importantly, will CWM mods work with TWRP? (like the .zip ones) Also, what about de-odexing?
Sorry for all of the questions, I'm new to android modding.
Cwm is buggy. You can use twrp for everything and it's fine.
gunnyman said:
Cwm is buggy. You can use twrp for everything and it's fine.
Click to expand...
Click to collapse
Alright so there are no downsides to using TWRP right? On this forum all I see is CWM on every thread
Mike724 said:
Alright so there are no downsides to using TWRP right? On this forum all I see is CWM on every thread
Click to expand...
Click to collapse
CWM is the most common recovery, cause its the oldest and most known. But, you can also tell its the oldest, as the UI is... Ugly, compared to TWRP. The "slide to confirm" function on TWRP is really nice IMO.
But yeah, when they say "CWM", they just mean a custom recovery.
Also, TWRP is officially supported on our devices, which is why its recommended above CWM.
Sent from my GT-N700 using Tapatalk 2
It's not 100% bug free but it is much more stable than cwm.
^That, and the TWRP tries to fix the bugs as they are presented.
Sent from my GT-N700 using Tapatalk 2
Good to note too that CWM nandroids are not restorable in TWRP. So all previous backups from CWM are useless once you change.
Sent from my HTC One X using xda app-developers app
i have CWM on my one x, if i want to change it to TWRP, how would i do that? follow instruction on TWRP web site?? http://teamw.in/project/twrp2/99
I started out using CWM but switched because I use CleanRom and Scott suggested using TWRP. I just loaded it by downloading GooManager from google play and then following the install instructions. Worked fine for me...
claudiuslu2011 said:
i have CWM on my one x, if i want to change it to TWRP, how would i do that? follow instruction on TWRP web site?? http://teamw.in/project/twrp2/99
Click to expand...
Click to collapse
You can just install TWRP right on top of CWM using a flashable TWRP zip, Goo Manager, or through fastboot.
Mike724 said:
On my HOX I have TWRP installed. What is the difference between CWM and TWRP?
Click to expand...
Click to collapse
Another point, the version of cwn for the HOX is an unofficial port and thus not supported. There is an official version of twrp for the HOX, which is reason enough to switch.
Mike724 said:
On my HOX I have TWRP installed. What is the difference between CWM and TWRP? Don't they do the same thing?
Most importantly, will CWM mods work with TWRP? (like the .zip ones) Also, what about de-odexing?
Sorry for all of the questions, I'm new to android modding.
Click to expand...
Click to collapse
CWM was never officially released for our phone. It was a port from another version and isn't perfect. My experience with twrp has not shown me a single problem or even a hiccup.
Sent from my HTC One X using xda premium

[Q] TWRP on Note 10.1 Tablet

Has anyone tried to install TWRP Recovery yet on any versions of the Galaxy Note 10.1 Tablets yet? If not I would like to start testing it and trying it out as an alternative to the CWM Recovery. If someone has started to test it out please post any information here and or lets open up a thread in the Development section and try to get the ball rolling there too with testing and information on usage.
hkeyman said:
Has anyone tried to install TWRP Recovery yet on any versions of the Galaxy Note 10.1 Tablets yet? If not I would like to start testing it and trying it out as an alternative to the CWM Recovery. If someone has started to test it out please post any information here and or lets open up a thread in the Development section and try to get the ball rolling there too with testing and information on usage.
Click to expand...
Click to collapse
the quicker we can get TWRP on the better. good luck trying it out.
I have already sent a PM over to TeamWin to ask about sending over any info/files needed and getting testing going to port it over to this device...I will keep this thread posted on developments. :thumbup:
UPDATE!
In case you wanted to know and did not know yet that an Update has happened for the NOTE 10.1 now for TWRP. I downloaded and installed recovery and it works (As you can see). Only bug I have experienced so far is the keyboard is responding then double typing or backing out of the function I was in like in backup trying to name the backup. But so far it works!
Should flashed it via goo and worked perfectly!!!!
Thank god cause i really dislike CWR
GooManager cant find my recovery
I used GooManager try to install TWRP in my N8000 also but it is said that no recovery is found for my device.......
What is the problem???
I tried to flash from ODIN also, but as i reboot my device the TWRP is gone then chg back to stock recovery......i need to flash agn when i want to use it and prevent it to reboot before i used.
Is that still no solution for N8000 for having the permanent TWRP yet???
exooodx said:
I used GooManager try to install TWRP in my N8000 also but it is said that no recovery is found for my device.......
What is the problem???
I tried to flash from ODIN also, but as i reboot my device the TWRP is gone then chg back to stock recovery......i need to flash agn when i want to use it and prevent it to reboot before i used.
Is that still no solution for N8000 for having the permanent TWRP yet???
Click to expand...
Click to collapse
Exactly the same for me (N8000 + Android 4.1.1).
is TWRP better then CWM if yes why because most people suggest to use CWM for almost all devices I have seen
It doesn't support the 64gb sd card exfat format...
Its not bad if you us other cards but I love my big (almost full) 64gb card....
How do I flash TWRP, does it support 64gb exfat?
Enviado desde mi GT-N8000 usando XDA Premium HD app
OLYMPIAKOI said:
How do I flash TWRP, does it support 64gb exfat?
Enviado desde mi GT-N8000 usando XDA Premium HD app
Click to expand...
Click to collapse
Already answered in post DIRECTLY above yours....
64GB SD Card works fine on my Team Union Rom TWRP with exFat format.
:thumbup:
Sent from my GT-N8013 using xda app-developers app

[Q] Verizon Galaxy S3 Rom Flashing Help

I have been flashing (roms) for a while now devices including G2, HTC Hero, HTC Thunderbolt, Moto Razr, and now Galaxy S3. I don't typically post questions on any forums because I usually can find an answer with enough searching, it pains me to write this.
Problem: I can only flash certain roms on my Verizon SGS3.
I have no problem flashing unofficial aokp, unofficial cm10, and Synergy.
When I try to install different roms from xda and other websites i get the attached photo. These roms include paranoid android, miui, liquids jelly bean, and a few others.
My device is rooted, unlocked bootloader through ez unlock, running clockworkmod (touch) v5.8.4.5 via ez recovery.
Before I flash I always:
wipe data/factory reset
wipe cache partition
format system
wipe dalvik cache
Re-downloading has not fixed the issue. I'm sure im missing something simple any help would be warmly welcomed!
Thanks in advance all!
-Stumped S3 User
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
annoyingduck said:
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Bingo!! Wrong version of CMW, just download e-z flasher from the play store and use it to flash either TWP or CMW. Easy peasy quick and easy.
I suggest you use twrp.
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Cwm 6.0.1.2 all day. Refuse to use anything else lol. Unless amon ra gets ported
Sent from my SCH-I535 using Tapatalk 2
Worked like a charm!
I downloaded rom manager, installed latest clock work, updated to touch, and it is working perfect! Thanks to all! The fun begins

Twrp vs cwm vs amon-ra

so i have always used cwm on my devices, and i love cwm, but sometimes there is only a limited amount of custom recoverys for my devices such as my g1 that the guide i followed gave me amon-ra instead which i thought was terrible, i dont think i have tried twrp yet, is there like partition differences? more options between each?
Trozzul said:
so i have always used cwm on my devices, and i love cwm, but sometimes there is only a limited amount of custom recoverys for my devices such as my g1 that the guide i followed gave me amon-ra instead which i thought was terrible, i dont think i have tried twrp yet, is there like partition differences? more options between each?
Click to expand...
Click to collapse
I just switched to TWRP from CWM and it's much better. I would highly recommend TWRP.
RXG9 said:
I just switched to TWRP from CWM and it's much better. I would highly recommend TWRP.
Click to expand...
Click to collapse
When you switched from CWM to TWRP did you lose any CWM backups you might have had on your device?
same here just moved to TWRP. loving the interface so far. no issues aswell
What is TWRP? Sorry im newbie
Brainjitzu
Brainjitzu said:
What is TWRP? Sorry im newbie
Brainjitzu
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that is touch based. So instead of constantly clicking buttons like in CWM you can just just do a full wipe with one swipe, if you only want to wipe certain partitions you can with advanced wipe. Also it also allows you to flash as many as 10 zips at a time. i recommend this to any user and i use it for My Galaxy Nexus, and Galaxy SIII. easiest way to get it is via Goo.im app you can get it via the Play Store.
CWM.
Because well supported on all low end devices..:thumbup:
Sent from my A1 using xda premium
Sanjay said:
CWM.
Because well supported on all low end devices..:thumbup:
Sent from my A1 using xda premium
Click to expand...
Click to collapse
Agree with that, during the past 2 years i had over 6 android phones and CWM supported all of them
Sent from my XT890 using XDA Premium 4 mobile app
I've used CWM versions that are touch based too. For old phones it is hard to find TWRP that supports them.

[Q] CM Stuck on logo animation while booting

Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Categories

Resources