Related
I have always used CWM and currently use the touch version. I have had some problems with CWM lately like the no media mess up with ROM manager. And the other day when going to 4.2. Things I like about TWRP is the keyboard and file manager as well as being able to update to the newest touch recovery through goo manager. So before making the switch from my staple recovery is there anything I should know. I have heard TWRP may have issues with Cyanogen and might be a little slow?
Sent from my toroplus using xda app-developers app
I still use CWM, it does the job for me. Others swear by TWRP so you're better off trying them both
EddyOS said:
I still use CWM, it does the job for me. Others swear by TWRP so you're better off trying them both
Click to expand...
Click to collapse
Same here. Although the /0/ thing has me seriously considering switching to TWRP.
I don't mind trying both but I like all my backups to be easily accessible within my recovery. Plus I don't think I would run into anything for a while and don't want to invest making all my backups in TWRP then find out an issue that someone may have already encountered before me. Sorry of that comes off weird. I started this thread more as an opinion on what converts maybe like or dislike about TWRP.
Sent from my toroplus using xda app-developers app
I've had CWM for a long time(since the galaxy S days) but when i got my gnex off on ebay, It had the TWRP recovery installed, after trying it I decided that I will never go back to CWM. It's just a matter of user preference really, for all those years that I've used CWM I've never had any single issues with it. I can say the same for TWRP after using it for almost a year now.
Few things I love about TWRP:
-Swipe to confirm Install
-Full touch screen with big buttons(i know CWM has touch screen version too but I was only able to try the semi touch screen version and did not really like it)
-File Manager
-Ability to compress(don't know if CWM can do this but I've included it too) and rename/name backups
-You can queue the zips you want to install(maximum of 10), no more going back and forth between sdcard directories and recovery menus
Those are the ones that I could think of at the moment. I'm sure there's a lot more else to list down. If you ask me TWRP is a bit more user friendly because of the UI
Just switched to TWRP a couple of months ago, after having always used CWM. No real issues with CWM. I have just found TWRP to be more user friendly for me.
TWRP have more features than CWM, for example, file managing and the ability to name backups. Thats a great advantage if you ask me.
Recently switched to TWRP. Loving it so far. I especially like the Advanced -> ADB Sideload function so I can superwipe and flash without worrying about the internal storage.
I've always used CWM, but like others, because of /0/, I'm considering trying twrp. I just made a backup with CWM 6.0.1.9, but now that i've found it, i'm unsure of how to copy it to my computer. That is, my mac recognizes /data/media/0 via android file transfer, but i cannot transfer the backup from here. And I really dont want to move the backup and blobs folders twice just for the sake of copying. Any ideas? Also, whatever happened to navbar arrows in cwm touch?
I switched to TWRP because of the excessive number of blobs made by CWM.
It's a real pain having to copy over 2,000 files and folders over MTP to a computer.
I like to keep the most recent backup on my Gnex, while moving the older backups to my computer.
Consider this. I used cwr on my droid X and it worked fine. The day I got my Gnex and rooted it I ignored CWR and immediately installed TWRP. Never looked back. I always hear people say "I switched from CWR to TWRP and its great". Not once have I heard it the other way
Sent from my Galaxy Nexus using Tapatalk 2
I'm preaching to the choir here, I know, but one of the main reasons for rooting is a custom Recovery and the benefits that come with that. Both CWM and TWRP are included in the Note 2 Toolkit, but after an incident yesterday and over an hour of XDA reading since, I honestly don't know which Recovery to use anymore.
CWM EPIC-FAILED me yesterday when just trying to flash stock MA5 over stock LJC. I did a Nandroid, a full wipe, flashed the MA5 Firmware, flashed Stock Deodexed MA5, reflashed the MA5 firmware (like the OP said to do), rebooted, and BARF. Looping device activation, and after I chased my tail around in that for 4 or 5 cycles, it ended up in boot loop. I could get into Recovery as well as Download Mode, but restoring any of my six Nandroids via Recovery did not work and I also determined that CWM was wiping anything.
So I searched and found where another Note 2 user had the same wiping problem with CWM and was told to use TWRP. So I Odin'ed TWRP over replacing CWM, wiped everything via TWRP, and then Odin'ed CWM back over so I could (hopefully) do a restore. Soft brick...that looked scarily like a hard brick for a second or two as my phone would do NOTHING. I was finally able to convince it into Download Mode, so I flashed everything back to unrooted stock. Thankfully, I had a Titanium Backup of all my apps/data, but I still had to reconfigure the system settings all over again since I don't use TB for that (because...y'know...that's what Nandroids are for).
By the time that was all said and done it was 3AM, so this morning I immediately searched the forums for Recovery issues, and I have to say that I'm surprised and disappointed with what I've found. There doesn't seem to be a reliable Recovery available for the Note 2! I've found threads with far more problems with TWRP than CWM, but the few I found with CWM are real deal-killers like what I encountered (can't wipe, can't restore).
I'm not being a whiner -- it's a legit question. On all my previous and other current devices, I had my choice between at least two sometimes three or even four rock-solid Recoveries. Is the Note 2 really without a solid Recovery option? Because if it is, then my flashing days are pretty much over except during the rare times where I can potentially be without a phone for 24-48 hours in case a CLUSTER happens like my latest experience. Given my CWM issues, I've now switched to TWRP, but after reading everything in the forums, I can't say that I feel very warm/fuzzy about it.
internetpilot said:
I'm preaching to the choir here, I know, but one of the main reasons for rooting is a custom Recovery and the benefits that come with that. Both CWM and TWRP are included in the Note 2 Toolkit, but after an incident yesterday and over an hour of XDA reading since, I honestly don't know which Recovery to use anymore.
CWM EPIC-FAILED me yesterday when just trying to flash stock MA5 over stock LJC. I did a Nandroid, a full wipe, flashed the MA5 Firmware, flashed Stock Deodexed MA5, reflashed the MA5 firmware (like the OP said to do), rebooted, and BARF. Looping device activation, and after I chased my tail around in that for 4 or 5 cycles, it ended up in boot loop. I could get into Recovery as well as Download Mode, but restoring any of my six Nandroids via Recovery did not work and I also determined that CWM was wiping anything.
So I searched and found where another Note 2 user had the same wiping problem with CWM and was told to use TWRP. So I Odin'ed TWRP over replacing CWM, wiped everything via TWRP, and then Odin'ed CWM back over so I could (hopefully) do a restore. Soft brick...that looked scarily like a hard brick for a second or two as my phone would do NOTHING. I was finally able to convince it into Download Mode, so I flashed everything back to unrooted stock. Thankfully, I had a Titanium Backup of all my apps/data, but I still had to reconfigure the system settings all over again since I don't use TB for that (because...y'know...that's what Nandroids are for).
By the time that was all said and done it was 3AM, so this morning I immediately searched the forums for Recovery issues, and I have to say that I'm surprised and disappointed with what I've found. There doesn't seem to be a reliable Recovery available for the Note 2! I've found threads with far more problems with TWRP than CWM, but the few I found with CWM are real deal-killers like what I encountered (can't wipe, can't restore).
I'm not being a whiner -- it's a legit question. On all my previous and other current devices, I had my choice between at least two sometimes three or even four rock-solid Recoveries. Is the Note 2 really without a solid Recovery option? Because if it is, then my flashing days are pretty much over except during the rare times where I can potentially be without a phone for 24-48 hours in case a CLUSTER happens like my latest experience. Given my CWM issues, I've now switched to TWRP, but after reading everything in the forums, I can't say that I feel very warm/fuzzy about it.
Click to expand...
Click to collapse
I used the MA5 One Click and it flashed fine. Then I downloaded the Note II Took kit and flashed TWRP using Mobile Odin and it worked fine also.
Amigo, bad versions happen even with the best software.
Further MA5 is a leak and not official stable code....use it at your own risk.
MikeyLee said:
I used the MA5 One Click and it flashed fine. Then I downloaded the Note II Took kit and flashed TWRP using Mobile Odin and it worked fine also.
Click to expand...
Click to collapse
All that is risky business if you don't have a working Recovery to restore from. Have you tested that? You might want to.
I've been a flashing fool on all my other Android devices, and always been able to work my way out of any/all problems with a proper backup. I don't have that same level of confidence with the Note 2. Sure, I can always ODIN back to stock unrooted and start all over, but I don't have time for that and...really...who wants to do that?
Skripka said:
Amigo, bad versions happen even with the best software.
Click to expand...
Click to collapse
Well, that's true, but the TWRP issues span numerous versions, and since my backups were in CWM, I probably tried just about every version of CWM that's been released for the Note 2, since all I wanted to do was restore even just one of my six Nandroids (a basic function of Recovery). Even after restoring everything to stock and re-rooting (including the latest version of CWM), I still couldn't even restore my very first Nandroid (or any of the other five). Brand new latest tech phone, all this development going on, and unless I have the time to restore back to stock, re-root, reconfigure, etc., then I simply can't risk trying any it. This all by itself makes my ancient EVO4G the better phone, which is just ridiculous.
Hence my question, is there a reliable Recovery for the Note 2? In my experience, there isn't, but I would absolutely love to be wrong.
Skripka said:
Further MA5 is a leak and not official stable code....use it at your own risk.
Click to expand...
Click to collapse
My complaint isn't with MA5 at all. I've had plenty of failed flashes over the years on my devices for a variety of reasons including myself, but there's always been an easy way around any issue by simply restoring with Recovery.
I had some similiar but smaller problems and reluctantly flashed CWM 6.0.2.5 (I think) through the CWM Rom Manager app. I've gone through the app do backups, installs, etc and it has worked great. I also use Rom Toolbox and it doesn't like that recovery sometimes, but otherwise it's been good.
Sent from my SPH-L900 using xda app-developers app
I've only used TWRP since I got the phone in October.
Not even 1 problem yet so I recommend TWRP.
Sent from my SPH-L900 using xda premium
You are aware the twrp is not compatible with cwm backups? Also did you rename your cwm backup,( ive corupted my own backups through this) ?
Sent from my SPH-L900 using xda app-developers app
AndroidStephen said:
I had some similiar but smaller problems and reluctantly flashed CWM 6.0.2.5 (I think) through the CWM Rom Manager app. I've gone through the app do backups, installs, etc and it has worked great. I also use Rom Toolbox and it doesn't like that recovery sometimes, but otherwise it's been good.
Click to expand...
Click to collapse
Have you tried a restore yet? I didn't have any problems with CWM until I noticed it wasn't wiping and then none of my restores worked either.
devynbf said:
I've only used TWRP since I got the phone in October.
Not even 1 problem yet so I recommend TWRP.
Click to expand...
Click to collapse
Despite so many posts about problems with TWRP, I decided anything had to be better than what I was encountering with CWM, so I gave it several test backups and restores today, as well as wipes and flashing. Everything went without a hitch except that I encountered the "Unfortunately, Chameleon has stoppped" message, but that's was because things were so convoluted with LJC, LK8, and MA5 on my device. I finally got everything cleaned up and back on running LJC, and it would seem that I have some reliable, restorable backups now. I guess only time will tell.
irule9000 said:
You are aware the twrp is not compatible with cwm backups? Also did you rename your cwm backup,( ive corupted my own backups through this) ?
Click to expand...
Click to collapse
Of course -- this is why I had to use TWRP to wipe (when CWM wipe wasn't working), and then re-flash CWM so I could try to restore my CWM backups. I don't get any error messages when trying to do a CWM restore -- it runs through the whole restore process (taking as long as it should), but then when I reboot, I have running exactly what I had before the restore. I think my problem is more of a wipe issue than a restore issue, but it could also be a combination of both.
Don't really know who to report the problem to since there doesn't seem to be a CWM thread for the Sprint Note 2.
Anywho, it looks like I'll be going with TWRP (not that I have much choice). Unfortunately, this means that I'm now running three different recoveries on my devices -- CWM on the Nooks, Amon Ra on the Acer A500, and now TWRP on the Note 2.
I've had TWRP running flawlessly on my last device (Evo 3D) and my GNII. I'll continue to use it unless something better comes along. Its always been solid for me.
Sent from my Mackified Galaxy Note II using XDA Premium.
If you're having the chameleon error, thats not because twrp.
Go to sesrch and look for the EviL KoNCEPTz and garwynn fix for chameleon.
Theres a flashable zip that fixes the chameleon errors.
Sent from my SPH-L900 using xda premium
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
Here.
Go to this page and flash the zip file on here for the chameleon fix.
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using xda premium
TWRP has never failed me on any device from ego to evo3d to evo 4g lte and finally my note 2. Stick with twrp and make your backup with twrp so it actually restores Just my input but twrp shouldn't give any problems.
I posted earlier that CWM had been working for me... well, today I tried to do a restore and got an error stating the md5 didn't match, so no go. Said the same thing for 3 seperate back-ups, and I was trying to do the restore with the same app that made the back-up. Soooo... TWRP, here I come.
Sent from my SPH-L900 using xda app-developers app
devynbf said:
If you're having the chameleon error, thats not because twrp.
Go to sesrch and look for the EviL KoNCEPTz and garwynn fix for chameleon.
Theres a flashable zip that fixes the chameleon errors.
Sent from my SPH-L900 using xda premium
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
Here.
Go to this page and flash the zip file on here for the chameleon fix.
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Thanks -- I did figure out that it had nothing to do with TWRP, but I found a thread on another forum that only had three posts on it (a lot less to wade through) and a different solution where you simply replace the Chameleon.apk file. Since I was running (not walking) back to LJC from MA5, it worked. I'll just wait for Samsung/Sprint to release an official update. The only thing I got out of LK8 and MA5 was soft-bricked phone and Chameleon/registration headaches.
I did some more testing with TWRP and it's looking good, so I'll just stick with it.
AndroidStephen said:
I posted earlier that CWM had been working for me... well, today I tried to do a restore and got an error stating the md5 didn't match, so no go. Said the same thing for 3 seperate back-ups, and I was trying to do the restore with the same app that made the back-up. Soooo... TWRP, here I come.
Click to expand...
Click to collapse
Y'know, I'm a very forgiving man when it comes ROMs, kernels, and other hacks to my phone, but I freely admit to being a demanding little whiny baby when it comes to Recovery -- it needs to work. Period. When it doesn't that makes my tech life hell. TWRP has been working for me fine over the past couple days of testing things, so I'm sticking with it it. I don't know why there are so many posts here with TWRP issues, but so far I haven't had any through multiple wipes, backups/restores, flashes, etc. Usually when I try to get something to break it breaks, but so far I haven't been able to do that with TWRP.
When I originally rooted CWM was installed. I then went to install the upgraded stock but had problems as CWM did not do a proper wipe. I then installed TWRP and have not had any problems.
Prior to the Note II I was using the original EVO 4G. I had CWM originally installed but again had issues with the wipe. I wound up using AmonRa Recovery which I loved. I wish there was one like it for the Note II as it was also able to restore nandroid backups made by CWM.
Doc
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.
Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.
n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app
I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.
I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium
I currently have a rooted E980 on stock ROM/Recovery.
My goal is:
1) Install CM 10.2 (and CM11 once stable)
2) Be able to back up ROMs (i.e. nandroid) - If I have a problem I would like to restore via a nandroid.
3) If all goes well, maybe try other ROMs (Carbon, Slim, etc) - Although I am not a flash addict.
I have experience with CWM and TWRP with other devices (Nexus, HTC), but it seems to be a bit different with the LG E980. I hear about Loki, Lokified, soft-bricks, boot loops, etc.
Should I use Freegee, TWRP 2.6.3 or PhilZ Touch? Any recommendations would be appreciated!
I have used the CWM 6.0.3.7 that came from Freegee to flash/backup/restore probably 20 ROMs with no issues. I know some people have had issues with it and prefer @madmack's hacked TWRP. I haven't had any though, so I have yet to jump ship. 2 cents.
Sent from my Optimus G Pro using Tapatalk
thathamiam said:
I have used the CWM 6.0.3.7 that came from Freegee to flash/backup/restore probably 20 ROMs with no issues. I know some people have had issues with it and prefer @madmack's hacked TWRP. I haven't had any though, so I have yet to jump ship. 2 cents.
Sent from my Optimus G Pro using Tapatalk
Click to expand...
Click to collapse
same experience with freegee, no problems. the only issue I seem to have on some roms is that gps doesn't work and I have no idea why. and from what I hear you can't flash modems with cwm so I'm not sure if that's the problem or not.. everything else works perfect.
Thanks for the recommendations. Anyone used PhilZ Touch?
Ok, I used FreeGee to bypass security and installed TWRP 2.6.3.0. Boots into recovery fine, BUT it will not see my SD card and I tried two different ones. Normal boot shows the cards just fine. Trying to get CM 10.2 flashed.
Any ides???
madgalaxy said:
Ok, I used FreeGee to bypass security and installed TWRP 2.6.3.0. Boots into recovery fine, BUT it will not see my SD card and I tried two different ones. Normal boot shows the cards just fine. Trying to get CM 10.2 flashed.
Any ides???
Click to expand...
Click to collapse
Your cards are most likely in EX-Fat format. EX-Fat is a proprietary file system that is licensed my Microsoft. Since TWRP doesn't license it they can't (legally) include support in their recovery. You're going to have to copy everything over to your computer, reformat the card and transfer everything back. Otherwise you can look to see if there are any recoveries for the G Pro with EX-Fat support.
mrfeuss said:
Your cards are most likely in EX-Fat format. EX-Fat is a proprietary file system that is licensed my Microsoft. Since TWRP doesn't license it they can't (legally) include support in their recovery. You're going to have to copy everything over to your computer, reformat the card and transfer everything back. Otherwise you can look to see if there are any recoveries for the G Pro with EX-Fat support.
Click to expand...
Click to collapse
That is a negative, my cards in FAT format but for the heck of it I did a full format and still no dice. I even tried to use FreeGee and flash CWM, but TWRP still boots as the recovery.
Any other ideas?
madgalaxy said:
That is a negative, my cards in FAT format but for the heck of it I did a full format and still no dice. I even tried to use FreeGee and flash CWM, but TWRP still boots as the recovery.
Any other ideas?
Click to expand...
Click to collapse
Solved. I tried another install of CWM via FreeGee and it took. CWM is recognizing the sd card!
madgalaxy said:
Solved. I tried another install of CWM via FreeGee and it took. CWM is recognizing the sd card!
Click to expand...
Click to collapse
Just checkin....did you use the latest version of free gee from the play store?
Sent from my LG-E980 using XDA Premium HD app
I am embarrassed to have to ask this since I've had android phones for 3 years now.
But to install a new custom recovery... Is it really as easy as just flashing it with my current recovery? I ask of course because I am trying to get kitkat and I was getting error 7. Which, after research led me to believe I need to update my recovery. I've used Download mode before, but I don't know if that is necessary. I've never messed with it before because if it ain't broke, don't fix it kind of deal. Any instructions and/or recovery recommendations for me?
Yes, it is that easy. You can install zips for the newest versions of CWM, TWRP, or PHILZ from your current recovery.
Of course you may not be able to restore your old backups. But you can flash back to the old recovery to restore these too.
Most people are changing to different recoveries because of recent changes in Android that makes it trickier to flash the newer Roms.
I personally switched from TWRP to Philz. It is CWM based, but will also restore TWRP backups. Phil is very receptive to questions and had made his recovery available on a lot of devices, more being added every day.
Thank you, it's much appreciated! I am looking into Philz now!