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
Related
Any idea when well be receiving this recovery? The Sprint Note II has already made it onto their supported device list.
bhowanidin said:
Any idea when well be receiving this recovery? The Sprint Note II has already made it onto their supported device list.
Click to expand...
Click to collapse
I thought this is already available for the Note 2. http://teamw.in/project/twrp2/115. Is there a version specific for different carrier models? I was under the impression that the CWM recovery we used for rooting was from N7100, so I'm assuming that the TWRP recovery will also work on the Note 2. I'm still using CWM recovery though and haven't tried installing TWRP.
akkidy said:
I thought this is already available for the Note 2. http://teamw.in/project/twrp2/115. Is there a version specific for different carrier models? I was under the impression that the CWM recovery we used for rooting was from N7100, so I'm assuming that the TWRP recovery will also work on the Note 2. I'm still using CWM recovery though and haven't tried installing TWRP.
Click to expand...
Click to collapse
i went a little bit adventurous and installed the TWRP for the n7100 on my t889 and atleast it booted and went to recovery just fine and installed supersu without problems
Yo_MaMa said:
i went a little bit adventurous and installed the TWRP for the n7100 on my t889 and atleast it booted and went to recovery just fine and installed supersu without problems
Click to expand...
Click to collapse
Good to know Yo_MaMa, thanks for reporting back. I thought i read somewhere that the backups are not restoring successfully with TWRP.
akkidy said:
Good to know Yo_MaMa, thanks for reporting back. I thought i read somewhere that the backups are not restoring successfully with TWRP.
Click to expand...
Click to collapse
Ya I tried it on mine and it would not mount the sdcard properly so I could not even see files on the sd card nor could I make a nandroid... It's just not working properly for some reason?
EDIT: New version out and it installs through GooManager and it's working 100%!
http://forum.xda-developers.com/showthread.php?t=1966105
shojus said:
Ya I tried it on mine and it would not mount the sdcard properly so I could not even see files on the sd card nor could I make a nandroid... It's just not working properly for some reason?
EDIT: New version out and it installs through GooManager and it's working 100%!
http://forum.xda-developers.com/showthread.php?t=1966105
Click to expand...
Click to collapse
Thanks shojus, I'll install it now. I've always preferred TWRP than CWM because of the file manager advance option and the ease of use selecting internal or external storage. :good: Good News!!!
akkidy said:
Thanks shojus, I'll install it now. I've always preferred TWRP than CWM because of the file manager advance option and the ease of use selecting internal or external storage. :good: Good News!!!
Click to expand...
Click to collapse
Ya I always miss TWRP on new devices.... Glad it is working now!
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've flashed roms before on my phone and it was all fine and dandy. I recently though went back to stock, removed root. Then I downloaded Chainfire SU today out of boredom, rooted, installed TWRP and tried installing GE roms on my M919V. No matter which one I flash, I'm stuck on the Galaxy S4 screen which is annoying. Is there anyway to fix this?
Make sure you are flashing YOUR kernel made for your device.
Mateoftw said:
I've flashed roms before on my phone and it was all fine and dandy. I recently though went back to stock, removed root. Then I downloaded Chainfire SU today out of boredom, rooted, installed TWRP and tried installing GE roms on my M919V. No matter which one I flash, I'm stuck on the Galaxy S4 screen which is annoying. Is there anyway to fix this?
Click to expand...
Click to collapse
What version of TWRP are you using? I have heard of TWRP causing problems with v2.6. Try TWRP 2.5.0.2
Another thing could be a 64GB msdc. If you have one in that's format to exFat, a kernel that does not support exFat will cause you to bootloop or freeze on start screen. If that's the case flash a compatible kernel as suggested by TheAxMan or reformat to FAT32
baseballfanz said:
What version of TWRP are you using? I have heard of TWRP causing problems with v2.6. Try TWRP 2.5.0.2
Another thing could be a 64GB msdc. If you have one in that's format to exFat, a kernel that does not support exFat will cause you to bootloop or freeze on start screen. If that's the case flash a compatible kernel as suggested by TheAxMan or reformat to FAT32
Click to expand...
Click to collapse
TWRP 2.5.0.2 isn't without it's problems either. It worked alright for about 6 weeks and then it caused my phone to be unable to mount /data. I didn't have my phone useable for a whole day, and i finally found out how to fix it and now i stick with CWM which has never given me a scare like that.
Also, i used to have my 64GB SD card and it was exFat with a custom kernel that didn't support it, and my ROMS would still boot up, just my external SD would not be recognized until i reformatted to FAT32.
Those are by no means the one and only solutions. They're only a few things to look at as reported by others with similar problems.
☞Sent from here☜
Hello, i've been trying lots of different roms but basically every time i try to change my rom (running 4.3 google edition), i put the zip file in my internal sd card by usb cable, go on recovery, flash it, and it either says bad file- not compatible or it flashes but won't boot.
I tried all different recoveries. All of them suck as they don't have usb mounting working..
ATM I'm running Philz touch recovery that i downloaded a month ago.
Also, my phone has this weird problem with wifis disconnecting and not reconnecting sometimes, it started a few months ago..
Anybody know why is this happening? Should i try other recoveries? Bad USb connection? I tried downloading it on wifi too..
Right now i flashed a old version of wicked that i had saved in my internal sd because usb mounting wouldn't work in recovery..
Are you checking md5 sum of your files?
What are your procedure for flashing(steps you're taking)?
i have seen and heard problem with philz touch and twrp for a while now
philz touch doesnt like allot of roms
twrp works for some people, and doesnt for others
so try a different recovery. if you want the most stability install cwm or cwm touch. if problems still persist, try wiping internal storage. at one point i couldnt get anything to flash untill i wiped it
TheAtheistOtaku said:
i have seen and heard problem with philz touch and twrp for a while now
philz touch doesnt like allot of roms
twrp works for some people, and doesnt for others
so try a different recovery. if you want the most stability install cwm or cwm touch. if problems still persist, try wiping internal storage. at one point i couldnt get anything to flash untill i wiped it
Click to expand...
Click to collapse
Thanks for the help guys, after wasting 2 hrs of my hw time doing roms -.-! i flashed CWM recovery (latest) and it works perfectly.
TWRP didn't work for me either, latest version wouldn't go to recovery at all. PhilZ wouldn't flash most roms.
Husam2011 said:
Thanks for the help guys, after wasting 2 hrs of my hw time doing roms -.-! i flashed CWM recovery (latest) and it works perfectly.
TWRP didn't work for me either, latest version wouldn't go to recovery at all. PhilZ wouldn't flash most roms.
Click to expand...
Click to collapse
If you like TWRP and would prefer to use it, use the 2.5.2 version. There is a flashable zip for it in the TWRP thread somewhere. You will have to search for it...
That version is far more stable than the latest versions.
Sent from your phone. You should be careful where you leave that thing.
Husam2011 said:
Hello, i've been trying lots of different roms but basically every time i try to change my rom (running 4.3 google edition), i put the zip file in my internal sd card by usb cable, go on recovery, flash it, and it either says bad file- not compatible or it flashes but won't boot.
I tried all different recoveries. All of them suck as they don't have usb mounting working..
ATM I'm running Philz touch recovery that i downloaded a month ago.
Also, my phone has this weird problem with wifis disconnecting and not reconnecting sometimes, it started a few months ago..
Anybody know why is this happening? Should i try other recoveries? Bad USb connection? I tried downloading it on wifi too..
Right now i flashed a old version of wicked that i had saved in my internal sd because usb mounting wouldn't work in recovery..
Click to expand...
Click to collapse
Hi I couldn't use twrp it didn't work for me so I suggest you download cwm touch works great. Also when you download the rom from your computer make sure its going to the root of your EXTERNAL sd card. This is usually achieved as mounting as disk drive and your device will showup as external drive D or E. Then when you download your rom download to external drive D orE which ever name it gave your device when mounting as disk drive. This way the rom is placed on your external sd card. and when your in cwm you will press download rom from external sd card scroll down and find your rom then you should be good to go. Hope this helps .
realsis said:
Hi I couldn't use twrp it didn't work for me so I suggest you download cwm touch works great. Also when you download the rom from your computer make sure its going to the root of your EXTERNAL sd card. This is usually achieved as mounting as disk drive and your device will showup as external drive D or E. Then when you download your rom download to external drive D orE which ever name it gave your device when mounting as disk drive. This way the rom is placed on your external sd card. and when your in cwm you will press download rom from external sd card scroll down and find your rom then you should be good to go. Hope this helps .
Click to expand...
Click to collapse
Bad usb cables can cause problems so if you know for sure that the md5 was good and you followed all dev instructions related to wiping before install it wouldn't hurt to try a different cable.
Sent from my SGH-M919
The fix is simple!
Install CWM via freegee, it'll replace TWRP.
Afterwards everything will work like it's supposed to, you'll be able to use CWM to flash the newer CM roms on your phone!
PaRaNoidNeM said:
The fix is simple!
Install CWM via freegee, it'll replace TWRP.
Afterwards everything will work like it's supposed to, you'll be able to use CWM to flash the newer CM roms on your phone!
Click to expand...
Click to collapse
Umm...if your on a Custom ROM, that won't work. You can also use the hacked TWRP and the problem is solved.
You did not think this thread out to clearly, you stated the obvious but not the entire spectrum of problems and ways...just sayin'.
Sent from my LG-E980 using Tapatalk 2
Sorry but what was the error you were getting while flashing newer CM?
Use the hacked twrp from madmack. It works fine.
sent from my OG PRO using tapatalk 4