Did I brick my Pixel 3 trying to bring it back to stock?

Did I brick my Pixel 3 trying to bring it back to stock? - Google Pixel 3 Questions & Answers

Hello guys,
I needed to send in my Pixel 3 for repair and wanted to bring it back to stock. So I thought that I flash a factory Image and lock the bootloader afterwards.
But It did bug and give me errors like boot.img not in archive etc. even though I completly upacked the zip inside that path.
Anyways, now my adb doesnt find any devices and I cant boot. On the Fastboot screen it says the following:
boot slot: b
Enter reason: error booting boot.img
thanks in advance!

Try to factory reset your phone from recovery.

levibuko said:
Hello guys,
I needed to send in my Pixel 3 for repair and wanted to bring it back to stock. So I thought that I flash a factory Image and lock the bootloader afterwards.
But It did bug and give me errors like boot.img not in archive etc. even though I completly upacked the zip inside that path.
Anyways, now my adb doesnt find any devices and I cant boot. On the Fastboot screen it says the following:
boot slot: b
Enter reason: error booting boot.img
thanks in advance!
Click to expand...
Click to collapse
Do you have the latest sdk platform tools (fastboot)? Run the flash-all batch file you find in the extracted factory image. When you boot into the bootloader run fastboot devices from your pc. Is your device reconized?

Did you download the right image for the current build your on??

anasmhds said:
Try to factory reset your phone from recovery.
Click to expand...
Click to collapse
If I try to acces recovery it just reboots back to fastboot or I get the android logo with no command error
jd1639 said:
Do you have the latest sdk platform tools (fastboot)? Run the flash-all batch file you find in the extracted factory image. When you boot into the bootloader run fastboot devices from your pc. Is your device reconized?
Click to expand...
Click to collapse
I updated from the google webpage . Yes, fastboot devices gives me a a device ID. But with adb it says waiting for devices.
thatsupnow said:
Did you download the right image for the current build your on??
Click to expand...
Click to collapse
I did download android 10, before I was on android 9. Was that my mistake?

levibuko said:
If I try to acces recovery it just reboots back to fastboot
. Yes, fastboot devices gives me a a device ID. But with adb it says waiting for devices.
Click to expand...
Click to collapse
ADB only works when booted in to recovery or system. You need fastboot when booted in to the bootloader. That's why you don't get anything from adb.

Are you sure anything happened when you tried to relock? Since you can get fastboot to recognize the device, try a flash-all.

sliding_billy said:
Are you sure anything happened when you tried to relock? Since you can get fastboot to recognize the device, try a flash-all.
Click to expand...
Click to collapse
I didnt relock yet. If i try the flash all script now it does some more than before but it restarts and shows me the no command (android logo) error. and then the script finishes and says waiting for other devices.

levibuko said:
I didnt relock yet. If i try the flash all script now it does some more than before but it restarts and shows me the no command (android logo) error. and then the script finishes and says waiting for other devices.
Click to expand...
Click to collapse
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.

jd1639 said:
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.
Click to expand...
Click to collapse
Allright, I will try it as soon as I am back home tomorrow.

jd1639 said:
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.
Click to expand...
Click to collapse
levibuko said:
Allright, I will try it as soon as I am back home tomorrow.
Click to expand...
Click to collapse
What JD said. You aren't bricked most likely. Lots of things can be done from stock recovery. Once you are at the recovery command page, you will likely have ADB recognition as well.

sliding_billy said:
What JD said. You aren't bricked most likely. Lots of things can be done from stock recovery. Once you are at the recovery command page, you will likely have ADB recognition as well.
Click to expand...
Click to collapse
I am glad to hear that. So could you recap what I gotta do now?
As far as I understand I need the stock image (any particular one?) and just need to run the flash-all script while in fastboot mode ?
What if it reboots and I am at the no command screen? Do I need to do sth with the phone or wait?

So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.

levibuko said:
So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.
Click to expand...
Click to collapse
There are archives (images) that the device doesn't use and aren't contained in the factory image so that's normal, fastboot tries to run them anyway. But only running a few seconds is not normal. Do you remember, or can try to run the script again, what images it does try to run and what the last thing that it did flash? And it doesn't show any errors? If you see that it doesn't contain certain sig files, that's also normal.
Edit, one other thing. Try downloading the factory image again. Only extract the factory image zip file, don't extract the other zip file you find in it. Then run the flash-all script from within the extracted factory image.

levibuko said:
So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.
Click to expand...
Click to collapse
First, the "errors you are seeing about "not containing" are not errors but part of the script. Are you getting to fastbootd after what seemed like a reboot into recovery? Are you doing something there? You shouldn't as it is part of the script that started that way with Android 10. If you watch command prompt, you will see that it is still running and will eventually finish and reboot properly into system. For the Pixel 3 (not 3XL since you are in the P3 forum), you should be using 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...y-bc480ac4.zip. Be sure to check the SHA-256 of the file before you flash. As for flashing, extract the DL either right into your ADB/Fastboot folder or wherever if you have your PATH set properly. Current platform tools are 29.05 available for Windows at https://dl.google.com/android/reposi...st-windows.zip. Then, just run flash-all from command prompt. The next thing you should see after a fairly lengthy reboot through the G screen is your device ready to be setup with Google.
If you can take some pictures with a camera or something and post, that would help with anything you might be seeing. The other thing you could do since you can get into recovery is to run the actual OTA install. Follow the directions here and use 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...8-7a817e0d.zip. Same thing about checking the SHA-256.
This last line in your post "the scipt also only runs for a few secs" leads me to believe you are not letting it run through the fastbootd half.

sliding_billy said:
First, the "errors you are seeing about "not containing" are not errors but part of the script. Are you getting to fastbootd after what seemed like a reboot into recovery? Are you doing something there? You shouldn't as it is part of the script that started that way with Android 10. If you watch command prompt, you will see that it is still running and will eventually finish and reboot properly into system. For the Pixel 3 (not 3XL since you are in the P3 forum), you should be using 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...y-bc480ac4.zip. Be sure to check the SHA-256 of the file before you flash. As for flashing, extract the DL either right into your ADB/Fastboot folder or wherever if you have your PATH set properly. Current platform tools are 29.05 available for Windows at https://dl.google.com/android/reposi...st-windows.zip. Then, just run flash-all from command prompt. The next thing you should see after a fairly lengthy reboot through the G screen is your device ready to be setup with Google.
If you can take some pictures with a camera or something and post, that would help with anything you might be seeing. The other thing you could do since you can get into recovery is to run the actual OTA install. Follow the directions here and use 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...8-7a817e0d.zip. Same thing about checking the SHA-256.
This last line in your post "the scipt also only runs for a few secs" leads me to believe you are not letting it run through the fastbootd half.
Click to expand...
Click to collapse
Hello,
first of all thank you for the detailed answer!
I did as you told me and got so far:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another question: I just click on the flash-all script and let it run. do i have to open he power shell in w10 and do it within there?
EDIT: I think I dont know how to properly add images. Phone stays at the fastbootd screen and I get the error fastboot error: command failed.

levibuko said:
Hello,
first of all thank you for the detailed answer!
I did as you told me and got so far:
Another question: I just click on the flash-all script and let it run. do i have to open he power shell in w10 and do it within there?
EDIT: I think I dont know how to properly add images. Phone stays at the fastbootd screen and I get the error fastboot error: command failed.
Click to expand...
Click to collapse
Yes, you need to run it from command prompt or PowerShell. There are some differences between the two, but if you just type cmd in PowerShell, it will put it in command prompt mode. Make sure to hold down shift and right click and open power shell widow from here so that the open directory is in the command line when you run flash-all. Withe a batch file in windows in the actual directory, you can just type run-all with no .bat or .\ or anything. Your pics are not showing, but something like what I am showing. BTW, sideloading the OTA needs done from command prompt as well. Like I said, easy way is just to extract the image into the same directory where you have Platform Tools extracted so you don't need to worry about the path.

levibuko said:
Another question: I just click on the flash-all script and let it run.
Click to expand...
Click to collapse
You should be able to just double click the flash all batch file. You don't need to run it in a power shell. It'll open one up to run the fastboot commands.

sliding_billy said:
Yes, you need to run it from command prompt or PowerShell. There are some differences between the two, but if you just type cmd in PowerShell, it will put it in command prompt mode. Make sure to hold down shift and right click and open power shell widow from here so that the open directory is in the command line when you run flash-all. Withe a batch file in windows in the actual directory, you can just type run-all with no .bat or .\ or anything. Your pics are not showing, but something like what I am showing. BTW, sideloading the OTA needs done from command prompt as well. Like I said, easy way is just to extract the image into the same directory where you have Platform Tools extracted so you don't need to worry about the path.
Click to expand...
Click to collapse
I tried everything exactly the way you told me but its the same result. So I tried sideloading the OTA it switches to the no command error na d I get this:
adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: No error
Edit: If I try to boot to recovery via combo keys I get the no command with the android logo too. Is my recovery dmged?
If I try to flash teh image I get to fastbooted and from there I can get into recovery mode. I tried OTA again and now I got this error:
>adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: Invalid argument
and the error when I flash the image:
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/4 (524284 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...

levibuko said:
I tried everything exactly the way you told me but its the same result. So I tried sideloading the OTA it switches to the no command error na d I get this:
adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: No error
Edit: If I try to boot to recovery via combo keys I get the no command with the android logo too. Is my recovery dmged?
If I try to flash teh image I get to fastbooted and from there I can get into recovery mode. I tried OTA again and now I got this error:
>adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: Invalid argument
Click to expand...
Click to collapse
The no command is not recovery yet. You need to do the step listed in the OTA instructions --To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear. You can't start the sideload from anywhere besides that menu that you seem to not be at yet. I was just about to recommend the OTA sideload since that is a little more reliable. Fastbootd cannot be used for all things. Just start from scratch using the OTA instructions here: https://developers.google.com/android/ota Also, make sure you are getting a 'fastboot devices' devices recognition (for image flash) or an 'adb devices' recognition once in recovery for sideload. Also, be sure to try different cables and ports. Reboot computer, etc to make sure the daemon is completely reset. There is something missing in your steps. Image instructions are here, BTW: https://developers.google.com/android/images. If you can get fastboot devices to recognize the device, you aren't hard bricked. Soft bricked of course, but not hard.
That product error is one that nobody seems to have figured out a reason for. Get yourself to that error, stay connected and in command prompt (I thionk you do have to do a press any key to continue to get back to a prompt once the error happens, but I'm not sure). Just don't close anything. Then do the sideload from fastbootd. Yes, you are using half of the image install and half of the OTA install with different files.

Related

[Q] Recovery Mode inexistant

Okay, so I posted about a week ago re: my softkey issue and fortunately that was fixed by returning my phone to stock, however, I followed nexushacks method and when it told to do this:
Step 12. Once you get the Android guy with exclamation mark, hit Volume Up and Power button at the same time until you get blue menus.
Nothing bloody happens. Please don't tell me I have to hold it for something like 60 seconds because I. Will. Rage. Lol.
When I try to go into recovery I get that symbol and can't do anything but batt pull. I'm still unlocked and rooted, to my knowledge.
I downloaded ROM Manager because I wanted to flash a recovery on it but it told me that "An error occurred while attempting to run privileged commands"
It also says this when I open Rom Manager "You must root your phone for ROM Manager to function. Superuser was not found at "/xbin/su" or "/system/xbin/su". Use google blabla"
I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a responce from device" whatever that message is...
Trying to give as info as possible so someone can help a brother out.
I can't deal with this Stock OEM crap anymore *twitch*
Thanks!

Herp Derp
Okay, I didn't realize it was Press the Power button, then the volume up button.
Silly noobs.
So my question, is there a way to get Clockwork Recovery back on now or do I have to go through the whole "Rooting" process again?

I assume you see a lock symbol while booting. This means you're unlocked. Now you'll just need to use fastboot to flash a custom recovery (namely, CWM). NexusShacks details how to setup and use fastboot and i think they provide TWRP now, feel free to use this or just download CWM from here and flash that .img file instead.
After this, download the latest Superuser-3.0.7-efghi-signed.zip and flash that. Note that on a stock ROM it will flash stock recovery on every boot. To change this, rename /system/etc/install-recovery.sh to something else.

But how do I flash a .img file when I don't have Recovery mode?
Or can I use do that through the OEM Recovery (blue screen)?

You flash it with fastboot. Fastboot is a command line tool to flash various images through the bootloader screen. To enter the bootloader, turn off the device and hold Vol. Up + Power. This is the same place you would've typed "fastboot oem unlock", except to flash the new recovery you'll be typing something along the lines of "fastboot flash recovery recovery.img". NexusSHacks teaches you how to do all of this.

Ah sorry, I still get Fastboot and Bootloader mixed up.
Only problem is that I don't know if my computer is recognizing my device when I plug it in through Bootloader.
As mentioned in my original post
"I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a response from device" whatever that message is..."

I'm at work now and trying to figure out how to do this using Terminal on my mac.
When I type in "cd /nexussrootICS" it keeps on telling me "no such file or directory"
Do I need to put this file in a specific folder? I got this step working on my PC at home but it told me "Waiting for device" the whole time.
Any thoughts?

I'm not particularly familiar with OS X so forgive anything i say that might be off target.
You need to direct the terminal to the relative OR absolute directory of that folder. A relative directory can be done by "cd ./blah", while an absolute will be done by "cd /blah". This is quite confusing for people who aren't used to command line, but very simple once you've done it a few times.
Easiest way aside from magical OS X shortcuts i don't know about is:
-Unzip the files to a "nexus" folder on the desktop, making sure the adb files are in this nexus folder and not a sub folder
-open terminal
-"cd /user/artist/desktop/nexus" or whatever the FULL PATH to the folder is. You should be able to see this through the folders properties or in the file explorer.
-Now you are in the folder, you can use adb and fastboot by just typing those words
I believe OS X can recognise the device straight away so you shouldn't need to install any drivers - at least my linux distros were like that. Installing drivers on Windows is detailed in the video, too.

Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"

TheArtist8 said:
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
Click to expand...
Click to collapse
The command should be
./fastboot-mac flash recovery recovery-clockwork-5.0.2.0-crespo.img
You were missing the recovery flag in the command.
Sent from my Nexus S 4G using Tapatalk 2

Also do "man fastboot-mac" in terminal to show all its options.
Sent from my Nexus S 4G using Tapatalk 2

Son of a... alright ill try after my lunch.
Sent from my Nexus S using XDA

Omfg I love you guys.
Thanks so much
I just got into Recovery mode, now on to Cyber-GR

[TIP] How to install Clockworkmod Recovery (detailed instructions)

Moderator Edit 12/8/12
Do not use this this method twrp is officially supported for the one x. Download goo manager from the market or check the dev section.
It is not my intention to step on the toes of other people who have been more than helpful when it comes to questions relating to the installation of this or that.
Although I am reasonably familiar with many of the installation procedures when it comes to ROMs and Kernels, including Clockworkmod Recovery, etc., I am still a bit hesitant because I simply want to make sure that I am not making a mistake. After all, we spend lots of money on our phones, and the slightest error can be permanent.
I respect and admire all the developers who work tirelessly to make our lives a little bit better, and who often fulfill our ongoing need to “fiddle” with our phones. Thank you!
That being said, here is a detailed explanation of how to install Clockworkmod Recovery.
First, your bootloader must be unlocked. It doesn’t matter if you have the “TAMPERED” entry; this procedure will still work. Second, you must also have all necessary mobile phone drivers installed, including ADB, ADB drivers, and fastboot. From this point forward, I will call all these files your “Fastboot” files. If you don’t have these files, you can download them by clicking on the link at the end of this post.
At this point I’m assuming you’ve placed your Fastboot files in a separate folder within the root directory of your PC (the “C” drive?). I put these files in a folder called fastboot, but it really doesn’t matter, as long as you remember the location.
Here’s an image from my Windows Explorer screen to give you an idea of what I did:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, here we go …
Download the Clockworkmod Recovery image file and change the name to CWM.img. This is an easy name to remember, which will help further along in these instructions.
Place your newly-named CWM.img file in the directory where your Fastboot files are located.
Power down your device.
While holding VOLUME DOWN, press and hold the POWER button for a few seconds. Continue to hold VOLUME DOWN until your bootloader screen appears.
Somewhere in the middle of your bootloader screen will be seven entries entitled FASTBOOT, RECOVERY, FACTORY RESET, CLEAR STORAGE, SIMLOCK, IMAGE CRC, and POWER DOWN.
Using your VOLUME keys, make sure FASTBOOT is highlighted, and then press the POWER button once.
You should now be in the FASTBOOT Bootloader screen. On my ONE X, and I’m assuming the same for everyone, the word FASTBOOT will be highlighted with a RED background. Either way, it should be highlighted.
Connect device to your PC via USB cable.
If all is going well, the word FASTBOOT should now say FASTBOOT USB. From this point forward, do not touch the device.
Open a Command Prompt window on your PC (Press the Start button, and in the search field type cmd, and then press Enter). Here’s an example of how your Command Prompt window may look:
You must now change the directory to where your Fastboot files are located. As I mentioned above, mine are in the directory c:\fastboot. Therefore, I would need to type the following command in the Command Prompt window: cd c:\fastboot
The “cd” refers to “change directory,” while the rest is where your Fastboot files are located. Here’s how your Command Prompt window will look like after you’ve typed the above, and BEFORE you press the Enter key.
Here’s an example of how your Command Prompt window will appear AFTER you press the Enter key:
Next you need to type the following: fastboot flash recovery CWM.img
Renaming the file to CWM.img simplifies the above entry because this name is easy to remember.
Here’s how your Command Prompt window will appear BEFORE you press the Enter key:
Now press the Enter key and let the program run.
The entire installation/flash will take only a few seconds. When complete, your Command Prompt window will return to your fastboot directory (see image below).
Ignore the error in my image above, the line called error: cannot load ‘CWM.img’
This error message appeared ONLY because I didn’t want to install Clockworkmod Recovery on my device a second time. Hey, if it ain’t broke, don’t fix it, right?
Reboot your device.
DONE! You now have Clockworkmod Recovery on your phone.
These instructions are available in PDF format by clicking on the link at the end of this post.
Peter
Here's the link to the Clockworkmod Recovery file:
Clockworkmod Recovery Image
Detailed Instructions
Fastboot Files

Thanks for the excellent guide, Peter!
We were all hardcore newbies at one point and while it's annoying to see them ask redundant questions or ones that have been answered in the first post of a thread, you have to have some sympathy for them. Especially when they do something like get a soft-bricked device and begin to panic.

Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!

THANK YOU this was very helpfull

Mac or Linux, I simply don't know ...
zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Regretfully, I have little to no knowledge concerning Mac and Linux, so I don't know if it would work. Sorry.
Perhaps others can answer this question.
Peter

zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Almost identical. On my Ubuntu machine I just need to type "sudo fastboot flash recovery xxx.img" and boom!
I can't see Macs being too different.

PeterHTC said:
First, your bootloader must be unlocked.
Click to expand...
Click to collapse
has this been done? have I missed something in the past day?

So far this is only for Rogers version

Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>

fastboot flash recovery recovery.img
Sent from my HTC One XL using xda premium

No, you didn't miss anything ... so far
fionic said:
has this been done? have I missed something in the past day?
Click to expand...
Click to collapse
No, you didn't miss anything so far. The bootloader on AT&T units cannot yet be unlocked, but I'm sure it's only time. Once unlocked, then you can follow the installation instructions.
Peter

Peter said change the file name to CWM

I hope I'm not patronizing, but ...
sm625614 said:
Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>
Click to expand...
Click to collapse
I hope I don't insult you, but did you connect the phone to your PC via USB? The reason I ask is that I got my error message because I disconnected my phone prior to hitting the Enter key. As I mentioned, I didn't want to install it a second time and risk doing something harmful.
Did you also get FASTBOOT USB highlighted on your device after you plugged it in?
Peter
Addendum: Don't forget that these entries in your Command Prompt are case sensitive. Capital letters must remain as capitals, and small letters as small ... exactly as shown in my instructions. Again, I hope I'm not patronizing anyone. That's not my intention.

Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.

Did you ...
sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
One thing I should have included in my first post (I will amend it shortly), is a link to the actual Clockworkmod Recovery file, which is currently available on another thread.
Did you download THAT file?
Peter
Addendum: Clockworkmod Recovery Files link now included in original post
Addendum 2: Re-installing HTC Sync might be helpful. It's what I would eventually do.

YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?

I changed the first image in the original post ...
I changed the first image in the original post. It now includes the Clockworkmod Recovery file, marked as CWM.
Peter

Hmm, I would ...
sm625614 said:
YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?
Click to expand...
Click to collapse
Well, I'm not entirely sure. What I would do is start all over again after restarting your PC and Phone. If it does not work then, uninstall and reinstall HTC sync. After that, I'm stumped. Sorry.
Peter

sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
Do you have a file named "CWM.img" in the same folder as fastboot? That part of the command is telling fastboot which file to install. Make sure the image file is named correctly, or you can alter the command to reflect the name of the file.

I think you should write it into the title and the post saying for now this is only for Rogers users. It might cause a problem bbecause you said even if the bootloader ssays tampered it'll work. And I'm on att and it says tampered bbut this won't work for ATT HOX.
Just a precaution
Sent from my HTC Vivid 4G LTE using Tapatalk 2

[Need Serious Quick HELP!!!]One S stuck.on bootup

im on my one s, found out that my volume wasnt working an so i tried to fix it by reflashing the rom, but by accident i did a factory reset and the rom was gone, i already wiped the davlik and all that then i barely remembered that i already deleted the rom (was flashing T-Mobile noble series 7.5 for USA version) so now i tried to reboot the phone and im stuck on the bootup and it stays there for a GOOD while..im freaking out right now, anyway i can still get into the bootloader and fastboot but i cant get the rom back into my phone, i did no back ups and im really scared, if anyone can help it would be totally awesome. And if it helps I used the hasoon toolkit 1.0 to unlock my phone and Paul o Brian method to root it.

search for adb and push.
You schould be able to push the rom zip via ADB onto the sdcard and afterwards you can normaly flash it via cwm recovery

HighRoIIer said:
search for adb and push.
You schould be able to push the rom zip via ADB onto the sdcard and afterwards you can normaly flash it via cwm recovery
Click to expand...
Click to collapse
can you post a link to get it, i'd look through the whole place but i have to get to school and the last weeks of it are keeping me busy..i would really appreciate it if you could find me a link

Nice descriptive title of this thread...
Anyways http://lmgtfy.com/?q=adb+push+rom if youre in a hurry, and http://www.catb.org/~esr/faqs/smart-questions.html for when you have more time again, good luck m8
Sent from my HTC One S using xda premium

any help making this easier, idk what the hell im doing, im just trying to push my rom into the phone, this is confusing, im going insane!!!! ok i need this alittle easier im a noob at this, i got my phone rooted with cwm and i accidentallly erase the rom now im trying to put it back in. is there a certain adb fastboot that im missing cuz i tried it and it gives me the correct prompt file....this is really starting to irritate me, it doesnt even push the rom in......i would really appreciate some step by step process on how to do this today.this is my first phone and i really dont want it to brick at all.

let's assume you have adb and fastboot files on pc, if not you need to either install them to a folder of your choice ie Android or install android sdk and set them up that way:
These are the files that need to be in that folder--
http://dl.dropbox.com/u/28338566/adb_fastboot_win32.zip
but if you have them on pc and can connect phone and open command window, cd to your folder where the adb and fastboot files are, maybe something like cd/ hit enter then cd android/android-sdk-windows/tools, or whatever the path is
when you are there and right after the whatever your path is type adb devices and you should get your phone id #
you can google some of this stuff and see videos
if you can get that far do this: download the same rom to your pc and extract it with winrar. open it and you should see a system.img and boot.img file. copy them to the folder where you have the adb/fastboot files
then after you have the adb devices command recognizing your phone type this:
adb reboot bootloader which will put you into fastboot, to verify that before you proceed you can type fastboot devices and see the phone ID # again--then
fastboot erase system
fastboot erase boot
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
not sure if you need fastboot -w since you already wiped userdata
you should then be able to get rom booted back up and reset things up again--then nandroid and you should always have an sdcard bu also
if you don't have a recovery anymore you can fastboot it same way by typing
fastboot flash recovery "exact name of recovery.img"
fastboot reboot
I am no expert and you can research this stuff till you feel comfortable or someone can confirm

Yes still no.luck, I'm still stuck on boot up...
Sent from my YP-G1 using XDA

You seem to be able to use adb from what you post. So
1) Boot the phone into CWM
2) Put the rom into the same folder on your pc as the adb program
3) Open a command prompt on the pc, and navigate to the folder with the rom and adb in it, eg "cd c:\adb"
4) Push the rom to the phone: "adb push rom.zip /mnt/sdcard" (if it doesn't work, try it again and change "mnt/sdcard" to just "sdcard"
5) In CWM, choose flash zip file. The zip file should be in the root of your sd card.

rugmankc said:
let's assume you have adb and fastboot files on pc, if not you need to either install them to a folder of your choice ie Android or install android sdk and set them up that way:
These are the files that need to be in that folder--
http://dl.dropbox.com/u/28338566/adb_fastboot_win32.zip
but if you have them on pc and can connect phone and open command window, cd to your folder where the adb and fastboot files are, maybe something like cd/ hit enter then cd android/android-sdk-windows/tools, or whatever the path is
when you are there and right after the whatever your path is type adb devices and you should get your phone id #
you can google some of this stuff and see videos
if you can get that far do this: download the same rom to your pc and extract it with winrar. open it and you should see a system.img and boot.img file. copy them to the folder where you have the adb/fastboot files
then after you have the adb devices command recognizing your phone type this:
adb reboot bootloader which will put you into fastboot, to verify that before you proceed you can type fastboot devices and see the phone ID # again--then
fastboot erase system
fastboot erase boot
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
not sure if you need fastboot -w since you already wiped userdata
you should then be able to get rom booted back up and reset things up again--then nandroid and you should always have an sdcard bu also
if you don't have a recovery anymore you can fastboot it same way by typing
fastboot flash recovery "exact name of recovery.img"
fastboot reboot
I am no expert and you can research this stuff till you feel comfortable or someone can confirm
Click to expand...
Click to collapse
Yea I'm still stuck and after a long time of seeing a couple of people not being able to fix my issue, I'm wondering of someone can confirm if this works or if it's possible to flash a ROM without putting it in the phone just flash it from adb? Been a while since I got on and I'm just gonna dedicated time on fixing my one s.... I really appreciate the feedback
Sent from my YP-G1 using xda app-developers app

Yes you can push it thru adb as mentioned above
i have to call it a nite. Just google pushing a Rom thru adb for more Info if needed
---------- Post added at 05:21 AM ---------- Previous post was at 05:12 AM ----------
You never mentioned just downloading Rom to pc and copying to sd card. Then thru recovery wipe and flash rom.
---------- Post added at 05:26 AM ---------- Previous post was at 05:21 AM ----------
Never mind guess you can't connect phone pc and mount to copy files

This thread show how to ADB push a file to your phone
http://forum.xda-developers.com/showthread.php?p=26430276

Yea I'm gonna try that today but I was wondering if somehow we can make the computer flash it onto the phone for us (you know technology now a days) for situations like this for people who can't get access to their sd cards since the sd cards are non removable and make it a little more simpler to fix phones in this type of situation....just a thought put out there, I'm just thinking alot of things to make situations like this easier for people who are trying to get the best of their phone.
Sent from my samsung galaxy player

leohdz148 said:
Yea I'm gonna try that today but I was wondering if somehow we can make the computer flash it onto the phone for us (you know technology now a days) for situations like this for people who can't get access to their sd cards since the sd cards are non removable and make it a little more simpler to fix phones in this type of situation....just a thought put out there, I'm just thinking alot of things to make situations like this easier for people who are trying to get the best of their phone.
Sent from my samsung galaxy player
Click to expand...
Click to collapse
Yeah with a removable SD card it would have been as easy to just take the sdcard and stick it in the computer.
Just be patient and learn to use adb. In the long run it will make things easier for you. Plus you earn some valuable info and upgrade from noob status.
Good luck!
Sent from my HTC One S using Xparent ICS Tapatalk 2

ok....I will give this a try until I get my phone restored, most of my time is dedicated to my phone. Will update later on on progress
Sent from my samsung galaxy player

Just go on bootloader, install CWM recovery (adb is working on it) and send a rom by adb : adb push rom.zip /sdcard
copy the rom in adb folder first and replace "rom.zip" by the name of your rom.
Next go to recovery and flash your rom !
I already have he same problem like you, I was scared too, but don't panic you can install a rom

Ok I just got my phone back and it gets stuck on the boot on the way to the bootloader I can't get into Fastboot or the recovery, any ideas?
Nvm I got it back now it's only the recovery it goes to right away I try to go into bootloader but it gets stuck.on the HTC boot with red text displaying on it. Ok another thing I got into the bootloader and flashed the stock recovery but it got stuck on the boot again....ok another edit, I got the other recovery flashed but it won't boot into recovery it stays on the boot screen with red text.
Sent from my samsung galaxy player

I get back into the bootloader and flashed the recovery again and then try to go into recovery but it stays stuck On boot up with red text for a little bit then turns off black then turns on again in bootup with red text and stays there, any clues?
Edit: I'm in recovery now but it won't push the ROM and I keep trying but it says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my samsung galaxy player

Not sure what all you have done by now--so--
First off did you unlock again, as HTC may have locked it--even though you have red letters? (You said you just got it back--assume from HTC)
If unlocked confirmed--
Can you turn phone on and have it just boot into the homescreen
If so, can you connect to pc and have phone with usb debugging on and fastboot off (fastboot is under settings/power). Open command window and cd to your adb/fastboot folder and type adb devices then fastboot devices
if they work put latest cwm recovery image in the adb/fastboot folder and flash it by--
type adb reboot bootloader
then fastboot flash recovery recovery.img of course use exact recovery image name
if adb devices and fastboot devices don't work verify your sdk is set up and drivers are installed--
you may have already done this--sorry, just trying to start at the beginning

Ok so I'm at the point where I'm in recovery and the command prompt is open but idk how to do this...some help would sure be nice this is what I get when. I try to push something
Note: I kinda modified the name to just ROM so I won't have to type so much
Sent from my samsung galaxy player

what is x86 Mac? i just do a cd/ [enter] then cd android/android-sdk-windows/tools [enter]. that is my path. If on windows and sdk, you need the environmental variable path set to that path i just typed, or whatever your's is. not sure on a mac.
on windows I use forward slashes--not sure it matters
at the prompt you show type adb devices, if it doesn't come back with # followed by numbers you are not set up with adb, reinstall htc drivers and make sure whatever you are fastbooting, is in your tools folder

[Q] [Problem] Cannot flash recovery

Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.

It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error. Screenshot of cmd would be very helpful too please
Sent from my Nexus 5 using Tapatalk

rootSU said:
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What I did is to check if the boot loader is unlocked.
And yes. It is unlocked.
So I carried onto checking if fastboot detects my devices by doing "fastboot devices". And my nexus5 gets detected.
Then I moved on to trying to flash recovery using " fastboot flash recovery recovery.img ".
But the error appears at this point. And I'm stuck.
Is this sufficient?
Do note that I did change the file name to recovery and not recovery.img as most files do not include the file type in the file name.

Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.

You would be better served setting windows not to hide known file types to be honest.
A screenshot of your fastboot flash attempt and error would be most useful please
Sent from my Nexus 5 using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:28 PM ----------
chblg said:
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
Click to expand...
Click to collapse
He hasn't got root. Fastboot is his only option
Sent from my Nexus 5 using Tapatalk

Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img

Nukyi said:
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
Click to expand...
Click to collapse
rootSU said:
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Click to expand...
Click to collapse
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.

Nukyi said:
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Click to expand...
Click to collapse
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.

Nukyi said:
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Click to expand...
Click to collapse
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?

rootSU said:
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
Click to expand...
Click to collapse
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.

Nukyi said:
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Click to expand...
Click to collapse
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks

rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
Alright. I'll do it and get back to you shortly.
Thank you.
Really hope this fixes the problem.

rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?

Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)

jj14 said:
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
Click to expand...
Click to collapse
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.

Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
Now try and run cmd as an administrator if you are not doing

Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
no. the recovery.img is not in c:\users\username\
put that file there, then retry your command
OR
fastboot flash recovery c:\entire\path\to\recovery.img

Nukyi said:
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Click to expand...
Click to collapse
are you sure you downloaded the image and not the zip??

samersh72 said:
are you sure you downloaded the image and not the zip??
Click to expand...
Click to collapse
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.

Nukyi said:
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Click to expand...
Click to collapse
Ah. It just worked suddenly. No idea why. But I guess @rootSU 's suggestion works well.
And maybe also @Zepius 's suggestion.
Here's what I did to help others who have the same problem.
I did what rootSU asked me to do (changing the "path" part).
Then took Zepius suggestion and duplicated the recovery img in a few folders (the original folder i'm using, on desktop, on C drive root folder)

How to unroot, lock bootloader and go back to stock?

For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks

Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.

Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?

iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.

@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).

iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already

@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?

Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?

iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.

here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.

iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?

"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.

Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!

Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)

Database Info

welcome