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
Related
ok here's what's going on perhaps someone can figure out what's wrong. Last night I had placed my mda on its charger like usual b4 bed. well sonce my battery cover is slightly broken I had placed a some cardboard within the battery door due to the fact that it would "white screen" then rest and get stuck at the loading screen and drain my battery, anyhoo.... well it whitescreened cause my dresser rocked due to my cat stepping on my phone. so I reset it as usual and the splash screen would load then fade to white. after several attempts it finally started to load as usual but then it went to the boot loaderscreen. I had reset it several more times but no luck. I took out the mobo to see if something was stuck and again nope. luckly I had an older mobo that wouldent charge so I had replaced the mobo but does anyone know why it would randomly get stuck on the boot loader screen? I had even did a hard reset in the device and still no luck. if it was a normal computer I would say that it had lost it's OS any ideas on how to fix it so I can get back my phone the way it should be?
-rastlin
update on bootloader
well I was able to aquire tmobiles flasher utility and I attemted to flash the unit to no luck. I went through all the steps and it gave me an error that it cannot retreive data from the device. ok now I am totally stumped. I am open to any and all suggestions
-rastlin
Right I feel silly, knowing this I just couldn't resist trying to fix my "phone", so I've bought a S7 Edge from eBay from a trusted company with a 14 day refund which is good right?
We'll I couldn't rest as the phone was going into boot loops, i.e booting once every 5 times, going into the black screen of death with blue LED.(Had to wait for the battery to drain to 0%) https://youtu.be/K9T_UF-_5ho (Even though it booted at the end after a minute of use it crashed and went back into a boot loop and crashed and then it was fine for like an hour)
It would get stuck if I went to stock recovery, get this weird static line. I did boot into recovery once so I did a factory reset hoping it would fix something, which it did not. So I guess I was going to return the phone, I then had the stupid smart idea that it booting up fully and me activating it and then resetting it would be a good idea, and boy I was wrong. So it went to you know the usual "erasing screen" in which it would get stuck on, I did the hard restart maybe 4 times then it sorta worked the android guy kept spinning until IT JUST DIED.
And here we are now me typing this out, I feel like the company isn't going to accept it back due to it not being "functional".
Absolutely no sign of life now. Not even charging, this has happened before with it when I went into the recovery menu and it got stuck. I waited out an hour and then pressed ALL the buttons and the charging icon appeared but now, now I think it's different.
TLDR: Bad eMMC of phone, caused me to try to reset it and now it's bricked?
Well lesson learned? When things aren't working at the first place don't try to fix them just refuse outright.
Some say the phone can't be bricked but I feel like I really did it this time.
No the phone wasn't rooted, no I didn't flash with ODIN.
http://imgur.com/SxA0Q9b
http://imgur.com/QLLwhot
Just return it.
There is nothing else you can do and I see no reason why they wouldn't accept it unless there's a physical damage.
Sent from my SM-G935F using Tapatalk
Ok, so this all started about a week ago. My dad has had this phone and for the most part has enjoyed it. The other day he calls (from the house phone) to let me know that his phone doesn't work. I was expecting the typical black screen so hold all the buttons to force a reboot and boom hero for the day.
God no. This phone would suddenly not boot properly at all. I mean I had trouble getting stock Recovery mode to even come up or download mode. I bought a new battery thinking it could help. Twice now I have managed to use ODIN to reflash stock firmware of 7.1.1 . Both times the phone would be fine and suddenly it would turn off and bam the same thing over again. Firmware screwed and it doesn't want to turn on reliably. Recovery mode would display all sorts of errors with mounting /efs and dm verity errors....
This must be a hardware problem right? I don't know what else to think at this point. Is it possible the restore of his backup from sammy cloud is corrupting it? I am willing to try this one more time and not restore any of his files or is it hopeless? Is there something fried?
And just for the record, I am not new to ODIN/Rooting/Custom Roms/ etc but at no point EVER has this damn phone been attempted to be rooted or anything. I hope someone has something positive to share or just put me out of my misery so I can destroy this f******* phone into a thousand pieces.
Has anyone ever had an issue where the plastic back cover is somehow causing the phone to short out or overload which makes it freeze or turn off? I swear this back cover is the cause of all of this. Last night i reflashed everything and really just forgot to put the cover on. It stayed on all night without a single issue. I rebooted and powered down multiple times and it turned right back on. Then I put the back cover on and what do you know, difficulties with powering on and freezing.
On the top right above the sim/microsd slot there is that spot with metal looking conduction material or something and it is also at the bottom near the charge port. What are those things? At this point the phone has become a pet project and I just have to have the answer. My dad already got a new phone lol. Any ideas?
Hello, so I have a J7 2017 (SM-J730GM/DS) 32 GB Unlocked Dual SIM which has served me well for a while. I ended up dropping the phone at some point in a sliver of time without a case and the screen cracked. After replacing the screen I noticed if the screen was pressed in a certain area it would go crazy and reboot the phone (crazy as in the pixels would do weird things like dimming, going grainy, like the display shorted in some area, then the phone would reboot itself), probably some error on my installation of the screen and the ribbon cables (I can see an area where it looks creased, it never sat flush with the body of the phone as the OEM screen did). I was able to just be careful and not trigger the reboot for some good time until it happened again and the phone would continuously reboot, allowing me to only get back to the OS through the boot menu, selecting "reboot now". That worked for a while until it would never boot into the OS, just looping at the screen where it says the phone name, where it would vibrate, go black, and go back to the phone name screen. I gave up trying to fix it, as I had a backup phone, and just now had some ideas. I figure the OS is corrupted in some way, I am no master in knowing the details on how phone boots up and such, so I did some research and successfully flashed the most recent ROM onto the phone using Odin 3.14. It still doesn't stop the looping, unfortunately.
Any ideas? I hear people talking about using TWRP or something to do things boot related, but I don't want to possibly mess anything up further nor do I know what they were talking about.
Thanks,
Stella
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.