Database Users

NEXUS 4 stuck during booting X screen? now what? (unrooted+stock)

So today i discovered that my month old Nexus 4 did not want to boot again.
Last night the phone was off, so i assumed the battery was dead, after putting it in the charger and asking it to boot i went to sleep.
when i woke up i was still looking at the multicoloured pulsating X.
since then it keeps getting stuck at the X screen, powering it down will make the phone power up again for no reason.
The phone was running a OTA version of 4.2.2
When powering it on with ON & vol - I get the boot menu, though navigating to the recovery mode resulted in a "No command." line with a red triangle on a android.
Currently i have no experience with either rooting/flashing, neither am i aware if this is the only option to fix this semi bricked phone.
How would i best go about fixing this issue?
Thanks.

MissStabby said:
So today i discovered that my month old Nexus 4 did not want to boot again.
Last night the phone was off, so i assumed the battery was dead, after putting it in the charger and asking it to boot i went to sleep.
when i woke up i was still looking at the multicoloured pulsating X.
since then it keeps getting stuck at the X screen, powering it down will make the phone power up again for no reason.
The phone was running a OTA version of 4.2.2
When powering it on with ON & vol - I get the boot menu, though navigating to the recovery mode resulted in a "No command." line with a red triangle on a android.
Currently i have no experience with either rooting/flashing, neither am i aware if this is the only option to fix this semi bricked phone.
How would i best go about fixing this issue?
Thanks.
Click to expand...
Click to collapse
Try to get in bootloader mode then go to recovery and wipe cache /do a data factory reset and reboot.

Okay. Get back into recovery by holding Vol-/pow.
Then scroll to recovery.
When in recovery reveal the menu by pressing vol+/pow
Once there wipe data and reset cache.
Sent from my Nexus 4 using xda premium

gee2012 said:
Try to get in bootloader mode then go to recovery
Click to expand...
Click to collapse
When i try to get into recovery mode i am greeted with this:
{
"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"
}
and a "No command." message.
There is no interface there to work with.

Try vol+/pow to reveal recovery menu once on that screen
Sent from my Nexus 4 using xda premium

elliot.newnham said:
Try vol+/pow
Click to expand...
Click to collapse
Tried that at the recovery screen but nothing responded.
also tried vol+- and +- and vol- no response from any combinations.

ah i got it to appear, it turns out that pressing the power button first instead of the volume button was an issue...
also if i do the wipedata+reset will i lose all 16 gb's of onboard storage?
and would there be a way to write/backup that data before doing so?

Here is googles support page for reset: http://support.google.com/nexus/bin/answer.py?hl=en&answer=2936226
follow these steps:
If your phone is on, power it off.
Press and hold Volume Down, and then press Power until the device turns on (while still pressing Power). You will see the word Start with an arrow drawn around it.
Press Volume Down twice to designate Recovery mode.
Press Power to restart into Recovery mode. You will see an image of an Android robot with a red exclamation mark.
While holding down Power, press Volume Up.
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it.
Scroll down to "Yes - erase all user data" and press Power to select it.
Note: If at any point during the above steps your phone becomes unresponsive, you can restart it by holding down the power button for several seconds.

hepatiit i got that to work, though what i am wondering is, will this erase all 16GB's of onboard data?

MissStabby said:
hepatiit i got that to work, though what i am wondering is, will this erase all 16GB's of onboard data?
Click to expand...
Click to collapse
Yes.

Would there be a way to backup all data over USB, from the recovery menu?
I have my photos and agenda automatically backed up, but im not sure about my contacts or installed apps.

MissStabby said:
Would there be a way to backup all data over USB, from the recovery menu?
I have my photos and agenda automatically backed up, but im not sure about my contacts or installed apps.
Click to expand...
Click to collapse
Contacts are backed up to the google servers. (can check them through GMail). Apps are also backed up to play.google.com... Note, sometimes the data isn't backed up though. Just what you've installed.
I believe a factory reset will NOT erase SDCard though. I could be wrong.
I'd say your out of luck on getting the data off. You can through recovery and ADB I think. I tried searching for the commands but I couldn't find them.

elliot.newnham said:
I believe a factory reset will NOT erase SDCard though. I could be wrong.
I'd say your out of luck on getting the data off. You can through recovery and ADB I think. I tried searching for the commands but I couldn't find them.
Click to expand...
Click to collapse
ahw shucks, the Nexus doesnt have any extended storage, it just has 16GB onboard storage, though im not sure if that is somehow a seperate entity or joined in, i looked into ADB but it requires you to have usb debugging set in advance from android.
aaaaaand now i get to also replay all the games since those savegames are gone too.... good times...

And then my phone got bricked....
after it completed the wipe i inserted the SIM card (it was in another phone)
after that the phone turned off, but now it wont respond to the power button....
now what.....

After applying some USB (charger) power and holding the on switch for a long time it finally woke up.
Now i have a blanco phone again.
Thanks for the support anyways

I had the same exact issue with my Nexus 4. When I flashed the stock image it got stuck on the X. I flashed a custom recovery and erased chase and data and it worked just fine.
I'm not sure why this is "necessary" step now when I didn't have to do do this with my Gnex but oh well.
Sent from my Nexus 4 using xda app-developers app

Root LG T-Mobile LG GPAD X 8.0 V52110c

First check oem unlock in setting>develop> go to fastboot > fastboot oem unlock.
- Download Rom add rooted: https://drive.google.com/file/d/0BwLkiuDnHmY0bTBsOG12VnBOa3c/view?usp=sharing
- LGUP 1.14.3:http://oceanhost.eu/eps4h4pmwphu/LGUP.zip.htm
- Use LGUP load file dz twrp then START.
- Done phone have rooted
Paypal: [email protected]
Thank you donate.[/B]

I will try this in the morning. I'm new to LG, how do you flash stock?
I put in $25 and will send it when I verify it works.
Thanks for the work!

Currently I am at work.
I will test it once I got home.
----- edit -----
Got soft brick on the device.
TWRP seems to work, but it is stuck on LG boot screen (The device can't be checked for corruption)
I have to open the back cover and reconnect the battery.
Since I have stock kdz file, it goes back to normal after flashing with stock kdz

mingkee said:
Currently I am at work.
I will test it once I got home.
----- edit -----
Got soft brick on the device.
TWRP seems to work, but it is stuck on LG boot screen (The device can't be checked for corruption)
I have to open the back cover and reconnect the battery.
Since I have stock kdz file, it goes back to normal after flashing with stock kdz
Click to expand...
Click to collapse
You can open a thread and put some pictures about how to open the back cover and disconnect the battery.
@tungkick, our device name is T-Mobile LG GPAD X 8.0, not 8.3. Hope those gpad 8.3 users weren't confused.

googlephone said:
You can open a thread and put some pictures about how to open the back cover and disconnect the battery.
@tungkick, our device name is T-Mobile LG GPAD X 8.0, not 8.3. Hope those gpad 8.3 users weren't confused.
Click to expand...
Click to collapse
Pry open from USB OTG port, and use a mini screwdriver to remove the battery connector.
Once you turned off this way, press and hold volume up and plug USB to enter download mode.
Run LGUP and install stock kdz file (upgrade).

mingkee said:
Currently I am at work.
I will test it once I got home.
----- edit -----
Got soft brick on the device.
TWRP seems to work, but it is stuck on LG boot screen (The device can't be checked for corruption)
I have to open the back cover and reconnect the battery.
Since I have stock kdz file, it goes back to normal after flashing with stock kdz
Click to expand...
Click to collapse
Do not know if you're having the same boot problem as me. But I did not have to remove battery to get it to reboot. I just hold all 4 buttons down for a good amount of time and device will reboot. Leave USB cord in and release all buttons then vol up to get into download mode.
Re-reading your post the same exact thing happened to me when testing with tungkick on Skype. dz seems to flash just fine but then it will not boot tablet, so no way to adb reboot recovery.

emilyrugburn said:
Do not know if you're having the same boot problem as me. But I did not have to remove battery to get it to reboot. I just hold all 4 buttons down for a good amount of time and device will reboot. Leave USB cord in and release all buttons then vol up to get into download mode.
Re-reading your post the same exact thing happened to me when testing with tungkick on Skype. dz seems to flash just fine but then it will not boot tablet, so no way to adb reboot recovery.
Click to expand...
Click to collapse
It's uneccesary to open the device to reboot it. Once you've flashed TungKicks stuff, you can Hold Volume down and Power to restart the device, then enter recovery with the key combo, then you can shut down or do whatever with the device with TWRP.
-----------------------------------------------------------------------------
So, Using the info on TungKicks' post I've flashed the device, It has TWRP, but does not boot to android. it just hangs on the dm-verity warning.
I had to use the key combo to get to recovery.
Volume Down + Power. Release power when LG logo shows up, continue to hold Volume Down. Re press power after one second.
Recovery has issues too.
-Can't wipe the device.
-nothing gets mounted.
-TWRP claims that there's no OS installed
-Upon further testing, the recovery reports itself as V510 via MTP. No beuno!
{
"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"
}

eriklion said:
It's uneccesary to open the device to reboot it. Once you've flashed TungKicks stuff, you can Hold Volume down and Power to restart the device, then enter recovery with the key combo, then you can shut down or do whatever with the device with TWRP.
-----------------------------------------------------------------------------
So, Using the info on TungKicks' post I've flashed the device, It has TWRP, but does not boot to android. it just hangs on the dm-verity warning.
I had to use the key combo to get to recovery.
Volume Down + Power. Release power when LG logo shows up, continue to hold Volume Down. Re press power after one second.
Recovery has issues too.
-Can't wipe the device.
-nothing gets mounted.
-TWRP claims that there's no OS installed
Click to expand...
Click to collapse
I didn't know how to get to recovery with key combo, everything else I knew. As for TWRP... it's a start, but I wonder what needs to be changed for it to work with this device.

emilyrugburn said:
I didn't know how to get to recovery with key combo, everything else I knew. As for TWRP... it's a start, but I wonder what needs to be changed for it to work with this device.
Click to expand...
Click to collapse
I mention the key combo for restarting the device and entering recovery.
Re: TWRP, it's probably the mounts. Not sure.

eriklion said:
I mention the key combo for restarting the device and entering recovery.
Re: TWRP, it's probably the mounts. Not sure.
Click to expand...
Click to collapse
Nice... thanks for the info. Hopefully @tungkick can fix this mount issue.

eriklion said:
-Upon further testing, the recovery reports itself as V510 via MTP. No beuno!
Click to expand...
Click to collapse
What happened here then? tungkick got confused (it is confusing) because of the model names and compile twrp wrongly from it?

I think waitting upload file root done but he network verry low. I need personal contact me i root with twrp this then backup full tot add root

Twrp this verry hard use

First check oem unlock in setting>develop> go to fastboot > fastboot oem unlock.
- Download Rom add rooted: https://drive.google.com/file/d/0BwLkiuDnHmY0bTBsOG12VnBOa3c/view?usp=sharing
- LGUP 1.14.3:http://oceanhost.eu/eps4h4pmwphu/LGUP.zip.htm
- Use LGUP load file dz twrp then START.
- Done phone have rooted

tungkick said:
First check oem unlock in setting>develop> go to fastboot > fastboot oem unlock.
- Download Rom add rooted: https://drive.google.com/file/d/0BwL...ew?usp=sharing
- LGUP 1.14.3:http://oceanhost.eu/eps4h4pmwphu/LGUP.zip.htm
- Use LGUP load file dz twrp then START.
- Done phone have rooted
Click to expand...
Click to collapse
Tot link got cut off. invalid link

emilyrugburn said:
Tot link got cut off. invalid link
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BwLkiuDnHmY0bTBsOG12VnBOa3c/view?usp=sharing
HEHE^^

tungkick said:
https://drive.google.com/file/d/0BwLkiuDnHmY0bTBsOG12VnBOa3c/view?usp=sharing
HEHE^^
Click to expand...
Click to collapse
I will test it after work.
Thanks for your hard work.

tungkick said:
https://drive.google.com/file/d/0BwLkiuDnHmY0bTBsOG12VnBOa3c/view?usp=sharing
HEHE^^
Click to expand...
Click to collapse
Flash success. Rooted :good: :highfive:
For anyone who flashes this dz. Towards the end it will hang at 100%, just let it continue and it will eventually reboot.

emilyrugburn said:
Flash success. Rooted :good: :highfive:
For anyone who flashes this dz. Towards the end it will hang at 100%, just let it continue and it will eventually reboot.
Click to expand...
Click to collapse
Root also works on mine.
No Adapt Client.
Install Adaway now

I'm getting a Boot verification fail message - Cause MISMATCH_SIG_LEN. Everything went 100% in LGUP, not sure what happened. Its just boot looping on startup screen (LG - powered by android screen)

Axon 7 bricked and I'm in a very tight situation. Any quick solution?

To sum it up quickly, I put my Axon 7 up for sale on ebay. 5 day listing. It currently has ~24 hours left on it and plenty of bidders. ZTE Gladly offered a replacement but it would take 10 or more days. I had previously rooted the phone, and wanted to send it as though it came from the factory. I went into fastboot, did 'fastboot oem lock' over the fastboot shell, and it said successful. The device "rebooted" into a black screen. The device now appears to be bricked. It will show a ZTE logo for about a second when I hold the power button and then no more. I cannot seem to get it respond to a charge, go into fastboot, recovery, or anything else except what I described. It sounds hopeless to me, but maybe someone here is a miracle worker. Thank you very much.

for starters which model to you have?

You were completely stock, not rooted before locking?

lafester said:
You were completely stock, not rooted before locking?
Click to expand...
Click to collapse
I had flashed CM to it previously but when I did a relock I had reflashed stock MiFavor found here on XDA.
Edit: TWRP official a2017u was on the device, and I may have flashed supersu as well during the stock reflash. It was almost a week ago, I can't remember.
DrakenFX said:
for starters which model to you have?
Click to expand...
Click to collapse
A2017U

erer1243 said:
I had flashed CM to it previously but when I did a relock I had reflashed stock MiFavor found here on XDA.
A2017U
Click to expand...
Click to collapse
If you can boot to recovery you can try using ZTE B20 file, look here https://www.zteusa.com/axon-7#support under SOFTWARE UPDATES
* Move that file to your SDCard ,
* Boot to your recovery and flash that file.

DrakenFX said:
If you can boot to recovery you can try using ZTE B20 file, look here https://www.zteusa.com/axon-7#support under SOFTWARE UPDATES
* Move that file to your SDCard ,
* Boot to your recovery and flash that file.
Click to expand...
Click to collapse
I cannot boot into recovery. I cannot do anything except what I described, the quick ZTE logo, and then nothing. The computer does recognize that there is a device plugged in though, but ADB and fastboot will not see it.

erer1243 said:
I cannot boot into recovery. I cannot do anything except what I described, the quick ZTE logo, and then nothing. The computer does recognize that there is a device plugged in though, but ADB and fastboot will not see it.
Click to expand...
Click to collapse
not even Manual boot to recovery?
Press & Hold Volume Up + Power till menu kicks in.
you other option booting to EDL and use @tennear or tenfar tool to flash TWRP ONLY and flash that file or my B29.MergeBootstack and StockSystem files

DrakenFX said:
not even Manual boot to recovery?
Press & Hold Volume Up + Power till menu kicks in.
you other option booting to EDL and use @tennear or tenfar tool to flash TWRP ONLY and flash that file or my B29.MergeBootstack and StockSystem files
Click to expand...
Click to collapse
Nothing happens. It will not go into fastboot or recovery, no matter what I hold, for how long, anything. I believe it is either trying to display the "Your device cannot be trusted" screen and fails or is trying to do some other thing during pre-boot and is stuck in a loop. I don't know what EDL is but I'd be willing to tear this phone a new asshole if I can fix it within 24 hours. Happy to try anything, it seems like it can't get any worse than this.

erer1243 said:
I believe it is either trying to display the "Your device cannot be trusted"
Click to expand...
Click to collapse
this means, you still UNLOCK, when you are there and i mean when that message shows up, press any of the volume key and will give you a menu, from there you can boot to recovery - fastboot - bootloader.
if you see that menu, BOOT to BOOTLOADER and tell me the status.

DrakenFX said:
this means, you still UNLOCK, when you are there and i mean when that message shows up, press any of the volume key and will give you a menu, from there you can boot to recovery - fastboot - bootloader.
if you see that menu, BOOT to BOOTLOADER and tell me the status.
Click to expand...
Click to collapse
Well I just successfully locked it before making the thread... So it is not unlocked any longer. That was just speculation. I have no menus, holding down volume buttons and power does not do anything, I cannot get into fastboot, recovery, etc at all.

erer1243 said:
Well I just successfully locked it before making the thread... So it is not unlocked any longer. That was just speculation. I have no menus, holding down volume buttons and power does not do anything, I cannot get into fastboot, recovery, etc at all.
Click to expand...
Click to collapse
you know how to manually boot to EDL? so you can use any of the tool to flash TWRP.
manually booting to EDL and to make sure is in EDL mode CONNECT your device to your PC/Laptop and open DEVICE MANAGER now just Hold & Press Vol. Up and Down and make sure you are pressing both , if you are using case take the phone out of the case so you can really do it. Once you are pressing and holding both volume keys, press Power and check Device Manager for Qualcomm Port your device is using.
after that just proceed with the rest.

Just to make it a little clearer, to go to EDL mode. Phone must be off when you connect to PC, you hold both volume up/down and then touch power. It will still remain off BUT should now be recognized by the PC's device Manager.

I was in the same situation before. Using tenfar's tool to flash tenfar's TWRP (not official TWRP) the phone will boot TWRP with a locked bootloader. Then, go https://www.zteusa.com/axon-7 there and click the Support tab, then the Software Updates subsection. Download that, it could take a while though.
Once that's done, open the update.zip in something like 7-Zip and navigate to META-INF\com\google\android and extract the file updater-script. Open it with Notepad++ (not Notepad) or, if you're not on Windows, the text editor of your choice.
{
"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"
}
On line 2, which is highlighted, delete that line. If you don't do this, it won't flash in TWRP. Don't worry though, it won't mess anything up. After saving, drag the extracted updater-script back into the zip file and confirm that you want to replace it.
Then, once your phone is in TWRP, copy the update.zip to your phone and flash it. For me, it took about 7 or 8 minutes to flash.
This part is the most important, absolutely do not skip this:
Before you reboot go back to the main TWRP menu and open the Mount menu. Uncheck system and then reboot. This is because TWRP installs a survival script in /system if it can, because otherwise TWRP will be changed to stock recovery. In this case though, it's what we want. This way OTA updates will successfully install. Stock recovery checks for any changes to /system and refuses to work if it sees any change at all, like the one TWRP makes unless you unmount system before you reboot.
After rebooting, you should update your phone from B20 to B27 and then from B27 to B29 to be up to date.
Also, this will re-lock your bootloader!
If you have any questions please ask, hopefully that helped you and maybe others too

RainofOranges said:
I was in the same situation before. Using tenfar's tool to flash tenfar's TWRP (not official TWRP) the phone will boot TWRP with a locked bootloader.
Click to expand...
Click to collapse
Maybe I just haven't looked hard enough... but I can't find any working instructions on how to flash/boot to a recovery. When I go by his instructions, nothing seems to work. I have, in the same folder as axon7root.exe, a recovery.img that is tenfar's twrp release. I have installed the driver he linked. I run axon7root -p 4 -r (yes, my phone is connected to the COM4 port) and the program just prints his little copyright splash screen and nothing happens. I have left it for ~half an hour, so it's obviously not just taking it's time. When I unplug the phone, it tells me my horse is dead (lmao someone get on translation) so it obviously knows the phone is there, but it just cannot do anything. Also, I cancelled the ebay listing a few minutes before seeing your post, disappointingly. Hopefully I can revive my horse and relist it.

erer1243 said:
Maybe I just haven't looked hard enough....
Click to expand...
Click to collapse
Are you sure your phone is in EDL mode? Did you try running it through a command promp as Administrator?

RainofOranges said:
Are you sure your phone is in EDL mode? Did you try running it through a command promp as Administrator?
Click to expand...
Click to collapse
I will try running it as admin. I am unsure how to tell if my phone is in EDL mode. I have reason to believe that it is stuck in a silent boot loop and maybe I can't get it into EDL/any other mode but I am just speculating there. I think that because 1, it won't respond to a charge and 2, I have to hold down the power button much longer than usual to make the ZTE logo pop up; It's as though I had to force shut down the phone and then boot it again in the 1 press.

erer1243 said:
Maybe I just haven't looked hard enough... but I can't find any working instructions on how to flash/boot to a recovery. When I go by his instructions, nothing seems to work. I have, in the same folder as axon7root.exe, a recovery.img that is tenfar's twrp release. I have installed the driver he linked. I run axon7root -p 4 -r (yes, my phone is connected to the COM4 port) and the program just prints his little copyright splash screen and nothing happens. I have left it for ~half an hour, so it's obviously not just taking it's time. When I unplug the phone, it tells me my horse is dead (lmao someone get on translation) so it obviously knows the phone is there, but it just cannot do anything. Also, I cancelled the ebay listing a few minutes before seeing your post, disappointingly. Hopefully I can revive my horse and relist it.
Click to expand...
Click to collapse
Mine did that - unplug phone, restart computer, hold both volume buttons and plug phone back in.

erer1243 said:
I will try running it as admin. I am unsure how to tell if my phone is in EDL mode. I have reason to believe that it is stuck in a silent boot loop and maybe I can't get it into EDL/any other mode but I am just speculating there. I think that because 1, it won't respond to a charge and 2, I have to hold down the power button much longer than usual to make the ZTE logo pop up; It's as though I had to force shut down the phone and then boot it again in the 1 press.
Click to expand...
Click to collapse
You can't tell that the phone is in EDL mode on the phone itself. You can only tell by trying the tool. If I remember right the button combination to get into EDL mode is both volume buttons held down and the power button also held down for 2 seconds or so at the same time.

tabletalker7 said:
Mine did that - unplug phone, restart computer, hold both volume buttons and plug phone back in.
Click to expand...
Click to collapse
No dice. As admin, computer restarted, I tried holding both volume buttons while plugging in.

update from my last post: I got tenfar's tool to upload his TWRP to the phone (sent it to the horse o.o) but it still will not boot anywhere. The phone has not changed at all.

Update to 6.1 "broke" my Shield. I only get "No command" and cannot get to fastboot

Update to 6.1 "broke" my Shield. I only get "No command" and cannot get to fastboot
Hi!
This patch broke my Shield :\ I was cooking when it was updating and when i came back there was picture of Android guy and text "No Command"
{
"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"
}
What to do now?
I have Shield (2015) 16gb model and not rooted. Version is one behind 6.1.
When i plug the power on Shield starts automatically and then comes the Nvidia logo (no Google logo at all) and after a while comes the Droid lying down with hatch opened and "No Command" displayed on the screen. Sometimes it stays on that and sometimes it bootloops. Here is an video of the boot
I found info that i should get into fastboot but i have tried to without success :\ I have tried the press power button after putting power cable on about 40-60 times without success and tried the press A and B button of Controller during the boot 10-20 times (i am not sure if it's for this version of Shield though)
So what can i do to get my Shield working again? :]

DARKKi said:
Hi!
This patch broke my Shield :\ I was cooking when it was updating and when i came back there was picture of Android guy and text "No Command"
What to do now?
I have Shield (2015) 16gb model and not rooted. Version is one behind 6.1.
When i plug the power on Shield starts automatically and then comes the Nvidia logo (no Google logo at all) and after a while comes the Droid lying down with hatch opened and "No Command" displayed on the screen. Sometimes it stays on that and sometimes it bootloops. Here is an video of the boot
I found info that i should get into fastboot but i have tried to without success :\ I have tried the press power button after putting power cable on about 40-60 times without success and tried the press A and B button of Controller during the boot 10-20 times (i am not sure if it's for this version of Shield though)
So what can i do to get my Shield working again? :]
Click to expand...
Click to collapse
pull all the plugs from Nvidia shield for about 30 min then plug in hdmi and power and hold power button until its on recovery screen

jionny said:
pull all the plugs from Nvidia shield for about 30 min then plug in hdmi and power and hold power button until its on recovery screen
Click to expand...
Click to collapse
A Shield Pro arrived yesterday, plugged in and it started to update. Got about 10-15% of update download, went to black screen, and would not 'hard reset' afterwards. Nvidia says send it back.
Another Pro is arriving tomorrow. Almost afraid to touch.

The following video may help you in the process of booting into fastboot or bootloader mode and teach you how to flash .img files via fastboot. I made the video and a 2015 16gb Nvidia Shield TV model was used.
PS: You need to download nvidia recovery image (firmware) for your specific device model from Nvidia's website but DO NOT use flash-all.bat or flash the .bin file manually, there's no need and should be avoided because that's the bootloader and you really don't wanna mess with that. You've been warned!, otherwise you may hard brick it.
https://developer.nvidia.com/gameworksdownload
https://youtu.be/LQaYb4oVHVc
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player

jionny said:
pull all the plugs from Nvidia shield for about 30 min then plug in hdmi and power and hold power button until its on recovery screen
Click to expand...
Click to collapse
This does not work either, tried 20+ times :\
lavero.burgos said:
The following video may help you in the process of booting into fastboot or bootloader mode and teach you how to flash .img files via fastboot. I made the video and a 2015 16gb Nvidia Shield TV model was used.
PS: You need to download nvidia recovery image (firmware) for your specific device model from Nvidia's website but DO NOT use flash-all.bat or flash the .bin file manually, there's no need and should be avoided because that's the bootloader and you really don't wanna mess with that. You've been warned!, otherwise you may hard brick it.
https://developer.nvidia.com/gameworksdownload
Thanks for all the guides! But it seems i cannot get into fastboot
https://youtu.be/LQaYb4oVHVc
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
JeffDC said:
A Shield Pro arrived yesterday, plugged in and it started to update. Got about 10-15% of update download, went to black screen, and would not 'hard reset' afterwards. Nvidia says send it back.
Another Pro is arriving tomorrow. Almost afraid to touch.
Click to expand...
Click to collapse
Hopefully this wont happen to me, i fear the worst :\

If you're trying to boot into fastboot mode on a 4k tv then try in a 1080p tv or monitor. That would be the last think i could think of and shield tv's power source, but in that case the shield wouldn't even power on in first place.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player

Okay, i finally got into the fastboot menu and did full wipe / factory reset but i still got the same lying droid with "no command"
How to proceed from here? :]

Hi.
I know it is very frustrating trying to go to bootloader mode and not be able to.
I was only able to go into bootloader mode AFTER using the default USB cable that came on the box AND connecting it to the PC. Without those 2 conditions my shield never go into bootloader.
You can read my post where I explain how I did solve my firmware corruption here
Anyway if were able to go to bootloader you can follow nvidia steps to recover your shield.
Good luck
DARKKi said:
Hi!
This patch broke my Shield :\ I was cooking when it was updating and when i came back there was picture of Android guy and text "No Command"
What to do now?
I have Shield (2015) 16gb model and not rooted. Version is one behind 6.1.
When i plug the power on Shield starts automatically and then comes the Nvidia logo (no Google logo at all) and after a while comes the Droid lying down with hatch opened and "No Command" displayed on the screen. Sometimes it stays on that and sometimes it bootloops. Here is an video of the boot
I found info that i should get into fastboot but i have tried to without success :\ I have tried the press power button after putting power cable on about 40-60 times without success and tried the press A and B button of Controller during the boot 10-20 times (i am not sure if it's for this version of Shield though)
So what can i do to get my Shield working again? :]
Click to expand...
Click to collapse

Hugonow said:
Hi.
I know it is very frustrating trying to go to bootloader mode and not be able to.
I was only able to go into bootloader mode AFTER using the default USB cable that came on the box AND connecting it to the PC. Without those 2 conditions my shield never go into bootloader.
You can read my post where I explain how I did solve my firmware corruption here
Anyway if were able to go to bootloader you can follow nvidia steps to recover your shield.
Good luck
Click to expand...
Click to collapse
Thanks a lot! Nvidia had changed those guides since there was no mention of plugging in OTG Cable before to enter fastboot.
Got it working! Thanks a lot for this, i thought my shield was a goner for a moment :crying:

Nokia 6 stuck in boot loop

My Nokia 6 (TA-1021) got stuck in boot loop.
Every time i power on the device it gets to the screen that says "Powered by android" and keeps rebooting.
It also shows "shutdown device" on top. How can i get into recovery mode ??
i tried using power + volume up key but it keeps entering the boot loop..
i even tried using adb but as the device is not starting it shows "error: no devices/emulators found".
{
"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"
}

https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
walkn911 said:
My Nokia 6 (TA-1021) got stuck in boot loop.
Every time i power on the device it gets to the screen that says "Powered by android" and keeps rebooting.
It also shows "shutdown device" on top. How can i get into recovery mode ??
i tried using power + volume up key but it keeps entering the boot loop..
i even tried using adb but as the device is not starting it shows "error: no devices/emulators found".
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441

Mine is also so, if you managed to solve please help.
Mine is also so, if you managed to solve please help.

igorbm2010 said:
Mine is also so, if you managed to solve please help.
Click to expand...
Click to collapse
If you know how to flash MENA FIRMWARE then when your pc ask you to connect your device to OST LA tool then plug it, next time when your device will reboot then it will directly go to download mode and hence u could be able to flash your device

sltushar said:
If you know how to flash MENA FIRMWARE then when your pc ask you to connect your device to OST LA tool then plug it, next time when your device will reboot then it will directly go to download mode and hence u could be able to flash your device
Click to expand...
Click to collapse
My phone is also stuck in boot loop and i tried flashing using OST LA but it always shows error.Error detaıls:-
Error code : 0xc6da
Error : Download fails,
Error = SE_ERR_ADB_CMD_GET_FAIL_RESULT (0xC6DA)

Can you enter recovery? What's the recovery version? Have you tried to upgrade to Oreo when bootloop happened?

qwertysmerty said:
Can you enter recovery? What's the recovery version? Have you tried to upgrade to Oreo when bootloop happened?
Click to expand...
Click to collapse
no can't enter into recovery. The phone is already updated to Oreo. And now when i tried to install stock version its stuck in boot loop and shows these error messages when i tried to flash using OST LA.

That's sad since you already have oreo sbl/aboot and cannot enter recovery to downgrade it. I think you have 2 options - either go to service center, or open up your phone to short test point and enter edl mode, but you will lose warranty if you have one.

qwertysmerty said:
That's sad since you already have oreo sbl/aboot and cannot enter recovery to downgrade it. I think you have 2 options - either go to service center, or open up your phone to short test point and enter edl mode, but you will lose warranty if you have one.
Click to expand...
Click to collapse
How to open to short test point and enter edl mode? Thanks in advance.

barun777 said:
no can't enter into recovery. The phone is already updated to Oreo. And now when i tried to install stock version its stuck in boot loop and shows these error messages when i tried to flash using OST LA.
Click to expand...
Click to collapse
Apparently the process to access Recovery Mode changed from Oreo beta to Oreo stable, at least for the TA-1025:
Phone model: Nokia 6 TA-1025
Android version: 8.0.0 (Oreo, stable)
Android security patch level: February 1, 2018
Build number: 00WW_5_22A
Power off your phone.
Connect your phone to a charger.
"POWERED BY android" logo will appear, followed by the battery charging screen.​
[*]Hold VOLUME UP + POWER BUTTON for 10 seconds, release.​
During the 10 seconds, your phone will power cycle, followed by the "POWERED BY android" logo, followed by an image of Bugdroid (Android robot) with the text "no command".​
If you see the the NOKIA logo instead of Bugdroid, you released VOLUME UP + POWER BUTTON too early or too late. Start over.​
From the "no command" screen, hold POWER BUTTON, tap VOLUME UP, release POWER BUTTON. This should take you into Recovery Mode.
Credit to CJShawnz

I faced same problem.i was lucky as i could change it guving 30$ to store to change it.

MisterNeato said:
Apparently the process to access Recovery Mode changed from Oreo beta to Oreo stable, at least for the TA-1025:
Phone model: Nokia 6 TA-1025
Android version: 8.0.0 (Oreo, stable)
Android security patch level: February 1, 2018
Build number: 00WW_5_22A
Power off your phone.
Connect your phone to a charger.
"POWERED BY android" logo will appear, followed by the battery charging screen.​
[*]Hold VOLUME UP + POWER BUTTON for 10 seconds, release.​
During the 10 seconds, your phone will power cycle, followed by the "POWERED BY android" logo, followed by an image of Bugdroid (Android robot) with the text "no command".​
If you see the the NOKIA logo instead of Bugdroid, you released VOLUME UP + POWER BUTTON too early or too late. Start over.​
From the "no command" screen, hold POWER BUTTON, tap VOLUME UP, release POWER BUTTON. This should take you into Recovery Mode.
Credit to CJShawnz
Click to expand...
Click to collapse
Its not working. phone is not gong into the ''no command''. Its stuck in boot-loop.

barun777 said:
Its not working. phone is not gong into the ''no command''. Its stuck in boot-loop.
Click to expand...
Click to collapse
Just put it somewhere and let the bettery be low and then let it properly shutdown
Then put it to charge
Then try to enter to recovery mode
Remember you will have one chance only
Don't power on your device, just follow the steps to enter to the recovery menu, because power on will put u again to boot loop.

sltushar said:
Just put it somewhere and let the bettery be low and then let it properly shutdown
Then put it to charge
Then try to enter to recovery mode
Remember you will have one chance only
Don't power on your device, just follow the steps to enter to the recovery menu, because power on will put u again to boot loop.
Click to expand...
Click to collapse
I have already tried this method. Its not working. Actually I can power off the phone by pressing vol + and vol - buttons together. Boot-loop stops and the phone shutdowns but the navigation LEDs remains in the ON state.

barun777 said:
How to open to short test point and enter edl mode? Thanks in advance.
Click to expand...
Click to collapse
Are you sure you want to do this? You can break your phone. It might be easier to send it to the nearest Nokia service center.
You can find a video on youtube about how to tear down Nokia 6 (JerryRigEverything channel). You need to remove screen and battery plate. Then connect back battery and screen cables. Power up your phone and short test point while phone boots. It should enter EDL mode so you can use whatever flasher. Personally I would just flash sbl/aboot/recovery partitions with images from Nougat using emmcdl. Something like this:
emmcdl -p COM3 -f prog_emmc_firehose_8937_lite.mbn -b recovery recovery.img
where COM3 is the assigned port name. Programmator prog_emmc_firehose_8937_lite.mbn you can take from any Nougat OTA zip, as well as recovery, appsboot, and sbl images.

Did you ever get this sorted? Mine is doing same, OST won't recognise it, keeps saying process failed error = SE_ERR_SUT_PHONE_KEY_ACCESS_FAIL (0xC60E)

Same problem my phone but i go store return my phone he says no solution i am very sad please help us plssss