Related
I recently bought Samsung Focus from eBay. It has two problems. First, its battery has huge drain. It don't even last for a day. Secondly, there's problem with power functionality. Whenever I power it off it automatically reboots itself instead of powering off. I did hard reset as well but the problems are still there.
You might want to explain a couple of more details like if you are trying to power the focus off while charging it will turn right back on. Also, you can try the official roms located in the in the development section and reflash the rom. In the about section what version of wp7 are you running ie. nodo, pre nodo, mango beta. Also, did you do a full reset in the settings section, through the diagnosis app? You might want to try a full recovery through the diagnosis app. Instructions are in the diagnosis codes thread stickied in the Focus general section.
Also would be helpful if you gave a few details about the condition. New? Used?
I'm going to guess used.
The original owner may have improperly charged the battery all the time. Solution? Buy a new battery. They're pretty cheap. Be sure to look for Samsung Galaxy S batteries as well, since they're the same batteries as the Focus.
If it were me, I would start by flashing the original ROM on the website... you never know what the original owner did, maybe he/she improperly tried to hack the phone and did something.
After flashing so you know you are dealing with a fresh install I would disable wireless/Bluetooth if you do not use them regularly, I would then suggest getting a new battery as already stated.
It's used phone. It becomes warm even in sleep mode. I guess it keeps on consuming battery. And instead of powering off it reboots, even if not plugged to charger or pc.
I think you guys are right; I should try reflashing it. But I never did this thing before. Will it go back to original state, like when it was locked to at&t?
fawadrafique said:
It's used phone. It becomes warm even in sleep mode. I guess it keeps on consuming battery. And instead of powering off it reboots, even if not plugged to charger or pc.
I think you guys are right; I should try reflashing it. But I never did this thing before. Will it go back to original state, like when it was locked to at&t?
Click to expand...
Click to collapse
The reboot instead of power off isn't normal.
I can think of 2 things to try:
- Find someone with a Focus and try their battery in your phone (also your battery in theirs)
- Reflash
I can vouch it will stay unlocked, the flash doesn't affect NCK (network lock) - I had to do the same as you
GL and I hope it's not hardware.
Thanks guys for you guidance, but unfortunately even after reflashing I still have those issues.
I used "Samsung i917 Focus firmware UCJK2 AT&T USA" to reflash my phone. The phone has gone back to 7004 state but the problems are still there.
Do you think I should do reflashing with "Samsung i917 Focus firmware UCJK3 ATT USA 4K" this time?
I'm going to buy new battery to see if the new one works. But what do you think, is problem with powering functionality?
Thanks.
fawadrafique said:
Thanks guys for you guidance, but unfortunately even after reflashing I still have those issues.
I used "Samsung i917 Focus firmware UCJK2 AT&T USA" to reflash my phone. The phone has gone back to 7004 state but the problems are still there.
Do you think I should do reflashing with "Samsung i917 Focus firmware UCJK3 ATT USA 4K" this time?
I'm going to buy new battery to see if the new one works. But what do you think, is problem with powering functionality?
Thanks.
Click to expand...
Click to collapse
I think you should try to go warranty on this. If the board/power adapter assembly is bad, you would just waste more money on this by buying another battery. That's why I suggested find someone to swap batteries for a day.
Reflashing with another Rom isn't going to change much and will just take more time, as this is clearly a hardware issue, this is clear by now.
Maybe drop in a AT&T store and ask for some help? They might know this issue and provide more help...
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"
Its a Note 4 SM-N910F, Android 6.0.1, BB N910FXXU1DPE2, kernel 3.10.40-7733605 [email protected] #1
i feel I have tried everything... History:
Phone has been working fine for a year, upgraded to 6.0.1 no problems about 2 or 3 months ago. no new apps installed. Last week it started getting very laggy, keyboard strokes took for ever to register. I thought, ok, time to to a factory reset to blow out any old cobwebs. Did it via the menu. However the phone froze midway thought. I left it for an hour and then pulled out the battery. I popped it back in and it performed the reset without me having to press anything. Cool, thats good I thought.
Now I was going to change the battery, so I powered off as normal and put my other 2 week old original samsung battery in, and it would not power on. After a few reinsertions it powered back on. I though i have to do another reset. So I tried, and it would not reset. It just died. I cant restart the phone, it dies. If I shut it down normally. it wont turn on back on, I have to take out and reinsert the battery multiple times, holding down the powerbutton between to discharge. this can take up to 10 tries now. Sometimes it will go th the unable to bot in normal mode and "downloading , do not turn of target, but it will stay there for ever, more than an hour.
Every 15-20 tries it would turn on, let me get in via pin, only to start freezing up within a min, and then die again. Somewhere I read that a guy hada similar problem, and he used wakelock and that worked, on level 4. I managed to download that and used it, and hey presto, it works!
Now I had to power down the phone for a reason, and it took me about 30 min of battery and powerbuttonholding before it managed to boot up, and I was quick enough to start wakelock on level 4.
It wont boot in to safe mode, it wont boot in to recovery mode, it wont boot in to the factory reset mode. Its the same with either battery, and different cables.
Any ideas what i can do here, or what could be wrong? I havent gotten it wet or banged it.
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
armstrongracer said:
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
Click to expand...
Click to collapse
are you still under warranty? i sent mine to a samsung center, the guy recognized the problem as the motherboard, said I wasnt the first. That was 3 weeks ago, they are STILL waiting for the parts. They say the Samsung factory are way behind with repair parts, etc etc. I am hoping it will go under warranty. Ill update when I know!
I've been having the same problem that started yesterday morning. I've tried a few different solutions but nothings worked, I get the feeling that my phone is dead and I'm not in warranty either. I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
neils0911 said:
I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
Click to expand...
Click to collapse
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
bonfilet said:
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
Click to expand...
Click to collapse
Definitely...surely it couldn't have been that hard to make a device with a battery that was still removable on the newer phones. It's frightening how many forum posts I've found with people having their phones just brick out of nowhere (and that's just the note 4). I've given up trying to fix mine, I've tried every method I could find and nothings worked. I can only assume that this problem is simply the motherboard of the phone not working anymore. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
neils0911 said:
. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
Click to expand...
Click to collapse
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
mymigi said:
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Click to expand...
Click to collapse
If you are able to boot it into Download Mode then you should Download Stock Rom file for Galaxy Note 4 from Sammobile and Flash it through Odin..
Everything will be OK... ?
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can find here firmware for N910A , 5.1.1 and 6.0.1 : https://simunlockremote.com/firmware-support/
bonfilet said:
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
Click to expand...
Click to collapse
I think the camera on the note 4 is absolutley terrible. I might even go so far as to say the pictures are unusable. the applied noise reduction renders everything splotchy, colors are off and its not sharp at all. and Im not talking dark conditions here.
Anyway, my phone was repaired under warranty and is back to working as it should. It was indeed the motherboard, so if you have the same troubles I had, those are your best bets.
I don't think replacement via warranty will be available. I will attempt to power into download mode and verify if I can get it back up and running. If not, a good ole paperweight.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here ..
https://www.androidfilehost.com/?fid=24459283995298017
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here. .
https://www.androidfilehost.com/?fid=24459283995298017
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
onno72 said:
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
Click to expand...
Click to collapse
My phone is also random Rebooting
It also shuts down at 25% of battery remaining, Have you also faced similar issue?
Download the app "Wake Lock" and run the Partial Wake Lock option. Apparently the updated software impacts the CPU. For the restarting issue, put it in the freezer for a couple minutes. You may have to take the battery out once, but it has worked for me every time.
This looks very much like the issue reported here:
https://forum.xda-developers.com/no...-error-fix-t3434335/post72944466#post72944466
There are temporary fixes (wakelock), but ultimately this is a harware issue, and the fix is a new motherboard.
I think that underlying it is a problem with heat affecting the eMMC chip or its connection to the motherboard.
See also:
https://us.community.samsung.com/t5...ePhones/thread-id/12183/highlight/true/page/1
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/
Hey can u pls get me the stock firmware for n910gddu1dpb4
You might find this interesting. Since I couldn't get mine to power up at all, I called Samsung tech and they quoted me $75 to fix it and they would pay for shipping. I figured it was better then getting another phone off Swappa. 2-3 weeks later i get an email that they are repairing it under warranty at no cost to me. I got a refurbished phone since i know my IEMI number was different. they didn't explain why. Anyway, I got lucky i guess.
hello everyone, I recently received a galaxy A3 A300FU that had problems of bootloop, my cousin send it to me so I can help him with the problem, since he was not going to do a factory reset (because he has a lot of pictures of his now deceased wife may her soul rest in peace) I was going to try a dirty firmware install or a 3rd party program like "fonedog or thenorshare" but when the phone got to me the phone had no sign of life, nothing, no booting no splash screen nothing the phone is completely dead, I called him to know if the phone had a damage screen before, he swears not, so the phone has to be damaged in shipping or it may be another problem that I'm not aware of, I tested the motherboard and the battery with a multimeter I found the voltage is good and all the connections were good, everything seemed to be alright.
So my question is: -is there any way to know if the screen is still working with it not turning on ?
-if not, how can I recover the data knowing that the screen is black and the phone shows no sign of life besides
the tests I did with the multimeter that were all good ?
note: for now I have no way of buying spare parts to test with.
Thank you for reading, I hope you doing great stay safe
sorry for the spelling English isn't my first language
Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.
Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.
XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/
XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha
angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.