Database Info

CWM recovery problems and how to install .img recovery files

Two questions:
1. How do i flash the new touch recovery without using rom manager (.img file from clockworkmod site)?
2. I installed the latest non touch recovery (with rom manager) but it's causing me problems. Every time i install a new rom I can't boot into recovery. I had to use LG flash tool to reinstall the stock v21e gingerbread and start all over again. Then i installed CM10 (which didnt work) and recovery didn't work again so i had to flash with LG flashtool again. Why is this happening?

With Cm10 I also had problem entering recovery, to enter recovery I've had to remove usb cable, then hold power button for 10sec( to have phone completely off) and then hold 3D+vold down+ power. Was releasing power when have backlight and holding buttons until entering recovery. Hope it will help. For me it works.
Sent from my LG-P920 using xda app-developers app

Have you tried an older recovery? I'm on CWM 5.0.2.0. Installed with Recovery Manager: http://forum.xda-developers.com/showthread.php?p=23474089

The older recovery works fine, but that's not the point. I cant think of a single reason why is this happening with the newest version.
So does anyone know how to flash those .img files? Maybe from terminal emulator?
Sent from my LG-P920 using xda app-developers app

Stinger2U said:
The older recovery works fine, but that's not the point. I cant think of a single reason why is this happening with the newest version.
So does anyone know how to flash those .img files? Maybe from terminal emulator?
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Yeah, you need to use Terminal emulator.
Instructions:
1. Put it on the root of the internal sdcard
2. Open Terminal App
3. Run :
Code:
su
Then
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
4. Reboot and now it would work !

^ Don't know why, but it didn't work for me. Maybe it's needed to install the regular non-touch recovery and then the touch one?
Edit: Nope, that wasn't it. Is CWM 6.0.1.9 for our phone broken? I can't get it to work whatever I try (Recovery Manager or flashing thru Terminal). So I got back to CWM 5.8.1.5 Touch.

I managed to get the latest recovery running. But as soon as I install another rom it stops working. Weird.
Sent from my LG-P920 using xda app-developers app

What are you using to install them? Cuz it sounds like you are installing some recovery in the system partition like the ics temp ones
Sent from my LG-P920 using xda app-developers app

idriff said:
What are you using to install them? Cuz it sounds like you are installing some recovery in the system partition like the ics temp ones
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I used rom manager and terminal emulator. I still haven't tried the latest touch recovery. I'll keep the older version until this gets fixed.

Stinger2U said:
I used rom manager and terminal emulator. I still haven't tried the latest touch recovery. I'll keep the older version until this gets fixed.
Click to expand...
Click to collapse
i have the same problem with my p920, flashing the newest CWM 6.0..1.9 and trying to reboot into it bricks the device...
i wanted to try out CM10, but i'm stucked on the lg logo after flashing it ( http://forum.xda-developers.com/showpost.php?p=35439373&postcount=721 )

At first this thread in the wrong section .
Try this (it's toooo easy) . It worked for me (in GB ) :-
http://forum.xda-developers.com/showthread.php?t=1598320
And about flashing the .img . you can flash the .img with omap4boot when the phone in fastboot mode ( this what you should do with ICS) .
Maybe change the twrp.img or cwm.img with the recovery you want to flash . Maybe I'm not sure .
Sent From My P920 (ICS ported)
Hit Thanks Button If I Helped

I had the same problem.
The latest CWM recovery (6.0.1.9) bricked my phone upon restart.
I had to flash a new rom to get it working, tried to entrer CWM recovery and it bricked again.
Finally reverted to stock recovery, i'm thinking about flashing CMW 5 again.
Can someone tell me which is the latest 5 version?

^ 5.8.1.5 Touch.
I couldn't make CWM 6.0.1.9 to work (non-touch and touch). Managed to boot into it temporarely, but that's all.

i am using CWM 6.0.1.9 with no problem. it works fine, also i am using CM10.

Corvus Corax said:
^ 5.8.1.5 Touch.
I couldn't make CWM 6.0.1.9 to work (non-touch and touch). Managed to boot into it temporarely, but that's all.
Click to expand...
Click to collapse
Thanks Corvus.
Can you or someone else tell me where to download the non-touch version of it?
I've searched through xda and google and could not find it.

daniel.mota said:
Thanks Corvus.
Can you or someone else tell me where to download the non-touch version of it?
I've searched through xda and google and could not find it.
Click to expand...
Click to collapse
I think that you can find it in the Recovery Toolkit here: http://forum.xda-developers.com/showthread.php?p=24820818

Corvus Corax said:
I think that you can find it in the Recovery Toolkit here: http://forum.xda-developers.com/showthread.php?p=24820818
Click to expand...
Click to collapse
I used that one to flash stock recovery, it works great.
But I think it includes CWM Recovery version 5.2.0.7, not 5.8.1.5.

daniel.mota said:
I used that one to flash stock recovery, it works great.
But I think it includes CWM Recovery version 5.2.0.7, not 5.8.1.5.
Click to expand...
Click to collapse
It's possible. I didn't use non-touch recovery in a while.

Corvus Corax said:
It's possible. I didn't use non-touch recovery in a while.
Click to expand...
Click to collapse
I prefer non-touch, I find it more reliable.

If you have any problems with ClockworkMod 6.0.1.9
You can not install the CM10 or Jelly Bam
You have the bootloader locked.
I had the same problem and I unlocked the bootloader.
Now everything works perfectly.

Update CWM

I've searched and Googled... I can't find this at all. How do I update my CWM?? I'm on 6.0.2.3. I hear there is a 6.0.2.8
Sent from my S3 via Taptalk

If you haven't already, download Rom Manager from the play store here.
Open the app, and go to the Recovery Setup section and you can update it from there.

Try this
http://forum.xda-developers.com/showthread.php?p=38962551
Also IDF you want to try twrp you can get goo app and select menu then update recovery.
Sent from my SCH-I605 using xda premium

Delete.

Can anyone please provide me with the latest s3 Verizon CWM Touch 6.0.2.8 odin flashable tar file?
Thanks in advance!

I made tar.md5's here of 6.0.2.8 for you guys of both touch and regular, you can get them here
http://invisiblek.org/sch-i535/recoveries/
I'm going to recommend that you DO NOT use the dd method posted above. Its dangerous. If you were to type the wrong partition, you could very easily brick your device.
If you want to use an img, use heimdall to flash it, otherwise create a tar/tar.md5 and flash it with odin
Or use rom manager
Or....find some other way....dd is dangerous http://en.wikipedia.org/wiki/Dd_(Unix)

Patr1ck. said:
If you haven't already, download Rom Manager from the play store here.
Open the app, and go to the Recovery Setup section and you can update it from there.
Click to expand...
Click to collapse
+1
Definitely the easiest method! Just did it two days ago using this method
Its free for the non touch version, or like $1 or $2 for the touch version, well worth it!
Sent from my SCH-I535 using xda app-developers app

invisiblek said:
dd is dangerous http://en.wikipedia.org/wiki/Dd_(Unix)
Click to expand...
Click to collapse
Wow, did not know that.
Sorry for posting a dangerous method to flash a custom recovery.
Its been deleted.
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
I have always used the dd method to flash recoverys to my phone, but I always make sure everything is typed correctly in terminal emulator before I press enter. With this new information I will no longer use dd commands for anything.
Thanks invisiblek for the info.
Sent from my SCH-I535 using xda app-developers app

I just updated via ROM Manager to Clockwordmod 6.0.2.9 and once I booted into recovery and did a backup, I was unable to reboot the system. I was able to reboot the phone via power + home button power on and installed Clockworkmod Touch 6.0.2.9. I also had the same problem with Clockworkmod touch where it wouldn't reboot the phone.

powells85 said:
I just updated via ROM Manager to Clockwordmod 6.0.2.9 and once I booted into recovery and did a backup, I was unable to reboot the system. I was able to reboot the phone via power + home button power on and installed Clockworkmod Touch 6.0.2.9. I also had the same problem with Clockworkmod touch where it wouldn't reboot the phone.
Click to expand...
Click to collapse
I had the same problem. Neither version of 6.0.2.9 CWM works. I had to restore back.
Sent from my SCH-I535 using Tapatalk 2

I had to restore back.
Click to expand...
Click to collapse
how?

For those getting stuck in recovery loop...
Reboot in odin (power+volumedown+home) and select cancel.
Tokedup found this link for previous versions...use ez recovery to flash img files.
http://forum.xda-developers.com/showthread.php?t=2096735

is this a known issue with the latest CWM? i ran into the recovery loop, too.

Using EZ Recovery and those recovery img files at that link work for me to get an older recovery installed. Also verified that I can successfully reboot the phone from recovery again.

Mikecolorama said:
is this a known issue with the latest CWM? i ran into the recovery loop, too.
Click to expand...
Click to collapse
Version 6.0.2.9 for our phone is bad. Use an earlier version.

ROM manager says 6.0.2.8 is the newest version our phone supports
Sent from my SCH-I535 using xda app-developers app

I downloaded 6.0.2.8 tar md5 from rootzwiki and used Odin to go back. ROM manager says there is a 6.0.3.0 now but I'm waiting on that until I hear that its good.
Sent from my SCH-I535 using Tapatalk 2

Eric021 said:
I downloaded 6.0.2.8 tar md5 from rootzwiki and used Odin to go back. ROM manager says there is a 6.0.3.0 now but I'm waiting on that until I hear that its good.
Click to expand...
Click to collapse
Its good. Used it a few times today. No problems

OK thanks I'll try it.
Sent from my SCH-I535 using Tapatalk 2

invisiblek said:
I made tar.md5's here of 6.0.2.8 for you guys of both touch and regular, you can get them here
http://invisiblek.org/sch-i535/recoveries/
I'm going to recommend that you DO NOT use the dd method posted above. Its dangerous. If you were to type the wrong partition, you could very easily brick your device.
If you want to use an img, use heimdall to flash it, otherwise create a tar/tar.md5 and flash it with odin
Or use rom manager
Or....find some other way....dd is dangerous http://en.wikipedia.org/wiki/Dd_(Unix)
Click to expand...
Click to collapse
When flashing with Odin, I enter in PDA, correct? Thanks.
Sent from my SCH-I535 using Tapatalk 2

[REF] List of Custom Recoveries (3-08-14)

Custom Recoveries​
This is the most recent list of recoveries for the SCH-i535 Verizon galaxy S3. I will be keeping this up to date to make it easier to find the most recent recoveries for our device.
Installation
CWM and TWRP are .img files and are easiest to install from EZ Recovery or Flashify apps from the play store.
​EZ-Recovery
​Flashify
Philz is installed by either using odin to flash the .tar.md5 file or by flashing the zip in recovery.
Safestrap is installed through an application.
I don't hold any responsibility of what happens to your phone due to flashing these.
Clockworkmod Recovery
Clockworkmod 6.0.4.3 - 10-21-13
Clockworkmod 6.0.4.5 - 1-1-14
Clockworkmod Touch Recovery
Clockworkmod Touch 6.0.4.3 - 10-21-13
Clockworkmod Touch 6.0.4.5 - 1-1-14
TWRP Recovery
TWRP Recovery 2.6.3.0 - 10-21-13
TWRP Recovery 2.6.3.1 - 11-24-13
TWRP Recovery 2.7.0.0 - 3-08-14
Philz Touch Recovery
Advanced CWM Recovery
Philz Touch Recovery 5 - v. 5.15.0 - CWM 6.0.3.7 - 10-21-13
Philz Touch Recovery 6 - v. 6.15.4 - CWM 6.0.4.7 - 2-13-14
Safestrap Recovery
Only use on VRUCML1 base! Modified TWRP with sdcard partitioning ability for custom roms on locked bootloaders.
Safestrap Recovery - TWRP 2.6.3.1 - 1-10-14
Updating the Update-Binary
If you receive a status 7 error when flashing a zip in recovery, pull the update binary from the latest CM nightly. This should be resolved in Philz Recovery as it automatically works around it, but may throw errors in the latest CWM recovery.
Here's how to replace the file:
Unzip the folder
Navigate to META-INF/com/google/android
Replace the older update-binary with the newer one
rezip
This will allow files to flash on the newer recoveries until all developers update the binary on their own zips, or a fix is in place.
I want to thank @andybones for giving me this idea, and giving me permission to make an updated thread.
I also want to thank all the developers of these great recoveries.
I don't always have time to check and see when these are updated, so if someone could reply to this thread or PM me when there's an update that would be great. I'll provide a link for it and update the thread.

Thank you ever since i flashed an aosp rom and created that stupid 0/ folder i javent been able to flash a new recovery. Stuck on TWRP 2.6.0.0 for months
Sent from my SCH-I535 using Tapatalk

DROID3R said:
Thank you ever since i flashed an aosp rom and created that stupid 0/ folder i javent been able to flash a new recovery. Stuck on TWRP 2.6.0.0 for months
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I used flashify to upgrade my recovery from TWRP 2.5.0 to 2.6.3 just fine.
Sent from my Verizon Wireless Samsung Galaxy SIII, via Tapatalk.

Flashify works fine, I just recommend ez recovery because the interface is very simple and it's made for flashing recoveries only.
It's also made for this specific phone model only and it flashes recoveries more reliably and without any hiccups that I've seen with other recovery apps. I think it's very well made despite it being over a year old.
Sent from my SCH-I535 using Tapatalk 2

For some reason when I've used ez recovery, it didn't change my recovery version.
Sent from my SCH-I535 using XDA Premium 4 mobile app

InfantryMarc said:
For some reason when I've used ez recovery, it didn't change my recovery version.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought it was me. Mine did the same thing. I don't know if it flashed it or not.
Sent from my Ktoonzified PACmaned SGS3!

Mine says flash successful and to reboot to recovery and when I do, it says recovery version 6.0.3.0
Sent from my SCH-I535 using XDA Premium 4 mobile app

InfantryMarc said:
Mine says flash successful and to reboot to recovery and when I do, it says recovery version 6.0.3.0
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sometimes it does that, I usually flash from my internal card and that fixes the problem, try moving the file and try again.
You can tell it was successful because it takes a second to flash, if it doesn't work the notification flash successful will come up instantaneously.
Sent from my SCH-I535 using Tapatalk 2

It doesn't even show up from the internal SD card when I'm in recovery. I've tried using ez and flashify and both say the same thing but same results. I've even tried downloading it from the website and it won't even download the img file
Sent from my SCH-I535 using XDA Premium 4 mobile app

InfantryMarc said:
It doesn't even show up from the internal SD card when I'm in recovery. I've tried using ez and flashify and both say the same thing but same results. I've even tried downloading it from the website and it won't even download the img file
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Some browsers don't download the file properly, I use Chrome and it works. You should be able to move it to your internal SD card, find it by hitting the ellipses next to custom, and flash it.
If you still can't do it, there's a tar file on their website that you can use to ODIN flash.
Sent from my SCH-I535 using Tapatalk 2

Prolly just do it that way. Will it erase my ROM and all that or will it be safe? Haven't ever reflashed a recovery after being rooted
Sent from my SCH-I535 using XDA Premium 4 mobile app

InfantryMarc said:
Prolly just do it that way. Will it erase my ROM and all that or will it be safe? Haven't ever reflashed a recovery after being rooted
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't touch the rom, only the recovery.
Sent from my SCH-I535 using Tapatalk 2

Thanksm had to use Odin to flash the update. Worked like a charm guess I'll have to use that way in the future
Sent from my SCH-I535 using XDA Premium 4 mobile app

Does anybody know of a recovery that will work with a new Verizon GS3? I just got an insurance replacement that is brand new. I can't find a recovery that will mount the internal or external SD card. I was able to root, unlock the bootloader, and install a custom recovery but neither TWRP or CWM will mount the SD cards (or any partitions that I can tell).
It sounds like the guys with the Sprint GS3 have figured it out and I'm wondering if anybody has a modified recovery for the Verizon GS3. Here's the Sprint forum about this issue. http://forum.xda-developers.com/showthread.php?t=2391616
Any help would be appreciated. I miss my CleanRom!

Durangodude said:
Does anybody know of a recovery that will work with a new Verizon GS3? I just got an insurance replacement that is brand new. I can't find a recovery that will mount the internal or external SD card. I was able to root, unlock the bootloader, and install a custom recovery but neither TWRP or CWM will mount the SD cards (or any partitions that I can tell).
It sounds like the guys with the Sprint GS3 have figured it out and I'm wondering if anybody has a modified recovery for the Verizon GS3. Here's the Sprint forum about this issue. http://forum.xda-developers.com/showthread.php?t=2391616
Any help would be appreciated. I miss my CleanRom!
Click to expand...
Click to collapse
both of the recoveries you mentioned will work, but you must ensure its the latest version.
Sent from my SCH-I535 using Tapatalk

Thread updated, new TWRP version.

never had a prob with clockwork mod thusfar.... until tonight actually ha

Durangodude said:
Does anybody know of a recovery that will work with a new Verizon GS3? I just got an insurance replacement that is brand new. I can't find a recovery that will mount the internal or external SD card. I was able to root, unlock the bootloader, and install a custom recovery but neither TWRP or CWM will mount the SD cards (or any partitions that I can tell).
It sounds like the guys with the Sprint GS3 have figured it out and I'm wondering if anybody has a modified recovery for the Verizon GS3. Here's the Sprint forum about this issue. http://forum.xda-developers.com/showthread.php?t=2391616
Any help would be appreciated. I miss my CleanRom!
Click to expand...
Click to collapse
Make sure you are on the newest version. They both work.
Sent from my SCH-I535 using xda app-developers app

Thread updated, official Philz touch recovery is now supported for our device! Give it a try if you like CWM recovery.

I can't flash any roms with Philz recovery. Will edit with more info in a moment.
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 02:07 PM ---------- Previous post was at 01:57 PM ----------
FingersMcGee7 said:
I can't flash any roms with Philz recovery. Always get :
Assert failed: get prop("to. Product. Device")
E: error in /data/media/0/download /pac-d2vzw-nightly-20131228.zip
What's going on here?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SCH-I535 using XDA Premium 4 mobile app

Softbricked One Mini

so I've got a interesting situation. A friend managed to softbrick his Mini. I don't know how he got it in this state, but, it has TWRP installed, its copy of android does not boot, and it's S-ON. I played with RUUs for a few hours and couldn't get any of them to work. If I can get any working copy of android on it I can then get S-OFF and fix it. As far as I see there's two routes to fix this.
-Get S-OFF without using android
-Get a android ROM on there without S-OFF.
I pretty much have access to fastboot and twrp that can't flash Roms because of s on. Recoveries also have errors about mounting /system or /cache.
Any help in fixing this would be appreciated.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Adding abit more information, I tried using a RUU but get errors because of firmware version. When I get the rom.zip out of the RUU and try to use fastboot to flash it, on windows I get a error about header errors (error 32). On Linux I get errors about the file is too large.
Also, nomatter what recovery I can try, neither can mount either /system or /cache unless you format them, then after a reboot they cant be mounted again.

I had an issue where my os was completely wiped after a botched update attempt. Lol I went through every possible I could think of or find until I see something about using an external drive. So what I did was use fastboot to flash a recovery, which you already have which is good. And then from there I used an OTG cable, and connected my USB drive to it, which had a ROM zip on it and flashed it. It worked. I am bootloader unlocked but not s-off. But as long as you have a recovery you can do this. I actually wasn't even rooted.
Sent from my One Mini using XDA Premium 4 mobile app

dizzyman1180 said:
I had an issue where my os was completely wiped after a botched update attempt. Lol I went through every possible I could think of or find until I see something about using an external drive. So what I did was use fastboot to flash a recovery, which you already have which is good. And then from there I used an OTG cable, and connected my USB drive to it, which had a ROM zip on it and flashed it. It worked. I am bootloader unlocked but not s-off. But as long as you have a recovery you can do this. I actually wasn't even rooted.
Sent from my One Mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm still worried about the failing to mount /system and /cache errors. Did you have those as well?
Sent from my HTC6525LVW using XDA Premium 4 mobile app

polaric said:
I pretty much have access to fastboot and twrp that can't flash Roms because of s on.
Click to expand...
Click to collapse
You don't need S-OFF to flash roms. As long as you unlocked the bootloader you can fastboot-flash boot, system and recovery. And so you can flash ROMs when in recovery mode.
polaric said:
I'm still worried about the failing to mount /system and /cache errors. Did you have those as well?
Click to expand...
Click to collapse
What HBOOT version do you have?

morschesholz said:
You don't need S-OFF to flash roms. As long as you unlocked the bootloader you can fastboot-flash boot, system and recovery. And so you can flash ROMs when in recovery mode.
What HBOOT version do you have?
Click to expand...
Click to collapse
HBOOT is 2.22
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Well, then it looks like the same issue as in the thread next to this one. So please go over there and perhaps you'll try my next steps written down there: http://forum.xda-developers.com/showthread.php?p=51737651

morschesholz said:
Well, then it looks like the same issue as in the thread next to this one. So please go over there and perhaps you'll try my next steps written down there: http://forum.xda-developers.com/showthread.php?p=51737651
Click to expand...
Click to collapse
I followed that and it got me a working recovery, but both twrp versions and the cwm version won't flash the cm zip, regardless if its modified, if I modify it myself or use a attached update-script. Both recoveries simply say "Failed to flash zip".
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Then you should repeat the flashing and have a look at the recovery log right after it. At TWRP it's located at /tmp/recovery.log (don't know for CWM).
Either do a
Code:
adb shell cat /tmp/recovery.log
or pull it to your pc:
Code:
adb pull /tmp/recovery.log

morschesholz said:
Then you should repeat the flashing and have a look at the recovery log right after it. At TWRP it's located at /tmp/recovery.log (don't know for CWM).
Either do a
Code:
adb shell cat /tmp/recovery.log
or pull it to your pc:
Code:
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
Already tried multiple times, of course. I looked at the log and didnt see anything of value though. I can post it if you like.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

That's what I recommended in another post:
morschesholz said:
Meanwhile you could try flashing CM11. There is an edited updater-script and boot.img over here: http://forum.xda-developers.com/showthread.php?p=51613028
I used it with cm-11-20140403-NIGHTLY-m4 successfully. Maybe the edited script works with newer versions of the CM nightlies as well, but I didn't test that yet.
Click to expand...
Click to collapse

This is the 0403 CM11 nightly I modified to match the new partition layout: https://dl.dropboxusercontent.com/u/5035075/m4kk/cm-11-20140403-NIGHTLY-m4kk.zip
You should be able to flash it with the modified version of TWRP 2.7.0.5

[Q] Any tips how to get CWM working?

Hello guys, this is my first post on xda forums!
I've got a question. I rooted my Moto G XT1032 with flashing superSU through CWM 6.0.4.7. After reboot, CWM offered me some options about fixing recovery, I just ignored it, selected no to every option. After reboot I had root access. For some unknown reasons, I am not able to do nandroid backup when I reboot to recovery. It looks like it is backing it up somewhere, but I cannot see it anywhere on my "sdcard". BTW, I choosed CWM because TWRP is extremely buggy, for my finger size unusable :laugh: . Thanks guys for every reply!!!
Oh, btw, CWM still offers me some "root fixes" when I try to reboot...

CWM ask you to fix root you should accept try flashing su again, try philz touch recovery
Enviado desde mi XT1033 usando Tapatalk 2

Feliox said:
Hello guys, this is my first post on xda forums!
I've got a question. I rooted my Moto G XT1032 with flashing superSU through CWM 6.0.4.7. After reboot, CWM offered me some options about fixing recovery, I just ignored it, selected no to every option. After reboot I had root access. For some unknown reasons, I am not able to do nandroid backup when I reboot to recovery. It looks like it is backing it up somewhere, but I cannot see it anywhere on my "sdcard". BTW, I choosed CWM because TWRP is extremely buggy, for my finger size unusable :laugh: . Thanks guys for every reply!!!
Oh, btw, CWM still offers me some "root fixes" when I try to reboot...
Click to expand...
Click to collapse
1)Your CWM Backup is Saved To Data/media/Clockworkmode (into the internal Directory)
2)In CWM Every time you have to select Yes To Fix Root... No Need To Flash supersu again and again.

My root always works, even if I do not choose to fix root, lol.
But i'll flash the phils recovery... Is it just normal process using fastboot flash recovery?
Sent from my Nexus 7 using XDA Free mobile app

Feliox said:
My root always works, even if I do not choose to fix root, lol.
But i'll flash the phils recovery... Is it just normal process using fastboot flash recovery?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Yes...
Fastboot flash recovery recovery. img
(Where recovery. img is ur philz recover name)

Thanks a lot
Sent from my Nexus 7 using XDA Free mobile app