FORUMS
Remove All Ads from XDA

[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE

5,379 posts
Thanks Meter: 10,423
 
Post Reply Email Thread
Announcement from [NUT]: The installer contains a ROOT EXPLOIT, this will trip A/V tools (e.g. ESET NOD32), disable it to download!!
9th December 2018, 04:42 PM |#7121  
Rootk1t's Avatar
Senior Member
Thanks Meter: 601
 
More
Quote:
Originally Posted by thewizardoz

i still haven't got a response to my question about the xzdualrecovery 2.8.27 folder being empty!!

Is there a xzdualrecovery 2.8.27 version out there anywhere?

no.

Quote:
Originally Posted by thewizardoz

if not, what is the best recovery to install on a stock phone please?

Thanks.

2.8.26 or separate TWRP. Depends on a device.
 
 
6th July 2019, 03:45 PM |#7122  
serqeftin's Avatar
Senior Member
Thanks Meter: 31
 
More
Hi,
How can uninstall dualrecovery, because I cant install any newer version TWRP. help p.ease.
Thanks.

---------- Post added at 03:45 PM ---------- Previous post was at 03:45 PM ----------

Hi,
How can uninstall dualrecovery, because I cant install any newer version TWRP. help p.ease.
Thanks.
The Following User Says Thank You to serqeftin For This Useful Post: [ View ] Gift serqeftin Ad-Free
7th July 2019, 05:27 PM |#7123  
Rootk1t's Avatar
Senior Member
Thanks Meter: 601
 
More
Quote:
Originally Posted by serqeftin

Hi,
How can uninstall dualrecovery, because I cant install any newer version TWRP. help p.ease.
Thanks.

You can try XZDR-removaltool.zip located here.
9th July 2019, 07:00 AM |#7124  
serqeftin's Avatar
Senior Member
Thanks Meter: 31
 
More
Quote:
Originally Posted by Rootk1t

You can try XZDR-removaltool.zip located here.

Thanks.
11th September 2019, 08:23 AM |#7125  
Member
Flag Tokyo
Thanks Meter: 9
 
Donate to Me
More
Rooting D6616 failed
Hi,

I failed to root my D6116. I tried with supersu in vain. And I tried firmware D6616_23.1.C.0.385_R15C_US T-Mobile_1286-4514.ftf also, in vain.
Code:
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 D6616
Firmware is 23.1.C.0.399
Android version is 5.0.2

=============================================
Step2 : Sending the recovery files.
=============================================

1 KB/s (31 bytes in 0.029s)
1925 KB/s (18170 bytes in 0.009s)
277 KB/s (501 bytes in 0.001s)
3755 KB/s (12812 bytes in 0.003s)
6105 KB/s (65965 bytes in 0.010s)
2004 KB/s (3159 bytes in 0.001s)
5412 KB/s (29204 bytes in 0.005s)
434 KB/s (699 bytes in 0.001s)
4687 KB/s (34473 bytes in 0.007s)
716 KB/s (1202 bytes in 0.001s)
6823 KB/s (96956 bytes in 0.013s)
7612 KB/s (870760 bytes in 0.111s)
7733 KB/s (3415700 bytes in 0.431s)
7542 KB/s (2420099 bytes in 0.313s)
3642 KB/s (14346 bytes in 0.003s)

=============================================
Step3 : Setup of dual recovery.
=============================================

Look at your device and grant supersu access!
/system/bin/sh: su: not found
Press enter to continue AFTER granting root access.

/system/bin/sh: /system/xbin/su: not found

=============================================
             Installation FAILED!

Please copy and paste the contents of
this window/screen to the DevDB thread.
=============================================
As you see, I'm running XZdualrecovery on Linux. What's wrong??


EDIT: Finally rooted with KingRoot (windows version.) Now I'm replace this with supersu.
12th September 2019, 07:58 AM |#7126  
Member
Flag Tokyo
Thanks Meter: 9
 
Donate to Me
More
Self reply!!

Quote:
Originally Posted by maverick6664

Hi,

I failed to root my D6116. I tried with supersu in vain. And I tried firmware D6616_23.1.C.0.385_R15C_US T-Mobile_1286-4514.ftf also, in vain.

EDIT: Finally rooted with KingRoot (windows version.) Now I'm replace this with supersu.

My bad!!

It has turned out that I forgot to turn "Allow mock locations" on before I ran XZdualrecovery. Now twrp is in my D6616. Indeed it works with D6616 as advertised!! Sorry for misinformation!!!

Cheers and thanks NUT!! You are a jewel!!
Post Reply Subscribe to Thread

Tags
cwm, doomkernel, locked bootloader, recovery, twrp
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes