Your device is corrupt ... Red warning - Nexus 5X Q&A, Help & Troubleshooting

I know that this issue has been discussed several times here on the forum, but I couldn't find a solution for my situation. So, kindly bear with me.
I was talking on the phone when it slipped and fell down to the ground. When I lift the device, the screen was fine but the touch was not working. I couldn't draw the lock pattern or type the password or anything. I restarted the device several times but without success.
I found a youtube video on how to open the device to check the screen flat cable. I opened the device and checked the cable. It was a little bit loose, I secured it and put everything back. I turned on the device and the screen worked, but it gave the message "Your device is corrupt ..." (Red warning).
The google support forum said that this warning is due "tampering" with the OS. This is not my case because simply, I don't know how.
I tried "Factory Reset" several times, but wasn't successful. The device keeps showing this warning and when I continue, it works for half an hour or so before it restarts again, and so on.
My problem now is that I don't know if this is a hardware or software problem.
I really appreciate all your help and support.
Best Regards,
mwahid

mwahid said:
My problem now is that I don't know if this is a hardware or software problem.
I really appreciate all your help and support.
Best Regards,
mwahid
Click to expand...
Click to collapse
That is what shows up on every boot after you unlock the bootloader. There may have been a short circuit of some kind and was viewed as tampering. It affects nothing in the way your phone operates but affects warranty.

If it is really bothering you, you can try to flash the factory image and relock the bootloader. Then re-unlock the bootloader to see if that gets rid of the problem. However, as stated above it does not affect how your phone operates; so personally I would just leave it.

Thanks for your reply.
The problem is that the device is not working properly. It keeps restarting every half an hour or so and sometimes it hangs even when I am not using it.
I checked the bootloader from the fastboot menu and it is locked. I didn't try to unlock the bootloader or reflash the device. This message appeared only after I opened the device to fix the screen.
I will try reflashing the factory image and see what will happen.
Thanks again for your help.

I followed this guide to the letter, but the problem is still the same. The phone works for a few minutes then suddenly restarts and displays the message "Your device is corrupt ..." (Red warning)
I really appreciate any ideas.
Thanks

Hello again,
Could a hardware malfunction be the cause of this problem?
I just want to know so I can evaluate my option whether to fix it or buy a new one.
Thanks,
mwahid

Im haveing the same problem but i never drop it or open it its did not boot half the time now its having none of it its will not even turn on so gg LG.

Related

Help: no display/power during rom upgrade on O2 Exec

I was attempting to upgrade the rom image (to an O2 rom for an O2 device), when the device powered itself off. It hadn't written anything, it just got to the splash screen where it said checking device.
My PC never shut down, just my Exec. I thought it was one of the various power offs that the devices do during rom flashing.
I can do a hard reset, and I get the screen that says press zero or x, but after that I never get anything. even if I plug the device in, I don't even get a charging light.
can anyone help me with where I should begin troubleshooting????
well, I just tried re-updating it, just to see what woudl happen, even though there is no display. I used the WM6 I found, and it made it through the radio stack (screen is now dark, no back lit, but can see X% upgrade completed), so it looks liek its working, just needs to finish the rom. I hope, lol!
well, it made it all the way through the rom update, and asked for a cold boot, but the screen just stays dark, even after the hard reset.
Any ideas anyone???
okay, problem solved! I was able to get the device into bootloader mode, and then ran a flash for WM6.
toast said:
I was attempting to upgrade the rom image (to an O2 rom for an O2 device), when the device powered itself off. It hadn't written anything, it just got to the splash screen where it said checking device.
My PC never shut down, just my Exec. I thought it was one of the various power offs that the devices do during rom flashing.
I can do a hard reset, and I get the screen that says press zero or x, but after that I never get anything. even if I plug the device in, I don't even get a charging light.
can anyone help me with where I should begin troubleshooting????
Click to expand...
Click to collapse
hi toast
i got the same problem with xda exec. i read all your thread but cant find any instuction which you might got. can you please let me know what you have done to solve that issue. cheers
how did you get it through!!
hey, you the got the problem to be solved, please help me too in solving this porblem. I am getting the same problem of that screen scrambleness. Please help through step by step information.
LMAO....help me too...it wont even sync with with the ative sync program...how am i supposed to even begin fixing this problem????

I think I bricked my tablet

My tablet is the WiFi only version. I had it unlocked and rooted previously.
So I downloaded the new 5.1.1 images, intending to finally switch to Lollipop, and I kept getting the "missing system.img" error when trying use the batch scripts.
So I found this guide:
http://www.talkandroid.com/guides/b...-lollipop-factory-image-on-your-nexus-device/
And tried to follow it to the letter.
Sadly, once I flashed the boot.img, the device wouldn't boot anymore and it won't show up in fastboot and adb.
I also can't seem to boot it into recovery mode. My volume down button is finicky so perhaps I'm not trying hard enough?
Is there anything that can be done?
Edit: Okay, I was being an easily-panicky moron. Stupid key. Must have tried it like 10+ times till it acknowledged my press.
All is fine... I think. Once it finishes optimizing a crap-load of apps.
So, after optimizing everything works fine?
Indeed it does. Marvellously.
Rooted, enjoying the latest of Android and even helped pinpoint the source of a long-standing problem I had with brightness.
It may even help battery life.
Same Problem still exists for me
I have the wifi only version and I seem to be at a loss now.
I cannot get into recovery no matter how many times I try
PC recognises device but as APX
Screen appears to be stuck on an image of Andy stood upright with a sort of hexagonal wire frame rotating in his belly with "erasing" underneath. Stays this way for hours/days and does not change. Have looked through all sorts of forums for help or do you guys think I should just give up??
ANY Help at all would be greatly appreciated
It seems that your device is toast Maybe your NAND storage is faulty and you will need to purchase a new mainboard
tommygraham429 said:
I have the wifi only version and I seem to be at a loss now.
I cannot get into recovery no matter how many times I try
PC recognises device but as APX
Screen appears to be stuck on an image of Andy stood upright with a sort of hexagonal wire frame rotating in his belly with "erasing" underneath. Stays this way for hours/days and does not change. Have looked through all sorts of forums for help or do you guys think I should just give up??
ANY Help at all would be greatly appreciated
Click to expand...
Click to collapse
I had a booting problem as well but i was able to fix it with nexus root toolkit

HELP! McAfee thinks my phone is rooted and locked me out

So a little background first. Over the past couple of weeks I've been having an issue where my phone just all of a sudden tells me that my sim is not recognized. Usually a power down and back up fixes it, but it's been getting worse and worse. I tried getting a new sim card but that didn't help.
So today the problem occurs again, and when I restart I get a McAffee screen telling me my phone is locked because it's been rooted (it has not). From what I can tell, the only thing it will let me do is enter a pin that I don't know. Do I have any options here, or am I totally bricked? Any help would be appreciated, I'm starting to panic.
Don't worry, your phone till okay.
the last option you can do is hard reset or try to flash stock
Edit: found similar topic here: http://forum.xda-developers.com/showthread.php?t=2796958

Device State: error!

Can't load into recovery or system, only fastboot mode. In fastboot, I get these errors:
https://imgur.com/a/bBdbnvH
It was previously unlocked until I tried flashing the recent December update.
Any ideas on how to get it back up an running? I haven't seen Secure boot: NONE and NOS Production: Error posted on here before or a state where it can't determine if it's locked or unlocked. I'll try ubreakifix otherwise. Thanks!
Ofuroski said:
Can't load into recovery or system, only fastboot mode. In fastboot, I get these errors: https://imgur.com/a/bBdbnvH It was previously unlocked until I tried flashing the recent December update. Any ideas on how to get it back up an running? I haven't seen Secure boot: NONE and NOS Production: Error posted on here before or a state where it can't determine if it's locked or unlocked. I'll try ubreakifix otherwise. Thanks!
Click to expand...
Click to collapse
Don't start a duplicate thread dude! Starting to sound like a Google FRP workaround to me. What does Google support say??
Same here (with Pixel 3 non-xl).
I don't know what to do. Recovery doesn't work, only fastboot mode with "device state: error!" .
Bootloader is locked, and I have no way of unlocking it, because fastboot times out.
It happened shortly after I took it in the shower (it's never a problem). Maybe it's not that waterproof.
Google support says the phone is probably done, but they can't help with the warranty because apparently I got scammed buying it second-hand, the invoice doesn't match the IMEI.
starcleff said:
Same here (with Pixel 3 non-xl).
I don't know what to do. Recovery doesn't work, only fastboot mode with "device state: error!" .
Bootloader is locked, and I have no way of unlocking it, because fastboot times out.
It happened shortly after I took it in the shower (it's never a problem). Maybe it's not that waterproof.
Google support says the phone is probably done, but they can't help with the warranty because apparently I got scammed buying it second-hand, the invoice doesn't match the IMEI.
Click to expand...
Click to collapse
I might be a bit late, but I had exactly the same issue, lost hope and all. I have tried multiple chargers and cables but nothing helped.
How I fixed it is:
1) Left the phone on in fastboot mode, until the battery died (unplugged obviously).
2) Left the phone unplugged for about 8h.
3) In the morning, keep pressed power button and plugged in the charger.
4) After few seconds it started up.
Hope this is helping you guys.
This just happened to me. Has the problem returned on you? Assuming I can get it to boot again, I'm wondering if I should do a factory reset to give myself a fresh start and clear out whatever software issue may be causing it, if it is a software issue.
Thanks fixed it
Thanks NathanTan...
It fixed my issue. I left it overnight with fastmode displayed. After it ran out of battery powered on and boom phone was back to normal. I never thought it will sort without replacing handset. Thank you
Hey guys. Please help. I am facing this issue in Pixel 5a now.
Only the end user can set the user-settable root of trust. It cannot be set at the factory or any other point before the device is delivered to the end user.
geometry dash is a game that is loved by many people.

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!

Categories

Resources