Related
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
sumasage said:
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Can you get to stock recovery for a factory reset?
It doesn't even let me get to recover. Picking recovery from the bootloader screen just make the phone restart like it try to go to recovery but then it come back to the same screen saying it can't find valid operating system.
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
trim81 said:
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
Click to expand...
Click to collapse
What did you say Google? Did you tell them it happened while re-locking boot loader? I am on same boat....I tried to relock bootloader and getting Can't find valid operating system
I rma the unit as well.
sumasage said:
I rma the unit as well.
Click to expand...
Click to collapse
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
ram4ufriends said:
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
Click to expand...
Click to collapse
Tell them exactly that. It no longer boots
As soon as I said there was no valid os the rep proceeded to rma. Seem like it a know issue so they didn't bother to transfer me to tech support.
Not sure if you want to try any of these solutions before you RMA, but here's another thread on the same "No OS ....." with several options, might be worth a try?
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
megernic said:
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...l-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
Click to expand...
Click to collapse
Did you check or uncheck OEM unlocking in Developer Options before doing this?
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!
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.