yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S7 Edge Questions & Answers] solefalcor:
I tried the engboot thing to root my g935a but the links were dead in the OP so i downloaded off some other site. Anyways, my phone bricked after flashing G935EngineeringBoot.tar. It was ruinning nougat, 7.1 i think. Phone just keeps resetting and flashing the boot logo. Anyways, i have no idea what my full model number is. I goggle it before and like only a few sites came up that number. It seemed to be really uncommon, not known or maybe newer model. Im woundering if it be ok to use firmware for G935AUCS4API2 to unbrick my phone. Would it really make that much of a difference using a different G935A firmware?

im gonna make sure to download off XDA this time

https://xdaforums.com/att-s7-edge/how-to/firmware-pi2-s7-edge-sm-g935a-10-03-16-t3477246
[AT&T Samsung Galaxy S7 Edge Questions & Answers] norbarb:
Flash this if this is G935A : http://xdaforums.com/showthread.php?p=73222921
[Shield Android TV General] orificium:
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.

But also, I believe the latest version of YouTube will be the stock app, which I just don't like.

I am rooted, which I realize will go away after the upgrade. But also, I don't have anything installed that requires root really. I wanted to take advantage of some xposed features, but apparently there is no version of the framework that supports nvidia shield tv 5.2?

So is it worth upgrading right now? Has anyone tried it? Anything notable worth upgrading for?
[Shield Android TV General] Kickasscowboy:
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.

Any ideas? Anyone?

What to do, what to do?
[Shield Android TV General] jionny:
Most likely have to wait for the developers image .
[Shield Android TV General] meksis:
And flash through FlashFire
[Shield Android TV General] darrendunham:
I have a stock shield (not rooted), but had backed off the YouTube app to be the old one (the one that works with secondary accounts).

I let it upgrade and it did not force a YouTube update. After it finished, I'm still running YT 1.3.11. So you should be okay there.

Of course other than Google Assistant, I haven't found much new. What I really want is for Google Assistant to work with Google Play Music, but it doesn't do that (yet?).
[Shield Android TV General] WisdomWolf:
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
[Shield Android TV General] Kickasscowboy:
I hear you guys. I will wait for OTA update to be downloadable or I might even consider returning to stock. I really don't have any use for root now.
[Shield Android TV General] n1gh7mar3:
FYI, Doesn't work with flashfire.

https://m.imgur.com/a/4ZKy6
[Shield Android TV General] jionny:
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
[Shield Android TV General] mLgz0rn:
I got mine to update even though its rooted.

After it finished downloading, it rebooted into twrp and installed the update automatically with no issues.

I did however get some issues after it finished updating.

The recovery/twrp is gone and cant boot into that anymore.

Root is of course gone.

And now im also just getting a black wallpaper in the launcher instead of the default nvidia one.
[Shield Android TV General] fritzeman:
data/data/com.nvidia.ota/app_download
[Shield Android TV General] n1gh7mar3:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
[Shield Android TV General] jionny:
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
[Shield Android TV General] n1gh7mar3:
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
[Shield Android TV General] jionny:
No you have to get that from Nvidias site however last time I checked it was not up yet
[Shield Android TV General] fritzeman:
you have to flash all the files inside, not only recovery. (nv-recovery-image-shield-atv-5.2.0.zip)

now it worked
[Shield Android TV General] Tifulb:
Screen flickers

My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
[Shield Android TV General] CharliesTheMan:
I've seen a few fixes for screen issues, either making sure in advanced display resolution settings things are correct, or disabling/renabling the CEC in settings.

You may want to check out the nvidia geforce forums thread, I'd probably start out middle to last several pages (assuming you read this soon, in a few days you'll just have to take a guess as there will be way more pages) https://forums.geforce.com/default/.../shield-experience-upgrade-6-0-for-shield-tv/

I think there's a post about chroma clipping which may be what yours is doing, but it could be some of the HDR stuff or something with the HDMI or CEC issues for all I know.
[Shield Android TV General] Thunder2001:
Hi,

i have a 2015 Shield (root) with 5.2 image.

I would back to stock image and unroot my shield.

I have download the "nv-recovery-image-shield-atv-5.2.0".

my approach.

*** Prerequisites:

1. Ensure that the bootloader is unlocked (see above step)

*** Flashing instructions:

1. Execute these commands on the host PC:

fastboot flash staging blob

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot flash vendor vendor.img

fastboot reboot

Is this the right way?

Thanks!
[Shield Android TV General] dafresh:
OTA zip shield 2015 6.0

if someone need:

Original ota zip for Shield TV 2015 (non pro) 5.2 -> 6.0

https://mega.nz/#!BChlSbaR!em9CV5PoRzalWnMWf7iqAj4oVeDQqLhrz_Q1GGXy0Ug
[Xiaomi Redmi Pro Questions & Answers] wilkofife:
I have a 9-month old Redmi Pro which suddenly refused to recognize fingerprint or PIN.

I can get into the Fastboot screen, or alternatively several other screens in Chinese with no English options.

Can anyone advise any sensible action for this non-tecchie other than the dustbin and a new phone ??? (There is not much data on it so a hard reset is no problem -if I can find out how to do it!)
[Xiaomi Redmi Pro Questions & Answers] ayhan4ik:
Hi Friend,

Go to settings --> Additional settings --> Backup & reset --> Factory data reset.

Please let us know if that helps.
[Xiaomi Redmi Pro Questions & Answers] wilkofife:
When I say bricked, I mean I can't get into anything, certainly not Settings. Thanks anyway. I think it's the bin option.....
[Xiaomi Redmi Pro Questions & Answers] neuck:
That screens in Chinese have the recovery option, you can see this video to get that options in English and make a factory reset.

https://m.youtube.com/watch?v=lpoMcO1sQKM
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Ing_Emperor:
Hello,

i have a Samsung Galaxy A5 (2015) SM-A500X Live Demo Unit.

It came with it's stock Kitkat ROM and does not find any updates, but i know that there is a 6.0 update for this phone. So i tried to modify the DBT-Germany Stock 6.0 that i downloaded with those guides:

https://www.reddit.com/r/oculus/comments/40rsdv/if_you_get_a_samsung_s6_live_demo_unit_store/

https://xdaforums.com/showthread.php?t=2349948

In the first guide i could only remove the "modem.bin" but both the other files are not in the stock Rom .tar file. i tried to Flash it anyway, but Odin gave me an error that it couldn't Flash one part, the phone showed some error in download mode "couldnt Flash secured" or something like that. i think the Partition is missing for a specific file?

So i used the second guide and removed EVERYTHING besides the files which are Name in the guide (like stated there), the Flash in Odin went fine, but the phone only shortly Shows the Splashscreen and then Comes back to download mode which tells "Could not do normal boot"

Then i began to Panic, because recovery was dead too...

So i could save the phone, i flashed the twrp recovery, i could atleast go into a working recovery and then i was able to restore the backup of the stock Rom (glad i did this one)

So the phone is working again, at least. But could somebody tell me what i have to do to Flash the 6.0 stock Rom?

Or: Do i really Need to do this since i only want to use lineageos (Nougat), but in the guide it is telling me, that i Need to have at least the marshmallow bootloader and modem. i know that a LDU has no modem but what about the bootloader?

I am very sorry for my bad english! :angel:

I would really appreciate some help...

Thanks a lot!
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Fuji-san:
I've looked around, and there's only a Germany DBT rom for the SM-A500FU:

http://updato.com/firmware-archive-select-model?record=61451820219F11E7963AFA163EE8F90B

You could try that one out, rather than trying to modify some other rom.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Ing_Emperor:
Thanks for the answer, this was also the ROM i modified, but if i flash it unmodified with Odin, i always get this log:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1207)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

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

<ID:0/004> SingleDownload.

<ID:0/004> aboot.mbn

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

<ID:0/004>

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

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

On the phone:

"Secure Check Fail: aboot"

It seems that the bootloader is somewhat locked?

I can still flash a recovery (TWRP) and this is working, the kitkat stock Rom is also working (from backup in TWRP) but i cant get anything else to work, especially lineageOS doesnt boot :/

EDIT:

Slowly i begin to understand: https://techusall.com/solved-secure-check-fail-aboot-error-flashing-firmware/

If i am right, my baseband/bootloader ist not compatible with the normal A500FU so i can't update it?! So there's no solution to this Problem?! :(

Ok, i think this is the end... I even tried to flash the 4.4 Stock ROM for A500FU but it still get the damn aboot.mbn auth error. I think the bootloader on demo phones is somewhat locked and can't be flashed at all, so i am stuck with Kitkat Bootloader preinstalled. So i only can flash 4.4 ROMs i think, this is sad :/

Especially because there is official 6.0 for this phone.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Ing_Emperor:
I still have the same Problem. Does some dev have some advanced Knowledge of those Errors?

It would be okay if it's simply not possible, so i can sell the unit again, but i would like to be sure to not waste an opportunity to use this nice device.
[G4 General] MathiasR33:
Relock LG G4 Bootloader easily

First of all, I'm new here. So please tell me if I broke any rules or if I made any english mistakes.

Warning:

This guide will show you how to easily Re-Lock your Bootloader. Your Bootloader is then Locked! So, it's not really clever to lock the Bootloader when a Non-Stock-Rom is installed...

Requirements:

- LG G4 (H815) [This probably works with other LG's too]

- TWRP-Recovery installed or temporary booted using "fastboot boot"

- Stock-Android installed (Any Version)

- Flashable Bootloader/Boot Zip's for your Android-Version

For Android 6.0 you can get them here: https://xdaforums.com/g4/development/stock-h815-20g-images-kdz-flashable-t3450503

How to Relock:

Step 1: Boot into TWRP

Step 2: Copy the Zip-Files to internal storage

Step 3: Go to Advanced/Terminal

Step 4: Perform this command:

dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc

Your bootloader is Non-Functional now... Don't reboot until the next steps are completed!

Step 5: Flash both Zip-Files using TWRP

Step 6: Reboot

You now have a G4 with stock ROM and locked bootloader. If you wish to uninstall TWRP (Its no longer working) just Flash a Stock kdz-File using LGUP

Hope I was able to help someone...
[G4 General] MathiasR33:
Reserved
[G4 General] ghepardus:
in dd command are 2x //, is the corect command ? or just one / ?

dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc

to

dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

for me misc is /dev/block/mmcblk0p22
[G4 General] MathiasR33:
The command is correct... If you perform it, it will make the bootloader crash. If you flash a clean bootloader now ur device is locked again.

Mathias
[G4 General] steadfasterX:
... Thx for your thread even if it is known that the unlock state is handled by misc partition but it's good to have an own thread for it now. Latest TWRP beta can save the unlock state since a while.

Just wanted to add: if you made a misc backup before unlock you can just restore your backup. You can even flash a misc of an extracted kdz.

And another thing: if you zero out it like described you may loose your WiFi Mac and you can loose your imei. So before using this it's better to backup your current unlocked misc e.g. with the latest TWRP beta (select BL unlock state).

Backup before unlock is possible with SALT DLM backup ( https://tinyurl.com/dlbackup )
[G4 General] freno25:
you said temporary booted using "fastboot boot", which is the method with just fastboot? and second thing the command :

dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc

need any substitution?
[G4 General] steadfasterX:
u can now re-lock your device with fastboot

important: you device must be FULLY STOCK

BEFORE

you lock it again! That means no TWRP, no custom ROM etc! otherwise you will brick the device

if you still want to use that method mentioned here:

Make a backup with SALT (basic mode is enough)

boot into fastboot:

[B]fastboot erase misc[/B]

is doing the same then the above mentioned way.

the misc partition contains also your IMEI, your MAC (wifi) and Bluetooth address. Those SHOULD be re-generated once you boot Android again but if not you will have the backup you created with SALT before.

.
[G4 General] freno25:
wow perfect you was very clear, and OMG I didn't saw your projects man, you rock! another and last questions(after the cmd "fastboot erase misc" I should use the cmd mentioned in your first link? so "fastboot oem lock" (because i tried this cmd with fastboot and my phone is recognized I checked with "fastboot devices" but my try failed maybe I miss something? I unlocked bootloader 1 year ago now I want to relock it so I refurbished the stock kdz with lgup and try the cmd but the console said to me FAIL (unknown command remote) somethings like that)? otherwise What I should do? just flash bootloader and boot zips?

EDIT:

What I've done:

-Refurbished with LGUP last version of KDZ STOCK of my country

-Now I have my device STOCK but with bootloader to relock

-I downloaded your os

-I downloaded the zip bootloader and boot of my KDZ from this site

-I made a backup basic with your software SALT (just in case)

-I have just to erase misc part (don't reboot before I haven't done last flash for rebuild misc partition)

-But my last doubt is which cmd I have to do with SALT for reflash the two zip and if this zip containg the misc partition (because inside I did found misc bin or img)
[G4 General] steadfasterX:
I meant that you can also go the new way which is less risky by flashing the nougat bootloader in my mentioned link. Then you don't need to erase anything.
[G4 General] freno25:
So I can just flash the v29a bootloader over my v20g or I should flash the entire stock with lgup?
[G4 General] steadfasterX:
Flash the TOT available is the easiest way.
[G4 General] mrbelou:
Hello,

thanks for the tuto.

With this method, will the message on the top left corner "bootloader unlocked" no longer appear?
[G4 General] Koile:
how do I restore the backup created with salt? Unfortunately my IMEI & MAC won't restore >.<
[G4 General] steadfasterX:
manually with fastboot or in TWRP. Both require an unlocked device though.

SALT will allow restore in a future release in download mode too.
[G4 General] Koile:
bootloader is unlocked again, but TWRP won't show the bin-files created and fastboot just returns:

> .\fastboot flash misc E:\salt_backup\misc.bin
target reported max download size of 536870912 bytes
sending 'misc' (16384 KB)...
OKAY [ 0.375s]
writing 'misc'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.406s
[G4 General] Spaceboy60:
Can I restore a stock image i backed up with with twrp and go from there or will I need to reflash a tot/kdz and reflash twrp first?
[G4 General] Spaceboy60:
C:\Windows\system32>fastboot erase misc

erasing 'misc'...

FAILED (remote: cannot erase this partition in unlocked state)

finished. total time: 0.031s
[G4 General] steadfasterX:
in twrp:

adb push misc.bin /tmp/
adb shell
dd if=/tmp/misc.bin of=/dev/block/bootdevice/by-name/misc
sync

really reflashing a kdz is your best option. everything must be stock (no twrp or other mods are in place) so flashing a kdz ensures you are good.

that happens when you are on v29a.

on v29a its just a fastboot cmd to lock again: https://xdaforums.com/g4/general/managed-to-relock-bootloader-t3660282

keep in mind that your phone is better pure stock before doing this and it will

100% brick

your phone when you have

UsU'd

your device.

.
[G4 General] Spaceboy60:
I'm on marshmallow, not 29a

EDIT:reflashed back to stock, but command fastboot erase misc still comes up with an error about not being able to flash in an unlocked state.
[G4 General] whitewolf1608:
Hello, dear MathiasR33

I am asking you with a very polite request for technical support. I upgraded after OTA Wi-Fi to the latest version of Android MarshMallow 6.0.

Please help me in the next steps.

The fastboot devices command does not work for me.

I post a screen showing the version of my Firmeware in the LGUP.

And Screen from the CMD console saying that the fastboot devices command does not work.

Please, help me, I am waiting for your answer.
[G4 General] whitewolf1608:
Hello, thanks for your comprehensive answers.

I apologize to you that I have sent you so many messages at once.

Dear Mathias R33 after entering the command in the CMD terminal fastboot boot I have to wait for the device.

The adb devices command works correctly. The CMD console responds correctly - with a message.

Screenshot_1 - the adb devices command

Screenshot_2-the fastboot boot command - Waiting for any device
[G4 General] Spaceboy60:
deleted
[G4 General] Spaceboy60:
OK, I'm using WindowsLGFirmwareExtract where do I find misc from the extracted dz file, browsing through the files there's nothing named misc so I presume it's called something else?

Also when doing the commands from the first page i get (is this normal?):

dd: writing /dev/block//bootdevice/by-name/misc: no space left on device

32769+0 records in

32768+0 record out

(16 MB copied), 21.7 MB/s

should i flash the two files now or am i going to have a bricked device?
[G4 General] steadfasterX:
The time I wrote this I didn't knew about the fact that there is no misc partition in a kdz. Even when you find one it is just a bunch of zeroes as you always start blank .

I don't know what you're trying to achieve here though . You can erase that partition and you will be locked again which means you should be pretty sure that everything is pure stock before !! Using lgup is the best way to ensure this. Then you can just use fastboot erase misc (do a SALT basic backup before is always a good idea!!)
[G4 General] Spaceboy60:
Was trying to verify whether those error messages of "no space left" mean nothing has changed on the device and therefore I can reboot safely or that something has been written and therefore I need to flash the two zip files as per the guide here. Obviously don't want a bricked device so have been waiting for an answer before rebooting.

Would be grateful for a response. Thanks
[G4 General] steadfasterX:
That's how dd works in this particular command using /dev/zero as input device. it will write as much zeroes as possible - until no space left . So yes the command ended successful . As said I hope you have pure stock before rebooting !!
[G4 General] Spaceboy60:
Well was running stock (used lg Bridge). However now the LG Logo appears and keeps annimating and led is flashing blue but it never completed boot.
[G4 General] steadfasterX:
Try Download mode and reflash with lgup
[G4 General] Spaceboy60:
Download mode is playing up a bit on my device (pressing keys don't work most of the time) . I have managed to flash a UK KDZ file after eventually getting into download mode. however must be the wrong firmware for my region as I get a mcc/mnc code error. Getting back into download mode is proving the mission an impossible mission at present time
[Samsung Galaxy S 5 Unified Development] afaneh92:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Instructions :

Download the latest build

Reboot to recovery

Flash the latest build

Wipe data

Reboot

Downloads :

Official builds:

https://download.lineageos.org/klte

Afaneh92's builds:

LineageOS 15.0 for klte

LineageOS 15.1 for klte

Working :

Boots

Sensors

Wi-Fi

Bluetooth

NFC

Audio

Video

Led

RIL (thanks to haggertk & javelinanddart for oss-ril port & [MENTION=5510581]nx111[/MENTION] for data fix)

Fingerprint

Flash

Camera (partially working)

Not Working :

GPS

Sound record

A lot of stuff

Haggertk's unofficial builds, TWRP 3.2.1 needed.

LineageOS 15.1 for klte

Review & Instruction video :

https://youtu.be/Ie6UxhXdD64 thanks to [MENTION=8580938]MikeTheTechSavvy[/MENTION]

Reporting Bugs :

DO NOT Report bugs if you installed Xposed

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)

If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

Sources :

https://github.com/LineageOS

Vendor : https://github.com/TheMuppets/proprietary_vendor_samsung

Thanks :

haggertk

lineageos team

list will be updated, tell me if I missed you!