Database Develop

[Q] CWM - Failed to mount /recovery

I just rooted and got everything up and running again. I have ClockworkMod installed and I am trying to do a backup now, but I get an error. Here is what it says during/after the backup:
SD Card Space free: 7568MB
.
Backing up Boot.....
.
Backing up Recovery.....
.
E:FAILED to mount /recovery ( Block device required )
.
Can't mount /recovery!
.
END
What could this mean and what can I do to fix it ? I dont even see a /recovery mount point.
Please advise !

Did you do it using IOMonster's root pack and install CWM using his zip? If so, you can try flashing CWM through ROM Manager. I'm having the exact same issue and nothing is working for me, but most seem to be able to flash CWM through RM and it's fixed.

eyecrispy said:
Did you do it using IOMonster's root pack and install CWM using his zip? If so, you can try flashing CWM through ROM Manager. I'm having the exact same issue and nothing is working for me, but most seem to be able to flash CWM through RM and it's fixed.
Click to expand...
Click to collapse
Yes I used his CWM zip. I have tried via Rom Manager and get the same result's. The only thing that is different is that IOMonster's recovery is using 3.0.0.5 and When I installed Rom Manager it downloaded 3.0.0.7 but then when I tried a backup via CWM the recovery changed back from 3.0.0.7 to 3.0.0.5 Not sure what thats about, but I dont see any reason why it cant find or mount the restore dir.
Im lost :O( I need to make a ROM backup !

I am in the exact same place you are. IOMonster says he's uploading a new version of his root pack tonight that will include a new flashable CWM. I'm hoping it'll work for me. If not, i'm going back to stock and rooting with autonooter to see if that fixes it. Did you root with IOMonster's root.zip? Or just his CWM?

eyecrispy said:
I am in the exact same place you are. IOMonster says he's uploading a new version of his root pack tonight that will include a new flashable CWM. I'm hoping it'll work for me. If not, i'm going back to stock and rooting with autonooter to see if that fixes it. Did you root with IOMonster's root.zip? Or just his CWM?
Click to expand...
Click to collapse
I rooted with IOMonster's root.zip I also used his gapps and block1.1 script's ... then I installed his CWM.
I wish someone can help us ! please let me know if you find a solution.

Stuck booting into recovery

SO i was running nook color version 1.1.0 and i used the autonooter to get clockwork installed. I then tried to use the monster rootpack to install phiremod but after it says install is complete i rebooted but now every time i reboot it goes directly to clockwork and i cant get it to boot up normally. is there anything i can do besides a restore to stock to install phiremod/cm7 or exit recovery? BTW i did remove the monster sd card so thats not the reason its booting that way....

When booted to CWR, use adb:
adb shell
Check that rom is mounted with:
mount
You should see /rom somewhere in the returned result.
If it's mounted, do:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
If not:
mkdir /rom
mount /dev/block/mmcblk0p2 /rom
Then use previous command.
If that doesn't help, you can always flash my cwr remover .zip, found on my nook color restore to stock thread.
Sent from my HTC Desire using XDA App

thanks im going to try that right now.

So i am trying to run adb but it says device not found and i cant figure out how to get the device to mount

I had the same thing happen. In recovery, install the zip file in this post to remove recovery and keep it rooted. You will then be able to reboot normally.
http://forum.xda-developers.com/showthread.php?t=914690
I read that it does that with autonooter 3.0. What you need to do is reboot normally after flashing recovery (don't reboot into recovery immediately after flashing). Afterwards you can reboot into recovery.

Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.

krisslake said:
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
Click to expand...
Click to collapse
Not really sure what you are saying was your problem. But I have a lot of solutions to booting problems in my nook color tips thread linked in my signature. See items A8 and A12. And there is my partition repair thread.
Sent from my BNTV400 using Tapatalk

[Q] Can't boot phone after flashing CM9

Hello everyone,
I've tried to install CM9 on my Samsung Galaxy S I9000. However, I must have done something wrong in the process. I'm totally new to the whole custom ROM thing. I'll try to list the steps I performed to install CM9. I hope someone can point out where I went wrong.
Generally, I followed the instructions given in http://forum.xda-developers.com/showthread.php?t=1363593 .
1) Installed "ROM Manager" (https://market.android.com/details?id=com.koushikdutta.rommanager&hl=de).
2) Rooted my phone according to the instructions in http://androidadvices.com/root-samsung-galaxy-gt-i9000-android-234-xxjvr-firmware/3/ . This uses Odin 3 v1.7 and also installed CWM Recovery (v3.0.0.5) . I checked that my firmware exactly matches the one for which the description is for.
3) Performed a backup using CWM Recovery.
4) Performed wipe (data/factory reset AND cache).
5) Installed CM9 using CWM which I had downloaded from the links given in the thread given at the beginning and placed the four .zip files (CM9, Google apps, Google apps fix and Faceunlock) on my external SD card. I only realized afterwards that the instructions said to place them on the internal SD card.
6) Installed Google apps, Google apps fix and Faceunlock using CWM.
7) Selected reboot in CWM. However, the device didn't boot into Android. First I saw the CM logo screen, then the phone got stuck on the "Samsung Galaxy S I9000" screen.
8) Read instructions again, realized that I forgort the wipe after installing Google apps. Performed the two wipes again, however the problem remained.
9) Read instructions again, realized that I was supposed to install the .zip files from the internal SD card. I assumed that was the step I went wrong. So I decided to restore to my stock ROM which I had backup'ed before. I used the restore option in CWM, selected my previous backup (located on external SD card) and performed the restore.
10) However, the phone still does not get pass the "Samsung Galaxy S I9000" screen. When I boot into CWM, the following appears on my screen
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:Unable process volume! Skipping...
Checking /cache...
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:Unable to process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
The same apperas if I try to do a "restore" from CWM again.
My questions:
1) Where did I go wrong?
2) What must I do to be able to attempt to install CM9 again?
Thanks in advance!

To get back to stock you have to flash a 3 file stock rom with repartition in odin.
i think the best is to get back stock, if you tried to restore a backup. then flash semapore kernel.
Then boot in recovery, wipe. Flash build 12 and gapps then reboot.
Sent from my GT-I9000 using Tapatalk

Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?

oxyris said:
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
Click to expand...
Click to collapse
First take a look in ramads thread: http://forum.xda-developers.com/showthread.php?t=1102881
1. Here you can read how to flash with odin and download the latest gingerbread stock rom
2 your backup will work, but you have to be on a stock rom first.
3. read how to flash with odin in the link.
4. Semapore kernel is a custom kernel, comes prerooted and stuff.
so after you are back stock you can flash this in odin, put it in pda and dont thick repartiton. No you are ready again. turn of phone, boot into recovery mode with 3 button combo, here you can restore your backup if you want. or wipe factory reset, wipe catche and dalvik catche flash build 12 and gapps from internal sd. reboot and enjoy ics http://forum.xda-developers.com/showthread.php?t=1112908 remember to download the correct kernel for your build.
5. hard to say, the best way to get correct cwm is to flash a kernel as semapore or cf root. maybe it was somthing with your cwm (recovery)
Edit: it take some time to boot the first time

Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?

oxyris said:
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
Click to expand...
Click to collapse
its not the newest. you should have thick repartition and 512 pit here. But if the phone boots up i think its ok. only kernel flash its important not to thick repartition.
its best to use this kernel http://download.chainfire.eu/124/CF-Root/SGS/CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip

I tried flashing CM9 again with the Semapore kernel I had installed first. It seemed to work, however, after booting into CM9, a screen appeared that said something like "Device encryption failed" and I could not get into the OS. Any idea what that could have been?
I'll give it another try anyway, this time with repartitioning and PIT when flashing the stock ROM and with the other kernel you suggested.

Slightly off topic, but what's with this obsession about 3 file roms that's been going around for a long time? I have yet to see any evidence to support the belief that 3 files rom is someone better than single file rom.
@OP: Try flashing CM7 first. See if that works. Then flash CM9.

So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
edit2: According to the CM7 thread (http://forum.xda-developers.com/showthread.php?t=1061946), "you're not able to flash any kernel or run any filesystem you want". So which kernel can I use?

oxyris said:
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
Click to expand...
Click to collapse
Hi,
I'll get 3 weeks ago SGS in a bottloop after flashing CM9 build11 (teamhacksung's) from latest CM7.
I went mad four about few hours, afterthat I decided to reflash stock 2.3.6 (JVX_JV3_JVT.tar).
After flashing with Odin, I end-up with in DBDATA error after rebooting..
So I flashed dbdata.rfs.tar and I've got original 2.3.6 working.
So:
-I've rooted my device again (CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar)
-Installed ROM manager
-Rebooted into recovery
-Flashed ICS port latest builds + GApps + face unlock (and wiped ALL).
No my device is working with ICS,
hope this will help you guys on flashing ICS and don't waste time.
Cheers

Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
Phone unnecessarily gets data connection on device encryption password enter screen.
Click to expand...
Click to collapse
But I'm not sure if they're referring to my particular problem.

oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
May be the only way is to wait devs to solve that issue.
I'm so sorry that my tips didn't work 4 u...

oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
One question, do you have your SD Card in your phone when you are going through the install process? If so, take that out before flashing anything. It has been the cause of problems for a lot of people coming to CM9.

Hi, thanks for your replies.
I seem to have solved the issue. When the "device encryption unsuccessful" screen appeared, I booted to recovery using the power button (a menu will appear letting you choose between shut down, restart or recovery) and came into CWM. There, I wiped everything (i.e. factory, cache and dalvik or whatever its called) and rebooted. I could then start the OS without any further problems (until now).
I also noticed that now my internal SD card is actually "clean" again, i.e. it only contains the folders and files that are there when you get your phone new. This wasn't the case when I performed a wipe BEFORE flashing CM9.
I'm using the CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar kernel you suggested, maybe that was the problem (I can't recall being able to boot into recovery the first time the "device encryption unsuccessful" screen appeared).
@ryanmat Yes, I did have my external SD card in the phone during the installation process, but thanks for your suggestions.
edit: I will report back if everything goes smooth for a few days.

ok, let me understand...
now you got CWM working and you've got CM9 after wipe all with rooted kernel I suggest you?

Exactly. Let me write down the individual steps I finally performed to get CM9 running.
1) Get Odin and PIT files -> http://www.multiupload.com/51MTA5K1H7
2) Boot phone to download mode
3) Start Odin on computer
4) Connect phone to computer (USB)
5) Flash stock ROM -> http://www.multiupload.com/PKVWPJJZMO (check repartition, put in the 512 PIT file and select the PDA, PHONE and CSC files from the stock ROM, then hit start)
6) Disconnect phone from computer
7) Restart Odin on computer
8) Boot phone to download mode
9) Connect phone to computer (USB)
10) Flash the CF kernel for root access -> http://www.filesonic.ch/file/2356034801 (don't check repartition, no PIT file, select the downloaded tar file as PDA, then hit start)
11) Boot the phone to the stock ROM. After the kernel was flashed, you should have CWM installed. Place the CM9 tar, as well as the gapps, gappsfix and faceunlock tars in your internal SD card. Start CWM and boot into recovery from there.
12) In CWM recovery, select install zip from SD card and select the CM9 ROM. After the installation, my phone automatically rebooted, booted CM9 and got into the "encryption unsuccessful" screen.
13) Hold the power button, select reboot and then select recovery to get back into CWM recovery.
14) Perform factory reset, cache wipe and dalvik cache wipe (found under advanced).
15) Select reboot in CWM recovery, you should now be able to boot into CM9.
16) Reboot into CWM again and install gapps, gappsfix and faceunlock if desired.
I don't know if all of these steps are required or if they must be performed in this exact order. However, it worked for me (CM9 build 12).

and now build 13 is out...!!!

Error mounting data and cache

Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?

devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.

YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.

I belive I have the same probleme, how i could i do it right?

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.

I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!

Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.

devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...

berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.

Cannot install Xposed in Z3Compact? Read this.

Good Night,
First of all, I hope this will be of use to someone
I own a Z3 Compact which I rooted yesterday. I followed the steps detailed in here, and today I was getting ready to start using XPosed but I am unable to install it, since I am getting a nice :
SD Card: /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip...
Mounting /system writable...
mount: permission denied (are you root?)
Could not mount /system writable
Trying to continue anyway...
cp: can't create '/system/bin/
app_process.orig': Read-only file system
Failed to create a backup of /system/bine/app_process
Click to expand...
Click to collapse
I followed every step, even flashed the part specified at the FAQ that asks me to flash RICDefeat.zip
FAQ
- Some root apps don't work, because /system can't be remounted rw, what's up with that?
Sony has a special in kernel protection that disallow remounting /system read-write, even for root. Flash this in recovery (copy it to the sdcard and reboot in recovery with volume UP pressed, then install it): https://github.com/dosomder/SonyRICD.../RICDefeat.zip
Click to expand...
Click to collapse
So since I could not get through, even after following every step, opted for a different Installation Mode, to see if I could avoid that by flashing stuff instead
Installation Mode
Classical (write to /system directly)
Recovery (flash zip automatically)
Recovery (write zip to SD card, flash manually)
Click to expand...
Click to collapse
I've tried all three methods
- The first one throws that error
- The second reboots the phone without flashing a thing,
- The third one ... well, it says the following
SD card: /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip...
Copying Xposed-Installer-Recovery.zip...
Copying XposedBridge.jar...
Please flash Xposed-Installer-Recovery.zip from the SD card to complete the operation.
Click to expand...
Click to collapse
So then you just have to reboot in recovery, dig to that same folder and find in there the zip to flash.
Anyway, just posting this in case anyone has that same problem, because it has driven me crazy not being able to fix that /system non writable problem with Sony. geez....
Cheers

Thank you so much. It works for my Z3C Docomo (already flashed with US ROM - D5803_23.0.1.A.5.77_US.ftf).

Thanks!
I had another Z3c that broke and the installation was as smoth as possible, but i had unlocked bootloader and rooted by the old method (that needed BU).
I got a new phone from assistence and did the root without UB.. and got the same problem .. thanks for the "tutorial"

Alright so this fixes some issue you had with the actual flashing of xposed in TWRP? I'm assuming it doesn't fix the bootloop problem that happens if you don't wipe the cache between every restart?
I'm not sure I follow your original thread,or what you actually did to resolve whatever issue it is that you were having...

NeLk said:
Installation Mode
Classical (write to /system directly)
Recovery (flash zip automatically)
Recovery (write zip to SD card, flash manually)
I've tried all three methods
- The first one throws that error
- The second reboots the phone without flashing a thing,
- The third one ... well, it says the following
So then you just have to reboot in recovery, dig to that same folder and find in there the zip to flash.
Anyway, just posting this in case anyone has that same problem, because it has driven me crazy not being able to fix that /system non writable problem with Sony. geez....
Click to expand...
Click to collapse
I'm currently being driven crazy by Sony's ridiculous R/W restriction, so I'd like to be able to lift it. If I understand correctly, your thread is partially about that. I'm having trouble flashing RICDefeat from recovery.
I don't understand the difference between flashing a zip automatically and flashing it manually. The only method I know is copying to SD/internal memory, booting into recovery and install/flash zip from there. Which recovery did you use?

Thanks.
The latest XPosed Installer is missing last option, but I found the file downloaded at /sdcard/Android/data/de.robv.../cache/downloads/framework