Which recovery can I use to get backup/restoring/flashing working? Does philz have that working, thanks.
Using the latest Philz and it is working for me.
Use trwp 2.7
Comet1966 said:
Which recovery can I use to get backup/restoring/flashing working? Does philz have that working, thanks.
Click to expand...
Click to collapse
twrp 2.7 works perfect even if your on NE5. GooManger doesnt work anymore but if you get it from the website and then flash it using odin your good to go.
twrp
Ive tried both philz ans TWRP, and personally like TWRP myself. Its cleaner in my opinion. 2.7works with no issues with backing up and restoring.
+1 on philz recovery. I use it to root even. Here's the link for the S5 if you need it
http://forum.xda-developers.com/showthread.php?t=2706253
Sent from my SM-G900P using XDA Free mobile app
I've never had problems with TWRP 2.7. I heard about all the talk of TWRP not doing well with NE5 and I switched to Philz based on it. Well Philz has only successfully restored about half of my backups so far. Switched back to TWRP and I'm happy.
Related
On my HOX I have TWRP installed. What is the difference between CWM and TWRP? Don't they do the same thing?
Most importantly, will CWM mods work with TWRP? (like the .zip ones) Also, what about de-odexing?
Sorry for all of the questions, I'm new to android modding.
Cwm is buggy. You can use twrp for everything and it's fine.
gunnyman said:
Cwm is buggy. You can use twrp for everything and it's fine.
Click to expand...
Click to collapse
Alright so there are no downsides to using TWRP right? On this forum all I see is CWM on every thread
Mike724 said:
Alright so there are no downsides to using TWRP right? On this forum all I see is CWM on every thread
Click to expand...
Click to collapse
CWM is the most common recovery, cause its the oldest and most known. But, you can also tell its the oldest, as the UI is... Ugly, compared to TWRP. The "slide to confirm" function on TWRP is really nice IMO.
But yeah, when they say "CWM", they just mean a custom recovery.
Also, TWRP is officially supported on our devices, which is why its recommended above CWM.
Sent from my GT-N700 using Tapatalk 2
It's not 100% bug free but it is much more stable than cwm.
^That, and the TWRP tries to fix the bugs as they are presented.
Sent from my GT-N700 using Tapatalk 2
Good to note too that CWM nandroids are not restorable in TWRP. So all previous backups from CWM are useless once you change.
Sent from my HTC One X using xda app-developers app
i have CWM on my one x, if i want to change it to TWRP, how would i do that? follow instruction on TWRP web site?? http://teamw.in/project/twrp2/99
I started out using CWM but switched because I use CleanRom and Scott suggested using TWRP. I just loaded it by downloading GooManager from google play and then following the install instructions. Worked fine for me...
claudiuslu2011 said:
i have CWM on my one x, if i want to change it to TWRP, how would i do that? follow instruction on TWRP web site?? http://teamw.in/project/twrp2/99
Click to expand...
Click to collapse
You can just install TWRP right on top of CWM using a flashable TWRP zip, Goo Manager, or through fastboot.
Mike724 said:
On my HOX I have TWRP installed. What is the difference between CWM and TWRP?
Click to expand...
Click to collapse
Another point, the version of cwn for the HOX is an unofficial port and thus not supported. There is an official version of twrp for the HOX, which is reason enough to switch.
Mike724 said:
On my HOX I have TWRP installed. What is the difference between CWM and TWRP? Don't they do the same thing?
Most importantly, will CWM mods work with TWRP? (like the .zip ones) Also, what about de-odexing?
Sorry for all of the questions, I'm new to android modding.
Click to expand...
Click to collapse
CWM was never officially released for our phone. It was a port from another version and isn't perfect. My experience with twrp has not shown me a single problem or even a hiccup.
Sent from my HTC One X using xda premium
So I installed Clockwork mod touch via terminal emulator and the image on their site. It installs fine and works.....not really.
When I get into recovery and attempt to perform a backup of my current rom it simply says an error has a occured. this happens weather I boot into recovery to do it manually or i attempt to do it through rom manager.
Any ideas of what could be wrong?
Try installing EZ-Recovery from the market, then flash CWM Touch from there. It's a one click flash to recovery, no terminal commands.
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Try installing EZ-Recovery from the market, then flash CWM Touch from there. It's a one click flash to recovery, no terminal commands.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
jesus that app made it so much simpler. too bad it's still not working correctly. Now I'm wordering if the img got corrupted somehow during download to the phone.
After redownloading and flashing it the error is still happening. Regular CWM Recovery works perfectly. Touch...still getting errors. Basically when I click backup it says "backing up boot image" then nothing happens and it goes right back the menu. When I click it again I get the erroer message "Error while backing up root image"
One thing I've noticed is, even with CWM Touch flashed, rom manager still sees it as CWM Recovery 5.8.4.9
Is it possible it just doesn't like synergy?
Yeah I had the same problem when I installed CWM touch using the adb push method. Wouldn't backup, backup was fine with the non-touch version. However, installing via ez-recovery worked.
jasondhsd said:
Yeah I had the same problem when I installed CWM touch using the adb push method. Wouldn't backup, backup was fine with the non-touch version. However, installing via ez-recovery worked.
Click to expand...
Click to collapse
even using ez-recovery didn't work for me.
Hitman3984 said:
even using ez-recovery didn't work for me.
Click to expand...
Click to collapse
Same issue for me. Looking for possible solutions.....
SiXandSeven8ths said:
Same issue for me. Looking for possible solutions.....
Click to expand...
Click to collapse
glad I'm not the only one.
Also noticed tonight smart alert isn't working after flashing to synergy. I thought maybe haptic feedback in power saving could be the cause but it isn't.
Edit: Tried again for the hell of it and this time I pointed to the cwm touch apart of ezrecovery and not the custom option by chossing the file and it now works.
All of that said rom manager and the cwm touch don't seem to work well together(im guessing unless you purchase
?) When you make a backup manually from going into recovery rom manager doesn't see it. CWM Touch also doesn't see the recovery made from non touch made in rom manager. Also Clockwork mod also still shows recovery as cwm 4.8.4.9
I'm relatively experienced in flashing roms but not ALL things root so this could be normal and just how things work.
Smart alert, still doesn't work.
I wanna flash Touch through Odin (unless there's an easier way) but will having regular clockwork installed hurt anything if I flash?
Sent from my SCH-I535 using xda app-developers app
Flash touch over regular cwm via ez recovery. It's fine. Don't use odin to flash recovery.
Thanks! Did that and it worked!
Sent from my SCH-I535 using xda app-developers app
FYI...it would be better if you ran CWM 6.0.1.0 instead of CWM Touch...ive had better results with the newer version, if you're interested in trying it out.
I actually used CMW to flash 6.0.1.2 over 6.0.1.0 as opposed to using EZ recovery. I used EZ Recovery to get 6.0.1.0 on the phone in the first place. I do this because the first S3 I tried to use the custom option in EZ Recovery on was soft bricked upon flash completion.
t h turkick
shangrila500 said:
I actually used CMW to flash 6.0.1.2 over 6.0.1.0 as opposed to using EZ recovery. I used EZ Recovery to get 6.0.1.0 on the phone in the first place. I do this because the first S3 I tried to use the custom option in EZ Recovery on was soft bricked upon flash completion.
Click to expand...
Click to collapse
Agreed, just use the CWM ROM Manager app to flash on the most current 6.0.1.2. You can also flash most recent touch recovery through the app as well, that option is at the bottom. I use the touch while I am using ICS roms, but when I start playing with JB developments, I flash back to 6.0.1.2 standard recovery. Though I have not experienced any issues with touch and JB, the developers warn in bold to not use it with JB roms. CWM is updated more frequently than the EZ recovery app, and why use an outside source to flash CWM anyways? EZ recovery is good to start out with because of its different recovery options, but ultimately is not better that the actual recovery source app CWM.
I have been flashing (roms) for a while now devices including G2, HTC Hero, HTC Thunderbolt, Moto Razr, and now Galaxy S3. I don't typically post questions on any forums because I usually can find an answer with enough searching, it pains me to write this.
Problem: I can only flash certain roms on my Verizon SGS3.
I have no problem flashing unofficial aokp, unofficial cm10, and Synergy.
When I try to install different roms from xda and other websites i get the attached photo. These roms include paranoid android, miui, liquids jelly bean, and a few others.
My device is rooted, unlocked bootloader through ez unlock, running clockworkmod (touch) v5.8.4.5 via ez recovery.
Before I flash I always:
wipe data/factory reset
wipe cache partition
format system
wipe dalvik cache
Re-downloading has not fixed the issue. I'm sure im missing something simple any help would be warmly welcomed!
Thanks in advance all!
-Stumped S3 User
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
annoyingduck said:
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Bingo!! Wrong version of CMW, just download e-z flasher from the play store and use it to flash either TWP or CMW. Easy peasy quick and easy.
I suggest you use twrp.
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Cwm 6.0.1.2 all day. Refuse to use anything else lol. Unless amon ra gets ported
Sent from my SCH-I535 using Tapatalk 2
Worked like a charm!
I downloaded rom manager, installed latest clock work, updated to touch, and it is working perfect! Thanks to all! The fun begins
Wifi was working fine with CM12.1. I wonder why its not working in CM12.0 Since 12.1 had crash issues, I flashed it back to 12.0 for which wifi doesnt turn ON.
I cannot flash stock ROM/firmware anyway. Can anyone help? Thank You.
sivakrishnan said:
Wifi was working fine with CM12.1. I wonder why its not working in CM12.0 Since 12.1 had crash issues, I flashed it back to 12.0 for which wifi doesnt turn ON.
I cannot flash stock ROM/firmware anyway. Can anyone help? Thank You.
Click to expand...
Click to collapse
Explain the exact way of flashing please
Sent from my mint using XDA Free mobile app
sivakrishnan said:
Wifi was working fine with CM12.1. I wonder why its not working in CM12.0 Since 12.1 had crash issues, I flashed it back to 12.0 for which wifi doesnt turn ON.
I cannot flash stock ROM/firmware anyway. Can anyone help? Thank You.
Click to expand...
Click to collapse
Did you come from the latest firmware??
SdtBarbarossa said:
Explain the exact way of flashing please
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
I was using CM12.1 and due to crashes i decided to install CM12, and for easiness i flashed twrp recovery to FOTAKernal using TWRP Manager app.
But TWRP failed to install any rom, so i flashed stock firm (not latest) using flash tool.
Then using in fast boot mode, flashed Philz Recovery by command "fastboot flash boot <boot.img>"
got Philz Recovery and using that recovery installed CM 12.0
is this clear?
Did I had to install latest firmware before flashing CM12.0 to get wi-fi turned on?!!!
sivakrishnan said:
I was using CM12.1 and due to crashes i decided to install CM12, and for easiness i flashed twrp recovery to FOTAKernal using TWRP Manager app.
But TWRP failed to install any rom, so i flashed stock firm (not latest) using flash tool.
Then using in fast boot mode, flashed Philz Recovery by command "fastboot flash boot <boot.img>"
got Philz Recovery and using that recovery installed CM 12.0
is this clear?
Did I had to install latest firmware before flashing CM12.0 to get wi-fi turned on?!!!
Click to expand...
Click to collapse
Yes it must be latest stockrom!
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
Yes it must be latest stockrom!
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
thank you so much, i have clicked thanks,
well will you please tell me why we should use latest stock firmware, since we are wiping all data, change kernel etc using recovery?
just out of curiosity
I would like to know whether i can use its FOTAKernel for TWRP Recovery??
Once I failed to flash rom using twrp recovery..
sivakrishnan said:
thank you so much, i have clicked thanks,
well will you please tell me why we should use latest stock firmware, since we are wiping all data, change kernel etc using recovery?
just out of curiosity
I would like to know whether i can use its FOTAKernel for TWRP Recovery??
Once I failed to flash rom using twrp recovery..
Click to expand...
Click to collapse
1. because of some "invisible" partitions that must be up-to-date... Most important is "modemst" partition... You never touch them while flashing!
2.use the app by Corphish to get my TWRP .... Twrpmanager is ****ty
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
1. because of some "invisible" partitions that must be up-to-date... Most important is "modemst" partition... You never touch them while flashing!
2.use the app by Corphish to get my TWRP .... Twrpmanager is ****ty
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
flash the recovery zip through recovery after flashing the image file via flashtool!
if we flash using flash tool, it will lose after flashing another CM rom right? i need to get it for ever that's why I'm asking about flashing in to fotakernel.
thanks