I need help to boot pls (broken button/old rom) - OnePlus 3 Questions & Answers

Hi,
I've got an old OP3 wich my son is using. The problem is that the power button is broken/not working. Last update was made years ago (maybe 4 or 5..), and there is "Tipsy rom" installed (Android 7.1.2 ).
So when battery is empty for instance, to put the phone on I had to put the phone on charge, and then the screen(s) appear(s) that it should "boot in 5 sec" (see attachments). It did work before, but doesn't anymore... ! Don't know why.. ?!
I've searched how I could do but I don't find an answer.
To be clear : adb is enabled but the phone isn't recognized (or only while in recovery) so I can't use code lines (I also tried in different usb slots / on different pc). And when I put it on charge, I still do have the boot screens that say "if no key pressed : your device will boot in 5 seconds", but instead the charge screen appears (with battery charging). I've tried to disconnect the battery, the volume button, the motherboard.. with always the same result.
Could someone please be kind enough to give me advice on how to boot the phone ? It'd be really appreciated !! Thanks.. !

It is difficult to assess the situation without carefully checking the operation of the switches, whether current is passing or not. If they are not damaged, the cause may be a defective electronic button controller on the motherboard.
Since it is currently not self-starting, there could be more causes.
I suggest replacing the switches with working ones. This will be the first,cheapest and maybe the only option for diagnosis.

ze7zez said:
It is difficult to assess the situation without carefully checking the operation of the switches, whether current is passing or not. If they are not damaged, the cause may be a defective electronic button controller on the motherboard.
Since it is currently not self-starting, there could be more causes.
I suggest replacing the switches with working ones. This will be the first,cheapest and maybe the only option for diagnosis.
Click to expand...
Click to collapse
Thanks for your reply !
I didn't test if current goes through because the battery must be get out to check it (I removed batteries before and had "bent" ones often). So you're right I don't know if it's the button switches/cable, or worse (contact/motherboard...).
That said, I would like to try to find a way to "force" boot, for exemple I've tried to hold volume button while/between/after boot screens appear, but yet I always come on the screen wich allows to choose from "power off, restart, recovery, fastboot mode"... (with volume button). I don't understand why it rebooted before (like the screen says "after 5 seconds") as it worked well before but refuse to now..
I appreciate your input, many thanks ! If you've another idea... ? . Thanks anyway !!

Related

My universal is a brick!

Hello everyone, my first experience of upgrading the firmware is sadly failed and now my beloved m5000 is only a beautiful paperweight!!!
No key combination could start the bootloader nor soft or hard reset works.
When I connect it to mains charger, the right led goes red for few seconds and then goes off...
In the service manual I have read that this signal means hardware failure but because the fault is the consequence of a failed upgrade I don't thing that it is really broken.
I already tried to contact htc and orange for repairing but in Italy where I live it seems that the warranty isn't valid and services are very scarce.
Someone have an hint?
Thanks.
Try to do a hard reset, many manage to get that white screen.
Thank you for the suggestion but it doesn't work The phone is completely dead, except for the red led. Any key combination including hard reset simply doesn't work.
I suspect that the only way to resurrect it is to reflash using a jtag interface.
But unluckily I don't own the pinout!!!
take a look here: http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen for instructions on how to use the mtty utility to bring your device "back to life"
There's additional information on the mtty utility in this thread: http://forum.xda-developers.com/showthread.php?t=259003
hope this helps
If you are on the bootloader menu...
Try to flash again a complete rom + extended rom + Radio
SOmetimes it can work again
sigh... thanks to everyone but I can't reach the bootloader menu: the uni is bricked!
My only hope is to find the jtag pinout...
Try holding down Light + power for at least 5sec. and while still pressing, do a soft reset.
If you dont go to BootLoader then try to increase the Hold down Light + Power some more.
This worked for me, could again get it active on usb and ran my original rom upgrade while it was in BootLoader mode.
If that dossent work, try the bootloader upgrade version at
http://wiki.xda-developers.com/inde...tion On How To Upgrade with Bootloader method
You can do the same with the two - - buttons, holding for more than 5sec. then soft reset. Should bring up the Reset with 0 or X to cancel.
But it just reverted to a brick every time for me with this.
BTW. do this with USB or Power Cable plugged in!!
another possibility is that your battery is low enough not to allow booting but is still able to light up the LED. it happened to me a few times that i was thinking it was completely gone and it was just low bat. remember that if you have a non booting device it may not even charge the battery anymore so you'd better ask a friend to lend you a charged one, just to be sure.
cheers!
Ill Buy The Brick!
au$200.00 in your paypal account upon a sale +50 to Australia.
Let me know...
Simon
Still Charging
I have 2 wizards and a universal... By mistake, i have tried to upgrade the G3 wizard but pluged the G4!!!!!...... So now i have abricked G4 wizard. Now when i plug the G4 it does NOTHING, it is completly dead, BUT is still charging the Battery!!!! I am sure of this because i have tested the battery in the other device.. So try the same on universal plug it in and wait a few hours it may charge the battery.
anyway, if you can't unbrick it, do me me know if u're selling it.
need some spare parts.
Suggestion
What you can also try is remove Activesync from your desktop, Restart your desktop, install Activesync again and connect your device.
It's word a try! Has something to with rapi.dll!
Cheers...
Leo
My failure...
Hello everyone, I've tried all yours suggestion one by one and step by step but without success.
My last chance to not consider this phone a complete loss is to sell it as spares/repair...
Does someone is interested?
P.S.: notwithstanding the phone is bricked it still charge the battery
Try holding the the two - softkeyes for longer/shorter time before you softreset while still holding them down.
Also try different intervals with the softbuttons while holding the Power + Light down, also with soft+Light & soft+power & power+light
all with different intervals.
Look closely at the screen after each try, to se if it goes to bootloader mode.
And remove SD card and Sim also.
I Hate Bootloader!
I have tried ALL of these power+light+reset suggestions and I STILL can't get into the damn bootloader menu! I just gave up and rip apart my JasJar every time I want to update it. For some reason the only way I can access this menu is by pulling the main battery and disconnecting the smaller(watch battery) one in the upper right hand corner and letting it sit for a couple of hours.
Come to think of it, when I use even the factory updates I don't even get a report on the update screen telling me what my current config is! So then I hit update anyway, the unit turns off, I lose my USB connection, it no longer charges, and I have to take the battery out. Almost like the PROGRAM can't even get it into the loader! This is probably how I learned to just yank the batteries when I want to upload.
Unless there is something different because I have an earlier model... I have no clue. Does the unit need to be running or something when I do this? I think this is a fairly elementary task but it just doesn't work. Has this happened to anyone else?
Yes, all my buttons are in working order = )
BTW after my last tear-down I have -
Bootloader: 1.01
Rom version: Ivan-2.60.00WWE
Rom date: 12/20/06
Radio version:1.14.00
ExtRom version: Modified
http://forum.xda-developers.com/showthread.php?t=247440&page=14 I think someone already suggested this, but just in case...
No chances
Well, today I've verified my battery and it works like a charm in the uni of a friend. Then the last possibility is gone.
Someone knows how to go ahead any further?

My Universal Dead . Please help...

Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.
Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.
I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?
I've tried whatever i can do. Hard reset is useless too.
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps
Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.
Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…
It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen
lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...
I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.
Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.
Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.
yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.
I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)
got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]
http://forum.xda-developers.com/show...6&postcount=52

a very strange hard brick

Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )

[Q] Endless reboot loop even when trying to enter recovery

One beautiful day the phone just restarted from itself. (wasnt really shocked though) After that it entered again into a boot loop, Im saying again because it happened once before and i noticed it was the SD Card and I just had to format it. So far so good, but now it doesnt matter if I pull out the SD Card or SIM, even battery... once ive put the battery the phone starts booting from it self and restarts everytime on a different place, like samsung logo, CM logo, CWM recovery, download mode.. it just cant stay on one place so i can choose an option. Only once ive managed to do a cache and dalvik wipe, also didnt help. Keeps rebooting and rebooting. Ive tried different ways of booting, with USB cable, with the recharger adaptor and without them. Left it for a whole night without battery, didnt help. I cant even manage to flash the stock ROM again, still reboots. I thought the power button was stuck or something, tried moving it arround but also didnt help. If you ask how many time Ive flashed the device... well perhaps countless, about 40 times counting the stock firmware. (maybe this number for some other maniacs is little, but now i see it like too much, because im kinda attached to this phone, the previous HD2 suffered a lot more xD) So guys my question is, do you have any suggestions? Ive searched the internet to check if the symptoms are close to hard brick but... didnt really saw any identity.
So.....
Normal boot.....it reboots, shuts off reboots.......?
Recovery mode.....reboots, shuts off, reboots.......?
Download mode.....reboots, shuts off, reboots......?
Battery insertion.....reboots, shuts off, reboots.......?
Same sequence every time?
Irrespective of which of the above scenarios is taking place?
If you just sat and watched it without pressing any buttons, will it endlessly reboot, shut off, reboot?.....
During this cycle, does it get to the same point in the boot process before restarting?.....
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
So.....
Normal boot.....it reboots, shuts off reboots.......?
Recovery mode.....reboots, shuts off, reboots.......?
Download mode.....reboots, shuts off, reboots......?
Battery insertion.....reboots, shuts off, reboots.......?
Same sequence every time?
Irrespective of which of the above scenarios is taking place?
If you just sat and watched it without pressing any buttons, will it endlessly reboot, shut off, reboot?.....
During this cycle, does it get to the same point in the boot process before restarting?.....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I thought nobody will answer. It reboots right after passing 3 to 5 seconds, sometimes on the CM Samsung splash, sometimes on the spinning CM circle(boot loading image), when i succeed entering CWM or download mode reboots again. I cant boot it normally and reach the home screen. I read something that it could be from the kernel boot code, im using CM 10 (if im not guessing wrong).
I've answered a number of threads in the XDA W forum where members were experiencing similar issues to yourself. I doubt it's software related as during access to download mode and recovery mode , the phone isn't even using the "main" system software and kernel....these modes use their own independent kernel and system (it would be HIGHLY unlikely that two separate systems and two separate kernels are suffering from the same fault).
If all of the symptoms I wrote about in my original reply apply to your phone, then it all points towards a faulty power button.
As I understand it, Samsung uses a type of button commonly referred to as "temporary push to make" which means that when you push the button, two contacts are bridged to make an electrical connection but when you release the button the contact is broken. Under normal circumstances, this "make, break" sequence will start a normal boot sequence. Under normal conditions, long pressing this button again will begin the shutdown process. Now assume for a moment that the button has become damaged....where this contact that is meant to be momentary, has in fact become permanent......the result would be a phone that will attempt to start up and shut down in an endless cycle....basically, YOUR phone........
Sent from my GT-I9100 using Tapatalk
Yeah, I also thought that as a reason but discarded it quickly because the button doesnt have any problems when pushing it. I mean it freely comes back when pushed and i can also freely push it without problems. Also discarded that problem because i thought the button cant stop the booting cycle while booting, but it seems like it can. Thanks for all the answering I will try fixing it and will report as soon as possible.
The plastic button is separate to the electrical part I described....so it is entirely possible for the part you normally touch to *seem* to be working as it should.....only for it to work against the faulty electrical part........
And yes, that type of fault IS caused by the permanent contact of a faulty electrical button. Anybody who has a normally booting W (as I do) can re create this fault simply by pressing and holding the power button......the phone WILL enter a boot/shut down/reboot cycle for as long as the button is held........
The same condition can be re created on my S2 in exactly the same way as well.....
Sent from my Infected KitKat bar.....
Well.. bad news.. i've managed to disassemble it, tried to see whats wrong with the button (not the plastic one), tried moving it arround, nothing seems to be damaged, still stable at one place, also tried booting the phone 3 times without any covers and the result was the same...
Perhaps i should drive it to service.
Check your date of purchase.....Samsung phones have a two year warranty.......
Sent from my Infected KitKat bar.....
Well bad luck here also, i got it almost brand new from England and I'm not from England. I bought it over online shop sold as a second hand long time ago, it was just a matter of time to damage him. Thanks anyway for all the help, I'll see what i can do with the service.
Bad luck mate.....word of caution though.....as you've found out, the button is soldered directly to the motherboard, Samsung's "modus operandi" seems to be rather than attempt to repair the button, simply replace the entire MB........for a phone that is outside warranty, this will have (erm) "cost implications" lol......basically they like to charge as much as they can in situations like these.....eg/ board replacement when button repair would be enough.....
Sent from my Infected KitKat bar.....
keithross39 said:
Bad luck mate.....word of caution though.....as you've found out, the button is soldered directly to the motherboard, Samsung's "modus operandi" seems to be rather than attempt to repair the button, simply replace the entire MB........for a phone that is outside warranty, this will have (erm) "cost implications" lol......basically they like to charge as much as they can in situations like these.....eg/ board replacement when button repair would be enough.....
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
True, my phone suffered the Power Off Loop as you may know from my previous thread. I decided to send my phone to a couple of repair shops and they said that the phone "cnt be repaired". i thought they knew about the change of MB but no. So rite now, my Galaxy W is in the grave ...
Sent from my GT-S6500 using xda app-developers app
i had encountered this issue with my galaxy wonder today and would like to seek for solutions over the internet. regardless that i also checked the button by disassembling the covers and separated the plastic button with the one on the board and tried to boot it but it still the same.
as most of you guys experienced this issue, what would you guys suggest me to do with my phone? i wish to save this phone for sentimental reason. would change the button DIY-ly is worth it? is it available for me to get the parts?
or did you guys manage to get a better solution?
thanks!

Random crashes - unless power button continuously pressed

Hello all,
after leaving the tablet for 1y I gave it another try and am seeking on one hand some general advice how to proceed, or possibly specific if somebody had that bizarre behavior or something similar.
The problem is mostly described here: https://forum.xda-developers.com/t/my-sm-t800-will-not-boot-normally.4016731/post-82060775
Now I fiddled with it a bit more and the status is:
- switching it on causes it to crash at arbitrary stages: directly after the samsung logo, while showing the lineage os logo, right when ready for using, any time later, sometimes it is even possible to use it for hours
- it works almost reliably when I keep the power button pressed
- entering download mode is possible without problems
- entering recovery mode works only sometimes, in most cases only with power button pressed continuously
- when it works "normally" I can enable dev options, connect adb and do whatever I want (as it seems)
Now since the device is fairly old, I want to avoid major investments, however I still have some hope that there is a way to fix it. However, I'm a bit ouf of ideas ...
Any suggestions how to proceed are very appreciated!
I know this reply is one month late, but I think I know the reason and fix. The exact behavior happened to my T800 but I was able to fix it after viewing this video:
It is the power connector to the motherboard, which is apparently not soldered. Once I have soldered the pins to the motherboard. All is good.

Categories

Resources