yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] sweetipi:
Guys, im stuck in "secure check fail: modem" about a day.

Odin is like:

<ID:0/007> Added!!

<ID:0/007> Odin engine v(ID:3.1005)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> SingleDownload.

<ID:0/007> boot.img

<ID:0/007> NAND Write Start!!

<ID:0/007> recovery.img

<ID:0/007> system.img.ext4

<ID:0/007> cache.img.ext4

<ID:0/007> hidden.img.ext4

<ID:0/007> NON-HLOS.bin

<ID:0/007> FAIL! (Auth)

<ID:0/007>

<ID:0/007> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

I'm using a more update firmware and I have tried a lot of modems (CP). I dont know what do do and im desperate because dont have money to pay technical assistance right now.

I'm trying to fix my phone about 3 days now.

He suddenly stopped work and after some hard trys it starts to charge again. But unfortunately got stuck on start up. He's boot looping and then Odin is showing this error(while in download mode, of course).

Also when I try to hard reset, show a 'Manual mode' but dont show the options to click and then back to the looping.

HELP????????? (Galaxy s4 GT-i9192 mini Brazil)
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
Hello,

Probably im not the only one here with this or even everyone with new version of system go this issue.

I'm talking about option "Allow OEM Unlock" in Developer Menu (have to press 10 times on build version in "Information about phone"). Till I've been on Marshmallow 6.0.1 (till MTC20F) this option was possible to turn it on and off -> what was nice way to make phone safer. First i got message about new (1,1GB OTA 7.0) update, then installed it and find out that this option is grayed, so i flashed full firmware from https://developers.google.com/android/nexus/images with full return to stock and factory reset. It didn't helped still its grayed out (by whole time it is grayed on ON position), so i sideloaded SuperSU without changing system integrity (read only in twrp) - still grayed. Anyone knows how to do this working ??
[Nexus 5X Q&A, Help & Troubleshooting] berndblb:
Well, I would guess your bootloader is unlocked already?
[Nexus 5X Q&A, Help & Troubleshooting] SlimSnoopOS:
Mine is greyed out as well. I don't recall reading any posts highlighting this for the developer previews though. Might run the unlock command for the heck of it.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
Relock the bootloader in fastboot (will wipe data), then the toggle will be active again.
[Nexus 5X Q&A, Help & Troubleshooting] RusherDude:
Just to gray out asap he unlockes the bootloader again?

NEVER LOCK A BOOTLOADER.
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
I'm sorry, after locking OEM it will be active yes? But if I unlock it back will it stay active ?

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
If you want the Allow OEM unlocking switch active, the bootloader must be locked. What good is the switch when you are already unlocked?
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
This is what I need. When OEM is unlocked but "in system" trigger OEM unlock is turned off it gives no possibility to flash or use any command in bootloader. I want to flash root then switch off that trigger.

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
[MENTION=4220063]JaCh0o[/MENTION] That switch wouldn't prevent someone from flashing images if the bootloader is already unlocked. That's no how it works. It's there to prevent someone from unlocking the bootloader from fastboot who doesn't have access to the operating system. If you don't want someone flashing images to your phone and you want FRP intact, your bootloader must be locked, and the Allow OEM unlocking turned off. There is no way around that. Root or security. You can't have both.
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
So till marshmallow it was possibly now it's not since 7.0.0?

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] Oblox:
No it still worked the same way in MM as far as im aware just let users toggle the switch but served no real purpose.
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
It's not working in same way course there is no possibility to get this working while having unlocked oem. This was best possibility to keep any other person witch can not log into the system from flashing any files or running commands. Under N it is not possible, under MM it is possible.

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] Lawstorant:
No, it isn't! The switch was toggleable bot did nothing since your bootloader stayed unlocked. Just lock your bootloader and then the switch will be active again, but i will strongly suggest leaving your bootloader unlocked in case of any mishaps. You're rooted, you can still make your device unbootable and then it'll be as good as a brick, you won't be able to recover it because of locked bootloader.
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
First of all it is easy to recover from soft brick by download mode and lg flash tool.

Second it did much because its been disabling possibilities of using bootloader while having unlocked oem - without flash tool it impossible to reset phone or enter to system. So it could be rooted, encrypted, secured by pre system pin and with locked bootloader. And this is what I need to do now.

To cut this discussion, I don't need your suggestions what is safe and what's not. I need someone to tell me how to enable this function in-system "enable oem unlock" trigger while having unlocked oem.

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] Lawstorant:
That's what we all try to tell you. It didn't, fastboot commands were still perfectly usable.
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
Witch one? Fastboot //oem lock/unlock/device-info//boot//flash has not been working on unlocked bootloader with locked function in developer menu.

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] Lawstorant:
It was a delusion then. This setting is only responsible for changing a boolean (true/false) value in memory. Based on the state of this flag, bootloader knows wether it can allow "oem unlock" or not. All the other commands depend solely on device's lock state (locked/unlocked).

A tak btw. to "Wysłane z mojego..." nie pasuje do XDA :)
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
Its not true. It worked as it should in mm and now it's greyed out -disabled anyone knows how to turn this option on?

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I think you are confused.

On MTC20F

Settings->Developer options->OEM unlock = disabled

Bootloader = oem unlock

C:\n5x>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.094s]
finished. total time: 0.094s

C:\n5x>fastboot flash recovery twrp5x.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.766s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.922s
[Nexus 5X Q&A, Help & Troubleshooting] JaCh0o:
On 8th I'm coming back from vacations will check this again and keep you update

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X Q&A, Help & Troubleshooting] milan187:
I agree with others if your bootloader was unlocked that option did nothing by turning it On or Off. This why Google gtayed it out. Once bootloader unlocked it serves no purpose.
[Nexus 5X Q&A, Help & Troubleshooting] RealPariah:
Yeah It's simantics. Look that toggle only tells the phone IF you are allowed to run fastboot oem unlock. IF you ALREADY unlocked it the toggle can be placed in either position and the bootloader would REMAIN unlocked so as to eliminate confusion they greyed it out for devices that boot up reporting an unlocked bootloader.

As everyone keeps warning you IF you lock the loader now with it still rooted it will go erasing data and could cause a problem and you will own a paperweight. IF you are crazy enough to still want to lock it then you should really make sure you go in to SuperSU and select FULL UNROOT and let that finish before I would even think of locking it down again. Some people like this as they install exposed then remove su and lock the laoder so it appears more legit, BUT they are trading off safety if something happens because of xposed or an su command or su itself and your phone goes out to lunch if the loader is locked you have all your disaster recovery options blocked essentially.

I hope that is more clear and all, just ignore the boot warning message which is prolly what is freaking you out it is just informational really incase some app somehow unlocked it without your knowledge and since you knowingly unlocked it you are fine. Besides if you go to send in for warranty you can always lock it later after you flash whatever stock ROM you need.
[Nexus 5X Q&A, Help & Troubleshooting] alvaretto:
I agree with most of you BUT...

I agree that having the toggle disabled while the bootloader is unlocked does not prevent other people from running commands in the bootloader, however, having it in the off possition made it possible to preserve FRP (Factory Reset Protection). I tested this myself. For example, in MM my device had the bootloeader unlocked, it was rooted, i was running Xposed, had a custom kernel, etc, and also had the toggle in the off position. If I factory reseted the device, in the initial config it would say that the device was already tied to a gmail account, and that it needed to enter the details of that account before i could use it. This happened even if I switched between different custom ROMs or installed stock with fastboot commands.

So... It would be great to have that again in N. I want to root and do all kinds of things with the device but also keep FRP working by keeping the toggle disabled.
[Nexus 5X Q&A, Help & Troubleshooting] sintax64:
hi guys

i have problem with re locking my nexus 5x

i cant re lock the bootloader !!

because OEM unlocking is disable !

how i can fix it and relock the phone?

( i flashed stock 7.1.1 and i want to lock it and fully back to factory situation)

pic: uupload.ir/files/0dx_screenshot_20170317-011106.png

(for see picture just copy & paste it in address bar )
[Moto G4 Plus Questions & Answers] ax.xu:
I couldn't get pie controls to work on my g4 plus. Anybody know how to get pie controls or can help me? Thanks.
[Moto G4 Plus Questions & Answers] SMARTHACKER67:
It's working for me well.

I assume you have installed exposed module properly and you are using correct gravity box.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] GnatGoSplat:
I just can't seem to make an extended ROM that won't get corrupted.

As far as I can tell, I am following Faria's tutorial properly. I have tried 2 ways, and I get the same result both ways.

1. Empty out the 9b000000-Extension.nb that I extracted (5MB) and then drag & drop my own files into it using WinImage.

2. Downloaded the blank 10MB extended ROM image, then drag & drop my own files into it using WinImage.

Both ways, if I don't let the customization run, it looks fine in Total Commander. If I do a hard reset and clear everything, then let the customization run, it stops on the second CAB. I hit reset and then look at the extended_rom in Total Commander. It will now be corrupted with lots of folders with funny characters for filenames and several files missing.

I tried a 3rd way and got better results:

- Took extracted 9b000000-Extension.nb and renamed all my CABs to match the names of the existing CABs so I don't have to change config.txt. I replaced 4 of the maybe 40 files. I drag & dropped and when it asked me if I wanted to replace, I clicked "Yes".

This method gets about 90% of the way through, but locks up just the same. I hit reset, go into Total Commander, and see now the extended_rom is completely corrupt again.

I have gone through this dozens of times. I tried flashing the ext rom alone, I tried flashing it together with the OS, together with a splash screen. No better results either way. I have gone over the Faria document several times and can't see what I'm doing wrong.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] GnatGoSplat:
No one has any jewels of wisdom for me?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] joemanb:
did you make sure all your files are set to read only? When you drop the files I think they default to read-only turned off. I forgot this a few times when doing my extended rom and the same thing happened to me. Rightclick on the file, choose properties, check read only (you can select all files and do it in one shot).

BTW: Winimage is the only program I've found for modding that's payware, when trial period expires you have to pay, here's a freeware image editor! the only difference is that it doesn't support long filenames. Just make sure you use 8.3 filenames!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] GnatGoSplat:
You mean set them to read-only within WinImage? For some reason I missed that, I do have them read-only as far as Explorer is concerned, but I didn't realize they need to be set to read-only within WinImage. I'll give that a shot. Thanks!
[X Play Q&A, Help & Troubleshooting] arnabJ:
Please delete this thread. Sorry for any inconvenience caused.
[Samsung Gear S2] obsydian:
Just got this, assume given S3 launch tomorrow it's related only to that as no difference whatsoever.

2.2.16070451
[Samsung Gear S2] tomj_pl:
Me to. Any visible changes.

Wysłane z mojego SM-N910C przy użyciu Tapatalka
[Samsung Gear S2] hegartyp:
Just got the same update. Only difference i can see is there is a battery monitor to tell you what apps are using the battery the most
[Samsung Gear S2] jambo89liam:
Gear app kept failing to update for me, so i uninstalled it, now i can install it at all. Perhaps they have suspended it, untill the release of the s3.
[Samsung Gear S2] Jonbo298:
I noticed on the watch itself it has an option to manage notifications if you scroll left (if there's no active notifications there) but tapping it says ! Failed.

Though it's giving me problems. Not all my notifications are showing up now like they used to. Default SMS app notifications come through and calendar reminders. But Gmail and Facebook messenger aren't coming through (probably more, don't know of yet). Verified they're still set to show notifications on watch.
[Samsung Gear S2] obsydian:
That was already there in the last update but never worked as never resets after a charge
[Samsung Gear S2] echudoba:
Got the update also, could it have been the Gear Plugin that got updated? Mine is 2.2.03.16082251, not sure what it was before but this is a August update.
[Samsung Gear S2] hegartyp:
Ah i see sorry i hadn't noticed it before so assumed it was a new edition
[Samsung Gear S2] yotaman:
After yesterdays update my gear has had a battery drain...my gear 2 is normally at 67% when I go to bed at night at 9pm now at 20% at 3:30pm... this suxs
[Samsung Gear S2] optimummind:
I noticed it too. I shut it down, recharged, and so far it's back to normal.
[Samsung Gear S2] tomj_pl:
I think I know what is new after last upgrade. Now I recieve reports from Gear S2 when it registered some kind of sport activity, I don't remember anything like this earlier.

Wysłane z mojego SM-N910C przy użyciu Tapatalka
[Samsung Gear S2] obsydian:
Yeah realised that when you get the move your arse alerts, when you do move it flicks to the activity screen - so kinds useful.
[X Play Q&A, Help & Troubleshooting] arnabJ:
I appears to me that 'out/target/product/lux/' is having permissions issue. Because there was no 'obj' directory inside 'lux/' when the first error occured. I manually created it. But now when it's there, I still get errors of file not being found such as that eport_includes file.
[X Play Q&A, Help & Troubleshooting] arnabJ:
A clean build again results in initial error. Hope anyone can help me fix it.
[X Play Q&A, Help & Troubleshooting] GtrCraft:
Or your build system is not powerful enough. Or you didn't set it up properly. Anyway building on aosp source is just a waste of your time. Wait for caf or cm releases
[X Play Q&A, Help & Troubleshooting] arnabJ:
I understand it's time consuming but I am willing to put that time and effort.

And regarding my PC Confugration, its Gen 3 Core i3 (4 Cpus @ 2.59Ghz, 4+8 GiB DDR3 RAM 1600MHz)
[X Play Q&A, Help & Troubleshooting] regalstreak:
Sorry new to this answer-question thingy.

Deleted.

---------- Post added at 02:53 AM ---------- Previous post was at 02:52 AM ----------

still this error [MENTION=5293805]GtrCraft[/MENTION] [MENTION=5014460]arnabJ[/MENTION] on the caf sources
[X Play Q&A, Help & Troubleshooting] regalstreak:
still this error [MENTION=5293805]GtrCraft[/MENTION] [MENTION=5014460]arnabJ[/MENTION] on the caf sources
[X Play Q&A, Help & Troubleshooting] arnabJ:
You mean to say that I may not be at fault here? I mean my setup of Local-manifest.
[HTC 10 Guides, News, & Discussion] nkk71:
Coming soon to an HTC 10 near you:

MultiROM 33 and TWRP-MultiROM Edition 3.0.2-6
​

TWRP-MultiROM Edition 3.0.2-x

.

.

Encryption supported

...
<14>[ 2.443388] c1 1 trampoline: Done initializing
<11>[ 2.443423] c1 1 trampoline: Loading fstab "/mrom.fstab"...
<3>[ 2.446923] c1 1 EXT4-fs (mmcblk0p63): VFS: Can't find ext4 filesystem
<11>[ 2.447047] c1 1 trampoline: Failed to mount /realdata with data from fstab, trying all filesystems
<3>[ 2.447500] c1 1 EXT4-fs (mmcblk0p63): VFS: Can't find ext4 filesystem
<6>[ 2.448483] c1 1 EXT3-fs (mmcblk0p63): error: can't find ext3 filesystem on dev mmcblk0p63.
<3>[ 2.448947] c1 1 EXT2-fs (mmcblk0p63): error: can't find an ext2 filesystem on dev mmcblk0p63.
<14>[ 2.448995] c1 1 trampoline: Failed to mount /data, trying encryption...
<14>[ 2.449349] c1 1 trampoline: Running trampoline_encmnt
<11>[ 2.474039] c3 465 trampoline_encmnt: Loading fstab "/mrom.fstab"...
<14>[ 2.474189] c3 465 trampoline_encmnt: Setting encrypted partition data to /dev/block/mmcblk0p63 /dev/block/bootdevice/by-name/extra ext4
...
<6>[ 7.935460] c3 465 device-mapper: req-crypt: req_crypt_ctr: Mapping block_device /dev/block/mmcblk0p63 to dm-req-crypt ok!
<14>[ 8.267473] c3 465 trampoline_encmnt: Found block device /dev/block/dm-0
[B][I]<14>[ 8.268361] c3 1 trampoline: Updating device /dev/block/mmcblk0p63 to /dev/block/dm-0 in fstab due to encryption.[/I][/B]
<11>[ 8.350888] c1 1 trampoline: Running multirom
<11>[ 8.390364] c2 485 multirom: Running MultiROM v33a
<14>[ 8.390992] c2 485 multirom: Loading MultiROM status...
<11>[ 8.391154] c2 485 multirom: Loading fstab "/mrom.fstab"...
<14>[ 8.393403] c0 485 multirom: Adding ROM Internal
<14>[ 8.396716] c0 485 multirom: Adding ROM cm-13.0-20160609-UNOFFICIA
<14>[ 8.398215] c0 485 multirom: Adding ROM ice-2.1.1_PERFUME_UHL_M60_
...

.

.

MultiROM Boot Menu

.

.

Booting Primary ROM

.... Obviously :D, and luckily ;)

.

.

Booting secondary ROMs (even on an encrypted device), here's CM13 test build:

Like it? Add your vote to the poll ;)
[HTC 10 Guides, News, & Discussion] 5m4r7ph0n36uru:
Man that's great news.

Came to know this mod back on the M8 and loved it ever since. Used your port on the M9 - when my username has still been HTCNerdYoda - and definitely would love to see and use it on the 10 as well.

In combination with a partition on my extSD this would be great to try out and test several of the upcoming CM/AOSP based ROMs while still on Viper10!
[HTC 10 Guides, News, & Discussion] Captain_Throwback:
Yeah, hi, I'd like to order a MultiROM for my HTC 10?

kthxbye
[HTC 10 Guides, News, & Discussion] rav101:
I've not used multirom before but I really want to try it out as I've been testing CM builds and helping give feedback. Would make that whole process a lot more simple!
[HTC 10 Guides, News, & Discussion] nkk71:
External SD untested atm, but I'll get to that soon enough... my 200GB sdcard already has 30GB of ext4 formatted space... it flashes fine too, but havent tried booting from it.

Today was the first real trial, and CM13 (okay, I used it because it's small, and relatively painless to flash), and booted fine after a little tweak :cowboy:

I have Viper10 as primary (encrypted too... though most would know how I feel about that), and nonetheless the CM beta ROM, booted, and didnt break anything in internal :)

Order noted, any seat preference :p

BTW guys, he's the one that keeps pushing the boundaries ;)
[HTC 10 Guides, News, & Discussion] 5m4r7ph0n36uru:
Yeah [MENTION=1162986]Captain_Throwback[/MENTION] is the master of TWRP for our HTC devices.

Seems the first test was already a large step on the road to success. Of course extSD is another thing. But you'll do it.
[HTC 10 Guides, News, & Discussion] TeroZ:
Super excited to see this coming! Great for those who wants to try custom build without erasing the daily driver.

Big thanks!
[HTC 10 Guides, News, & Discussion] azZA_09:
I....want....to....ASK YOU WHERE IS THE DOWNLOAD LINK !!!!111!!111!11! (jk jk Im super excited and as [MENTION=1162986]Captain_Throwback[/MENTION] I want a VIP order)
[HTC 10 Guides, News, & Discussion] nkk71:
small update: ext4 (secondary partition does work) ... i mean for the CM13 test build, which I can now safely flash and boot both to internal and external, without "modifications"

...I chose that particular build for certain reasons... ;)

however, I have yet to determine the cause of the "denials" for ROMs in general, so bear with me..........
[HTC 10 Guides, News, & Discussion] 5m4r7ph0n36uru:
Man development is moving on much faster now, then it has been for the first weeks. You're already doing a great job. I'm looking forward to testing this mod as you decide it is stable enough and get it released.

Thanks a million for keeping us updated, much appreciated :good:
[HTC 10 Guides, News, & Discussion] azZA_09:
Any news? (I'm just super excited :) :D )
[HTC 10 Guides, News, & Discussion] 5m4r7ph0n36uru:
It'll need time, but as soon as he's going to release it it'll be easy to use. At least easy for such a kind of mod. Has been great to use his port of the mod on my M9.
[HTC 10 Guides, News, & Discussion] nkk71:
Me too, but you don't want some half baked cookie ;)

Hmm, and you haven't noticed the M9 one is "kinda" broken, thanks to "more unconventional scripts" :p

Anyway, I'm still working on it... but there are several issues (ie more than one) to overcome

One of them, I can "understand" (not really, but ok, I'll accept it), and will look for a more consistent/reliable approach; shouldnt be too bad.

The other one.... just cause I can get it to boot, doesn't mean, "it's ok", even if I'm using a "hack" again, to do that, it's not good enough. I need to (at least a bit) understand what's going on, to be able to make things more consistent. (Hack or not, it still has to have some consistency)

But thanks guys, I'll keep you updated, and hopefully will get this working, but there are so many variables to consider, it does take time, and i can only spare so much :o
[HTC 10 Guides, News, & Discussion] 5m4r7ph0n36uru:
Take your time. And I know it'll be a great hack once it can be released. I'll patently wait.

And no I didn't recognize that it has been kind of broken on the M9. Following your instructions back there worked like a charm mate.:good:
[HTC 10 Guides, News, & Discussion] azZA_09:
Take your time and good luck and happy coding :DD
[HTC 10 Guides, News, & Discussion] nkk71:
The M9 one isn't really broken, just some people *cough* *cough*, keep changing their scripts ;)

And since no one has mentioned it, I never updated it, but it will probably be included in the HTC 10 release, since that device uses some new methods as well :eek:

... that is ... if it ever get's released, let's just hope we can get to the bottom of this :fingers-crossed:

and soon