Related
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
nkomp18 said:
Hello,
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
Click to expand...
Click to collapse
The single vibration with no screen normally means the batteries dead, and it's possible that it's not charging when hooked up to your computer, open it up, take the battery out for 15 seconds, put it back in, then plug it into the charger for an hour or so.
nkomp18 said:
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
Click to expand...
Click to collapse
Are you sure the zip you downloaded is cm11? There was an issue with yesterday's first cm12 build that resulted in bricked devices.
The device can be recovered
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
mikeioannina said:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
Click to expand...
Click to collapse
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
nkomp18 said:
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
Click to expand...
Click to collapse
Go to your custom recovery, wipe /data /cache /Dalvik and /system, then flash CM+GApps. If you used the tool in my thread, you'll have to boot into COS before flashing anything.
Now it's almost perfect,
The power button only works to lock the screen, not to turn it back on again.
As you can imagine, the phone is unusable if I can't wake it up from sleep.
I tried a lot of things. First of all it's not a hardware issue because the power button works flawlessly to lock the phone or to reboot. It only fails to wake the phone up, which sounds like a software issue.
I tried the option "double tap to wake" and that does nothing. The only thing that wakes the screen is connecting it to a USB.
Any ideas?
I noticed after I followed the instructions some things changed in my phone. The OPPO logo is different when the phone loads and fastboot graphic is different. Now I get Chinese characters whereas before I believe it was an android robot.
I suspect this is causing the power button errors. Any ideas how to put it back?
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
AWretchSavedByGrace said:
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
Click to expand...
Click to collapse
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
thelad said:
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
Click to expand...
Click to collapse
So done that and got one black screen and the white light,went to work had 3g/4g on all day didn't get one black screen,got home connected to wifi and I got a black screen,so something to the with wifi seems to cause it for me
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Paradoxxx said:
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Click to expand...
Click to collapse
I think I'll have to its pissing me off now,goes great for hour or two then I'll get this black screen 4 or 5 times in a row
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
nono77240 said:
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
Click to expand...
Click to collapse
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
I don't know how much time after, maybe 6 hours later or so...
I had a freeze yesterday evening and had to reboot my phone.
Everytime it freezes on reboot and I have to wait 3 to 4 tries before the phone really boot.
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
I created a RMA ticket this morning.
My phone will go to repair center
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
My situation
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Breecko said:
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Click to expand...
Click to collapse
Have you tried holding power and volume down for a few seconds without the cable plugged into the phone?
thelad said:
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
Click to expand...
Click to collapse
acmerw said:
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
Click to expand...
Click to collapse
AWretchSavedByGrace said:
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
Click to expand...
Click to collapse
I received a mail yesterday evening saying that they can't take my phone and I have to do a factory reset.
I replied to this mail saying that I did multiple factory resets and even do a remote session with a oneplus tech support.
They sent me a mail an hour after with a number and the process to send my phone.
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
anyone?
SallyTheDevil said:
anyone?
Click to expand...
Click to collapse
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
muhamet said:
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
Click to expand...
Click to collapse
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
SallyTheDevil said:
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
Click to expand...
Click to collapse
Force restart,press volume up and power button same time
muhamet said:
Force restart,press volume up and power button same time
Click to expand...
Click to collapse
Volume up and power doesn't do anything
Volume down + power restarts the phone but it comes to the same samsung black screen
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
k3lcior said:
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
Click to expand...
Click to collapse
I can't enter recovery mode
Volume down + power restarts but I did try to go to recovery by releasing volume down and pushing volume up the second screen goes black but it's not working
I can only enter download mode when it's connected to pc with odin running
Could it be a hard drive problem?
And I'm pretty sure i got the right firmware
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
k3lcior said:
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
Click to expand...
Click to collapse
tried it, it doesn't recognize the phone.
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
SallyTheDevil said:
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
Click to expand...
Click to collapse
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
SallyTheDevil said:
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
Click to expand...
Click to collapse
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
muhamet said:
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
Click to expand...
Click to collapse
done that already, it flashes the firmware successfully but still won't boot, it just gets stuck at the same screen.
JulianaO said:
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
Click to expand...
Click to collapse
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
SallyTheDevil said:
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
Click to expand...
Click to collapse
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
JulianaO said:
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
Click to expand...
Click to collapse
yh I installed that update too and this happened later the same night.
unfortunately for me all the shops n services are currently shut down because of the Co-Vid situation so i have to wait for now.
thanks for sharing, lemme know what happens.
I've had these same problems before. When flashing with Odin, don't populate the last slot with anything (the HOME_CSC slot). Flash it to the device without auto reboot on, restart the device manually and hold vol up + down to get to blue scrern, then unlock bootloader. Let it restart, then reflash ROM.
So, this is more for interest than anything else, but here's the scenario.
A friends 5T did a sudden shutdown. He picked up the phone, unlocked the screen and opened WhatsApp. An error message flashed on the screen - too fast to read - and the phone shut down immediately. He tried to restart, but it was stuck at the boot logo (circle with rotating dots).
We had a go at trying to get it back up again and did the following. I should note that both recovery and fastboot were available, however the bootloader was locked.
1) Booted into recover and sideloaded the latest OnePlus ROM - Stuck at boot logo
2) Got hold of unbrick tool and flashed with latest version (seems to be Android 8.1) - Stuck at boot logo
We were about to give up assuming a hardware issue when on a whim I tried the old unbrick for Android 7. Amazingly the phone booted. I quickly enabled bootloader unlock and unlocked the bootloader. We then flashed TWRP and tried to flash a custom ROM (Bliss in this case) - followed all the instructions to the T and got stuck at the (Bliss) boot logo (very cool boot logo by the way).
We then flashed a rollback version of Android 7 designed for folks coming back from one of the early beta 8 versions. This booted again, although it replaced TWRP as expected. We then sideloaded the latest version of 7 we could find (seems to be 7.11).
So here's the question. The only thing not working on the phone is the Wi-Fi. It does not switch on and shows a MAC address of 02:00:00:00:00:00 which indicates an issue. So I'm assuming something to do with the Wi-Fi has died on the mainboard. However, Bluetooth still works, SIM cards still work. I can use the phone normally with a mobile data.
So, what would stop anything above version 7.11 from booting if just the Wi-Fi is broken? Is there some link to this that was added in Android 8. It would great to update to 8 or 9 and still be able to use the phone, as everything else seems to work.
P.S. I have noticed that the camera takes about 10 seconds for the image to appear after the app opens, then works fine after that. Related maybe?
Anyway, was just wondering if anyone knows the inner workings and can shed some light on this one.