Can anybody tell me if this is a problem for me? I've unlocked the bootloader, rooted with 2.62 SU and installed CyanongenMod
Syystole said:
Can anybody tell me if this is a problem for me? I've unlocked the bootloader, rooted with 2.62 SU and installed CyanongenMod
Click to expand...
Click to collapse
No problem at all. Just ignore it.
https://support.google.com/nexus/answer/6185381?hl=en
Witek_M said:
No problem at all. Just ignore it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
You think it's possible to actually remove this message from bootup?
Syystole said:
You think it's possible to actually remove this message from bootup?
Click to expand...
Click to collapse
On my N5X I have replaced those images with boot logo. I am sure this will get worked out in no time for N6P as well.
http://forum.xda-developers.com/nex...-change-bootlogo-images-imgdata-tool-t3240052
Syystole said:
Can anybody tell me if this is a problem for me? I've unlocked the bootloader, rooted with 2.62 SU and installed CyanongenMod
Click to expand...
Click to collapse
Witek_M said:
No problem at all. Just ignore it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
This message actually is something to worry about, it isn't the usual "your device can't be checked for corruption" message.
Syystole said:
Can anybody tell me if this is a problem for me? I've unlocked the bootloader, rooted with 2.62 SU and installed CyanongenMod
Click to expand...
Click to collapse
Just ignore it , its because your not running stock Kernel, CM would have to patch it or try a different Kernel that's been patched .
I believe its due to unlock bootloader. I locked my 6p and dont get any message like that, unlocked and got this message everytime i reboot my 6p.
Sent from my Nexus 6P using Tapatalk
Hi there, i had this issue and fixed it.
I posted what needs to be done here, http://forum.xda-developers.com/showthread.php?t=3275025
Sent from my Nexus 6P using Tapatalk
Heisenberg said:
This message actually is something to worry about, it isn't the usual "your device can't be checked for corruption" message.
Click to expand...
Click to collapse
Yeah, this is a different message than what I get. I get "Please lock your bootloader" message, not this one.
Related
Does anyone know what's the cause of this? I built Omni yesterday and it was fine, but I tried to flash another one I built today and that's what it tells me followed by the phone getting stuck during the bootanimation when the logo turns fully green. And, the thing is that I checked the zip and there is a file_contexts.
rickoslyder said:
Does anyone know what's the cause of this? I built Omni yesterday and it was fine, but I tried to flash another one I built today and that's what it tells me followed by the phone getting stuck during the bootanimation when the logo turns fully green. And, the thing is that I checked the zip and there is a file_contexts.
Click to expand...
Click to collapse
The file_context warning has nothing to do with you not being able to build. See if you can get a logcat to see what is going on.
Sent from my Xperia T using Tapatalk
scanno said:
The file_context warning has nothing to do with you not being able to build. See if you can get a logcat to see what is going on.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
No no, you misunderstood. I can build fine, but I can't boot.
I saw the same warning, with no apparent ill effect, on these I just flashed:
omni-4.3.0-20131020-i9300-HOMEMADE
omni-4.3.0-20131022-m7ul-HOMEMADE
HTC One and GS3 seem to be running fine.
rickoslyder said:
No no, you misunderstood. I can build fine, but I can't boot.
Click to expand...
Click to collapse
Sorry that was a typo, I ment boot (auto correct is a pain sometimes).
But getting a logcat (if you get that far in the boot process) can help in diagnosing the problem.
Sent from my Nexus 10 using Tapatalk 4
scanno said:
Sorry that was a typo, I ment boot (auto correct is a pain sometimes).
But getting a logcat (if you get that far in the boot process) can help in diagnosing the problem.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Doesn't let me logcat. I'm gonna download Rebellos's Omni and see if that boots, probably should have done that first thing now that I think about it..
rickoslyder said:
Doesn't let me logcat. I'm gonna download Rebellos's Omni and see if that boots, probably should have done that first thing now that I think about it..
Click to expand...
Click to collapse
Hmm works with Rebellos's zip..
*sighs* Resynced and rebuilt today and it's booting first time. Don't know what changed but mods, you can lock/delete this now.
I got this trying to do adb push to a Nexus 4 and the ROM will not flash...
nvm missunderstood.
gleggie said:
I got this trying to do adb push to a Nexus 4 and the ROM will not flash...
Click to expand...
Click to collapse
Wiping data and system seems to be what made it work for me.
[NO file_context ] problem with OmniRom 4.4.2
my phone is N7000 .. and i downloaded omnirom 4.4.2 from the site and paste it into the sd ,, when i make a flash to this rom .. a message appear to me
WARNING : no file_context
plz help me :-/
I think its the issue of that particular nightly build. I too had the same experience. So I flashed with another nightly and it works fine. After this error I changed to stock ROM but the flash counter didn't reset to 0. I tried to flash 3 times and now the counter is showing as 3. Can anyone advise me to reset it
Sent from my GT-I9100 using XDA Premium 4 mobile app
I got the same warning in recovery what does it mean?
Ronii10 said:
I got the same warning in recovery what does it mean?
Click to expand...
Click to collapse
My guess would be vastly outdated recovery but who knows.
Okay how do i update?
help
i am using system extractor and repacking, but it saids needed file_contexts. i dont know is the one in the rom zip or i need to make a new one?
"There's an internal problem with your device. Contact your manufacturer for details
I got this message, I cannot view my files on my computer. I flashed the latest factory image and did a factory reset, flashed the vendor file, but no luck. What else could it be? Drivers?
an internal problem. have you tried reaching out for warranty support?
Already unlocked Bootloader.
640k said:
an internal problem. have you tried reaching out for warranty support?
Click to expand...
Click to collapse
I'm sure since I unlocked my bootloader it wouldn't do me any good, right?
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
09eric09 said:
I'm sure since I unlocked my bootloader it wouldn't do me any good, right?
Click to expand...
Click to collapse
unlocked bootloader does not void your warranty, this has been confirmed by google's csr
dipole said:
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
Click to expand...
Click to collapse
No.
dipole said:
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
Click to expand...
Click to collapse
your advice fixed the problem on my nexus 6p.. thank you
It fixed my problem on Nexus 6p after rooting to Cataclysm
Thanks!!
toenail78 said:
your advice fixed the problem on my nexus 6p.. thank you
Click to expand...
Click to collapse
09eric09 said:
No.
Click to expand...
Click to collapse
dipole said:
did you set a fingerprint before rooting? That is why I got that message. Just go here
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
Click to expand...
Click to collapse
yangqi said:
unlocked bootloader does not void your warranty, this has been confirmed by google's csr
Click to expand...
Click to collapse
superchan08 said:
Thanks!!
Click to expand...
Click to collapse
Hi Guys,
Anyone successfully got rid of this? i've been running Catacalysm with elementalx with no issues. But suddenly i wanted to try layers and one of the layer i tried made me to loop at colorful dots screen that turn into android. But it never turned to android and didn't boot.
i tried to restore nandroid, flash catacalysm again etc., but nothing worked. Finally i had to flash all the factory image (from bootloader to vendor) again. then restored the latest data nandroid. i had my finger print set and following http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 i removed locksettings.db file to successfully get in the system.
however, on every restart i get this error message that my phone has an internal problem and manufacturer to be contacted. I am afraid to flash the nexus 9 fix, as someone reported that its spoiling his touch screen.
Try flashing the vendor img only in fastboot and see if that removes the error message.
steviemch said:
Try flashing the vendor img only in fastboot and see if that removes the error message.
Click to expand...
Click to collapse
Thanks! Easy fix!
Flashing the vendor img didn't work for me.
Is there any other way to do it or do I have to wipe it all and start over?
So, I see that it's based on the build number MMB29X but that's a Nexus 6 build. I have a Nexus 5x. If I flash that vendor image, will it work or mess things up? I've never had to do that before so I'm sort of lost... I'm positive that I downloaded the right build from the CM site. Thanks in advance for the help.
erichjelm said:
Flashing the vendor img didn't work for me.
Is there any other way to do it or do I have to wipe it all and start over?
So, I see that it's based on the build number MMB29X but that's a Nexus 6 build. I have a Nexus 5x. If I flash that vendor image, will it work or mess things up? I've never had to do that before so I'm sort of lost... I'm positive that I downloaded the right build from the CM site. Thanks in advance for the help.
Click to expand...
Click to collapse
Do not flash that nexus 6 image!! Do not flash or install any zip or image that is not expressly for your phone!!
This is the forum for the Nexus 6p. You will have better luck finding the answer to you question somewhere here (Nexus 5x forum). If you have installed an image or zip of any type from anywhere other than that forum (or official google downloads) you are probably going to have a bad day. Good luck.
I didn't even notice.
I'm sorry.
Just opened a Google search link.
Sorry!
erichjelm said:
I didn't even notice.
I'm sorry.
Just opened a Google search link.
Sorry!
Click to expand...
Click to collapse
No worries, mate! I have found solutions to problems in forums that were not for my phone. Just pay attention to where you post you questions. The fact that you are using google first puts you years ahead of some people I've seen posting. Definitely no reason to apologize twice. :highfive:
Found the fix in the form of a ZIP in Nexus 9 forum.
Ha.
Thanks, again!
Can anybody verify that this works for the 6p before I flash a zip and Jack my phone up any further? Lol
How do I find the right vendor img for my nexus 6p?
mrjoeyloke said:
How do I find the right vendor img for my nexus 6p?
Click to expand...
Click to collapse
With a file browser, head to /System/build.prop and look for this line "ro.build.description" and your system software should be listed after the Android version. I believe this is also listed in Settings/About Phone. You can view which Vendor you have installed in /Vendor/build.prop. Make sure both match up each month when you update.
Sent from my Nexus 5X using Tapatalk
I have a major problem, I need to know if it will be possible to flash a custom rom on a nexus 6p. It seems that it will be hard because of that new bootloader.
smilehead said:
I have a major problem, I need to know if it will be possible to flash a custom rom on a nexus 6p. It seems that it will be hard because of that new bootloader.
Click to expand...
Click to collapse
What do you mean? Any bootloader version on this device can be unlocked.
Heisenberg said:
What do you mean? Any bootloader version on this device can be unlocked.
Click to expand...
Click to collapse
Sorry, I'm new to this stuff. I thought they can change the bootloader when you upgrade. Thanks for the help though
smilehead said:
Sorry, I'm new to this stuff. I thought they can change the bootloader when you upgrade. Thanks for the help though
Click to expand...
Click to collapse
The bootloader does get updated. But you can unlock any bootloader, and updating it doesn't lock it again. Take a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Oh, because i was afraid of the phone won't boot because of the android n won't boot if the phone has a unlocked bootloader.
smilehead said:
Oh, because i was afraid of the phone won't boot because of the android n won't boot if the phone has a unlocked bootloader.
Click to expand...
Click to collapse
Nope, nothing like that to worry about. The locked/unlocked status won't stop it from booting.
Thanks. I can now upgrade in peace
I have a Verizon LG V20 and I need help. Every time I boot my phone, I get this message "Your device is corrupt. It can't be trusted. It may not work properly". How do I get rid of the message for good? I'm not rooted, my LG V20 is stock like it was out the box. Also, I factory reset my LG V20 numerous and nothing. Any help and suggestions would GREATLY be appreciated! Thanks in advanced..
Storm26 said:
I have a Verizon LG V20 and I need help. Every time I boot my phone, I get this message "Your device is corrupt. It can't be trusted. It may not work properly". How do I get rid of the message for good? I'm not rooted, my LG V20 is stock like it was out the box. Also, I factory reset my LG V20 numerous and nothing. Any help and suggestions would GREATLY be appreciated! Thanks in advanced..
Click to expand...
Click to collapse
The message can be caused for either you unlocking the bootloader or in very rare situations by an app sticking its nose where it does not need to. If your phone still boots after that message then you are just fine. On the other hand, if it doesnt boot properly, or if you want to trick LG or your carrier into believing you havent root your phone .... Then you are not fine. You can use LG up clean installation the KDZ for your variant and it will remove the message and relocked the OEM (preferably using the refurbish function and not the upgrade. I see that the Verizon's variant does have unmodified KDZ's so.... I think you can do that too.
https://lg-firmwares.com/lg-vs995-firmwares/
You can use LG UP and install one of the KDZ. ( and do not unlock the bootloader unless you want that message to show).
Now, if for X or Y reasons your message is showing for any other reason im not aware off... Then i hope someone else can help you with that
I haven't gotten any updates since January..
Storm26 said:
I haven't gotten any updates since January..
Click to expand...
Click to collapse
The main question is... Have you tried to root the phone? or have you unlocked the bootloader?
jinkerz9430 said:
The main question is... Have you tried to root the phone? or have you unlocked the bootloader?
Click to expand...
Click to collapse
I have done neither.
Storm26 said:
I have done neither.
Click to expand...
Click to collapse
What color is the triangle? orange or red?
me2151 said:
What color is the triangle? orange or red?
Click to expand...
Click to collapse
Red
Storm26 said:
Red
Click to expand...
Click to collapse
Hmmm... the only way to get red is if you tried dirtysanta... or got malware but if you got malware it wouldnt(or shouldnt...) boot. Best thing you can do is use the verizon kdz and reinstall the whole phone. that will get rid of the triangle.
me2151 said:
Hmmm... the only way to get red is if you tried dirtysanta... or got malware but if you got malware it wouldnt(or shouldnt...) boot. Best thing you can do is use the verizon kdz and reinstall the whole phone. that will get rid of the triangle.
Click to expand...
Click to collapse
How would I do that?
https://forum.xda-developers.com/v20/how-to/ultimate-guide-to-unbrick-lg-v20only-t3563925
me2151 said:
https://forum.xda-developers.com/v20/how-to/ultimate-guide-to-unbrick-lg-v20only-t3563925
Click to expand...
Click to collapse
My LG V20 isn't bricked
Storm26 said:
My LG V20 isn't bricked
Click to expand...
Click to collapse
You wanted to know how to use a kdz. thats the guide. Enjoy.
me2151 said:
You wanted to know how to use a kdz. thats the guide. Enjoy.
Click to expand...
Click to collapse
I'm kinda scared to do it though.
Storm26 said:
I'm kinda scared to do it though.
Click to expand...
Click to collapse
Thats the only way to restore it. You most likely did do the DC guide... Theres not really any other way you could get that screen. There is no removing it even if you factory reset... Its either the KDZ restore or you live with the screen lol
Biff627 said:
Thats the only way to restore it. You most likely did do the DC guide... Theres not really any other way you could get that screen. There is no removing it even if you factory reset... Its either the KDZ restore or you live with the screen lol
Click to expand...
Click to collapse
What's DC guide?
Storm26 said:
What's DC guide?
Click to expand...
Click to collapse
dirtycow
jerrycoffman45 said:
dirtycow
Click to expand...
Click to collapse
Oh okay, do you need a computer to do the KDZ restore?
Storm26 said:
Oh okay, do you need a computer to do the KDZ restore?
Click to expand...
Click to collapse
yes
jerrycoffman45 said:
yes
Click to expand...
Click to collapse
Oh okay. .
Storm26 said:
Oh okay. .
Click to expand...
Click to collapse
Is it easy to use KDZ restore? How long would it take?
I unlocked the bootloader and now there is a message telling me whenever I boot that my device has been unlocked and cannot be trusted. Does anyone know how to fix this? Thanks
donster42019 said:
I unlocked the bootloader and now there is a message telling me whenever I boot that my device has been unlocked and cannot be trusted. Does anyone know how to fix this? Thanks
Click to expand...
Click to collapse
lock bootloader!
nicolap8 said:
lock bootloader!
Click to expand...
Click to collapse
Anything apart from that, and that is quite obvious!
donster42019 said:
Anything apart from that, and that is quite obvious!
Click to expand...
Click to collapse
No.Anything.
nicolap8 said:
No.Anything.
Click to expand...
Click to collapse
Okay, I just want to keep root, but I can't do that if I lock the bootloader. So please can you give me a solution, so I do not have to deal with an ugly message whenever I boot!