Database Users

[Q] Bricked Nexus S

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

[Q] Stuck at bootloader unlock screen

Update: I format the Windows 8 OS and install the Windows 7, everything works and there is no problem anymore.
I entered the fastboot mode and use a unlock tool to help me into unlock procedure, the instrucion shows that I should use the volume keys and power key to select and confirm, but none of these keys responded, meanwhile they work perfectly at any other situation. I think the phone just stuck in this screen rather than the keys fail at the step. BTW, I update 4.1.2 via OTA.
Could anyone shows his wisdom or experience?

syph1x said:
I entered the fastboot mode and use a unlock tool to help me into unlock procedure, the instrucion shows that I should use the volume keys and power key to select and confirm, but none of these keys responded, meanwhile they work perfectly at any other situation. I think the phone just stuck in this screen rather than the keys fail at the step. BTW, I update 4.1.2 via OTA.
Could anyone shows his wisdom or experience?
Click to expand...
Click to collapse
Hold down power button till shuts off , while still holding power hold down , down volume key let go power then press and hold power key while still holding volume down , should restart bootloader ..... Pm me if don't work
This is y no one should use toolkits

I had a similar issues on my nexus s
I read on a thread to keep the phone near a source of heat. so i turned on the stove and kept the phone 20cms away from the heat , and ran to the pc hit commands and voila it worked xD
Wouldn't suggest this on a Nexus 4 though

Qwerty123 \m/ said:
I had a similar issues on my nexus s
I read on a thread to keep the phone near a source of heat. so i turned on the stove and kept the phone 20cms away from the heat , and ran to the pc hit commands and voila it worked xD
Wouldn't suggest this on a Nexus 4 though
Click to expand...
Click to collapse
Nope, this doesn't work. But if this does work, I would definitely buy the Google guys some lava since they love heat so much.

[Q] Stuck in APX mode after bootloop

I was running the 2.99 PA rom on my Nexus 7 with m-kernel without any issues until 2 days ago, when my device rebooted and entered a bootloop, got stuck on the Google screen first, then I managed to get into the twrp recovery and erased cache and dalvik cache. Then it booted until the "X" screen and got struck there until I resetted the device by holding the power button for a while. Since then, the screen is totally dead, the only response I can get is the Windows usb device connected sound. I've tried each and every button combination and also pulled the battery but it did not help. The tablet shows up as an APX device in the device manager. I have searched the forums and I only found other people who have accindentally erased their bootloaders and then got stuck in APX, but this is not the case with my nexus as there wasn't any bootloader tinkering involved at all.
Do you have any suggestions on what I should do/try to do?

Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers

bftb0 said:
Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
Click to expand...
Click to collapse
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?

wasab said:
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?
Click to expand...
Click to collapse
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).

bftb0 said:
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).
Click to expand...
Click to collapse
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?

wasab said:
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
Click to expand...
Click to collapse
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
wasab said:
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?
Click to expand...
Click to collapse
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7

bftb0 said:
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7
Click to expand...
Click to collapse
Thanks for your help! I think that I will try to solve this the easy way, but if I have no luck with that then I'm sure that I'll do some serious digging about the apx recovery.

[Q] Can enter bootload but nothing else.

So recently my phone went into Deep Hibernation so I plugged it into a charger and held down Power, Volume down.
I managed to get into the boot loader screen but only the volume keys are responsive to select options but the power button is unresponsive.
I have no idea on how to start the phone or turn it off anymore, what can I do?

Is your bootloader unlocked. If it is use fastboot reboot. That should boot your device
Sent from my Nexus 5 using XDA Free mobile app

Well I have no idea if it's in Fastboot or not. Currently the phone is stuck in the mode where there's an arrow pointing towards the power button and 2 white arrows with representation to the volume buttons. I think it's in Fastboot right now but again, the power button isn't working at all to select anything.
I'm not too familiar with these terms. All I know is that I have the phone unlocked and Paranoid Android installed.

TheBluePylon said:
Well I have no idea if it's in Fastboot or not. Currently the phone is stuck in the mode where there's an arrow pointing towards the power button and 2 white arrows with representation to the volume buttons. I think it's in Fastboot right now but again, the power button isn't working at all to select anything.
I'm not too familiar with these terms. All I know is that I have the phone unlocked and Paranoid Android installed.
Click to expand...
Click to collapse
Sounds like you're in fastboot mode. From a command prompt on your pc and with the usb cable plugged between your phone and the pc, type fastboot reboot. It should boot your device. Hopefully that will clear what ever is causing your power button not to work
Sent from my Nexus 5 using XDA Free mobile app

Do I need any sort of program to connect a cmd to my phone? As of right now my phone isnt even registered as a device when it's connected to my computer. Mind giving me a step by step?

TheBluePylon said:
Do I need any sort of program to connect a cmd to my phone? As of right now my phone isnt even registered as a device when it's connected to my computer. Mind giving me a step by step?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my Nexus 5 using XDA Free mobile app

Well I managed to reboot it and get back phone's home screen. Though I still have the issue of the fact that my lock/power button is completely busted and/or unresponsive.
Should I just install an app that will serve as an alternative to the power button? By now my Warranty would've already expired and I would have no way of getting it repaired. Are there checks I can make to see whether or not it's a software or hardware fault?

TheBluePylon said:
Well I managed to reboot it and get back phone's home screen. Though I still have the issue of the fact that my lock/power button is completely busted and/or unresponsive.
Should I just install an app that will serve as an alternative to the power button? By now my Warranty would've already expired and I would have no way of getting it repaired. Are there checks I can make to see whether or not it's a software or hardware fault?
Click to expand...
Click to collapse
My best guess is it's a hardware issue. A local cell phone repair shop can put in a new power button without a lot of cost.
Sent from my Nexus 5 using XDA Free mobile app

oneplus 2 not working after screen replacement

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.