Related
Anyone figured out how to do it? I've tried following the guides with no success (gingerbreak). Model is P970g and software is 10a. Country code is TLS.
Anyone have a Telus OB and been able to root it? How did you do it?
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
alexredford said:
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
Click to expand...
Click to collapse
I tried both z4 and the superoneclick you suggested to no avail.
Do you think it's safe to try flashing another vulnerable rom? 10b or 10c? I'm worried the basebands may be different and the phone will have no voice/data connection.
Running out of ideas.
Attempted to root another one, same model, same version and none of the previous methods worked, was able to root this one as well using a combination of SOC 2.1.1 and the attached ADB Shell.
1. Download and run SuperOneClick 2.1.1, choose psneuter and click Shell Root
2. It should get stuck on step #4, run task manager, end superoneclick and terminate any adb.exe processes. (You should have Shell Root now)
3. Extract ADB.zip and open a command prompt to where you extracted it.
4. Enter the following commands
Code:
adb push su /tmp/
adb push Superuser.apk /tmp/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
The permissions on /system/bin/su didn't stick the first time for me, and the phone rebooted a couple times, but eventually it all went through. To verify permissions on su, type "adb shell", then "ls -l /system/bin/su". The permission should read -rwsr-sr-x, if it doesn't repeat the shell root process and type
Code:
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
chmod 06755 /system/bin/su
ls -l /system/bin/su
Ok, i've figured out what the problem is. As soon as the adb process from SOC is shut down, the phone soft reboots and I lose temporary root. I've tried the psneuter exploit in the same adb command shell, but it hangs just like SOC. I've tried to be "quick" and get the commands in before the reboot, but it isn't possible.
Suggestions on how I may bypass that? Otherwise i'll wait for the official 2.3 update in september and try again then.
One of the phones I tried it on, did the same thing, ended the adb process and phone would reboot, pushed a file, phone would reboot, set permissions, phone would reboot. Occasionally the phone would appear to hang, buttons flash at the bottom for awhile, phone becomes unresponsive. Just wait a minute or 2 and it should return to normal. I also tried creating a script to do all of the above before the device had time to reboot and it didn't help.
Persistence was the key.
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Hey i am having the same problem and am fearing bricking my phone from making a mistake. is there an easier method than those above mentioned?
Android 2.2.2
software: v10a
Sobralobo said:
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
This method worked when rooting my wife's P970g.
KDZ file
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
s0dhi said:
This method worked when rooting my wife's P970g.
Click to expand...
Click to collapse
...which ROM did you use, the v10a EEU from the thread?
I'm worried cause on Telus 970g as well.
The_non_rootable said:
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=1
Hello gentleman, i'm new to this forum and android issues, read a lot of threads but today i got registered. hahaha
OK. First of all, im using ubuntu 12.04. Got my phone rooted yesterday with ICS using unlockroot with starter thread help on windows, today im trying to install CM10 and i really don't know what i'm doing wrong or if is missing something. Let's see...
On android sdk platform-tools in terminal mode, i started adb server with sudo to check if the problem is with permission:
Code:
sudo ./adb start-server
and verified if device is connected as well:
Code:
adb devices
the device is identified and another step i made was:
Code:
adb push /home/anon/Downloads/cm10.0.0-p970.zip /media/8184-18FE/
doing this i got my first error step receiving a message like: "no such file or directory error."
ps: this folder on /media/8184-18FE/ is the local to sdcard on device connected on usb using mass storage mode.
looking for some awnsers on other threads, people say to run adb as root using:
Code:
adb root
when i do this command line i get another message error: "adbd cannot run as root in production builds."
what is the difference of start adb on sudo mode or start adb on root mode? I thought it was about previleges, but seems equal for me.
I really don't know im missing or doing wrong, but still can't tranfer the rom to sdcard to upgrade my android.
As begginer on android, any help is welcome. Thank you!
Sv: [Q] adb problems
When you push it type adb push *directory* and the where you want it like /sdcard
So it is,
adb push /home/name.zip /sdcard
Or just enable mass storage and move it that way.
But you can't flash it since you have ics that you can't use cwm on
Cheers
Daniel
RomWiz said:
When you push it type adb push *directory* and the where you want it like /sdcard
So it is,
adb push /home/name.zip /sdcard
Or just enable mass storage and move it that way.
But you can't flash it since you have ics that you can't use cwm on
Cheers
Daniel
Click to expand...
Click to collapse
I realized that adb push command was wrong, but tryed it and now im receiving the error message: permission denied.
searched on another threads and figured out that the kernel that i have on official ICS is insecure, maybe that's why i can't flash like you said
but now my mind is a mess, i can't use the cwm because it cannot reboot in recovery mode like i saw on another threads?
what i do now? install a custom kernel and gingerbread, them root and install cm10 on recovery mode?
Sv: [Q] adb problems
cleitonpp said:
I realized that adb push command was wrong, but tryed it and now im receiving the error message: permission denied.
searched on another threads and figured out that the kernel that i have on official ICS is insecure, maybe that's why i can't flash like you said
but now my mind is a mess, i can't use the cwm because it cannot reboot in recovery mode like i saw on another threads?
what i do now? install a custom kernel and gingerbread, them root and install cm10 on recovery mode?
Click to expand...
Click to collapse
You flash a modded GB ROM with sft and install the ROM.
Cheers
Daniel
RomWiz said:
You flash a modded GB ROM with sft and install the ROM.
Cheers
Daniel
Click to expand...
Click to collapse
HAHAHA im such a dumb ass. Dont know why i tryed reboot into recovery mode on CWM, now i ****ed up my bootloader or bricked. XD
Sv: [Q] adb problems
Just flash a gb rom with sft
Cheers
Daniel
RomWiz said:
Just flash a gb rom with sft
Cheers
Daniel
Click to expand...
Click to collapse
Less than 5 days with my first android, i bricked 1 time...
i flashed, installed cm10, gapps and superuser, im so happy that i dont bricked permanently LOL
now im testing cm10 jelly bean =D
Thank you Daniel
Cheers :good:
Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.
Does anyone if the root stop you from updating the device like GS4?
Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.
Finally success root my shield
oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?
Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.
Please help me look at my attachment
What happend i cant install framework on my xperia..
My phone xperia Z3 and already root
xerxess said:
Please help me look at my attachment
What happend i cant install framework on my xperia..
My phone xperia Z3 and already root
Click to expand...
Click to collapse
try a different installation method, perhaps from recovery
same problem
could someone help us plz
I have the exact same problem same phone
I'm a nooby I did my rooting step by step from youtube and it works fine
plz don't ignore I'm stuck and depressed from this
guys a lot of you visited this page, no one of you can help us
Two things to check
1)Are you rooted?
1b) Just because you rooted doesn't mean you actually are rooted
2)Does xposed have root permission?
Bakerboy448 said:
Two things to check
1)Are you rooted?
1b) Just because you rooted doesn't mean you actually are rooted
2)Does xposed have root permission?
Click to expand...
Click to collapse
I checked with Root Checker and it's working also fine on other app that requires a root.
about giving the permission what do you mean ? through SuperSU ?
yes I grant xposed when it asked me so what els ?
I think it's a problem in the z3 because it's a dual sim not like other phones !!!
m4l3k said:
I checked with Root Checker and it's working also fine on other app that requires a root.
about giving the permission what do you mean ? through SuperSU ?
yes I grant xposed when it asked me so what els ?
I think it's a problem in the z3 because it's a dual sim not like other phones !!!
Click to expand...
Click to collapse
Try installing it via recovery, it has a better chance of working IF you have a custom recovery as well.
I already solve my problem..
Just need re root from start until update to the last fw with pre root flashable and do install recovery once again...
And dont forget change to rw via terminal in your pc
xerxess said:
I already solve my problem..
Just need re root from start until update to the last fw with pre root flashable and do install recovery once again...
And dont forget change to rw via terminal in your pc
Click to expand...
Click to collapse
Thanks a lot, but could you make it more simple for me
step by step without any abbreviations, so I can look at it online if I didn't know how to do it
I'm nooby like I said
m4l3k said:
Thanks a lot, but could you make it more simple for me
step by step without any abbreviations, so I can look at it online if I didn't know how to do it
I'm nooby like I said
Click to expand...
Click to collapse
just re root like usually you do and after that , update the FW to the lastest with pre root FW..
then when you finish..
in my experience my dual rec is gone so you cant do anything in recovery mode thats make you cant change system from ro to rw
to make recovery enabled again your phone after update..
do this
run your terminal in your pc inside giefroot folder then when the terminal already open
just copy command in below to your terminal pc..
just remember dont forget connect your phone to pc and make sure your debug is activate
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
but about how to use giefroot you can look to this thread
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
So I followed this guide to root my phone:
http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
Which worked. After that I decided I wanted a bash shell for my phone so I followed this guide:
http://forum.xda-developers.com/showthread.php?t=727566
I couldn't use adb remount because it gave me permission denied so I decided to use:
Code:
adb shell
su
mount -o rw,remount /system
And then I followed it up with the commands in the guide.
When I exited out of the adb shell I couldn't adb shell into it anymore.
It's giving me the following error:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
This is likely because in the guide you replace the default /system/bin/sh with the bash version.
And in the guide it doesn't tell you to chmod it. I think this is where the problem lies.
Then I thought maybe I could open up a shell inside my phone with a terminal emulator.
However the shell crashes and closes automatically.
Then I thought maybe I could use a file explorer to change sh.old back to the normal sh.
Unluckily I haven't yet given root permission to my file explorer so I couldn't.
I noticed that my root also got broken when I checked whether I was still rooted.
So I tryed re-rooting it with iRoot which didn't work.
Any idea on how I could fix this problem?
I still have adb access but I can't use any kind of shell not on the phone nor using adb.
EDIT: because of this I am now unable to change my EMUI theme, I also can't connect to wifi anymore.
Also, I tried a factory reset which didn't work...
EDIT: okay so I've made a backup of my current ROM through TWRP and now I am attempting to install the stock firmware of B133SP01 through local update.
After that I'm going to locally update to B602 and B609 again. Hopefully that will fix it...
EDIT: Seems like I can't install the stock firmware it's giving me an error message saying that it failed. And yes I have flashed my recovery back to stock B609. I suppose this has something to do with sh not working correctly...
Have I screwed myself for life?
I'm still hoping that someone can come in and help me fix it. If not I might be doomed.