yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] tlip:
Your device is corrupt. It can’t be

trusted and may not work properly.

Visit this link on another device:

go.co/ABH

Problem:

This is the ultimate warning, and you likely don’t want to see this message show up on your screen. Shall this appear, it would mean your device is not safe to use, not trusted and/r corrupted. The OS could still work, but there’s high chances you will encounter performance and security issues.

Consequence:

Before your device begins to start it will be shown:

Android system

There’s an internal problem with your device. Contact your manufacturer for details nexus 6p

Also:

The camera may be no longer properly work

Fixxed:

fastboot flash bootloader bootloader-angler-angler-xx.xxx.img

fastboot reboot-bootloader

fastboot flash radio radio-angler-angler-xx.xx.img

fastboot reboot-bootloader

fastboot flash recovery recovery.img

fastboot flash boot boot.img

mfastboot flash system system.img

reboot bootloader

fastboot flash cache cache.img

fastboot flash userdata userdata.img

fastboot reboot-bootloader

fastboot reboot-bootloader

fastboot flash vendor vendor.img

Important:

fastboot flashing lock_critical

Enjoy!
[Nexus 6P General] Heisenberg:
[MENTION=5939249]tlip[/MENTION]

A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:

fastboot format userdata

Also, bootloader reboots are only required after flashing the bootloader and the radio, so the sequence should be like this:

fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot

And one more thing, you need to take more care when typing these instructions, you made a few errors, I'll highlight them:

fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
[Color=red]m[/color]fastboot flash system system.img [Color=blue](extra m at beginning of command)[/color]
[Color=red]reboot bootloader[/color] [Color=blue](missing "fastboot" prefix, and hyphen between reboot and bootloader (fastboot reboot-bootloader))[/color]
fastboot flash cache cache.img
[Color=red]fastboot flash userdata userdata.img[/color] [color=blue](incorrect command as outlined above)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](unnecessary)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](another one?)[/color]
fastboot flash vendor vendor.img
[Nexus 6P General] sandfreak:
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
[Nexus 6P General] Dissmeister:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.

Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.

EDIT: This info only applies for "Bootloader MAY BE Corrupt" and not "IS Corrupt". Different situation from the OP
[Nexus 6P General] gd6noob:
Thanked [MENTION=4153349]Heisenberg[/MENTION]

Please OP, you give instructions that you expect people to follow and if they type in the wrong info could be fatal...
[Nexus 6P General] nadiros:
Seriously, this thread needs closed asap. All the above info( besides Heisenberg) is careless in itself, let alone posting it for others. Stop....just stop. Smh
[Nexus 6P General] tannerln7@gmail.com:
I have for sure made this mistake before... One lesson learned the hard way :rolleyes:
[Nexus 6P General] CNLiberal:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
[Nexus 6P General] Heisenberg:
That's exactly right, locking the bootloader means you can't flash anything to the device.
[Nexus 6P General] Dissmeister:
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.

Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
[Nexus 6P General] dontbeweakvato:
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
[Nexus 6P General] Dissmeister:
That is one hell of a silly mistake. You're right, I apologize for not seeing that earlier. Will fix my previous reply so others dont get the wrong info from it. Thanks for that :good:
[Nexus 6P General] CNLiberal:
The way I understood it, after I re-lock then need to unlock again, the phone will force a wipe. The old app Unlock Bootloder would lock and unlock in Android. You wouldn't have to reboot. I guess the developer believes that the new 6P can't perform this same function due to the nature of new locking/unlocking.
[Nexus 6P General] Rovaine:
Hi Heisenberg,

as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?

Does this hold true also for already having this problem, though?

Cheers, Rovaine
[Nexus 6P General] Heisenberg:
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:

http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
[Nexus 6P General] Rovaine:
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.

You've got any advice for starting all over -propperly- for getting rid of this issue?
[Nexus 6P General] Gorgtech:
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.

I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.

On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.

You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
[Nexus 6P General] Rovaine:
Just for getting it straight...

Initial situation:

Rooted device, latest Cyanoge installed, showing the described issue

How to solve:

Get angler-xxxxxx-factory-xxxxxxxx, unzip ...

"fastboot flash vendor C:\angler\images\vendor.img"

Gratulation issue solved?

Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
[Nexus 6P General] Gorgtech:
Exactly, you need the latest Factory Image for the Nexus 6P. Extract all content and only flash the vendor.img through fastboot.
[Nexus 6P General] Heisenberg:
Flash the factory images, instructions are in my guide.
[Nexus 6P General] azsl1326:
I get the same message that the OP references and even saw it in a video tutorial on rooting. I assumed it was due to my BL being unlocked, but the last few posts make it seem like I need to flash vendor.img to fix the issue? What's the consensus on this?
[Nexus 6P General] azsl1326:
This link should help clear up some of the confusion. After reading it, the message I am getting regarding the BL is different than the OP's and it seems that it is normal for it to appear once the BL is unlocked.
[Nexus 6P General] mhughes1966:
OK I have never tried nor has anyone else tried to change anything with my Nexus 6p. I have kept it stock and plan to keep it that way.

I shut it down to install a screen protector and when I turned it back on I got that "your device is corrupt. It can't be trusted and may not work properly" notice. I am now very concerned. I again have not done any rooting, unlocking ... nothing before and no one has access to my device.

Can the message have any other meaning ?

Thank you
[Nexus 6P General] bjoostema:
I have searched for hours as this happens to me every time I flash twrp and I can't find any solid answers as to what specifically triggers this. You are not the first person I have seen on full stock who has experienced this. The only way I found resolution and piece of mind was to flash factory images, which will obviously require you to unlock your boot loader. I'm annoyed that no matter abd or toolkit, I get the "device is corrupt" message when flashing twrp. Sorry you're dealing with it bud, I'll let you know if I ever find out what specifically is triggering the message. I can't phathom why you're experiencing the issue. At least I know mine is from flashing a recovery.
[Nexus 6P General] mhughes1966:
OK. Called Google support late last night. They just had me go in and clear out my cache and it fixed the problem. Again I just had the message upon boot up but the phone wasn't hanging in any way and worked fine throughout.
[Nexus Player Q&A, Help & Troubleshooting] aamir123:
I am having trouble playing large video files either mkv or mp4. I recently tried watching star wars from my external hard drive and it wouldn't play past a certain point. I had to then use my computer to finish the movie. It also happened with a mission impossible copy. The mission impossible movie would not play past 30-45 mins whereas star wars played to 130-1:45.

The star wars was 3.5 gb and mission impossible was around 8gb. Both play fine on my laptop. What is going on?
[Galaxy S6 Edge General] MihirSheth:
Convert your S6 Edge to S6 Edge Plus [Nobel Rom]

We knew that once Galaxy Note 5 and S6 Edge Plus were released, we’d soon have Note 5 or S6 Edge Plus ROMs for Galaxy S6 and S6 Edge.

Well, it’s already here for you! *If you install the latest Noble ROM, you will get all of the features of Note 5 and S6 Edge Plus on your Galaxy S6 or S6 Edge.

This ROM is based on the Korean S6 Edge Plus model, giving you the Note 5/S6 Edge Plus launcher, camera (with YouTube LiveStream mode), and the latest edge/app shortcuts for the edge screen which also works flawless on edge-less Galaxy S6.

Also you can install this on my Galaxy S6 or S6 Edge models including SM-G920F, SM-G920I, SM-G920S,*SM-G920L,*SM-G920K, T-Mobile*SM-G920T, Canadian*SM-G920W8,*SM-G925F, SM-G925I, SM-G925S,*SM-G925L,*SM-G925K, T-Mobile*SM-G925T, and Canadian*SM-G925W8.

Performance and battery life is actually nearly identical to stock Android 5.1.1 since it uses a stock-based kernel. *Overall, this is an excellent way to upgrade your Galaxy S6 or S6 Edge into S6 Edge Plus without getting a new phone so definitely check it out this week(end) and do let me know what you think!

For Download , Features , Installation Instructions

Visit :-

http://xdaforums.com/galaxy-s6/development/rom-noble-rom-t3183902
[Galaxy S6 Edge General] pickles523:
What about g925p?
[Galaxy S6 Edge General] MihirSheth:
As its not mentioned above i have to deep research about your model

If i finish with it will mention above

Thanks
[Galaxy S6 Edge General] :
Thread closed.

There is no point to this other than to direct users to the other ROM thread.

Regards,

The_Merovingian

Forum Moderator
[P3300, MDA Compact III ROM Development] NikMel:
This is a fixed cab file.

voipphonecanvas.dll replaced and it works like a charm. This file comes from TOM_Artemis_Black_Blue_v3.7 rom. TNX Tom!

Tap on today screen and it toggles available/selected

Just install it and use SIP Config Tool to setup your SIP.

BTW: I have a cleaned P800w_SEA_ENG_WM6_Upgrade_20070713 from extrom and if some one wants it let me know.

Download this fixed cab file from http://rapidshare.com/files/52777992/WM6VoIP.FIXED.CAB

Have fun! :)
[P3300, MDA Compact III ROM Development] zaarbelink:
Thanx!

Could you please tell us what you cleaned out of the rom?
[P3300, MDA Compact III ROM Development] NikMel:
Only extrom removed.
[Xiaomi Mi 4i] jonathanfilbert:
Hey guys

so after ive rooted my MI4i, i installed a custom ROM called Infinitive OS, which is quite good then i stupidly flashed Sensei Kernel to My MI4i, and now, my phone is bricked. I tried to turn it on, after the Mi logo, it shuts off. I am still able to get to my TWRP Recovery, tried to delete cache/dalvik/factory reset, but no use. Still can't boot to system. PLEASE HELP GUYS

Thanks..

:cowboy:
[Xiaomi Mi 4i] haikalizz:
Tried flashing back the rom? and did you get to boot into the rom before flashing the kernel?
[Xiaomi Mi 4i] jonathanfilbert:
Yes, b4 I flashed the kernel everything works fine.
[Xiaomi Mi 4i] gurukos:
If i understand well, if you can get to twrp there is no reason to worry...

You just download an official / developer rom or any custom rom, reflash and you are done.
[Xiaomi Mi 4i] jonathanfilbert:
Yeah I know, thing is, mi4i doesn't have an external memory slot..
[Xiaomi Mi 4i] dabhic:
go to recovery and connect your phone in mtp mode from recovery , take backup from internal memory and flash official stable rom
[Xiaomi Mi 4i] Hackerpunk1:
You may flash the device recovery/kernel/firmware via FastBoot

Flash TWRP Recovery via Fastboot, then adb sideload a ROM on the Device. Or Download Official Fastboot firmware for the device and flash it.

Don't forget to say thanks :)
[Xiaomi Mi 4i] kadalmeinside:
flash the device with fastboot rom via FastBoot using mi flash
[Xiaomi Mi 4i] siregarbintan:
I have the same problem. Just Go into TWRP and wipe Dalvik/Cache/Data/System, after that just flash ROM again and everything works fine
[Xiaomi Mi 4i] StratOS_HTC:
The problem is with firmware and kernel. The firmware isn't compatible with kernel. If u flash the whole rom with firmware it will be fine, if U know witch FW have u used flash it flash it back or flash back original kernel.

check http://xdaforums.com/mi-4i/development/miui-firmware-flash-t3367968

Regards
[Xiaomi Mi 4i] Probal Basak:
Whatever You Do, first take a backup of your EFS Partition with TWRP or MI Toolkit. My device crashed and corrupted all partitions suddenly and my IMEI is lost now and I didn't have any backup of EFS to restore my IMEI.

And for restoring your device back to normal you will have to follow this..

1. Take backup of EFS and store it somewhere safe in you pc.

2. Download and extract the Fastboot ROM for Mi4i from here : http://update.miui.com/updates/v1/fullromdownload.php?d=ferrari_global&b=X&r=global&n=

3. As you have already rooted, I suppose that you already have adb drivers installed. If not then install

4. Open Recovery and press and hole POWER and VOLUME DOWN button after recovery boots up completely and do not release the keys until fastboot opens.

5. open Terminal(Linux)/CMD(Windows) and navigate into the directory you just downloaded and extracted.

5. Run "flash_all.bat"(Windows)/"flash_all.sh"(Linux).

6. Give it some time and you will get a brand new MIUI 7. After flashing miui 7 you can install any rom you wish.

Let me know if your device gets fixed or if you need any help..

Thanks.
[Xiaomi Mi 4i] navinkrvr:
not able boot to twrp recovery and even not in system

not able start twrp in my mi4i as system get crashed and now my phone is not booting up just suck in mi logo. plz help not able to start my device and not able flash my device. I think I lose my imei no. because i was trying to change my imei. I have a backup of miui8 by twrp will it help me to start my device. plz help !!!
[Xiaomi Mi 4i] Sajilpopz:
My mi4i couldn't complete booting,when i try to switch on it will show mi logo and goes to black and again mi logo(mi logo is blinking in a regular interval) the red notification light is also blinking,i tried the mi flash tool ,but the problem is still alive....i was using cm 13 ....somebody please help me:(
[General Questions and Answers] NewRoot23:
New to this forum and new to Android root. I'm excited to get started!

I'm on an LGG3 850 and running Lollipop 5.0.1.

I've followed the root instructions, when I power off the phone, hold down the up-volume and plug in the USB, I get to the Firmware screen. I then use Command Window to insert command string and all looks good, but they don't actually install on phone. I think it's because every time I unplug USB and plug back in USB tethering is off and has to be on for phone to connect to computer. USB Debugging is on. Any suggestion to keep USB tethering ON as the default?

Thanks for helping me!!!

Steve
[General Questions and Answers] mshoaib7:
You don't need USB tethering for adb the problem is probably with USB debugging. Had the same problem with my Lenovo A6000 and I don't have a solution for this but an alternative method. First install kingroot to root your phone and install flashify for flashing custom recovery
[Nexus 5 Q&A, Help & Troubleshooting] NexusUser5:
Hi,

I have come here seeking help for repairing my Nexus 5 which is stuck in bootloop. The phone wasn't rooted with possibly no custom recovery and it's bootloader is locked. And I am not sure which firmware was on it. And I also don't know what was done to it for it to become "bricked" as it was given to me in that state.

I can access the Bootloader Mode (a.k.a. Fastboot) but when I try to enter the Recovery Menu it gives me an Android logo with the red triangle with "No Command." written underneath it. And since the bootloader is locked, I am unable to flash a Stock ROM on the phone.

I have somehow managed to "temporarily" unlock the bootloader by entering the following command.

fastboot oem unlock

But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.

So I tried entering that command then I immediately entered the following commands to flash the stock 6.0.1 recovery.img

fastboot erase flash
fastboot flash recovery recovery.img

But in vain, as it still gives me the "No Command." Android logo when I run the Recovery Mode. I have also tried the same procedure with the TWRP recovery.img but with the same results.

I have also tried launching the flash-all.bat from the stock 6.0.1 right after running the bootloader unlock command mentionned previously. But it fails as i guess the flash-all.bat is programmed to reboot the bootloader before flashing. Thus re-locking the bootloader right before attempting to flash it.

I have come here seeking for help as I believe XDA is the most active Android community online.

If my post is somehow against any forum rules here, please be indulgent as this is my first time posting on XDA.

Thanks in advance.
[Nexus 5 Q&A, Help & Troubleshooting] Primokorn:
At first, fastboot erase flash is not a working fastboot command. It is used to erase a partition: boot, cache, data...

Is your bootloader relocked after typing this?

fastboot oem unlock

fastboot reboot-bootloader

In the stock Android, press Volume up when you see "No Command".
[Nexus 5 Q&A, Help & Troubleshooting] JonesL:
Sounds like the EMMC is dying. http://xdaforums.com/google-nexus-5/general/fix-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
[Nexus 5 Q&A, Help & Troubleshooting] NexusUser5:
Yes the bootloader gets re-locked. And pressing Volume Up doesn't work either.

I've tried the tool and I can't get it to work properly as it gives me an error saying "partition.txt does not exist. Please extract the file from the total binary image."

UPDATE: I just got it to work. The SDRAM test passed but EMMC test failed. So that means it's hard-bricked right? And is changing the motherboard the only way to fix it?
[Nexus 5 Q&A, Help & Troubleshooting] audit13:
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
[Nexus 5 Q&A, Help & Troubleshooting] NexusUser5:
I suspect a hard-brick, so I am strongly considering it. Would you know if motherboards are carrier specific? Meaning if I get a motherboard from another carrier's Nexus, would it end up changing the carrier of my phone?
[Nexus 5 Q&A, Help & Troubleshooting] audit13:
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
[Nexus 5 Q&A, Help & Troubleshooting] NexusUser5:
Thanks a lot for your help, very much appreciated.
[Galaxy S6 Q&A, Help & Troubleshooting] Pottertons:
Posted this in the LG section but have since rid of that phone for the S6.

I'm hoping to find a way to disable the lock screen when i'm at home or another trusted area, without the need for unnecessary GPS/Location usage as with what the 'smart lock' option demands. Also, without having to root the device.

On my S4 widgetsoid did this brilliantly right from the notification panel and it would coincide with the device locking features that were set.

For instance. Whenever i was home I'd disable by tapping the padlock icon. Then if i went out I'd just tap it again to enable it. If I forgot to enable it, the set time limit for the locking options would take control and eventually automatically lock the device on it's own.

Is there anything available like this? Widgetsoid needs system access for this feature to work now.
[Pixel C General] tyvar1:
https://developers.google.com/android/nexus/images#ryu

https://developers.google.com/android/nexus/drivers#dragon
[Pixel C General] oRAirwolf:
Is the MXB48J just an older version than MXB48K? Or are they for different hardware?
[Pixel C General] dkryder:
i'm not sure what is happening with the images. it could be one is u.s.a. and one is international. i've read that upon first boot there is an OTA so it might be one 48j was from factory the 48k is the new update. but i do not think it would be a newer hardwre situation. the binaries are 48k though soit might be a hardware thing. perhaps keyboard related. again complete guessing on my part.
[Pixel C General] CharlesW123:
I'm on 48J after getting the 58mb OTA on first boot, got the Pixel C yesterday(I'm in the UK). No system update available to 48k as yet?
[Pixel C General] McChen147:
I'm also on j, got mine today and during setup it did an ota. I'm in the us
[Pixel C General] scoobydu:
Also now on J in the UK after a small OTA update.
[Pixel C General] scanno:
Any news on kernel sources / device tree?
[Pixel C General] SnegovikRZN:
Who have OTA links?
[Pixel C General] charesa39:
New factory image has been posted for the February security update. Anybody wanna flash it and see if they've fixed the touchscreen and wifi issues?
[Pixel C General] superchilpil:
I'll flash this later today, hopefully it is still compatible with our current boot images.
[Pixel C General] Rox598:
Since Google skipped the Jan update for the Pixel I really hope this one has the fixes for touchscreen etc

Hopefully a Dev can jump in on this and find out.

There wss no OTA to 48K it was a developer build not released to the public other than a factory image.
[Pixel C General] andreoidb:
I just did a Clean flash of the latest factory image and at least for me my wifi is back to normal!!! More testing will be required to see if its really fixed but just ran speedtest and looks promising

---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------

Got a keyboard update as well, having trouble installing it though
[Pixel C General] Rox598:
Can you unlock and relock the bootloader okay on the pixel c? no bootloader flags or anything?