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.
Related
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.
I have a developer unlocked Focus that is currently running 7004. It was dropped in water and I assumed it did not work as all it would give on boot is the connect to PC icon.
Earlier today I was thinking "Hey I should get a second battery" Well I remembered that other 'broken' Focus and I plugged it in. Mistakenly I was holding the camera button as it took a picture and brought me to the camera screen. This allowed me to exit and browse through the phone as normal. Everything worked as normal (Aside from there being no SIM) I could even browse the marketplace.
I decided to test the apps to see if they'd work first Facebook (no good couldn't update stuff even though I was on WiFi) and twitter. After writing a tweet the phone locked up and reverted to the connect to PC screen. Now the hardware buttons do not respond (Back, Home, Search, Camera will focus but won't take picture)
Short version:Now whenever I boot up it goes to the connect to PC screen. If I connect the phone to a PC it just keeps rebooting itself. The hardware buttons do not respond if I do the reset command. (Back, Home, Search, Camera will focus but won't take picture)
Question: Is it possible to fix this issue of infinite boot and have a normal phone again?
Phone specs
Unlocked
ATT Focus
No MicroSD
Version is 7004
If the hardware hasn't been affected you can try a reflash with one of these ROMs. If you can still do that. Plus a hard reset.
From what you have described, I can't tell for sure what is wrong (soft, hard or both). Hopefully none.
The fact that the phone worked, suggests that part of the software is working. The hardware seems ok, so if you're lucky enough the phone might work with a reflash.
What I recommend, before you reflash, considering it was dropped in water, is make really sure it's dry. I hope you removed the battery quick enough as that usually damages the phone if left in, afterwards.
I've heard various methods, and I know 2 that work:
- remove the battery and the cover and find a warm/hotter and dry place (not too hot) and put the phone there, over a towel and in between the phone and the towel, kitchen towel. The idea is to heat the phone slightly. DO NOT use a microwave or a blow dryer or fire. A good example is over an electric blanket, at lowest power (+towel, +paper towel).
- dry rice. immerse the phone completely in dry rice (batt/cover removed) and leave for 24h
So when I flash the device it comes up with a connect to PC screen. However the flash does complete the entire process. Zune then starts running but says restoration fails.
EDIT: I don't think this phone is good to work anymore.
Picture of Zune error: http://imageshack.us/photo/my-images/98/erroron.jpg
Mister Locke said:
So when I flash the device it comes up with a connect to PC screen. However the flash does complete the entire process. Zune then starts running but says restoration fails.
EDIT: I don't think this phone is good to work anymore.
Picture of Zune error: http://imageshack.us/photo/my-images/98/erroron.jpg
Click to expand...
Click to collapse
Did you re-flash the firmware or you only tried to restore from Zune?
The flash process doesn't involve Zune...
I reflashed the phone and then it reboots itself. First with the screen with the red arrow. Which is supposed to happen. Then it reboots itself again and Zune boots up, giving me that error. It then returns to the connect to PC screen once again no matter how many times it is rebooted.
EDIT: Would it matter which AT&T ROM I used to flash it with?
Mister Locke said:
I reflashed the phone and then it reboots itself. First with the screen with the red arrow. Which is supposed to happen. Then it reboots itself again and Zune boots up, giving me that error. It then returns to the connect to PC screen once again no matter how many times it is rebooted.
EDIT: Would it matter which AT&T ROM I used to flash it with?
Click to expand...
Click to collapse
Hmmm.
Here's an Omnia 7 guide, but should apply to the Focus as well (evidently, with Focus ROM/binaries from Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe)
I suppose you followed it. If that's the case then your hw might be affected...
Yeah I followed that exactly. I'm guessing the hardware is affected and can't be used anymore. Guess the one time I used it was a fluke. XD Oh well. So much for having two Samsung Focuses.
Mister Locke said:
Yeah I followed that exactly. I'm guessing the hardware is affected and can't be used anymore. Guess the one time I used it was a fluke. XD Oh well. So much for having two Samsung Focuses.
Click to expand...
Click to collapse
I think you should ask Heathcliff74 (PM him), maybe the problem is that one of the steps just doesn't complete and maybe there's a way to force that, or there might be more you can try.
Hello i have a question regarding my recently water damaged galaxy grand prime (rather not discuss how it got wet) but the top portion of my phone got submerged. I immediately removed the battery and vacuumed out water for a few minutes, tested it to see if it would power on (i know, too soon. So stupid) and to my dismay the camera flashed upon the battery touching the connectors inside the phone so im guessing something shorted there. I proceeded to let it sit in rice for the day but i dont have much patience and was missing using my device with cm12.1 flashed and kept checking it every 4-5 hours or so. So at the end of the day i took it out the bag of rice, powered it on, and everything was functioning as it should, besides a little screen flickering which has disappeared entirely now. But here and there and random times im not using my phone, it will restart and get stuck on the "Samsung Galaxy Grand Prime Powered By Android" screen. It wont make it to the boot animation or even go into recovery, but it will boot download mode. So after pulling the battery a dozen times i finally get it to boot again and i go into recovery and try repairing the system with TWRP repair or replace file system option thinking it could probably help. But to this point my phone still restarts by itself and gets stuck on the logo screen here and there and i have to fight it to boot system. Could somebody please help me out here? I hope it isnt a hardware failure and just some software corruption i can fix by factory resetting and re-flashing the rom. Any help is highly appreciated. Oh and i forgot to mention my camera definitely shorted somewhere only the rear works and if i try to switch to front it cant connect. This happens in snapchat and the cameranextmod cyanogen camera. My stock one stopped entirely.
If your phone got submerged, i'm afraid it'll damage the hardware, sorry bro, you'll have to let it go
I've had a VS995 for about two months. One of the first things I did when I got it was root(dirty santa) and install custom firmware. After doing this I noticed that watching any type of video on the phone would lag extremly bad (<10 fps), unless I held my finger on the screen, and I would get different screen glitches (turn black, turn all static, half and half, etc). I then decided to go back to stock so I flashed a stock KDZ with lgup. This didn't fix the problem. After several weeks of putting up with it, It's gotten to the point where the phone is unusable. It freezes constantly. To get the screen to unfreeze I have to lock then unlock the screen, and half the time it freezes again instantly. Attempting to watch a video (or even a GIF) stutters and chokes after 1-2s and turns the whole screen into static.
At first I was thinking something might be corrupted so today I re-rooted but once I tried to get into twrp the screen kept turning to static. So I flashed back to stock KDZ with no change in performance. Also I can not boot into recovery or fastboot, I've tried several times. Does KDZ upgrade also flash the bootloader?
I'm starting to think it might be something bad on the main board, has anyone ever reflowed one?
I bought the phone used online and it only came with a 30 day warrenty, so no luck there.
Any input would be greatly appreciated.
Thank you
SmokeyMP said:
I've had a VS995 for about two months. One of the first things I did when I got it was root(dirty santa) and install custom firmware. After doing this I noticed that watching any type of video on the phone would lag extremly bad (<10 fps), unless I held my finger on the screen, and I would get different screen glitches (turn black, turn all static, half and half, etc). I then decided to go back to stock so I flashed a stock KDZ with lgup. This didn't fix the problem. After several weeks of putting up with it, It's gotten to the point where the phone is unusable. It freezes constantly. To get the screen to unfreeze I have to lock then unlock the screen, and half the time it freezes again instantly. Attempting to watch a video (or even a GIF) stutters and chokes after 1-2s and turns the whole screen into static.
At first I was thinking something might be corrupted so today I re-rooted but once I tried to get into twrp the screen kept turning to static. So I flashed back to stock KDZ with no change in performance. Also I can not boot into recovery or fastboot, I've tried several times. Does KDZ upgrade also flash the bootloader?
I'm starting to think it might be something bad on the main board, has anyone ever reflowed one?
I bought the phone used online and it only came with a 30 day warrenty, so no luck there.
Any input would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
Yes upgrade in lgup flashes EVERYthing, bootloader, modem, recovery, even the download mode partition. Have to use partition dl mode to be picky (needs the modified lg up files from the mismatched variant thread). The static screen sounds like you need a custom kernel or a new twrp, depending on where its occuring (its related to the dirtysanta bootloader and theres workarounds to fix it builtinto custom kernels and recent twrp)
It's prolly water damage. My V20 was doing exactly the same thing after rooting. I opened the phone and noticed the LCD plug to the Mobo had corrosion on it, I unplugged the LCD from the Mobo and got a clean cheap brand new toothbrush and gently brushed and blew debris off then followed with cleaning with a ear Qtip with a bit of alcohol. Check the seal around the LCD and make sure any gaps are closed with slices of clear tape. I don't know how rooting messed up my phone, it's something strange with resetting the phone, the glitches kicked in from the corrosion on the gold parts. After my first boot from cleaning, my phone was totally normal again. A month later I got screen retention..... Lol but that's a whole other Obvious story everybody shares and knows about lol. I hope you get your situation solved.
Hi there,
I've had this PH-1 for almost a year now, no issues, worked fine. Then out of nowhere it just started locking up in the middle of use, going to a black screen. I'd try rebooting and sometimes it'd work, sometimes it wouldn't. It got progressively worse to the point that I legitimately thought that my phone was bricked. Eventually I figured out to give it some time, let the battery drain to empty and I was able to boot into fastboot/recovery. I backed up what I could and flashed new recovery images then did a fastboot -w after wiping, well, everything. But the black screens continued. Sometimes I can boot into recovery, sometimes I can't. I'm starting to believe that it's a hardware issue. I'm not sure what would have caused this to suddenly start happening - not even sure how to go about diagnosing it but it's definitely a problem. I've been using Lineage recovery as I was told a while back that TWRP doesn't work well with Mata, not sure how accurate that is currently.
Anyway, while it's black-screened I can connect it to my PC and it'll chime like it's recognized a connection but it won't mount and I can't reach it via fastboot. The best way to kind of force it into booting into recovery/fastboot appears to be pulling out or inserting the USB C connector while it's connecting but that's not 100%, it almost feels like chance.
Has anyone ever encountered a hardware issue like this before? Is it my screen connector or a solder, perhaps, that's faulty? Or something more dire?
Any insight would be appreciated!
Thank you,
Brandon
EDIT: At first I thought that this was a firmware issue as it seemed to resolve itself after updating to Lineage 19.1 but after about 20 mins of use, the same freezing, black screen, locking up started up again. After a good amount of searching, I've discovered that my phone is showing up in Device Manager as QUSB__BULK - which, according to this thread, seems to mean that my memory chips have 'reached the end of their normal life cycle through natural wear and tear'.
"Google's bug tracker entry has officially changed to "Won't Fix"/"Infeasible" - their reasoning is that their memory chips have completed their "natural lifecycle" and have failed due to normal consumer use case wear and tear.
https://issuetracker.google.com/issues/192008282"
https://www.reddit.com/r/Pixel3/comments/mm7yp2
Are there any Android tools/apps that can identify/flag/fix memory or bad sector issues to help head this memory degredation off at the pass?
try installing qualcomm drivers for EDL mode on PC? then will it show up as 9008 mode
then if it is 9008 mode maybe flash with EDL?