Does NDRutils work ok to get in to twrp?@Nut I can't get into twrp using volume keys? Any idea? Thanks
Does NDRutils work ok to get in to twrp?@Nut I can't get into twrp using volume keys? Any idea? Thanks
ndrutils doesn't work on into twrp, but it could get into phil recovery. However the keys work now after I reinstalled ndrutils from play store. I removed that after I installed your recovery. Why do we need ndrutils now?Does NDRutils work ok to get in to twrp?
You don't but you might be using an older version?ndrutils doesn't work on into twrp, but it could get into phil recovery. However the keys work now after I reinstalled ndrutils from play store. I removed that after I installed your recovery. Why do we need ndrutils now?
Not really, using 2.7.94You don't but you might be using an older version?
What XZDR beta version did you install?
Not really, using 2.7.94
Yah... that is something I might want to change in the future... ahem...I installed this and i can't install ROMs on my Pollux_Windy because it says the device is Pollux, Help?
Got the same message - but i have the pollux and i get the error that my device is not the " " or not the pollux. was wondering what the problem is..Yah... that is something I might want to change in the future... ahem...
Anyway, if you want to install CM/AOSP rom's, please use the kernel provided with it to boot to the recovery to use for this. XZDR was never meant to be used for flashing non-stock-based ROM's.
made you a little video you can use in your OP if you like Dual Recovery install video-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia Tablet Z Questions & Answers thread!
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.
Currently supported XPERIA models:
These are also links to the device specific Q&A threads.
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543, D6563
Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
Xperia ZR: C5602, C5603, C5606
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322
Xperia Z3: D6603, D6633, D6643, D6653, D6616
Xperia Z3 Compact: D5803, D5833
Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651
To follow development, be sure to check the DevDB thread!
Grab the logs from either cache or sdcard1. Without them I can't help.My LED goes red on starting , not green . I have tried to reinstall but it is the same just wont go in. Any help appreciated
lol... niceAh OK, if I remove the SD Card the LED is green and I can get into Recovery, if the SD card is in I can't get in and LED is RED
Is there something I need on the SD card to get it to go in while SD card is in?
---------- Post added at 08:30 AM ---------- Previous post was at 08:13 AM ----------
OK ...all working now
I will tell you what happened. Yesterday I told tablet to shutdown and left for work. When I got home the battery was dead, so I placed on the charger. After 20 mins I notice the tablet was in a boot loop... it would not power off just came back on in boot loop sequence, nothing I could do would get it to boot. I read the 1st post here about the donotrun file, so I added one. This gave me the ability to get out of the boot loop and power down if required! I thought all was sorted. Then I tried to get into recovery, and I had the RED led not allowing me. I tried installing the new version , but still the same (SD card in with donotrun file) This morning after ejecting the SD, I can get into recovery. placing the sd card in (with donotrun file present) I cannot get into recovery. I renamed the donotrun to donotrun1 and now I can get into recovery. The tablet will now also power down without the boot loop... so I think I am all sorted.... just unsure why I had the boot loop in the 1st place?
is a version soon coming, who will support Lolipop? :=)lol... nice
You might have a broken/defective /system/bin/chargemon.stock file there. This is (or should be) the stock sony binary, which is supposed to hold the boot process when connecting the device to the charger in an off state. Removing this file will break your offline charging capabilities (the device then will just start up when a charger gets connected), if it gets damaged or replaced it can cause a kernel panic, which in turn explains the boot loop (as a kernel panic will always cause a reboot).
Thanks for v17==============================================
= =
= XZDualRecovery =
= Maintained by [NUT] =
= =
= For many Sony Xperia devices! =
= =
==============================================
Run the installer with sudo if it fails to connect to your device!
Choose an installation option:
1/ Installation on device rooted with SuperSU
2/ Installation on device rooted with SuperUser
3/ Attempt installation on an unrooted device
Q/ Exit
Enter option:
1
Adjusting for SuperSU!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
Succes
=============================================
Device and firmware information:
=============================================
Device model is SGP312
Firmware is 10.6.A.0.454
=============================================
Step2 : Sending the recovery files.
=============================================
1 KB/s (31 bytes in 0.026s)
3596 KB/s (18099 bytes in 0.004s)
240 KB/s (501 bytes in 0.002s)
3393 KB/s (11961 bytes in 0.003s)
4852 KB/s (65965 bytes in 0.013s)
1520 KB/s (3082 bytes in 0.001s)
4974 KB/s (31780 bytes in 0.006s)
716 KB/s (1357 bytes in 0.001s)
4525 KB/s (34473 bytes in 0.007s)
589 KB/s (1089 bytes in 0.001s)
3296 KB/s (13592 bytes in 0.004s)
4986 KB/s (719520 bytes in 0.140s)
4992 KB/s (3572614 bytes in 0.698s)
4850 KB/s (1995453 bytes in 0.401s)
5056 KB/s (2426269 bytes in 0.468s)
3256 KB/s (11760 bytes in 0.003s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
-rwxr-xr-x shell shell 719520 2015-06-14 17:10 busybox
Press any key to continue AFTER granting root access.
##########################################################
#
# Installing XZDR version 2.8.17 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
The byeselinux module exists, testing if the kernel accepts it.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event5!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event0!
XZDualRecovery will unload byeselinux every boot.
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation FAILED!
Please copy and paste the contents of
this window/screen to the DevDB thread.
=============================================
Getting similar output as well. Hopefully it can/will be resolved soon.Thanks for v17
Installattion of v2.5.17 seems to fail for me with no error, but I am unable to flash anything as recovery cannot write to system?
Hi. 2.8.18 isn't working for me.Getting similar output as well. Hopefully it can/will be resolved soon.
Just noticed that [NUT] had posted a new version .18 will try that and see if this works. Report back later.
2.8.18 with patched byeselinux.ko module from this post http://forum.xda-developers.com/showpost.php?p=61397400&postcount=5510 is working !Hi. 2.8.18 isn't working for me.
Device model is SGP321
Firmware is 10.6.A.0.454