I tried to flash a custom ROM on my Nexus but since then the phone will not start up.
If I try to boot normally, the screen flashes for a second, I get a quick buzz of haptic feedback, then the "Home" and "Search" buttons light up, then the "Back" button, and then the "Settings" button lights up and stays lit. Sounds weird but this is true.
If I try to boot into the bootloader, the "Search" and "Home" buttons light up and stay on, but nothing appears on the screen.
Annoyingly, fastboot picks up the serial number of the phone, but it can do nothing else. oem unlock is unresponsive, the three dots come up and the cursor flashes, though it at least gets past the "waiting for device" stage. If I try issue oem lock, it reports that the phone is already locked so Johnny 5 is somewhat alive.
adb doesn't recognise the phone at all, I tried on mac, WinXP, W7, and linux for good measure.
Superboot also reports that the phone is locked so no luck there.
I hope I'm not covering old ground here, any help would be greatly appreciated.
What custom ROM did you flash? What is your phone model?
Of course ADB wouldn't recognize your phone. ADB requires the phone to be on.
The only thing that would detect would be "fastboot devices" in bootloader mode.
Are you able to get into recovery mode?
And your phone is not bricked. Stop using that term. There hasn't been a report of a brick for the Nexus S unless the user has flashed a ROM that isn't for their phone via Odin or whatever.
I don't know... if he doesn'tget that Google and lock or unlock screen he might be a first one.
Did you try the volume up and then hold power to boot? It should go into fastboot menu. If that doesn't than you are first to brick it. Must have been faulty from the beginning though.
Sent from my Nexus S 4G using XDA App
Take out the battery and hold the power button for 20 seconds
Uncle Jimmy says hello
zephiK said:
What custom ROM did you flash? What is your phone model?
Of course ADB wouldn't recognize your phone. ADB requires the phone to be on.
The only thing that would detect would be "fastboot devices" in bootloader mode.
Are you able to get into recovery mode?
And your phone is not bricked. Stop using that term. There hasn't been a report of a brick for the Nexus S unless the user has flashed a ROM that isn't for their phone via Odin or whatever.
Click to expand...
Click to collapse
I believe I can use that term if the phone does not boot into recovery, which, to answer your question, and to re-iterate what I already said, it doesn't.
I don't have the other details you asked but I will post again later with them.
snandlal said:
Take out the battery and hold the power button for 20 seconds
Uncle Jimmy says hello
Click to expand...
Click to collapse
Can't just now, but I will give it a go later, thanks.
obsanity said:
I don't know... if he doesn'tget that Google and lock or unlock screen he might be a first one.
Did you try the volume up and then hold power to boot? It should go into fastboot menu. If that doesn't than you are first to brick it. Must have been faulty from the beginning though.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Absolutely, I am getting the feeling it's a faulty handset too. No, it doesn't boot into fastboot, or normally either, the screen is completely blank.
No-one has seen this behaviour where the buttons along the bottom of the screen light up when you try to boot the phone? I concede that this is a very rare thing to happen to a Nexus S, but it seems strange that nobody has seen or heard of it before?
I'm sorry I didn't fully understand. It doesn't boot into fastboot but it picks up the serial number? Have you tried flashing a recovery through fastboot?
culberto said:
Absolutely, I am getting the feeling it's a faulty handset too. No, it doesn't boot into fastboot, or normally either, the screen is completely blank.
No-one has seen this behaviour where the buttons along the bottom of the screen light up when you try to boot the phone? I concede that this is a very rare thing to happen to a Nexus S, but it seems strange that nobody has seen or heard of it before?
Click to expand...
Click to collapse
In your OP post you said,
Annoyingly, fastboot picks up the serial number of the phone, but it can do nothing else. oem unlock is unresponsive, the three dots come up and the cursor flashes, though it at least gets past the "waiting for device" stage. If I try issue oem lock, it reports that the phone is already locked so Johnny 5 is somewhat alive.
Click to expand...
Click to collapse
But yet you can't get into the bootloader mode? I'm confused.
If you want us to help you, you have to be as precise and clear as you can.
zephiK said:
In your OP post you said,
But yet you can't get into the bootloader mode? I'm confused.
If you want us to help you, you have to be as precise and clear as you can.
Click to expand...
Click to collapse
I think he means that if you do "fastboot devices" it comes up with a number. That means there is some hope.
Did you try flashing with Samsung's exe? You have to know which model you got.
zephiK said:
In your OP post you said,
But yet you can't get into the bootloader mode? I'm confused.
If you want us to help you, you have to be as precise and clear as you can.
Click to expand...
Click to collapse
Fastboot reports the serial number okay, but when I turn the phone on holding the volume button up, nothing happens.
Actually, I had a moment of inspiration when using the fastboot oem unlock command- I realised that when the cursor was flashing it was waiting for me to confirm that I wanted to unlock on the phone itself. So, I pushed up on the volume rocker and confirmed by pushing the power button, and fastboot reported that I had successfully unlocked the phone. "Great!" I thought, but whatever I try to flash onto the phone I get the same behaviour, the lights at the bottom of the screen flash but nothing happens on the screen.
So it seems I have a faulty screen, or I did something to screw with the electronics. There are a couple of sugestions here to try but I don't hold out much luck.
Thanks for you help anyway
brmayhem said:
I'm sorry I didn't fully understand. It doesn't boot into fastboot but it picks up the serial number? Have you tried flashing a recovery through fastboot?
Click to expand...
Click to collapse
No problem, from other posters it seems I'm not too good at explaining myself. I think the phone is actually booting into recovery but the screen is dead so it looks like nothing is happening.
Yeah, I finally managed to unlock the handset (see my previous post), and I can flash the recovery no problem (or at leasts it reports no problem), but nothing comes up on the screen. As I said in my last post I think the screen must be borked.
Thanks for posting anyway, it's much appreciated.
obsanity said:
I think he means that if you do "fastboot devices" it comes up with a number. That means there is some hope.
Did you try flashing with Samsung's exe? You have to know which model you got.
Click to expand...
Click to collapse
Samsung's exe? Sorry, I did a quick google on this but I'm not sure exactly what you mean? As I've said in my last 2 replies, I think the screen is the problem but it's worth a try.
Thanks for all the suggestions so far, and sorry to pipe on about this, but has nayone seen this behaviour where the screen flashes for a millisecond when the phone is turned on but then stays dead, and instead the function keys at the bottom light up and turn off in a particular sequence? As I've said in my last couple of posts I think my phone is toast but maybe there is a clue somewhere in that description?
Samsung has an exe for windows to restore your system where it was original. Find the one for your phone and flash it. The file is different depending on who you carrier is and what model number do all the research them run the exe
Edit exe is called swupdater on sprint
Sent from my Nexus S 4G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1072698
Uncle Jimmy says hello
Related
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?
razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.
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?
"Your device is corrupt. It can't be trusted and may not work properly." (Red)
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
https://support.google.com/nexus/an...6399943843044-1589582643&p=verified_boot&rd=1
Has anyone else experienced this?
I also got that message when I first got device. Set up my Google account and then let it sit and charge. Looked 30 mins later that message appeared. It was also followed up by another screen talking about unsecure boot or something and powered it self off. It said can not boot when I tried to restart phone and I tried again and no response from the phone at all.waited 5 mins and it booted fine and never seen the messages again .
that screen appears when the bootloader is unlocked. did you guys unlock your bootloader? or, did you purchase from T-Mo/someone else?
Bl still locked and bought online from tmobile never even loaded any apps yet
anoymonos said:
Bl still locked and bought online from tmobile never even loaded any apps yet
Click to expand...
Click to collapse
if you reboot to bootloader mode, does your screen look like the picture below:
Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.
maruichan said:
Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.
Click to expand...
Click to collapse
if your phone screen in bootloader mode does not look like the one in my post, you purchased the phone direct from T-Mobile/Other Retailer and you didn't unlock the bootloader, i'd ask for a replacement. if your phone screen in bootloader mode looks like the one in my post, the bootloader has been unlocked somehow/by someone...
cortez.i said:
if you reboot to bootloader mode, does your screen look like the picture below:
Click to expand...
Click to collapse
Power + Vol Dwn gives me this screen...
maruichan said:
Power + Vol Dwn gives me this screen...
Click to expand...
Click to collapse
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.
cortez.i said:
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.
Click to expand...
Click to collapse
K, will try it in a bit
maruichan said:
K, will try it in a bit
Click to expand...
Click to collapse
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.
cortez.i said:
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.
Click to expand...
Click to collapse
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.
maruichan said:
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.
Click to expand...
Click to collapse
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.
See still locked
cortez.i said:
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.
Click to expand...
Click to collapse
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.
maruichan said:
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.
Click to expand...
Click to collapse
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.
BTW, did anyone get a second screen saying contact customer support (some kind of language like that)? It is very similar to the red error screen, but it read like the device was basically bricked. It disappeared after a while and the phone turned off while I was trying to get a picture.
Got both screens
cortez.i said:
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.
Click to expand...
Click to collapse
I did, that is how I got the return date. They notated my account massively and it looks like it'll be a root canal to a exchange.
I'm not sure that it's anything more than a bug... it hasn't stopped the phone from working and possibly may be an oversensitive security measure on Android's part. So far it seems only related to Nexus(?) that I could find... I am only posting here so others can inform themselves. Maybe others with similar errors who have owned a Nexus could enlighten us.
Either case, doing a factory reset in a little bit. I also received the latest update and applied it. So maybe that'll help too...
franki_667 said:
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
Has anyone else experienced this?
Click to expand...
Click to collapse
Yes I have had this happen 2 different times and 4 days apart on my AT&T LG G6, U.S. Variant. NO I don't unlock my devices ever. And I only install well known apps from the Play store. One possible pattern I noticed was that both times it happened relatively soon after turning OFF the always on display. Then when I rebooted the AOD was turned back on by itself. No other settings appear to be changed and my Nova launcher is running normal.
Did you happen to turn off your AOD as well?
Hello i have recently tried to return my phone from cyanogenmod into the stock rom using this thread: "https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110" and my phone got stuck in the process while making the command "fastboot flash bootloader bootloader.img". And now my device is stuck on boot loop showing the cyanogenmod loading screen.
Anyway now i found a way to get to stock but for that i need to get my device into fastboot. THE PROBLEM IS that my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
p.s I have used to think that my fastboot was deleted but on an other thread i have been told that as long as i see the cyanogenmod loading screen of the OS that means i have a boot-loader.
Please help!
I want to get into Fastboot on my Moto Pure.
Thanks a lot
Eden.
Power down 1st
Try volume down & power key together. That will get you into fastboot directly.
Oops just seen that, my bad, I wont respond anymore.
Sent from my Portable
PassatSport15 said:
Power down 1st
Try volume down & power key together. That will get you into fastboot directly.
Oops just seen that, my bad, I wont respond anymore.
Sent from my Portable
Click to expand...
Click to collapse
Haha, as said. can't power off.
Np thanks for responding!
Anyone got an idea?
u cant poweroff does that means your phone is continuously bootlooping or its just booting but takes a hell lotta time to boot up?
Sagar_1401 said:
u cant poweroff does that means your phone is continuously bootlooping or its just booting but takes a hell lotta time to boot up?
Click to expand...
Click to collapse
I think @edenah is saying it just gets stuck at the loading screen. If the battery discharges all the way and the device is plugged in, the battery symbol shows and after the charger is unplugged, the battery charging doesn't go away until the battery dies again or the power button is pressed (which leaves us right back to where we started)
edenah said:
Hello i have recently tried to return my phone from cyanogenmod into the stock rom using this thread: "https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110" and my phone got stuck in the process while making the command "fastboot flash bootloader bootloader.img". And now my device is stuck on boot loop showing the cyanogenmod loading screen.
Anyway now i found a way to get to stock but for that i need to get my device into fastboot. THE PROBLEM IS that my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
Click to expand...
Click to collapse
Try this:
Hold power button for 10-20 sek, when screen will turn off hold only vol-(at bootloop screen).
You should flash stock without "oem" commands.
Find how to update bootloader​.
aybarrap1 said:
I think @edenah is saying it just gets stuck at the loading screen. If the battery discharges all the way and the device is plugged in, the battery symbol shows and after the charger is unplugged, the battery charging doesn't go away until the battery dies again or the power button is pressed (which leaves us right back to where we started)
Click to expand...
Click to collapse
Yes thats exactly what i mean.
dzidexx said:
Try this:
Hold power button for 10-20 sek, when screen will turn off hold only vol-(at bootloop screen).
You should flash stock without "oem" commands.
Find how to update bootloader​.
Click to expand...
Click to collapse
tried this, but the device still goes into the cyanogenmod loading screen.
its soft brick but can't be fixed (just thinking any method but no idea man)
get your phone to moto service centre and they can only fix it (or maybe not) caus this is worst case happening to you
if any pro dev read this thread he might be able to answer but badluck (nobody gives a ....)
btw when you connect your phone to pc does it shows unknown device or it just charge the phone?
Sagar_1401 said:
its soft brick but can't be fixed (just thinking any method but no idea man)
get your phone to moto service centre and they can only fix it (or maybe not) caus this is worst case happening to you
if any pro dev read this thread he might be able to answer but badluck (nobody gives a ....)
btw when you connect your phone to pc does it shows unknown device or it just charge the phone?
Click to expand...
Click to collapse
:/
It recognizes it as portable usb device.
And well. I have bought the device in the us but i live outside of the US. so its bit problematic to return it now. Some help could do the trick!
I found SP flash tool and i believe it would do the trick. But i need to get the scatter loading file of the moto pure, but i can't find it anywhere, maybe anyone got the idea how to get that?
edenah said:
:/
It recognizes it as portable usb device.
And well. I have bought the device in the us but i live outside of the US. so its bit problematic to return it now. Some help could do the trick!
I found SP flash tool and i believe it would do the trick. But i need to get the scatter loading file of the moto pure, but i can't find it anywhere, maybe anyone got the idea how to get that?
Click to expand...
Click to collapse
We haven't been able to get the QLoad files for most Moto devices, at least not for the last 2-3 years... Sorry.
Well i have found a way to get the device charged while the screen is off!
If i connect it to my computer while pressing the power button and the vol down button and keep pressing it, the device stays turned off!
Now i'm trying to play with it, to turn the bootloader. so far the classical power and vol combo doesn't work.
edenah said:
Well i have found a way to get the device charged while the screen is off!
If i connect it to my computer while pressing the power button and the vol down button and keep pressing it, the device stays turned off!
Now i'm trying to play with it, to turn the bootloader. so far the classical power and vol combo doesn't work.
Click to expand...
Click to collapse
I am stuck. No button combination works. I suspect that the device isn't really off but the display is just closed. As even to open up the device takes a reallly long press on the power button.
if it got interrupted while flashing bootloader, you're pretty much not going to be able to do anything.
motorola service center is likely the only place that can fix it.
sorry for your luck.
edenah said:
Haha, as said. can't power off.
Np thanks for responding!
Anyone got an idea?
Click to expand...
Click to collapse
ericpeacock79 said:
if it got interrupted while flashing bootloader, you're pretty much not going to be able to do anything.
motorola service center is likely the only place that can fix it.
sorry for your luck.
Click to expand...
Click to collapse
exactly that's what I'm saying but he needs to get his phone to USA as he specified..
only a specialist can help ya
Sagar_1401 said:
exactly that's what I'm saying but he needs to get his phone to USA as he specified..
only a specialist can help ya
Click to expand...
Click to collapse
i see :'(
Ok Thank your guys
I guess its a lost cause.
edenah said:
i see :'(
Ok Thank your guys
I guess its a lost cause.
Click to expand...
Click to collapse
Lost cause? No, probably not... Do you know anyone in the US you trust well enough to receive the phone from repair and ship it to you where ever you are? I believe that is all you need. The US service center cannot ship outside of North America (maybe US), but they can receive packages from anywhere. If you had a US contact that could receive the device and forward it on to you it might be worth it to get it fixed if it is still under warranty, if it isn't, then it might not be worth fixing. Lots of things to consider here.
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.