Hey everyone, I would like to say thanks in advance for any help/time spent towards helping me resolve this issue.
I've had a Redmi Note 5a Prime for a little over a year now. 2 days ago, it was dropped in water. Completely submerged. As soon as I realized, I took the back off and removed the battery. Every attempt I made to revive it didn't work. Finally, I tried a last ditch solution. I removed the logic board and remove the cameras from it and soaked the board in a solution of 91% alcohol. I scrubbed it clean with a toothbrush and also the connector ends. I let it dry for a very long time and finally got it to boot to the Mi logo. That's as far as I got. So, I figured software was corrupted. I looked into unlocking the bootloader to reflash stock firmware, but I get an error that the account isn't attached to the device. I am 100% sure I used the correct account. It's the only one I have. I'm not sure if it's because I also have a Redmi Note 4 attached to the same account or what.
Anyways, between trying different methods to restore firmware, somehow I randomly got the phone to boot and used it all night last night. Today, it's back to being stuck on Mi logo. I tried EDL test point method to flash fastboot rom, and it was successful but still stuck on Mi logo.
Any ideas? Maybe a hardware problem? Maybe it's done for. I'm not sure but I do apprectiate the help. Thanks.
Also, I apologise if this is in the wrong section. I looked thoroughly before posting.
Also, forgot to mention, I don't have usb debugging enabled and the bootloader is locked. I can access both fastboot and Mi Recovery. When choosing to wipe all data in recovery, it switches to a blank screen with 1% and then completely goes blank and I have to hard reset/ battery pull.
Related
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
simon211175 said:
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
Click to expand...
Click to collapse
ok mate
right the mcgyver trick works a treat and is surprisingly easy. i wasnt keen on it but it works and is not hard although it is fiddly and if you are anything like me it will take a few attempts to peel back the shielding and expose the wires and then get them in place.
i found the best way to get the wires in place was not put them under the battery as the guide suggests but instead just put the battery in as normal and have the wires in at the very end. you will understand what i mean when you start but i have decided to take a photo and you can see what i mean here
http://sdrv.ms/OPDczX
everything you need for that this section of the recovery is here.
http://forum.xda-developers.com/showthread.php?t=892026
then you need to flash the sbf again. the one you have already flashed is fine and is the one you need so use that. (if for some reason it doesnt work after what i am going to tell you then ask again on here before you choose another).
next follow the guide to un-bricking your phone (linked below). if the phone wont boot and gets stuck after you have flashed the sbf you need to boot into recovery and wipe the data/ cache. reboot and all should be ok.
so follow the guide to the letter but when/ if (the phone wont boot past the moto logo) follow step 8. however you will find that when you press power on/ volume down that instead of motorola recovery you get a droid with an exclamation mark (this is ok so dont panic). to get into stock recovery from this position you need to press and hold down both up and down volume buttons at the same time for about three seconds and viola. then you can wipe and you should (fingers crossed) be good to go. if you dont understand anything then ask but it is relatively straightforward and if you do what i suggest above then you should have a working phone in next to no time.
http://forum.xda-developers.com/showthread.php?t=1828639
good luck
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
simon211175 said:
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
Click to expand...
Click to collapse
did you wipe the cache/ data after you flashed the sbf? if you didnt you may want to give it a go before you send it off. it may spring to life once you have done that.
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
simon211175 said:
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
Click to expand...
Click to collapse
It looks real bad. You sure the battery didn't die in the flashing process.?
Also try booting into recovery and do a wipe.
It's entirely possible that the battery died during the flash.
I cannot boot in to recovery - the phone doesn't get that far!
I've sent it back to be repaired. hopefully they'll do it under warranty, but if not it's only going to cost around £60 to buy out the remainder of my contract so if the repair costs more I've got that as a backup option.
Thanks for all your help guys.
You can cut an old wall charger but if you can't measure the voltage to know what wire have 5 volts and 0 Volts , and you can hold the wires 5V to plus on akku and 0 to minus and the supply would load..... you can left the batt out of the device...
Wait 10 till 15 min ,for save check if batt getting hot, boot into stock recovery and factory reset your phone
If you can't enter recovery you should be able to enter boatloader
If there is battery low can not program ..load akku.. or ready to program which means .... flash rom with rsd, factory reset , reboot, have fun
i did this two times, flash with low batt one of with not loading batt in dev - i charged with Nokia wall charger cable
If only battery is too empt and briked batt loader.......
If boot loader is briked by bad flashing search Google......
But i mean ciao loved defy
And don't forget : factory reset is always after you changed your rom....
Wiping cache/dalvik cache in only installing new nightly
Sent from my MB526 using xda app-developers app
so, here's my update.
You will recall (see two posts up) that I gave my phone back to T-Mobile on 20th August for a repair. I got my phone back today (+18 days). Here's how it went:
Day 1
Took phone to T-Mobile store. Informed them my battery had a strange lump, which I suspect had fried my phone somewhere. They advised they would send it to the repair centre the following day. No courtesy phones available so I'd be living in the 1980s for a while.
Day 10.
Phone actually arrives a the repair centre. I have no idea where the repair centre is, but I'm guessing really really far away.
Day 15.
Repair centre advise my battery is faulty and to replace would cost me £26.40 for a genuine Motorola battery. Advised repair centre that I told them my battery was broken, and asked why it took them 15 days to repeat that back to me. Also advised them I would rather by my genuine Motorola battery from Amazon for £11.95. Gave them a link in case they want to update their price lists.
Day 17.
Repair started on actual phone.
Repair finished. Yep - the repair took less than 24 hours.
Day 18.
Phone returned to store. it took 24 hours to get there, so I'm assuming the post travels down hill only on the way back.
Picked up phone from store, all set to complain about poor service etc. Noticed brand new battery I hadn't paid for sitting in the returns package. Kept quiet. Left store promptly.
So now I have a working Defy once more (Hurrah).
Obviously I've rooted it already in order to get Titanium Backup to restore all my apps.
Now I have stock 2.2 Blur running on my phone (Boo!), and with only a few months remaining on my contract, I'm not sure if I want to risk loading a new ROM again (I'll reread this once I've loaded a new ROM next week, for sure).
Hi guys...I accidently dropped my tablet in water...after drying it for 3-4 days..i tried to start it up..but it is rebooting directly to TWRP recovery mode...even I tried rebooting from there but it never reboots ...it just powers down...i tried to completely wipe and flash OS..but it is not working..do you think there is some hardware related issue or any other? Please help me.
Boot into bootloader, flash factory image using fastboot. You can find everything here: https://developers.google.com/android/nexus/images
Sent from my Nexus 6 using Tapatalk
Thanks nhizzat i will try it.
How did that go? I have the same problem - dropped the Nexus 7 in the pool, but immediately took it out, opened the case, dried it and left it in rice (forgot to disconnect the battery though); but after reconnecting it can only get to the recovery menu as you say. I tried changing battery with another N7 and that didn't help.
quidnunc said:
How did that go? I have the same problem - dropped the Nexus 7 in the pool, but immediately took it out, opened the case, dried it and left it in rice (forgot to disconnect the battery though); but after reconnecting it can only get to the recovery menu as you say. I tried changing battery with another N7 and that didn't help.
Click to expand...
Click to collapse
hi ...no improvement same problem..i tried almost everything now..
alright. same here. even completely disassembled it to clean the circuits with alchohol. thanks
Sorry if the thread is not in the right place and not fancy written, I don't use forums a lot..
So I've had that phone for about 3 years now. I've never rooted the device, never installed any custom roms, nothing. Only did a factory reset/wiped data couple of times.
One day I woke up (on 2nd of January), looked at my phone (it was charging whole night) and it was showing the "Google" logo. After that it switched to "colorful X", then it turns off, vibrates and all over again.
I was doing it until I took out the battery for a half an hour. Plugged it back in, turned on... Same thing was happening.
I've removed the battery again and plugged it back in. Pressed the power + vol up + vol down buttons in order to get into the bootloader. Got to the "recovery" and wiped the data/factory reset, and wiped the cache.
Restarted, didn't work.
Got mad here and decided to first time to attempt installing a rom. I've got to the google developer website where there are factory images. There were a couple of versions of the Galaxy Nexus. I didn't know which one to pick, so I've picked the first one (GSM with google wallet latest version). (I've already had Android SDK) so I've followed the instructions by using the "fastboot oem unlock"
then "flash-all". It failed. And the reason is when it rebooted, the bootloader locked again and the script couldn't continue installing/flashing.
So every time I unlock the bootloader and reboot, it locks it again.
I've decided to flash every img individually. By using this pattern:
fastboot oem unlock
fastboot flash bootloader bootloaderblabla.img
fastboot reboot-bootloader
fastboot flash...... and every single image including the radio, boot system, etc....
basically every time I flash and reboot, I unlock the bootloader.
That however didn't fix the problem, it was still remaining in the bootloop.
So I am not sure which version of the galaxy nexus I have, I've tried doing that will few versions of the factory images with no success.
So I came here, in a chance to get it fixed by some magic!
Please help?
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Same thing happened to me and I changed my motherboard
Sent from my Galaxy Nexus using XDA Free mobile app
playitlouder said:
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Click to expand...
Click to collapse
Ahh that's unfortunate, I think it's better to upgrade to a new phone.. It became laggy anyway.
Thanks!
Hello, please for help, I will not create new thead.
I have a problem, I'm tring to start phone and stucks on bootloop.
The solution should be start recovery, but my second problem is volume down doesn't work.
Is any chance to get to recovery throught ADB while phone is turned off?
Thanks.
I got an OTA update. I think it was PG2. My phone was sluggish on PE2 all along without any solution in sight, but after updating to PG2 it was ok, no more sluggishness. However, just a few minutes after registering a fingerprint on the phone it went blank. Initially I thought it was the screen that locked itself. After a while I picked the phone to check something and no response. Thought it was powered off, tried to power it on, no response. Removed battery and reinserted, tried to power it on, no response. I plugged in the charger, no response. Not until I plugged it into my laptop and heard a sound that I now checked Device Manager and lo and behold - QDLoader 9008. This phone was not rooted, not modded in any way, just bone stock. Only took PG2 update OTA. Any help from anywhere?
EDIT: Funny thing happened. As I was about to pack up the phone and stow it away in hope of the debrick files being made public anytime, I removed the battery and then something else took my attention away for like 5 minutes. When I got back to the phone I just told myself to try this again. I put the battery back and tried to boot into fastboot... Lo and behold, it booted into fastboot. I quickly removed the battery and tried it again, no show. I removed the battery and waited a couple of minutes and tried and it booted again into fastboot. I quickly downloaded the PE2 firmware and flashed through Odin. It worked. I flashed TWRP, just for the sake of making it impossible to take the [email protected] PG2 OTA again. Right now the phone is in excellent working condition once again... Someone likes me 'upstairs'...
ezeuba said:
I got an OTA update. I think it was PG2. My phone was sluggish on PE2 all along without any solution in sight, but after updating to PG2 it was ok, no more sluggishness. However, just a few minutes after registering a fingerprint on the phone it went blank. Initially I thought it was the screen that locked itself. After a while I picked the phone to check something and no response. Thought it was powered off, tried to power it on, no response. Removed battery and reinserted, tried to power it on, no response. I plugged in the charger, no response. Not until I plugged it into my laptop and heard a sound that I now checked Device Manager and lo and behold - QDLoader 9008. This phone was not rooted, not modded in any way, just bone stock. Only took PG2 update OTA. Any help from anywhere?
Click to expand...
Click to collapse
Not sure if this other post is related to your issue, but you can check it out.
http://forum.xda-developers.com/note-4-sprint/help/sprint-note-4-n910p-boot-failure-t3431069
@ezeuba
The black screen you got after registering fingerprint seems to be your initial issue.
Some users reported a similar issue after installing Samsung's Good Lock SystemUI replacement that is not compatible with fingerprint unlock. Not saying you did that but the fingerprint registration commonality can't be overlooked. It may have a related failure. Some users dealing with that had to restore a backup or start over on Odin.
I don't suspect the OTA update but some issue registering fingerprint. When you registered it, did you select lock-screen unlock option as fingerprint? If so, you may want to avoid selecting that option but a wiping internal memory and factory reset may be enough to continue using finger unlock. But finger unlock cannot be used with Good Lock application.
Sent from my SM-N910P using Tapatalk
That's strange, but I don't even know about any Good Lock UI, never used it. After the phone sorted itself out, I tested the fingerprint again and used it like that for nearly an hour, no issues. If the fingerprint stuff had anything to do with it, it would also be due to that [email protected] PG2 OTA. The phone is permanently on PE2 now, with TWRP recovery installed to thwart any future OTA installations. Anyway, I'm just glad the phone 'fixed' itself.
I'm something of a noob here, so I appreciate your patience and help.
My wife's Nexus 5x applied the latest update for 7.1.1 and her phone then fell victim to the dreaded bootloop. I was able to get through this guide to apply a rescue OTA: https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view (sorry, I can't post the hyperlink to an external site since I'm so new here, lol).
All of the steps completed down to step 21, when I tried reboot after the update - it rebooted then went right back into the boot loop.
The OTA I used was for Bullhead N4F26O (which is the one I should use based on the guide). I also tried N4F26I, but the OTA failed and it went straight to the bootloop.
I ran out the battery, charged it a bit, and tried again, but ran into the same problem (update completes, reboot, bootloop starts again).
Does anyone else have any more ideas on what I can try? At this point all I really care to do is recover any photos I can from the device (my wife forgot to setup image backup on her phone and USB debugging was never turned on). Google Fi already offered to send out a replacement, so I'm not worried about getting the device fully functional again.
Thanks for your help.
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
LeChuck5000 said:
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
Click to expand...
Click to collapse
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Tulsadiver said:
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Click to expand...
Click to collapse
I can get it into fastboot, and can sometimes get it into recovery (but not consistently...it often just goes into the bootloop when I try to launch recovery).
To apply the update I just followed the guide I linked to in my OP. First, installed the adb, fastboot, & usb drivers on my computer. I then put the phone into recovery, and wiped the partition cache. I then connected the phone to my PC, picked Apply update from ADB on the phone, and ran adb sideload c:\MyNexus\bullhead-ota-n4f26i-06953aec.zip from the command line on my PC.
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Arrivale said:
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Click to expand...
Click to collapse
You stick it in the oven? Use a heat gun? How hot/long?
tallgrasshawk said:
You stick it in the oven? Use a heat gun? How hot/long?
Click to expand...
Click to collapse
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
How else?
Arrivale said:
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
Click to expand...
Click to collapse
I don't have a heat gun, how else can I heat it? Also, excuse my ignorance, I'm new to phone thing since my Nexus 5x went into bootloop last week I've learned a lot, fast. Where exactly is the EMMC? How else can I heat it? I'm desperate to get this phone working as I just went overseas and Nexus won't send a replacement here
My attempt at the Rescue OTA fails in step 19, I can't get the device state to be "unlocked" does anyone know how to unlock it when the phone is in bootloop? (So all I really have access to is command prompt, which says I can't unlock the oem) HELP!?!