Database Users

[Q] Need Help!!! Not able to root Defy Plus..

Not able to root Defy Plus..
Build number: 4.5.1-134_dfp-231
tried all versions of super one click..
but no luck..

Hi.
Use this
http://forum.xda-developers.com/showthread.php?t=1595013

Thank you. . It worked...
Sent from my MB526 using XDA

Pls help me!!!
Hi,
I'm trying to root my Motorola Defy plus.
Android:2.3.6
System Version:45.0.2310.MB526.AsiaRetail.en.03
Baseband version:EPU93_U_00.60.03
Kernal version: 2.6.32.9
BUILD NO: 4.5.1-134_DFP-231
It seems I'm not having write access for System folder...
Can any one help me to get rid of it...
My log is below.....
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
256 KB/s (23060 bytes in 0.087s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
368 KB/s (1075144 bytes in 2.845s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
48 KB/s (439 bytes in 0.008s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 94% bytes
test: 94%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .​
Thanks in advance..

Try this method as only this method works on BL7.
http://forum.xda-developers.com/showthread.php?t=1542956

Bharath256 said:
Hi,
I'm trying to root my Motorola Defy plus.
Android:2.3.6
System Version:45.0.2310.MB526.AsiaRetail.en.03
Baseband version:EPU93_U_00.60.03
Kernal version: 2.6.32.9
BUILD NO: 4.5.1-134_DFP-231
It seems I'm not having write access for System folder...
Can any one help me to get rid of it...
Thanks in advance..
Click to expand...
Click to collapse
you seriously need to read the threads prior to posting.. Its been answered like a 100 times..

MY Defy+ got rooted
Thanks a lot.....my defy+ got rooted....:victory::good:

Stressful problem

So...some days ago i rooted my phone for the first time,after that i had some problems so i`ve decided to flash again the original ROM via KDZ.
Everything worked perfectly,but this time i had some serious problems in rooting the phone,i flashed the stock ROM several times until i was able to ROOT the phone,but at least,it worked.
Then,i wanted to try CM 9 but i bricked the phone,so i flashed again the stock ROM via KDZ but this time i cant ROOT the device anymore,i even have problems with the ROM installation,every time i`m trying to install the stock ROM i get this error "MOD UpTestEX MFC Application has stopped working"
But the phone reacts like the ROM installed succesfully,the only problem is that there are almost no changes,my apps remain the same and etc..only the bootloader is changed.
Anyway,now i cant root my phone anymore,i tried with SuperOneClick but it always get stuck,z4root but no results..
Until now i used Spectrum to ROOT my phone but not it isnt working anymore...everytime i get this error
Code:
[*]
[*] LG Spectrum Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your tablet
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
link failed Permission denied
[*] Rebooting device...
[*] Waiting for device to reboot...
cannot create /data/local.prop: permission denied
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
[*] Cleaning up...
rm failed for /data/local.prop, No such file or directory
rm failed for /data/gpscfg/*, No such file or directory
Unable to chmod /data/: Operation not permitted
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
PS: I even tried with anoter PC and USB Cable,reinstalled the driver a few times but still no results.

saferoot protocol failure error

I'm trying to use the saferoot rooting method for my att galaxy s4 on MK2 but keep getting this error:
Waiting for your phone to appear
Your phone is detected and ready for rooting.
Sending files to your device...
protocol failure
rm failed for /data/local/tmp/Superuser.apk, No such file or directory
protocol failure
protocol failure
protocol failure
protocol failure
protocol failure
Unable to chmod /data/local/tmp/getroot: No such file or directory
Unable to chmod /data/local/tmp/busybox: No such file or directory
Starting rooting program.
/system/bin/sh: /data/local/tmp/getroot: not found
Removing temporary files...
rm failed for /data/local/tmp/getroot, No such file or directory
rm failed for /data/local/tmp/selinuxoff, No such file or directory
rm failed for /data/local/tmp/su, No such file or directory
rm failed for /data/local/tmp/busybox, No such file or directory
rm failed for /data/local/tmp/install-recovery.sh, No such file or directory
Rebooting... Please wait.
Waiting for device to re-appear...
I've updated the drivers, toggled usb debugging, toggled camera and media mode, but nothing seems to work...

just download a new version of saferoot, but am getting this error now:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
Unable to chmod /data/local/tmp/getroot: No such file or directory
Unable to chmod /data/local/tmp/busybox: No such file or directory
[*] Starting rooting program.
/system/bin/sh: /data/local/tmp/getroot: not found
[*] Removing temporary files...
rm failed for /data/local/tmp/getroot, No such file or directory
rm failed for /data/local/tmp/su, No such file or directory
rm failed for /data/local/tmp/busybox, No such file or directory
rm failed for /data/local/tmp/install-recovery.sh, No such file or directory
[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...
[*] Checking if su is still there
Something has deleted su - looking for the backup copy
The backup is gone too - can't recover!
Press any key to continue . . .

Problem with root LG Optimus L3

Hi guys, i've got problem with rooting my smartphone.
I cannot root my phone with any scripts ect.
For example
"[*]
[*] LG Spectrum Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your tablet
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
link failed Permission denied
[*] Rebooting device...
[*] Waiting for device to reboot...
cannot create /data/local.prop: permission denied
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: Read-only file system
link failed File exists
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
[*] Cleaning up...
rm failed for /data/local.prop, No such file or directory
rm failed for /data/gpscfg/*, No such file or directory
Unable to chmod /data/: Operation not permitted
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . ."
I need help.

try with kingroot
--SIGNATURE--

V20 H990DS Help To Install TWRP And lineage rom

hello
i have a lg v20 h990ds and i want to install twrp for install custom rom on my Phone
i Download Version 7 Android Firmware KDZ and Downgrade with lg up from android 8 to 7 and After try for install twrp recovery fail !
i,m downloaded any rev of android 7 kdz and flash with lg up and try to install twrp is fail !
list android 7 KDZ Rev i downloaded and try :
H990ds10h_00_OPEN_AME_DS_OP_0117.kdz
H990ds10e_00_OPEN_AME_DS_OP_0417.kdz
H990ds10b_00_OPEN_AME_DS_OP_1103.kdz
H990ds10d_00_OPEN_AME_DS_OP_1216.kdz
after flash firmware with lgup i try to install twrp have this Problem :
Step 1 :
C:\adb>step1.bat
C:\adb>adb push dirtysanta /storage/emulated/0
654 KB/s (18760 bytes in 0.027s)
C:\adb>adb push aboot.img /storage/emulated/0
2219 KB/s (2097152 bytes in 0.922s)
C:\adb>adb push dirtycow /data/local/tmp
1218 KB/s (9984 bytes in 0.008s)
C:\adb>adb push my-run-as /data/local/tmp
1349 KB/s (13796 bytes in 0.009s)
C:\adb>adb shell chmod 0777 /data/local/tmp/*
C:\adb>adb shell /data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/my-run-as
warning: new file size (13796) and file old size (14360) differ
size 14360
[*] mmap 0x743cc53000
[*] exploit (patch)
[*] currently 0x743cc53000=10102464c457f
[*] madvise = 0x743cc53000 14360
[*] madvise = 0 1048576
[*] /proc/self/mem -2122317824 1048576
[*] exploited 0x743cc53000=10101464c457f
C:\adb>adb shell /data/local/tmp/dirtycow /system/bin/applypatch /data/local/tmp/dirtycow
warning: new file size (9984) and file old size (165144) differ
size 165144
[*] mmap 0x76d9697000
[*] exploit (patch)
[*] currently 0x76d9697000=10102464c457f
[*] madvise = 0x76d9697000 165144
[*] madvise = 0 1048576
[*] /proc/self/mem 1367343104 1048576
[*] exploited 0x76d9697000=10102464c457f
C:\adb>adb shell
elsa:/ $ run-as con
elsa:/ # chmod 0777 /storage/emulated/0/*
elsa:/ # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
elsa:/ #
Step 2 :
C:\adb>step2.bat
C:\adb>adb pull /storage/emulated/0/bootbackup.img
remote object '/storage/emulated/0/bootbackup.img' does not exist
C:\adb>adb pull /storage/emulated/0/abootbackup.img
remote object '/storage/emulated/0/abootbackup.img' does not exist
C:\adb>adb reboot bootloader
Step 3 :
C:\adb>step3.bat
C:\adb>fastboot flash boot boot1.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.341s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.365s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (24964 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.854s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.009s
Please help me to resolve this problem
Thanks , Regards

mo4sa said:
Please help me to resolve this problem
Click to expand...
Click to collapse
The solution to your problem it's simple enough... You don't follow the instructions the way they are supposed to be follow.
This thread you open about the TWRP failed to install, but it's failing to unlock your device, and it has an entire thread about it. Recently there's one user who has some problems on how to perform this unlock and since I'll not write again (because you and everyone can search ) So this is my most recent post with my considerations/instructions.
How can I say with confidence that you aren't following the instructions? Because on the same thread the most appropriate guide for the H990DS (I have the same device by the way) don't need the step3. And this clear message device is locked, so the unlock failed.
So take your time, read with care and attention what was already discussed on the links that I share here, and if you still have problems, post to the right thread and we can continue this discussion there so others could benefit of this experience as well.