Develop Bugs

[Q] Nexus 7 suddenly bricked ?

Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.

Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.

I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app

There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.

The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!

Do u guys have the most up to date version of whatever particular recovery that you're on?

Yep. I've flashed the stock recovery multiple times to no avail. :/

nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?

wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/

nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?

wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.

nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.

wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!

Probably hard bricked my K420n using service menu

So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system

Krystiannnnnn said:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Click to expand...
Click to collapse
It shouldn't happen though
Try to flash the firmware again in download mode.

Krystiannnnnn said:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Click to expand...
Click to collapse
Are you sure LG Drivers well installed? They might not have been and that's why your device isn't recognized. If your device gets recognized while it's in download mode, you can try these guides:
LG Bridge: https://forum.xda-developers.com/lg-k10/how-to/guide-unbricking-flashing-firmware-due-t3380529
LG UP: https://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839

Finally, after 5 hour tough battle with my phone, I made it to boot up.
thx for help xd

Krystiannnnnn said:
Finally, after 5 hour tough battle with my phone, I made it to boot up.
thx for help xd
Click to expand...
Click to collapse
Ciao bro, how did you solved that, I did the same mistake and now have the same problem

dioariete said:
Ciao bro, how did you solved that, I did the same mistake and now have the same problem
Click to expand...
Click to collapse
Flash ROM 5.1.1 (for me (K420n), flashing ROM 6.0 didn't work - I had to update to 6.0 earlier) until phone boots up. I think that I used this ROM: https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319
You can also try to recover/flash via TWRP but this method didn't work for me.

Krystiannnnnn said:
Flash ROM 5.1.1 (for me (K420n), flashing ROM 6.0 didn't work - I had to update to 6.0 earlier) until phone boots up. I think that I used this ROM: https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319
You can also try to recover/flash via TWRP but this method didn't work for me.
Click to expand...
Click to collapse
Thank you bro, you helped me solve the problem :good: . Have a nice day !

Touch Screen not working at all

Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks

I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet

touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!

after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.

tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks

milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.

milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!

Question A52s random “Can’t load Android system.” when rebooting

Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!

Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)

IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.

My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!

Question Super strange problems with OnePlus 9 Pro

Hey guys,
I'm forcing some super strange problems with my beloved OnePlus 9 Pro since yesterday. I already did everything I could imagine for the whole 2 days, but doesn't matter what I try, it's not helping. I hope you can maybe help me out with your ideas, as I don't know what else I should do!
It all started yesterday in the morning, where I noticed that the screen rotation was not working, even after I restarted the phone (which is definitely taking longer now than before). During the day I noticed that the phone got overheated a lot of times (I know overheating is an issue but since the last update it worked pretty well with mine), even though it was in the shadow, at 25 degrees without any hard tasks, thus I noticed the first software bugs e.g. unlocking took a lot of time, with black screen, fingerprint sensor not visible, apps lagging...In the display settings, I can't change the video enhancement settings because it's telling me the phone is too hot - all the time! The next I noticed that the video function in the original camera app is suuuuper laggy, so it's not possible to take any video at all (attached a screen recording). Other camera apps work fine for the video, but hardware detection apps can just detect the 12MP sensor? During the day I then ran a sensor identification app which was able to identify all the sensors on another device but showed error messages for all my sensors (attached as well). I ran multiple security scans (Bitdefender, Avast, AVG, Kaspersky...) without any problems. Also, I updated the software and already did a hard reset - which changed nothing.
Now it's getting even more strange... As the phone got slower and slower with the day, I checked the storage and noticed that a huge amount (more than half of my whole storage) is full of system data AND IT KEEPS EXPANDING WITH ANY MINUTE. I have to delete more and more of my private data to keep the phone running... I attached you some screenshots over the time to recognize the growing data.
I hope so much that you can help me out with that! Already thanking you for your responses...
Some background information about my device...
It's a OnePlus 9 Pro, 256gb, 12 GB RAM EU Original Oxigin 12 Version (installed the new update around a week ago), non-rooted. I've installed some MOD APKs but always kept scanning with Bitdefender after that - anyway, I know that's not super safe.
Thanks so much,
Max

Screen record of the camera bug:
Record_2022-02-13-20-07-20.mp4
drive.google.com

I would think possibly factory reset w/wipe data might fix? I would be weary of mod apks. I hope it's something simple and am not sure but thought I'd share what comes to mind.

If you did a factory reset and it didn't help you with your issue, I would STRONGLY suggest using MSM tool to re-flash your phone and eliminate any possible issues with the OS. If you're not ready to use MSM, well, than claim your warranty...
Btw. MSM tool is for unbricking OP phone, it's nothing complicated or "dangerous". But it does a clean flash from the scratch on the phone including formating all the partitions, etc...

Safe mode and see what it does.
If it still doing it it sounds like a mobo failure.
No rootkit should have survived the factory reset unless you reloaded it How much internet bandwidth is it using at idle? Think back to what you did when it started. In the last month or so?
Try to find what is running in the background.
If you come up with nothing try reflashing to the last known good version... not the newest.
If it continues, it's almost certainly hardware. Flash memory shouldn't get corrupted so even if a reflash fixes it... keep an eye on it.

blackhawk said:
Safe mode and see what it does.
If it still doing it it sounds like a mobo failure.
No rootkit should have survived the factory reset unless you reloaded it How much internet bandwidth is it using at idle? Think back to what you did when it started. In the last month or so?
Try to find what is running in the background.
If you come up with nothing try reflashing to the last known good version... not the newest.
If it continues, it's almost certainly hardware. Flash memory shouldn't get corrupted so even if a reflash fixes it... keep an eye on it.
Click to expand...
Click to collapse
Could be possible, as I restored a backup. But even before I restored the backup, I had the screen rotation and camera lagging problems without having anything intalled but the fresh OS. I really just started 2 days ago out of nothing, that's why I was so surprised. Also, the internet bandwith is quite normal, and it keeps expanding the system data without running internet connection... have the phone off the whole day now as it is not possible to use any app at all as the system data is at 70% of the whole storage now and still keeps growing... Always have to delete another app to use my phone for 5 min lol .
I'll try the safe mode and see what's happening. After that, I'll try to wipe the whole data again, like @Samuel Holland suggested and will reflash with MSM like @ekin_strops told (to an older version than).
Thank you very much so far guys,
I will keep you posted!
Max

baacon said:
Could be possible, as I restored a backup. But even before I restored the backup, I had the screen rotation and camera lagging problems without having anything intalled but the fresh OS. I really just started 2 days ago out of nothing, that's why I was so surprised. Also, the internet bandwith is quite normal, and it keeps expanding the system data without running internet connection... have the phone off the whole day now as it is not possible to use any app at all as the system data is at 70% of the whole storage now and still keeps growing... Always have to delete another app to use my phone for 5 min lol .
I'll try the safe mode and see what's happening. After that, I'll try to wipe the whole data again, like @Samuel Holland suggested and will reflash with MSM like @ekin_strops told (to an older version than).
Thank you very much so far guys,
I will keep you posted!
Max
Click to expand...
Click to collapse
Msm is the only thing if you were rooted and had malware get in the system

blackhawk said:
Safe mode and see what it does.
If it still doing it it sounds like a mobo failure.
No rootkit should have survived the factory reset unless you reloaded it How much internet bandwidth is it using at idle? Think back to what you did when it started. In the last month or so?
Try to find what is running in the background.
If you come up with nothing try reflashing to the last known good version... not the newest.
If it continues, it's almost certainly hardware. Flash memory shouldn't get corrupted so even if a reflash fixes it... keep an eye on it.
Click to expand...
Click to collapse
Just tried it in Safe Mode now... screen rotation and video function are still not working, and the system data is also still expanding (around 1,5gb in 10 min). I'll try to flash from the beginning with MSM tool now and see what happens.

After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?

baacon said:
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
Click to expand...
Click to collapse
Reboot the PC...
Try a different cable and port.
Check Windows Event Viewer for error messages.
Driver, is the right one loaded? Try updating or rolling it back.
Try different sequence or timing with the buttons.

baacon said:
Also, in fastboot mode it's not getting recognized by my pc
Click to expand...
Click to collapse
Update driver in device manager. Choose from list of manufacturers, ONEPLUS, and reinstall all 3 again.
Also, Check status of adb devices. If it's "unauthorized" authorization was revoked. You need to unplug the phone then delete this file : C:/users/<username>/.android/adb key
And replug your phone, then allow connection again.
A last resort is to extract payload.bin, then flash all partitions again. Here's a good tutorial. Never tried it though...
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com

baacon said:
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
Click to expand...
Click to collapse
temp boot twrp. in twrp reboot edl mode.

baacon said:
After an hour, I'm still figuring out how to boot my OP to EDL mode... watched dozens of YouTube videos, but it's always ending in fastboot mode after I connected it to my pc (even just when holding the volume buttons without power button). Also, in fastboot mode it's not getting recognized by my pc. Any ideas on that? Or this there any other method to force it into EDL mode?
Click to expand...
Click to collapse
had the same issue.
I somehow expected some kind of special EDL screen on my phone.
but its just black.
start the MSM tool with pressing the start button.
shut down the phone.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
additional info:
MSM tool for OP9pro you can find here : MSM tool OP9pro
More guides how to use it find here : MSM guide

vincemue said:
had the same issue.
I somehow expected some kind of special EDL screen on my phone.
but its just black.
start the MSM tool with pressing the start button.
shut down the phone.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
additional info:
MSM tool for OP9pro you can find here : MSM tool OP9pro
More guides how to use it find here : MSM guide
Click to expand...
Click to collapse
yes, it's exactly the same with mine... I noticed that the problem is the Qualcomm driver, as the device is shown with an error in other devices. Already tried to reinstall it 3 times, as well, with the Windows driver verification deactivated. Also tried the manual way, but it always says that windows can't find drivers in my Qualcomm folder... Will try it with another computer later and see how it works.

baacon said:
yes, it's exactly the same with mine... I noticed that the problem is the Qualcomm driver, as the device is shown with an error in other devices. Already tried to reinstall it 3 times, as well, with the Windows driver verification deactivated. Also tried the manual way, but it always says that windows can't find drivers in my Qualcomm folder... Will try it with another computer later and see how it works.
Click to expand...
Click to collapse
Try online automatic driver update.

My friend, after using MSM tool, do NOT restore back-up!
If you restore it is all for nothing.

Alright, it worked now - the problem with the MSM tool worked with another laptop, don't know what was wrong with the other one. The good news is that the video function in the camera app is now working again (which is super important for me) BUT the sensors are still all not working and won't be detected by the phone. Do you have any other idea what could cause that? They stopped working from one day to another without any physical damage or anything. I'll also keep you posted about the storage (if it still keeps growing), so far it's growing but because the device installs all the updates...
(and for sure I'm going to install everything manual now )

baacon said:
Alright, it worked now - the problem with the MSM tool worked with another laptop, don't know what was wrong with the other one. The good news is that the video function in the camera app is now working again (which is super important for me) BUT the sensors are still all not working and won't be detected by the phone. Do you have any other idea what could cause that? They stopped working from one day to another without any physical damage or anything. I'll also keep you posted about the storage (if it still keeps growing), so far it's growing but because the device installs all the updates...
(and for sure I'm going to install everything manual now )
Click to expand...
Click to collapse
Try it in safe mode. Don't update anything until sensors are tested. If no go, check for system updates. The firmware may have become corrupted, reflash to the known good stock rom. Firmware shouldn't go corrupt and if so may indicate a mobo failure... keep an eye on it.

blackhawk said:
Try it in safe mode. Don't update anything until sensors are tested. If no go, check for system updates. The firmware may have become corrupted, reflash to the known good stock rom. Firmware shouldn't go corrupt and if so may indicate a mobo failure... keep an eye on it.
Click to expand...
Click to collapse
I am back to my latest known version of Android that worked well with my sensors. I also already tried in safe mode again. The crazy thing is that the sensors are not even shown in apps like device info 360 - it says that my phone has 0 sensors.

baacon said:
I am back to my latest known version of Android that worked well with my sensors. I also already tried in safe mode again. The crazy thing is that the sensors are not even shown in apps like device info 360 - it says that my phone has 0 sensors.
Click to expand...
Click to collapse
It's possible you lost a chipset. It show battery temperature? A repair manual be useful if you could dredge one up online.