Upon entering CWM, it says " E: unable to mount /cache/recovery/" etc..
my /cache/ folder is empty..
lockedbootloader SGP311 stock .370 firmware..
Last edited:
Upon entering CWM, it says " E: unable to mount /cache/recovery/" etc..
my /cache/ folder is empty..
lockedbootloader SGP311 stock .370 firmware..
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
Take any FTF of your ROM and use flashtool to wipe ONLY your cache. That will restore your cache partition.
You should see a folder lost+found at least there.
You might have run in to a CWM bug that I thought I fixed... Will have to dig deeper in to that it seems...
Sent from my C6603 using xda app-developers app
Could you try to use DooMLoRD's easy rooting toolkit to see it that works ok? His scripting is similar to mine with a similar files location.
If that works but mine doesn't then I'm stumped as I would not get why mine fails for you... Otherwise it could be a general incompatibility with your version of Windows...
Sent from my C6603 using xda app-developers app
Now it's okay after wiping the cache thru flashtool as you instructed..thanks..
wiping cache partition isn't working ..it freezes...and a reset will result to a corrupted cache..
Last edited:
I actually used his script for rooting and it worked.
Anyway, I tried again, it worked this time. Nothing changed on my end. I'm stumped too!
BTW, thanks. exFAT is a lifesaver! I can now load huge movies for my travels without having to recode them.
I hoped I fixed this behavior in 2.x but i guess I'll have to investigate it some more... it will be one of the biggest points of interest in the 2.6 BETA releases, besides fixing TWRP in landscape of courseNow it's okay after wiping the cache thru flashtool as you instructed..thanks..
wiping cache partition isn't working ..it freezes...and a reset will result to a corrupted cache..
I am guessing you had either pc companion, flashtool or a lingering adb running in the background while trying to install... that was my hunch anyway. Glad it worked in the end
Is it possible to create standalone version of TWRP, instead of bundling it together with CWM? No one really uses 2 recoveries, especially given the fact backup images are not cross compatible.
Yes, that would be possible but not everything works as good as it can in either recoveries, this package gives you the possibility to test/try in both.
If it's space you are worried about, this package in total takes up only 5 mb on your system partition and from the looks of it I might be able to decrease that once I merge then even more for 2.6...
Sent from my C6603 using xda app-developers app
This is more about not being able to boot TWRP at all. Instead of you spending time debugging it and me spending time to installer keyloggers I dont want to install and collecting several rounds of logs I thought it'd be much easier to create TWRP only zip
Actually, not at all... The keychecking testing is now completed and future proof. If Sony decides to change the key event node again the chance of XZDualRecovery not reading it is quite slim. We would have had the same issues with a TWRP only package as the keycheck does not work for 4.2.2 on the older release on the Xperia Z phone.
As it is now XZDualRecovery reads 7 event handlers at once, to cover all possible future changes.
Next is to merge the CWM and TWRP ramdisks to get the best of both to work as one trouble free solution with a dynamic way to get the info on the hardware and loading the correct themes as it assembles the boot process.
My goal is to have a solution which will work on any if not all Xperia products regardless of resolution or hardware and faultless in any case
Sent from my C6603 using xda app-developers app
I have flashed 2.5 Release and just like 2.5 Beta it boots into CWM and there is no way to access TWRP. I do have that default file with "twrp" in it, but it makes no difference. That's why I'm asking for standalone version of TWRP. If you don't want to do it can you please let me know how to get access to TWRP in the current 2.5 Release? I don't want to install any keyloggers on my tablet
You won't be able to use it anyway as it's orientation has not yet been fixed. So doing so would be completely pointless.
Then you will have to wait until I find someone who is willing to help out.
can install in SO-03E, but cannot boot to recovery even i pressed vol up during boot when the LED turns GreenIt should
Sent from my C6603 using xda app-developers app
That's a good thing... For me that is... There is a larger difference between the 311/312 and the 321/03E (these are basically the same)... Are you willing to help me out by running a test script to capture input events during boot?
Sent from my C6603 using xda app-developers app
Sure, please let me know how to help. cheers
forget to mentioned. that my SO-03E never vibrate during boot.
after i put the drdebug.sh in the folder and do a reboot, a XZDebug.log with zero bytes is created in the same folder.
the LED flashed blue once, and they it is docomo's boot animation, no vibration, no white LED flashes.
Last edited:
Oh wow... seems like NTT changed more then just the basics on the tablet, troubleshooting on the SO-02E (Xperia Z) was a breeze ... hmmm...
Can you send me the log from /tmp/XZDualRecovery ? I need to know what goes wrong in the preperation stage...
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone