Dear Forumites,
I have considered all available options in my capacity to attempt to fix my device mentioned above to no success. I will mention all the things I have done below so as to better inform you. But before I do that, let me give you the background of how I got here.
My device fell into water some months ago (while trying to be an hero to resque a drowning little boy, LOL). I guess I should have been more patient but I guess I got carried away by a water test I saw of this device before I bought it done by some of these reviewers and thought, Ok maybe my device too will stand this. I ignorantly put the device into plug and I am guessing I compounded its problem. Initially, I saw the red charging light come on and stayed on while the device was making a kind of sound but after I plug it in power, the device showed some screen flash and then went off. Let me mention that three devices went into the water at the same time but this one was the only one I couldn't remove the battery so the other two are fine now.
Fast forward to few days later, I waited and allowed it to dry out more but when i plugged it into power, the red ligh started to flash without stopping. So this got me searching for solutions to fixing it. I tried:
Downloading all available flash tools
Putting it in EDL mode (I am constantly finding it in 9008 in COM Ports). And when it fails, I tried all the available methods to get it back to that mode again.
I downloaded the fastboot rom and tried to flash it using several flash tools and also various methods.
Then after so much time and effort, I found a thread that says I should just let the battery die itself and then check it later. I left the device for about 2 weeks. Then one day I plugged it in and then it came up charging. I allowed it to charge to 100% then I switched it on. I guess the mistake I made was not leaving it plugged in power while it was booting up again because suddenly it seems the battery power gave out and the device went blank again.
Since then, charging it never again worked. I have left the device for a few months now and still charging it never worked again. I even purchased an extra battery to replace the old one but nothing has worked. I have tried taking the device to a local repair centre where the motherboard was cleaned, heated and still nothing worked.
Till date, when I plug the device into my system, it still recognizes the device but flashing isn't working. I am at the point now where I am considering either getting a new motherboard or just thrashing the device. Been searching online to get a Kate board but it seems that is not available to buy as all i find is the motherboad for Kenzo.
Here is my request, CAN I REPLACE THE KATE BOARD WITH THAT OF KENZO. Some sellers are telling me it will fit inside the panel but it seems they are just saying that to get my money. All the othe parts are working fine along with the extra battery and several tempered glass and cases.
Pls help me with the above so I can decide how to proceed. Thank you in advance. Attached is the image of my motherboard.
i007tosee said:
Dear Forumites,
I have considered all available options in my capacity to attempt to fix my device mentioned above to no success. I will mention all the things I have done below so as to better inform you. But before I do that, let me give you the background of how I got here.
My device fell into water some months ago (while trying to be an hero to resque a drowning little boy, LOL). I guess I should have been more patient but I guess I got carried away by a water test I saw of this device before I bought it done by some of these reviewers and thought, Ok maybe my device too will stand this. I ignorantly put the device into plug and I am guessing I compounded its problem. Initially, I saw the red charging light come on and stayed on while the device was making a kind of sound but after I plug it in power, the device showed some screen flash and then went off. Let me mention that three devices went into the water at the same time but this one was the only one I couldn't remove the battery so the other two are fine now.
Fast forward to few days later, I waited and allowed it to dry out more but when i plugged it into power, the red ligh started to flash without stopping. So this got me searching for solutions to fixing it. I tried:
Downloading all available flash tools
Putting it in EDL mode (I am constantly finding it in 9008 in COM Ports). And when it fails, I tried all the available methods to get it back to that mode again.
I downloaded the fastboot rom and tried to flash it using several flash tools and also various methods.
Then after so much time and effort, I found a thread that says I should just let the battery die itself and then check it later. I left the device for about 2 weeks. Then one day I plugged it in and then it came up charging. I allowed it to charge to 100% then I switched it on. I guess the mistake I made was not leaving it plugged in power while it was booting up again because suddenly it seems the battery power gave out and the device went blank again.
Since then, charging it never again worked. I have left the device for a few months now and still charging it never worked again. I even purchased an extra battery to replace the old one but nothing has worked. I have tried taking the device to a local repair centre where the motherboard was cleaned, heated and still nothing worked.
Till date, when I plug the device into my system, it still recognizes the device but flashing isn't working. I am at the point now where I am considering either getting a new motherboard or just thrashing the device. Been searching online to get a Kate board but it seems that is not available to buy as all i find is the motherboad for Kenzo.
Here is my request, CAN I REPLACE THE KATE BOARD WITH THAT OF KENZO. Some sellers are telling me it will fit inside the panel but it seems they are just saying that to get my money. All the othe parts are working fine along with the extra battery and several tempered glass and cases.
Pls help me with the above so I can decide how to proceed. Thank you in advance. Attached is the image of my motherboard.
Click to expand...
Click to collapse
Buy new phone instead. Kenzo and kate had no good value. Replacing parts of old phone is of no worth.
Better get rn7 or rn7 pro.
Related
Hi all,
I've spent hours researching and nothing so just looking for new ideas.
The last few days I've been running official SE 2.1 and today it started force-closing many apps. I restarted the phone a few times and that didn't fix it. So I restarted again to go into recovery and switch ROM. The phone switched off and won't turn on. It said it had low battery life if that's a part of it. The phone will not switch on, it will not charge with any combination of with/without SD card, SIM card etc.
1. SEUS and PC Companion will not repair it, they don't see it.
2. Laptop/PS3 don't see the phone.
3. I left the phone connected via the wall-charger for over 2 hours at two seperate occasions uninterrupted an nothing.
4. The phone shows no LED. Not even the quick-flashing red LED when the battery is extremely low.
I searched every SE site where this is discussed and no help, I've tried everything. I emailed SE and they said it would be better to send it away. I note that they charge a fee if they can't fix it. (It's within warranty though) and my phone is unlocked, debranded and shows various mods typical of users' phones from this site and the warranty says if SE find user mods they phone will void warranty. It may not switch on and neither the network or SE may find the mods which may mean I get past OK, but besides that, is there anything I can do myself? Thanks.
REPAIRED MYSELF
After hours and hours of research and effort, 5 minutes after posting this thread I fixed my phone myself. I hope though that this will help others out there. As with everything like this, especially on this site, these are user mods and frequently delicate or dangerous - you do them at your own risk, and could destroy your device or warranty. If you haven't rooted/flashed many times or don't know what they are, you do not know enough to do this. I say this to protect you, trust me.
If you take off the back cover, above and to the left there are two RUBBER coverings. I used a pin to remove the LEFT cover. You see the power connector of the phone to the battery. Use the pin, carefully and at your own risk, to remove the white part by gently pulling back and up. It's stiff so try a few times. You see 3 wires connected to the white tab. I clean the white tab and metal connector with my finger, re-attached the white tab, you must do that firmly or it won't connect, try again and again. Try the power button on the phone when you have it connected to laptop/pc/etc. and you should see the the red LED gently indicating it's slowly returning to power.
That was a hardware issue it seems?
I really don't know...I've seen other's recommend giving your phone a jump-start with a battery and connector but I couldn't find a connector, and just tried cleaning it with my thumb (no obvious cleaning needed, but I tried) and it did the job...strange. I'm sure this info. will help the next person who gets lost. It'll save time and perhaps money. And us guys around here like to fix things ourselves anyway...
phoneyericsson said:
Hi all,
I've spent hours researching and nothing so just looking for new ideas.
The last few days I've been running official SE 2.1 and today it started force-closing many apps. I restarted the phone a few times and that didn't fix it. So I restarted again to go into recovery and switch ROM. The phone switched off and won't turn on. It said it had low battery life if that's a part of it. The phone will not switch on, it will not charge with any combination of with/without SD card, SIM card etc.
1. SEUS and PC Companion will not repair it, they don't see it.
2. Laptop/PS3 don't see the phone.
3. I left the phone connected via the wall-charger for over 2 hours at two seperate occasions uninterrupted an nothing.
4. The phone shows no LED. Not even the quick-flashing red LED when the battery is extremely low.
I searched every SE site where this is discussed and no help, I've tried everything. I emailed SE and they said it would be better to send it away. I note that they charge a fee if they can't fix it. (It's within warranty though) and my phone is unlocked, debranded and shows various mods typical of users' phones from this site and the warranty says if SE find user mods they phone will void warranty. It may not switch on and neither the network or SE may find the mods which may mean I get past OK, but besides that, is there anything I can do myself? Thanks.
REPAIRED MYSELF
After hours and hours of research and effort, 5 minutes after posting this thread I fixed my phone myself. I hope though that this will help others out there. As with everything like this, especially on this site, these are user mods and frequently delicate or dangerous - you do them at your own risk, and could destroy your device or warranty. If you haven't rooted/flashed many times or don't know what they are, you do not know enough to do this. I say this to protect you, trust me.
If you take off the back cover, above and to the left there are two RUBBER coverings. I used a pin to remove the LEFT cover. You see the power connector of the phone to the battery. Use the pin, carefully and at your own risk, to remove the white part by gently pulling back and up. It's stiff so try a few times. You see 3 wires connected to the white tab. I clean the white tab and metal connector with my finger, re-attached the white tab, you must do that firmly or it won't connect, try again and again. Try the power button on the phone when you have it connected to laptop/pc/etc. and you should see the the red LED gently indicating it's slowly returning to power.
Click to expand...
Click to collapse
---------------------------------------------------------------------------
Thank you very much!!!!My SE x10 mini now works properly!!!!great fix!!!!
You're welcome buddy! It's nice to be able to share advice with others!
i think,there is no need to remove back pin...
if you press home button simultaneously along with power button for few seconds phone restarts...i used to get same problem.
I have a Motorola Atrix 4G on Bell Mobility. Currently the phone will not boot at all. The phone is out of warranty.
When this started I began by searching through the xda forums and found several similar problems. Most pointed to the sleep-of-death or a charging adapter problem. I have tried charging with the Motorola adapter that came with the phone, a USB cable and the Motorola Lapdock. None of these have provided any happy. Each time I tried, I left the phone overnight, when I checked on it, the phone and battery were cold. I tested a known-working battery from another Atrix and the phone would still not boot.
Some other searches point to a factory cable. I bought one on Ebay however the phone will not boot. I tested the cable on a known-working Atrix and it works fine. I did notice that when I plug the factory cable in to my phone and in to my Windows 7 PC, it detects *something*. Under device manager I see an unknown device called "APX". So far Google and xda searches haven't been able to provide me with a correct answer.
When I plug in the regular USB cable the green LED turns on for a while, if I touch the power button, the green LED goes out. RSD Lite does not detect anything, I assume this is because the phone is not in RSD mode.
I have tried combinations of volume buttons/power button as well, both with the wall charger and with the factory cable. Nothing displays on the screen at all no matter what I've tried. The phone had the stock install from Bell however was rooted with SuperOneClick (obtained from xda forums and installed many months ago) and had no third-party apps on it.
This death seemed to start slowly, at first battery life was at times terrible, then it moved on to not wanting to power on for a while if the battery died or the phone was turned off when the battery was low. Removing/re-inserting the battery several times typically helped. Eventually the phone got so bad, when it booted it would just crash repeatedly with a message about motorola.home.something (sorry I don't remember exactly what). Hitting force close would just bring the message back up again. I left the phone off overnight and the next morning, R.I.P. my Atrix
I have access to Windows XP or 7 as well as Linux.
Any help would be appreciated. Also I apologize for the long-winded post, I'm trying to provide as much information as I can.
I had this problem to, I freaked out, what I needed to do was to get another Atrix (in this case my Uncles) and make sure that the battery in it is FULLY CHARGED, then I took out my battery (in the broken phone) and put in his, then I got a solid green LED, then I had to leave it on the charger overnight, after that the M would show, but that was it, so I then went into fastboot and flashed the ICS Leak, and ta-da.
Xerox98 said:
I had this problem to, I freaked out, what I needed to do was to get another Atrix (in this case my Uncles) and make sure that the battery in it is FULLY CHARGED, then I took out my battery (in the broken phone) and put in his, then I got a solid green LED, then I had to leave it on the charger overnight, after that the M would show, but that was it, so I then went into fastboot and flashed the ICS Leak, and ta-da.
Click to expand...
Click to collapse
I had tried that before, but I can't remember if I had charged the battery full. I'll give it a shot today, thanks!
jonbruce said:
I had tried that before, but I can't remember if I had charged the battery full. I'll give it a shot today, thanks!
Click to expand...
Click to collapse
I've tried that with no luck. I should also note that the factory cable bypasses the battery, potentially eliminating any battery problems.
It's possible that your phone is finished. The 'motorola.home' error is usually caused by something you've updated (google search?) but I would doubt that it would cause your phone to not even start up.
At this point, I might be inclined to open the phone up (http://www.ifixit.com/Teardown/Motorola+Atrix+4G+Teardown/4964/1) and see if you can see anything obvious?
barry_ said:
It's possible that your phone is finished. The 'motorola.home' error is usually caused by something you've updated (google search?) but I would doubt that it would cause your phone to not even start up.
At this point, I might be inclined to open the phone up <url removed so I could reply> and see if you can see anything obvious?
Click to expand...
Click to collapse
I will check that out tonight and report back, thanks!
jonbruce said:
I will check that out tonight and report back, thanks!
Click to expand...
Click to collapse
Nothing obvious when I took it apart, no visible damage or problems. Any other thoughts? I've been told to try ADB from a Linux box and see if it will do anything. I've started installing ADB but looking for more insight.
jonbruce said:
Nothing obvious when I took it apart, no visible damage or problems. Any other thoughts? I've been told to try ADB from a Linux box and see if it will do anything. I've started installing ADB but looking for more insight.
Click to expand...
Click to collapse
Update. I found this ... http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75 and now instead of "APX" in Windows device manager, I have "NVIDIA USB Boot-recovery driver for Mobile devices".
It looks like NVFlash might be something I need next. In other news, the phone when plugged in via the factory cable, is actually very slightly warm. It's the first new sign of life I've seen in this thing for a few days.
jonbruce said:
Update. I found this ... http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75 and now instead of "APX" in Windows device manager, I have "NVIDIA USB Boot-recovery driver for Mobile devices".
It looks like NVFlash might be something I need next. In other news, the phone when plugged in via the factory cable, is actually very slightly warm. It's the first new sign of life I've seen in this thing for a few days.
Click to expand...
Click to collapse
I've had no luck at all since my last reply. http://forum.xda-developers.com/showthread.php?t=1046994 seems to have something to do with my problem, but I'm not able to dig up a solid answer. As best as I can tell, I manged to hard brick the thing and I'm up the creek without a required paddle.
Any other thoughts on this would be great. Even if I'm able to ensure the device is wiped, I could send it in. There are work files on there (I know, I know, I'm an idiot) I can't have out in the wild.
Just bought a replacement Atrix for $100. It included three cases, three batteries, wall charger with cable, car dock and a metric ass-load of screen protectors.
I do want to thank everyone for offering help and ideas, it was a good learning experience!
jonbruce said:
Just bought a replacement Atrix for $100. It included three cases, three batteries, wall charger with cable, car dock and a metric ass-load of screen protectors.
I do want to thank everyone for offering help and ideas, it was a good learning experience!
Click to expand...
Click to collapse
I've just encountered this issue and cannot find a solution anywhere online. I've come to terms with my phones fate by now. Just wanted to ask where I could find this Atrix replacement for 100 w/ all the neat stuff you've listed above? Please advise
thanks
Cheekan
cheekan said:
I've just encountered this issue and cannot find a solution anywhere online. I've come to terms with my phones fate by now. Just wanted to ask where I could find this Atrix replacement for 100 w/ all the neat stuff you've listed above? Please advise
thanks
Cheekan
Click to expand...
Click to collapse
I found mine on Kijiji, luckily right in my city.
Hello, so much time searching for this on the web, spanish is my birth language... so i wanted to know some update from this of any of you if posible, thanks in advance.
i couldn't describe better the problem and situatiob, is exactly the same, same phone of course.
I was about to try to make a factory cable, so i ended here, i think is not going to help me then is that right?
PD: i don't know what more to do with the atrix, sell for parts, even that is difficult over here, and the services don't help either, i've tryied 2 of them already, only ignorance they have
My phone wouldn't power on so I got it repaired at a phone repairs shop. The guy there thought there was a software error because he saw the error triangle on bootup. He was mucking around with it in download mode when I got there, I said not to worry about it, paid for the repairs and left.
The phone will not boot, and will not go into recovery or download modes with the respective key combinations
UNLESS
I have it plugged into a power source, in which case I can enter download/recovery mode, but when I try to boot the phone I just get the empty battery picture with the loading circle appearing periodically.
--- Possible solution: bad battery
I have flashed CWM onto the phone using odin in download mode and have flashed .zip roms that were previously working before this debacle, but again the phone won't boot onto the newly installed rom.
I have tried flashing the correct stock rom using odin but the phone won't boot this way either.
When I take the battery out and connect the phone to a power source it is non-responsive.
Apart from a batter problem (which I will be able to test tomorrow), what could be the cause of this problem, and how might I be able to fix it?
Sounds like a JTAG (but don't get your hopes up) or a motherboard replacement job (more likely) to me. If the phone won't boot at all/shows no signs of life, something is majorly wrong. As to what that is, nobody here could tell you that with certainty because we don't have the phone in front of us, but if it's not booting at all either the NAND is buggered or something else on the MB has crapped itself.
Cross your fingers it's just a simple battery issue, but it doesn't sound like it.
MistahBungle said:
If the phone won't boot at all/shows no signs of life
Click to expand...
Click to collapse
What does being able to access recovery mode/download mode contribute to this? The phone works to a degree, it seems, it just won't boot to an OS.
How might I go about troubleshooting the hardware?
(Might as well use this as a learning experience)
Right. Sorry. Just re-read your OP. Still sounds like the NAND is stuffed, which explains why you've tried flashing flashing stock/CWM & phone still won't boot normally. One thing you could try is search for Hopper8's 'Odin troubleshooting' thread, and flash the 3 part firmware linked in that thread. If the phone still won't boot normally after that, it's pretty much a certainty that you'll need to replace the MB at least, which leads to the next paragraph...
Also, if you find the 'booting when plugged into charger but not with battery' thing is still happening even with a new battery, that suggests whatever circuitry is responsible for taking zzz's from the battery & powering the device is (also) faulty/damaged. You could also try the obvious & clean the battery contacts with some isopropyl alcohol. The most common charging/power type problems we see here is the USB board/port dying. But if the phone is slightly functional whilst on charger, it probably isn't that, still might be worth replacing though given how quick/cheap/easy it is to do. There could be a short/whatever causing at least some of the problems, and it wouldn't be the first time a faulty USB board has caused that/manifested itself in less obvious ways than what we normally see (I.E causing the problems you're seeing rather than causing intermittent charging problems or phone rebooting randomly on its own or whatever).
In that case, try the service manuals for the device; these have been posted here before & can also be found with a Google search. They have detailed schematics/parts lists/walk throughs of the most common repairs w/pics, and might help if you want to have a go at fixing it yourself.
Thanks for the response.
I'm in the process of downloading the three part firmware to test later in the night.
Providing that fails, I'll look into part supplies and start researching how I can, if at all, repair this myself.
On the topic of faulty USB boards- I had my phone serviced a few months ago for just that, and it worked fine, but in the weeks leading up to this event my phone HAD been rebooting itself semi-regularly, although I put this down to a software issue rather than a hardware issue. I'll get my hands on the service manual for the I9100 and start reading up.
In the meantime I can just get a cheap burner Nokia that won't play up on me for the next 20 years.
Interesting. In that case, given the other alternatives are more expensive (assuming the 3 part firmware & new battery doesn't fix things), it may just be a case of another dodgy USB board & you might want to start there.
If you can't find the manuals anywhere, let me know & I'll see if I can dig them up from an external drive I have stashed away somewhere (don't have it handy now, but will dig it up tomorrow for you if necessary).
Yep, unlike current technology, old phones like that just seem to work no matter what you throw at them
The three part firmware flashing has moved things along slightly- after it finished the stock SGS2 boot screen appeared for a second or so and while leaving it on the charger it will cycle between showing the grey loading battery and an android with a loading bar underneath, which is progress from before. It is still unresponsive when disconnected from the power- I have procured the service manual and will look into disassembly/diagnostics when I have some small enough tools. I'll still try using a different battery when I can, but it probably isn't the issue.
Clean the battery contacts hard with a pin
Sent from my GT-I9100 using xda premium
all key combinations have failed to produce boot and screen but the vibration responds quickly to the sequenced key combinations. no password issue always seemed to need a reset and extra attention but worked fine until left in partial sun through draped window and was powered on without a cool down. I heard a hiss and though the battery was discharging itself, tried when cool nothing so I put new battery in got a battery icon with low level and would not progress in power from there would not accept the charge . I charged with a new cube led usb charger and data cable overnight got the right results noted above but this time no icon just black screen I dont know what the power level is. I have tried three days charging nothing computer and wall. Tried to make phone vibrate and plug back in no. Windows phone one after mango, have lumia 710 zero problems removed battery twice to reboot phone twice in three years no biggie. Mango 7.5 on 710. want to use 800 as a data phone only would not trust it (mine anyway) for communication. Paid good price for it would like it to work again. Should I try powering it up for a few days? Oh phone always put on a surge protector as all my phones are. I once put phone under my pillow and a few hours later it booted screen came on. Have read people putting hair dryers on them I dont think thats the way to go got me here in the first place. very wonky phone it will and then it wont. I thought maybe usb connection damaged but obviously it is accepting some power and phone responding normally and readily to various key combo prompts but no boot and screen. How might this phone be repaired I would like to know what specifically could be the problem a base power or temp for reboot, what parts I could purchase (out of warranty) all parts inside were connected and looked pristine. No evidence of any heat damage. Used another Nokia battery for this phone new. This phone was let to totally power drain and what I have read that is not good for this phone. Maybe it is only accepting minimal power as before dont know but will try to charge another day to see if any activity occurs but would appreciate any help in zeroing in on what the problem or problems maybe, no software updates if no boot and it should do that if anything.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Register an account on XDA forums for more questions or replies.
Stand by
Good luck
Hi,
words cannot describe how p***** off I am with this phone. I've had it for quite a while, ever since updating it to Android Marshmallow I've faced a lot of issues. Main one being the slugglish speed of the Note 4, and it turning off before it reaches 0% battery life (often in the 15% zone it would turn off) and when the phone did turn off, turning it back on again with the 15% of remaining battery life would just kill itself in a bootloop on the Samsung splash screen, it would not go on and play the Samsung animation but rather bootloop on the splash screen with the model of the phone. After overcoming this issue, (by charging it before it reaches 20%) I still was not happy about the performance and how often the phone would freeze using Facebook. I blamed the app for not being well developed for android Marshmallow on the Note 4 and uninstalled it. However, the phone would still freeze and play up. So I decided to give a factory reset a go and that made no difference whatsoever. I thought it was my battery as that would explain the shut down of the phone before reaching 0% battery life; I ended up purchasing two brand new batteries.
HERES THE CURRENT STORY
Whilst I waiting for them to arrive, I turned the phone off and put it in my drawer hoping that keeping it off might just make a difference. 3 days later the batteries came, after work I came home to try them out on my phone and guess what? The phone wouldn't turn on. I put the other battery in thinking it was just a bad unit but nope, that wouldn't work either. Last resort, I used my previous battery and still... it doesn't work. I put the battery in my external battery charger thinking it was just the USB port that died but the external battery charger charged the battery up and the phone would still not turn on. What's going on? I decided to open up the phone as I've opened it up before hand to repair minor issues that we're easy to replace. Reconnected the screen, cameras, ear piece, charger port... still no luck? Could it be the screen had died? Only one way to find out... test it on a computer and find out what the computer detects it as.
I'm running Windows 7 Ultimate, not many programs are installed but all the essentials for my phone are, USB drivers, KIES, etc... Also, just to add to this I have not unlocked the bootloader on this phone, nor have I attempted to root it. It's just been living a stock life.
I put the battery in my phone, plug it into the computer and it didn't pick up anything.... oh wait... about 10 seconds later it starts downloading a driver. Woohoo! Some relief, but the real question is. Which is at fault? The screen or the motherboard? I was hoping neither... my temper just shot in the sky after finding out the driver being installed was QHSUSB_BULK. I knew exactly what this was, I had a HTC One which I hard bricked and it resulted in QHSUSB_DLOAD. But this? I wasn't so sure, so I googled it hoping it wasn't a full hard brick but just a soft brick, even though hard bricks show no life in the phone. Moments later after researching my PC said the drivers we're installed and the driver was named... "RELINK HS-USB QDLoader 9008 (COM8)" At this point I just lost it. How can I be to blame? I remember 100% that this phone has no attempts of being rooted or modified in any way. I do not have any knowledge on using a JTAG and do not wish to spend so much time and money on a JTAG to fix this phone. Is there no other way around this? How could this have happened? Was it the battery? Or something I replaced in the phone? The only thing I did replace was the dock for the home button, and charger port. Could that have put it into the casket?
Any replies WILL be appreciated.
I had hopes for this community, but looks like it's just time to sell the phone.
Or do some more searching
Seems like it's not completely dead. Pay attention since this a conversation about Note 3, so you'd probably need an Note 4 debrick image
Hope this helps: http://forum.xda-developers.com/showthread.php?t=2720203
Good luck.
Thanks but that's for a Note 3, I've read about someone looking for a Note 4 debrick.img but he had no luck and made one for himself using another Note 4 which I can't afford to buy and see no point in reviving it if I get another...
Note 4 debrick did not work...
Reflashing firmwares did not work....
R.I.P Note 4.