Related
I tried installing CWM and somehow must have done it wrong. Gtab bricked, would not turn on at all. Let the battery run down, connected to DC, still nothing.
Plugged in the USB and my Windows 7 computer recognized the device, so I assumed it was in APX mode
Followed instructions for NVFlash, got it up and running. Shut it down, but it would not come back up with the power button.
Repeated the NVFlash, got it up and running again - shut it down and same thing - it would not come back up.
I then used the FORMAT routine to wipe the Gtab, then the NVFlash routine, same thing. It recovered but would not power back up after powering down.
I used two different NVFlash routines, one from this forum, one from another. One included the CWM, one did not.
I also ran update on the Gtab, downloaded 1.1-3588 successfully, however when installing, at the reboot stage, the Gtab again would not power up.
Present configuration shows Tap UI version 1.0-2638.
Common problem is inability to restart/power up after these steps.
Any ideas? Is this a hardware thing?
PS - I have spent quite a few hours looking for similar problem in the forums without luck - however if there is a thread that covers this please point me.
Im having the same problem, iv tried both nvflash techniques and nothing, also cant find anything helpful in forums
Hoping someone else on this forum has an answer... Are planning to return it? Got mine on woot and I think I have 30 days??
Sounds like some crickets are chirping on this one. I have continued to review other threads and can't find anything quite like what I am experiencing as described above. I continue to re-NVFlash the gtablet whenever I need to use it. It will go into "sleep" mode and recover with a short power button push but will not come back after fully powering down.
I've loaded three different NVFlash routines, one from this site and two from another. One has the clockwork mod built in. In all cases I can't get the power up cycle to work. When I plug in the USB cable it pings indicating it is in APX mode (boot looping??).
The only thing I can think of is cracking the case and hitting the reset button.
Since I can re-flash it I guess I could always return it??
Any ideas
Update; Rangercaptain and 440bro suggested the power switch or the usb port may be the problem.
I dismantled the phone and got my ohm-meter, the power button's circuit is opening and closing as it should between pressed and depressed.
Furthermore I tested the usb port for conductivity at each pin, from the side of the usb cable that would normally connect to the pc all the way through the 'charging flex ribbon' to the phones PCB. all connections are good.
Editing this post as I try new things i find or the things i try that people suggest.
Currently my Note will not boot into recovery or it's ROM, I was running a version of Slimbean.
I can get it to go into download mode via the volume down + power key but I can not for life of me get any pc to recognize it via usb.
I have tried Odin, Adb, and Heimdall with five or six different versions of Samsung USB drivers, Version #'s 1.5.14.0, 1.4.6.0, as well as the drivers listed in the Note 'Super thread' ATT I717 v1_3_2200_0 and two other sets of drivers that did not have version numbers listed, but came from other XDA USB problem posts. I have also tried the Google drivers from the Android SDK.
I have done all this on two different pc's and different usb cables. I've read other problem threads about this and tried most of those suggestions I.E. Uninstall old drivers, reboot, install new ones, reboot, turn off internet, plug in phone. Nada, no sign of the device being recognized at all.
I've tried the 'adb devices' command while the device was in download mode, the command returns nothing.
the USB port still works so far as i can tell, if you plug it in to a charger or the pc the phone will try to boot like it usually does if it's powered off and you plug it in and the phone had been charging fine before this issue, so i've no reason to suspect a bad port.
I have however encountered this USB problem before even while the note was stock and functioning with it not being recognizable over USB, I eventually gave up and it's what caused me to install a ROM on it in the first place because i couldn't get the official android updates with Kies (they require a usb connection).
Would a USB jig be of any benefit in this situation? After searching through XDA forums and the like that's the only thing that seems like it may work but i haven't tried. I'm unclear if it will be of any benefit because the device can already access the ODIN downloading screen.
All in all I've been working on this for about 12 hours so far, so it's possible i may have forgotten something I've tried but i'll update if i remember anything significant.
Finally I'm aware there are two similar threads currently running on the XDA note troubleshooting forums,"Is my note bricked?" and "can't enter download mode" I am also watching them and trying anything that looks relevant but elected to make a new post as my problem is slightly different in that I can access the download screen. If you posted anything there that you think may have applied here, you don't have to re-post. I'll have tried it.
Your power button is stuck.
rangercaptain said:
Your power button is stuck.
Click to expand...
Click to collapse
Thanks, I should clarify that the reboot cycle is not indefinite though. it'll give the boot vibration 6-8 times with a few seconds in between each vibration and then stop trying to boot. It also doesn't cycle every time, just occasionally. The other times it will give the vibration only once and then do nothing till you hold the power button down again as if you were trying to turn it on.
It will also stay in the downloading mode until i manually hold the power button down, so the power button is functioning correctly.
morthicius said:
. . . so the power button is functioning correctly.
Click to expand...
Click to collapse
If you say so.
Take out the sim and sd card.
I have tried removing the SD card and SIM card as well. Makes no noticeable difference.
I can also add that the USB port still works so far as i can tell, if you plug it in to a charger or the pc the phone will try to boot like it usually does if it's powered off and you plug it in.
I can dismantle the phone and check the power button if you're fairly convinced that's what it is but it really responds exactly like you would expect. The press and return feels fine and the way the device responds to it also feels fine.
Yeah I'm pretty sure it's a stuck power button. If the phone is off and you plug in usb, or charger it should NOT startup by itself. If it does it's most definitely a stuck power button. So I'm guessing your phone is no longer covered by warranty?
Before you go tearing apart the phone try this first. Take off the battery cover and where the power button is you'll see a lil outline. Flick this area with your finger a few times. Flick it hard enough to mildly hurt your finger but not the phone. I had to do this for a while till I got a new note. If that doesn't help take it apart at your own risk.
440bro said:
Yeah I'm pretty sure it's a stuck power button. If the phone is off and you plug in usb, or charger it should NOT startup by itself. If it does it's most definitely a stuck power button. So I'm guessing your phone is no longer covered by warranty?
Click to expand...
Click to collapse
It has always started up on its own when you plug it in, at least if it's out of charge. Of that I'm certain. I've had the phone a year and a half or so now. It may not boot up on it's own if you just manually shut it off and plug in a charger though. I don't recall ever trying that scenario directly. It could also be a functionality Slimbean added if stock phones don't do it.
I did just try your flick trick though, thanks. No change.
Just as another example on the power button, I can take the battery out and put it back in and the phone will do nothing until i hold the power button down a few seconds, only then does it do the the "i'm trying to boot" vibration.
Damn I was really hoping the flick trick worked for you like it did me. If you decide to take the back of the phone off, try flicking again anyways before you completely disassemble it. Once you disassemble it, there really isn't much you can do power button wise other than replace it. I'll attach a pic of the power button area for ya. I have one already torn down.
If it's not your power button, I wonder if it's your usb charger port on the phone.... That's an easier part to replace if it is.
I do feel like the USB port is a possibility, even despite my saying it appears to work. is it possible for the port to be damaged in such a way that it still allows the phone to be charged but not establish a data connection? When the phone went brick yesterday It had pretty much just finished fully charging. I had disconnected it from the charger used it a little bit, set it down when it still at about 98% battery life. Around 10 minutes later I got a text message, it made the god awful slimbean text tone (i hate that tone) I went to check it, turned on the display it then repeated the incoming text message tone about five more times in quick succession, locked up, and then died never to return.
I have had the phone apart before because i'm a curious cat, and didn't really mind voiding a warranty.
The only things that would make me skeptical of it being a usb port problem is. 1: It was charging fine and 2: the symptoms at least of the reboot problem itself are leaning towards a software issue the Slimbean install has never really worked great, and would crash and reboot probably twice a day.
Just because the button works doesn't mean it isn't stuck. I've only saved about ten phones by helping the owner to understand the cause of the reboots.
The fact that you already opened the phone increases the chance its the button. Because you said it rebooted on stock or custom ROMs eliminated software. Because your phone charges normally and is recognized by a pc shows its not the usb port.
But hey, what do I know. . .
morthicius said:
Editing this post as I try new things i find or the things i try that people suggest.
Currently my Note is in a reboot cycle, it will not load the ROM or go into recovery mode. I was running a version of Slimbean.
I can get it to go into download mode via the volume down + power key but I can not for life of me get any pc to recognize it via usb.
Click to expand...
Click to collapse
rangercaptain said:
Just because the button works doesn't mean it isn't stuck. I've only saved about ten phones by helping the owner to understand the cause of the reboots.
The fact that you already opened the phone increases the chance its the button. Because you said it rebooted on stock or custom ROMs eliminated software. Because your phone charges normally and is recognized by a pc shows its not the usb port.
But hey, what do I know. . .
Click to expand...
Click to collapse
He has more than one problem. He can NOT get a pc to recognize it. I missed it first too and had to re-read it a few times. So it could be the port, or the power button.
I think your options are....
-Find a repair center nearby
-Send it in for repair
-Find out which part is cheaper and replace that yourself first.
Sounds good. The usb port is cheap and easy and while the bezel is off you can verify the power button isn't stuck in its hole in the bezel.
Because he flashed a custom ROM from a stock ROM I took that to mean he had to connect to a pc through the usb port, either to Odin flash a recovery or Odin flash Slimbean. And he can still charge it. And data cables go bad, removing drivers doesn't take them out of memory, etc. So usb port isn't 100% bad for sure, but you're right, its a cheap, easy repair.
rangercaptain said:
Just because the button works doesn't mean it isn't stuck. I've only saved about ten phones by helping the owner to understand the cause of the reboots.
The fact that you already opened the phone increases the chance its the button. Because you said it rebooted on stock or custom ROMs eliminated software. Because your phone charges normally and is recognized by a pc shows its not the usb port.
But hey, what do I know. . .
Click to expand...
Click to collapse
If the button is 'stuck' it implies that the it's either stuck engaged or disengaged correct?
If that were true and lets say it were stuck engaged, the power button should be acting as if it is pressed. Which at first would make sense when i say it reboot cycles. It however does not make sense that i can get into download mode and the phone never shuts off until I hit the power button.
It also does not make sense that if i pull the battery out and put it back in the phone does nothing. until i hit the power button. If it were stuck engaged the phone would immediately try to boot when i put the battery back in.
The rom has also been on it for awhile now, 6 months? So i don't exactly remember the processes i went through but i know i never got kies or odin to recognize it. And Yeah, pc wont recognize it now even tryin two different pcs, one of which has never had a samsung device connected to it.
That said I wont rule the power button out either, Is there a good way to check the power button with a multimeter?
I should also say I have the phone apart now so i could at least do external checks of the power button since you both thought it was a possibility, externally it looks fine the actual button inside the case (the little white button the big silver one hits) acts fine but the circuit inside could still be screwed i suppose, which is why i ask about a meter test.
Ultimately I think you're both right though, I'm just going to have order a replacement button and port. Start with the port since it's easier, and if that doesn't enable me to connect it to the pc to flash it try the button too.
Since you mention the ROM, it is possible to have a bad download, flash the ROM, and get into a bootloop. The usual cure for that is a re-download of the ROM, wipe caches, wipe system, and flash fresh ROM.
The sticking power button is a common fault of Samsung phones. Its not broken, but it just gets a little out of alignment in its hole in the bezel. If you already wiggled and snapped, you would have noticed a difference in the phone's behavior, unless there's lint under it.
I think you have your plan -- replace the usb port, and check the button while the phone is without the bezel.
The usb port is on ebay and there is a Youtube video for the process. Everything is here:
http://forum.xda-developers.com/showthread.php?p=28247335
Good luck.
Thanks for the Help Ranger and 440.
Update; Rangercaptain and 440bro suggested the power switch or the usb port may be the problem.
I dismantled the phone and got my ohm-meter, the power button's circuit is opening and closing as it should between pressed and depressed.
Furthermore I tested the usb port for conductivity at each pin, from the side of the usb cable that would normally connect to the pc all the way through the 'charging flex ribbon' to the phones PCB. all connections are good.
I'm going to try the phone tonight on a friends PC. Who doesn't have another note but at least has a Samsung Gs2 and 3 that connect to Kies and see if i can get it to establish a connection.
If anybody else has any ideas on troubleshooting the connection between the device and a PC i'm all ears.
Good luck!
440bro said:
Good luck!
Click to expand...
Click to collapse
Well interestingly, when i hooked it up to the friends pc (using one of the same usb cables i already had) not only did his pc recognize it, the phone also booted up immediately. with 15% battery life remaining.
Strange strange.
I started to restore to a back-up I made two days ago in TWRP and I think it got interrupted by my accidentally canceling it. I was on my way out the door and wasn't paying attention and must've touched the screen (phone in hand).
Now it behaves much like cadcamaro's description in his recent post about having tried to install a Z2 ROM. I can get into FastBoot, but all options simply shut down the phone. If I don't choose an option, it shuts down by itself after a a minute or so.
Power + Volume Down gets a short vibration.
When I plug it into the PC, Power + Volume Up Gets me a blue LED that stays lit, but the PC (and Flashtool) doesn't see it.
Power + Volume Down gets an orange, then green LED with vibration that repeats.
The first time I realized it was screwed up, I did get into Recovery. I tried to re-run the back-up (which is saved to external SD), and it shut down.
Thanks, all.
AddictedToGlass said:
I started to restore to a back-up I made two days ago in TWRP and I think it got interrupted by my accidentally canceling it. I was on my way out the door and wasn't paying attention and must've touched the screen (phone in hand).
Now it behaves much like cadcamaro's description in his recent post about having tried to install a Z2 ROM. I can get into FastBoot, but all options simply shut down the phone. If I don't choose an option, it shuts down by itself after a a minute or so.
Power + Volume Down gets a short vibration.
When I plug it into the PC, Power + Volume Up Gets me a blue LED that stays lit, but the PC (and Flashtool) doesn't see it.
Power + Volume Down gets an orange, then green LED with vibration that repeats.
The first time I realized it was screwed up, I did get into Recovery. I tried to re-run the back-up (which is saved to external SD), and it shut down.
Thanks, all.
Click to expand...
Click to collapse
Have you tried pressing and holding the reset button next to the SIM tray? Try holding it down for 2+ minutes and see what happens.
Have you tried pressing and holding the reset button next to the SIM tray? Try holding it down for 2+ minutes and see what happens.
Click to expand...
Click to collapse
Thanks for responding, BladeRunner.
I just tried that in a variety of ways, and got either no response or it simply did what it was doing. I'll explain;
Believing the phone to be OFF, nothing happens for 2 1/2 minutes of pressing the Reset button.
Same goes for a variety of combinations of switches also depressed, such as Volume Up/Down, Power, or any combo therof.
(At this point, I'm uncertain if I even have much of a charge in the phone.)
FastBoot is the menu that has the green Droid with a choice of 4 options, including Power Down, Continue to Power Up, Factory Reset, and something else, correct?
The one time that I did get that to appear during these last few attempts to use the Reset switch, the menu simply shut down after 15 seconds. I continued to press the reset switch, but nothing happened.
Plugged into the PC, the phone continued to cycle Power-On every 8 seconds, with the Orange LED followed by the Green, then Shut-Down. (Apparently, as without the screen on I have no idea what it's really doing....)
Plugged into PC, Power Button in and Volume Up gives me the Blue LED that stays on constantly, but depressing the Reset Switch does nothing.
As I stated earlier, I have no idea how much charge the phone has, so I'm leaving it on the PC in the Blue LED state. It may not be charging, but all it does when I try to charge it any other way is cycle through every 8 seconds with the Orange & Green LED.
Sigh... This would be the first phone I've ever bricked, and I've been messing around since Vivo on the V3m, and always very careful. Sucks since this has been my favorite of them all.
AddictedToGlass said:
Thanks for responding, BladeRunner.
I just tried that in a variety of ways, and got either no response or it simply did what it was doing. I'll explain;
Believing the phone to be OFF, nothing happens for 2 1/2 minutes of pressing the Reset button.
Same goes for a variety of combinations of switches also depressed, such as Volume Up/Down, Power, or any combo therof.
(At this point, I'm uncertain if I even have much of a charge in the phone.)
FastBoot is the menu that has the green Droid with a choice of 4 options, including Power Down, Continue to Power Up, Factory Reset, and something else, correct?
The one time that I did get that to appear during these last few attempts to use the Reset switch, the menu simply shut down after 15 seconds. I continued to press the reset switch, but nothing happened.
Plugged into the PC, the phone continued to cycle Power-On every 8 seconds, with the Orange LED followed by the Green, then Shut-Down. (Apparently, as without the screen on I have no idea what it's really doing....)
Plugged into PC, Power Button in and Volume Up gives me the Blue LED that stays on constantly, but depressing the Reset Switch does nothing.
As I stated earlier, I have no idea how much charge the phone has, so I'm leaving it on the PC in the Blue LED state. It may not be charging, but all it does when I try to charge it any other way is cycle through every 8 seconds with the Orange & Green LED.
Sigh... This would be the first phone I've ever bricked, and I've been messing around since Vivo on the V3m, and always very careful. Sucks since this has been my favorite of them all.
Click to expand...
Click to collapse
I'm not sure what fastboot mode on the z3v looks like honestly, but your description sounds about right. You could try getting into xz dual recovery again and wiping the cache maybe? The instructions to there are in the xzdr thread. If you can get there wiping, a factory reset or flashing something might work but failing that you might want to try letting the battery drain all the way down. If you just let your phone sit that can take a while ( days at least) or you use a rubber band to hold down the poet and volume down button, I believe, to drain the battery. Once its dead completely connect it to your PC and see what happens.
A failed flash on a eeprom can be a hard thing to recover from, sometimes it can ruin the eeprom preminently, depends on the state the eeprom was in in the flash process,usually in erase process it will not be recoverable. . Removing power will not reset the eeprom, eeproms are preminent memory, but it can allow the device to be discovered again hopefully.
You have to get something to erase and flash again, if the eeprom is in a failed state that may be impossible to do.
1linuxfreak said:
A failed flash on a eeprom can be a hard thing to recover from, sometimes it can ruin the eeprom preminently, depends on the state the eeprom was in in the flash process,usually in erase process it will not be recoverable. . Removing power will not reset the eeprom, eeproms are preminent memory, but it can allow the device to be discovered again hopefully.
You have to get something to erase and flash again, if the eeprom is in a failed state that may be impossible to do.
Click to expand...
Click to collapse
So I'm assuming the eeprom is like an order of operations & file allocation index or something really basic upon which everything else is built? This is an old school term for file index, right?
So even if I manage to get everything wiped, I need to start fresh by installing the stock ROM that the phone came with and progress to where I can load the saved Back-Up that's on the External SD?
If the eeprom gets wiped as it's re-written from the Back-Up, and interruption blew this process mid-wipe, will my Back-Up still be useable?
How is it that battery drain will help my device become recognized by the PC?
Thanks for all the help.
AddictedToGlass said:
So I'm assuming the eeprom is like an order of operations & file allocation index or something really basic upon which everything else is built? This is an old school term for file index, right?
So even if I manage to get everything wiped, I need to start fresh by installing the stock ROM that the phone came with and progress to where I can load the saved Back-Up that's on the External SD?
If the eeprom gets wiped as it's re-written from the Back-Up, and interruption blew this process mid-wipe, will my Back-Up still be useable?
How is it that battery drain will help my device become recognized by the PC?
Thanks for all the help.
Click to expand...
Click to collapse
Correct. Your backup is safe as long as you don't mess with sdcard storage. You have to get the eeprom healthy before you can do a recovery.
Back to working on my bricked Z3v...
Plugged into PC with Volume-Up held in yields solid Blue LED. This is the only time that in Windows 8.1 Device Manager that the phone shows up as a connected device. The name of the device is "S1 Boot Fastboot", for which there is no driver installed. When I navigate to Z3-lockeddualrecovery2.8.23-RELEASE.combined / files / adbdrivers and try to install the driver, Windows says "Windows could not find driver software for your device."
However, in the "Events" tab it shows three previous dates that the device was configured. It listed the device as such "Device USB\VID_0FCE&PID_0DDE\BH900JCL1N was configured." on those dates.
Was there something different I had to do for Windows 8? I cannot remember, but this feels familiar.
Driver Name: Google, Inc. (WinUSB)...
Status: Install failed
Meanwhile other drivers do install. What gives?
Well I was hoping for a bit more. Extremely frustrated right now as it took me about 15 minutes just to get here to see that nobody can help.
In the meantime with all the **** I've downloaded trying to fix my phone, I've completely scxrewed my computer. 4 virus scans later and I'm still f'd.
Great.
AddictedToGlass said:
Well I was hoping for a bit more. Extremely frustrated right now as it took me about 15 minutes just to get here to see that nobody can help.
In the meantime with all the **** I've downloaded trying to fix my phone, I've completely scxrewed my computer. 4 virus scans later and I'm still f'd.
Great.
Click to expand...
Click to collapse
Your phone is toast and the only way to get it back is through the Flashtool imo. It wouldn't be common for many to have your circumstances with a bricked phone so you aren't getting much feedback. See if you can follow these instructions with Flashtool that I posted. I've gone from 4.4.4 to 5.02 non-rooted and back to root on 4.4.4 and then forward again so it has worked well for me.
http://forum.xda-developers.com/showpost.php?p=63800685&postcount=8
See if you can download the 4.4.4 firmware after getting flasthool 09.18.6 installed. Granted my instructions are from Windows 10 64 bit but it should work.
Couldn't do any of it. My PC is s screwed up, but even in Safe Mode I was unable to load drivers that would recognize my z3v.
So I'm typing this on my replacement phone that came today via FedEx. I was very nervous about getting a refurb, but this one really is like new. I managed to get the glass protector of the old one, rinse it off, and apply it to the new one.
Now I'm on unrooted kitkat.
If I root and install TWRP, can I simply flash my saved lollipop backup from my SD card and make this phone exactly like the other one was before I borked it?
AddictedToGlass said:
Couldn't do any of it. My PC is s screwed up, but even in Safe Mode I was unable to load drivers that would recognize my z3v.
So I'm typing this on my replacement phone that came today via FedEx. I was very nervous about getting a refurb, but this one really is like new. I managed to get the glass protector of the old one, rinse it off, and apply it to the new one.
Now I'm on unrooted kitkat.
If I root and install TWRP, can I simply flash my saved lollipop backup from my SD card and make this phone exactly like the other one was before I borked it?
Click to expand...
Click to collapse
I wouldn't recommend that. I have used titanium backups before from one device to another and it worked. The whole system from a twrp backup really doesn't sound like a good idea.
OK. Think I'll just be patient and do it from scratch. Have to get the computer cleaned up first.
Really glad to have a clean, new z3v back again, but this ordeal has certainly impacted my confidence doing this stuff.
Thanks for your help, everyone.
Hey guys. I'll try to keep this brief. I bought a Redmi Note 3 Pro "global edition" online, which says it supports my carrier's bands. It got here, but it wasn't working with my SIM (said something about a network error). From what I found, it seemed to be because of the ROM that came with it (it didn't allow me to select any English speaking country from the list during setup). So I found the one I needed, followed some highly rated instructions to flash it, and it got stuck at like 99% with an error. That's when the phone seemingly hard-bricked. No display whatsoever, any combination of buttons held down did nothing. The only thing was a red flashing LED (when power button held or when plugged in). It is detected by my computers in device manager, but only comes up as "Qualcomm HS-USB Diagnostics 900E", which doesn't allow me to flash it or really do anything with it on the computer. I've tried literally everything I could find about it, both software-wise and hardware; I made a deep flash cable, tried it multiple times to no avail. Then I finally took the phone apart to get at the testpoint; it did nothing besides cause the red LED to flicker a little in its pattern. I've contacted a bunch of phone repair places near me, but none seem to be able to do anything for me. Do I have any options left at this point?
broodyr said:
Hey guys. I'll try to keep this brief. I bought a Redmi Note 3 Pro "global edition" online, which says it supports my carrier's bands. It got here, but it wasn't working with my SIM (said something about a network error). From what I found, it seemed to be because of the ROM that came with it (it didn't allow me to select any English speaking country from the list during setup). So I found the one I needed, followed some highly rated instructions to flash it, and it got stuck at like 99% with an error. That's when the phone seemingly hard-bricked. No display whatsoever, any combination of buttons held down did nothing. The only thing was a red flashing LED (when power button held or when plugged in). It is detected by my computers in device manager, but only comes up as "Qualcomm HS-USB Diagnostics 900E", which doesn't allow me to flash it or really do anything with it on the computer. I've tried literally everything I could find about it, both software-wise and hardware; I made a deep flash cable, tried it multiple times to no avail. Then I finally took the phone apart to get at the testpoint; it did nothing besides cause the red LED to flicker a little in its pattern. I've contacted a bunch of phone repair places near me, but none seem to be able to do anything for me. Do I have any options left at this point?
Click to expand...
Click to collapse
Can you go to fastboot mode (press volume down + power botton together until bunny appears) ?
Nabin Pokhrel said:
Can you go to fastboot mode (press volume down + power botton together until bunny appears) ?
Click to expand...
Click to collapse
Nope. Literally nothing I do will get anything to come up on the screen.
Bump
if you're in 900e, means the phone is prolly not dead. remove the back, get to your board, plug it to your pc and keep on holding your tweezers until the pc recognizes it as a 9008 device. then just use flash tool. it takes time, u should be patient. refer to the vid
https://www.youtube.com/watch?v=HDLV4LdEBHk
this thing is pretty unbreakable, unless its really fried, in which case, well, trash it
this is soft brick , not to worry , the flashing red is EDL mode ...this guide is for note 3 pro but will work with you http://en.miui.com/thread-235865-1-1.html
sikica133 said:
if you're in 900e, means the phone is prolly not dead. remove the back, get to your board, plug it to your pc and keep on holding your tweezers until the pc recognizes it as a 9008 device. then just use flash tool. it takes time, u should be patient. refer to the vid
https://www.youtube.com/watch?v=HDLV4LdEBHk
this thing is pretty unbreakable, unless its really fried, in which case, well, trash it
Click to expand...
Click to collapse
Alright, I was just using a flimsy wire before but I do have a good pair of tweezers coming in the mail. I'll give it another shot as soon as I get those.
tdassa said:
this is soft brick , not to worry , the flashing red is EDL mode ...this guide is for note 3 pro but will work with you http://en.miui.com/thread-235865-1-1.html
Click to expand...
Click to collapse
I appreciate the effort, but I'm positive it's not in EDL mode. I've looked at just about every guide out there, including that one. It isn't detected by XiaoMiFlash, and I can't get it into actual EDL mode either.
Thanks guys
it wont work with miflash if it's not in 9008 mode which is effectively edl. as far as tweezers go, i used a safety pin and it worked fine. it will work, just repeat the process a few times
My S9+ was acting quite weird this morning. Some apps continuously crashed or wouldn't start.
So i rebooted my phone (just from the normal power button menu) and then it went completely black.
It doesn't charge (or at least, it doesn't show it charging), it doesn't respond to forced resets and the screen is completely black.
The only thing it does, is briefly show a USB device when connecting it to a PC.
I've connected it to a Linux dev computer i have laying around and i see the following device connected briefly:
VID: 0x04e8
PID: 0x1234
It stays connecting longer if i hold the power button (about 8 seconds before power cycling).
The only things i could find online were some very old threads about Samsung's DNW mode, but nothing from this decade.
I think my Flash chip might be cooked, but i hope i'm wrong.
Anyone got any experience with this?
Update
I've sent it back to Samsung for repair under warranty.
The flash chip was gone. It started corrupting writes and finally it was so far gone that it couldn't load the bootloader.
They've replaced the main board and battery (probably because they tested it and saw it was going bad), that fixed it.