Related
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
GoremanX said:
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
Click to expand...
Click to collapse
Did you delete system (AT&T) apps?
coolmingli said:
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
Click to expand...
Click to collapse
Yep, I did all of that. Exact procedure:
- Reset flash counter using triangle away
- full unroot using SuperSU
- reboot immediately into Odin mode (system status says "Official")
- reboot immediately into recovery, do a factory reset
- reboot immediately into Odin mode (system status still says "Official")
- reboot immediately into recovery, do ANOTHER factory reset (because I'm anal that way)
- reboot immediately into Odin mode, (system status STILL says "Official")
- reboot normally, go through normal first-time setup, go into settings, check Device status... it says "Custom"
- reboot into Odin mode, system status now says "Custom"
- reboot normally, stupid open padlock is there again with the word "Custom"
- countless reboots later, it still says "Custom"
serpent2005 said:
Did you delete system (AT&T) apps?
Click to expand...
Click to collapse
Nope, none. They're all still there. Like I said, I'm still running the bone stock image, never flashed a ROM, and I never edited the image. I only use root for things like GMD S-pen control, Titanium Backup, and FS Trim.
What's really annoying is that damn open padlock is never there while the system really IS modified, it only shows up when I unroot and everything is back to stock. I call it irony.
Would region lock be affecting this? I disabled the region lock many moons ago using RegionLock Away. Does that survive after a factory reset, and would it cause my device status to show up as Custom?
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
GoremanX said:
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
Click to expand...
Click to collapse
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
the2rrell said:
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
Click to expand...
Click to collapse
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
GoremanX said:
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
Click to expand...
Click to collapse
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
the2rrell said:
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
Click to expand...
Click to collapse
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
GoremanX said:
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
Click to expand...
Click to collapse
you have all the drivers and everything loaded up?
thats odd.
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
GoremanX said:
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
Click to expand...
Click to collapse
Yes but it should work, another member just did the same thing you are trying to do. with success. it has to be drivers or maybe running odin as a admin.
Oh and you may want to move the Odin file to a folder on your desktop or just put them on your desktop and try that. im betting its something simple that we are just over looking.
Finally got it restored to factory. Just about everything that can go wrong did go wrong. My USB cable failed. Then my SD card failed and was spitting out garbage. And one of my downloaded files was corrupted. At one point, I got the status back to "Official", but the phone was so screwed up it was nearly unusable, spitting out error messages every 30 seconds. When this happened, I took it to a local AT&T store hoping they would just flash a new image on there (it did say "Official" in all the right places after all). But all they wanted to do was replace it with a refurb unit. Screw that! So I went home and tried AGAIN, re-downloading everything and using an all new USB wire and SD card, and this time it worked like a charm.
Now I'm attempting to install the OTA update, hopefully all goes according to plan.
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
GoremanX said:
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
Click to expand...
Click to collapse
That is stock. It's not prepared for root. You can choose to root or not. I have not updated so I don't know. But if you made it to nb4 why do think it would do that if the mj5 was fixed for root right
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Nah, everyone else in the same situation as me has the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2686652&page=21
We're talking dozens and dozens of attempts by sozens and dozens of people here. Downgrading to the MJ5 image in that restore thread does not actually bring the phone back to stock. The NB4 upgrade apparently just doesn't have the same level of verifying in it as the KitKat update. The author of that thread specifically mentions that the MJ5 image he's listing has been modified to allow rooting using his method, but the rooting part of it is optional. Either way, the image itself has been modified. That's why it has the word "fix" in the filename.
Others have stated that going to an AT&T retail location and having them flash a real MJ5 image DID work, and allowed the KitKat update to happen without issues.
So I was following this guide to rooting the Nexus 6: http://forum.xda-developers.com/nex...exus-6-one-beginners-guide-t2948481?nocache=1
I unlocked the device, and verified when I go into fastboot.
However when I run the Chainfire.cf-root it fails to unlock because it's already unlocked, then successfully loads the boot images and such, then says when the phone restart I should see a big red android. I do not ever see this though and I'm not sure where to go at this point.
Any suggestions?
gabessdsp said:
So I was following this guide to rooting the Nexus 6: http://forum.xda-developers.com/nex...exus-6-one-beginners-guide-t2948481?nocache=1
I unlocked the device, and verified when I go into fastboot.
However when I run the Chainfire.cf-root it fails to unlock because it's already unlocked, then successfully loads the boot images and such, then says when the phone restart I should see a big red android. I do not ever see this though and I'm not sure where to go at this point.
Any suggestions?
Click to expand...
Click to collapse
Install a root checker app
oh cool, it worked thanks. I just assumed somethign was wrong and didn't bother to look into it
I upgraded from 5.1.1 to 6.0 by flashing the factory image without flashing userdata. Everything worked perfectly, but, as many people have noted, I get a "Your device is corrupt" message briefly on startup, before having the opportunity to enter my encryption code. Again, the phone functions just fine despite this.
I'm wondering what it is about my phone that causes this message to display. My bootloader is unlocked, though I don't think this alone should be a problem. I am completely stock, unrooted (though I was rooted on previous versions). As such, I don't think it can be a problem with the system or boot partitions, since, again, I have flashed and re-flashed these directly from the factory image. I don't see how it can be problem with userdata, since this isn't even decrypted when I get the "corrupt" message (i.e., I haven't entered the encryption code yet). Perhaps it's some problem with how userdata is encrypted?
Any logs that might give insight into where the fault is occurring?
Verity is the cause. That post should answer your question.
cupfulloflol said:
Verity is the cause. That post should answer your question.
Click to expand...
Click to collapse
Thanks for the link. I'm still not sure this explains my situation. I get a red "corrupt" warning telling me my device is actually corrupt, which should mean that system files have been modified. However, my system is unmodified; I know this because I have flashed it directly (multiple times).
Although it is extremely unlikely and might be a unique situation, Verity might have actually worked for what it was designed for, for once, and your system might actually be corrupted by either persistent malware or bad memory.
I would warranty return the phone, if possible.
Sent from my VS985 4G using Tapatalk
Wipe data factory reset from stock recovery.
trent999 said:
Although it is extremely unlikely and might be a unique situation, Verity might have actually worked for what it was designed for, for once, and your system might actually be corrupted by either persistent malware or bad memory.
I would warranty return the phone, if possible.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
droidstyle said:
Wipe data factory reset from stock recovery.
Click to expand...
Click to collapse
Thanks. I'm not looking really looking for a radical solution (wiping phone, returning it); I'm looking for an explanation (which might guide me to a less radical solution). Again, I wonder whether Verity makes a log somewhere. As I mentioned, my phone is working perfectly.
Hard to imagine it's persistent malware, since I've flashed every partition other than userdata (which is still encrypted when I get the "corrupt" message). Moreover, I'm by no means the first person to report this behavior.
NYZack said:
Thanks. I'm not looking really looking for a radical solution (wiping phone, returning it); I'm looking for an explanation (which might guide me to a less radical solution). Again, I wonder whether Verity makes a log somewhere. As I mentioned, my phone is working perfectly.
Hard to imagine it's persistent malware, since I've flashed every partition other than userdata (which is still encrypted when I get the "corrupt" message). Moreover, I'm by no means the first person to report this behavior.
Click to expand...
Click to collapse
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
simms22 said:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
Click to expand...
Click to collapse
I didn't notice mine until I installed a custom recovery. Hrm..maybe I just didn't pay attention lol
Tower1972 said:
I didn't notice mine until I installed a custom recovery. Hrm..maybe I just didn't pay attention lol
Click to expand...
Click to collapse
i didnt get it either. but i flashed a custom kernel as well, which gets rid of that message.
simms22 said:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
Click to expand...
Click to collapse
I'm unlocked, stock and get no such message(s). Expecting it when I install a recovery though
Larzzzz82 said:
I'm unlocked, stock and get no such message(s). Expecting it when I install a recovery though
Click to expand...
Click to collapse
So I can't figure out what the true story is. Some people say that it happens to everybody with an unlocked bootloader, but, according to what you say, this isn't the case. I am stock in every way - recovery, bootloader, boot image, system image - and yet I get this warning. It's not a big deal, but it eats at me and makes me wonder whether there really is something corrupt about some aspect of my system.
NYZack said:
So I can't figure out what the true story is. Some people say that it happens to everybody with an unlocked bootloader, but, according to what you say, this isn't the case. I am stock in every way - recovery, bootloader, boot image, system image - and yet I get this warning. It's not a big deal, but it eats at me and makes me wonder whether there really is something corrupt about some aspect of my system.
Click to expand...
Click to collapse
It has to be changes to recovery. I'm running stock 6.0 with an unlocked bootloader and root and I have no such message on startup. Rooted and unlocked through Wugfresh NexusTool and temporary modified recovery option (non-persistent).
dasDestruktion said:
It has to be changes to recovery. I'm running stock 6.0 with an unlocked bootloader and root and I have no such message on startup. Rooted and unlocked through Wugfresh NexusTool and temporary modified recovery option (non-persistent).
Click to expand...
Click to collapse
No, if you're rooted, it's a different story. The modified boot image installed when you root disables verity checking.
I got the message after rooting my phone with CFRoot. Have done that before, always worked. But now the phone stops working after that boot message, I have reinstalled the stock image.
simms22 said:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
Click to expand...
Click to collapse
I can confirm that this is not true. I ultimately factory-reset my phone from Recovery (it was acting strangely in other ways - Contacts crashing, for instance). My bootloader remains unlocked, but I no longer get the "Corrupt" message on startup.
I'm unlocked on marshmallow also and have never had that message
Take a look at here, it was my experience and solution.
https://productforums.google.com/forum/m/#!topic/nexus/sTu8Bdc1GLA;context-place=topicsearchin/nexus/category$3Adevice-security
Sent from my Nexus 6 using XDA Free mobile app
Semseddin said:
Take a look at here, it was my experience and solution.
https://productforums.google.com/forum/m/#!topic/nexus/sTu8Bdc1GLA;context-place=topicsearchin/nexus/category$3Adevice-security
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
A simple factory reset in Recovery was all I needed. But I was hoping for a solution that didn't involve wiping my phone, ... and some insight into why so many of us are getting this message with stock systems.
NYZack said:
A simple factory reset in Recovery was all I needed. But I was hoping for a solution that didn't involve wiping my phone, ... and some insight into why so many of us are getting this message with stock systems.
Click to expand...
Click to collapse
Glad you could fix yours with a simple factory reset. Mine was in a much worse situation where i immediately got the corrupted message once i entered gmail account into phone. Google reps couldnt find the answer to the issue but advised me to downgrade to previous os and take OTA to marshmallow, that definitly fixed the issue for me.
Sent from my Nexus 6 using XDA Free mobile app
Device verification on Android and Nexus can be a bit of an interesting subject.
In theory, dm-verity on a Nexus will ONLY validate the system image, and nothing else.
This is the key description that Google made regarding verified boot;
http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
The key takeaways from that are;
1) an enforcing secure boot chain will involve validating each of the bootloader/boot partitions from the previous level, up to and including the boot.img.
2) The boot image contains the linux kernel and the verity_key file.
3) The verity_key file is the public key used to validate the contents of the metadata partition, which stores the hash tree for the system partition and is used to validate the contents of the system partition *on the fly*.
4) When dm-verity detects a change, it causes an I/O error.
5) On Nexus devices, the validation of the boot partition can be disabled.
The part that is interesting, is figure 2.
The part where it verifies metadata signature files --> no, causes it to reboot in logging mode and gives you the big ugly warning page.
Note that an unlocked Nexus 6 does NOT implement the yellow or orange warning states in its default configuration - see the description of "Class A". I'm not entirely sure if they can be enabled or not, but I've heard chatter of something to the effect of fastboot oem verify, which might enable validation of the boot partition.
So what happens during a dm-verity?
Well, when init tries to mount the system partition using dm-verity, it fails signature check. When it fails signature check, it sets a boot flag that it failed signature check, and *reboots*. The bootloader picks up this boot flag, and loads the error. If dm-verity PASSES signature check, it just continued boot as normal -- no rebooting.
So the approach for getting rid of that error message is actually this; if you tell init not to apply dm-verity, then the signature check is never even applied, so it continues boot as normal.
What isn't clear, is how it could be even remotely possible for a corrupt boot or cache partition to trigger a bootloader error. The only thing I can imagine, is maybe there is some additional check that isn't documented, or a bug in the bootloader that gets triggered when some boot flag is set wrong.
Hey everyone!
First posting here, long time reader. So, I just f***** up big time. I tried to install the YT Vanced modules for my X4, realized I had to get rid of the stock YT app first, installed Terminal Debloater and at that point my device stuck during boot. To make things infinitely worse, I then proceeded to re-lock the bootloader cycling through the last commands issued. That was dumb, yeah.
Now I get the "device corrupt" message when I try to boot normally and fastboot won't let me flash again saying I need to enable USB debugging, which I can't because the system won't let me boot.
I have a severe feeling I'm screwed with nobody but myself to blame, but I'm also aware of the godlike knowledge in these boards so... can anyone point me in a direction here? Damn I like that phone and have zero funds for a new one right now :/
I can still get into the Power+Down menu, the stock recovery gets me nowhere though. Oh, and it's the Euro Model, Motorola Moto X4 XT1900-05, running the Oreo OTA update.
Cheers people,
grslbr
You need to flash the original official firmware that came loaded on your device but good luck trying to find a copy of that. With the bootloader locked, you're screwed.
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
FI stock roms seem to be located at https://firmware.center/firmware/Motorola/Moto X4/Stock/ Have not tried them myself and not sure you can flash with a locked bootloader.
You should be able to flash a stock ROM pretty easily. From what I've seen, you should be able to install any retail stock rom without unlocking the bootloader.
grslbr said:
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
Click to expand...
Click to collapse
Hold Vol+ and Power buttons. Phone will try to reboot several times and then boot normaly. Go to developer options and tick allow factory unlock and USB debugging. Then you just unlock bootloader as usual.
This procedure helped fix the same issue with my xt1900-7 reteu.
Hello everyone,
Every time my moto x4 is restarted, a message appears on the boot screen:
"verity mode is set to logging"
It is something quick, written in yellow and soon the device finishes the initialization.
I wonder if this affects anything on the device?
I make the following observations:
My moto x4 was in the version PAYTON_OPW29.69-26_SUBSIDY-DEFAULT_REGULATORY-DEFAULT_CFC.XML. As I was having problems with Wi-Fi on the device, I decided to unlock the bootloader and flash another version of the android. Finally I opted for PAYTON_FI_OPWS28.46-21-12_SUBSIDY-DEFAULT_REGULATORY-DEFAULT_CFC.XML, this after having tested other versions, all with success. But since I unlocked the bootloader and did the first downgrade this message appears at the boot of the device.
My moto x4 is an XT1900-6.
Another thing done through a previous search was to run the command "getprop ro.boot.veritymode" in the terminal, directly on the device, which returned: "enforcing".
Anyway, I'm not sure if everything is OK with the device or if I lost any important function. If it is a normal error and if it is not, I would like to know the solution to this problem.
This is "normal". I think you can ignore it. If you were worried about security and privacy, you would want it to be enforcing so that the phone wouldn't boot if it was modified. Most users do not want this since it would break a lot of things.
Edit: are you using any third party zips to hide root or pass safety net? They might mask the verity mode, maybe? I don't use them so I couldn't tell you the expected behavior.
gee one said:
This is "normal". I think you can ignore it. If you were worried about security and privacy, you would want it to be enforcing so that the phone wouldn't boot if it was modified. Most users do not want this since it would break a lot of things.
Edit: are you using any third party zips to hide root or pass safety net? They might mask the verity mode, maybe? I don't use them so I couldn't tell you the expected behavior.
Click to expand...
Click to collapse
I did another clean install, using the same firmware as android 8.1 (one), now I'm not using root, as I see no need. I hope there is no problem with this message on the boot screen. I hope I still receive updates via OTA.
To remove this message needs to flash the bootloader from phone variant. This file fix for XT1900-6.
filipepferraz said:
To remove this message needs to flash the bootloader from phone variant. This file fix for XT1900-6.
Click to expand...
Click to collapse
nice bro, it worked for me. :good: :fingers-crossed: