Help! Stuck at Splash Screen / Battery damage? - Touch Cruise General

Hello ppl,
since 2 days I've got a big problem with my Polas (at all XDA Orbit 2)
Ok first the bad story. My device did take a little shower and had water in it, which seems to be dried out now.
First, you all should think there is nothing to rescue here anymore.
BUT after the first problems (i will tell you some lines below), later on my device got working again. It worked for nearly a whole day.
And then the same problems as before came back again and now I'm stuck on it.
Here is the scenario:
- Without Power Plug: I turn on the device. It boots up as always. When boot is finished and coming to Windows Mobile, the device tells me "low power" and shuts off directly
- With Power Plug: I turn on the device. Showing the o2 Splash Screen. And that's it. Not even the ROM Version Numbers are showing up. When I take out the Plug after a while, XDA just turns off. Oh and the orange LED is lightened.
I can also plug it in while the XDA is off and it shows the orange LED, so you should think it's getting power.
But it doesn't when I try it afterwards without the Plug.
When I boot up without the plug, and plug it in after the Splash Screen, it's the same behaviour as on the scenario "Without Power Plug", it doesn't recognize that the plug is in or is not getting power I don't know.
So why was it working for one day? I don't get it!
You think that maybe only the battery is damaged? But why was it working?
I hope this text is not too confusing and maybe somebody is able to help.
I'm dying without my lovely device.
Oh and yes, i did try a hard reset.
I think the biggest problem for me is, that the device doesn't boot when the plug is in. That is totally weird from my perspective.
Thanks in advance!
gmc

Weird! I am able to flash the ROM. But still the same ;( What the hell?
While flashing the ROM there was no sign of a not working battery.
I'm confused!
Update: Re-Flashed O2 Rom and also tried udK Diamond. Flash is always successful but behaviour doesn't change or get fixed ;(( This can't be true.
Well one question... when the version numbers show up on the Splash Screen what is the "G"-Number? It looks a bit weird, "25.69.30.05H"
Maybe that part of the ROM is down?

gmc said:
- Without Power Plug: I turn on the device. It boots up as always. When boot is finished and coming to Windows Mobile, the device tells me "low power" and shuts off directly
Click to expand...
Click to collapse
I had this problem too, so did some other guys, Check out this thread:
http://forum.xda-developers.com/showthread.php?t=381442
Don't know how/if others managed to solve it but in my case only the replacement of my motherboard (under warranty) solved it.

satfly said:
I had this problem too, so did some other guys, Check out this thread:
http://forum.xda-developers.com/showthread.php?t=381442
Don't know how/if others managed to solve it but in my case only the replacement of my motherboard (under warranty) solved it.
Click to expand...
Click to collapse
Thanks for the link. Will check it out. As there is no more sign of water damage on my device, i hope i can use the warranty too.

Related

HELP!!!Impossible to charge the battery,permanent RED Led

As i said on the title,suddenly i couldn't recharge my Universal anymore,yes i've tried with a brend new official battery as well but everything was in vain.As soon as i plug my charge to my Universal it appear a Red Led and after 3 min or so the led turn off and so the battery.
How can i fix this problem?!
Is there any chance?!
Is it really dead like that?!
Please HHHHHHHEEEEEEEEELLLLLLLPPPPPPPPPPPPPPPPPPP!!!!!!!!!!!!!!!!
If the battery is really brand new, then I guess the connectors might be damaged or the internal power buses might be broken somewhere. Have you dropped your device recently? Or did anything that might explain broken connectors or internal buses?
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
tetsuokaneda said:
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
Click to expand...
Click to collapse
It can be a software error. Have you tried hard resetting or installing another ROM?
tnyynt said:
It can be a software error. Have you tried hard resetting or installing another ROM?
Click to expand...
Click to collapse
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
tetsuokaneda said:
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
Click to expand...
Click to collapse
Your battery is fine, unfortunately your device broke
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
mzalan said:
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
Click to expand...
Click to collapse
I wanna die!!!I'm completely Fu.. up!!!
What a terrible news!I can't believe it!!!!
If i'll bring my phone to the assistant i'm gonna pay alot of money,at least 200.00 euro!!!!
similar problem
i had the exact same thing happen to my EXEC when i got 2 new batteries for it. One was a standard sized, pretty much the same as the stock one that came with the phone and one was a much larger capacity one that needs an extra cover for the back.
Id been using the device for ages on this huge battery and the charge said 100% constantly. then the device turned itself off and it wouldnt come back on. upon connecting the charger the LED was red, so i thought the battery was dead. I left it on charge over night and when i tried again the next morning it was fine.
this happens everytime with this battery, it just needs a much longer charge than the standard one, and doesnt register properly on the default OS, i havent tried it on my recent upgrade to one of the midget roms.
so try leaving it on charge over night or for a very long time. if all else fails just get a new battery.
That might reset the battery back to life, but I wouldn't exactly count on that. A battery with a broken monitor circuitry is pretty hard to reset.
My last hope,i'm gonna leave charging my phone for a day and then see what happend....I'm desperate
Permanent red light...
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
wtpelzer said:
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
Click to expand...
Click to collapse
Could u post it please?!
Took a while but here it is...
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Same Problem, Led Indicator Always red
Hi,
We have the same situation, my jasjar just died in my hands, im reading a txt messages then al of the sudden it hangs, so what i did is reset it but it didnt power on, i removed the battery then after 10mins i put it back but then no power,then i charged it but it didnt power on too and the led indicator is always red, they say that if the indicator is red it means that there is no battery or the battery is missing but i check it thoroughly,the battery is perfectly place on the back of jasjer, i even tried to enter to bootloader but it cant. If anyone knows how can i revive my jasjar pls pls let us know....Thank you so much.
So sad till now there's no single solution.....
wtpelzer said:
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Click to expand...
Click to collapse
Exactly if my Jasjar is completely dead how can i connect via usb and then use mtty?!
I'm losing my hope to bring it back to live!
have same problem - can do nothing, still waiting
but there is one thing - led flashes once, when i put the charger into the device - but it does nor light, nor flashes - exactly nothing happens
If your device is dead...
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
wtpelzer said:
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
Click to expand...
Click to collapse
The point is that the device is dead and that is why the constant red light. I have a device that is stuck on the splash screen (no solution in sight) and another that fell down and broke. The one that fell down does not power on. If you put a charged battery ang plug in the charger nothing happens, no light comes on, but if you put a discharged battery the red light comes on. I have a third Uni that I accidentally flashed with a BA rom. It is behaving exactly like the broken uni, it does not turn on, does not go into bootloader and the red light comes on when I plug in the charger with a discharged battery in it.
For some things, there's just no cure...
Okay I understand where you're coming from but essentially what you need to do, under normal circumstances, is connect it to your PC, which if the device is working at all the PC will detect it but not connect... In the case of two of your Uni's I don't think this will help - the dropped one and the BA ROM failure. The one with the Red LED, which has stopped working could be a component failure on the board or it could be a Corrupt DOC table. Now to get back to how you'd go about fixing it if it is a corrupt DOC table, when you connect it to the PC and the PC detects it you disable ActiveSync and start MTTY it should give you the option of connecting to the USB port, when it does this if you get a prompt the problem should be fixable because MTTY can "talk" to the device... As for the other's try this method and if it doesn't work sell them for parts or canabalise the one for parts for the other...

[Q] Bricked? Or just battery acting up?

Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?
Hi guys,
i have exactly the same problem, already have tried all of these solutions, nothing have worked for me... Please help.
PS:sometimes my screen lights up <black totally, but lights up>... when plugged into usb cable or charger... but not now anymore...
I have bought this phone in china, there is S/N but i guess that here in UK i cannot do anything about it since HTC's warranty is not global...
listenger said:
Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?
Click to expand...
Click to collapse
Have you tried a different battery?
I just ordered a new battery... Takes a couple of days before I recieve it
listenger said:
I just ordered a new battery... Takes a couple of days before I recieve it
Click to expand...
Click to collapse
Also keep note of which recovery you are working off of. There have been charging issues with certain recoveries.
Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/
listenger said:
Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/
Click to expand...
Click to collapse
I would suggest to go to a store that sell's the Sensation and ask if you can test one of their batteries out to see if your phone has either a battery issue or something else. If you are stateside, of course try a tmobile store, but without knowing where you are located, this is a hypothetical at this point.
I know I had an issue with my Nexus1 not booting up from a kernel I had flashed. But I noticed my charging led was flashing three times and then stop. I researched this here on xda and found that it just needed to be put into recovery again somehow. I ended up just plugging the phone into the wall and remove the battery. Try to power it on there and then reinsert the battery and try the power + volume down button. That time it booted for me. But again, this was for my Nexus1 not with this phone.
same happened to me, sent to HTC and had main board replaced, lcd, flex cable etc. the driver the phone looks for is the equip HTC use to jtag... I am not sure if this is a hardware failure or boot corruption...but even though it was s-off via alpha rev it was that damaged they didnt complain... i say hardware failure. the thing is even when i have s-off i didnt change the rom. I have a riff box on order so if this happens again we can surely see if this failure is software or hardware..
Yeah, do what kpjimmy said; go to a store where Sensation's are sold and ask if you could use a battery to test it out to see if it's bricked. It it's not, you'll need a new battery (try getting one for free from HTC, citing warranty. I did it with my battery cover). If it doesn't work, you're mostly likely bricked, unfortunately. Refer to anarchy's post for more info on that side of things
Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?
arifafzan said:
Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?
Click to expand...
Click to collapse
Havn't had the time to really do any custom ROM or the like, so the phone was all original from the factory...

Nexus S 4G hard bricked!! want to restore

i have a nexus s 4 g from sprint. it is hard bricked. i tried to root it and change recovery.then it shut off and wont power on, light up at all. I would like to know if i am able to achieve download mode, what do i need to do, what files and how to install to return this phone to stock?? please help!!!
Take out the battery for a few seconds and put it back; then while holding Volume UP (+) press the Power Button.
See what happens...
One helpful tool is found here:
http://forum.xda-developers.com/showthread.php?t=1984849
kozmo2k4 said:
Take out the battery for a few seconds and put it back; then while holding Volume UP (+) press the Power Button.
See what happens...
One helpful tool is found here:
http://forum.xda-developers.com/showthread.php?t=1984849
Click to expand...
Click to collapse
Nothing. Happens it don't light up or power on at all. It is not reconized on computer either. It's hard bricked.
Make sure the Battery is charging...
How can I make sure the battery is charging when no lights come on at all? All I do know is I had it plugged in for a while yesterday and it got really warm. But no lights whatsoever. The screen doesn't light up at all neither does the led.
??????
There are no notification lights on the D720, but when you plug it in with a charger, you should see a battery bar on the display.
Other than that, you are probably right about hard-brick.
I, luckily, never had a "brick" on the Nexus S, so someone else with experience may wanna chime in. But Google and YouTube are your friends.
Sorry...
Sent from my NookColor using Tapatalk 4
Hey man, did you have any luck with this? I'm experiencing the same problem.
Talal916 said:
Hey man, did you have any luck with this? I'm experiencing the same problem.
Click to expand...
Click to collapse
Please help me, i have the same problem
been awhile since any action here. saved mine with JIG method once but this time it won't work ??!(why) , in search of a solution again! -> hardbrick #2 on this device!
You guys can try a USB Jig. If that does not help, I think JTAG is what you need.
Jesus... just to revive this thread (and this concept of hard bricking), I think I just accidentally bricked mine as well.
Here's exactly what I did:
One moment, it was working spectacularly - fully stock, but unlocked. I had just listed it on eBay, too.
So I ran a factory reset on it (from the Settings menu), also "erase USB storage".
Then, after it shut down for the reboot, I pulled the battery.
...
That was it. Now it doesn't turn on for anything whatsoever. No device detected on USB when plugged into PC. Remove, replace battery, hold VolUp+Power, nothing. Plug into power adapter, nothing. Nothing at all.
But the back does get lukewarm after a minute or so, as if it's alive in the head but frozen, unable to start the bootloader.
WTF? I also have 2 more of these Nexus S 4G's, and both of them seem to have Flash storage chips that exhibit the same behavior when their chips are placed in (this) working motherboard. They can't boot. When I try to "hot-flash" it by booting the bootloader then swapping the Flash chips, they can't flash anything (this is probably to be expected). So, if I can get my ONCE-WORKING phone back to life, there's a good chance I can get another working as well (one just has a cracked glass, otherwise working mainboard & peripherals).
It's old, yes, but it's a damn shame to E-waste these things for a stupid software problem like this!

Nexus 5 new screen is not working anymore

Hello,
I had an accident and after that my Nexus 5 screen was broken. So I decided to buy an new one from Amazon (~60$) and I tried to replace the screen on my own.
Yesterday I replaced the screen with a YT-Video, then I charged my Nexus 5 an the "Charging-Symbol" showed up.
After that I left the house for 2 hours and when I came back (I left the Nexus at home for charging ofc.) I tried to turn on the phone and nothing happened.
Then I tried to press power and volume down to get into the boot-menu and this also worked and the screen showed everything perfectly (!) and then I tried to start my handy from the boot-menu.
Until then everything has worked well but during the start progress I noticed that the (starting-)animation is really slow and laggy, so I decided to try to reboot my phone by holding power off for around 10 secs.
I tried to start my phone one or two times more and tried to get into the boot-menu, restart bootloader, etc. and then I realized that my phone didn't even want to work anymore. I could(and can) neither get into the bootmenu nor simply start it...
Do you have any ideas?
What suprised me the most is that it stopped working so quickly, so I concluded that I replaced the screen right but anything else went wrong...
Please help me :/
PS:
USB-Debugging is turned off and I cant access my phone with my pc or anythin else
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
audit13 said:
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
Click to expand...
Click to collapse
Thanks, now I could get into my phone and enable USB-Debugging with much lock D)
My problem is, that my phone runs very unstable and shuts down often so I can't really work with it.
Do you know any solution and the more important question:
How can I save my data? I think, that I can save it anyhow if I enabled USB-Debugging with the bootloader and a pc, can't I?
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
audit13 said:
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
Click to expand...
Click to collapse
I have now moved on!
My charger cabel was broken but now I got a new one!
I can start my Nexus (with some issues) and it runs but sometims it still shuts down and always when I try to plug in my cabel into the Nexus the screen gets black (but on the side you can see that the screen is light up in some way, idk...)
Is there a reason for the heating and for the shut downs? :/
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
audit13 said:
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
Click to expand...
Click to collapse
And that means what?
And can I do anything for it? Maybe flash it or something?
Reset, etc..
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
audit13 said:
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
Click to expand...
Click to collapse
Yeah first sentence makes sence..
I swapped software and hardware, sry
my other screen doesn't work at all, completly destroyed...
The problem is that I can't imagine what should be the failure...
And yeah, I already tried disassembling and re-assembling it...
Still same problem
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
audit13 said:
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
Click to expand...
Click to collapse
Nahh but the screen works I think..
Everything looks clear etc and the screen wasn't really cheap with 65$-70$ I guess..
I think it's something else because my phone gets really on near the CPU and this can't be because of the screen...
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
audit13 said:
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
Click to expand...
Click to collapse
Yeah, I also thought about a short-circuit but I don't know how I can test this.
When I try to start my phone it fails like 4-5 times and then it works most of the time. The fail looks the following:
The "Google" logo appears and then suddenly the screen gets black, but not the "out"-Black (so that screen it out), I mean the "on, but black"-Black (hope u can understand.. xD)
During this 4-5 Tries my phone feels like 40°C-50°C (sry im from Germany, idk the conversion to °F value.. )
After this (I got the phone running one time for about 20 minutes) the phone doesn't heat up so much, if it starts right I think that the temparatur problem is over, but there is still the problem (also if the phone is running for 20 minutes) that it suddenly shuts down... :/
Sorry, idk much about canadian dollar, like I said im from germany and I payed around 65€
Google says, that this is around 67 (US-Dollar)
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
audit13 said:
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
Click to expand...
Click to collapse
Mhh, ok :/

Is my phone dead after falling on the floor, need confirmation.

Hey guys,
After two years of constant care, it happened... the drop of death.
A perfect hit on the floor, screen first, perfectly parralel to the stone floor, with the neat "Poc!" sound... :crying:
My phone now does not turns on. Does not vibrate when I plug it and the computer does not detect it.
That's a perfect brick.
I disassembled it and re-assembled, in case of there was a loose piece or cable, but without success.
Is there any chance that it's only the screen, or is it, as I suspect, the end of my beloved OPO?
Thanks for your advice.
Anghirrim said:
Hey guys,
After two years of constant care, it happened... the drop of death.
A perfect hit on the floor, screen first, perfectly parralel to the stone floor, with the neat "Poc!" sound... :crying:
My phone now does not turns on. Does not vibrate when I plug it and the computer does not detect it.
That's a perfect brick.
Click to expand...
Click to collapse
What was the state of the device before it fell?
Mr.Ak said:
What was the state of the device before it fell?
Click to expand...
Click to collapse
Perfectly good.
Anghirrim said:
Perfectly good.
Click to expand...
Click to collapse
Anyways,I'd recommend you to get it checked from a professional repair shop.There're chances that you might only need display to fix your device.
Mr.Ak said:
Anyways,I'd recommend you to get it checked from a professional repair shop.There're chances that you might only need display to fix your device.
Click to expand...
Click to collapse
Yep, will do.
Mr.Ak said:
Anyways,I'd recommend you to get it checked from a professional repair shop.There're chances that you might only need display to fix your device.
Click to expand...
Click to collapse
Well well well.... small update.
The phone is finally partially alive.
I just tested to plug it without the battery in and.... I had the small vibration and OnePlus boot logo. But of course, as no battery, the screen turns black right after.
But.....
If i plug the battery in, the phone will turn on (I did not say Android booted ).
But only if:
- I plugged once without battery, then unplug
- I put the battery back in place
- Then I re-plug the USB cable
Following this, I can:
- Enter TWRP (fully functional, I can backup my rom, wipe caches, etc... and all the buttons I tested were OK, touchscreen seems fine) / (Vol down + plug)
- Within TWRP, ADB sees my phone as an unauthorized device.
But I can't:
- Enter Fastboot mode (Vol Up + plug)
- Boot the phone up:
- Even within TWRP, reboot does not work
- As long as the battery is in, if I power off the phone, it won't turn on again until I remove the battery and do the first plug trick first.
So there is hope!!
Can it be the battery?
If I am on TWRP (with both USB cable and battery plugged) and unplug the USB, the screen stays on, but becomes unresponsive and only removing the battery can turn the phone off.
Or is the phone somehow bricked on a software standpoint? And can be unbricked?
Side note, when I first plugged the phone and it turned on, on the Computer, it installed a driver called "Care Suite Emergency Connectivity"
Anghirrim said:
Well well well.... small update.
The phone is finally partially alive.
Click to expand...
Click to collapse
Replaced display?
Mr.Ak said:
Replaced display?
Click to expand...
Click to collapse
No, just tried out without battery. I did but that's tricky. Once you remove the battery, you really need to push the power button first before plugging in the cable, seems the mother board needs to discharged in some way first.
I called a repair shop, the battery might be faulty and put the mobo in security mode... But as I can't access fastboot mode, they said it could be a part of the phone's ROM which is damaged.
Any way to use adb through TWRP to try to dump all partitions to see if any of them are damaged?
Anghirrim said:
I called a repair shop, the battery might be faulty and put the mobo in security mode... But as I can't access fastboot mode, they said it could be a part of the phone's ROM which is damaged.
Click to expand...
Click to collapse
So,you're trying to say display works fine atm? After such a drastic fall?
Mr.Ak said:
So,you're trying to say display works fine atm? After such a drastic fall?
Click to expand...
Click to collapse
Display works perfectly fine at least under TWRP.
The problem is somewhere else, maybe on battery or ROM (not the OS)
Anghirrim said:
Display works perfectly fine at least under TWRP.
The problem is somewhere else, maybe on battery or ROM (not the OS)
Click to expand...
Click to collapse
Could be battery.
Mr.Ak said:
Could be battery.
Click to expand...
Click to collapse
Quick update.
There must be a problem with the mobo.
I ordered a new battery that arrived today.
With the new battery, the phone boots up Android, but after some time, it freezes completely.
If it does not freeze and if I try to power it off or reboot, it just shuts down and will never reboot unless I do the battery trick again (remove and put back in place).
SIM is recognized but I don't have network.
I did not manage to get a GPS fix.
Fastboot works, I flashed the stock LOS 13.1 image. But it did not change to the freezing behaviour, and even under fastboot, a "fastboot reboot" just powers off the phone.
That's frustrating!!!
I think it's dead for good. The only reason I see for such a strange behaviour is a shortcut somewhere on the MOBO, maybe a damaged soldering.
Anghirrim said:
Quick update.
There must be a problem with the mobo.
I ordered a new battery that arrived today.
With the new battery, the phone boots up Android, but after some time, it freezes completely.
If it does not freeze and if I try to power it off or reboot, it just shuts down and will never reboot unless I do the battery trick again (remove and put back in place).
SIM is recognized but I don't have network.
I did not manage to get a GPS fix.
Fastboot works, I flashed the stock LOS 13.1 image. But it did not change to the freezing behaviour, and even under fastboot, a "fastboot reboot" just powers off the phone.
That's frustrating!!!
I think it's dead for good. The only reason I see for such a strange behaviour is a shortcut somewhere on the MOBO, maybe a damaged soldering.
Click to expand...
Click to collapse
Hmm,could be the pcb itself then.Did you get your device check from a professional repair shop?
Mr.Ak said:
Hmm,could be the pcb itself then.Did you get your device check from a professional repair shop?
Click to expand...
Click to collapse
No, but I discussed with two of them on the phone.
Considering the price of the phone, it's not worst anymore to repair PCB if it can be.
I will go for a Oneplus 3 I think. There is an auction ending on eBay soon and it's still at 170€... And with the 5T coming out, there will be a lot of other good options in the coming weeks.
I have the Oneplus 3 now... Thanks @Mr.Ak and see you guys!!

Categories

Resources