Related
Hi,
New to the forum and looking for a bit of guidance.
My M5000 will not power up, even to the Orange Logo etc. However if you try a hard reset the screen comes up "press 0 to reset "etc and if you try to go to bootloader that comes up with serial. When you insert the usb cable in bootloader it flicks from serial to usb but can't be accessed on the PC even though it shows up as mobile device.
When on charge the redlight doesn't come on unless you press the reset button and then it only flashes for a second.
It could be something simple like the battery is gone etc but I am a bit lost and could do with some advice.
Thanks in advance.
I hate it when you only get half a story. You are stuck in bootloader and it didn't get there all on it's own. Did you try to update the rom and something went wrong? Were you buggering about with it? Or something different.
Look tell us EXACTLY what you did to get it into this state as getting it out of it has many different answers depending on what you did.
Now fess up else you'll probably do more damage to it when suggestions arrive on this thread that may be incorrect because we don't know how it got like this in the 1st place.
Psi
PsiDOC said:
I hate it when you only get half a story. You are stuck in bootloader and it didn't get there all on it's own. Did you try to update the rom and something went wrong? Were you buggering about with it? Or something different.
Look tell us EXACTLY what you did to get it into this state as getting it out of it has many different answers depending on what you did.
Now fess up else you'll probably do more damage to it when suggestions arrive on this thread that may be incorrect because we don't know how it got like this in the 1st place.
Psi
Click to expand...
Click to collapse
Not half the story, the only reason I got to bootloader was because I was trying to see if a reinstall of the software would make any difference. There has been no mods to this unit at all. Was working fine for a year and a half then these problems started happening.
At first I thought it may be a problem with the power button and that is part of the reason I got into bootloader to see if the power button actually worked!
Long story short - phone has suddenly stopped turning on apart from factory reset and bootloader.
OK first thing is to get it OUT of bootloader and see what happens next.
Read this. I suggest method 2 at the bottom of the page as it's a lot easier.
Psi
Thanks, will try those.
After a total brick, Black screen. I am convinced that this phone is truly un-brickable, I did not ask for help. All you need to do is READ READ READ! Having said that I would like to thank eugene and everyone else for the usefull tips.
30Glock said:
After a total brick, Black screen. I am convinced that this phone is truly un-brickable, I did not ask for help. All you need to do is READ READ READ! Having said that I would like to thank eugene and everyone else for the usefull tips.
Click to expand...
Click to collapse
Congratulations! It is widely believed that this phone is about as close to being unbrickable as any phone out there.
Would you care to share how you got your phone working again? It's possible that someone might actually read this instead of asking, in which case you can forward the cause
Yea--DO SHARE!!!
I wrecked my phone somehow and have not been able to reflash a stock rom no matter what...I have a few days before I have to ship it back with to the warrantee center--I'd love to try and fix a HW locked phone.
this is true, unless u have a hardware locked phone, in that case, ne thing can brick ur phone easily
ookas said:
this is true, unless u have a hardware locked phone, in that case, ne thing can brick ur phone easily
Click to expand...
Click to collapse
That is not entirely accurate, I "bricked" my phone, and I have a hardware locked vibrant, seems download mode can be gotten into with some due diligence("due diligence"=Don't panic and read read read) .
I have a hardware locked phone, obviously I read the threads. I cannot get into download mode - at all. No recovery.
If you're bad at pressing key combinations on your hardware unlocked phone, that's okay. You will eventially get it and then post how you got your hardware locked phone into download mode, I'm sure (hint, take off the back cover, makes pressing the buttons trivial).
Don't spread misinformation.
Hardware locked phones will not let you get into download or recovery mode. They will just power cycle over and over again if you try to hold keys down while the phone is booting up. You can try evey combination immaginable and one of two things will happen:
1. It will power cycle indefinitely (if power button held down) to the Vibrant Logo (turns off and on to that screen forever).
2. It will get stuck at the Vibrant Logo and never move (if the Volume Buttons held down). Will get to Vibrant Screen and stay there.
If you let go of all the buttons, it will just boot up normally (if it can, or get to a black screen if you bricked it /shrugs/).
I know. We tried for 3 hours in the store and I stayed up half the night trying. There's no way to get there, Lol. Seriouly: No way.
T-Mobile says it's a known issue. Asurion knows of the issue. Samsung knows the issue (issued a patch for Canada, but no one else IIRC). All 3 told me the only recourse is to get my phone replaced.
And that's what I'm doing.
I doubt you will get charged for bricking a hardware locked phone, because the manufacturer will have to flash a new ROM onto the phone anyways - at a repair factory.
Mine is locked, but I got into recovery mode via terminal app connected on USB.
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
I'm fairly new to this, bear with me. I'll try to include lots of detail. If I'm asking or posting in the wrong area, just let me know. I've been trying to do this without any hand-holding, but it's been pretty frustrating and it's a lot to soak in and I think I probably got something wrong.
My S4 seems to be partially bricked.
I was given a retired S4. The phone is locked to Bell in Canada (It's an SGH-I337M, not a 9500 en.wikipedia.org/wiki/Samsung_Galaxy_S4#Model_variants ). When it was given to me, it had Cyanogenmod 11 on it. The previous owner is techsavy and tried to unlock it, paid for several websites to give him codes, none worked and they refunded. This was when the S4 was new, he hadn't tried since.
I wanted to use it with Rogers. I was happy to just pay for an unlock code, but, it seemed I needed to be on the original firmware. So I learned how to use ODIN and downloaded Bell's original firmware. As suggested here: ( galaxys4root.com/galaxy-s4-stock-firmware/ ) and I picked the Bell one ( stockroms.net/file/GalaxyS4/SGH-I337M/I337MVLUAMDJ_I337MOYAAMDJ_BMC.zip ). It seemed that I needed to downgrade anyway to get most of the carrier unlocks to work. (In Canada, IIRC, there was no region lock, just carrier, but regardless it spent two years on a Bell plan).
When I finished using ODIN, successfully, the phone restarted but now appears to not complete booting or be able to flash a new ROM of any kind, at least by methods I've tried.
On powering up:
1 - "Samsung GALAXY S4" in curvy font.
2 - Blue swirly animation of Samsung.
3 - Do do do do doo dooooooooo, audio.
4 - Blue LED in top left stays lit.
5 - SAMSUNG in white on black screen stays there, pulsing with blue light occasionally.
6 - It stays here forever.
It never finishes booting, and it's a hell of a power draw the phone got hot after an hour.
When I try to boot into recovery, I get the blue text in the upper left, but it just reboots.
When I try to put it into download mode, I get a green warning about custom OS's, I can use volume up to agree or volume down to cancel. Either way, it just reboots.
If I try to power it down without pulling the battery, it just boots up, same loop as above, and stays there, pulsing the logo forever.
I can't get to any diagnostic screen, but maybe I'm trying the wrong ones or the wrong ways.
How badly did I mess up my phone?
I'd like to just use it as a camera even, if I can't get it to unlock so I can use Rogers, but it seems I've messed that up now too.
Any help or advice would be greatly appreciated. If you need more detail, I'm happy to give it. (Sorry for bad links, new user, can't post links).
Download from Sammobile the stock rom for your model and flash it in download mode wit Odin
TroubleshotHell said:
I'm fairly new to this, bear with me. I'll try to include lots of detail. If I'm asking or posting in the wrong area, just let me know. I've been trying to do this without any hand-holding, but it's been pretty frustrating and it's a lot to soak in and I think I probably got something wrong.
My S4 seems to be partially bricked.
I was given a retired S4. The phone is locked to Bell in Canada (It's an SGH-I337M, not a 9500 en.wikipedia.org/wiki/Samsung_Galaxy_S4#Model_variants ). When it was given to me, it had Cyanogenmod 11 on it. The previous owner is techsavy and tried to unlock it, paid for several websites to give him codes, none worked and they refunded. This was when the S4 was new, he hadn't tried since.
I wanted to use it with Rogers. I was happy to just pay for an unlock code, but, it seemed I needed to be on the original firmware. So I learned how to use ODIN and downloaded Bell's original firmware. As suggested here: ( galaxys4root.com/galaxy-s4-stock-firmware/ ) and I picked the Bell one ( stockroms.net/file/GalaxyS4/SGH-I337M/I337MVLUAMDJ_I337MOYAAMDJ_BMC.zip ). It seemed that I needed to downgrade anyway to get most of the carrier unlocks to work. (In Canada, IIRC, there was no region lock, just carrier, but regardless it spent two years on a Bell plan).
When I finished using ODIN, successfully, the phone restarted but now appears to not complete booting or be able to flash a new ROM of any kind, at least by methods I've tried.
On powering up:
1 - "Samsung GALAXY S4" in curvy font.
2 - Blue swirly animation of Samsung.
3 - Do do do do doo dooooooooo, audio.
4 - Blue LED in top left stays lit.
5 - SAMSUNG in white on black screen stays there, pulsing with blue light occasionally.
6 - It stays here forever.
It never finishes booting, and it's a hell of a power draw the phone got hot after an hour.
When I try to boot into recovery, I get the blue text in the upper left, but it just reboots.
When I try to put it into download mode, I get a green warning about custom OS's, I can use volume up to agree or volume down to cancel. Either way, it just reboots.
If I try to power it down without pulling the battery, it just boots up, same loop as above, and stays there, pulsing the logo forever.
I can't get to any diagnostic screen, but maybe I'm trying the wrong ones or the wrong ways.
How badly did I mess up my phone?
I'd like to just use it as a camera even, if I can't get it to unlock so I can use Rogers, but it seems I've messed that up now too.
Any help or advice would be greatly appreciated. If you need more detail, I'm happy to give it. (Sorry for bad links, new user, can't post links).
Click to expand...
Click to collapse
Don't worry you are fine. Just try to flash another stock rom.
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.