Hi all,
I've a Samsung Nexus S here from a friend of me.
The phone was rooted and flashed with Cyanogenmod 10.1. Without any special action the phone doesn't power on again after a reboot (during a software update CM10.1). There's nothing. Only a black screen. No lights! Nothing...
I've tried to power on it for several times. I've tried to start it into the download mode and the fastboot mode. But only a black screen. My computers Mac, Linux, Windows are detecting nothing when I'm connecting them to the phone.
Do you've any ideas for unbrick this nexus s?
regards
Marco
MarcMarin said:
Hi all,
I've a Samsung Nexus S here from a friend of me.
The phone was rooted and flashed with Cyanogenmod 10.1. Without any special action the phone doesn't power on again after a reboot (during a software update CM10.1). There's nothing. Only a black screen. No lights! Nothing...
I've tried to power on it for several times. I've tried to start it into the download mode and the fastboot mode. But only a black screen. My computers Mac, Linux, Windows are detecting nothing when I'm connecting them to the phone.
Do you've any ideas for unbrick this nexus s?
regards
Marco
Click to expand...
Click to collapse
That's exactly what I'm working on right now.. Let's start with the basics.. Do you have a good cable (tested with other micro-usb devices?)? If so, on Linux, under terminal, does the lsusb command show any Samsung devices while connected?
Hi,
I have a similar problem.
My Nexus S suffers from the power button bug with the power button occasionally not working. When I turned it off today (using the terminal as I always do) it shut down as normal. However, when I tried to start it again it, it would not boot. When I press the power button (it usually works to start the phone, it just does not work within the recovery / OS), the backlight turns on but there is no vibration and it does not proceed to the Google logo. Similarly if I try to start it using the charger, the backlight turns on but it does not proceed from there.
Linux does not recognise the device, i.e. neither dmesg nor lsusb show any output. Therefore I cannot use the Unbrickable Resurrection tool.
Would doing that be helpful?
http://forum.xda-developers.com/nexus-s/development/i9020t-nexus-s-development-platform-aka-t1566475
I cannot enter Fastboot or Download mode. Again, only the backlight turns on.
Is it a hardware fault?
Has anyone had similar problems?
Thanks.
Yes, it will if yours is a i9020a or t. BUT you need a VERY steady hand and PROPER soldering equipment.. I had mine in Dev mode but it wasn't flashing anything, so I thought I didn't do something right, took it all back apart, and 20 mins and a popped micro resistor (from too much heat from the soldering wand) later, I had a completely dead phone.. So if you attempt it, be very careful.. If you don't feel comfortable you can do it, I would definitely find someone who can..
Related
Hello XDA friends. This is my first official posting on the XDA site and I'm in need of serious help.
I've noticed that intense research and development has been put into this phone. With so many rom selections available for the MT4GS I decided to try out several different roms kind of playing around. Many of the roms available were very well put together.
I decided to try out the Doubleshot MIUI v0.3 as I have used on other devices in the past and liked its customization. After installing the rom I made some adjustments in the settings to personalize my phone. Everything was working fine until I rebooted my phone and now it is hard-bricked. My device is S-Off with bootloader unlocked, and prior to installing MIUI I formatted all data, Dalvik, and system. I don't know what I did to brick my device and I can't find similar issues among others.
Issue Details:
When I have the phone powered off then hit the power button my backlight will slightly light up (very dim with no splash or image), and it will vibrate (Like on a normal boot). What else is crazy is every 37 seconds it will vibrate, and this is ongoing if I let the phone sit in that state.
If I have the phone off and plug it in a power source I get no love.
I'm unable to access HBOOT or Recovery mode, and the phone is not detected when connected to PC.
Please help me.......
that looks like a screen/digitizer problem. I don't think you're even bricked seeing as you didn't mess with any partitions according to what you did above. Also if the phone vibrates and the backlight turns on then it's still alive.
Thanks for the response. I'm sure the screen is fine. I performed the reboot when the issue first happened. This phone is driving me crazy.
wait u said you phone isn't connecting to adb right?
Did you try Fastboot?
I'm not able to bring up the HBOOT menu to enter fastboot mode.
have you tried a battery pull?
Thanks for the reply. I have tried pulling/replacing the battery and didn't have any luck. I also have two spares and the issue continues........
I can't figure it out, or figure what I did exactly to cause this.
Any other ideas?
does adb recognize it when it is plugged in?
Hi, so yesterday after powering my Surface 2 down (it was working fine), it no longer boots up. Instead, it will show the 'Surface' on the screen for about a second, and then the screen will go black for 8 seconds, and repeat until I turn it off or the battery dies.
I've been having a hard time finding other people with this problem, but the few I did said that sending it to MS (and getting a new one) is what they had to do. One person did say that they were able to fix the problem with a bootable Surface 2 recovery USB. I have a lot of work on my surface that I don't have copies of, and would really like to be able to save those files.
Things I have tried: Holding the power button with a combination of volume rocker/home key. Holding the power button for 20 seconds followed by 2 seconds off and on. I have fully charged it and know it has enough battery.
Help would be greatly appreciated.
Hi John,
What was the solution to fi this problem?
I encounter the same problem.
Regards,
Hans
You should be saving your stuff to your OneDrive...anywho
If you have a USB recovery drive, you could try booting from it and doing a refresh,(NOT a reset) that would keep your files.
If you don't have a USB recovery drive you could make one using the 8.1 RTM ISO, I wrote a how-to guide here;
http://forums.wpcentral.com/microso...w-install-windows-rt-8-1-rtm-surface-2-a.html
or you could download one here;
https://onedrive.live.com/?cid=203A62CBEDC78BA2&id=203A62CBEDC78BA2!6247&authkey=!AIcBVsLygTfpZxQ
(I think that one is for the UK, but that shouldn't matter, just do a full reset from your recovery once you get your files off)
Hope this helps.
Guys,
I have a OPO 64gb which is in Dead State (Hard-bricked) currently.
It doesn't switch on. Nothing comes up on the screen after pressing Power button. Can't even go to Recovery Screen or Download Screen. No display, no logo, no vibration. I even tried it after keeping it for charging overnight.
This happened after my cousin tried to flash something (I have no idea what he was doing).
I have gone through many thread on this and various other forums which gives solution of Unbricking the phone. However none of them helped, because my case is a little different.
In all those Recovery procedures, it is mentioned to connect the phone to PC and press Vol Up + Power button. When I connect the OPO to PC, it is not detected at all. Even it doesn't show up in the Device Manager (no QHSUSB_BULK, as many mentioned). There is absolutely nothing which indicates that the phone is connected to PC. This is were I get stuck because I don't know what needs to be done from here.
Has anyone ever faced such an issue? How to I bring back the OPO back to life from this state? Is there a solution to this?
Please help!
What did you end up doing???
What did you end up doing???
I have the exact same situation though I wasn't trying to update anything, it just crashed and all the same symptoms appeared...
@SuzAnDroid
Dont worry,
If you are still facing the problem,
Then You can follow this Superb Link
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi!
I'm trying to help out a friend here. They have a pixel 2 device and their screen went completely dark off one day. Apparently it didn't fall or anything. Anyway, if I plug the device into a pc I get the sound of it recognizing new hardware but I can't find it in the device manager. Alongside that a hard reset or trying to get ot the recovery mode does not seem to work. I don't think the screen image just died because there is no response to HW buttons being pressed on the phone.
ADB does not see the device with ADB devices and I can't seem to get any response from the device at all. Any ideas what do?
niirb said:
Hi!
I'm trying to help out a friend here. They have a pixel 2 device and their screen went completely dark off one day. Apparently it didn't fall or anything. Anyway, if I plug the device into a pc I get the sound of it recognizing new hardware but I can't find it in the device manager. Alongside that a hard reset or trying to get ot the recovery mode does not seem to work. I don't think the screen image just died because there is no response to HW buttons being pressed on the phone.
ADB does not see the device with ADB devices and I can't seem to get any response from the device at all. Any ideas what do?
Click to expand...
Click to collapse
Try holding power and volume down button for 10-12 second, then connect the device to PC and enter fastboot Device, if it shows your device then flash it and reboot, now it should boot with screen on.
If it doesn't show in fastboot Device then it should be hardware problem, maybe screen or motherboard.
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.
s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?