Database Users

[Q] Nexus stuck on 'X' screen, even after full wipe

So, a few days ago, I started having some problems with my stock Nexus 7 (not unlocked, no ROMs or anything like that). Some apps just wouldn't open, they would force close within a second of opening. Anyway, I think it might have stemmed from the game "Let's Golf 3", as problems started after playing that, and when going back in to it after a day of issues, a message appeared saying "Unfortunately, launcher has stopped" - it gave me the option to report or cancel, but whatever I pressed, the message popped back up. I pressed the sleep button, which seemed to turn my Nexus off somehow.
Then, when trying to to turn my Nexus back on, it just stays on the 'X' screen. I have done a factory wipe through the fastboot menu a few times, but it still stays stuck on the 'X' screen. To turn it off, I hold down the power button, but it just starts the process again automatically. The only way to actually turn the device off is through the fastboot menu.
I have seen talk of 'factory image' and drivers etc... but I am not too comfortable with that sort of thing. I know the basics of troubleshooting devices, but not much more. I am very wary of doing anything more than what the device provides me with.
Any idea how I can get my Nexus started, or am I going to have to look for a replacement?

If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.

Leonhan said:
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Click to expand...
Click to collapse
Is that not for rooted devices?

Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?

AW: [Q] Nexus stuck on 'X' screen, even after full wipe
Gawge said:
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
Click to expand...
Click to collapse
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1

mihahn said:
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I too had the same problem. Tried everything. Finally gave it to ASUS service centre in Nehru Place. They will replace the mother board. May take 15 more days. So sad!

Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus

Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
FYI,
The tablet can "play possum" when it is in APX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown APX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.

bftb0 said:
FYI,
The tablet can "play possum" when it is in AVX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown AVX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
Click to expand...
Click to collapse
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?

Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
Service centre seems to be the only solution. My sympathies!

Gawge said:
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Click to expand...
Click to collapse
Call Asus first. Make sure to let them know it is less than 2 months old. If they want you to perform the return through the original retailer, they will tell you. But it's best to eliminate any other middlemen if that is possible, as I suppose that the tablet ultimately goes back to Asus anyway.
(Might be different through other channels, e.g. PlayStore - I dont know).

[Q] Is it possible to retrieve files from N7 whilst dead/bricked?

Hi all
Apologies at coming on here and immediately asking for help, but....
I've had my Nexus 7 since July and have been very happy until NOW!
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
I've tried all the methods of long push of buttons/multiple buttons/etc but to no avail.
I can bring up the factory restore option so I know I can get it working again, but....
I have an exam in a week which foolishly had work stored for on my n7 without back up (yes fool) so....
Please is there anyway to retrieve my files via PC etc before factory resetting
All help genuinely appreciated
Mark

rooted vs unrooted (or unlocked bootloader even if not rooted) makes a huge difference in the answer.
Please state which.

Sorry about that
Not rooted.
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark

pleading said:
Sorry about that
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
Click to expand...
Click to collapse
I believe you are SOL in that case. Sorry.

Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Sent from my Nexus 7 using xda app-developers app

bigbop said:
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Click to expand...
Click to collapse
pleading mentions the battery, but then says "stalls" - not "shuts down", which is what you might expect if the battery was drained:
pleading said:
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
Click to expand...
Click to collapse
But, bigbop could be correct if pleading meant "low battery shutdown"
One other very long shot - assuming that that the device is hung - is to see if either adb or MTP are available. Normally that happens very late in the boot & I have to imagine that he has already tried that though.

Hi again guys
Firstly thanks for not giving up on my situation!
Bad explanation by me I guess....
The battery went flat/dead (my bad)
Plugged in to charge and screen lit up again but showing the 'powering off' script
Left over night on charge, wouldn't switch on again next morning
Left on charge all day still no joy but if I try switching on whilst plugged in I first get the Google name, then the Google X but then gets 'hung' (probably a better description than freezes etc as it still pulsates the colours)
Only way to get out of this is to keep power button pressed which switches n7 off and starts the cycle again
If during the recycle I keep the volume down pressed then it accesses the option screen to recover/reboot etc
Hope this helps, and again thanks (desperate to recover course work)
Mark

Hi again
Update...
Battery is showing full now
But still same 'hung' situation
Regarding the 'ADB'
I can get to the 'apply update from ADB' option
And if I choose it states.... 'now send the package you want to apply to the device with "adb sideload <filename>"'
As always thanks for any help or suggestions
Mark

Mark,
It sounds to me like what you are describing is ADB in the stock recovery, not a ADB when the regular operating system is running. (Is that right?)
Unfortunately, the stock recovery is only good for 2 things: applying an OTA update, and doing a factory reset. Even if your tablet needed an OTA update (and it probably doesn't if it is up to date), it probably wouldn't fix the looping/wedged phenomenon: usually that is caused by stuff in the userdata partition.
Doing the stock recovery factory reset might cure the wedged/looping problem - but only if it wipes all the data from your tablet. (Including the /sdcard area too).
The only hope I held out was if your tablet was reachable via a ADB or MTP with the wedged operating system sitting there looping. Usually those facilities start up quite late in the boot sequence, however so probably you don't have that.
Sorry. I think you are still SOL when it come to retrieving files.

Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all

pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
I had same sort of problem N7 went flat tried to charge but would not power on
Took back panel off and disconnected battery for 10 mins reconnected battery and put back on charge
it then booted up as normal

pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
Uhhh ... what?
The OP was about a tablet that you couldn't get into because
[a] it had a correctable soft-fault
you didn't want to exercise an available soft-fault recovery method because of a desire to reclaim user files not backed up
... and so far as we know the soft-fault recovery mechanism still is available to you.
How did that morph into "this is the end"?
You need to re-do your homework, perform a factory reset, and move on with your life.
You have used either software or hardware in the past haven't you? That thing isn't a toaster or a waffle-iron! No backups of important stuff? Come on!
OK, well then. Pack it up and send it to me with the charger and I'll pay for the shipping - UPS ground.

Doesn't the Nexus have a safe-boot mode?
Sent from my Nexus 7 using xda app-developers app

bigbop said:
Doesn't the Nexus have a safe-boot mode?
Click to expand...
Click to collapse
Just tried right now - held the Vol-down button down continuously from about 2 secs after the Google B&W splash screen appeared until the lock screen appeared. That worked. (Stock 4.2.2)
"Safe mode" appears in the lower left corner. I had access to all the market apps (that I tried), but did not see a toast notification from StickMount after the boot - suggesting that safe mode only inhibits apps from starting on boot.
I suppose this could work (although the OP's deadline has probably come and gone) for bypassing a hung boot - but only if the hang is due to a market app that normally starts on boot.

Hard bricked nexus 4 help please?

So last night I hard bricked my nexus 4. its rooted, with cyanogenmod 10.1 ROM, and ive never had any issues with this phone. I have no idea what happened, but I sent a text message to someone, and it powered itself down. it was fully charged when this happened, so I know its not the battery. ive done some research, and its a true hard brick. no bootloader, no recovery, I just get a red/orange flashing light if I hold down the power button. google said im still under warranty, and they will still replace it even with it being rooted. My question is, is it possible to fix without having to get a replacement, or JTAG? If anyone has had any success, please help.
And like I said, I was only sending a text. I have no idea why it bricked, it restarts itself once in a while randomly, but this time it didn't turn back on.

Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?

exb0 said:
Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?
Click to expand...
Click to collapse
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.

sinndissension said:
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.

exb0 said:
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.
Click to expand...
Click to collapse
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?

sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
Nope. It's different.

sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
You can compare it too fastboot mode.

gee2012 said:
You can compare it too fastboot mode.
Click to expand...
Click to collapse
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.

sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
Did you press volume down first and then the power button both for a few seconds to get into fastboot mode?

Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, or the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone knows of that I didn't just list, my last option is JTAG.

sinndissension said:
yep. ive done EVERY combination of holding down the buttons, no response. when I plug it in to a laptop, the laptop beeps, like the USB connection sound, but the nexus doesn't show up on the computer. I know the computer recognized what kind of phone it was, cuz the first time I plugged it in, I got a pop up message saying "installing qualcom drivers", or along the lines of that. other than that, NOTHING has worked. If theres ANY fix for this, id like to give it a try, cuz ALL my stuff is on there.
Click to expand...
Click to collapse
Try charging it for a while and try again in a few hours or better yet tomorrow. Sometimes that helps bro. If that doesn`t help you`ll have to take it in for repair an maybe they can salvage your data if they are wiiling to do that. Good luck.

I think it's just your battery(RLOD) instead of a brick.
See this:
http://forum.xda-developers.com/showthread.php?t=2250454
I wouldn't be worried about your files stored on your phone because I think Google has more work to do than search in peoples pictures. What I would worry about is your warranty since you have a custom rom, unlocked bootloader and root...
Sent from my Nexus 4 using xda app-developers app

Well, found out it WAS a hard brick. Google replaced it with my warranty. For some reason they returned my money before I even got the chance to send the broken nexus 4 back. Didn't even mail it. So I'm assuming I don't have to send it back. So I'm gonna JTAG the hard bricked nexus, and hopefully it'll work again.
Thanks everyone for your help.

sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
You may not be doing it right. When I get the flashing light on mine it means I forgot to let go of the power button fast enough. When it vibrates, let go of power button immediately but keep pressing the volume. Does your phone vibrate a few seconds prior to the flashing light?
Sent from my GT-P7510 using xda app-developers app

Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.

sinndissension said:
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.
Click to expand...
Click to collapse
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?

Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted

Mashed_Potatoes said:
Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted
Click to expand...
Click to collapse
ok...that has nothing to do with a hard brick. That just means your phone was dying.

dominiqueovalle said:
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?
Click to expand...
Click to collapse
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?

sinndissension said:
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?
Click to expand...
Click to collapse
its a hard brick. ive tried it all bought a new battery installed it etc. ive looked up jtag and i have the money but idk if i should do it. do you recomend it? i have no experience doing anything like it and im planning on getting the iphone 6 in the fall but i cant stand not having a phone till then especially since high school starts soon.
But the reason im sure its a hard brick is cuz when it shut down the battery was like 50 and charging and it froze for 25 seconds or so then shut down and refuses to boot or show any signs of life now except a blinking or solid red light but its not the red light of death because i replaced the battery therefore i came to the conclusion that it is hard bricked.
i know ive said alot of unecessary information but my question is do you think i should buy the jtag thing? do you reckon its easy to do? or maybe i could pay an experienced professional to do it?
thanks for the reply btw

Can't hardware boot into fastboot.

I think I'm bricked. My shield is stuck in a simple bootloop and should be considered a softbrick. I can't seem to get into fastboot. Forget adb, that's not responding, but I'm still getting the android boot logo. I've tried so many ways. Holding the button, mashing the bettenbetter, plugging at the brick, power at the console, just about everything. Anyone figure out how to get into fastboot with hardware? If so, please let me know or I'll be throwing this out. It just won't seem to respond to fastboot. Such a shame.
EDIT: Android figured it out somehow and just booted, but I'd still like to know how to get into fastboot for when I'm not so lucky next time. Or any other way to get into recovery.
EDIT 2: Thought I posted this in troubleshooting. My mobile data was lagging somethinf fearce. Sorry.

It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"

baileyjr said:
It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"
Click to expand...
Click to collapse
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.

kdb424 said:
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.
Click to expand...
Click to collapse
It certainly doesn't help that there isn't a physical button on the Sheild, so your not absolutely sure your pressing in the right place after re-inserting the power cable.

In my experience the whole button is sensitive, bit that's still a pain. I have no problems booting my phone to recovery or fastboot, but that's just nuts. Oh well. Hopefully teh learned something as I'm sure their techs are complaining too. It is a consumer device, so I guess I can't be too mad, but still, they expect us to reflash before an RMA when needed sometimes, and that's not fair to ask with thes device lol.

I have the same issue here. I was able to get in fastboot hardware wise a bunch of times before. Now I think the device is done. I've tried every combination. What's weird is I did get a flicker of the bootloader continuing once. What could have changed that the bootloader is not responding anymore? How did you get lucky, let it sit there loading for a day? I've tried to see if fastboot commands can reboot the bootloader when I plug it in timing it correctly. So frustrating.

Yesterday from many many trying times I did it only once and don't wanna go cross again and don't ask me how I don't know how and still don't know how. I did everything by "book/instructions" finally give up and just randomly (panicly ) pressing / holding finger on it, power on / off...and then somehow bootloader screen appear. That should be fix by Nvidia
Sent from my SM-G925K using XDA Free mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:49 AM ----------
I hope some developers out there will create some magic solution how enter easily in bootloader mode, like using micro sd ports some modded scripts or usb ports where in plugged in mode console entering bootloader mode or recovery etc.
Sent from my SM-G925K using XDA Free mobile app

Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.

mow4cash said:
Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.
Click to expand...
Click to collapse
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.

kdb424 said:
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.
Click to expand...
Click to collapse
Same here - finally haotic random pressing / unplugging and at the end done only once
Sent from my SM-G925K using XDA Free mobile app

Im also in the same boat
Just tried to flash stock 2.1 and Full android 2.1 and now the shield wont boot into anything
Im trying the hardware bootloader method but thats not working so far.........ive just unplugged everything, and giving it a while before i keep trying.........i suspect i might have to try rma......that'll be fun...........(im implying, that it wont)

Same here, mine is stuck on on screen and stating production fused , and couple of options like recovery kernel forced recovery, none works fallowed nvidia instructions , tried downloading SDKS And followed commands nothing working , as well tried holding power button , and unplugging and nothing works, I will try what you guys did and see maybe I get lucky somehow

I have a Shield TV power device but the screen is black and I can not go to the Hardw
I have a Shield TV power device but the screen is black and I can not go to the Hardware Bootloader Access:crying::crying::crying:

Same here - when I plug int he power the green light comes on for about half a second then goes off.
Quite infuriating really.

I get a screen that sasys "continue booting..." and then it loads normally do I need to let go once it says this or should I continue to hold?

need urgent help

My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help

xgerryx said:
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
Click to expand...
Click to collapse
To me that looks like a HW issue!

xgerryx said:
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
Click to expand...
Click to collapse
Flash it back to normal factory built
Sent from my IN2023 using Tapatalk

Bad turns to worse. Now stuck in crashdump mode, can't get into edl. Pretty screwed right now

xgerryx said:
Bad turns to worse. Now stuck in crashdump mode, can't get into edl. Pretty screwed right now
Click to expand...
Click to collapse
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.

FreshlyBaked 420 said:
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
Click to expand...
Click to collapse
I can't get edl mode to stick. Once I release the volume buttons after it's plugged in it just reboots. Won't stay in edl so I can't use the msm tool.
Tried both USB 2 and 3 ports, no difference. Could be a driver thing but nothing I've tried has enabled me to update the qc drivers. Can't get the ones built into the phone obviously.
Nothing is backed up.
So now holding volume up and down and then connecting to PC just brings up fastboot every time. Not even recognizing the driver anymore in device manager.

Update....finally got back into the OS after hours of trying things. Ended up flashing all the img files manually and booting back up. Hugeeeeeee issues. See pictures. The phone is going back.

xgerryx said:
Update....finally got back into the OS after hours of trying things. Ended up flashing all the img files manually and booting back up. Hugeeeeeee issues. See pictures. The phone is going back.
Click to expand...
Click to collapse
That appears to be a loose flex cable to the screen. Shame it can't just be popped back in. Careful when sending it back as they may look at it and suggest it's been dropped (not saying you have) I've worked in the mobile industry in my younger years and we would certainly query this is it came into our shop.
Hopefully they take it in and deal with it, give you a brew device.
Certainly wouldn't be happening pal.

dladz said:
That appears to be a loose flex cable to the screen. Shame it can't just be popped back in. Careful when sending it back as they may look at it and suggest it's been dropped (not saying you have) I've worked in the mobile industry in my younger years and we would certainly query this is it came into our shop.
Hopefully they take it in and deal with it, give you a brew device.
Certainly wouldn't be happening pal.
Click to expand...
Click to collapse
It's funny you say that something could be loose, I have no idea how. I've only had that replacement device for about 2 months and I've never even tossed it in something other than the bed or a chair, normal handling of a device, let alone dropped it. I hope they deal with it though, between the screen and the extreme overheating I wouldn't doubt that something is fried at this point. There's not a scratch on the device.
Waiting for them to send an email about the repair so I can send it back.

xgerryx said:
It's funny you say that something could be loose, I have no idea how. I've only had that replacement device for about 2 months and I've never even tossed it in something other than the bed or a chair, normal handling of a device, let alone dropped it. I hope they deal with it though, between the screen and the extreme overheating I wouldn't doubt that something is fried at this point. There's not a scratch on the device.
Waiting for them to send an email about the repair so I can send it back.
Click to expand...
Click to collapse
Well the overheating could have been a poor contact with the heatsink (more than likely)
The loose connection if it is that won't be your daily as they should clip in, if this is a refurb then that's probably your answer.
It's a weird one but you've just got to roll the dice mate..
All the best of luck with it..
If you can, try to talk to a tech from OnePlus about it.
Get some clarity if possible.

FreshlyBaked 420 said:
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
Click to expand...
Click to collapse
I have persist.img backed up, but bootloader is locked as I tried to msm.
Anyway to flash it?

areyouanand said:
I have persist.img backed up, but bootloader is locked as I tried to msm.
Anyway to flash it?
Click to expand...
Click to collapse
Check out this thread about the persist.img
https://forum.xda-developers.com/on...de-fix-persist-img-loss-finger-print-t4125909