[help] iovyroot problem - Xperia Z5 Premium Q&A, Help & Troubleshooting

when i connect my device and run iovy
i got this error:
iovyroot by zxz0O0
poc by idler1984
Error: Device not supported
rm: /data/local/tmp/tabackup/TA-*.img: No such file or directory
Press any key to continue . . .
i have z5p dual e6833 - 5.1.1 (.115)
and i want to backup drm keys
i tried rooting with kingroot and it's not working
please help.

bump..

Firmware .170 is the only build that will work with iovyroot.
Check iovyroot thread carefully !

Related

[Full guide][XM single] How to have full root and use gl2sd,link2sd[]

hi guys ...this is for those need full root and the locked bootloaders of M who are wondering y the phone reboots when mounting on gl2sd...and tried a lot to fix it...
so here the fix...
definitely not by me....
u have to be rooted for this....
[B]Follow the instructions...[/B]
FOR ROOT[Half root]:
use http://forum.xda-developers.com/showthread.php?t=2529561 to root ur device
now download and install Busybox[https://play.google.com/store/apps/details?id=stericson.busybox&hl=en]
now open busybox and wait till it loads...after that make sure the path is /system/xbin then give smart install
till now your phone rooted and busybox installed but u will be having reboot if u try to edit system app..or mounting RW in system or link2sd,gl2sd reboot on mount..[some says this as Half root]...follow next for reboot fix[full root]
FOR REBOOT FIX [Full root]:
u should use the busybox for this fix to work...so dont miss the above procedure..
Download the http://www.2shared.com/file/e9sDTGJk/rootfixer.html? Tool By Anto Kus
Unzip it somewhere you remember
connect ur phone to pc
then run supersu.bat when prompted grant root access on phone
your xm will reboot,Once phone reboots wait for pc to detect phone again then finish supersu.bat then unplug device
Done!
Upto this strictly for M user...
the guide below can be used in any android device
Guide to use SD card for storing apps and Games
FOR storing apps:use LINK2SD:
Get the app from here:https://play.google.com/store/apps/details?id=com.buak.Link2SD
first guys XM/Mdual dont support ext4....please format ur sd 2nd partition to fat32...then u can link the apps....or else u will endup in bootloop...
use mini partition tools for windows...its easy to use...and easy to create a partition....
and connect your phone with MSC mode to PC for partitioning with the mini partition...which will in settings/xperia/usb connectivity/usb connection mode..
see here http://www.xperiablog.net/2011/12/12/link2sd-guide-never-worry-about-internal-memory-limits-again/
and follow the procedure in that site after 3rd step that is backup sd step in that site....[dont try to use that method of rooting...its not for m,just use guide for Creation of partition] ...
and how to link all given on above site...so now we can link apps which is going to be stored on SD 2nd partiton
FOR storing Game data and how to play game:use GL2SD:
get the app from here:https://play.google.com/store/apps/details?id=com.slf.ListglApp
Guide:
first whatever game u need to play...use some website to download them ...bcoz u wont have space required in internal sdcard if u want to download from playstore...
so i assume u have downloaded the game apk + data from some website....and u have extracrted the zip or rar to somewhere in pc...
1.copy the apk to sdcard1...[Note:sdcard1 is ur external sdcard]
2.see the data folder...
mostly data folder has game name inside them mostly android/obb/game name/ or android/data/game name/ [game name will start as com.xxxxxx.yyy] structure will be followed and
some gameloft or reputed company will have their company name/games/game name/ [game name will start as com.xxxxxx.yyy] structure for games
3.now if it has .obb format file inside the above given structures...then copy game name folder and place them in sdcard1/obb/ [eg:sdcard1/obb/com.rockstar.gta3/xxyyyy.obb]
or if it has many folders and files inside the above structure....then copy the game name folder and place them in sdcard1/data/ [eg:sdcard1/data/com.rockstar.gta3/]
4.now install game.apk from sdcard1 and open gl2sd
5.click mount [the joined chain symbol at top] and click play the game...if u didnt see game on list ...just open setting go down and click recover list
6.if u download some medium size game like 250mb directly from playstore..then open gl2sd and click top right button and choose move data and wait till it moves data] after that ur game data is stored on sdcard1 ....now play with same step 5
7.if game didnt open or cant play or some error...restart ur phone...and repeat the 5th step...
8.if game work..cool but remember to unmount[unlinked chain on top] after u finished playing games..or u cant paste anything in sdcard1
[Note:To run game you must mount after every reboot and unmount if u r going to copy some files to sdcard1]
if u cant understand what i said about gl2sd
see this video..maybe it will help u.. http://www.youtube.com/watch?v=adLQgWyYIXQ
now u can mount any app or game to sdcard1...
credits to
dunc4n88
Anto Kus
Xzn
Hendrico Andre and Muhammad Arif
esrom02
and to link2sd,gl2sd app developers
problem with XM C2005
ansebovi said:
hi guys ...this is for those need full root and the locked bootloaders of M who are wondering y the phone reboots when mounting on gl2sd...and a lot to fix it...
so here the fix...
definitely not by me....
u have to be rooted for this....
[B]Follow the instructions...[/B]
FOR ROOT[Half root]:
use http://forum.xda-developers.com/showthread.php?t=2529561 to root ur device
now download and install Busybox[https://play.google.com/store/apps/details?id=stericson.busybox&hl=en]
now open busybox and wait till it loads...after that make sure the path is /system/xbin then give smart install
till now your phone rooted and busybox installed but u will be having reboot if u to edit system app..or mounting RW in system or link2sd,gl2sd reboot on mount..[some says this as Half root]...follow next for reboot fix[full root]
FOR REBOOT FIX [Full root]:
u should use the busybox for this fix to work...so dont miss the above procedure..
Download the http://www.2shared.com/file/e9sDTGJk/rootfixer.html? Tool By Anto Kus
Unzip it somewhere you remember
connect ur phone to pc
then run supersu.bat when prompted grant root access on phone
your xm will reboot,Once phone reboots wait for pc to detect phone again then finish supersu.bat then unplug device
!
Upto this strictly for M user...
the guide below can be used in any android device
Guide to use SD card for storing apps and Games
FOR storing apps:use LINK2SD:
Get the app from here:https://play.google.com/store/apps/details?id=com.buak.Link2SD
first guys XM/Mdual dont support ext4....please format ur sd 2nd partition to fat32...then u can link the apps....or else u will endup in bootloop...
use mini partition tools for windows...its easy to use...and easy to create a partition....
and connect your phone with MSC mode to PC for partitioning with the mini partition...which will in settings/xperia/usb connectivity/usb connection mode..
see here http://www.xperiablog.net/2011/12/12/link2sd-guide-never-worry-about-internal-memory-limits-again/
and follow the procedure in that site after 3rd step that is backup sd step in that site....[dont to use that method of rooting...its not for m,just use guide for Creation of partition] ...
and how to link all given on above site...so now we can link apps which is going to be stored on SD 2nd partiton
FOR storing Game data and how to play game:use GL2SD:
get the app from here:https://play.google.com/store/apps/details?id=com.slf.ListglApp
Guide:
first whatever game u need to play...use some website to download them ...bcoz u wont have space required in internal sdcard if u want to download from playstore...
so i assume u have downloaded the game apk + data from some website....and u have extracrted the zip or rar to somewhere in pc...
1.copy the apk to sdcard1...[Note:sdcard1 is ur external sdcard]
2.see the data folder...
mostly data folder has game name inside them mostly android/obb/game name/ or android/data/game name/ [game name will start as com.xxxxxx.yyy] structure will be followed and
some gameloft or reputed company will have their company name/games/game name/ [game name will start as com.xxxxxx.yyy] structure for games
3.now if it has .obb format file inside the above given structures...then copy game name folder and place them in sdcard1/obb/ [eg:sdcard1/obb/com.rockstar.gta3/xxyyyy.obb]
or if it has many folders and files inside the above structure....then copy the game name folder and place them in sdcard1/data/ [eg:sdcard1/data/com.rockstar.gta3/]
4.now install game.apk from sdcard1 and open gl2sd
5.click mount [the joined chain symbol at top] and click play the game...if u didnt see game on list ...just open setting go down and click recover list
6.if u download some medium size game like 250mb directly from playstore..then open gl2sd and click top right button and choose move data and wait till it moves data] after that ur game data is stored on sdcard1 ....now play with same step 5
7.if game didnt open or cant play or some error...restart ur phone...and repeat the 5th step...
8.if game work..cool but remember to unmount[unlinked chain on top] after u finished playing games..or u cant paste anything in sdcard1
[Note:To run game you must mount after every reboot and unmount if u r going to copy some files to sdcard1]
if u cant understand what i said about gl2sd
see this video..maybe it will help u.. http://www.youtube.com/watch?v=adLQgWyYIXQ
now u can mount any app or game to sdcard1...
credits to
dunc4n88
Anto Kus
Xzn
Hendrico Andre and Muhammad Arif
esrom02
and to link2sd,gl2sd app developers
Click to expand...
Click to collapse
in gl2sd
When I click mount the device reboot and after reboot not mounted
I think the device Can not read memory card
please help me
thanks for your efforts
mohamad khubayb said:
in gl2sd
When I click mount the device reboot and after reboot not mounted
I think the device Can not read memory card
please help me
thanks for your efforts
Click to expand...
Click to collapse
u must read xda rules properly...dont quote or reply OP post...edit ur post and delete the quotes
and u r using this thread to root?
if u r then...search for XM dual rooting guide...this is for XM single..
Will this work on C2004? firmware =15.2.A.2.5
danger ssteepr
Hi and thanks for the guide!
I've successfully (at least without errors) completed all steps you mention for a full root, but my xperia m still reboots when i try to delete system apps. Can you help me there?
krissel said:
Hi and thanks for the guide!
I've successfully (at least without errors) completed all steps you mention for a full root, but my xperia m still reboots when i try to delete system apps. Can you help me there?
Click to expand...
Click to collapse
r u sure u did install the given busybox?
bcoz my frnd using XM single gave this method...
and i seen some one told this way is to get full root.
ansebovi said:
r u sure u did install the given busybox?
bcoz my frnd using XM single gave this method...
and i seen some one told this way is to get full root.
Click to expand...
Click to collapse
Nevermind! i went through the whole process again, not it seems to work
thanks!
Hi, i have c1905 full root and was following the procedures for making a second partition. When i get the option for picking FAT32 in the link2sd app the phone reboots itself and stuck on a loop. Does anyone have any ideas to help please.
Persevere80 said:
Hi, i have c1905 full root and was following the procedures for making a second partition. When i get the option for picking FAT32 in the link2sd app the phone reboots itself and stuck on a loop. Does anyone have any ideas to help please.
Click to expand...
Click to collapse
Have you already have root access to your link2sd?
For 2nd partitions in sdcard format to ext3 and in link2sd select ext3 too.
Sorry for my English
Sent from my C1905 using XDA Premium 4 mobile app
I was told fat32 in this thread. But took the phone back, think its a joke. Got a moto g for roughly the same price with now problems atoll
Sent from my XT1032 using Tapatalk
Hi, I followed the instructions perfectly for my SingleSim Xperia M C1905 (firmware 15.1.C.2.8) but I can only get the half root. After doing the second part of the steps to fully root, when i try to RW using Root Explorer the phone reboots. So I am thinking the problem is somewhere in the last step when I do the Anto Kus Tool. Below is the result of using the Anto Kus Tool. The part below in bold looks like an error of some kind (rm failed for -f etc) and my phone is NOT being fully rooted (remains at only half root). Can someone please tell me what the below is saying? Some sort of error message right? Anyone have any ideas on what the problem could be? I have tried using the Anto Kus Tool like five times and always the same result as below.... and the phone remains at half-root. I don't know what to try next
==============================================
= =
= Anto Kus a.k.a Splakuk =
= FIX THE XPERIA M ROOT =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
.
=============================================
Sending the fixer.
=============================================
362 KB/s (557 bytes in 0.001s)
951 KB/s (1461 bytes in 0.001s)
53 KB/s (82 bytes in 0.001s)
5056 KB/s (657704 bytes in 0.127s)
1377 KB/s (2116 bytes in 0.001s)
.
=============================================
Installing the rootfix.
=============================================
-rw-rw-rw- shell shell 657704 2013-06-24 12:59 busybox
at your device GRANT supersu access!
Press any key to continue after granting root access.
Press any key to continue . . .
killswitch the ric, remount /system rw and temporarily disabling the ric service
...
Found busybox, checking if it supports nohup...
rm failed for -f, No such file or directory
It does not, copying a replacement busybox to system.
rm failed for -rf, No such file or directory
Xperia M (C1904/5) found, installing install-recovery.sh instead...
=============================================
= YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
Wait a few seconds to see if it worked, then
Press any key to continue . . .
And I just tried it again after playing around with BusyBox Free and this time I get a different Anto Kus wording result (in bold below) but again I still have only the half-root (when I click RW in Root Explorer my phone still reboots) :crying: Still not working!
What does it mean "installing install-recovery.sh instead" at the end of the Anto Kus Tool message? Does this mean the tool is installing something other that is should be instead? Is this why it's not working?
==============================================
= =
= Anto Kus a.k.a Splakuk =
= FIX THE XPERIA M ROOT =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
.
=============================================
Sending the fixer.
=============================================
mkdir failed for /data/local/tmp/rootfix, File exists
155 KB/s (557 bytes in 0.003s)
407 KB/s (1461 bytes in 0.003s)
26 KB/s (82 bytes in 0.003s)
3276 KB/s (657704 bytes in 0.196s)
590 KB/s (2116 bytes in 0.003s)
.
=============================================
Installing the rootfix.
=============================================
-rw-rw-rw- shell shell 657704 2013-06-24 12:59 busybox
at your device GRANT supersu access!
Press any key to continue after granting root access.
Press any key to continue . . .
killswitch the ric, remount /system rw and temporarily disabling the ric service
...
Found busybox, checking if it supports nohup...
Success!
Xperia M (C1904/5) found, installing install-recovery.sh instead...
=============================================
= YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
Wait a few seconds to see if it worked, then
Press any key to continue . . .
.
=============================================
Finish.. Enjoy
=============================================
.
Press any key to continue . . .
And now the third try today. I am not giving up haha! Thinking perhaps the problem is with the BusyBox Free version I went ahead and uninstalled BusyBox Free and installed the BusyBox Pro version. I did this because the instructions on the first page say to install BusyBox and "give Smart Install" and since Smart Install is not available with the free version I got the Pro version.
So when I clicked the BusyBox Pro icon in the apps tray for the first time it took a long time to load which I think is normal. Then I enabled Smart Install and clicked install. Now it is saying that BusyBox 1.22.1-Stericson is installed to /system/xbin as i think it should be. So I am doing everything right so far right?
So now I run the Anto Kus Root Fixer again (Windows7 64 bit) and again it doesn't work (RW doesn't work, phone reboots). Below is the wording from the latest Anto Kus Root Fixer attempt. What is wrong?
When I run a Root Checker app I got from the Play Store it says this (but like I said my phone reboots when I try to RW)
SU su found [/system/xbin]Version 1.93:Supersu
Root Access : access granted
UID=0 (root) GID=0 (root)
Unix Utils busybox /system/xbin/busybox Version IS
Path /system/xbin
/vendor/bin
/system/sbin
/sbin
/system/bin
==============================================
= =
= Anto Kus a.k.a Splakuk =
= FIX THE XPERIA M ROOT =
= =
==============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
.
=============================================
Sending the fixer.
=============================================
mkdir failed for /data/local/tmp/rootfix, File exists
155 KB/s (557 bytes in 0.003s)
475 KB/s (1461 bytes in 0.003s)
26 KB/s (82 bytes in 0.003s)
3219 KB/s (657704 bytes in 0.199s)
1033 KB/s (2116 bytes in 0.002s)
.
=============================================
Installing the rootfix.
=============================================
-rw-rw-rw- shell shell 657704 2013-06-24 12:59 busybox
at your device GRANT supersu access!
Press any key to continue after granting root access.
Press any key to continue . . .
killswitch the ric, remount /system rw and temporarily disabling the ric service
...
Found busybox, checking if it supports nohup...
Success!
Xperia M (C1904/5) found, installing install-recovery.sh instead...
=============================================
= YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
Wait a few seconds to see if it worked, then
Press any key to continue . . .
.
=============================================
Finish.. Enjoy
=============================================
.
Press any key to continue . . .
So now it's the next day. I am determined to get full root. But again FAIL.
I started out the day by removing SD Card and doing a FACTORY RESET of my Xperia M. Then first thing I did was do the rooting instructions. But again full root FAIL. I am only able to get the half-root just like before. I am telling you that the Anto Kus Tool does not work or a VERY IMPORTANT KEY PART of the instructions is missing!
Well hopefully when the new KitKAt update for XperiaM comes out next month then a new rooting method will need be devised in order to root these damn Xperia M's. Because right now the current full-root method just does not work. And I have tried and tried and tried again again again
Well, here we are again trying to full-root my Xperia M.
This time I took my girlfriends Xperia M and followed the steps, hers has same firmware as mine. And it all worked perfect. No problems at all to get the full root. One thing I noticed different is that when I used the the Anto Kus Tool on my girlfriend's phone it only rebooted once during the whole procedure while with mine it rebooted twice (the second time right at the point where the Anto Kus tool says "Wait a few seconds to see if it worked ok then..." then my phone reboots a second time while with hers it didn't. I am assuming that that check is to see if the RW works. And of course mine always reboots as I have been explaining for the past week as I am not achieving the full root.
So there is something wrong with my phone. I need to totally erase it and start all over to reinstall the Sony Android OS etc. But I don't know how to do that so I will open a new thread and ask how...
So the moral of this story is that yes, the instructions work fine however not with every phone. With mine it doesn't, then I followed the same procedure that I had used on mine with her Xperia M and it did work fine, first time.
andyxoxo said:
Well, here we are again trying to full-root my Xperia M.
This time I took my girlfriends Xperia M and followed the steps, hers has same firmware as mine. And it all worked perfect. No problems at all to get the full root. One thing I noticed different is that when I used the the Anto Kus Tool on my girlfriend's phone it only rebooted once during the whole procedure while with mine it rebooted twice (the second time right at the point where the Anto Kus tool says "Wait a few seconds to see if it worked ok then..." then my phone reboots a second time while with hers it didn't. I am assuming that that check is to see if the RW works. And of course mine always reboots as I have been explaining for the past week as I am not achieving the full root.
So there is something wrong with my phone. I need to totally erase it and start all over to reinstall the Sony Android OS etc. But I don't know how to do that so I will open a new thread and ask how...
So the moral of this story is that yes, the instructions work fine however not with every phone. With mine it doesn't, then I followed the same procedure that I had used on mine with her Xperia M and it did work fine, first time.
Click to expand...
Click to collapse
Well, it worked fine first time for me. Anyway, if you want to reflash stock firmware then use Sony's PCC. Go to Update and then repair (assuming you have a locked bootloader, if you don't then download an FTF and flash it)
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Antrikos48 said:
Well, it worked fine first time for me. Anyway, if you want to reflash stock firmware then use Sony's PCC. Go to Update and then repair (assuming you have a locked bootloader, if you don't then download an FTF and flash it)
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
Yes thank you, after so many tries I finally got full root. I had to do the repair with Sony PC Companion exactly how you said. Now full-root. I could tell it was working right away during the Anto Kus rootfixer because it rebooted only once during the procedure. And then RW was good to go/ Oh happy days
could not update system apps after using link2sd
Thanks for this post ...
m a noob at all this but hv been visiting xda forums since I purchased my xperia M 2 months back.
I have successfully rooted my phone, installed link2sd after lots of trials and now m facing an error while updating any system app.
It says : insufficient storage available
Is thr any solution to that, so that I can update my apps like Google Maps etc.
22sumit said:
Thanks for this post @OP
m a noob at all this but hv been visiting xda forums since I purchased my xperia M 2 months back.
I have successfully rooted my phone, installed link2sd after lots of trials and now m facing an error while updating any system app.
It says : insufficient storage available
Is thr any solution to that, so that I can update my apps like Google Maps etc.
Click to expand...
Click to collapse
Ah yes, I got that too. But I was tinkering with Link2SD setting so I can't be sure.
I fixed it by going into Link2SD Plus (running Plus if it makes difference) and selected settings -> Install Location -> Automatic
I did have the option 'External' set, cause I thought that made more scene, but maybe some apps need the option of Internal or External.
Have a look and see if this applies to your problem.
thanks
Dr Goodvibes said:
Ah yes, I got that too. But I was tinkering with Link2SD setting so I can't be sure.
I fixed it by going into Link2SD Plus (running Plus if it makes difference) and selected settings -> Install Location -> Automatic
I did have the option 'External' set, cause I thought that made more scene, but maybe some apps need the option of Internal or External.
Have a look and see if this applies to your problem.
Click to expand...
Click to collapse
Thanks a lot Dr goodvibes.
That was really helpful... Changed the Install Location to Automatic from External.
BOOM , problem solved :good:

[Q&A] [ROOT][S/SL] How-to for rooting newest firmware 6.2.B.1.96

Q&A for [ROOT][S/SL] How-to for rooting newest firmware 6.2.B.1.96
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I have made ROOT and now battery is not loading, can anybody help?
i cannot download the drivers
hii doomlord
i suppose u r the best on xda and the issue is that i am not able to find the drivers u mentioned to download from,
please check your details and respond to me asap
thanks yaar !!
---------- Post added at 07:28 PM ---------- Previous post was at 07:13 PM ----------
[email protected] said:
I have made ROOT and now battery is not loading, can anybody help?
Click to expand...
Click to collapse
hey
i did not get the boootloaders ...
please can u upload the one su had downloaded ??
ahhh question is after rooting how to install custom roms on this device as there is no CWM
secondly how to get in recovery mode to flash custom roms ???
Problems with root
I have installed adb drivers on my mac and flashed the XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf kernel in my Xperia S. But when i go to root, my Terminal say this:
Last login: Sat Nov 1 01:59:57 on ttys000
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh ; exit;
DarkStar:~ Rodrigo$ /Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh ; exit;
chmod: files/adb_mac: No such file or directory
---------------------------------------------------------------
Easy Rooting toolkit (v18.0)
created by DooMLoRD
"pref_event exploit"
Credits go to all those involved in making this possible!
---------------------------------------------------------------
Special thanks to: the_laser, Bin4ry, fi01, hiikezoe, [NUT]
and to all those who are contributing to our git tree!
Sources: https://github.com/android-rooting-tools
---------------------------------------------------------------
ported to Mac OS X by ChrisBoesing
---------------------------------------------------------------
[*] This script will:
(1) root ur device using the pref_event exploit
(2) install Busybox
(3) install SU files
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) connect USB cable to PHONE and then connect to PC
(5) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
--- STARTING ----
--- WAITING FOR DEVICE
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 32: files/adb_mac: No such file or directory
--- creating temporary directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 34: files/adb_mac: No such file or directory
--- cleaning
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 36: files/adb_mac: No such file or directory
--- pushing files
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 38: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 39: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 40: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 41: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 42: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 43: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 44: files/adb_mac: No such file or directory
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 45: files/adb_mac: No such file or directory
--- cleaning
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 47: files/adb_mac: No such file or directory
--- Please wait device is now rebooting
/Users/Rodrigo/Desktop/DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit/runme_mac.sh: line 49: files/adb_mac: No such file or directory
ALL DONE!!!
logout
[Proceso completado]
What should i do?
Flashed kernel in wrong mode?
Hello guys i think i am in a bit of a pickle right now
would be cool if you guys can guide me a little
But i think i flashed the kernel in the wrong mode (volume up with blue light) and the phone is not booting
My phone is Xperia SL and i have unlocked bootloader.
the phone is charging and can go into both modes (Flash and fastboot).
I tried soft and hard reset with no luck.
When i press the power button now a green led flashes and disappears with no response.
any advice on how to proceed
Found the problem
ubte said:
Hello guys i think i am in a bit of a pickle right now
would be cool if you guys can guide me a little
But i think i flashed the kernel in the wrong mode (volume up with blue light) and the phone is not booting
My phone is Xperia SL and i have unlocked bootloader.
the phone is charging and can go into both modes (Flash and fastboot).
I tried soft and hard reset with no luck.
When i press the power button now a green led flashes and disappears with no response.
any advice on how to proceed
Click to expand...
Click to collapse
This fixes the problem
1) I had put my phone into fastboot(blue) mode and not flash(green) mode.
2) This is the tool to be used for flashing the kernel flashtool.net
I can't get the ftf. format file.
After I downloaded both the kernel ftf. file. They appear as (application format) which the website told me to run the file. I followed the process and got the file which is also the (application format) but cannot be run, (just a black box similar to command prompt jumped out and closed itself). Then I tried the other method I found from the internet, I opened the file with Win RAR and extracted 1 folder and 2 files ( means a total of 3 files : 1) Folder: META-INF > MANIFEST.MF
2) kernel.sin
3) loader.sin
I just can't get the ftf. format file, how? This is my first time rooting a phone, my phone has never been rooted. Please help me.
File not available
Hi, the files are not available for me. The webpage is not available. Can you host those three files somewhere else.

Rooting -LG G3 (D851) Lollipop 5.0.1 Appears to work but doesn't.

Hello, I have an LG G3 (D851) Lollipop 5.0.1 And I have tried to root it with many different programs or manually band each times everything goes smoothly it says "Done" but the phone is not rooted ? What can I do ?
I have tried the following :
LG One Click Root (Visual)
LG One Click Root (Prompt)
PurpleDrake-Lite
LG Root Script v1.2
Kingroot
Newest root method V03
Towelroot
Here is what one click root says :
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
4432 KB/s (1048328 bytes in 0.230s)
316 KB/s (9226 bytes in 0.028s)
4150 KB/s (4017098 bytes in 0.945s)
Rebooting...
Looking for LG serial port...
Phone found at COM4!
Rebooting into Download mode...
Waiting for device...
Phone found at COM4!
Rooting phone...
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
- Mounting /system, /data and rootfs
- Extracting files
- Disabling OTA survival
- Removing old files
- Placing files
- Post-installation script
- Unmounting /system and /data
#
Done!
They seem to work but then nothing happens on the phone, it's not rooted. Do you have any idea why ?
Thank you for your help.
Assuming your phone is on 20e, use the second method in this thread...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
... after downloading and extracting the New_LG_Root_v0.1_by_dig.zip file, which is found in the OP, to your PC. Then download the Root Checker app from the Play Store...
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Thanks !
redduc900 said:
Assuming your phone is on 20e, use the second method in this thread...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
... after downloading and extracting the New_LG_Root_v0.1_by_dig.zip file, which is found in the OP, to your PC. Then download the Root Checker app from the Play Store...
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Click to expand...
Click to collapse
Thank you it worked ! Just one strange thing if that can help others, after rooting it I launched Root Checker Basic to check root access and it took a good minutes (way longer than normal) to tell me that I was not rooted, which was strange so I decided to double check with Titanium Backup and TB directly told me that I had Root access asked me to grantit to Root Checker, so I did then when I ran Root Checker it told me that I was Rooted. So double check ! And again thank you to redduc900 !
Can anyone pls help me to root my D85120e...
Many thanks
How to root LG G3 D851 with MM 6.0
Why can't work on mine
How to root LG G3 D851 with MM 6.0 or install TWRP or Install Custom Rom like MIUI 8
usmandaud said:
Why can't work on mine
How to root LG G3 D851 with MM 6.0 or install TWRP or Install Custom Rom like MIUI 8
Click to expand...
Click to collapse
there is no way to root android 6.0 MM
Rooting LG G3
anjesh12 said:
there is no way to root android 6.0 MM
Click to expand...
Click to collapse
Why don't any method i need it how to root it

Possible marshmallow root with locked boot-loader?

(not sure what thread to put it in)
I doubt this will work but i was using sony mobile flasher by androxyde and so my phone came up with root denied so I clicked on the root section and tried them all didn't work until i clicked on service menu and I got this
03/047/2016 19:47:53 - INFO - Pushing C:\Users\Myname\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\install-recovery.sh to /data/local/tmp/install-recovery.sh
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\99SuperSUDaemon to /data/local/tmp/99SuperSUDaemon
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\onload.sh to /data/local/tmp/
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\getroot.sh to /data/local/tmp/
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\install-recovery.sh to /data/local/tmp/
03/048/2016 19:48:13 - INFO - Look at your phone. Choose Service Test, then Display.
03/048/2016 19:48:13 - INFO - Waiting for uevent_helper rw
03/048/2016 19:48:15 - INFO - Device connected with USB debugging on
03/048/2016 19:48:16 - INFO - Connected device : Sony Xperia M5
03/048/2016 19:48:16 - INFO - Installed version of busybox : N/A
03/048/2016 19:48:16 - INFO - Android version : 6.0 / kernel version : 3.10.72+ / Build number : 30.2.A.1.21
03/048/2016 19:48:16 - INFO - Root access denied
03/048/2016 19:48:19 - INFO - Waiting for rooted shell
03/048/2016 19:48:20 - INFO - Root achieved. Installing root files. Device will reboot. Please wait.
03/048/2016 19:48:20 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\installsu.sh to /data/local/tmp/
but I just hard bricked my phone and just got it back so I don't want to try it but if anyone is willing to try that would be great
It's simple: starting with Marshmallow update, Xperia M5 now have verified boot (dm-verity) enabled, just like all other Xperia devices from 2015 and onwards (some older Xperia devices also got dm-verity through a firmware update). That means it doesn't matter if you find a working exploit or not, modifying a single byte of the system partition will simply fail dm-verity checks and as result your phone won't boot (that's apparently what happened to your phone, you managed to modify the system partition and as result it refused to boot). No write access to system partition means no way to install su binary and other required files.
In other words, the ages of root with a locked bootloader are gone, unlocking the bootloader (so you can flash a modified kernel with dm-verity disabled or a systemless root solution) is the only way to get root now.
mbc07 said:
It's simple: starting with Marshmallow update, Xperia M5 now have verified boot (dm-verity) enabled, just like all other Xperia devices from 2015 and onwards (some older Xperia devices also got dm-verity through a firmware update). That means it doesn't matter if you find a working exploit or not, modifying a single byte of the system partition will simply fail dm-verity checks and as result your phone won't boot (that's apparently what happened to your phone, you managed to modify the system partition and as result it refused to boot). No write access to system partition means no way to install su binary and other required files.
In other words, the ages of root with a locked bootloader are gone, unlocking the bootloader (so you can flash a modified kernel with dm-verity disabled or a systemless root solution) is the only way to get root now.
Click to expand...
Click to collapse
I bricked my phone because I'm an idiot not because of that and I was on lollipop when I did it
"Hard bricked and got it back" - HOW?????
ih8redsn0w said:
(not sure what thread to put it in)
... but I just hard bricked my phone and just got it back ...
Click to expand...
Click to collapse
Hi there, this quote is extremely interesting!
What do you mean with "just got it back"? Got it back to booting...? Or got it back from a warranty repair?
Please let us know what we have to do to get our's back too... I hard bricked mine and don't seem to find a way to unbrick it. And more of us with the same problem are out there... THANKS indeed!

[LG G PAD 8.3 V500] Conflicting reports about which safe method to use to root device

EDIT: (31/07/20) ... OK finally got it by following only the root parts of [Guide/tutorial/howto] LG GPad 8.3 V500 stock to Android 9 Pie/crDroid 5.x.
1. Download pack to device (the zip file) and extract.
2. Follow "Prepare Tablet" part of guide including checking build number which should be xxx.V50020f.
3. Follow the " ROOT LG GPAD 8.3 V500" part of the guide and install Stump-v1.2.0.apk (included in downloaded zip pack).
4. Wait a few minutes for Stump to complete. Reboot (manually, the Stump app won't do it). My device rebooted twice then I checked and device was rooted OK
---
Hi,
> Android = 4.4.2
> Firmware: v50020F
I managed to replace my competely useless Samsung Tab 3 (undepowered CPU and too little memory) with the much better LG.
All I need to do is root the device so I can use "app2sd" (or whatever method) to install apps to external storage sd card.
The first method I tried was this method using a batch file in "root_gpad.zip". But it fails with ...
Code:
If you do not want to possibly invalidate your warranty
press CTRL-C to stop this script.
You will have a rooted ADB, but no apps on the phone will be able
to access root functions.
Press any key to continue . . .
Mounting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to open /system/xbin/su: No such file or directory
Unable to open /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
2631 KB/s (2025538 bytes in 0.751s)
pkg: /data/local/tmp/superuser.apk
Success
***************************************************
Done.
***************************************************
Please check the above for any errors and let me know if you run into any issues.
Enjoy your phone!
Press any key to continue . .
.
Then I started looking at [Root][V500] G Pad 4.4.2 Stock w/ IOroot25 [Yippee!] but a lot of the info seems confusing and/or conflicted. One post in that thread says ...
Stump Root
This method can not be done root on LG G Pad 8.3 V500 on ROM V50020f from 2015-09-15.
You can do root through Stump Root for LG Devices (2012 - 2014).
Checked, because I did it.
Stump Root does not require an internet connection
Click to expand...
Click to collapse
But Stump Root does not list my device in its supported devices.
So I thought I'd better check here first before I attempt anymore of this. Any help appreaciated ! The LG G Pad 8.3 is a great device and, as my research showed, runs fast even in a market that is 6 years older

Categories

Resources