Related
Ok so here it is almost day 2 trying to install CWM on zv8 after using "mt's easiest way to keep root thru zv8'. (Oh and by the way MT your the MAN). Now getting to zv8 was easy, But getting the recovery installed is another issue all together. First started with the AIO bat. file which installs cwm (kudos to MT and djrbliss). And it reads
"system cannot find the path specified'.
SO ok well apparently the computer isnt reading the phone found out the driver has issue shows the error message(on both my laptops).
ok lets try the terminal emulator with
brad6360 said:
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.
Click to expand...
Click to collapse
didn't work and I the local.prop file in the data folder.
Someone PLEASE HELP!!!
(not a noob or expert but I can read and follow directions lol)
Are you sure you still have root level access?
Does adb detect your phone at all?
Still have root access I used root explorer to add the local.prop.
Adb recognizes my phone it shows a serial number under adb devices
Is there a way I can flash cwm in adb?
Sent from my VS910 4G using XDA
Use the newest aio from Mt. It worked for me. The simplest way is to flash the v7.tot then 'JUST' root, create the local.prop file, then ota to v8. Then continue on with Mt's aio to install cwm. Don't worry about having complete root access (cuz I didn't, but had cwm). Flashed broken out and haven't looked back.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
What happens when you go into recovery? Is it the stock recovery? Stock v8 didn't have the option to boot into recovery. Just a thought. When I did it I got a lot of errors, but it took.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
mrand1 said:
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
I have the same problem, Even when i Flash zv7 tot and try old AIO it says
Cannot find specified path
and i am not a noob and have broken out an old revo with mt's help but this new one with pre loaded zv8...No luck yet
had to manually push
I'm glad that I'm not the only one having this issue
Can you use Root Explorer to check and make sure adb is pushing the image file to your phone? Look in this directory: /data/local/tmp/cwmrecovery.img
You could always do this manually using adb. Here's how.
1. Open the ZV8CWMRecovery folder on your PC.
2. Double click the 'Files' folder to go into that directory.
3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:
Code:
C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files
4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.
5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.
6. You should now be positioned in the folder containing the adb and CWMRecovery files.
7. Type the following to copy the CWMRecovery image to your phone:
Code:
adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot
Phone should reboot. Try and boot into CWMRecovery after it reboots.
idk if I'm not doing something right or wrong. I have usb debugging and internet connection, and I'm getting "remount failed: operation not permitted".
I had the same issue but following these instructions helped me, what finally helped me was typing a wrong command wich gave me a help menu with all the commands, the important one being "adb reboot [Recovery:Bootlaoder]"
adb reboot recovery did the trick, then wiped flashed broken out and sooo happy to be done with it.
after pushing CWM in command prompt of course
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
slimzim said:
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
Click to expand...
Click to collapse
I did the same thing, flashed to zv8 tot, was able to root but was unable to flash cwm recovery. I tried manually doing it and running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img. It appears I do not have any recovery either. Trying to get to Broken Out! Any help is appreciated, thanks guys!
asauber said:
I tried ... running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img.
Click to expand...
Click to collapse
For what it's worth I also tried that with the same results.
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
Man, that was too easy!
Thanks for posting this slimzim. This worked straight away for me, I'm installing Broken Out as I type! I'm actually a little glad this happened because now I'm a little more familiar with terminal emulator and what local.prop does. Never had to use it in the past. This is exactly the second phone I've ever rooted and am usually able to just use AIOs.
And of course, thanks to mtmichaelson for chatting with you about it and doing all the hard work in the first place!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
So far not working...repeating process now...
da_morales said:
So far not working...repeating process now...
Click to expand...
Click to collapse
If you've done all steps exactly it should work. I went through a ton of other "fixes" that didn't work, I believe the key here is when you use the terminal emulator directly on the phone to create local.prop. I was trying to create local.prop in every way but that, and until I did it directly on the phone did I have success.
Good luck!
local.prop missing
I used the Easy ZV8 All in One Rooting Tool, and have no sound at all like a couple of other users. One of the suggestions was to rename the local.prop file in the /data folder to local.prop.bak.
I assume this is the /data folder in the internal folder? When I did the steps for the all in one rooting tool (coming from rooted zv7), there is no local.prop file in my /data folder to rename, yet I still have no audio for ringtones, phone calls, etc. except for the boot up sound on the splash page.
Any ideas why my local.prop file isn't even there? I even tried copying the one from the mtmichelson zip file into there, still no avail. Thanks!
I have the same issue. I used the echo command in term emulator and the local.prop file was there. rebooted and the file is gone. I have root but cannot install cw recovery. I have tried AIO, adb, and terminal emulator but nothing makes it stick. Any help would be greatly appreciated
Rob
Hello,
I had posted this in Frequently Asked Questions about the LG Optimus 4x HD but got no help so I post here for a last try.
Just followed all dexter's steps in this thread to flash CMW
http://forum.xda-developers.com/showthread.php?t=2180138
but I got stuck here. Tried to read 34 pages of the thread but still couldnt solve my problem
My LG was rooted and unlocked.
Any help? thanks
Ekio
The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/
AlderCass said:
The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/
Click to expand...
Click to collapse
Tried and still not such files and directory thx anyway
ekiong said:
Tried and still not such files and directory thx anyway
Click to expand...
Click to collapse
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...
Bogeyof said:
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...
Click to expand...
Click to collapse
Omg I already did
Look pics
ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...
RuedasLocas said:
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...
Click to expand...
Click to collapse
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
---------- Post added at 06:48 PM ---------- Previous post was at 06:40 PM ----------
ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
Did you do it in recovery mode from the start? When I did it it was when the phone was just switched on normally into the main OS.
ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
Click to expand...
Click to collapse
Where the hell did you found that path /mnt/sdcard/....... ???
Tutorial CWM
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:
RuedasLocas said:
Where the hell did you found that path /mnt/sdcard/....... ???
Click to expand...
Click to collapse
It's in the system root for me, it's a symlink. Though it didn't work for me in the cat command, which is why I suggested using /storage/external_SD/ instead which did work for me. It looks like the OP has the files in the right places, and the hash in the command line screenshot implies that SU is working correctly, so I'm all out of ideas now.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
Click to expand...
Click to collapse
Little bit arrogant, we're all trying to help here, so I hope for your sake your way works for the OP
AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
Click to expand...
Click to collapse
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:
Click to expand...
Click to collapse
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.
ekiong said:
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.
Click to expand...
Click to collapse
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Dexter_nlb said:
......
GUIDE:
1. when you are running unlocked bootloader and is rooted goto step 2.
2. download attached zip files and extract content to internal sdcard location
3. use adb shell or terminal from market and execute the commands below
4. you are now running with native CWM recovery and unsecure boot, which enable adb root at boot instantly.
5. boot into recovery, by rebooting device and hold VOL-DOWN during bootup. (from power-off = keep holding vol-down during power on)
execute these 3 commands for recovery image install
Code:
su
cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
execute these 3 commands for unsecure boot image install
Code:
su
cat /mnt/sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
or see screenshot here
do this at your own risk, and do NOT try this on old 4.0.3, which is not with unlocked bootloader, and you are required to install KDZ again.
THANKS to:
skydev - for his continued effort in finding root and giving our device full freedom with boot/recovery.
Click to expand...
Click to collapse
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !
RuedasLocas said:
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !
Click to expand...
Click to collapse
Still no such file, I give up :angel:
Thx every one
ekiong said:
Still no such file, I give up :angel:
Thx every one
Click to expand...
Click to collapse
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."
RuedasLocas said:
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."
Click to expand...
Click to collapse
OH MY GOD I'm stupid, I copied files with ZERO byte.
sorry I used airdroid to copy them to my phone. But only their icons moved into my phone, not contents.
It works now THANKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS :laugh:
Close thread and my stupid problem :silly:
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.
Im following the guide on the unlocker.com. I can root the watch, flash the custom recovery with odin and copy the file over null.zip file.
The trouble i encounter is when trying to enter twrp by selecting recovery.
The android sign comes up with installing update? and then it boots back into the operating system and i have to repair it with my note 3 again? am i doing something wrong or is it just sods law?
Thanks for the help in advance
I had the same problem with mine. You have to enter the following commands after rooting to make the new recovery stick (note, don't put the $ and # symbols in the command) -
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
Full Throttle1 said:
I had the same problem with mine. You have to enter the following commands after rooting to make the new recovery stick (note, don't put the $ and # symbols in the command) -
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
Hi is this with the windows command? the rooting method im following is using an impactor.exe to supersu onto the system and then installing supersu on the watch with wondershare mobilego? is this the same as you?
dav08094194 said:
Hi is this with the windows command? the rooting method im following is using an impactor.exe to supersu onto the system and then installing supersu on the watch with wondershare mobilego? is this the same as you?
Click to expand...
Click to collapse
Correct. You do it through the Windows command (after rooting), the same way you flash the new recovery (TWRP) through ADB. So before flashing, type those commands and it'll allow the new recovery to stick without reverting back to the factory Samsung software every time you enter the recovery mode.
Full Throttle1 said:
Correct. You do it through the Windows command (after rooting), the same way you flash the new recovery (TWRP) through ADB. So before flashing, type those commands and it'll allow the new recovery to stick without reverting back to the factory Samsung software every time you enter the recovery mode.
Click to expand...
Click to collapse
Hi jumping in here as appears I am having the same issue. Question the recovery is added through Odin and then the ROM is added through Wondershare directly to the SD card on Gear. Where and how are the commands you typed to be added? Thinking original poster and I are in the same boat. I go to flash recovery and get complete reboot.
ptfd139 said:
Hi jumping in here as appears I am having the same issue. Question the recovery is added through Odin and then the ROM is added through Wondershare directly to the SD card on Gear. Where and how are the commands you typed to be added? Thinking original poster and I are in the same boat. I go to flash recovery and get complete reboot.
Click to expand...
Click to collapse
The correct way of installing null_ would be:
1. Root your Gear
2. Enable ADB in your Gear (Search how to enable)
3. Conenct to PC and install Gear adb drivers
4. Download ADB to your PC, unpack, in explorer go to the adb folder, Hold shift and right click the mouse, choose "Start command prompt here"
5. Run the commands listed in this thread.
6. install TWRP using odin.
7. Move your null_ zip file to Gear storage using wondershare
8. Reboot Gear into Recovery and install your null_ zip.
That should be about it... There is great guides on this forum that explains every step more detailed.
st-tps said:
The correct way of installing null_ would be:
4. Download ADB to your PC, unpack, in explorer go to the adb folder, Hold shift and right click the mouse, choose "Start command prompt here"
5. Run the commands listed in this thread.
That should be about it... There is great guides on this forum that explains every step more detailed.
Click to expand...
Click to collapse
Thats step apepars I am having issue with... is ther detailed explanation how to do? I have ADB on puter but lost once I get to "prompt" part as I've never used this method in any of my previous roots/roms.
ptfd139 said:
Thats step apepars I am having issue with... is ther detailed explanation how to do? I have ADB on puter but lost once I get to "prompt" part as I've never used this method in any of my previous roots/roms.
Click to expand...
Click to collapse
Try the thing I explained:
Hold shift on keyboard and the rightclick anywhere in the folder window. You will get a new alternativ saying something like "Start command prompt here", choose that and a command window shows.
Now copy and paste row one and press enter, row two and so on... You should notice if things go good or bad.
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Over the last few months development on the LG L90 has made some great strides, up to the point where we can actually install roms! In order to do this, however, you'll need an unlocked bootloader.
The problem that arises is that there are different models of the L90, being the D405, the D405n, the D410 and the D415. For most of the models the unlock process is very similar, but for the D415 another method is needed.
This guide is aimed at explaining the entire unlock process in a complete and simple way, so even if you have no experience flashing custom recoveries or roms at all, you should still be able to follow this guide. If you run into problems, please just post a reply or send me a PM and I'll do my best to help you.
First of all I'd like to note that I did not develop any of the bin files or apks in this guide, I'm only collecting all the unlock methods in one place for easy reference. Therefore I am not responsible for you bricking your device or causing any kind of damage to it. You follow this guide AT YOUR OWN RISK! That being said, let's get to the unlocking!
What you'll need to unlock the bootloader
1. A rooted LG L90
You can root the phone by going to https://towelroot.com in your mobile browser and tapping the lambda sign. Save and install the apk (make sure unknown sources are enabled in "menu > general > security"). Google will warn you about the app, this is because of the exploit which will enable the root access. Execute the program and tap "make it ra1n", then install supersu from the play store. Open supersu and choose to rebuild the binaries. This will fail, but after a reboot supersu should be installed and working properly.
UPDATE: If towelroot doesn't work for you, you've probably got the L90 with an updated firmware. In that case you can follow this guide by @gdjindal to obtain root access. Afterwards you can follow the rest of this guide again.
2. Have adb installed.
just download the Android sdk and install it or, if you don't care about the SDK itself, the minimal adb from the bottom of this post (thanks to @shinobisoft for the upload). Now add the C:/path_to_the_sdk/sdk/platform-tools to your windows PATH variable (Windows 7: right click my computer > properties > advanced system settings > environment variables) or the foler in which adb.exe is located if you downloaded the minimal adb..
On your phone go to "menu > general > about phone > software information" and tap build version a few times untill it says you're a developer, then go to "menu > general > developer options" and enable usb debugging. Connect the phone with your PC and choose to connect in software mode and install the drivers and tools. When you get a message on your phone that your PC want to access usb debugging make sure you check the checkbox and accept. Now open a cmd prompt and type "adb devices" without the quotes. If it shows a series of letters and numbers followed by device, you're good to go. If it says unauthorized, you haven't accepted the prompt on your phone yet. If your device doesn't show up at all you haven't installed the drivers correctly.
3. Find out which device and software version you're running.
Go to menu > general > about phone > Hardware information for your Model number. Mine is LG-D405n, so my model is D405n.
Go to menu > general > about phone > Software information for your Software version. Mine is V10b-EUR-XX, so I've got version v10b.
4.1 If your model number is D405, D405n or D410, you'll need a modified aboot.bin to unlock the bootloader.
Go to the bottom of this post and download the file with your model and software version. I used the L90_D405n_v10b_hack.zip. Extract the aboot.bin in the zip file to a folder on your PC.
4.2 If your model number is D415, you'll need another method to unlock the bootloader, which is explained in this thread made by @aSuperSaiyanG0D.
Unlocking the bootloader on the D405, D405n and D410
1. Open a cmd window an CD to the folder where you've saved the aboot.bin you've downloaded in step 4.1
2. Execute the following commands:
Code:
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Right after the su command, supersu will give you a root request on your phone that you'll have to accept!
This will also make a backup of your current aboot partition as stockaboot.bin on your external SD card. If you don't have an external SD card, this won't work and you'll have to use /storage/emulated/0 (this is a zero, not the letter o) instead of /storage/external_SD/ like this:
Code:
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin 5429599
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
3. That's basicly it, you can now install a custom recovery. I suggest downloading the latest TWRP (2.8.0.0 right now) from @shoxxy's thread, which can be found here. Just use ROM Toolbox to install it, choose rom installer, press settings > flash image and select the TWRP image from @shoxxy's thread. Afterwards you can boot to recovery using ROM Toolbox, or by shutting down the phone, holding volume down and power untill the lg logo shows, then releasing and immediately pressing those buttons again. You should get a screen asking to perform a factory reset. Choose yes twice (don't worry, it wont actually perform the reset) and TWRP should boot up. Now you can create backups and install custom roms too!
If you're a fan of cyanogenmod, you should visit @Quarx's thread, which can be found here. His CM11 is already mostly functional (right now on some models the front camera doesn't work and the ir blaster doesn't have any software, but most other functions actually do work very well, while it is faster than LG stock and gives almost twice the battery life), so if you like CM it's a thread worth keeping an eye on.
Flashing back the stock rom (in case of a brick)
If you've bricked your device, or want to revert to stock for any reason, you can follow this guide made by @gdjindal.
Post reserved
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Gabe.INc said:
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Click to expand...
Click to collapse
If you have a problem with step 4.2 only, I assume you have a D415 and you should actually ask this question in the thread that step 4.2 links to. Or isn't that what you meant?
EDIT: please note that step 4.2 is for the D415 ONLY.
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Gabe.INc said:
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Click to expand...
Click to collapse
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
SubliemeSiem said:
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
Click to expand...
Click to collapse
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Gabe.INc said:
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Click to expand...
Click to collapse
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Mind that I've only tested this using the external SD, but it should work both ways.
Error 1
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
BTW: what's the output of
Code:
adb devices
?
SubliemeSiem said:
Gabe.INc said:
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
SubliemeSiem said:
Gabe.INc said:
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Gabe.INc said:
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Where did you get the not found message? And what do you mean you flashed stock again? If you couldn't execute the dd commands then your bootloader is still locked and all you've done so far is root the device..
UPDATE: I don't get a response, but it seems this user previously flashed the wrong aboot.bin (or did something else, unfortunately he's not being very clear on that) so please only follow this guide when you have a stock recovery + aboot partition. If you did try some things before, please flash the stock rom back first and then follow this guide.
Thats awesome! Thank you! :cyclops:
guilherme.fuzo said:
Thats awesome! Thank you! :cyclops:
Click to expand...
Click to collapse
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
SubliemeSiem said:
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
Click to expand...
Click to collapse
I found no problem, but anyway thanks dude! :laugh:
guilherme.fuzo said:
I found no problem, but anyway thanks dude! :laugh:
Click to expand...
Click to collapse
Then don't say thanks, but hit the thanks button on the first post!