Database Users

Life after death

Okay, so I just got my Hermes on Monday. No less than 4 days later, I accidentally brushed it from my couch to a cup of tea I had sitting on the floor (what luck!). So, I waited a few hours, then tried charging it and turning it on. I then read in several places that you're not supposed to try to turn on a device after water damage because you run the risk of shorting it. I had little hope for it at this point, so I decided to take it apart to give it all a good cleaning with electronics cleaner. So, after taking it completely apart, and giving it a good aeresol spray down with electronics cleaner, I let it dry for 2 days. Today, I put it all back together and tried to turn it on, low and behold it actually turns on! Problem is, its on what appears to be bootloader mode (tri-color screen, dislpays IPL and SPL and just says Serial at the bottom). So at this point, I get slightly happy thinking I may just be able to flash it with the official WM6 RUU. So, I run the RUU, and the Hermes starts showing the progress, it gets all the way to 100% and the RUU says its finished. But, upon Hermes restart, it just goes back to bootloader mode. I tried to hard reset after 'successful' flash, but still restarts back to bootloader screen. Is there any other steps anyone recommends trying to try to bring my baby back to life?

Yoy MAY just need to give it longer to dry out in the nooks and crannies. There may be moisture trapped in micro switches causing bootloader mode to be entered. Possibly try a hair dryer or a fan oven on a very low setting - But be careful obviously. You could also try leaving the m/board on a radiator. (Take all the usual anti-static precautions).
Mike

eek
I had a stupid cat knock over a glass of water on to my 8525 one day.
I immediately pulled the battery, took every thing out of it and set it out in the hot sun all day long (was summer then). By the ned of the day I put it back together and all was fine (thank god).
Haven't had a problem with it related to that incident.

So, I'm reading a lot about mitty.exe fixing problems like these (stuck in bootloader mode), but I can't seem to find out exactly what mitty is, or its purpose. I figure it may be worth a try, although it probably won't work. Can anyone point me in the right direction for mitty info? I've searched, can't find much of a description.
Edit: Okay, from a little more reading, I understand what mtty.exe is, and I see that some non-water-damage-related-stuck-bootloader issues are resolved by using the commands "SET 14 0" and "TASK 8". It seems that the former command is basically like a hard-reset, but I'm not sure what the latter command does. I'll update after I try this later today.

Okay, so did the mtty command and reset, still stuck in bootloader. Tried flashing with official htc at&t wm6. The phone however wasn't shipped with windows mobile 6, could it be that I need to flash it with the original windows mobile 5 that it was shipped to me with? Or is this thing toast.

Stuck at tricolour screen after visit to the toilet..

Hi,
A coworker of mine dropped her Diamond 2 in the toilet. True story!
Anyway, since it was brand new she dried it up and if you switch it on now you get to the tricolor screen. I tried attaching it to my pc, and the text at the bottom changed from serial to USB. I now thought I might have a chance to salvage the phone by trying to flash the original rom. owever, even if everything seems to have worked out fine during flashing, the screen (when ready flashing) turned blank only to go back to the tricolor screen again.
Any one have any idea on what to try next? Is it bricked for good?
The screen shows no sign of water damage whatsoever.
Regards -
/Ballista

BallistaSlim said:
Hi,
A coworker of mine dropped her Diamond 2 in the toilet. True story!
Anyway, since it was brand new she dried it up and if you switch it on now you get to the tricolor screen. I tried attaching it to my pc, and the text at the bottom changed from serial to USB. I now thought I might have a chance to salvage the phone by trying to flash the original rom. owever, even if everything seems to have worked out fine during flashing, the screen (when ready flashing) turned blank only to go back to the tricolor screen again.
Any one have any idea on what to try next? Is it bricked for good?
The screen shows no sign of water damage whatsoever.
Regards -
/Ballista
Click to expand...
Click to collapse
The best thing to do in these situations is to immediately pull the battery and put into a bag of rice to absorb all of the moisture before putting power to the unit thus risking a short circuit.
You may still have water shorting out your hardware keys and its putting the phone into bootloader mode.

My wife put her phone on the kitchen counter, well, it got completely wet. In addition to using rice, I put the rice and the phone in one of the vacuum bags and pulled vacuum, left it in for 2 or 3 days and the phone worked and functioned 100%. 6 months later, still up and running.

Thanks for the answers. I think it is as dried up as it can be though. She have dried it with rice etc. Is there any tip on what to do from the tricolour screen?

Hi,
I maybe didn't understand when the screen goes blank, but since the situation looks pretty desperate why not try to install latest HSPL, it's still a flashing procedure and should end up succesfully if you don't have any hardware damage. If HSPL flashing works, you'll be able to flash any ROM you like, official ones included. Since the device is not yours sorry for the silly question: you have WMDC installed on your pc ,don't you?

The screen goes blank after the bar goes up to 100% on the telephone. I have WMDC installed, but I cant get it to connect to the phone, so installing HSPL will be a problem or?

Edit: Doublepost

If you can't connect to WMDC you can't flash anything,I'm afraid...Any chance to flash by putting the ROM image into the SDcard? Problem is that official ROMs come in .exe format while flash procedure via SDcard needs the ROM image to be in .nbh format..I'm sorry, I'm stuck.

You most probably have a hardware problem, probably a button stuck. Try pressing volume up down repeatedly for example 30 times then try to turn on the device. If that doesn't work you will have to disassemble and dry off your device and check for a shortcircuit or some resistivity in the volume down area. Even if you dry your device on the outside, some water still remains on the inside (I know since I'm an electrician).

Sorry for posting in here - my issue is with an opal but it sounds like a very similar issue.
I tried to clean out the stylus holder on my opal with some washing up liquid on a cotton tip bud. Nothing happened at the time, but some washing up liquid must have got into the phone, as the next time I went back to it seemed to be bricked. I didn't know how to deal with washing up liquid so I disassembled the phone and put it into the freezer to see if that would get me anywhere. I didn't think rice would be much use at absorbing washing up liquid. Anyway, a few cycles in the freezer followed by a cold blast with the hair dyer seemed to have the phone able to get to the bootloader, and able to hard reset.
This is where I am now. Hard resets only get as far as displaying:
ONBL 1.27.000
SPL 1.27.000
GSM 03.29.90
with the 'smart mobility' splash below. That's it - after about 5 seconds the phone turns off. I can keep performing hard resets in this loop, and I can also get the phone into the bootloader 'tri-colour' screen where it shows
ONBL 1.27.000
SPL 1.27.000 (all in the red bar)
and then 'F256' in the green bar
the white bar will change from USB to SERIAL as appropriate.
I thought I'd cracked it when I downloaded the stock ROM from htc, and it seemed to run succesfully. However, once it got to 100% it turned itself off again and I was still only able to either unsuccessfully hard reset, or get to the bootloader screen. I've tried installing the stock ROM through an SD card too, and it seems to work again, but same result. I suspect the phone is a brick now, and there must be hardware damage somewhere important. Any ideas appreciated though.

BallistaSlim said:
A coworker of mine dropped her Diamond 2 in the toilet. True story!
Click to expand...
Click to collapse
It might need re-flushing. hahah

oneplus 2 not working after screen replacement

My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe

Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.

there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..

Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx

Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs

@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.

dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs

Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.

Anyway to retrieve data from a *dead* LeEco Le Pro3 (x727)

I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?

easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
No fastboot or custom recovery ?
Then no theirs nothing really to do
Maybe a battery replacement would boot it up
Sent from my ONEPLUS A6010 using Tapatalk

No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?

easyxpress said:
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
Click to expand...
Click to collapse
Nope it's just a chip on a circuit board
Sent from my ONEPLUS A6010 using Tapatalk

easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.

twistyplain said:
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
Click to expand...
Click to collapse
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph

easyxpress said:
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
Click to expand...
Click to collapse
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.

twistyplain said:
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
Click to expand...
Click to collapse
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph

easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
what happened to TWRP ? thats stock recovery
will it enter fastboot mode ? if you can get into TWRP their is a chance of off loading your userdata to a PC

easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Sent from my LeMobile Le X526 using XDA Labs

twistyplain said:
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Click to expand...
Click to collapse
Sorry bad news.
As twistyplain said, your phone is absolutely fried, and there is no solution.
It's definitely no brick, that is a hardware issue... Most likely shorted solder connections. The same thing happened to two of our X727s, we have one left that still works.
I highly recommend buying a seemingly unbrickable Xiaomi phone. Their budget models are awesome and of course their flagships are awesome. Everyone in my family has Migrated to Xiaomi . I currently have Android 10 working flawlessly.

Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph

easyxpress said:
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
Click to expand...
Click to collapse
If you are in China and located in a large city or tech industrial area you should have plenty of shops that repair at the component level.
Your phone could very likely be repaired by a shop that has a hot air rework soldering station with an electron microscope.
We used to have these types of places in the US but they have all gone out business, replaced by board swappers, who charge a lot. I would suspect that you could get it repaired in China for 100 yuan or less.
I worked in Beijing for 3 months, about 18 years ago and these types of places were everywhere.

Need help identifying Bootloop cause on my M1A1

Greetings everyone,
As the title of the thread states, I have in my possession a M1A1 that is stuck on a Bootloop.
First of all, let me explain the situation a bit. This phone was accidentally put inside a washing machine, lasting inside there for what may have been a good 20 minutes until it was noticed there and promptly removed.
Upon removal it was still showing some signs of life, such as the LED lights going off. My first decision was to quickly open the phone and remove the battery in order to avoid further possible damage. I then decided to disassemble the phone while at the same time removing the water and letting the components dry up in a lit location. Once they dried up, I proceeded to wash them with alcohol, fully bathing the motherboard while giving a slight rinse to the other components, and used a soft brush to very gently clean the slight corrosion that formed in some places. I repeated this process up to 4 times, each time letting the components dry before giving it another go. It is worth mentioning that i was not able to remove the electromagnetic shielding due to the lack of tools.
Upon seeing no more corrosion, I decided to reassemble the phone and test if it was still alive. To my surprise, it did actually turn on. However, once it got to loading the OS, the loading bar got frozen and the phone restarted, resulting in a bootloop. I argued that maybe, somehow, the OS may have been corrupted, and I decided to try to flash a new ROM. I don't exactly remember whether I first tried via Fastboot or if I went straight to unlocking the phone in order to use TWRP, but long story short, I ended up unlocking the phone and therefore wiping all the data, however allowing me to freely use TWRP to flash new ROMs.
In retrospective, that may have been an extremely foolish decision, as no matter which ROM I tried, the result was the same as it previously was: The phone shows the Mi logo, it then starts loading the OS, the loading animation freezes up, and then restarts. So not only did I end up wiping all the data, but I am still stuck with the same problem.
This is my main issue. I do not know how to identify what is causing this Bootloop. The phone is at least somewhat working, seeing as how I am able to fully use TWRP. Is there maybe some component that may have been fried that is preventing the booting sequence? I would really appreciate some pointers. Thanks.

Something similar happened to me using the adriane tool , I resolved it by unpluging the phone from the PC and the forcing the phone off and rebooting into fastboot mode, and when I got it to boot the first boot was slow, A couple minutes maybe ?. I don't know if this can be helpful, I wish I could do more bro.

lionr2 said:
Something similar happened to me using the adriane tool , I resolved it by unpluging the phone from the PC and the forcing the phone off and rebooting into fastboot mode, and when I got it to boot the first boot was slow, A couple minutes maybe ?. I don't know if this can be helpful, I wish I could do more bro.
Click to expand...
Click to collapse
Hmmm, I don't think this approach would work for me. I have tried every possible rebooting combination to no result, but I really appreciate the help man.