first time using custom recovery - T-Mobile Samsung Galaxy S 4

why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.

I think most people still recommend 2.5.0.2, because 2.6 is so buggy...
Sent from my SGH-M919 using XDA Premium 4 mobile app

Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
Yes, TWRP has issues, use CWM. I'm using it for a while. So far so good
Sent from my SGH-M919 using xda app-developers app

TWRP is my preferred recovery and I've had zero issues with version 2.5.0.2 since I got this phone.

Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
I had exactly the SAME expirence.although I'm not new at rooting and using custom roms this being a new device for me I took everyone's advice and installed twrp. it was so buggy that it almost bricked my device. it got stuck on the introduction screen I couldn't get into tecovery or get out of the screen.i Eben pulled battery and it continued on that screen. finally finally I was able to get into the recovwry system, I rebooted and immediately I downloaded cwm recovert touvh wick has been wonderful ever since. That said, I thought this expirence with twrp was mine alone until ive heard of similiar complaints. I would NOT recommend twrp to ANYONE myself.i couldn't even flash a rom on it. I'm stocking with cwm recovery where its solid and works well

Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
I am clueless as to why anyone would want to use TWRP as well lol. CWM has always done its job.

When I restore a backup that I made, do I have to wipe anything before or after the restore process?

Related

Rom Manager Recovery 6.0.1.4

Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Hoezack said:
Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yea, It almost ruined my phone as well. I ended up having to restore to an older version. It wouldnt let me flash anything, constantly hung or restarted, and never actually told me that it finished, though when I rebooted it turned out that it did finish flashing, although much of it was messed up, almost like it only flashed certain parts of the rom.
I've had very similar experience with 6.0.1.4.
I'm glad I'm not alone, I thought it was just something I did wrong.
Sent from my SGH-T989 using xda premium
mth785 said:
I'm glad I'm not alone, I thought it was just something I did wrong.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Why they have released the update is puzzle to me? Its bad. 5.0.2.7 is the best.
ksrikanthreddy777 said:
Why they have released the update is puzzle to me? Its bad. 5.0.2.7 is the best.
Click to expand...
Click to collapse
5.0.2.7 cache wipes and fix permissions do not work for ics hence the scripts. 6.0.1.2 worked great. i've had problems with 6.0.1.3 and eventually started using twrp. no regrets.
I'm using sk8's CWM 6.0.something touch recovery and everything is working.
Sent from my SAMSUNG-SGH-T989 using xda premium
I didn't flash 6.0.1.4 from ROM Manager (blackwing version), but I flashed it from CWM and I just got a boot loop while trying to install CM9 09-23 Nightly.
Did a battle pull, and tried to do stuff in CWM6 and it was super slow and nothing would flash. I couldn't even wipe caches or do a factory reset.
I ended up doing a Restore (which never finished) but did a battery pull and luckily I was able to boot into my previous ROM.
I never had any issues with 5.0.2.7 thanks to Darkside Super Wipe and Cache scripts, even flashing ICS and JB ROMs.
freedom_xda said:
I didn't flash 6.0.1.4 from ROM Manager (blackwing version), but I flashed it from CWM and I just got a boot loop while trying to install CM9 09-23 Nightly.
Did a battle pull, and tried to do stuff in CWM6 and it was super slow and nothing would flash. I couldn't even wipe caches or do a factory reset.
I ended up doing a Restore (which never finished) but did a battery pull and luckily I was able to boot into my previous ROM.
I never had any issues with 5.0.2.7 thanks to Darkside Super Wipe and Cache scripts, even flashing ICS and JB ROMs.
Click to expand...
Click to collapse
Yeah I had the same problem so I had to go back to 5.0.2.7.... Wit this version I have no problems backing and restoring roms.....Also with this version I can flash any rom ics, aokp, gb
Sent from my SGH-T989 using xda app-developers app
I'm currently using sk8's cwm6.0.1.4 and no issues so far.
pepe7053 said:
Yeah I had the same problem so I had to go back to 5.0.2.7.... Wit this version I have no problems backing and restoring roms.....Also with this version I can flash any rom ics, aokp, gb
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I had the same issue with 6.0.1.4 non-touch. But the touch version is working just fine.
Make sure you wipe dalvik cache and wipe partition before flash.
wow, I also had flashed the non-touch recovery and that's when I started getting all my problems.
I'm still using v5.0.26 and darkside superwipe, no issue at all roms
Twrp 2.2.2 is stable
another case of a product becoming a paid product while losing quality in the process.
Im currently running a Nandroid backup using 6.0.1.4 and its hella slow... like 20+ mins and still running, this is beyond bad. On 5.0.2.7 it ran in about 5mins.
Is the touch recovery better?
Edit: Now its at almost 40 mins... yeesh
Hoezack said:
Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I had the same exact problem with it yesterday. I was trying to restore my backup, so I tried to do a wipe/reset and it wouldn't do anything. So I just restored my backup anyway and it would always just stop at restoring secure.android. So I took out the battery and rebooted and my backup was restored. So I tried ROM manager to flash back to 5.0.2.7. But it constantly forced closed. So long story short, I'm now using twrp and I like it better.
Omg I thought I was the only one with this problem. Took me forever to get my phone working again. Had to Odin back to stock. 6.0.1.4 touch was working fine though (installed using Odin)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hmm.. ROM manager flashed 6.0.1.4 just fine on my phone. I've done this procedure about 4 times too. Weird.
Sent from my SAMSUNG-SGH-T989 using xda premium
Khameleon said:
Im currently running a Nandroid backup using 6.0.1.4 and its hella slow... like 20+ mins and still running, this is beyond bad. On 5.0.2.7 it ran in about 5mins.
Is the touch recovery better?
Edit: Now its at almost 40 mins... yeesh
Click to expand...
Click to collapse
on 6.0.1.4 and 6.0.1.5, mine just hangs on "backing up .android_secure" and the progress bar never moves. I've waited up to 40 minutes with no progress. I've never completed a backup since I switched from 5.0.2.7. I'm going to switch to another recovery.

Phone won't boot into recovery?

Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.
Nothing wrong with CWM.
Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?
EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium

TWRP Problem!

Hi, So when I tried to open up twrp recovery, it wouldnt open....it would just stay at the logo and blink every now.and then....So I used oden and installed cwm over twrp and it was fine....I didnt like cwm so I went back to twrp..... it works fine and I can do everything EXCEPT some files are inaccessible and every time I flash something,it works but also gives me the error measages in the image I posted... does anyone know how to fix this?
Sent from my SPH-L710 using xda premium
razzack3000 said:
Hi, So when I tried to open up twrp recovery, it wouldnt open....it would just stay at the logo and blink every now.and then....So I used oden and installed cwm over twrp and it was fine....I didnt like cwm so I went back to twrp..... it works fine and I can do everything EXCEPT some files are inaccessible and every time I flash something,it works but also gives me the error measages in the image I posted... does anyone know how to fix this.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Maybe try installing twrp from goo manager while connected to WiFi to ensure a good download
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
I had the same exact problem a couple days ago. I fixed it by going Into goo manager and re flashing a new TWRP. I did it on Mobile Data, worked fine!
Sent from my SPH-L710 using Tapatalk 2
Go back to 2.3.3.0. Search for the flashables ones. Since 2.4.2.1 TWRP have a lot of issues.
Sent from my SPH-L710
I see a lot of people complaining about TWRP related issues with various versions of this recovery.
Is there any reason people don't talk about CWM around here? I've been using different versions of cwm touch and twrp ... And I'm honestly pretty happy with cwm.
Why does it appear that people avoid talking about cwm? ... If indeed it works as well as it seems to me that it does?
One reason is that a lot of people think it's better and recommend it to others. I used cwm on my old evo and was going to when I got my s3, but most people and roms were recommending twrp. I've been using it and have tried out cwm as well. For me, at least it hasn't been problematic, but I don't download them through the goo manager. As I feel like I have less control over what I'm getting (I don't even know what version I'm getting until after I download it). That, and I just don't trust the phone to download without errors even when on Wi-Fi.
Just my two cents.
Sent from my SPH-L710 using xda app-developers app
I just actually switched to cwm a couple days ago because twrp had been giving me backup and restore problems.. everything twrp can do cwm does also, and it seems to be faster backing up and restoring also, but that might just be placebo... devs recommend twrp because that is what their Rom/kernel/mod was tested with... 99% of the time cwm will work just fine also
SPRINT GS3 FAQ
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
razzack3000 said:
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Actually, having used both, I think TWRP had been the better of the two because of the ease of naming your nandroids and the fact that backups in TWRP don't take up so much space as the CWM backups do. Have you seem the crazy Blobs folder in CWM? I like backing stuff up to the PC, but the CWM backups made that process extremely painful. I don't know what happened to make TWRP so unreliable recently, but I just noticed a newer version is out: 2.5.0.0
Sent from my SPH-L710 using Tapatalk 2
DurhamHusker said:
I see a lot of people complaining about TWRP related issues with various versions of this recovery.
Is there any reason people don't talk about CWM around here? I've been using different versions of cwm touch and twrp ... And I'm honestly pretty happy with cwm.
Why does it appear that people avoid talking about cwm? ... If indeed it works as well as it seems to me that it does?
Click to expand...
Click to collapse
There's nothing bad about CWM, but is 2013 and you can't rename your nands which is very important(not necesary) in a phone which date as 1970. Also the touch version looks like a '90 recovery.
But if you want a issues free TWRP go back to 2.3.3.0.
Sent from my SPH-L710
I did that... Now it only recognizes my ext sd card and the 0 folder in my internal storage that I clear out a while ago
Sent from my SPH-L710 using xda premium
topherk said:
One reason is that a lot of people think it's better and recommend it to others. I used cwm on my old evo and was going to when I got my s3, but most people and roms were recommending twrp. I've been using it and have tried out cwm as well. For me, at least it hasn't been problematic, but I don't download them through the goo manager. As I feel like I have less control over what I'm getting (I don't even know what version I'm getting until after I download it). That, and I just don't trust the phone to download without errors even when on Wi-Fi.
Just my two cents.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you update from goo manager, a pop up will tell you what version you are about to install beforehand. Also the webpage that it takes you to in order to start the auto download also states the name of the .IMG which also indicates version. I know what you mean about trusting downloads from the phone though. I personally think that is the reason a lot of people have issues with twrp. I've always updated to the latest twrp and flash almost daily, but have never had to switch versions because of bugs. All versions have ran perfect for me.
razzack3000 said:
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I've used both for quite a while. I used to only use cwm for the longest but decided to try out twrp because of those ridiculous blobs! What's with that? So I decided to try twrp and I've stayed because of all the little features like a warnings before you wipe things you shouldn't, option to flash more than one zip at once, option to clear cache and dalvik right after flashing, etc... Plus there are some pretty major features that get overlooked. Like the built in file browser. I installed miui once and it created a folder I could not delete and keep deleted. Every time I would reboot, it would come back. Twrp file browser deleted it and kept it deleted. The only thing I don't like about twrp is the system date and time being way off.
Edit: Lol. I've edited like 5 times because I keep wanting to add more info. Also, twrp doesn't take ages to fix permissions. As long as cwm takes, I can just do it manually
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
I've been on 2.4.0 and 2.4.4, and only had to do backups but haven't tried to restore yet, so after hearing all the war stories, I went back to 2.3.1.
UPDATE: I just upgraded from 2.3.1 to 2.5.0, performed wipes, a backup and a restore and all went perfectly smooth. The only issue was the time was 2 hours behind what it should have been for US central, so I selected 2 hours ahead and chose military time (my preference) and I'm happy.
Where did you get 2.5.5?i only found 2.5.0
Sent from my SPH-L710 using xda premium
oops, I mean't 2.5.0

What recovery are you using?

This isn't a "which is better" thread. Just curious as to what recovery everyone is using and why. I tried out Philz touch recovery and it was awesome, but it was really slow when it came to creating and restoring backups. Did anybody else experience this?
marcoxx626 said:
This isn't a "which is better" thread. Just curious as to what recovery everyone is using and why. I tried out Philz touch recovery and it was awesome, but it was really slow when it came to creating and restoring backups. Did anybody else experience this?
Click to expand...
Click to collapse
TWRP because it was recommended by different devs and stayed with it because it never gave me an issue as of yet.
I just used TWRP 2.6 and had to go down to TWRP 2.5 because it was sooooo laggy. Everything seems to work good now.
Sent from my SGH-M919 using xda app-developers app
I use them all.
Sent from my SGH-M919 using xda app-developers app
I'm on TWRP 2.6 and, unlike many, have experienced zero problems.... aside from unintentionally wiping internal storage a few times due to the rearranging of the wipe menu from 2.5.x. I've tried CWM and Philz Touch, but I've become so accustomed to TWRP because that's the only recovery I used on my previous device and was the 1st I flashed on the S4.
TWRP 2.5.0.2
I'm on TWRP cause a lot of people were recommending it. Had Clockworkmod on my Xperia Play, It's good too. You can't really go wrong with either of those. But, I noticed with TWRP, it has a touch screen interface, it's a little clumsy in navigation and will take some getting used to, to browse directories, that's my only real complaint.
Clockworks free recovery, (i think they charge for their touchscreen version) is navigated usually by volume rocker, i prefer that than touch. I know i'm weird like that. =P
lordcheeto03 said:
I'm on TWRP 2.6 and, unlike many, have experienced zero problems.... aside from unintentionally wiping internal storage a few times due to the rearranging of the wipe menu from 2.5.x. I've tried CWM and Philz Touch, but I've become so accustomed to TWRP because that's the only recovery I used on my previous device and was the 1st I flashed on the S4.
Click to expand...
Click to collapse
I didn't have any problems with 2. 6 on my s3 but it just didn't play too friendly on my s4 I'm with you though, I feel attached to TWRP lol
Sent from my SGH-M919 using xda app-developers app
I'm on TWRP, but it is very laggy for me. Iv been trying to find 2.5.x.x. Can someone post a download link?
Sent from my SGH-M919 using Tapatalk 2
As somebody who came from ClockworkMod recovery (since the Froyo days), I was interested in trying touch recovery. I tried clockworkmod touch but it just didn't feel right. I then tried team win recovery project and the interface seemed light years ahead of clockworkmod. Needless to say, I've been on team win recovery project ever since.
Sent from my SGH-M919 using Tapatalk 2
I've been using TWRP 2.5.0.2. for months without any issues.
2.6.0.0 has had issues of which I don't know if they've been resolved yet. There is a TWRP thread which you can always check out.
If you use Goo Manager to install TWRP, 2.6.0.0 will be installed by default. Then if you are having issues, you'll have to use ODIN and install 2.5.0.2.
To install TWRP 2.5.0.2 with ODIN, here is the file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
If you need the steps on how to install TWRP via ODIN, let me know
It seems like everyone, including me, is using some version of TWRP.
~~~~~~~~~~~~~~~~~~~~~
I am always on the mobile app and am always 'trying' to help others and moderators on the forum and learning something new everyday. I make stupid posts sometimes, but I never repeat a mistake more than once. I may not be a developer, but I know alot of stuff, so feel free to messsge me any questions and I'll be happy to answer them to the best of my ability.
~~~~~~~~~~~~~~~~~~~~~
I'm starting a video game company with my friend where we will be making Android games. message me for more info or go here: http://forum.xda-developers.com/showthread.php?t=2290843
Oudhs touch recovery its cwm based with rainbow mode feature and swipe gestures
Looks good easily controlled.
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
Biker1 said:
I've been using TWRP 2.5.0.2. for months without any issues.
2.6.0.0 has had issues of which I don't know if they've been resolved yet. There is a TWRP thread which you can always check out.
If you use Goo Manager to install TWRP, 2.6.0.0 will be installed by default. Then if you are having issues, you'll have to use ODIN and install 2.5.0.2.
To install TWRP 2.5.0.2 with ODIN, here is the file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
If you need the steps on how to install TWRP via ODIN, let me know
Click to expand...
Click to collapse
The only issue I seem with twrp 2.6.0.0
Is it takes an unusual amount of time for the recovery to boot up on the s4
Like 30 seconds..
And especially a long time on the gN2
Like a minute or so...
Sent from my SGH-M919 using xda app-developers app
Phil's CWM Touch best cwm out there.
Philz Touch
I use Philz Touch on my S3 and S4. Highly customizable CWM with support for the Aroma File Browser.
I don't have any problems that I've noticed with TWRP 2.5.0.2 taking too long to load. I did also try philz touch but I found myself hitting the wrong stuff all the time. I almost wiped everything on my phone (including internal storage) lol. I noticed it was slower than TWRP when making backups also, takes a loooong time for me.
Sent from my SGH-M919 using xda app-developers app
I thought I broke my phone when I put TWRP 2.6 on it. I rooted the phone with oudhs and right away wanted TWRP as that is what I use on all my Android devices. When it appeared hung at the splash screen I panicked. It was stuck trying to boot to recovery when powering on so I put oudhs back on with Odin. Glad to hear I can use an older version and will now get back in TWRP.
Sent from my SGH-M919 using xda premium
Fishtick26 said:
I thought I broke my phone when I put TWRP 2.6 on it. I rooted the phone with oudhs and right away wanted TWRP as that is what I use on all my Android devices. When it appeared hung at the splash screen I panicked. It was stuck trying to boot to recovery when powering on so I put oudhs back on with Odin. Glad to hear I can use an older version and will now get back in TWRP.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
In case you need it. Use ODIN to intall
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
lojak29 said:
Oudhs touch recovery its cwm based with rainbow mode feature and swipe gestures
Looks good easily controlled.
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
The only issue I seem with twrp 2.6.0.0
Is it takes an unusual amount of time for the recovery to boot up on the s4
Like 30 seconds..
And especially a long time on the gN2
Like a minute or so...
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
With TWRP 2.5.0.2, Recovery boot time is:
- 10s between vibrate & TeamWin screen
- 8s between TeamWin screen and Recovery screen
Total is approx. 18s
I use Quickboot to boot into Recovery:
- 6s between pressing Recovery and the vibrate alert.
Quickboot used to be quicker on my S3, which was about 2s instead of 6s..
Am I the only one who's on cwm? I've used twrp a lot and I switched over to cwm. At least for now.
Sent from my GT-I9505G using XDA Premium HD app

[Q] Such bad luck with recoveries

Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Have you tried PhilzTouch yet?
Alex9090 said:
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
lalec said:
Have you tried PhilzTouch yet?
Click to expand...
Click to collapse
Never used philz and never thought of just reflashing the kernel. I may try that though. Now to find the kernel. I should mention that I end up using Odin to reflash stock. Then I root and then custom recovery. That boots fine and for the most part all I'm ever doing is trying to restore a 4.4 rom I backed up.
Flashing a kernel worked. lol my phone doesn't think it's the stock kernel but it booted at least.
I do find this interesting. I would think when you restore a nandroid backup that it would restore the kernel that was with the rom you are restoring. I guess this isn't the case?
Using the latest clockwork has always worked for me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had Rom Manager Premium since my Defy days. I'm a firm believer in it. I was just surprised I would have to reflash a kernel after restoring a rom.
Corwinder said:
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
Click to expand...
Click to collapse
I use OUDHs Touch recovery v1.0.3.3 in conjunction with Rom Manager and I have NEVER had that problem. Also, when I use Rom Manager to "Back Up Current Rom" I can NAME the backup file, and it goes into the recovery and uses the filename I have already typed in and it's a seamless operation. Even using restore via Rom Manager works seamlessly and it has NEVER balked on me.
The only time I had a problem was once using My Backup Pro and trying to do an on-line system backup. MMS, SMS, Call Log has always been absolutely perfect! No out of sequence messages, and all the pictures are restored correctly too!
Aloha and Good Luck!
BTW, I am on a Stock 4.2.2 with the latest M919UVUFNB4 (modem.bin) Flashed for the radio and it's reception qualities are better than it's ever been before!

Categories

Resources