yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Theese are all of the 67 MSM8960 Snapdragon s4 Plus/Pro devices:

I found theese using Gsm Arena Feature Search

BlackBerry Z10

Nokia Lumia 1020

BlackBerry Classic

Motorola Moto X - Los 11

BlackBerry Leap

BlackBerry Z30

Nokia Lumia 920

BlackBerry Q5

Sony Xperia SP - Los 17

Casio G'zOne CA-201L

Nokia Lumia 925

BlackBerry Porsche Design P'9983

Motorola DROID RAZR M - Los 14.1

Nokia Lumia 820

Sony Xperia V - Los 17

BlackBerry Porsche Design P'9982

Samsung Galaxy S III I747 - our device - Los 14.1

HTC Windows Phone 8X

Pantech Flex P8010

Samsung Galaxy S III CDMA - our device - Los 14.1

Pantech Discover

Pantech Vega Racer 2 IM-A830L

Yota YotaPhone

Samsung Ativ S I8750

NEC Terrain

Samsung Galaxy S III T999 - our device - Los 14.1

Sony Xperia LT29i Hayabusa - Los 17

Nokia Lumia 928

Motorola DROID RAZR HD - Los 14.1

Motorola DROID RAZR MAXX HD - Los 14.1

LG Optimus Vu II F200

Samsung Galaxy Rugby Pro I547 - cm-10

HTC One XL - Los 14.1

LG Optimus LTE2 - cm-12

Motorola RAZR M XT905 - Los 14.1

HTC One SV - cm-11

Motorola ATRIX HD MB886 - Los 14.1

Sony Xperia SX SO-05D

Kyocera Hydro Elite

Nokia Lumia 822

HTC One X AT&T - Los 14.1

Nokia Lumia 810

Samsung Galaxy S Relay 4G T699

Samsung Galaxy Stratosphere II I415

Sony Xperia GX SO-04D

Sony Xperia T LTE - Los 17

Huawei Ascend P1 LTE - cm-11.1

Kyocera Torque E6710

Kyocera Hydro Xtrm

Samsung Galaxy Victory 4G LTE L300

Samsung Galaxy Express I437 - cm-11

LG Motion 4G MS770

Motorola Luge

HTC Evo 4G LTE - Los 14.1

LG Mach LS860

Huawei Premia 4G M931

Samsung Galaxy Stellar 4G I200

Samsung Ativ Odyssey I930

LG Spectrum II 4G VS930

HTC DROID Incredible 4G LTE - cm-12.1

LG Lucid2 VS870

LG Escape P870

LG Optimus F5

ZTE Flash - cm-11.1

ZTE Grand X LTE T82

ZTE Vital N9810

XOLO LT900

There are a lot but the most supported is the Sony Xperia T/X/V/SP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
good luck bro ,you can do it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
The device still get twrp updates so even android 9 can be flashed with this recovery version (3.3.0)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I am sorry for constantly replying, but in my opinion, I should just skip OREO. It's a pain and there are typos on the source code. I will continue, but with Los 16, because it's still updated. I think that all of the issues are with the device tree, vendor files and sepolicies. I do not promise it will work but I think this is our best bet. On Github, people add changes to the kernel because they want to optimize it fully, and remove bugs. This will take a while, but I think that skipping oreo is better and we will save time : ) Let me know your thoughts. I want to bring this device to PIE and the only thing that is still keeping us is the developers and the knowledge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
that is better to skip oreo , i am not developer and my informations are poor but i think device tree and vendor shoud be taken from samsung device there is some differents between sony and samsung so it may causes errors-i asked someone and he tells me that- But by experience we can know that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I am still making progress, but I was looking at galaxy s3 motherboards (i9300, neo) prices on aliexpress and I was shocked after seeing the really low prices for theese boards! (4-15$!!) I was thinking if I could swap boards between my other broken d2 and i9300 or neo. We could still have our old phone with a newer snapdragon 400 and enjoy android 10! One thing that would concern me is the display, the inner frame and the cameras but I think it would be a great and cheap project to do! One thing we would lose is the 4G LTE but 3G still works fine in my region and I dont use mobile data. What do you guys think about it? Should I try it?

Here are some s3 boards: https://www.aliexpress.com/wholesal...n=y&SearchText=Samsung+galaxy+s3+motherboards
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
i that's good idea but it's not easy to do
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Advice for anyone trying to build this past 14.1, study a similar devices tree put all the files side by side and make the appropriate changes . I have successfully compiled past 14.1 but there is a problem with the kernel that stops it from being loaded and read in the new order so it just bootloops after flashing. I dont have the funds to put in the amount of time and effort it would take to get it running but for anyone that does, study the tree make the changes and build an updated kernel. The kernel is the priority.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
You are finally back!! So you are saying that the device tree is the issue? It's not the kernel?

I am compiling Los 16, and I would say it's better than 15.1 because it had a lot of errors.

For example I am stuck at "No rule to make image.gz" (Don't remember if it was the exact error)

One problem I have with the device tree is that there is the D2att and then D2-common and it's so confusing.

But I am willing to put the effort into it especially that I have the source already downloaded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
The only device tree that we have is from 14.1, so you take that device tree compare it to similar device tree running a newer version of android, note the changes and make them match accordingly. Your error is because you have to add BOARD_KERNEL_IMAGE_NAME := zImage or something very similar to the boardconfig.mk file you will run into another error about recovery image being to large if you dont add the command to compress it in the boardconfig.mk ( something like LZMA_RAMDISK_TARGETS := recovery) but it is a kernel problem I have not messed with anything in the kernel source but its setup to boot in the older order of android around oreo the implemented project treble. Do some research study the trees and concentrate on the kernel and recovery the device tree will come together given enough effort and research but until there is a d2 kernel that can boot the new configuration it will not boot also the d2 common folder is the d2 folder the d2att folder and the d2spr etc are to separate the different variances of the device to pull prop files
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Alright, now I have a lot of time to play around with this, now that I installed Ubuntu on my machine in dualboot, planning to switch fully to it, which is quite amazing. I have more played with the Surface RT and helping the hacking scene to make programs for it hoping to get other OSes working, hence the fact that I haven't been active on the att S3. So I will be continuing soon, I have to take some time to setup everything. It should be much faster on my main instead of a VM to take advantage of the 16GB of RAM and 8 cores, to get builds to compile faster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] palmbeach05:
I understand that if you upstream a kernel, its better to use a LTS for that. Is upstreaming the kernel a good idea or a possibility?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DavidWCS:
Thx for keeping us 'in the loop' regarding your work.

There are still a few Samsung Galaxy S3 users out here, and I for one greatly appreciates your efforts. Thank you for keeping us 'in the loop' regarding your work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] palmbeach05:
I see potential. Ok, this is a backup device for me since i broke my regular phone (samsung j5 2015). It may be a bit sluggish at times, but i agree with what joker had said, focus on the kernel. But i'm also wondering if we could push 3.10 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I read that upstreaming a kernel is not a perfect idea, and I don't know how to do that :/. Joker said to also look at the device tree, and apply Oreo changes to it. I can do that, but I am not sure if that will fix the problem. Basically, he said that the phone won't boot to Oreo (He made a build of Oreo for this phone) and would loop, without showing the initlogo, similar to TWRP not booting when the kernel is set to enforcing (If you ever experienced this problem). I and Joker think the problem is that the Kernel does not get loaded, maybe because of the device tree, we don't have a way to capture logs, but I will do my best to see if the device tree "Upgrade" will fix the problem. However, I would continue with Pie, since for some reason, Oreo compilation had some problems with typos which got me stuck at a stage, and I could not fix it myself, since I don't know where that typo is. (It was the fault of Lineage, not the phone or OS.) I am happy to see someone else interested in "Reviving" the Galaxy S3 custom ROMs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
hello , my t999 board was bricked so i did the same thing you talk about , i9300 board doesnt fit to i747/t999 case so i breaked it to fit and worked fine but still have network problems maybe i9300 board has problem on sim card place... i will try los 15.1 16 17.1 to test it on this device for daily usage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Update: unfortunately I am still not able to successfully build Android 9 for it up to now.

I have been very busy but I hope I can use this holiday vacation to finally release a successful build. I have created a unified Android 9 device tree to avoid confusion with the common stuff here https://github.com/alexenferman/device_samsung_d2att and I will modify it as I go along with the compilation process. Since I first started one year ago, I have picked up so much stuff so the process of diagnosing and fixing problems will be much easier for me right now. If there is any other developer who is willing to build or help let me know, have a nice year everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
There is quite a problem with the kernel or Init on this device. I started by Creating a Recovery image since that is easier to debug but it does not boot, it only goes to Download mode, with prebuilt or source kernel. Maybe it's another issue, but I am just wondering how Joker got Oreo recovery to work. Anyways, I will hopefully find a fix for this.

Edit: Will build 7.1 recovery and see if it works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ClaireCameron:
This quite is a big problem :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Ironically LineageOS recovery built on 14.1 works but the one built on 16 is not. So the kernel or Device tree is an issue. I will take the time to examine the differences required to update the device tree to make it work with Lineage 16.0 correctly.

Also when building LineageOS 16 it was almost done, but I don't think it makes sense to continue with the ROM right now because the kernel is not working for L16. I will first fix the recovery to make it work and then I will continue with the ROM itself.

Download Lineage 14.1 recovery here: https://files.alexenferman.com/?/Samsung-Galaxy-S3-i747/Custom-ROM-Builds

Edit: The LineageOS 16 recovery is missing the init files, no wonder it won't boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I finally successfully built a Lineage 16.0 ROM and RECOVERY, spent 2 full days on this and I hope it will finally boot. I had to make a few changes to the kernel source and device tree. Right now there is a high possibility the Camera and GPS will not work, and a 10% chance cellular connection will not work. I will install the ROM tomorrow, because it's very late right now. Wish me luck!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Recovery is working!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
The ROM flashed successfully but unfortunately, initlogo shows up and then it goes to download mode again, but I got the Kernel Logs and it looks like there are a few errors. It's looking for V-Sync stuff which is pretty hilarious. I searched the last errors and it looks like it's only happening in emulators, so I have been building for a generic device for all of this time, I am not sure if this is a kernel issue or a device tree issue, but I will ask some people about it. I am getting very close.

Kernel Logs: https://del.dog/imununomer.txt

Edit: It looks like vendor is not in the right place, so it's not able to pick up the files in vendor to continue the boot process so it shuts down and goes to download because it does not know what to do next, same thing what happened to the first recovery attempt, the init files were missing, so it went to download mode immediately.

Edit 2: Looks like the issue is the SEPolicy denials. I will build a fresh ROM with permissive and see if it works.

I have created an organization with all the device trees I am using here: https://github.com/Samsung-Galaxy-S3-MSM8960
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Now I got the notification LED blinking for 5 seconds before shutting down again and going to download mode. I am almost there. I built in permissive so I got rid of the SELinux errors.

Happy new year everyone, hopefully I will finally get Lineage 16.0 to at least boot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] palmbeach05:
nice job. just as an fyi, and you probably know this already, but official twrp has been broken since about 3.4.0 and is even more broken with 3.5.0. I'm going to try what i can with your trees to help bring that up, not that we really need anything more with pie roms, but still, that twrp tree is labeled ics, so its probably missing a lot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Yeah it's quite broken. For example the reboot or power off does not work. I don't even know if they are actually using the tree they have on Github as it is very old. Maybe you or we can restart official support (It's still official but it's broken) and have a fully functional recovery. If you want to "update" the tree, just make sure it's for omni instead of lineage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] palmbeach05:
Can you put up on your repo the msm8960-common repo you are using? I'm doing what i can from my end with updating, but i keep getting a fail with a recovery.img size of 11.7mb. its either that repo or something with the vendor. i'm not sure yet, but i think its the msm8960-common. I can upload what i've done later on tonight and post the links

Edit

GitHub - palmbeach05/android_device_samsung_d2att

Contribute to palmbeach05/android_device_samsung_d2att development by creating an account on GitHub.

github.com

GitHub - palmbeach05/android_device_samsung_d2-common

Contribute to palmbeach05/android_device_samsung_d2-common development by creating an account on GitHub.

github.com

GitHub - palmbeach05/android_device_samsung_msm8960-common

Contribute to palmbeach05/android_device_samsung_msm8960-common development by creating an account on GitHub.

github.com

GitHub - palmbeach05/android_vendor_samsung: proprietary_vendor_samsung

proprietary_vendor_samsung. Contribute to palmbeach05/android_vendor_samsung development by creating an account on GitHub.

github.com

prebuilt kernel added, but the problem seems to be ramdisk size related. they may not be full trees for rom building, but missing stuff can be added in at any time.

Edit 2 - 10.9 with d2att from your git, d2-common and msm8960-common from s3 git
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I haven't touched this device for a week so I have not built any recovery or made any progress with Lineage 16. By the logs it looks like there are some init files missing and Graphics issues (maybe). As for the recovery, I don't know but is it really necessary to include all of these trees only to build TWRP (d2att, d2-common, msm8960)? Reducing unnecessary stuff will lower the Image size. When building with ICS it was fine, but now when building with Omni 9, the size is larger. I invited you to the MSM8960 Samsung on Github if you wish to contribute to anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] palmbeach05:
I do have an update. I backed down to 7.1 minimal manifest and I did get it to build, exporting a roughly 7.3mb img, twrp 3.5.0_9-0. It works.

Issues so far (will update as needed)

- sd card labeled as storage 1, but does not mount Fixed

- double entries labeled storage Fixed

- brightness does not work despite max set to 255 Fixed (yes! we finally can adjust brightness in twrp!)

- tzdata flag not added (should be easy fix) Fixed

logs

dogbin - wirfoluper (del.dog)

I take a moment to remember the words of capt throwback (i think it was on tg). with each android revision, the size of twrp gets bigger. i want to fine tune this before pushing to the repo and before uploading the recovery here or to twrp. A good start to the new year!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chaseadam:
@alexenferman and @palmbeach05, seems like there was some progress. Can you chime in with any issues preventing further progress? Any updates (even if it is just a "moved on")?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I decided to come back to this project and continue from my previous progress.

There is nothing really preventing us from doing any more progress, I had a lot of other stuff to do, but I will surely continue as best as I can to finally get LOS 16 for this phone.

The new 16.0 device tree is ready and working, but what isn't is the kernel source. I could start fresh, using a CAF kernel but the newest release is for android 6. The best way to "Upgrade" the kernel source would be to cherrypick commits from similar msm8960 devices with L16 support (HTC One and Sony Xperia T, TX comes to mind).

I will let you guys know if I make any more progress.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JINKXS:
Bro as if right now, I am still waiting for a lineageos 16. I just hope it comes soon this year.
[Moto X Q&A] markd89:
Hi,

I've had my phone for 5 years. I seem to remember a keypad code to enter which would get into a programming mode where you can change the frequency that the phone polls the tower to see if there is a call coming in... but I don't remember.

*#*#4636#*#* gets to some settings but not that.

Can someone post other codes which work on the Moto-X 2013?

Thanks!

Mark
[Honor 8 Questions & Answers] Bistekka:
Hello,

yesterday for some reason that i don't remember i rebooted my Honor 8 with halogenOS 7.1.2 and from then it started bootlooping. i've tried to flash every rom and wipe everything but nothing other than bootlooping.

i've read that i can resolve, unbrick, my device flashing the stock firmware, but i don't now the build that i need to download. my device is an frd-l09, and i think it's the italian (or european version) but not so shure. Thanks to all that replies

EDIT: i've tried i think 10 firmwares starting with frd-l09 including ones downloaded from the italian honor site, is my device maybe a different model ? but i now it's an frd-l09 cause it's written on the back.
[Honor 8 Questions & Answers] Frau Son:
Did you try formatting your phone over fastboot?

I remember that it helped with my LG G6 when I softbricked it.
[Honor 8 Questions & Answers] renttudiktaattori:
when i formated my h8 in fastboot the bootloader went broken.
[Honor 9 Lite Questions & Answers] kpirnie:
Anyone know what these are?
[General Topics] gofawkurself:
Anyone have a link or know of a mobile browser that I can run on my home pc

I use remote desktop to tell my computer at home what to download while im gone and i think a mobile browser would work best.
[Shield Android TV General] illiam1:
Credit To Steel01

/sys/bus/his/drivers/hid-nvidia-blake/*/mode

The * is a folder named after the USB address of the plugged in or paired controller. It'll vary and there will be multiple if you have more than one plugged in. There are four modes supported:

disabled

absolute

gestures

mouse

again credit to Steel01 original post at:

https://xdaforums.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116/page6

I saved this little tidbit because it should have been standard on Shield just like the tablet. 199$ and I had to buy a mouse. lol

Unfortunetly the adjustment doesnt stick it goes back to normal. Someone Im sure can figure out a way to make is stick.
[Shield Android TV General] WisdomWolf:
When you say that it doesn't stick, I assume you mean after a reboot? Or does it just revert after an unspecified amount of time?
[Shield Android TV General] Steel01:
It'd be after anything that resets that usb port. So, controller going to sleep, unplugging/replugging, reboot, etc, etc. In theory someone could write an init script or something to auto set it, but that's not something I personally have much interest in doing. Especially I still haven't got them pairing properly on Lineage still...
[Shield Android TV General] illiam1:
Hey steel thanks for all your hard work on shield. This device really needs it to.
[Shield Android TV General] lohengrim93:
Unfortunately the changes are not saved to keep the touchpad activated on my NVIDIA shield controller 2015. If anyone knows how to keep it activated it would be very helpful for me and many people who ask this question.
[Shield Android TV General] ricflairandy:
Could you implelent a boot up script?
[Samsung Galaxy S9+ Questions & Answers] maverick629:
I was using the camera app and the front camera and I was moving around the phone and noticed these vertical streaks on the screen, only in front facing camera mode. It also does this in snapchat.

I have restarted my phone, reset the app data and cleared the cache.

Any ideas?

Thanks
[Samsung Galaxy S9+ Questions & Answers] twinh3ad:
Just noticed this happens to me too. Especially when the front camera facing bright sky
[Samsung Galaxy S9+ Questions & Answers] maverick629:
Hey so I actually returned my phone showed it to them and they gave me a new one. It is not software related (my issue) and was a loose connection it seemed. Try to return it and get a new one. Check in the store to see if it does the same thing.
[OnePlus 5T  Questions & Answers] colossus1958:
I bought this phone based on the overall web's assurance that it was one of the easiest phones to root. I found a guide in XDA that I thought would run me through the whole thing without problems. At first, this was true but as I went along everything fell apart. The posts on the web made it sound like the unlock code the bootloader was all you would need. I knew better than that but I still expected the simplicity I would need as a noob. If there aren't any phones like that please tell me. Also in the meantime I may have bricked my brand new OnePlus 5T. Irritating to say the least. Any ideas?
[OnePlus 5T  Questions & Answers] shadeau:
Compared to my Verizon Galaxy Note 4 this thing is a breeze to root. Here's a link to an un-bricking tool: https://xdaforums.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012

This thread pretty much has all instructions for unlocking your bootloader and rooting your 5T: https://xdaforums.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592

I haven't bricked my device yet so I can't speak for the first tool, but the guide is very well written.
[OnePlus 5T  Questions & Answers] colossus1958:
Yeah.. it wasn't quite as bricked as I thought LOL. Just an anxious noob probably. However, I am now running into a situation where the phone will not accept Magisk 16.0 and I would really like to go systemless if possible. I have flashed twrp-3.2.1. I hope that was at least correct.
[OnePlus 5T  Questions & Answers] Lossyx:
Flash either codeworkx or Blu spark twrp, then latest magisk version and you have root.
[OnePlus 5T  Questions & Answers] tbv2005:
Had the same problem with Magisk 16 not booting the phone. Flash Magisk 15.3 from twrp and once boited update from the magisk manager. Worked for me..
[OnePlus 5T  Questions & Answers] colossus1958:
Is it possible to flash one custom recovery over the top of another or do I have to go back to my stock recovery first.