Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!
Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.
I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?
unfortunately not. Any ideas on next steps?
That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.
I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks
Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell
It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.
Related
So my phone has been this way since Nov 2017, there are files that I need access to and would truly appreciate some guidance
I was experiencing issues with the bluetooth on nextbit previously so I installed a new rom after flashing the device. Once the rom also gave issues I decided to revert back to the Nextbit 7 OS and one fine day when the phone restarted it wouldnt go past the "nextbit" splash screen. Tried installing the OS again however the PC wouldnt recognize the phone anymore, switched laptop to a Mac and got the same issue
Any help would be greatly appreciated
It wont let me post a URL link. I have taken www out hopefully it allows to view the video, shows exactly whats wrong
youtube.com/watch?v=ImIk5CErWf0
It looks there's something wrong with the system boot, since it's reaching the blue boot-animation and it stays there (probably before loading the adb stuff). Fortunately u did unlock the bootloader and that annoying initial screen may be helpful this time, did u try to reach recovery or fastboot mode from there (pressing some volume key)? It's pretty hard for it to be broken there too and in such a case I would think about some hardware fault. Anyway from the recovery (I hope u have TWRP, if not install it with fastboot) you should be able to do whatever u want, including recovering your files or (re)installing a rom
My wife got this error today:
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
We aren't even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
I've seen a few posts of people having this issue, I haven't seen anyone state they recovered, but I wanted to make sure.
I figure since I can't even boot to recovery there is nothing to be done??
History:
This phone is < 3 months old. It has not been modified (no unlocked bootloader, root, or even USB debugging enabled AFAIK). It rebooted on her once in the middle of her just using it within the past 48 hours. Today she saw a notification saying the phone needed to reboot because of a system update. She did not reboot it yet, but was using it fine. When she went to use it this afternoon (after having been on it 15 minutes prior) it was booted to this error screen.
On a side note, Google refuses to send a new phone even though this one is < 3 months old and the problem appears to have been caused by their software updating and rebooting her phone without permission.
thanks
TraderJack said:
My wife got this error today:
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
We aren't even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
I've seen a few posts of people having this issue, I haven't seen anyone state they recovered, but I wanted to make sure.
I figure since I can't even boot to recovery there is nothing to be done??
History:
This phone is < 3 months old. It has not been modified (no unlocked bootloader, root, or even USB debugging enabled AFAIK). It rebooted on her once in the middle of her just using it within the past 48 hours. Today she saw a notification saying the phone needed to reboot because of a system update. She did not reboot it yet, but was using it fine. When she went to use it this afternoon (after having been on it 15 minutes prior) it was booted to this error screen.
On a side note, Google refuses to send a new phone even though this one is < 3 months old and the problem appears to have been caused by their software updating and rebooting her phone without permission.
thanks
Click to expand...
Click to collapse
It is under warranty. Phones brick on updates more than any other time. I don't see where they really have a choice but to replace it.
TraderJack said:
My wife got this error today:
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
We aren't even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
I've seen a few posts of people having this issue, I haven't seen anyone state they recovered, but I wanted to make sure.
I figure since I can't even boot to recovery there is nothing to be done??
History:
This phone is < 3 months old. It has not been modified (no unlocked bootloader, root, or even USB debugging enabled AFAIK). It rebooted on her once in the middle of her just using it within the past 48 hours. Today she saw a notification saying the phone needed to reboot because of a system update. She did not reboot it yet, but was using it fine. When she went to use it this afternoon (after having been on it 15 minutes prior) it was booted to this error screen.
On a side note, Google refuses to send a new phone even though this one is < 3 months old and the problem appears to have been caused by their software updating and rebooting her phone without permission.
thanks
Click to expand...
Click to collapse
Two questions. 1) Was it purchased from Google? If not, that may be why the issue with warranty replacement. 2) Is the phone a Google version (AKA unlockable bootloader)? If it is, you could always do a bootloader unlock which will also force a factory reset and if successful allow you to load a factory image. If not, there is nothing you can do without getting into recovery.
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?
Hi, is there anyone who has ever encountered with such issue? It just randomly restarting. I've done a MSMTool Unbrick Method but no avail, it booted but still randomly restarting. I suspect there is a hardware malfunction.
List of issues that I encounter :
1. Random reboot, a lot
2. Blinking screen on and off when boot animation shown
3. Always fail to do system update, locally and OTA
4. Google play store, gboard, oneplus launcher keeps crashing
5. ???
Will update the list once I remember and encounter a new one.
I've tried multiple method but still no sign of good news. I've tried wiping data & cache using default recovery, all in one tool and lastly MSMTool. Pls help!
Anyone?
Now, even MSM Tool cannot detect my device.
At first, my PC detected my phone as Qualcomm HS-USB Diagnostic 900e, something along that line. And then I found this tutorial to convert that into QDLoader 9008. But when I clicked enum, my MSM Tool didn't detect anything.
Few days ago my device start to restart by itself and then bootloop.
Normally I got bootloops in other phones (HTC) coz of MY fault always - like flashing wrong firmware or wrong version of boot.img but just like this bootloops is quite strange.
Maybe send it back - warranty if your bootloader is still closed etc.
Tapatalk via OnePlus 7T
I am really sad that my device still keeps restarting. I've countlessly tried to reflash the software using whatever tools exist. I've noticed something though, when playing youtube video, the video sometimes breaks (blur, I'll attach the ss later) and after several seconds it became normal again.
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Coddeh said:
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Click to expand...
Click to collapse
Try flashing the same firmware you're currently running using Odin and HOME_CSC to keep your data, possible it will replace and fix the corrupted files causing the bootloop
So last night I tried what you have mentioned. It didn't change anything unfortunately.
I then thought it might be worth trying an older firmware. I tried rolling back to the previous firmware and then to android 10. Both of these ended up making things worse and it would boot loop at the android startup screen.
Luckily I managed to get back into Odin mode and put the current firmware back on and I'm now back to square one.
OK so I have had a thought. I've seen that some people have managed to establish a USB connection to thier device through TWRP and managed to backup their data through that. I've also seen that on older phones you can use odin to only flash TWRP and then boot into it. I'm not sure if things have changed drastically and you are unable to do that on the S20 ultra now. After my data (pictures and videos) was backed up I could then reflash the recovery back to stock and do a factory reset to fix the bootloop.
Does this seem plausible?