Rooting the Xperia V: How-To.
(XDA member datagubben requested that I post this here, as per http://forum.xda-developers.com/showpost.php?p=36753824&postcount=19)
Mirrors for the files provided are welcome.
This root method is courtesy of Xperia-Freaks.org, originally developed for the Xperia AX, translated and adapted by me for the LT25i.
Supported firmware: 9.0.1.D.0.10, probably also 9.0.D.0.484.
Reportedly does not work with 9.1.A.0.489.
You will need: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (direct link: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf) or the original LT25i-SOL21_9.0.F.0.195.ftf (this FTF has its loader.sin replaced with LT25i's loader.sin; the trimmed version lacks unneeded files like baseband etc. and as such removes unneeded wipe/exclude options, leaving only the three files we actually need) and an LT25i FTF of your choice; the rootkit (this one is "translated" and edited for convenience; do NOT use regular GX/SX rootkits blindly as they require modification).
Make a backup using the stock Backup and Restore app in case something goes wrong so you can perform a factory reset.
Once rooted, you can safely restore from that backup.
1. Power the phone up in Flashmode (hold Volume down; connect USB). Using Flashtool, flash TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (or the untrimmed version if you like fiddling with excess checkboxes) using:
kernel.sin
loader.sin
system.sin
(Remember to uncheck the wipe options!)
2. Unplug USB. Turn the phone on. Enable USB debugging if it wasn't enabled previously. Connect the phone via USB again.
3. Unpack the Rootkit and start it (run install.bat). Confirm restore of the backup as requested, and press any key in the cmd window. Press any key again; the device will reboot (twice).
4. Run adb shell. To do it, you can open the rootkit folder in Windows Explorer, and shift-Right Click the "files" folder inside it. Choose "Open command window here". Type "adb shell" in that window.
If you're presented with a prompt that ends with "$", type "su".
The prompt should end with "#" now.
Type "echo ro.kernel.qemu=1 > /data/local.prop" and check if the file was created successfully by typing "ls -l /data/local.prop": below you will find an example of what the output looks like.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo ro.kernel.qemu=1 > /data/local.prop
echo ro.kernel.qemu=1 > /data/local.prop
[email protected]:/ # ls -l /data/local.prop
ls -l /data/local.prop
-rw-r--r-- system system 17 2013-01-15 17:29 local.prop
[email protected]:/ #
5. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
loader.sin
system.sin
(Remember to uncheck the wipe options!)
6. Turn the phone on. Open a command prompt into the files subfolder of the rootkit folder, like in step 4, or return to that window if you haven't closed it.
Type "adb shell". If you get a $ prompt, try "su" to get to "#". Once in adb, type "/data/local/tmp/step2.sh", then "reboot". The phone will reboot.
When it boots back, run adb shell again, and type "/data/local/tmp/step3.sh". You'll witness another reboot or maybe two. You should be rooted now.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # /data/local/tmp/step2.sh
/data/local/tmp/step2.sh
0+1 records in
0+1 records out
57 bytes transferred in 0.001 secs (57000 bytes/sec)
[email protected]:/ # reboot
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # data/local/tmp/step3.sh
data/local/tmp/step3.sh
43+1 records in
43+1 records out
22364 bytes transferred in 0.002 secs (11182000 bytes/sec)
1647+1 records in
1647+1 records out
843503 bytes transferred in 0.123 secs (6857747 bytes/sec)
2119+1 records in
2119+1 records out
1085140 bytes transferred in 0.089 secs (12192584 bytes/sec)
7. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
kernel.sin
loader.sin
(Remember to uncheck the wipe options!)
Do NOT skip this step: you need the LT25i kernel on your LT25i system!
8. Let's finish.
We will need adb shell once again. This time, you will need to type a few lines as follows:
Obtain root:
su
Remount /system:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
Remove /data/local.prop since it's a security hole; this is important and is normally done by the rootkit's step 3, but we needed to save the file to get to keep root access on our LT25i firmware:
rm /data/local.prop
And finally reboot:
reboot
Code:
G:\Android\LT25i\rootkitGXSX_v3\files>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
[email protected]:/ # rm /data/local.prop
rm /data/local.prop
[email protected]:/ # reboot
reboot
Done. You now have busybox, Superuser and su on your stock LT25i firmware.
Remember to clean up those pesky au apps.
Will link to the all in one. Many thanks
Good job translating!
Sent from your backyard...
Slender watches what you do...
I did some n00b experiments:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse :crying:
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?
datagubben said:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?
Click to expand...
Click to collapse
Using the Bin4ry approach should be possible since as far as I know it's the exact same backup/restore timing exploit, you probably need to recreate /data/local.prop though before flashing the V's system.sin. Or do you mean reducing the number of flashing operations to 2? That won't work, we need to regain root on V's system to get it to enable adb root shell with the V's kernel.
If you delete something from /system/app and the phone starts rebooting, it means you just deleted a part of the Timescape framework, I'd presume?
This method will clean up my installed app?
Dude i'm step 6 but I keep getting this prompt.
C:\Users\user\Documents\Development\Xperia\Xperia V\rootkit-sony\files>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
edit: now do i panic?
Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?
Gasai Yuno said:
Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?
Click to expand...
Click to collapse
Found my mistake, I'm going to try again Fifth time!
Edit: Done! Love you dude.
All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.
sunny7day said:
All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.
Click to expand...
Click to collapse
Because "some japanese" firmware is with exploit before it was fixed by Sony
where can I download official hong kong firmware? I am stuck on step 5.
sunny7day said:
where can I download official hong kong firmware? I am stuck on step 5.
Click to expand...
Click to collapse
I haven't seen HK firmware beeing uploaded here on XDA yet, but you can make yourself with PPC + flashtool (its not difficult, look in the forum how to do).
I just got the hk firmware and finished all the steps in the first post, now i am rooted.
Yes it is rooted but it left alot of unwanted au japanese sofware in my phone.
It should be noted in the first line in the first post of this thread.
But thank you anyways.
So, I have to wipe and re-flash my stock HK firmware.
Are there any other way to root my Xperia V without flashing other firmware?
If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
Remember to clean up those pesky au apps.
Click to expand...
Click to collapse
sunny7day said:
Are there any other way to root my Xperia V without flashing other firmware?
Click to expand...
Click to collapse
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.
Gasai Yuno said:
If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.
Click to expand...
Click to collapse
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!
datagubben said:
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
Click to expand...
Click to collapse
And if you do please PLEASE share it as we could do with it here
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
Click to expand...
Click to collapse
not a scooby doo fan then?
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
There is no way to know untill it lands on our devices, Sony can(and do) monitor what we do on this forum and, allthough they are quite dev friendly, do find way to fix the loopholes we exploit to get root access. They want us only to get that via an official unlocking from their site. You cant blame them for that, they are a big company and have lots of ways of losing contracts if they cant secure their system.
But you can be your bottom dollar tha if they close that exploit, we will find another way
[/quote]
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Click to expand...
Click to collapse
I know this is a personal message but the rules state this is an english speaking forum. You can post in other languages but an english translation is always required. (I know you dont need this next bit but..) Please use google translate if you have trouble with getting an english translation
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!
Click to expand...
Click to collapse
lol!
I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
I don't watch Scooby Doo.
I speak japanese and I said "I lived in Tokyo but not now".
S,h,i,t
datagubben said:
I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
Click to expand...
Click to collapse
I meant the other guy, in response to your post about making his own ftf, if he does, he should post it and share
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
Click to expand...
Click to collapse
not sure
I don't watch Scooby Doo.
Click to expand...
Click to collapse
google it and watch, a clasic kids cartoon with a classic catchphrase of "I would have got clean away with it, if it wasnt for you PESKY kids!
I speak japanese and I said "I lived in Tokyo but not now".
Click to expand...
Click to collapse
thanks
S,h,i,t
Click to expand...
Click to collapse
I gathered that
datagubben said:
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
c) Make a copy of your stock FTF file. Open the copy in Total Commander or 7-Zip. Delete everything except the manifest, loader.sin, kernel.sin and system.sin. No more app_log.sin appearing in Flashtool, yay!
d) Depends on two factors.
First, if the 4.1 update will replace the keys used to sign .sin files, removing compatibility with older firmware, this approach will be unavailable. This is what Motorola did with the DROID 2/X/2 GLOBAL.
Second, provided they don't replace the bootloader, and we can still flash back to 4.0: whether we will be able to retain root during firmware update (via OTA RootKeeper or whatever else exists).
As for the language filter, use Kunrei romaji (you know, the system where you use “si” instead of “shi” for し and “ti” instead of “chi” for ち) to work around it.
Related
You will have to manually install it via adb push or adb shell.
Below is the link for a package that contains /system/app and /system/framework fully deodexed and zipaligned (not signed). It's the Stock version, I didn't remove any apk or framework.
Use at your own risk!
Backup your /system before upgrade!
I did notice speed increase and better memory utilization.
http://www.usk.bz/android/system-deodexed.bz2
EDIT: Here is a quick howto do it. Do some research, speacially on the "Recovering from a software brick" thread posted by Designgears. You may need it, in ase you don't execute this right.
Warning: Do those steps carefully! If you get any error as a return for a command you did, stop immediately and post here with the error to make sure it's safe to continue or what you should do before continue.
1. Download the file system-deodexed.bz2 (it's a tar.bz2)
2. uncompress it with tar zxf system-deodexed.bz2. You will get a folder called "system" with two other folders inside(app and framework).
3. First push it to the device to a safe location (your internal sdcard):
Code:
adb push system /mnt/sdcard/deodexed/system
4. Now open an adb shell and backup the folders you will mess with to the sd card, in case you need to recovery them
Code:
adb shell
$ su
# mkdir /mnt/sdcard/original_system
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
# cp /system/app/* /mnt/sdcard/original_system/app
# cp /system/framework/* /mnt/sdcard/original_system/framework
5. Now the tricky part, you will get force closes on the device screen, because you will do this with the system running, don't worry for now. It should clear up once you are done. (Thx for the tip!) Lets update the system with the deodexed files. While still on the adb sheel as root, from the previous step, continue with these commands:
Code:
# stop
# mount -o rw,remount /dev/block/mmcblk0p12 /system
# cp /mnt/sdcard/deodexed/system/framework/* /system/framework
# cp /mnt/sdcard/deodexed/system/app/* /system/app
# rm /system/framework/*.odex
# rm /system/app/*.odex
6. Once you are done, exit the adb shell and do a reboot:
Code:
adb reboot
It should take a little longer to reboot, its normal for the first time. Then you should have normal boot speeds.
I recommend do this on a clear system, or that you do a factory reset once you reboot. The reason for that is that sometimes you get some data corruption during the force closes (corruption on the configuration files, not user data). But a factory reset fixes that.
If all go well, you have a deodexed system and are ready to use some Mods!
Have fun!
[ Known issues ]
- None! Please report if you notice anything!
http://forum.xda-developers.com/showthread.php?t=961382
Hey, here is a fully working on I did over the weekend.
Thanks! I didn't see it before. Will still compare with mine to see which package I messed up.
uskr said:
Thanks! I didn't see it before. Will still compare with mine to see which package I messed up.
Click to expand...
Click to collapse
usually packages with sound files get messed up for whatever reason when deodexing
designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Are you still planning on posting your mod version with steps? I am asking because I want to take look before making I own edits if necessary. I figured you may have it the way I want and it would less work for me either way.
designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Do you use an automated script to deodex them? or manually do one by one? The BOOTCLASSPATH dependencies sometimes give me some headache.
Also, do you mind to share which zip compression level do you use to repackage them?
Thank again!
designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Actually, I just tried yours and it has the same problem. Can you try to add the "Social Status" motorola widget to your MotoBlur and tap it to Setup your account and see if it starts something?
Mine doesnt start the Setup intent and I can see a Java exception on adb logcat.
uskr said:
Actually, I just tried yours and it has the same problem. Can you try to add the "Social Status" motorola widget to your MotoBlur and tap it to Setup your account and see if it starts something?
Mine doesnt start the Setup intent and I can see a Java exception on adb logcat.
Click to expand...
Click to collapse
Nevermind. Neither were bugged. I installed the deodexed without a data wipe and something got corrupted on the /data (some configuration file or something). I did a factory data reset and everything is working!
Not to play with changing some apks!
Hi guys,
I don't have an Atrix for now, so maybe it's just a dumb question. Sorry if it is.
With the Defy, if you push files and your phone won't reboot because you messed with something, you're screwed, as we don't have a true custom recovery. (you need a booting system to be able to get to the bootstap custom recovery, which you can't get into if your system is messed and the phone doesn't boot).
So when we are in that case with a Defy, our only option is to reflash a Motorola signed sbf file using RSD lite, root again, install again bootstrap recovery,... and try again ;-).
I guess it has to be the same with the Atrix (as the bootloader is locked as in the Defy)
So my question is:
- Are there already Atrix sbf files out there to recover a soft-bricked Atrix?
- If not, how do you recover it if you messed with the system files and the Atrix won't boot into a working system (of at least a state where you can get root shell though adb).
adlx.xda said:
So my question is:
- Are there already Atrix sbf files out there to recover a soft-bricked Atrix?
- If not, how do you recover it if you messed with the system files and the Atrix won't boot into a working system (of at least a state where you can get root shell though adb).
Click to expand...
Click to collapse
If you only messed only with /system/app or /system/framework folders/files, designgear posted how to recovery those files using the stock, that you can also download a tar with all the /system files from this forum.
Updated the post with a short howto.
If you get a software brick, search the forum for a post from designgears about how to recovery from a software brick.
As per the link below - I type "stop" once in the adb shell and it allowed me to transfer everything over without corrupting everything.
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html
slhawkins said:
As per the link below - I type "stop" once in the adb shell and it allowed me to transfer everything over without corrupting everything.
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html
Click to expand...
Click to collapse
Thx. Added to the howto!
uskr said:
Thx. Added to the howto!
Click to expand...
Click to collapse
Add the following to your instructions otherwise you will get an error message
You need the below line before the others
# mkdir /mnt/sdcard/original_system
The below are in your original instructions but the above is needed prior to the below
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
lpsi2000 said:
Add the following to your instructions otherwise you will get an error message
You need the below line before the others
# mkdir /mnt/sdcard/original_system
The below are in your original instructions but the above is needed prior to the below
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
Click to expand...
Click to collapse
Thanks! Updated.
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
NguyenHuu said:
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
Click to expand...
Click to collapse
Extract it to the file with no extension.
Open winrar.
Drag drop this file into that (u'll find the zipped up contents)
Drag drop these to ur desktop or anywhere u want them
NguyenHuu said:
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
Click to expand...
Click to collapse
push the file to sdcard of the device and using tar there after all it is also a linux system
diablo009 said:
Extract it to the file with no extension.
Open winrar.
Drag drop this file into that (u'll find the zipped up contents)
Drag drop these to ur desktop or anywhere u want them
Click to expand...
Click to collapse
great! thanks.
uskr said:
I recommend do this on a clear system, or that you do a factory reset once you reboot. The reason for that is that sometimes you get some data corruption during the force closes (corruption on the configuration files, not user data). But a factory reset fixes that.
Click to expand...
Click to collapse
Hi all,
I just did deodexed my atrix. Thanks much for the wonderful work~!!!
Mine has handful of apps installed prior to deodex. I was wondering what would be implication for not having clean system after deodex.
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
Generic Nvidia Tegra Secure Boot Key Dumper, v0.4
**************************************
YOU MUST GET ROOT BEFORE PROCESSING!!!
This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
**************************************
I am not sure it work for your devices or not, because I only get a SU660 device!
So , you must knew that P880 use a Secure Boot Key to encrypt its nflash communication, if you don't know the SBK, you can't use nvflash backup/restore your partitions.
I found that in the linux kernel, there is some protection that block the user try to read out SBK when the phone in "odm_production" status. So I designed a little software try to patch the phone RAM to bypass the protection.
This is a kernel patcher which will remove the protection when trying to read /sys/firmware/fuse/secure_boot_key
The dumper will patch the kernel in memory, and let you show the secure_boot_key.
Hope it work for all tegra devices.
Usage:
1. adb push dumpSBK /data/local/
2. adb shell
su
chmod 0777 /data/local/dumpSBK
/data/local/dumpSBK
After that, you can
4. cat /sys/firmware/fuse/secure_boot_key
dumpSBK will search the first 1MB physical address(which kernel will be there), and try to patch it.
Usage: dumpSBK [star_mem_addr in KB]
for example: dumpSBK 32
which will search the 32KB~1MB physical memory.
2012/12/31:
re-compile it with -static switch, so it can run on all android platform.
update instructions.
2013/01/01:
modify the program, and let you select which memory range to patch.
usage: dumpSBK [start_memory_addr] [end_memory_addr]
for example: dumpSBK 1 1024
which will search 1MB ~ 1024MB memory and try to patch the kernel.
2013/01/01:
v0.3 add more error detection in the file.
2013/01/06:
v0.4 wil search the first 1MB physical memory, you can specify the start_address , for example dumpSBK 32
and update the search pattern , it will fit for more compiler options.
2013/01/07:
Secure_Boot_Key Dumper for tegra2/tegra3 v0.1
1. adb push ss.ko /sdcard/
2. adb shell
su
cd /sdcard/
insmod ss.ko
dmesg
3. at the end of dmesg, you should see the secure_boot_key.....
2013/01/08:
v0.2 dump all known fuses.....
If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.
marsgod said:
If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.
Click to expand...
Click to collapse
will it hard brick the phone???
razerblade17 said:
will it hard brick the phone???
Click to expand...
Click to collapse
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:
SimonTS said:
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:
Click to expand...
Click to collapse
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up
The Troll said:
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up
Click to expand...
Click to collapse
Yep, i think Troll isn't trolling us i would try it out ,but i'm waitin' for my LG, factory reset via recovery bricked it.
This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
The patcher will patch a single byte in your phone RAM, it will not modify any bit in your NAND Flash.
C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
Click to expand...
Click to collapse
^ You guys have rooted phone and debugging turned on? maybe that's why these errors.
phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
C:\o4xr>adb push dumpSBK /data/local/
push: dumpSBK/Readme.txt -> /data/local/Readme.txt
failed to copy 'dumpSBK/Readme.txt' to '/data/local/Readme.txt': Permission deni
ed
Click to expand...
Click to collapse
So i put those files there with es file explorer and try to run second comand:
C:\o4xr>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
Click to expand...
Click to collapse
Who can explain why?
s7ar73r said:
phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
So i put those files there with es file explorer and try to run second comand:
Who can explain why?
Click to expand...
Click to collapse
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*
k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
I get the this,too.
the v1 patch did not completely work.
The Troll said:
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*
Click to expand...
Click to collapse
Its not the only known method... but now I don't have time, even to think... I just woke up and came to the computer.
You need to think widder
Gonna back to sleep :angel:
k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
En.... I think it is due to I compiled the dumpSBK with 4.1.2 android, so it will not work on a ICS rom... I will check it later...
s7ar73r said:
C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this
Click to expand...
Click to collapse
You MUST root your device.
then type
adb root
to get the adb rooted work.
Of couse, you must have your device USB debug ON.
please do all the steps the right way , starting with the OP instruction you the right way.
OP is assuming we got a "unsecure" booted device, which we have not exactly due to the locked bootloader.
so its pointless to write "root" instruction froms adb when the device is in secure mode. OP is now told and should update the instructions, thank you.
ignore all the "adb shell" instruction and log into the device with "adb shell" once only.
in that shell which is opened execute the "su", so you get a root # prompt.
then run instructions given and skip all "adb shell" infront.
thats it, good luck.
edit:
adb remount,adb root and running root commands only work on unsecure devices , we got ro.secure=1 here and adb not allowed to run root commands
i think it's better toroot Your 4X with Dexter http://forum.xda-developers.com/showpost.php?p=30574547&postcount=85 because it doesn't have any issues, for me with 1st root method for example titanium backup wasn't working.
@marsgod, yep - we don't have 4.1.2 but 4.0.3, but u can leave this version because we'll get 4.1.2 in january
k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?
bullghost said:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?
Click to expand...
Click to collapse
after adb shell type su, u should have [email protected], not [email protected]
@edit so... anyone tested it in right way?
Hi folks, I am at a loss on this one.
I was testing DooMKerneL v3 and v4 last night.
After installing V4 I decided to try and make an init.d script to control the volume levels. Here it is
Code:
#!/system/bin/sh
#init.d script by gregbradley xda recognised contributer;
#kernel level sound control;
#in conjunction with DooMKernel V4+;
#gpl_cam_mic_gain is Camera MIC;
#gpl_headphonbe_gain is Headphone;
#gpl _mic_gain is MIC;
#gpl_speaker_gain is Internal Speaker;
#each supports gain levels from 20 (-20) to 50 (+10), base is 40 (0);
echo "41" > /sys/kernel/sound_control/gpl_cam_mic_gain
echo "41 41" > /sys/kernel/sound_control/gpl_headphone_gain
echo "41" > /sys/kernel/sound_control/gpl_mic_gain
echo "41" > /sys/kernel/sound_control/gpl_speaker_gain
I made it with notepad++ with the correct EOL conversion. I called it 98ksoundtweaks and put it into
system/etc/init.d
I rebooted the phone several times, and each time it did not work with values set at 41.
I then edited the file in the phones text editor, then on the next reboot I got a bootloop.
Then after a hard reset I lost the touch screen capability.
Here is what I have tried to fix it.
Restore a working backup
Restore doomkernel v2 and a working backup
Factory reset and reflash Rom and kernel
Factory reset and flash stock kernel
Factory reset and flash stock ftf
None of them work. The next thing I am going to try is relock the bootloader and a PCCompanion repair, but I want to know if there is anything else I can try before that.
I am currently on doomkernel v2 with my last working backup flashed. I have checked and none of the v4 files are present, and none of the init.d scripts I wrote are present. I did not drop the phone, it was just connected via usb to my laptop and lay on my desk when this happened.
However, I can use my mouse with USB OTG
Any help would be appreciated
Re: Loss of touch screen
Tried wiping /system, /data, /cache and do a full fresh install of a rom?
Sent from my LT30p using Tapatalk 2
matt4321 said:
Tried wiping /system, /data, /cache and do a full fresh install of a rom?
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
gregbradley said:
Here is what I have tried to fix it.
Restore a working backup
Restore doomkernel v2 and a working backup
Factory reset and reflash Rom and kernel
Factory reset and flash stock kernel
Factory reset and flash stock ftf
Click to expand...
Click to collapse
Thanks, but I have tried that.
Re: Loss of touch screen
There was already a thread about this, where I wrote that I it would be safer to delete the touch firmware from /system/etc/firmware.
I think it was reflashed with error.
Try to reflash the firmware one more time.
But your problem could be somewhere else.
peetr_ said:
There was already a thread about this, where I wrote that I it would be safer to delete the touch firmware from /system/etc/firmware.
I think it was reflashed with error.
Try to reflash the firmware one more time.
But your problem could be somewhere else.
Click to expand...
Click to collapse
I just replaced the touch_module_id_0x32.img in system/etc/firmware with the one from my ROM, but it still does not work.
I will try a FTF flash again soon
Re: Loss of touch screen
I would skip straight to pccompanion.
Something may have cooked, the only way to rule it out....
Sent from my LT30p using Tapatalk 2
Re: Loss of touch screen
gregbradley said:
I just replaced the touch_module_id_0x32.img in system/etc/firmware with the one from my ROM, but it still does not work.
I will try a FTF flash again soon
Click to expand...
Click to collapse
I mean reflash touch firmware manually in terminal or adb. You can find the command in /system/etc/hw_config.sh.
Edit:
rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
There are some more options you can try:
Usage:
rmi4_fw_updater [options]
Options:
-h Print this help text
-b Complete path and name of firmware file
-d Path to the sensor to be updated
-f Force flash
-c Update config area
-e Don't erase chip before updating FW
-r Really force. Don't care about chip ID
-u Unconditionally do full FW update
But first use the command line with -r -f only.
cheers,
I am just pccompanion updateing ATM.
I will try those commands in adb if this does not work...
Pccompanion did not work.
Unlocked boot again. back to doomkernelv4 with my custom rom.
This is pain to do with no touch scrren..
@peetr_ can I just write that command in adb, or do I need to do adb shell first?
Re: Loss of touch screen
adb shell first and su
Reflashing should take about 2 or 3 secons, but there's no output, so try to restart and you'll see. Then I would try with other options (-c or -u).
done that
Code:
C:\Android>adb devices
List of devices attached
CB5121SC7S device
C:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img
-d /sys/bus/rmi4/devices/sensor00 -r -f
rmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f <
[email protected]:/ # reboot
reboot
C:\Android>
AND IT LIVES!!!!!!
Many thanks!!!!!!
Good.
Now delete the fw from /system/etc/firmware.
What does that do?
Sent from my star trek communicator
Sony Flagship device circa 2145
It looks like real firmware for the digitizer.
From hw_config.sh:
# Touch FW updater. Force firmware upgrade if necessary (for e.g. if'function 11' is missing.)
There is this condition, when something is missing on boot, the firmware is reflashed.
While we are still trying, flashing, restarting and the system checks for filesystem integrity (triangle), this condition could be met for some reason and the firmware is reflashed, even when it shouldn't. And it seems like it can be reflashed with error (maybe without those -r -f flags).
I don't see any good reason for reflashing touch firmware so I suggest to rename or delete it or change that script.
If we get some update with new fw update, we can pull it back.
Ok, but won't deleting it from system/etc/firmware produce problems?
Sent from my star trek communicator
Sony Flagship device circa 2145
No. It's there only for reflash. Fw is inside the digitizer.
It causes problems when it's there.
Ok, still learning new stuff every day here on xda.
I have renamed it.
Sent from my star trek communicator
Sony Flagship device circa 2145
Unresponsive touch screen
peetr_ said:
I mean reflash touch firmware manually in terminal or adb. You can find the command in /system/etc/hw_config.sh.
Edit:
rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
There are some more options you can try:
Usage:
rmi4_fw_updater [options]
Options:
-h Print this help text
-b Complete path and name of firmware file
-d Path to the sensor to be updated
-f Force flash
-c Update config area
-e Don't erase chip before updating FW
-r Really force. Don't care about chip ID
-u Unconditionally do full FW update
But first use the command line with -r -f only.
Click to expand...
Click to collapse
Yesterday I unlocked BL and when I flashed new kernel (DooMKernel v4). Still I don't understand what happened but my touch screen became unresponsive. I thought it was caused by wrong ROM (I am using Xperiment v2.3 and there are separate versions for locked and unlocked BL) so I replaced it with the second one (for unlocked BL). But it didn't helped anyway and I noticed that touchscreen is unresponsive also in touch version of TWRP (included in the latest DooMKernel) so it is probably not related to ROM. After many attempts and searching I bumped into this thread and tried to apply your command above and it worked!!! Thanks a lot.
I am just disturbed by the fact I don't understand how I got into this situation so I don't know how to avoid it in the future. Do you have any idea what happened?
All I can tell to this problem, I wrote here - http://forum.xda-developers.com/showpost.php?p=39921357&postcount=14
I suggest to rename the touch firmware image in all ROM's.
Today i ran into same issue where i flashed touch firmware T from to my TX while i was playing with some mods
I was able to recover it by flashing back to stock ICS firmware
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.