[EDIT: fixed typo ]
My brand new Pixel C is booting into "No command" error and stays there.
Noticed this has popped up once in the forum, wondering how many there are out there? Might be a bigger issue.
Got the device (64GB) Friday afternoon. Installed several standard apps, no rooting, nothing. Suddenly it reset Saturday evening and now boots into "no command". Can not boot device into recovery mode, nothing helps. Always ends up with same message of "no command". (And no USB recovery, apparently, for the Pixel C, at this time – sorry can't post link as on a new account here).
Will call Google first thing Monday (this happened Saturday night). Reckon it may need to be replaced
PallMiller said:
[EDIT: fixed typo ]
My brand new Pixel C is booting into "No command" error and stays there.
Noticed this has popped up once in the forum, wondering how many there are out there? Might be a bigger issue.
Got the device (64GB) Friday afternoon. Installed several standard apps, no rooting, nothing. Suddenly it reset Saturday evening and now boots into "no command". Can not boot device into recovery mode, nothing helps. Always ends up with same message of "no command". (And no USB recovery, apparently, for the Pixel C, at this time – sorry can't post link as on a new account here).
Will call Google first thing Monday (this happened Saturday night). Reckon it may need to be replaced
Click to expand...
Click to collapse
What you are seeing is the stock Android recovery. When you see that, you gotta hit power + volume up (or down) to bring up the recovery menu. However, if it keeps booting you to that by default, it sounds like maybe one of your partitions got corrupted somehow. Have you unlocked your bootloader? If so, I would fastboot flash the individual partitions in from factory image (WITHOUT FLASHING USERDATA). If that doesn't work (meaning your userdata is probably corrupted), then my next step would be flashing the entire factory image (including userdata).
If you haven't unlocked, but are planning to, keep in mind unlocking the bootloader wipes the device, so you will lose all your data.
charesa39 said:
What you are seeing is the stock Android recovery. When you see that, you gotta hit power + volume up (or down) to bring up the recovery menu. However, if it keeps booting you to that by default, it sounds like maybe one of your partitions got corrupted somehow. Have you unlocked your bootloader? If so, I would fastboot flash the individual partitions in from factory image (WITHOUT FLASHING USERDATA). If that doesn't work (meaning your userdata is probably corrupted), then my next step would be flashing the entire factory image (including userdata).
If you haven't unlocked, but are planning to, keep in mind unlocking the bootloader wipes the device, so you will lose all your data.
Click to expand...
Click to collapse
Thanks for your response. As mentioned, I have booted both into fastboot and recovery mode, to no avail. Sorry if that was unclear. I do get that menu to choose fastboot or recovery (or shut off, etc.), however it says "waiting for fastboot command" when going to fastboot, and reverts to "No command error" in the other instances. (I have not unlocked, but very happy to if it helps )
Is there ANY way of simply flashing the device now, esp. since USB recovery is not supported? Any pointers appreciated. Really hope I do not have to send this in to get replaced. Cheers.
PallMiller said:
Thanks for your response. As mentioned, I have booted both into fastboot and recovery mode, to no avail. Sorry if that was unclear. I do get that menu to choose fastboot or recovery (or shut off, etc.), however it says "waiting for fastboot command" when going to fastboot, and reverts to "No command error" in the other instances. (I have not unlocked, but very happy to if it helps )
Is there ANY way of simply flashing the device now, esp. since USB recovery is not supported? Any pointers appreciated. Really hope I do not have to send this in to get replaced. Cheers.
Click to expand...
Click to collapse
So it looks like you can get into the bootloader at least. Do you have ADB/Fastboot set up on your computer, along with the appropriate drivers? After booting into the bootloader, plug it into your computer and open a command prompt where your adb/fastboot is saved. If you type in "fastboot devices", does it show the serial number of the device?
charesa39 said:
So it looks like you can get into the bootloader at least. Do you have ADB/Fastboot set up on your computer, along with the appropriate drivers? After booting into the bootloader, plug it into your computer and open a command prompt where your adb/fastboot is saved. If you type in "fastboot devices", does it show the serial number of the device?
Click to expand...
Click to collapse
Thanks very much! So I've got a serial number. What do I do now? Flashall? [Edit: Device bootloader is locked; also, I have downloaded the "ryu" build image from developers at the google.com website]
PallMiller said:
Thanks very much! So I've got a serial number. What do I do now? Flashall? [Edit: Device bootloader is locked]
Click to expand...
Click to collapse
You need to unlock the bootloader before you can flash anything. You can double check, but I believe the new command is "fastboot flashing unlock" (without the quotation marks of course). The command is the same as the Nexus 6P. After that, it should ask you on the Pixel to confirm unlock, and it will begin the process, wiping all your data from the device. I would let it boot completely back up before unplugging it.
charesa39 said:
You need to unlock the bootloader before you can flash anything. You can double check, but I believe the new command is "fastboot flashing unlock" (without the quotation marks of course). The command is the same as the Nexus 6P. After that, it should ask you on the Pixel to confirm unlock, and it will begin the process, wiping all your data from the device. I would let it boot completely back up before unplugging it.
Click to expand...
Click to collapse
Will do and get back to you, but again: Very, very much appreciate your help. This is awesome.
charesa39 said:
You need to unlock the bootloader before you can flash anything. You can double check, but I believe the new command is "fastboot flashing unlock" (without the quotation marks of course). The command is the same as the Nexus 6P. After that, it should ask you on the Pixel to confirm unlock, and it will begin the process, wiping all your data from the device. I would let it boot completely back up before unplugging it.
Click to expand...
Click to collapse
Sorry, need another pointer please, as I have hit a snag: I am getting "FAILED (remote: Enable OEM unlock is not set)" when trying for "fastboot oem unlock". Any way I can change this? Thanks again.
PallMiller said:
Sorry, need another pointer please, as I have hit a snag: I am getting "FAILED (remote: Enable OEM unlock is not set)" when trying for "fastboot oem unlock". Any way I can change this? Thanks again.
Click to expand...
Click to collapse
I'm no expert by any means, but I believe you need to go into the Developer Options and switch the toggle so that you enable OEM unlocking. At least, I had to do that before unlocking my device the other day. Now if you can't start the device normally at all, I'm not sure if there is a workaround for this. Someone with more experience than myself will hopefully chime in on this.
PallMiller said:
Sorry, need another pointer please, as I have hit a snag: I am getting "FAILED (remote: Enable OEM unlock is not set)" when trying for "fastboot oem unlock". Any way I can change this? Thanks again.
Click to expand...
Click to collapse
Shoot! That's right. I forgot I had to do that with my 6P. But like the post above says, not usre5how you can do this if you can't boot into the OS. You did type "fastboot flashing unlock" and NOT "fastboot oem unlock", right?
charesa39 said:
Shoot! That's right. I forgot I had to do that with my 6P. But like the post above says, not usre5how you can do this if you can't boot into the OS. You did type "fastboot flashing unlock" and NOT "fastboot oem unlock", right?
Click to expand...
Click to collapse
Thanks, yes, did try that – not sure what to do now. I reckon there should be a way to unlock the device. Might poke around Android studio to see what's possible. Thanks again!
PallMiller said:
Thanks, yes, did try that – not sure what to do now. I reckon there should be a way to unlock the device. Might poke around Android studio to see what's possible. Thanks again!
Click to expand...
Click to collapse
Hi, just to tie up any loose ends here. I ended up having to replace the Pixel C as my OEM was locked. I have since received a replacement model and am extremely happy with it so far.
I have exactly the same issue like you, already contacted google and the offered me a replacement or a refund. So I am still thinking which option to take becouse I don't like my WiFi reception on the tablet.
Edit Nevermind
I've entered this situation twice and flashing the factory image fixed it.
It seems like that editing build.prop in TWRP leads to this problem. Even if you simply reflash system.img it still boots into recovery. It's possible that the corrupt flag is saved in some other partition.
I just got this too. I have not rooted, unlocked, or done anything. It rebooted while I was using it and now I can only get to the "No command" screen. That's too bad. I got it just yesterday and I really like it. If I had modified it in any way I'd wonder if I messed something up, but I haven't rooted, unlocked, or done anything else beyond the normal setup and installing some apps.
Did you set 'Enable OEM unlock' in 'Developer options' ?
Sent from my Nexus 5X using XDA-Developers mobile app
ilpolpi65 said:
Did you set 'Enable OEM unlock' in 'Developer options' ?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
No, I didn't do anything in developer options. I could try flashing the factory image if it came with a cable. I only ordered two and both just fall out of the port.
I don't think you can flash if you didn't set 'Enable OEM unlock'
Sent from my Nexus 5X using XDA-Developers mobile app
So experiencing the same issue. Device boots to "No Command".
The device is bootloader unlocked. It's been about a month, but if I recall correctly I did this before the first boot (bypassing the OEM Unlock option in Developer Options). Which I have read (sadly after I did it) can be an issue. Digging in other forms (about other Nexus devices) to see if there is a solution, but none so far.
I have already tried the following:
- Flash factory image (both M releases and N preview), reboots to the "No Command"
- Format all partitions, flash factory image, same "No Command"
- Flash custom recovery, then flash custom ROM (only tired unofficial CM13), just boots to Google logo, will be trying more options later (have read this may be possible solution)
- Flash factory image and then relock before first boot, same "No Command"
Before anyone suggests RMA, I had to RMA my original Pixel C and Google sent me a replacement. Then a day later a second unit showed up, this is that unit. May eventually try RMA (feels a bit unethical after I keep a mistake shipment) but right now I have a free device to play with.
Any help is appreciated.
So I'm trying to unlock bootloader using this tutorial:
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
But I get stuck when typing the "fastboot" line, since there is no fastboot option in my Download Mode.
M9 with Marshmallow update.
Any help will be appreciated.
tetruper said:
So I'm trying to unlock bootloader using this tutorial:
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
But I get stuck when typing the "fastboot" line, since there is no fastboot option in my Download Mode.
M9 with Marshmallow update.
Any help will be appreciated.
Click to expand...
Click to collapse
You need to be in download mode for the instructions to work.
There is a video of the procedure:
https://www.youtube.com/watch?v=0R6iZ3GtVnQ
Good luck!
That's my actual problem
The procedure shown in the video is made for devices that already have bootloader unlocked, but mine isn't, and the reason is step 2 shown in htcdev.com:
I don't have any fastboot option to highlight.
Also, when typing the "fastboot" command in terminal, I get the "unknown command" message.
tetruper said:
That's my actual problem
The procedure shown in the video is made for devices that already have bootloader unlocked, but mine isn't, and the reason is step 2 shown in htcdev.com:
I don't have any fastboot option to highlight.
Also, when typing the "fastboot" command in terminal, I get the "unknown command" message.
Click to expand...
Click to collapse
U do have fastboot.exe in the folder where u start the command prompt?
Here is another guide:
http://www.droidviews.com/how-to-unlock-bootloader-on-htc-one-m9/
Oh dear, now another problem since I'm on a Mac. :silly:
I'll get a windows laptop and do as you say, hopefully I'll do it right, otherwise please guide through the process.
It was a lot easier back in the One X days...
Fain11 said:
U do have fastboot.exe in the folder where u start the command prompt?
Here is another guide:
http://www.droidviews.com/how-to-unlock-bootloader-on-htc-one-m9/
Click to expand...
Click to collapse
So I'm stuck in bootscreen with the red text "this build is... bla bla...", the phone powers off, and then again to the same screen with the same message.
What did I miss?
Also, I was following the steps in the video without reading, and accepted that TWRP root my phone, despite the code saying not to. Maybe that's the problem?
Installed TWRP 2.8.5.0 and SuperSU 2.76
I've already managed to unlock bootloader, because it says: System modified, *unlocked*, s-on
U are already unlocked.
Now, restore a backup, if u did one in TWRP.
If not, try installing a custom ROM, ARHD or Maximus are closest to stock.
Good luck!
Stuck at google splash screen, ADB doesn't list devices with "ADB Devices" command
I was using Masgisk. I followed the steps from masgisk to restore before i took the OTA. The ota moved to step 2 but then restarted. Now i am stuck at the splash screen. I can get reboot to the bootloader but after I lauch my CMD from the platform tools window and use the command "ADB Devices" nothing is listed. I don't remember enabling usb debugging prior to this. Is there anything i can do to flash something that will not erase my data. If not is there any way i can flash the factory image?
angelino0919 said:
I was using Masgisk. I followed the steps from masgisk to restore before i took the OTA. The ota moved to step 2 but then restarted. Now i am stuck at the splash screen. I can get reboot to the bootloader but after I lauch my CMD from the platform tools window and use the command "ADB Devices" nothing is listed. I don't remember enabling usb debugging prior to this. Is there anything i can do to flash something that will not erase my data. If not is there any way i can flash the factory image?
Click to expand...
Click to collapse
Is your bootloader "fully" unlocked?? Have you tried side loading the OTA? It will not wipe data. From bootloader mode, type in fastboot devices to see if you get your phone ID displayed. The USB debugging part is what's worrying me though! Is OEM unlocking checked off in developer options at least??
Badger50 said:
Is your bootloader "fully" unlocked?? Have you tried side loading the OTA? It will not wipe data. From bootloader mode, type in fastboot devices to see if you get your phone ID displayed. The USB debugging part is what's worrying me though! Is OEM unlocking checked off in developer options at least??
Click to expand...
Click to collapse
Thank you for your reply, yes device state is unlocked and when I use fastboot devices I see something but not when I use adb devices
Edit: I was able to restore the factory image thank you though
I have the MetroPCS Revvl 4+ 5G model number 5062Z.
No matter what I do I can't get into the bootloader.
My adb is working. I can use the commands "adb reboot bootloader" and that just reboots the phone.
I can use "adb reboot fastboot" and that will bring me to a recovery with an option to reboot to bootloader but again that just reboots the phone.
Regular "adb reboot recovery" doesn't even have the bootloader option.
Please any help would be much appreciated.
Thank you for any help.
linsalata28 said:
I have the MetroPCS Revvl 4+ 5G model number 5062Z.
No matter what I do I can't get into the bootloader.
My adb is working. I can use the commands "adb reboot bootloader" and that just reboots the phone.
I can use "adb reboot fastboot" and that will bring me to a recovery with an option to reboot to bootloader but again that just reboots the phone.
Regular "adb reboot recovery" doesn't even have the bootloader option.
Please any help would be much appreciated.
Thank you for any help.
Click to expand...
Click to collapse
I have the T-Mobile model and experiencing the exact same issue.
Were you able to find a way to resolve it? Thanks
Sim Killer Pro tool Allow unlock bootloader for T-Mobile REVVL V+ 5G o other device MTK
darkherman said:
Sim Killer Pro tool Allow unlock bootloader for T-Mobile REVVL V+ 5G o other device MTK
Click to expand...
Click to collapse
Is there a link to the software or post you can detect me to cause I'm having the same exact issue they are
Where are all my developers @ when I need you guys most lol
linsalata28 said:
I have the MetroPCS Revvl 4+ 5G model number 5062Z.
No matter what I do I can't get into the bootloader.
My adb is working. I can use the commands "adb reboot bootloader" and that just reboots the phone.
I can use "adb reboot fastboot" and that will bring me to a recovery with an option to reboot to bootloader but again that just reboots the phone.
Regular "adb reboot recovery" doesn't even have the bootloader option.
Please any help would be much appreciated.
Thank you for any help.
Click to expand...
Click to collapse
fastboot oem unlock
Check it out. Right here guys.
Not sure if it's the 4+ or 4.... But It should work...
Finally...
Post in thread 'T-mobile revvl 4 root' https://forum.xda-developers.com/t/t-mobile-revvl-4-root.4173557/post-86648975
mrbigruben said:
Is there a link to the software or post you can detect me to cause I'm having the same exact issue they are
Click to expand...
Click to collapse
[ROOT] [FLASH STOCK]
DISCLAIMER: Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding. ***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A...
forum.xda-developers.com
i dont know why my last post published as 2 posts. #8 & #9 are one post. weird
linsalata28 said:
I have the MetroPCS Revvl 4+ 5G model number 5062Z.
No matter what I do I can't get into the bootloader.
My adb is working. I can use the commands "adb reboot bootloader" and that just reboots the phone.
I can use "adb reboot fastboot" and that will bring me to a recovery with an option to reboot to bootloader but again that just reboots the phone.
Regular "adb reboot recovery" doesn't even have the bootloader option.
Please any help would be much appreciated.
Thank you for any help.
Click to expand...
Click to collapse
to unlock bootloader? ibet you can do it with python and adb. IOt has mediatek chipset, you'll need tyhose drivers and python 3. download/bootloader/brom mode is what youre looking for here. unplug your device. power off. hold only the volume keys. both volume keyts. not the power key. while holding the volume keys, connect the device to your pc. the screen will remain black but it should be in BROM mode.
"python mtk e metadata,userdata,md_udc"
Disconnect and power on. If the device has been reset, then you have confirmation. Prepare the phone again. Enable developer options, OEM unlock, USB Debugging. Disconnect, then power off. While holding ONLY both volume keys, connect it to the comp.
Enter the following command without ":
"python mtk da seccfg unlock"
Try this. I believe it's the same fore the REVVL 4+. Not the root guide, just the first part about unlocking bootloader with python.
[ROOT] [FLASH STOCK]
DISCLAIMER: Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding. ***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A...
forum.xda-developers.com
I think that is for Mediatek (revvl 4), not Qualcomm (revvl 4+). It didn't work for me on a Revvl 4+ (TMobile)
Ive had my LG G7 for about a year now. I managed to unlock the bootloader without any problems and used magisk ok.
I just came to upgrade the firmware without any problems. I enabled dev and usb debug but the 'Enable oem unlock' button is greyed out and displays "bootloader already unlocked" ok so not a problem - that is until I come to access the bootloader again.
Here is the message:
Welcome to Fastboot mode: Please check "Enable OEM unlock" in developer options
adb commands no longer work at this point as connection is lost. Only choice is manually reboot or switch off.
WTF now what. Im unable to root or restore the bootloader. So even though its unlocked and displays the bootloader unlocked message when booting - Fastboot does not see it and it still wants me to 'Enable oem unlock' but its greyed out.
Any suggestions please anyone
You can use QFIL to restore laf_a & laf_b. Then flash full rom (Refurbish) in Download mode.
ps: the reason is you do not flash full rom after unlock bootloader in order to tell to the machine that you are in the illegal mode kakaka.
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall, cant freeze garbage etc.
Being relatively unsure, would you mind going over the QFIL method with me.
Thanks
chadandchew said:
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall
Click to expand...
Click to collapse
Never used QFIL before. Where do I get the firehose elf file from. I noticed a couple of elf files in the extracted folder, is it one of these.
Do I have to create any xml files and do I have to rename any of the kdz extracted files?
Some posts are a bit old and for other models.
Instead of flash the boot_a from magisk_patched image, you can use command
fastboot boot magisk_patched.img
and use the LGUP to reflash the firmware.
If you look at the photo above I LOSE ALL ADB commands after adb reboot bootloader.
fastboot boot magisk_patched.img or any other command just displays "Waiting For any Device" in CMD window.
This is my problem because the bootloader is already unlocked and oem greyed out - it is asking me to "Enable OEM Unlock"
I am wanting to either root the phone or restore bootloader to locked. Sorry for any confusion
type fastboot devices and show me the result.
maybe you do not have correct fastboot driver
It did say waiting for any device but now its gone from bad to worse. I followed this guide Here and now all I get is fastboot screen, see photo. If I now try fastboot devices then fastboot flash boot_a magisk_patched.img it shows error which does not look good actually , photo 2. Cant get download mode. If I try to get it by holding volume button and inserting usb lead I get this nasty screen, photo 3. I think that some of the partitions may have been overwitten. . Stupid move on my part.
Forgot to mention - EDL is still accessable
Ive managed to sort the above problem
QFIL flashed only the following 6 files :
abl_a and abl_b
laf_a and laf_b
boot_a and boot_b
Phone rebooted perfectly after this.
Thanks for your advice