So Ive been following this tutorial:
http://www.androidauthority.com/man...kitkat-nexus-7-20122013-wifi-nexus-10-317138/
and I'm stuck at Step 9.
I'm using Ubuntu and when I go to terminal, I have no idea on how to "navigate to platform tools". I think I did, I'm not sure, but when I typed in "adb sideload kitkat", it doesn't recognize the term "adb".
Can anyone help me with this, please? :/
We can chat with Google+ to make this quicker!
sudo apt-get install android-tools-adb android-tools-fastboot
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 09:33 PM ---------- Previous post was at 09:29 PM ----------
sudo apt-get install nautilus-open-terminal to open folders in the terminal.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
platform-tools right click open in a terminal
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
xMoKax said:
So Ive been following this tutorial:
http://www.androidauthority.com/man...kitkat-nexus-7-20122013-wifi-nexus-10-317138/
and I'm stuck at Step 9.
I'm using Ubuntu and when I go to terminal, I have no idea on how to "navigate to platform tools". I think I did, I'm not sure, but when I typed in "adb sideload kitkat", it doesn't recognize the term "adb".
Can anyone help me with this, please? :/
We can chat with Google+ to make this quicker!
Click to expand...
Click to collapse
In Ubuntu, Ctrl + Alt + T to open terminal
Then use the command cd to navigate to the platform-tools directory.
Example:
cd ~/Desktop/sdk/platform-tools
platform-tools is the directory (folder) that houses the programs adb and fastboot. It's part of the sdk you downloaded from Google in the "What you need" portion of the guide.
Sent from my Nexus 6 using Tapatalk 4
Related
I've downloaded redbend_ua and the clockwork recovery image. They're both currently on my sdcard's root. I'm trying to copy redbend_ua, but there's no 'cp' command???
I've been a Linux SysAdmin for over 5 years, so I'm comfortable on the command line. Where's cp? Is there an easy way to install bash 3?
Sent from my SPH-D700 using XDA App
I can't link the post with tapatalk, but detailed instructions are in a post labeled "Clockwork recovery no computer method"
By default the cp command isn't included in android... it is included in busybox. There is an app on the market, and the one click roots install it by default. Without busybox the cat command is used as so: cat > .
Sent from my SPH-D700 using Tapatalk
Wow... I'm embarrassed I didn't try that. I'm usually against piping cats but sfobv that's what is needed.
Sent from my SPH-D700 using XDA App
I got a new nexus 7 to day and I'm trying to install cwm and when I try to Adb terminal gives Adb command not found. Help please?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Did you install the Android SDK on your PC first? There are other sources of ADB, too. ADB is not built in on Ubuntu. Or, are you doing this on your N7?
I have all that installed. I have the Adb file and the fast boot file and I cd'd to them and when I try to use the "Adb reboot bootloader" command I get Adb command not recognized.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Are you actually using a capital A as in Adb? That would not work.
No that's just how my phone is correcting it.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Just remembered something... adb is a 32-bit app. You need to install a 32-bit library on a 64-bit machine to get it to run. Can't remember the name off the top of my head...will try to find it.
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
sudo apt-get install ia32-libs ... see if that works for you...it will take a while to install.
Okay, I'll try that when I can. Thanks. Is there a way for me to mount my n7 on here as mtp?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
spitfire2425 said:
Okay, I'll try that when I can. Thanks. Is there a way for me to mount my n7 on here as mtp?
Click to expand...
Click to collapse
Have had no luck with MTP on Ubuntu myself. To get files to my N7 without adb, I either use a USB stick with an OTG cable or the AirDroid app.
I'd try some kind of cloud storage but I don't have Internet access which makes things that much harder.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
spitfire2425 said:
I don't have Internet access which makes things that much harder.
Click to expand...
Click to collapse
I feel for you as I am in the same boat much of the time. Makes life hard.
Try "./adb ...." etc
Otherwise you will need to "chmod +x adb", then try the above.
Good luck!
./adb worked! Thank you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I dropped my N4 today. The screen cracked, and most of the touchscreen is not responsive (the screen image appears fine). My device is protected with a numeric PIN.
1. Any ideas on how to recover data (specifically photos) from the device. The device connects to my PC via USB, but I can't view the drive contents without entering the PIN, and I can't enter the PIN because the touchscreen doesn't work.
2. Second, I'd like to wipe the device, again without using the touchscreen. I'm assuming I can do this with the Nexus Root Kit and/or ADB/Fastboot commands.
Any advice, particularly on (1) above, would be greatly appreciated!
Hmm..
Well, i cant say I have tried to do this with a locked phone, but you should be able to do everything from your computer. and through adb, and fastboot.
For example to get ADB installed on your computer follow this quick guide: http://www.addictivetips.com/mobile/...ll-it-android/
and once that is done then open up "Command Prompt" if you are using Linux it would be the "terminal"
then navigate to the folder that has the files in it. To navigate you want to use simple commands like cd.. and cd Name_of_folder. "cd.." means go back to the previous directory. And for "Cd Name_of_folder" Means you want to go to the folder "Name_of_folder , for example you are in c drive, and you are trying to go to a folder called "Cats" you would type "cd Cats" and then it would take you there. command prompt is uppercase sensitive btw.
So once you are in the folder that has adb, type "adb pull /sdcard/dcim" and that should pull your entire folder.
EDIT: also you need to be in recovery to do the adb pull correctly, to get there you can hold down the power button long enough for it to restart, and when it does hold both volume button at once.
Good luck.:good:
If it didnt work, let me know.
capeorigins said:
Well, i cant say I have tried to do this with a locked phone, but you should be able to do everything from your computer. and through adb, and fastboot.
For example to get ADB installed on your computer follow this quick guide: http://www.addictivetips.com/mobile/...ll-it-android/
and once that is done then open up "Command Prompt" if you are using Linux it would be the "terminal"
then navigate to the folder that has the files in it. To navigate you want to use simple commands like cd.. and cd Name_of_folder. "cd.." means go back to the previous directory. And for "Cd Name_of_folder" Means you want to go to the folder "Name_of_folder , for example you are in c drive, and you are trying to go to a folder called "Cats" you would type "cd Cats" and then it would take you there. command prompt is uppercase sensitive btw.
So once you are in the folder that has adb, type "adb pull /sdcard/dcim" and that should pull your entire folder.
Good luck.:good:
If it didnt work, let me know.
Click to expand...
Click to collapse
Great tips, thanks!
Unfortunately, while Windows is recognizing my device, ADB is not recognizing it. This may be because the device is locked, may be because the phone is set to MTP file transfer (for some reason, adb only recognizes my device when it's in PTP mode), or something else altogether.
ddb540 said:
Great tips, thanks!
Unfortunately, while Windows is recognizing my device, ADB is not recognizing it. This may be because the device is locked, may be because the phone is set to MTP file transfer (for some reason, adb only recognizes my device when it's in PTP mode), or something else altogether.
Click to expand...
Click to collapse
Hmm, is it in recovery?
capeorigins said:
Hmm, is it in recovery?
Click to expand...
Click to collapse
I can boot into recovery.
ddb540 said:
I can boot into recovery.
Click to expand...
Click to collapse
ok, good, do that and then try adb pull.
capeorigins said:
ok, good, do that and then try adb pull.
Click to expand...
Click to collapse
Same deal, adb won't recognize device from recovery, either, even though Win7 Device Manager shows Android Phone | Google Nexus 4 BootLoader Interface as one of my devices.
Well then you will need to install the adb drivers, I'll give you a link in a minute
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 08:51 PM ---------- Previous post was at 08:46 PM ----------
Here, try this: http://developer.android.com/tools/extras/oem-usb.html
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 09:02 PM ---------- Previous post was at 08:51 PM ----------
That's really weird that it added my new message to the old? Just in case you didn't notice it here's the links: http://developer.android.com/tools/extras/oem-usb.html
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 09:21 PM ---------- Previous post was at 09:02 PM ----------
Hello?
I already have these drivers installed. Still, adb won't recognize the device when the device is booted up, and won't recognize the device when in recovery mode.
So, when your phone is in recovery, and plugged in, in device manager does it show a "?" Or something near the icon of the phone?
Sent from my Nexus 4 using Tapatalk 4
capeorigins said:
So, when your phone is in recovery, and plugged in, in device manager does it show a "?" Or something near the icon of the phone?
Click to expand...
Click to collapse
Device manager shows it as attached when in recovery mode.
Hmm, I think you might be in bootloader? What does it look like on your screen?
capeorigins said:
Hmm, I think you might be in bootloader? What does it look like on your screen?
Click to expand...
Click to collapse
You're right! I booted into recovery, and now adb recognizes my device! I pulled all SD card contents to my PC, which includes the photos I was trying to save.
Thanks so much for the help, and sorry for being dense; your first post should have been enough to get me through this.
ddb540 said:
You're right! I booted into recovery, and now adb recognizes my device! I pulled all SD card contents to my PC, which includes the photos I was trying to save.
Thanks so much for the help, and sorry for being dense; your first post should have been enough to get me through this.
Click to expand...
Click to collapse
I'm glad I could be of help
And you helped me too! Because I didn't have enough posts to post comments to a dev-forum. And now I do
So, yeah!
Sent from my Nexus 4 using Tapatalk 4
I need someone running mi9 to upload there boot.img for a rom i am working on.
open adb terminal on your computer, and do these commands
adb shell
su
mkdir /sdcard/Mi9
dd if=/dev/block/mmcblk0p14 of=/sdcard/Mi9/boot.img
ok now it is on your internal sdcard in a folder called Mi9.
Please upload it
drakeymcmb said:
I need someone running mi9 to upload there boot.img for a rom i am working on.
open adb terminal on your computer, and do these commands
adb shell
su
mkdir /sdcard/Mi9
dd if=/dev/block/mmcblk0p14 of=/sdcard/Mi9/boot.img
ok now it is on your internal sdcard in a folder called Mi9.
Please upload it
Click to expand...
Click to collapse
I have it in a zip! I am just waiting for it to upload!
Awesome. Thanks
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I don't know whats going on but it doesn't seem to want to upload. I can always email it or something if nothing else.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
---------- Post added at 10:40 PM ---------- Previous post was at 10:36 PM ----------
drakeymcmb said:
I need someone running mi9 to upload there boot.img for a rom i am working on.
open adb terminal on your computer, and do these commands
adb shell
su
mkdir /sdcard/Mi9
dd if=/dev/block/mmcblk0p14 of=/sdcard/Mi9/boot.img
ok now it is on your internal sdcard in a folder called Mi9.
Please upload it
Click to expand...
Click to collapse
I hope this link works instead.
https://www.dropbox.com/s/wel0afz00dxmsof/boot.zip
Yes it does. Thank you.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Somehow i double posted the link. oops
here is mine if you need from another phone https://www.dropbox.com/s/j7xp8o402mw6l5x/boot.img
Let me know if you still need my boot.img
thats all I need. Will start working on it somemore when I get home.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Hi guys, I didnt have much luck with the Easy Recowvery method on my G5 (20A)
Sooo, i thought i'd share with you, (what i like to call) Hard Recowvery method.
This is the most effective way i've rooted & installed TWRP my H830 on 7.0 (Nougat)
First lets download the neccessary recowvery files located here (Put them all in a folder): https://build.nethunter.com/android-tools/dirtycow/arm64/
Make sure you have the latest twrp for your phone: https://twrp.me/devices/lgg5h830.html
Latest Verity zip: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Latest SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
---
Shift+Open Command window in Recowvery folder
Note: Use app_process32 on 32-bit targets.
once in cmd window from your recowvery folder follow these steps:
---
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 0777 *
$ ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
$ ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
$ exit
adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
adb shell
$ getenforce
"<it should say Permissive, adjust source and build for your device!>"
$ cd /data/local/tmp
$ ./dirtycow /system/bin/run-as recowvery-run-as
$ run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
$ run-as su
(You need to rename the twrp img to "twrp.img" and put in the root of your internal storage, OR you can use this adb push command. The next two steps wont be neccessary if already done so.)
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
---
You should be in TWRP now,
flash supersu and the verity 4.1 zips. [Format Data] will remove internal storage encryption. so back up everything you need to with nandroid. lg backup, or titanium. (So i saw that they have updated verity zips but i just used 4.1)
I prefer lg backup, its easiest.
After you format data reflash supersu and verity zips for the hell of it. (you dont have to i dont think but i just did anyway)
Now just reboot, & enjoy
This isnt a method i created, i got it from this thread. and made the steps i felt were neccessary.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Works until "run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery" then says:
Current uid: 0
We have root access!
------------
Executing: 'dd' with 2 arguments
dd: /sdcard/twrp.img: No such file or directory
1|h1:/data/local/tmp #
No Twrp recovery any help?
---------- Post added at 08:47 PM ---------- Previous post was at 08:07 PM ----------
Forgot to rename recovery.
---------- Post added at 09:32 PM ---------- Previous post was at 08:47 PM ----------
Problem solved! Forgot to rename img.
Tinbender418 said:
Works until "run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery" then says:
Current uid: 0
We have root access!
------------
Executing: 'dd' with 2 arguments
dd: /sdcard/twrp.img: No such file or directory
1|h1:/data/local/tmp #
No Twrp recovery any help?
---------- Post added at 08:47 PM ---------- Previous post was at 08:07 PM ----------
Forgot to rename recovery.
---------- Post added at 09:32 PM ---------- Previous post was at 08:47 PM ----------
Problem solved! Forgot to rename img.
Click to expand...
Click to collapse
The 2 agreement how did u type it BC I had that but I didn't know what to type so I use the toolkit instead
Sent from my LG-H830 using Tapatalk
Rename to twrp.omg move to internal sd card.
Sent from my LG-H830 using Tapatalk
sorry guys i was busy! & yes you need to rename the recovery img to "twrp.img". i will add the step to rename the twrp file!
djevil said:
The 2 agreement how did u type it BC I had that but I didn't know what to type so I use the toolkit instead
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
Just copy and paste everything as you see it. and if you mean you didnt know how to rename twrp recover just rename to "twrp.img"
so my getenforce keeps saying enforcing?
---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------
and the command to run-as exec says no exec found?
---------- Post added at 10:50 AM ---------- Previous post was at 10:39 AM ----------
Hmm so after looking it up, apparently my brand new G5 I just got today is on 20c and not 20a. I guess that is the problem?
hello?
jdkzombie said:
hello?
Click to expand...
Click to collapse
Yes that is the problem Read Autoprime's thread on the H83020c update. He explains a way to root device by downgrading to H83020a using LGUP.
Sent from my LG-H830 using Tapatalk
I don't seem to get passed the adb logcat step because I do so and it says that all process was done correctly but my phone won't at all boot up after he T-Mobile logo
Tried and did everything step by step and this is always the problem and can't get passed it
Someone please help
Sent from my iPhone using Tapatalk
Just use the Automagically thread a few below this one. You have to be on 20A for it to work. I used that method and it worked on the first try. Now I'm on 20C and I'm rooted as well. This way is way too complicated.
djerick3 said:
Just use the Automagically thread a few below this one. You have to be on 20A for it to work. I used that method and it worked on the first try. Now I'm on 20C and I'm rooted as well. This way is way too complicated.
Click to expand...
Click to collapse
The easy recovery method that runs the script? I have tried it countless times and also doesn't seem to work
wadamean said:
The easy recovery method that runs the script? I have tried it countless times and also doesn't seem to work
Click to expand...
Click to collapse
First you need to run the script and follow the instructions to the letter. If you read into the thread you'll see that you need to turn off verification before you run it. I forget what option it is but ill check and post it for you. Worked smooth for me first try.
Stuck
I seem to be stuck at adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
It's been a while. It hasn't moved from there and it won't let me input anything else. I got stuck after beginning of main and beginning of system.
Will this work starting from MM or only once on Nougat? My phone hasn't downloaded the update yet and it won't let me force it. Trying it on MM doesn't seem to complete.
Sent from my LG-H830 using XDA-Developers Legacy app
---------- Post added at 04:17 AM ---------- Previous post was at 03:48 AM ----------
Rican39 said:
Deleted
Sent from my LG-H830 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my LG-H830 using XDA-Developers Legacy app
Well this is interesting. The script the people above are talking about never worked for me. So I came here and got my hands dirty and did it the manual way. Everything worked great until I formatted data and reflashed verity and su zips. After booting, all I can get the phone to do is boot to twrp. I've successfully flashed the 20A kdz back to stock with unlocked bootloader. Just wondering what I did wrong?
Once I get into TWRP the steps used were:
1 - Flash SuperSU
2- Flash verity zip
3- Format Data
4- Flash SuperSU again (for good measure)
5- Flash verity zip again (for good measure)
All these instructions make sense but at the top of the OP it says to NOT swipe to allow system modifications. I thought after formatting data and flashing the verity zip that we can swipe to allow. If we can't modify the system partition, how do we access it for busybox, etc..
Sorry for the odd questions - just looking for clarity!
UPDATE: Sorry, I resolved my own problem. Just don't ever swipe to modify system in TWRP and you're good. Not sure why this was the case.
eliolicious said:
I seem to be stuck at adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
It's been a while. It hasn't moved from there and it won't let me input anything else. I got stuck after beginning of main and beginning of system.
Click to expand...
Click to collapse
I have this same problem. Did you figure out the issue?
codahq said:
I have this same problem. Did you figure out the issue?
Click to expand...
Click to collapse
I figured out the issue. There are a bunch of threads floating around here that seem to think that the dirtycow exploit will work on 20A and 20C. That is definitely not the case. 20C it is patched so you have to KDZ back to 20A and then exploit. Then you can TWRP flash 20C if you want to go back to 20C.
I'm was on 20C though and dirtycow definitely doesn't work.
Noob question
I got this phone lg g 5 tmobile variant yesterday. I was on marshmallow rooted with Xposed Framework Flashed 7.0 thinking it was a rom. I lost root and lost custom recovery I'm trying to root on 7.0 via dirty cow but instructions r too complicated. Can anybody tell me what dirty cow files to download and were to put the folder pls