yashsingh1/xdaforums huggingface dataset:
[LG V20 Questions & Answers] DrPhant0m:
So, I did *#06# in the dialer to display the IMEI, and it's different than what's on the box and sticker! I'm guessing it's been rebuilt or refurbished. Would you all accept this as OK, or should I send it back to the seller for misrepresenting a rebuilt product?

Anyway... I used this new IMEI, and successfully got the unlock.bin generated from LG Developer.

Unfortunately, when I try to flash the unlock.bin, I get the following error (I ran it twice)...

D:\Android\adbconsole>adb reboot bootloader

D:\Android\adbconsole>[COLOR="Lime"]fastboot flash unlock unlock.bin[/COLOR]
Error: target reported max download size of 536870912 bytes

Error: sending 'unlock' (1 KB)...
Error: OKAY [ 0.050s]
Error: writing 'unlock'...
Error: [COLOR="Red"]FAILED (remote: oem unlock is not allowed)[/COLOR]
Error: finished. total time: 0.066s
D:\Android\adbconsole>[COLOR="Lime"]fastboot flash unlock unlock.bin[/COLOR]
Error: target reported max download size of 536870912 bytes

Error: sending 'unlock' (1 KB)...
Error: OKAY [ 0.037s]
Error: writing 'unlock'...
Error: [COLOR="Red"]FAILED (remote: oem unlock is not allowed)[/COLOR]
Error: finished. total time: 0.052s

Can anyone help with this? Thanks so much for your interest and responses. I bought a US996 from Swappa for last year, and didn't have any of these issues. It must have been more "legit."
[LG V20 Questions & Answers] DrPhant0m:
Update... the problem above happens when you don't have "OEM Unlock" enabled in developer options...

But, I had flipped that switch, and I guess it doesn't persist across boots (it turns off when you turn off the phone, I guess).

In any case... it appears that I have unlocked my bootloader now. Thanks to everyone for the replies, because it got me thinking.
[LG V20 Questions & Answers] pistacios:
I was just about to reply with "make sure to check the oem unlock box" in settings. You beat me to it.

Awesome!
[Galaxy S 4 Q&A, Help & Troubleshooting] dems314:
Hi everyone I'd really appreciate it if someone could link me to a google camera hdr+ port for galaxy i9500

I have been downloading apps left and right but the installation just says app isn't compatible with this device I'm using lineage nougat BTW ☺?
[Galaxy S 4 Q&A, Help & Troubleshooting] aloochat:
Nope, i don't think the S4 can take that much processing even S6 force closes background apps( Launcher and some other stuff), but it works on S6 though.
[Galaxy S 4 Q&A, Help & Troubleshooting] dems314:
Oh OK if its a hardware issue then I can live with that ?
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
The S4 processor is sufficiently powerful that it can handle standard hardware-based HDR. As opposed to a software overlay, which is how the stock S4 camera works, a hardware-based option takes (ideally) three pictures: one normal, one underexposed, and one overexposed and combines them. The reason the processor can't handle HDR+ is due to how HDR+ functions. HDR+ doesn't rely on adjusting the exposure but instead adjusts the image's ISO for each shot in a group of ten. The rapid change in ISO between shots in a group plus the number of shots taken requires more resources than the processor has available.
[Galaxy S 4 Q&A, Help & Troubleshooting] dems314:
Damn didn't know HDR was that hardcore, well at least now I know its not because I suck I finding the right version

Thanks
[Samsung Galaxy S8+ Questions & Answers] dwlotter:
I have posted on this twice and have not received any advice. My wife just tried to call from an airline desk and it went to voicemail. I called the number back and it is United Airlines phone system. She is desperate to get a hold of me. So that is why I need some help because this problem persists.

When I touch the phone it goes to voicemail. I don't know what else to say about this. I have checked all of the switches that I know that could be causing this like the proximity sensor and things like that.
[Samsung Galaxy S8+ Questions & Answers] KennethHau:
maybe you have the switch "reject private numbers" enabled?
[Moto G5 Plus Questions & Answers] JuanM28:
Ocurre lo siguiente, la barra de navegación se esconde como debe ser en todas las aplicaciones (Multimedia,Juegos,etc) pero no lo hace con un juego en particular y es GTA SA, es molesto porque me roba pantalla y el juego no se ve bien y es difícil controlar, solo con ese me ocurre esto.

Alguien sabe como solucionarlo o porque sucede??
[Moto G5 Plus Questions & Answers] mnoguti:
Nor english or spanish are my main language but I can translate it:

Navbar hides itself like it should be in all apps but that doesn't happen in GTA SA and that annoys him because it takes some screen space making it harder to see what's going on and the game is already hard to control. It only happens in this game. Does anyone knows how to fix it or why does it happen?
[Moto G5 Plus Questions & Answers] RonuPonu:
Es un problema de la aplicacion, me sucede en todos los dispositivos con los que he jugado el GTA SA (Moto G2, G3, E2, G5 Plus) tambien pasa con GTA Vice city entonces no es problema de tu celular es problema de la aplicacion

Tambien recuerda postear en ingles, el idioma principal de este foro, para obtener una respuesta mas rápida ;)
[Moto G5 Plus Questions & Answers] RokCruz:
Usas navegacion con un boton? en teoria deberia desaparecer la barra de navegacion por completo.
[Moto G5 Plus Questions & Answers] JuanM28:
Gracias, no tenía idea de que pasaba lo mismo en otros modelos, creo que al ser un problema del juego no tiene solución así que bue.
[Moto G5 Plus Questions & Answers] JuanM28:
La usaba, pero prefiero los botones virtuales, sé que es tonto pero me siento más cómodo así.
[Moto G5 Plus Questions & Answers] RokCruz:
Podrias utilizarlo mientras usas ese juego, o quizá reducir más el tamaño de pantalla para que no te estorbe.
[Galaxy S6 Q&A, Help & Troubleshooting] Dudeminator:
I installed the XtreStoLite DeoMod Edition 3.3.1 MMROM, which is great, but i wanted to install Smart Manager but overlooked it, if i want to go back and install it, do i have to start from scratch or can i just go back and pick it out and not lose everything else? Thanks.
[Galaxy Note5 Q&A, Help & Troubleshooting] Gdog2014:
Hi guys:

I am hoping someone can help. I am an average phone user and I tried to update my Note 5 to the latest Android OS that's available for it using the Verizon Wireless software upgrade assistant. I did this because it would not upgrade over Wifi.

As it was updating over USB, it disconnected and re-connected by itself ( I heard the usb-connect and reconnect sound) and then it gave me a message that said "The device is in need of repair, go to repair assistant" . So I am running that now for the past 2 hours. I am not sure if its stuck or just taking a lonnnnngggg time. On the phone display it says "Downloading, do not turn off target" . As A long time IT guy, I have my doubts that this will ever complete. What are my options if it does not ? My phone is mint, no issues other than this.

Thanks in advance for any replies.
[Android Q&A, Help & Troubleshooting] JailBreaker101:
Hey guys is it possible to activate mhl in a non mhl device??!
[Pixel C Q&A, Help & Troubleshooting] :
I was trying to flash LineageOS but didn't work. I then attempted to fix my mistake. My attempts only made the problem worse as now I can only use fastboot. There is no recovery or OS.

I do have the latest ADB and Fastboot drivers on my computer.

I have unlocked the bootloader.

fastboot oem unlock
...
FAILED (remote: Device already unlocked)

When I flash the factory image, I get this message:

writing 'bootloader'...
FAILED (remote:unsupported command)

This happens when I try to flash the other images found in the factory images file from Google individually. This also happens when I try to flash the latest TWRP recovery image.

The following commands also return a "remote: unsupported command" error:

fastboot erase [partition]
fastboot format [partition]

I have also locked and reunlocked the bootloader but doing this does not change anything when flashing again.

When the bootloader is locked and I return to the screen after pressing lock and volume down, there is a red box that reads:

OS on your tablet is damaged. Needs recovery.

This goes away when unlocking again.

I have tried Unified Android Toolkit but have run into the same "remote: unsupported command" response.

This highlights all my attempts to fix my tablet. Thanks for reading up to this point.

I've seen suggestions to use fwtool but I can't wrap my head around how to use it. If that is the only way to fix my tablet, can someone show me how to use it to solve my problem? Keep in mind I can only use fastboot. No recovery or OS.
[Pixel C Q&A, Help & Troubleshooting] sabrdawg:
Is there a flashall file in the image from Google?
[Pixel C Q&A, Help & Troubleshooting] :
Yes. When I run it, get into the same message.

writing 'bootloader'
FAILED (remote: unsupported command)
[Pixel C Q&A, Help & Troubleshooting] sabrdawg:
I was just reading about someone else who had a similar issue, and it was recommended for them to update their ADB and fastboot. Hope this helps!
[Pixel C Q&A, Help & Troubleshooting] rhmanoa:
Hi, did you tried to lock fastboot then unlock it again. Try also to change the bootloader or the kernel with fastboot or boot directly twrp without installing it
[Pixel C Q&A, Help & Troubleshooting] :
I have locked and unlocked the bootloader. I have also flashed bootloader and kernel images from the factory images and I get the same "Remote: unsupported command" message.

I don't think I understand this. By "twrp" you mean boot straight into recovery mode, I can't. Every time I try to, I am stuck on the Google screen. I left it on that for an hour with no change.
[Pixel C Q&A, Help & Troubleshooting] :
Can you direct me to where to download the latest drivers? You look like you're more familiar with this than I am and me being new to using fastboot, I may have gotten an older version.
[Pixel C Q&A, Help & Troubleshooting] sabrdawg:
This should help :)

https://developer.android.com/studio/run/win-usb.html
[Pixel C Q&A, Help & Troubleshooting] :
It appears I have the latest drivers. To make sure nothing's changed, I flashed the factory image again and it gives the same response as before.
[Pixel C Q&A, Help & Troubleshooting] Vartom:
fastboot boot twrp-3.1.1-1-dragon.img
[Pixel C Q&A, Help & Troubleshooting] :
I am greeted with "remote: image verification failed".
[Pixel C Q&A, Help & Troubleshooting] Vartom:
Is the boot loader unlocked before this command is executed?
[Pixel C Q&A, Help & Troubleshooting] :
Yes, it was unlocked. I tried relocking, reunlocking, and executing the same command but it still gave me the same message.
[Pixel C Q&A, Help & Troubleshooting] Bolemichel:
I got exactly the same problem. Any solution for this?
[Pixel C Q&A, Help & Troubleshooting] :
I've read relocking and unlocking the bootloader fixes it so that you can flash through fastboot. This didn't work for me, unfortunately , and haven't been able to fix my Pixel C.

Are you sure you no recovery? I was not able to fix my tablet because I foolishly deleted my recovery and was stuck in dev mode but unable to flash anything. As long as you have a recovery, you can fix it. I don't remember exactly how but you'll be able to find it.
[Pixel C Q&A, Help & Troubleshooting] Bolemichel:
lock/relock has no effect. Unfortunatelly recovery is broken, tab will reboot when I try to enter recovery.

I'm in contact with google and try to get a new unit now
[Pixel C Q&A, Help & Troubleshooting] RandolphWu:
I also have the same problem and I am so disappointed that I cannot figure it out....#pls forgive my poor English#who can help me ..it is same to me that I have no idea to use so called"fwtool"tool.
[Pixel C Q&A, Help & Troubleshooting] Evren Tekin:
Guys I have been trying to fix this for the past week and found these two posts.

https://xdaforums.com/t/recovery-twrp-dragon-3-5-0-2021-12-31.3400503/post-73361170

https://xdaforums.com/t/xceed-kernel-aosp-stock-purenexus-v9-xx-android-7-1-2.3289357/post-64777133

It explains how to use fwtool, it's actually pretty straightforward. The second link above has the download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:

adb push <path to fwtool>/fwtool /sdcard/Download/fwtool

You should get a message like this below:

fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)

Then open the shell in adb using:

adb shell

then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:

cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap

The output for me was:

127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0

I then set the flag to 1 using fwtool as below.

fwtool vbnv write dev_boot_fastboot_full_cap 1

After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot :)

I hope this helps everyone and good luck...
[Pixel C Q&A, Help & Troubleshooting] funguy2:
Yes, but no adb without recovery
[Moto G Android Development] DoctorStrange96:
Unfortunately this project can no longer be maintained. I have acquired a new device and can no longer use Google Cloud Platform to build ROMs.

Introduction:

Hello everyone, this is my build of LineageOS with full Substratum support, and by that I mean rootless Substratum, with all its goodies! Yay!

Installation:

- Download the ROM

- Download a gapps package of your choice. I recommend Open GApps, but if you're more fond of Beans GApps, it should give you no trouble

- Put both zips in the root of your internal storage (/sdcard) or copy them to a USB OTG drive if you have one

- Make sure you have the latest TWRP installed

- Reboot to recovery and flash both zips sequentially (ROM first, obviously)

Always clean flash (wipe data + system) when coming from another ROM!

If you're coming from official LineageOS and want to try dirty flashing, check reserved post #4.

- Reboot to system and have fun!

How do I su?

It's up to you. There are four options:

1. Lineage's su addon (my preferred!)

2. SuperSU

3. Magisk

4. phh's Superuser

Download:

LineageOMS for falcon

Thanks to:

The LineageOS team: this is all their work, I only added the necessary hooks for OMS and exposures

The Substratum team: their dedication would not make this possible (special kudos to @nathanchance for his thread on how to add OMS support to LineageOS)

@himavanth.reddy925 - I used his template for my thread. He built LineageOMS for osprey and merlin a while ago. Link to his thread

Any other open source contributors

Sources:

https://github.com/LineageOS

https://github.com/LineageOMS

Donations:

If you feel the need to donate to me as a "thanks"... There you go.

XDA:DevDB Information

LineageOMS, ROM for the Moto G

Contributors

Kamin4ri

Source Code: https://github.com/LineageOS

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

Based On: LineageOS

Version Information

Status: Abandoned

Current Beta Version: 14.1-20180303

Beta Release Date: 2018-03-03

Created 2018-03-03

Last Updated 2018-05-15
[Moto G Android Development] DoctorStrange96:
Changelog:

03 Mar 2018:
- Fixed missing Interfacer

02 Mar 2018:
- Initial build
- Based on latest LineageOS 14.1 source code with OMS commits merged
- Includes 05 February security patches
[Moto G Android Development] DoctorStrange96:
F.A.Q.

(Read this before crying!!!!)

Q: Oh look at him! He's building ROMs now!

A: This is my first attempt at it. Please on't expect me to perform flawlessly. And I don't know how long I'll be in this game for.

Q: Why did you come up with this ROM?

A: Because there were no LineageOMS builds for our dear Moto G.

Q: Will you maintain this project?

A: On a weekly basis, at most. But expect me to release new builds bi-weekly or when the LineageOS team merges the latest security patches.

Q: Can you also maintain for device xyz?

A: For now I plan on maintaining only for falcon (and perhaps titan). But if there's interest, I can maintain for the whole Motorola MSM8x26 family (falcon/peregrine/titan/thea).

Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!

A: Apart from the OMS exposures/hooks, I haven't changed a single line of code from the original LineageOS sources. So I don't know what can be the cause of your battery draining that quickly. Please do check your wakelocks.

Q: What works and what doesn't?

In theory, everything should work, and nothing should be broken, since this ROM was based on the latest (official) LineageOS source code.

Q: Will you add feature xyz from rom abc?

A: No. I don't plan on deviating from LineageOS. Let's keep things simple.

Q: How do I report bugs?

A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.

Q: How do I flash this?

A: I suggest you scroll up and read the OP. The instructions are there.

Q: How do I tweak this ROM?

A: LineageOS offers quite a few customisation options, and for theming, there's full OMS/Substratum support. If you still want more tweaks, use Xposed and GravityBox. (Just be careful to avoid conflicts)

Q: This kid is such a n00b!

A: Oh well then, why don't you go build a ROM yourself, instead of criticizing my work and consequently wasting your time?
[Moto G Android Development] DoctorStrange96:
Screenshots:
[Moto G Android Development] DoctorStrange96:
Instructions on how to migrate from official LineageOS:

(For those of you who want to dirty flash)

Remove all Substratum overlays before doing this! Remember that official LineageOS still uses legacy RRO which is incompatible with OMS! Don't do this and you'll most certainly get a bootloop.

- Download the official-to-unofficial ZIP file and push it to your phone (either via adb or via USB cable)

- Reboot to recovery

- Flash the ZIP

- Flash my LineageOMS build

- Reboot

In case you decide to go back to official LOS builds, repeat the above steps, but use the unofficial-to-official ZIP instead.
[Moto G Android Development] SunilSuni:
LineageOS with rootless OMS is a best combination. Thanks Dev for this ROM. Gonna try this now
[Moto G Android Development] SunilSuni:
Any modifications at kernel level ?? Or is it same as LineageOS, because I'm observing good battery backup
[Moto G Android Development] DoctorStrange96:
Same as LineageOS.
[Moto G Android Development] blunatic:
can i dirty flash over normal LineageOS ?
[Moto G Android Development] SunilSuni:
No Clean flash recommended. Read Instructions properly
[Moto G Android Development] DoctorStrange96:
Over official LineageOS? No. You'll run into signature problems.
[Moto G Android Development] DoctorStrange96:
That's quite all right. We all do that sometimes.
[Moto G Android Development] legendavey:
I know, but we must also encourage good forum etiquette. :o

Thanks for this build, BTW. The most stable option for a Moto G right now is Lineage 14.1 and OMS commits mean I can run completely rootless! :D
[Moto G Android Development] DoctorStrange96:
I agree with you there. Etiquette is essential. ;)

Yeah, it's been a long while since someone last built LineageOMS for the Moto G. Since I figured out how easy it was to add OMS support to Lineage, I decided to do it myself. Enjoy!
[Moto G Android Development] DoctorStrange96:
I just figured out a way to do that. Check reserved post #4 ;)
[Moto G Android Development] M4T145:
Where is the substratum menu? lol
[Moto G Android Development] SplaszIG:
Can you build this for peregrine too ?
[Moto G Android Development] JoKeR_Roxx:
try installing substratum from playstore or apk
[Moto G Android Development] DoctorStrange96:
I think so.

Edit: Here's a build. https://drive.google.com/file/d/10SYgZ0y0BxW4BGSAHWNzSnvFyNyxh2sj/view
[Moto G Android Development] DoctorStrange96:
Hey guys,

As I said in the KaminariKernel thread, unfortunately, my projects for falcon & family (peregrine, titan, thea) are coming to an end. My Moto G died and I have recently got a new G5S (montana), so, I'm going to develop for that device from now on.

And I don't think I'll be able to build ROMs again until I get a powerful enough machine (I was using Google Cloud Platform but my free trial ended and I - quite obviously, can't upgrade to a paid plan).

If someone wants to maintain this project, feel free to use my sources. Shoot me a PM if you need help / more info.
[Windows Mobile Development and Hacking General] itolson:
What do you need apart from wm6 sdk and vs 2005 to get up and running to write simple apps.

may seem a daft question but i have managed to write little programs in c# 2005 but would like to look at vs 2008.

any help would be appreciated.

thanks
[Windows Mobile Development and Hacking General] Koterpillar:
Nothing. Just create a Smart Device project. And 2008 didn't change much at all.

(On the second thought, though: common sense will be helpful.)

(On the third thought: "Express" editions will not do.)
[Windows Mobile Development and Hacking General] arpy:
...the Professional version of VS2005, the NET.CF installed on your Device,a good book about developing on Mobile Devices with .Net,some good ideas and other sdk`s,if needed...
[Windows Mobile Development and Hacking General] holodila:
What books? I've been searching everywhere, mostly there are the books about a program without a single line of code, just drag&drop. Can you advice please good books about mobile C++ programming??
[Windows Mobile Development and Hacking General] Koterpillar:
C++ says who? Original poster was using C#.

C# books:

http://www.c-sharpcorner.com/ebooks/

Judging by your avatar, here you are: http://www.intuit.ru/department/pl/csharp/lit.html

C++ books... get anything you want on Windows programming (MFC, WinApi, whatever), it's all the same. Almost. Use MSDN when in trouble.
[Samsung Galaxy S8 Questions and Answers] manjotsc:
Is it okay to flash Samsung S8 sm-g950W with the sm-g9500 or any model number version of firmware
[Samsung Galaxy Nexus] Dudefoxlive:
Hi, I'm sorry if this is not the spot to post this but i am looking for an android 4.4 rom for my verizon galaxy nexus. I want to use AOKP but they took down the 4.4 rom for this phone and it bums me out as i also want to use franco kernal and AOKP was the only rom that supported it. I wanted to either use AOKP or and old version of Cyanogenmod and LineageOS only has version 13 of their roms and i think they are Android 6.0. I have had performance issues on anything Android 5.0 and higher and Android 4.2.2 Official release no longer supports some of the apps that i use. Any help would be nice as Android 4.4 is kinda the sweet spot for this phone and I had the same issue with my Droid Razr. Found an old Cyanogenmod android 4.4 rom for it and its perfect. Any help would be nice. Thank you!
[Samsung Galaxy Nexus] rahimali:
AOKP to your heart's content :)
[Samsung Galaxy Nexus] Dudefoxlive:
OMG Thank You!! People on reddit want to complain that kitkat is unsecure. Yea i know and i am willing to live with it though. their website only has old jellybean roms for this phone and i wanted kitkat. I wish they had one for the Droid Razr but sadly they dont but i did find an old Cyanogenmod rom for it and that worked. I have also noticed that they run better on kitkat. LineageOS has BAD performance issues on these old devices. Thanks Again! :)
[Samsung Galaxy Nexus] rahimali:
I do agree with you KitKat provides the best performance on these legacy 1GB memory phones but I would recommend that you use one of the two most recently updated ROMs (unlegacy android / omni), both from 2018 rather than these almost four-year-old ROMs...
[Samsung Galaxy Nexus] Dudefoxlive:
I have heard of omni rom but I have never heard of unlegacy android. Could you provide a link to the site for it? Also the mobile app does not do well with going to other forums so I am not sure about the links above u sent for the two roms.