Constant bootloader start after "waterdamage" - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

Update:
To be more specific:
I watered my Fire 8 HD a bit. The bottom side with the speakers got wet, I immediately took it out of the liquid and tried to dry it. All worked well afterwards, expect the Volume down button doesn't correspond anymore, which is not a big deal. Now I haad to shut it off and can't get it back on, because it is always entering recovery mode, not letting me advance to the os.
Any ideas on how to fix this or work around?
Thanks in Advance!

If the partition containing recovery was damaged, I am pretty sure it's dead (unless firmware becomes available?). Dumb question but have you tried resetting and wiping cache when you do get to recovery?
Also if you have enough rice around...

Related

[HELP] A500 Unbricking challenge

OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
erica_renee said:
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
Click to expand...
Click to collapse
I might try that soon, gonna keep at it. It's not a heat issue; it only runs a few secs before it shuts down. I know it's got something to do with me formating the data and not finishing the reset.
Have to ask, but is the bat flat or does it do it plug in.
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
SmittyRN said:
OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
Click to expand...
Click to collapse
Well, I let it sit for a while, and instead of holding down the "-" key, I plugged in the keyboard and pressed the home key. Nothing seemed to happen, but when I turned it back on after that it booted up and let me go through the setup screen. Strange, but at least it's working.
shaun298 said:
Have to ask, but is the bat flat or does it do it plug in.
Click to expand...
Click to collapse
Yeah, sorry, I have no idea what you are asking.
tkirton said:
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
Click to expand...
Click to collapse
Yeah, it would say that the recovery key was pressed or whatever, just for about 1 sec, the shut off.

Nexus one got WET in Rain, CANT BOOT

My Mobile Got wet while it was in its ORIGINAL pouch.
I thought it wont effect the mobile if it was in the POUCH
As soon as i realised it got wet, i switched it OFF, but it was again getting back ON, so removed the battery.
Now every time i Power ON my nexus, it enters the RECOVERY Mode.
May be the TRACK ball is in contact, but no matter what , I cant boot IN
please Help\
EDIT:
i am using the OxygeN1mod Rom.
I tried the Hair Dryer on the mobile and now the mobile Screen became moist ( sort of WHITE )
Also sometimes i can boot-IN. But it says SAFE MODE and again BOOTS and says SAFE MODE and repeats.
I re installed the ROM but IT either enters the RECOVERY mode or says SAFE MODE.
please help.
First, stop powering it on, as that will just make things worse. Put the thing in a bag of dry rice, then try again in 24 hours.
firoz3321 said:
My Mobile Got wet while it was in its ORIGINAL pouch.
I thought it wont effect the mobile if it was in the POUCH
As soon as i realised it got wet, i switched it OFF, but it was again getting back ON, so removed the battery.
Now every time i Power ON my nexus, it enters the RECOVERY Mode.
May be the TRACK ball is in contact, but no matter what , I cant boot IN
please Help\
EDIT:
i am using the OxygeN1mod Rom.
I tried the Hair Dryer on the mobile and now the mobile Screen became moist ( sort of WHITE )
Also sometimes i can boot-IN. But it says SAFE MODE and again BOOTS and says SAFE MODE and repeats.
I re installed the ROM but IT either enters the RECOVERY mode or says SAFE MODE.
please help.
Click to expand...
Click to collapse
Put in the rice for 3 days to moist it out... Or brown sugar...
Sent from my Nexus One using XDA CYANOGENMOD!
OH. Ok.
what about the SAFE MODE thing ?
EDIT:
Ok
http://androidforums.com/android-lounge/4885-safe-mode-reboot.html
So i think the MENU key is the problem of that
I will try your method thank you bigmout and DaxElectro
firoz3321 said:
OH. Ok.
what about the SAFE MODE thing ?
EDIT:
Ok
http://androidforums.com/android-lounge/4885-safe-mode-reboot.html
So i think the MENU key is the problem of that
I will try your method thank you bigmout and DaxElectro
Click to expand...
Click to collapse
try that method... I had the same problem with my other phone, but it when to emergency mode...
Sent from my Nexus One using XDA CYANOGENMOD!
Still i am getting the SAFE MODE
cant get the NORMAL Boot
some is pressed. i mean sort of shorted.
When i enter the Recovery Mode, as soon as i enter the Recovery (RAmon) it reboots. because the REBOOT is the first option in the RAmon recovery.
Is there any way to boot the mobile in normal mode ??
Please help
I have the exact same problem. it's because the trackball is shorted. Try cleaning that, it might help, though with mine it didnt, I will have to get it repaired.
I cant post the link, but there's a poster (Luque07) on nexusoneforum.net, who did get it repaired himself:
Exclamation Stuck in Safe Mode on N1
There is another thread named "Stuck in Safe Mode" but I decided not to hijack that one. I dropped my phone into a fountain (Don't ask-->painful memory). I did the hair dryer thing and the bag of rice thing to dry it out. My phone is dry but now it boots only into Safe Mode. I've googled everything and apparently the world says, "Send it back to HTC". There are a couple of reasons why that isn't feasible for me.
1. I'm not in the US at the moment and won't be back home for a few months
2. It's now water damaged.
Does anyone know how to get out of safe mode? Google doesn't even document safe mode.
When you're in safe mode, you can't do anything. You can add an account to check your email and calendar but your sim card won't work. Only wifi mode works. You can't install any new programs (they say they are installed but won't appear on the menu and can't be run).
If I reboot the phone it ends up at the bootloader and I can't use the volume keys to move around and the power button doesn't work. The trackball doesn't work in recovery mode either.
I was able to get it into my clockworkmod recovery mode once and tried a restore from a backup but it didn't work. I haven't been able to get it into clockworkmod recovery since then.
I'm on CM7 nightlies build#37 with my N1. Any help would be appreciated. I've tried the following:
1. Pressing trackball while booting
2. Vol up while booting.
3. Vol down while booting
4. Nandroid restore (can't repeat because I can no longer access recovery).
5. Clear Storage (Hard Reset)
6. Reset from within Settings.
7. Cold booting after leaving battery out.
8. Innumerable battery pulls.
NVM. I figured out how to get out of safe mode. Apparently, I didn't hold down the Volume Up button long enough. For those unfortunate enough to experience this issue, here are is the possible reasons why you ended up here and the resolution:
Causes:
As near as I can determine, on the N1, the cause is due to water damage to the trackball which causes a continuous short. Basically, the trackball acts as if you are pressing down on it. Pressing on the trackball & menu key while booting initiates Safe Mode.
Resolution:
1. After making sure your device is 100% dry (try putting it in a bag of rice. Rice is a great dessicant). Press & roll the trackball with an absorbent lint-free cloth (I used a small shamwow). Do this for a few minutes until you are sure you've removed all possible liquid.
2. Put your battery back in and boot. If it boots to the bootloader and you can't get out, pull the battery and wait for 15 minutes. Put the battery back and you should be able to boot to safe mode.
3. If you reboot and safe mode comes back up, power down (off) your N1 using the power button then while holding the volume up key, press the power button again. DO NOT LET GO OF THE VOLUME KEY! This is critical. You have to hold the volume up key until the initial X of the bootloader disappears and you get the startup animation. Once the animation appears, you can let go.
You should now be in regular boot mode. If not, pull the battery, hold Volume up and put the battery in and press the power button. Make sure you keep the volume key pressed.
YMMV and I believe the above stuff only works on the N1 as I have seen other sequences for other phones posted elsewhere.
Click to expand...
Click to collapse
i am still stuck in safe mode
I tried all tricks.
Please help.
I disassembled the mobile like 70% and saw no water or moisture inside. I was scared to remove the mother Board from inside. so again assemble it back.
Am getting Safe mode then soon it reboots into safe mode and repeats forever.
If i pres Volume key and power button i am getting RECOVERY mode, is it coincidence ?
After continuous 10 hour struggle i finally booted in.
If i restart my mobile it will again repeat i am sure. Because The track ball is the problem
How i logged in:
After many hours of research and trials i finally realised that the track ball is in SHORT mode. So i noticed in the recovery menu that if i hard press the track ball it is releasing the circuit.
So while booting i gave the track ball one shot ( a hit).
Then after i got the 'X' i hard pressed and holded the Track Ball. (it was very painful to hold so long) finally i got in.
Hope this track ball gets fine with time.
Thank u all for guiding me through...
Sent from my Nexus One
firoz3321 said:
My Mobile Got wet while it was in its ORIGINAL pouch.
I thought it wont effect the mobile if it was in the POUCH
As soon as i realised it got wet, i switched it OFF, but it was again getting back ON, so removed the battery.
Now every time i Power ON my nexus, it enters the RECOVERY Mode.
May be the TRACK ball is in contact, but no matter what , I cant boot IN
please Help\
EDIT:
i am using the OxygeN1mod Rom.
I tried the Hair Dryer on the mobile and now the mobile Screen became moist ( sort of WHITE )
Also sometimes i can boot-IN. But it says SAFE MODE and again BOOTS and says SAFE MODE and repeats.
I re installed the ROM but IT either enters the RECOVERY mode or says SAFE MODE.
please help.
Click to expand...
Click to collapse
Late info now but best thing is put it in a ziplock bag of rice, cheap minute rice, because it absorbs moisture. If you have any packs of dessicant (they come packed in electronics boxes and say "DO NOT EAT" on them) that will help too.
You should never use a hair dryer, not because of the heat, but because you are not drying the device, you are blowing the moisture in further and doing more damage.
And last, don't power it on until it has thoroughly dried, that prevents shorts and more damage.
Hope the trackball comes back for you!
I dropped my N1 in the toilet! We're not talking about a little moisture like some rain...Mine SUBMERGED!
When I took it out, you could visibly see water in the screen, that's how bad it was.
At this point I had nothing to lose, so I found a dis-assembly video on youtube and took mine completely apart and used napkins to dry it out (there were small and tiny areas of pooled droplets that would've taken DAYS, if not WEEKS for rice to dry out!) the best I could. I then left it in pieces overnight.
The next day I put it back together and it WORKED!!
I should note that during my drying out everything with the paper napkins, I also took the trackball assembly out and dried that out thoroughly.
Lastly, if you've got a persistent short, then I think you've got one of those little pools of water that takes a LONG time to sit in rice to dry it out. If you didn't want to go the route of taking your phone apart (it's NOT all that easy and you do need very tiny tools) I'd recommend going to a craft store and buying some desiccant (whether in the packets or loose) and enclose your phone in a bag or container with that stuff for a WEEK to make sure you really dry your phone out...The desiccant should do a better job of drying-out than regular rice.
Good luck!

Possibly Hard-bricked?

Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
FluffyMittens said:
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
Click to expand...
Click to collapse
I think you've got your terminology mixed up. Bootloader is the mode that comes up by pressing both volume keys while powering on. This is where you flash stuff through RSDLite or use adb server to push and do hacker stuff.
Recovery is the phase where you can do factory wipes and data formatting. I can't get into recovery.
When you flash an SBF, it should be flashing a new recovery. I think the phone is hosed.
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
infazzdar said:
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You've got to be ****ing kidding me.
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
FluffyMittens said:
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
ADB isn't working. I don't think ADB works in bootloader.
You ask me what I have done so far, but I already put all that information in the OP. That is why I was so frustrated with that second guy. If you guys would take time and not skim over my post that I actually thought out and typed ****, you wouldn't have to waste your time asking me what I have done.
I appreciate the ADB suggestion.
Just trying to collect some information. I'm someone that doesn't let a phone just be deemed as bricked. How charged is the battery?
-Edit: Just checked, ADB doesn't work in bootloader. Confirmed by having RSD open and making sure it sees it, and then tried adb devices. Also as a supporting confirmation for the fun of it, ran the one click root.
-Edit: Further thinking about it, was this phone submerged in water or just had moisture in there? There could just be some minerals formed up on the board that a toothbrush would get rid of. I've fixed phones a dozen times. Some phones will turn on and get stuck. Some wont turn on. Some the backlight comes on but no video signal.
Deoxit
My guess is that the buttons aren't working. There's no way to test that since you can only get to the bootloader, but if you can successfully SBF the phone the odds of any of the solid state gear being bad are pretty low. It does seem odd though that you can't make it to the boot animation and get stuck at the boot logo.
I would suggest getting some deoxit (tv tuner cleaner) and spraying it in around the hardkeys on the bottom of the phone. You don't need too much (especially since it might end up behind the screen). Spray that in there and then work the buttons a few dozen times. That should loosen up any corrosion on the switches and let them close the circuit again. If that doesn't do it, I'm out of ideas, but at least you'll have some deoxit lying around (stuff is great for static-y radio/stereo volume control knobs, etc).
The battery is pretty well charged. When I got it in the mail, there was no charge. I cut a USB cable and hooked it up to power. After about 2 minutes, I tried it. It got to bootloader but said battery was too low. I used the cut USB cable and hooked it around the battery pins in the phone and put the battery in, so it charged it at the same time it was tricking the phone into thinking the battery was full.
Also, if you go into Bootloader and then power off the phone, the green LED comes on. I'm assuming that means it's charging? I was skeptical since all we hear is that you're ****ed if your battery runs out at this stage of the game. It was off this morning and had been plugged in with the green LED all night (no USB cable hack).
As for trying adb while RSDLite is open, no go. adb devices shows blank. Motorola OneClick root didn't work either. It just sat there waiting for my phone. I didn't have the balls to plug in my Bionic to see if Motorola OneClick would work (and therefore the problem is with the Droid X).
As for the water damage, who knows. The lady I got it from was surprised when I told her there was moisture under the screen. I'm not her mommy so she didn't have any reason to withhold information from me. I just thought a bag of rice, a $12 battery off Newegg (free shipping, too), might just get me a sellable Droid X out of the deal.
As for the hardware buttons - they feel like they're clicking, but I know that obviously isn't the 100% test whether they're functioning properly or not. The volume buttons and power button obviously do function, since I can use those to get into BL.
Another brain jog idea: Is there an SBF out there that wipes the data and cache, along with all the other **** it puts on? This probably won't work because I still should be able to get into Recovery - something is FUBAR.
Please give up if you feel like giving up. Bricks exist. This may very well be one of them.
P.S. The girl that gave me this dropped her new iPhone 3 days into ownership. It only cracked the back glass, but the point still remains: she may not be the most graceful phone owner on the planet. Who knows what this DX has been through.
Thanks for all your help, guys.
I would try cracking that thing open and seeing if there are any mineral deposits and cleaning them. This means those weird clips and stuff too, just take a toothbrush to the whole thing and see where that gets you.
As with giving up, I'm a pretty bored guy and finding something to do is better then sitting around and watching Star Trek.
I haven't lost a phone once
Edit: Except for this [email protected]*% of an ACN voip phone that I buffer overflowed in attempt to gain root.. That ended badly.
Same problem
I had the same problem with my dx trying to sbf to .602 I ended up flashing the stock stock froyo sbf and upgrading to gingerbread by rooting and flashing CM7 or any other gingerbread rom. You didn't specify whether or not you tried froyo sbf. No idea if this will work for you but its worth a shot if you haven't already tried it. I also had to use RSD lite 4.9 or 4.8 to get the sbf file to work right.
I'd like to toss my problem into this thread if it's alright. The OP is the closest description to my situation I've read. A co-worker brought his phone to me and it would only get to the round red logo and stop there. No bootloop just a freeze at the red logo.
I tried different ways to get to recovery but was only able to get it to the white bootloader screen. (30.04) So I flashed .340 using RSD and it completes and tells me to manually start the phone. But the phone is already at a white logo (not a red one). I do a battery pull to restart the phone and I still can't get the phone to a recovery by holding down home or any other key while powering on. Battery charge is near full.
The owners explanation of how the phone got this way is that he woke up one morning and there was a 'protection mode' transparency on the screen so he rebooted and had the red logo from then on.
So, I can RSD flash just fine but the phone won't get past the black screen with the white and black M logo.
I would try flashing other files or even the Linux CD option but I can't find anything downloadable since mega got shut down.
Any advice would be appreciated.
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
NType3 said:
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down together gets buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
Click to expand...
Click to collapse
1. Would be happy to try .602. Do you know of a working link?
2. It never gets to the eye.
Edit... I found a 602 iso to make a CD boot disk from and used that. The install went perfect but the phone still just boots to a red M logo and freezes there. It doesn't get to the red eye and no button press combo can get it to the recovery screen. I can only get it to the bootloader or let it go to the red logo. The buttons don't feel sticky or anything and the batt is fully charged.
The Fix
Skyroket said:
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Click to expand...
Click to collapse
This will have all sbf working files and linux operating systems along with everything you will need try to sbf one of those preff linux. If this doesn't work and your still stuck! Go to this web page you will need.
Motorola Droid X Motherboard Flex Cable Replacement
Motorola Droid X Keypad Flex Cable Replacement
http://www.repairsuniverse.com/motorola-droid-x-replacement-screens-repair-parts.html
Finally here is how you take it apart with out damaging it.
http://www.youtube.com/watch?v=wo7dXyJhL1U
GL to you enjoy your droid x once ya get it working!
I always have to sbf my dx twice, I always boot loop the first time.
Just fyi, if you bootloop after an sbf, you can pull the battery, boot into stock recovery with the usual key combo format data and you'll be all set: no more bootlooping (or double sbfing!)

Help stock boot loop

So, I'm trying to fix my friend's phone. She dropped it in a puddle and now it just boot loops. It's stock, not rooted, and I have no access to the developer options. I can barely get into recovery and when I tell it to do a factory wipe, it just boot loops again except in recovery mode. Any help would be greatly appreciated.
It sounds like the phone might be hosed. It's somewhat drop resistant and it's water resistant, but if the back cover isn't on well the water resistance doesn't exist. The phone is behaving like the hardware is damaged: a little water may have gotten in and short-circuited something, making the storage inaccessible.
Try connecting to a computer, then boot the phone into Download mode by first holding Home + Volume Down and then holding the Power button. Use the Odin software on the computer to flash a stock recovery image to the phone. That's the only other thing you can try.
painiac said:
It sounds like the phone might be hosed. It's somewhat drop resistant and it's water resistant, but if the back cover isn't on well the water resistance doesn't exist. The phone is behaving like the hardware is damaged: a little water may have gotten in and short-circuited something, making the storage inaccessible.
Try connecting to a computer, then boot the phone into Download mode by first holding Home + Volume Down and then holding the Power button. Use the Odin software on the computer to flash a stock recovery image to the phone. That's the only other thing you can try.
Click to expand...
Click to collapse
That's what I was fearing because the back popped off when it hit the water. I've tried using Odin to flash it but it always fails. Odin at least recognizes that it's connected. Any links to a stock recovery that I may be able to use? Thanks.
So, a LOT of water got in. That's an important detail.
You can try this restore image, but it sounds like you already tried everything that can be done. Don't be surprised if it is not successful, because any factory image with a matching md5 download would have worked: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
painiac said:
So, a LOT of water got in. That's an important detail.
You can try this restore image, but it sounds like you already tried everything that can be done. Don't be surprised if it is not successful, because any factory image with a matching md5 download would have worked: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
Click to expand...
Click to collapse
Yeah. She said it didn't get that wet. I find that very hard to believe. I'll give it one last effort. I appreciate your help!
Miss Integra said:
Yeah. She said it didn't get that wet. I find that very hard to believe. I'll give it on it.e last effort. I appreciate your help!
Click to expand...
Click to collapse
It does not have to get very wet at all for something to get shorted out. A friend of mine watched a single raindrop wick into the headphone jack of an older smartphone, then the screen went black and it never turned on again.

I am about to go crazy with this evil phone. j320a variant with complete stock firm

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?

Categories

Resources