Related
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Did you boot up the xoom? And do a DB reboot bootloader? Then fastboot OEM unlock?
Sent from my Xoom using xda premium
Yes I did...
Was it unlocked when you sent in? If so it may still be unlocked.
Sent from my Xoom using xda premium
It was unlocked, but they've upgraded the software to 3.2.2 and it's locked again.
It might not be. They don't have to lock it to flash it. And they probly didn't check either.
Sent from my Xoom using xda premium
Ok....pardon the ignorance but how can I tell? I no longer have Superuser. I can't even flash a custom image. Should I downgrade it to 3.0, Root, and then flash it with the Custom 3.2.2 found here on XDA?...
No not that way it screws it up! Use this and only this! Skip the unlock and see if the files work, then you know you were still unlocked.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
tdetroit said:
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
Click to expand...
Click to collapse
That's because your timing is slightly off, and you're letting the stock recovery overwrite your custom recovery. You have to "catch the boot"
You can follow these steps:4. Install recovery image (CWM)
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/show....php?t=1074979 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery recovery-solarnz-100611-1150.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
tdetroit said:
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Click to expand...
Click to collapse
I got mine back yesterday morning then used the Universal Xoom Root instructions and files to root it yesterday afternoon. Perfect!
-ts
I've tried that...won't work. As far as my timing being off....I'm literally watching the Screen the whole time...I never even get anything except the Fastboot Protocol screen...nothing changes. I simply can't go further. I've tried loading the img file (Step 4), but can't even get that far. I've spent an hour on the phone with Motorola yesterday and after being bounced to 5 different techs, they told me to contact the developer.....which I've done, with no success. I'm almost tempted to send this damn thing back and ask them to revert my device and install an older OS onto it.
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
hammer4203 said:
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
It is. That was the first thing I've checked.
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
hammer4203 said:
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Ah, I will do that. Matter of fact, I'll download it to my other laptop...which never had any sort of anything SDK related on it, give it a fresh start. Thanks....will do this when I get home this evening.
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
tdetroit said:
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
Click to expand...
Click to collapse
Nevermind. IT WORKED. I ended up using my work laptop. Something's wonky with both of my personal laptops....either way, it's now unlocked. Thanks for everyone's help and patience.
Ur welcome! Also remember your mouse on a desktop? Took me weeks to figure out the damn thing was causing the bsod errors, and it seemed to work perfectly fine. I would back up your computers you have issues with and do a fresh install on them. I do every 6mo or so.
Sent from my Xoom using xda premium
i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...
albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question
like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.
looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes
i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.
Hey everyone,
I have an LG P500 ( AT&T Variant - 'LG Thrive'). I had it rooted, although this is not the cause of the bricking. One day all of a sudden out of the blue it would not boot. After pressing the power button, the LG logo will come on, and the 4 button LEDs will flash 4 times and stay lit and the device will continue to stay on the LG screen. Currently this is the status of my device. ADB or fastboot are unable to notice the device whether it's on the LG screen, Emergency mode, or the console looking screen (white text/black background). FYI, I never had CWM or any alternate recovery program installed. Also - suggestions for the KDZ program would not be helpful, I run Linux and do not have access to a Windows computer.
Thanks for any help!
ok try factory reset power+vol down +home
hold them till u see android
androidisfuture said:
ok try factory reset power+vol down +home
hold them till u see android
Click to expand...
Click to collapse
This just brings me to the udc_start terminal looking screen (white text/black background).
rjortiz said:
This just brings me to the udc_start terminal looking screen (white text/black background).
Click to expand...
Click to collapse
Ok if that doesnt' works, you try this,, Power + Volume Up + Home,, that's how i use to make a factory reset on my thrive
And if that doesn't work either try this http://forum.xda-developers.com/showthread.php?t=1088046, this helped me to unbrick my thrive,, take note, that you will need a windows computer,, don't know if this works on ubuntu or another linux variant
If you decide to try the second method pm me
gabo_lope said:
Ok if that doesnt' works, you try this,, Power + Volume Up + Home,, that's how i use to make a factory reset on my thrive
Click to expand...
Click to collapse
This key combo has no effect on my device.
gabo_lope said:
And if that doesn't work either try this http://forum.xda-developers.com/showthread.php?t=1088046, this helped me to unbrick my thrive,, take note, that you will need a windows computer,, don't know if this works on ubuntu or another linux variant
If you decide to try the second method pm me
Click to expand...
Click to collapse
Basically this thread is showing how to flash recovery through fastboot, which I can/have tried through my system. As I mentioned, fastboot does not recognize the phone, nor will anything transfer through it (or through ADB).
I'm not sure but I'm starting to think that the last time my phone worked I did not have debugging enabled. Would that cause this current problem? Although, the phone does display the console screen:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
--suspend--
deleted
gabo_lope said:
that shows when you plug it in on the computer?
Click to expand...
Click to collapse
It shows this only when I do the key combo VolDn+Home+Power. Plugging it into the computer has no effect - it goes to the LG logo screen.
rjortiz said:
It shows this only when I do the key combo VolDn+Home+Power. Plugging it into the computer has no effect - it goes to the LG logo screen.
Click to expand...
Click to collapse
on what linux version are you on?
gabo_lope said:
on what linux version are you on?
Click to expand...
Click to collapse
kUbuntu, the system works fine connecting to my other Android based phone - so that is not an issue. I also have a Debian system to use if I needed to.
rjortiz said:
kUbuntu, the system works fine connecting to my other Android based phone - so that is not an issue. I also have a Debian system to use if I needed to.
Click to expand...
Click to collapse
OK, so if you say that fastboot doesn't recognizes the phone, i would guess that you have the android sdk, for fastboot to work,,, also the phone was recognized before by the computer??
just had an idea,, i will try on my computer...
well i tried to screw up my phone, by using using an incorrect recovery,, to recover it using ubuntu, the phone was recognized, and i recover it, but i had debugging enabled, and as you said before you have it disabled... The thing is this: i booted into the rom, and turn off the debugging, then i screw up my phone again and connect it, and it wasn't recognized,, I run out of ideas, maybe someone else knows a way to comunicate the phone and the computer.
The only thing left would be using KDZ, but that's a windows program, you could use wine, but even running it on windows sometimes causes a hard brick, i couldn't image what would happen if you use it on wine, so if you still have warranty i suggest you to use it
My best of luck...
gabo_lope said:
,, also the phone was recognized before by the computer??
just had an idea,, i will try on my computer...
Click to expand...
Click to collapse
I wanted to state that my other Android phone connects to this computer fine, therefore saying the computer itself does not have a problem with connecting. But, no, this bricked phone is not recognized by the computer.
gabo_lope said:
OK, so if you say that fastboot doesn't recognizes the phone, i would guess that you have the android sdk, for fastboot to work,,, also the phone was recognized before by the computer??
just had an idea,, i will try on my computer...
well i tried to screw up my phone, by using using an incorrect recovery,, to recover it using ubuntu, the phone was recognized, and i recover it, but i had debugging enabled, and as you said before you have it disabled... The thing is this: i booted into the rom, and turn off the debugging, then i screw up my phone again and connect it, and it wasn't recognized,, I run out of ideas, maybe someone else knows a way to comunicate the phone and the computer.
The only thing left would be using KDZ, but that's a windows program, you could use wine, but even running it on windows sometimes causes a hard brick, i couldn't image what would happen if you use it on wine, so if you still have warranty i suggest you to use it
My best of luck...
Click to expand...
Click to collapse
Thank you for all your help and attempts to recreate the problem...I hope your phone isn't completely bricked as well.
rjortiz said:
Thank you for all your help and attempts to recreate the problem...I hope your phone isn't completely bricked as well.
Click to expand...
Click to collapse
that's the thing, i was able to recover my phone using this windows tool http://forum.xda-developers.com/showthread.php?t=1827723
rjortiz said:
Hey everyone,
I have an LG P500 ( AT&T Variant - 'LG Thrive'). I had it rooted, although this is not the cause of the bricking. One day all of a sudden out of the blue it would not boot. After pressing the power button, the LG logo will come on, and the 4 button LEDs will flash 4 times and stay lit and the device will continue to stay on the LG screen. Currently this is the status of my device. ADB or fastboot are unable to notice the device whether it's on the LG screen, Emergency mode, or the console looking screen (white text/black background). FYI, I never had CWM or any alternate recovery program installed. Also - suggestions for the KDZ program would not be helpful, I run Linux and do not have access to a Windows computer.
Thanks for any help!
Click to expand...
Click to collapse
ADB wont recognize your phone if you cant enter fastboot.
What you can do is.. enter emergency mode andUse this tool.. its safe.
The recovery image given is for P500.. so replace it with thrive's recovery image.. partition data is ok to use!!
rr0yy said:
ADB wont recognize your phone if you cant enter fastboot.
What you can do is.. enter emergency mode andUse this tool.. its safe.
The recovery image given is for P500.. so replace it with thrive's recovery image.. partition data is ok to use!!
Click to expand...
Click to collapse
LGMDP is for Windows and won't run correctly in WINE.
Install VMware.. then you can install windows over it.
It will be like using windows over linux.. you dont need any partition or anything for that.
After you are done.. you can remove it easily!!
Are you running fastboot in terminal with root permissions
Sent from my LG-P500 using xda app-developers app
lg-one-man said:
Are you running fastboot in terminal with root permissions
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
I've tried both, either way gets the same result of nothing.
Regardless, I stated that I can use this computer to successfully connect to my other phone because I wanted to eliminate the possibility of the computer as a problem with connecting to the device.
When you run fastboot in terminal and then type device ,what does it say?
Sent from my LG-P500 using xda app-developers app
lg-one-man said:
When you run fastboot in terminal and then type device ,what does it say?
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
It prints nothing and quits. For 'adb devices' it says "List of attached devices" and lists nothing.
Code:
[email protected]:...$ ./fastboot devices
[email protected]:...$ ./adb devices
List of devices attached
[email protected]:...$
I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
I did wipe data. I remember I checked that box
I also got this error in the command line.
simms22 said:
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
Click to expand...
Click to collapse
benzso63 said:
I did wipe data. I remember I checked that box
I also got this error in the command line.
Click to expand...
Click to collapse
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
simms22 said:
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
Click to expand...
Click to collapse
benzso63 said:
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
Click to expand...
Click to collapse
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
simms22 said:
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse
benzso63 said:
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
Click to expand...
Click to collapse
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
bitdomo said:
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Click to expand...
Click to collapse
benzso63 said:
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
Click to expand...
Click to collapse
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
bitdomo said:
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Click to expand...
Click to collapse
benzso63 said:
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
Click to expand...
Click to collapse
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
bitdomo said:
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
Click to expand...
Click to collapse
benzso63 said:
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
Click to expand...
Click to collapse
What is shown on the PC?
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
bitdomo said:
What is shown on the PC?
Click to expand...
Click to collapse
benzso63 said:
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome.
You need to open a Master Class LOL. Seriously, you have no idea how frustrated when you can't get the phone to work.
bitdomo said:
Your welcome.
Click to expand...
Click to collapse
benzso63 said:
I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
Click to expand...
Click to collapse
if your pc cannot detect your phone , it seems you havn't install driver.
Hey,
Tried to root my phone and things got messy.
I'm at a point where when I try to access the bootloader I get the "No command" screen, which I can bypass with the Power+Up keys and reach the "Android Recovery" screen.
I used "Wipe Data/Factory Reset" which didn't help much.
I can't do much more than that because Windows doesn't recognize my device and so I can't apply anything through ADB.
I tried to install the drivers again, but still nothing. My phone doesn't appear on the Device Manager.
Windows does make a sound of connected USB when I enter bootloader, but soon as it hits the "No Command" screen I hear the sound of a disconnected USB device.
Any idea how to make Windows recognize the device again so I could try to install things back with ADB?
Thanks!
OK, managed to solve this part after some reboots.
I'm now failing to ADB the stock image.
The phone says on top of "Andoird Recovery" that it's 7.1.2/NZH54D.
That's the stock image I've downloaded and when I try to ADB it I get on the windows terminal
"cannot read 'sailfish-nzh54d-factory-127f0583.zip'".
How do I move on from this?
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
I would start over from scratch. This guide is really good, it's for Pixel XL, but should be interchangable for Pixel 1 (non-XL), just be careful of the model specific files (salefish vs. marlin)
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
Can't you acces bootloader with "adb reboot bootloader"?
Also make sure u switched on usb debugging in developer options.
Sent from my Google Pixel using XDA Labs
If you get to the screen where you can choose to enter recovery, that is the bootloader. The no command thing is something you always get when you choose to boot to recovery. When on the screen before the no command thing, plug it into your PC. If the PC recognizes it, use fastboot to access it. "Fastboot devices" will show your phone. Adb devices doesn't work there. Bottom line is, it sounds to me you're getting to the bootloader. Just not realizing it.
TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Milly7 said:
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Click to expand...
Click to collapse
Yup. I think I'm good now. Gave up on the ROM thing. Too much headache to maintain it. Sticking to stock. Imperfect, but less headaches.
I wanted to root my device mostly for Titanium backup.
The rest isn't that important to me.
Thanks for the help!