[Q] [LG V510] Can't Root/Install Custom Recovery - G Pad 8.3 Q&A, Help & Troubleshooting

I'm able to use adb to connect to the device and reboot into bootloader but every time I try to install a TWRP recovery.img i constantly get the message
C:\Users\David>fastboot boot recovery.img
cannot load 'recovery.img': No error
C:\Users\David>
I can't figure out what it is that I'm doing wrong. Is there a simple issue holding me up? I only bought the gpe for the sole reason of making this a seemless task. At this rate i might as well return this and get a v500.

jerzykid said:
I'm able to use adb to connect to the device and reboot into bootloader but every time I try to install a TWRP recovery.img i constantly get the message
C:\Users\David>fastboot boot recovery.img
cannot load 'recovery.img': No error
C:\Users\David>
I can't figure out what it is that I'm doing wrong. Is there a simple issue holding me up? I only bought the gpe for the sole reason of making this a seemless task. At this rate i might as well return this and get a v500.
Click to expand...
Click to collapse
Which recovery are you trying to install? And, are you in the install directory? Have you unlocked the boot loader first? sorry for all the questions, but you should be answered so we know more detail.

sleekmason said:
Which recovery are you trying to install? And, are you in the install directory? Have you unlocked the boot loader first? sorry for all the questions, but you should be answered so we know more detail.
Click to expand...
Click to collapse
The questions are welcomed.
1)I'm installing in platform-tools folder where adb.exe is located as many posters have suggested. It's located in a folder directly in the C:/ Drive
2)The bootloader was unlocked before i purchased the g pad
3)I'm trying to install TWRP. I tried 3 different versions (including the latest) with the same result.
I've tried the Path under Enviromental Variables that some users suggest. Through some research some have said to put the recovery image directly under the C drive and use cd to change the path until it registers on command prompt. then go through the shell commands. I haven't tried this yet.

jerzykid said:
The questions are welcomed.
1)I'm installing in platform-tools folder where adb.exe is located as many posters have suggested. It's located in a folder directly in the C:/ Drive
2)The bootloader was unlocked before i purchased the g pad
3)I'm trying to install TWRP. I tried 3 different versions (including the latest) with the same result.
I've tried the Path under Enviromental Variables that some users suggest. Through some research some have said to put the recovery image directly under the C drive and use cd to change the path until it registers on command prompt. then go through the shell commands. I haven't tried this yet.
Click to expand...
Click to collapse
I don't know much about windows... Your path is c/users/David . in Linux, the prompt would be opened in platform-tools. It sounds like you you should either have the recovery image in David, or your prompt opened in platform tools. In any case, it sounds as though you are trying to install it from the wrong location. unfortunately, being windows, somebody else may better be suited to help you.

SOLVED
sleekmason said:
I don't know much about windows... Your path is c/users/David . in Linux, the prompt would be opened in platform-tools. It sounds like you you should either have the recovery image in David, or your prompt opened in platform tools. In any case, it sounds as though you are trying to install it from the wrong location. unfortunately, being windows, somebody else may better be suited to help you.
Click to expand...
Click to collapse
so changing the path to the folder containing adb.exe was correct but I had to put the recovery.img directly like many have said. In Windows the command prompt doesn't always default to C:\(or whatever your main drive is called) and you have to manually change this.Most people are fairly fluent with command promt but for those who aren't you must use " cd.. " (without quotes)to change the path to your base directory. i hope this helps anyone else.I've seen others explain it but not detailed enough

Related

cannot for the love of all thats holy get adb to work

ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
dbc00per said:
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
Click to expand...
Click to collapse
This would be better suited for Q&A that being said post the commands you are issuing and the errors you are getting. This would help someone trying to help you. Good luck
Try posting in clear concise sentences and it will help as well. Your post is like reading a teenagers tantrum and it's hard to follow.
From what I gathered, you can't get ADB to work, even though you're attempting to run it from a command prompt but the command prompt immediately closes from some unknown commands. That makes no sense.
From your computer, in windows, browse to the Android SDK folder.
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
With your phone connected via USB and debugging mode enabled type:
adb remount
and press enter.
What do you get?
First off...wrong section, this belongs in Q&A
Anyways...
1) Go to Settings -> Applications -> Development -> Enable USB debugging
2) Make sure HTC Sync is installed. Link
3) Right-click My Computer and go into Device Manager (while your phone is plugged in), if you see any yellow flags or unknown devices, remove them.
Now unplug your phone and plug it back in.
4) Place the sdk folder on your C:\ and run command prompt in Administrator mode.
Type "cd " (don't forget the trailing space), do not hit enter yet.
Now try to physically drag the tools folder into the prompt window, it will type text for you.
Hit enter.
5) Type adb and it should work.
If it doesn't work, well, you're going to need to give us more details...especially since if you follow what I wrote above correctly there is no reason it shouldn't work.
Sirchuk said:
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
Click to expand...
Click to collapse
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Neotelos_com said:
Does that work in XP?
Click to expand...
Click to collapse
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Neotelos_com said:
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Click to expand...
Click to collapse
Only works in vista and win 7
gx1400 said:
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Click to expand...
Click to collapse
Yeah like I said "workstation", I don't call any of my personal machines "workstations".
Also, I'd hope I know command line well considering I just gave advice on how to run adb through it.
thank you I've just gathered more information here than searching for days
Anywhere else.

[GUIDE] Flash CWM Manually (for noobs)

It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
*--*--* I am not responsible for any damage that may occur to your phone by following this guide or any other guide. If you are at this step, your warranty is already void, and if you lie to Verizon to get a replacement, an angry bear will break into your house and molest you quite thoroughly. Those people are the reason why Verizon is forcing locked bootloaders, and why I had to wait two months to root my Inc2. Don't be one of those people. You might be a noob, but that doesn't excuse you from doing research. In short, anything that happens is your own damn fault, and you can't blame anyone else. /rant *--*--*
Now that that is out of the way, the steps:
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe and adbwinapi.dll, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Boot into fastboot by powering the device off, then powering back on while holding the volume down button on the side. It should boot to a white screen, similar to what you saw when you first rooted it. Plug your phone into usb if you haven't already.
6. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot".
7. Rooting the phone is only the beginning. You still need a rooted kernal, and su and busybox. Without these, rooting does you little practical good. To that end, follow RMK's guide here: http://forum.xda-developers.com/showthread.php?t=1160745. That will get you all set up to start enjoying root fully. I would recommend installing ROM Manager from the market and using it to flash the latest CWM (4.0.0.8). ****NOTE that you need to already have CWM to flash the su and then flasht he new CWM. I know, it seems silly, but that's the way things are. Also, a disclaimer: a few people have had problems with the newest CWM not working properly for them. It worked for me, though, and there is a fix on page four of this thread.
Credit goes to attn1 for the modified CWM, xgunther for posting it/original instructions, and crazythunder of Android Community for the original instructions for using fastboot with a G1. Hope this helps
Some information from supersonic that those trying this on linux will find useful. Thanks!
supersonic2.5 said:
Download this recovery: http://forum.xda-developers.com/showthread.php?t=1134520
BTW, if you havn't installed fastboot, download it here.
http://developer.htc.com/adp.html
1.First rename your android sdk folder to "sdk" just like that. Dont use quotation marks on anything fyi.
2.Next step is to move the sdk folder to your home folder.
3.Move adb, fastboot, and the recovery image from the link above into the tools folder of the sdk.
4.Open up terminal and type or copy this in there.
"cd sdk/tools" hit enter.
5. "./adb kill-server" hit enter.
6. "./adb start-server" hit enter. should look something this. (below)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7. "./fastboot" hit enter.
8. "./fastboot flash recovery cwm-recovery-vivow.img" hit enter
give it some time to flash.
9. "./fastboot reboot" hit enter
10."./fastboot adb reboot recovery" hit enter
And there you go, wait for your phone to reboot and what not and you should have CWM installed. I would immediately do a nandroid of the stock rom. after that i didnt bother messing with superuser on stock froyo because who the hell wants to be on froyo!? lol, so i installed the GB ota rooted version with superuser already because its very stable....found here http://forum.xda-developers.com/showthread.php?t=1161411 as i wait for a stable version of rewind,you can then install and update CWM through rom manager to the current version once you've done this.
there you go buddy sorry so long. if you encounter any problems let me know so i can boot into ubuntu and help out. i'd give you a little more details but im on my mac right now. hit the thanks button if i was any help
Click to expand...
Click to collapse
devator22 said:
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe, adbwinapi.dll, and ddms.bat, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot". And you should be done.
Credit goes to attn1 for the modified CWM, and xgunther for posting it/original instructions. Hope this helps
Click to expand...
Click to collapse
Just a heads up, if you are S-Off, you can enjoy these instructions on Mac, Linux, or Windows. ADB and fastboot give you options for all! <3
Here is another link i found to help out!
http://forum.xda-developers.com/showthread.php?t=1122694
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
b0gman said:
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
Click to expand...
Click to collapse
Dumbest solution ever... I was having the same problem. As long as you've installed the jdk file from the link it shows on the initial error on sdk install...
Just click 'back' then 'next' again on the SDK installer... It worked for me.
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Grouper said:
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
Click to expand...
Click to collapse
Guess I forgot to mention that this is for the people with problems with the automatic installer, including myself.
Sent from my Incredible 2 with Xda app
Clutch McWinner said:
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Click to expand...
Click to collapse
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
devator22 said:
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
I was, but it turns out I didn't have the HTC sync drivers. S-Off, Rooted, and running overclocked CM7 now!!!!!!!
This must be in Fastboot USB mode while doing?
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
SHAKEJONES said:
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
Click to expand...
Click to collapse
Should HTC Sync be opening? I think you're supposed to uninstall HTC Sync, but leave the drivers. AlphaRevX provided a link to the drivers only, so it might be easier to just completely uninstall everything and then reinstall the provided driver instead.
Just tried that and its still stuck... I'll mess with it more tomorrow
Yeah i've been having the exact same problems with the drivers. I have a completely fresh install of windows 7, and it still wont work. I installed the HTC Sync, and it still doesnt recognize my device. I tried using Ubuntu, however it makes absolutly zero sense in my mind, so unless i have a detailed instuctional text, windows is my only choice really. Its funny, this thread is for noobs, yet i can't get even do this, but other phones i've rooted without any problems, and they we're much harder for me. Blah.
I've tried all variations of connection modes, triple checked I had all the files in the right spot, and tried different usb ports and it still wont work... does someone have a more detailed guide for this?
Seriously frustrated about this. S-Off was no problem. I'm triple booted with OSX, Win XP Pro and Linux. Used linux to get s-off but didn't get a CWM install. Window won't allow the driver to install and Linux is a mystery. Anybody have luck with OSX or Linux and want to write it up?
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
devator22 said:
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
Click to expand...
Click to collapse
Thank you kind sir hahaha I JUST got done doing that and it worked like a charm! this thread will be a great help to anyone else ---> http://forum.xda-developers.com/showthread.php?t=1122694
The directions for fastboot are in the OP
Haha, yea. I guess I am a noob when it comes to writing guides. I updated the OP with an extra step for booting into fastboot.

Where Can I learn ADB?

This is annoying as heck.
I have had the Droid 1, Droid X, and Charge and have always been able to root the phones and install roms and follow directions with now problem.
I have installed SDK, I have downloaded the adb platform tools. However, I have no idea how to get adb where it needs to be from there.
Does anyone know where I can find an in-depth guide?
try here:
http://developer.android.com/guide/developing/tools/adb.html
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Yeah, I have seen that.
I guess the wall I am hitting is how you actually start adb. I know where the folder is. I might be overlooking something though.
Didn't see your post Mart, ill try that now.
martonikaj said:
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Pacifik said:
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Click to expand...
Click to collapse
Even easier is adding the folder to the system path variable.
That allows you to always run adb, no matter what folder you happen to be at.
Ok, I have effectively managed to get to adb and it is installed.
to root the nexus, do I now start at the 1st step in the "lets begin section" listed here:
http://rootzwiki.com/topic/12013-welcome-to-root-editionstep-by-step-oem-unlock-and-root/
http://wiki.cyanogenmod.com/wiki/ADB
Ohai droidstyle good to see you here
Has anyone seen John Connor?
skynet11 said:
Ohai droidstyle good to see you here
Has anyone seen John Connor?
Click to expand...
Click to collapse
Ya you too skynet! I have no gnex yet, but soon...very soon!!
I am now Bootlooped, the bootloader is unlocked, I flashed the recovery image without a problem, but now i am stuck at the constant flashing of the google logo
Did you flash a new ROM?
this is what I was flashing
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
I was just trying to get root and CWM
I have CWM, but all it does bootloop and I can't get it to detect a sd card.

How to get Verizon pixel xl back to stock so I can install TWRP.

Noob again. So I am rooted and I'm currently on build NDE63X on my Verizon 128 gb XL. If i understood the instructions correctly, I have to go back to stock before I can put TWRP on the phone. I know I get the factory images here.
https://developers.google.com/android/images
Do I get the NDE63P image for the phone since that was what was on the phone before I sideloaded the OTA for my current version which is NDE63X or do I just need to download the full image for NDE63X?
Can someone also list the steps needed to accomplish getting phone back to stock? I read Google's instructions and I was a little confused. I understand that I will lose root but should be able to root after installing TWRP since it looks like Chainfire updated the root method for those using TWRP.
Thanks.
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it. ?
Sent from my Pixel XL
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thank you. Gonna attempt it this weekend.
Deleted
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Veid71 said:
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Click to expand...
Click to collapse
https://developers.google.com/android/images
Sent from my Pixel XL
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
chipslate said:
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
Click to expand...
Click to collapse
if you are executing the commands, you are in fastboot, not adb.
try fastboot devices
if it doesnt return anything, your computer is not seeing the device.
you will need the computer to see the device in fastboot before you can proceed.
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
first thing to try is to go into fastboot, then unplug the cable, and then plug it back in.
if it is still not recognized, then its either an outdated adb/fastboot issue, or a driver issue (if you are using windows, if not there may be other possibilities).
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
When it finds your phone does it say unauthorized or authorized?
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
chipslate said:
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
Click to expand...
Click to collapse
What happens now when you attempt the next command?
Edit: So after running adb devices, you should be running adb reboot bootloader command next I believe.
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Also, I have the phone in MTP File Transfer mode and USB Debugging enabled.
chipslate said:
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Click to expand...
Click to collapse
You should now use the flash-all command but this is going wipe all of your data.
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
chipslate said:
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
Click to expand...
Click to collapse
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
magestic1995 said:
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
Click to expand...
Click to collapse
It finally worked!!! Thanks again for your help and going back and forth. I finally installed Android Studio and it inserted the ADB drivers at the top of Device manager. Worked like a charm then. Finally, Android 7.1.1 and unlocked bootloader... Bring it on, world!
Congrats! I've only used Android Studio for all this stuff since Im a developer. Congrats on getting it all figured out!
i have been trying to take my pixel xl back to stock but the flash-all.bat script hangs on the part where it should flash the system img zip. it says the file size is to large

Question How to install factory image using Linux

Hey guys,
I was trying to update while keeping root and made a mistake. i don't think my phone is hard bricked, as it does boot, it just never actually reaches the stock
When device boots, it says "device is corrupt, it can't be trusted and may not work properly". This happened after I tried to utilize the Master-Root.img file. Not sure exactly how this happened, I will investigate later, but right now trying to get something on my phone (right now it just doesn't boot past the error message I just mentioned)
I looked online, and I've heard methods about using a flash-all.bat and flash-all.sh file within the factory image. However, I'm using linux, not windows, these files so not seem to work.
for the record:
bootloader is unlocked
phone was rooted prior to this happening
i don't deny i made some kind of mistake that resulted in this happening, i just don't know what yet. i will investigate, but right now just trying to recover my phone. there does not appear to be an OS on it, or it is corruped
i will post any images that are needed, im just under a time constraint
i have the factory image on my computer already. what do i need to do to get this installed? i looked up tons of guide, but it only seems to be applicable for windows.
thanks so much in return btw!
You can use Android Flash Tool. Flash-all.sh should work on LInux as well. But Android Flash Tool is probably the easiest way.
Lughnasadh said:
You can use Android Flash Tool. Flash-all.sh should work on LInux as well. But Android Flash Tool is probably the easiest way.
Click to expand...
Click to collapse
is Android Flash Tool a windows only program? or does this work on Linux too? because linux is all i have at the moment.
pojr said:
is Android Flash Tool a windows only program? or does this work on Linux too? because linux is all i have at the moment.
Click to expand...
Click to collapse
Yes, supports Linux.
Android Flash Tool | Android Open Source Project
source.android.com
Lughnasadh said:
Yes, supports Linux.
Android Flash Tool | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks so much. I will try this out. For the record, I actually did go into flash-all.bat and I noticed the individual terminal commands it wanted me to put in. So I tried putting them in manually, but after I finished the commands and rebooted the phone, I still received the same message "device is corrupted, it can't be trusted".
I will still try the tool that you linked though, but I'm nervous it won't help because I tried running the commands individually that were within the flash-all file.
Later on I will go into more detail on what I mean, but I'm at work right now and I don't have a lot of time to type.
pojr said:
I looked online, and I've heard methods about using a flash-all.bat and flash-all.sh file within the factory image. However, I'm using linux, not windows, these files so not seem to work.
Click to expand...
Click to collapse
I'm on linux (fedora) and the flash-all.sh script will work, but you have to ensure adb and fastboot drivers are installed system-wide or you run your terminal from platform-tools. If you want to be able to run the script from any directory, you'll have to edit your bash config to point to the directory of your platform-tools. You may also need to edit your udev rules.
Bash
sudo nano .bashrc
export PATH=${PATH}:/home/YOUR-USERNAME/path/to/adb
udev Rules
See github page for instructions, assuming your distro requires it.
Linux Fix Fastboot "no permissions, verify udev rules"
Linux Fix Fastboot "no permissions, verify udev rules" - fbootfix.md
gist.github.com
Edit: If you're on any distro with an up-to-date version of android-tools, you can install the package and it will automatically install the adb/fastboot drivers system-wide and you can skip the above manual process. Otherwise, if android-tools is too old, fastboot won't work and the shell script will end abruptly as it's out-of-date compared to the most recent A12 or A13 builds.
pojr said:
Thanks so much. I will try this out. For the record, I actually did go into flash-all.bat and I noticed the individual terminal commands it wanted me to put in. So I tried putting them in manually, but after I finished the commands and rebooted the phone, I still received the same message "device is corrupted, it can't be trusted".
I will still try the tool that you linked though, but I'm nervous it won't help because I tried running the commands individually that were within the flash-all file.
Later on I will go into more detail on what I mean, but I'm at work right now and I don't have a lot of time to type.
Click to expand...
Click to collapse
One method to get rid of the corrupt message that has worked for people is to flash the boot image from the prior month in fastboot (it will likely not boot) and then flash your current boot image.
Lughnasadh said:
One method to get rid of the corrupt message that has worked for people is to flash the boot image from the prior month in fastboot (it will likely not boot) and then flash your current boot image.
Click to expand...
Click to collapse
I will try that as a last resort (if all else fails)
To go into more detail, when I opened up terminal, I migrated to the folder that has the flash-all files (both the .bat and .sh) by typing "cd [folder name]", however I didn't know how to run those scripts in terminal, even after googling. So I opened the .bat file in text editor and notice the script had 3 or 4 fastboot commands.
Since I couldn't get flash-all file to run on its own, I tried manually typing in fastboot commands right into the terminal. The first fastboot commands seems to run without any problems, but then the final fastboot command seems to have issues. While it ran, they were a bunch of files it could not find. But still, it didn't give a error or anything. So once the three or four fast food commands were ran, then I rebooted the device, and still received the "device is corrupted, device cannot be trusted" error.
Still haven't downloaded that program you linked to yet, I apologize. I have to wait until lunch to try this because I'm at work. Don't you hate it when you're running to issues right before work? Haha.
pojr said:
To go into more detail, when I opened up terminal, I migrated to the folder that has the flash-all files (both the .bat and .sh) by typing "cd [folder name]", however I didn't know how to run those scripts in terminal, even after googling. So I opened the .bat file in text editor and notice the script had 3 or 4 fastboot commands.
Click to expand...
Click to collapse
Use the batch file (.bat) on windows and use the shell script (.sh) on linux. They both execute the same commands based on the OS.
To run the shell script from terminal, type:
sh flash-all.sh
lottarake said:
Use the batch file (.bat) on windows and use the shell script (.sh) on linux. They both execute the same commands based on the OS.
To run the shell script from terminal, type:
sh flash-all.sh
Click to expand...
Click to collapse
thank you. i just tried this. says "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
not a problem. you did mention i need to install the latest platform tools. so i did, and tried again. same error message, fastboot too old. now i'm on the latest platform-tools, so not sure why i'm receiving that message.
currently installing android flash tool right now. having difficulties because (for some reason) chrome is required. i'm on firefox. but i will update once it's all installed. thanks again for the support btw.
Update: On the android flash tool right now. So far I like what is happening. Didn't realize how easy this is. I am a little concerned though, because while the site appears to be working as intended, my phone is still on the fastboot screen with nothing on it, but that might be normal. I'll keep waiting and see what happens.
pojr said:
thank you. i just tried this. says "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
not a problem. you did mention i need to install the latest platform tools. so i did, and tried again. same error message, fastboot too old. now i'm on the latest platform-tools, so not sure why i'm receiving that message.
currently installing android flash tool right now. having difficulties because (for some reason) chrome is required. i'm on firefox. but i will update once it's all installed. thanks again for the support btw.
Click to expand...
Click to collapse
If the latest adb/fastboot drivers aren't system-wide and you're running the commands from any other directory other than from the platform-tools folder, you'll get the out-of-date error. If you want to run it from the directory, make sure to add "./" (without quotes) before adb/fastboot.
Example:
./adb devices
If you edit your bash config to point to the new platform-tools folder, it'll execute adb/fastboot from the latest you've downloaded as system level versus what was installed on your OS previously.
lottarake said:
If the latest adb/fastboot drivers aren't system-wide and you're running the commands from any other directory other than from the platform-tools folder, you'll get the out-of-date error. If you want to run it from the directory, make sure to add "./" (without quotes) before adb/fastboot.
Example:
./adb devices
If you edit your bash config to point to the new platform-tools folder, it'll execute adb/fastboot from the latest you've downloaded as system level versus what was installed on your OS previously.
Click to expand...
Click to collapse
Thank you. I will look into that.
So at the moment, I'm running the Android flash tool. Seems to be pretty straightforward, but the download keeps starting over. Is that supposed to happen? Or is there something wrong? My apologies if I'm sounding like an idiot right now
pojr said:
Thank you. I will look into that.
So at the moment, I'm running the Android flash tool. Seems to be pretty straightforward, but the download keeps starting over. Is that supposed to happen? Or is there something wrong? My apologies if I'm sounding like an idiot right now
Click to expand...
Click to collapse
Not quite sure the reason it's restarting tbh. It should only download the zip once and then proceed to flash as long as it's properly connected to the phone. When using the Android Flash Tool, I stick to Chrome since it seems to work properly for me. I haven't tested it with Firefox yet. You could always reset the adb access to Firefox by disconnecting the phone and closing the browser, then from terminal run "adb kill-server" before reconnecting and granting adb to Android Flash Tool again.
lottarake said:
Not quite sure the reason it's restarting tbh. It should only download the zip once and then proceed to flash as long as it's properly connected to the phone. When using the Android Flash Tool, I stick to Chrome since it seems to work properly for me. I haven't tested it with Firefox yet. You could always reset the adb access to Firefox by disconnecting the phone and closing the browser, then from terminal run "adb kill-server" before reconnecting and granting adb to Android Flash Tool again.
Click to expand...
Click to collapse
I'm on Chrome now. I think it might just be poor USB connection. I moved it to a safer position, so hopefully that will fix the problem. Seems like it's installing now. I'm having some really bad luck today lol.
Good news. I checked my phone just now, it is now booted without any issues. Thank god. Long story short, I ran into some issues trying to perform an OTA update while keeping root access, but ran into issues while following the directions. So I started troubleshooting the problem and went a little too far with it. Thanks so much @lottarake and @Lughnasadh for helping me out.
Not sure if the OS will remain on there if I reboot the device. I assume so, because the OS was installed, not just flashed.

Categories

Resources