yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] ChaosClown:
Volte is not working, it doesn't have INS(Indian version) CSC
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] danish3311:
Samsung account is not logging in.it says an error

Processing failed
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] jam24ph:
that's right man.. the smart capture and the screenrecording, also the performance mode on dropdown quickpanel

and also it would be very nice if sir mohit wil also add double tap to lock..??
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] danish3311:
GPS is not also working sometime.but its ok.

Why samsung account is not logging in
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] MarkusBurns507:
now everything works fine with the fix but now I have a problem the front flash does not work with other camera applications like cameraMX, simple camera, Fotooj. J710mn
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] :
Why don't you use samsung camera app?

It has a front flash.

---------- Post added at 11:01 PM ---------- Previous post was at 10:56 PM ----------

I can login to samsung account for me.
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] die or die:
I have a problem with finder i cant add shortcut hidden apss
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] UltraKi11:
BEST ROM FOR J7 2016!

great respect to author
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] danish3311:
Everything is working fine Thanks to the Mohit Sir.
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] umdasu:
First of all great rom. Everything I wanted my Samsung apps back on an oreo rom.

I am also having spotfy issues. Spotify will only play about first 10 seconds of a song.

Not sure if this is a rom issue but on mobile legends bang bang, there is no high fps mode available. All other 7.0 official Samsung roms don't have this issue. It may he game related but I'm not sure. Thanks again for the great work.

Sm-j710mn

Update: I have included log files sorry for the delay
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] AbboodSY:
Been using this rom for few hours and everything is working great, wifi, Bluetooth, mobile data, front flash, calling, samsung account and everything else is working as it should.

Huge thanks and respect to the developer of this rom.

J710F user.
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] mohitmallick17:
Thats not a rom issue. If you see, even the stock oreo updated devices don't have front flash working. Thats something samsung should work upon or 3rd party apps changing their pattern of using front flash.
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] umdasu:
Not trying to be a nuisance. Like I mentioned above there is a bug with Spotify. Since your last post you haven't acknowledged this issue.

I am also the second person to report on the bug. Funny how no one else is having this issue. I'm using j7 mn varient. I'm also including a log file

Ty
[Wear OS Software and Hacking General] JaredTamana:
Wear 24 Development​

Contributors: [MENTION=6382516]JaredTamana[/MENTION], [MENTION=5376493]davwheat[/MENTION]​

Current Status: Active​

Current Kernel Status: Building, NFC driver working but still potentially WIP​

System ROM Status: Still WIP. Current task: collecting/compiling files, modifying .jars​

THIS ROM IS NOT YET AVAILABLE TO DOWNLOAD AS AN END-USER ROM​

This project has a few goals:

- Bringing NFC/Google Pay support to Wear24 [Feasible, main goal]

- Bringing system updates to the Wear24, ie System H [Probably doable, second goal]

- Adding/fixing functionality in the Wear24 (such as new radio bands, no cloud icon, etc) [Maybe possible but needs more research, low on the list)

- Other projects are being considered for the Wear24, but no news on them at this time.

Links

Social

Wear24Dev Blog, periodic updates on this project: http://wear24dev.blogspot.com

Wear24 NFC Discord, open chat so users can see us develop in real-time! Also, tech support. https://discord.gg/8XyTeUC

Development

Wear24-NFC-Kernel GitHub, this is our source for building the kernel. Instructions for building it yourself are in the README. https://github.com/davwheat/Wear24-NFC-Kernel

Travis-CI Build Logs for Kernel: https://travis-ci.org/davwheat/Wear24-NFC-Kernel

Wear24-NFC-ROM GitHub, will soon contain the files needed to make an image/zip, depending on how we decide to distribute. https://github.com/davwheat/Wear24-NFC-ROM

JaredTamana's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/folders/1h6gz-oLMPZ90nwt7BLhWVgHii1DRCW5c

davwheat's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/fold...droid-msm-dorado-3.18-nougat-mr1-wear-release

tetra release for enabling NFC: https://xdaforums.com/smartwatch-3/orig-development/sony-smartwatch-3-nfc-support-package-t3219713

NXP Setup Guidelines: https://github.com/NXPNFCProject/NF...r/AN11762-Android_NXP_NFC_Setup_Guideline.pdf

Special Thanks

janjan: Dev guidance
[MENTION=408926]bensdeals[/MENTION]: Donor, help
[MENTION=4421624]yochan[/MENTION]marquos, u/lerxi: Development help.
[Wear OS Software and Hacking General] JaredTamana:
-- RESERVED -- Because you never know ;)
[Wear OS Software and Hacking General] bensdeals:
Someone should have a TWRP backup handy with the images you are looking for. Correct me if I'm wrong, but all the images you require are inside a TWRP backup image.
[Wear OS Software and Hacking General] JaredTamana:
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
[Wear OS Software and Hacking General] freelowdr:
Please. I beg you to make this happen. Thanks for even trying
[Wear OS Software and Hacking General] jpreston84:
I'm definitely interested in this. If I knew I could get Google Pay working on this device, I would definitely buy one. I'll happily throw a few dollars your way too, if you can release something that works. :)
[Wear OS Software and Hacking General] freelowdr:
Hoping I found it

Is this what you're looking for? (Sorry, I'm not allowed to post url yet so just remove space before .com)

github .com/FlorentRevest/android_device_sony_tetra

My Wear24 just came in from eBay . It's a really good looking device. I might be able to help you test at some stage. Also willing to donate ducats if you get far enough. Good Luck :good:
[Wear OS Software and Hacking General] YTSec:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
[Wear OS Software and Hacking General] JaredTamana:
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
[Wear OS Software and Hacking General] JaredTamana:
** NEWS **

Semi-daily updates will be going on this Blogger Page so I don't clog up the thread :)

http://wear24dev.blogspot.com
[Wear OS Software and Hacking General] Eshal:
Hi, can i flash this rom to zte quartz 2017?

Hi, can i flash this rom to zte quartz 2017?
[Wear OS Software and Hacking General] JaredTamana:
Eshal, this ROM hasn't even been built yet. I cannot guarantee compatibility with your device because I'm not building for your device. You can try flashing whatever you like, but I'm not liable for your device.

This ROM is still in its first steps and I quite literally have nothing to release yet. I've just finished bringing backups over to my PC.
[Wear OS Software and Hacking General] YTSec:
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
[Wear OS Software and Hacking General] JaredTamana:
Glad to hear it! Make sure to read the main thread as to tips on how to do it. Use lots of heat, and don't forget the Y000 (0.6) screwdriver.
[Wear OS Software and Hacking General] JaredTamana:
Kernel builds are now passing, and I've begun debugging the boot process. More info on the Blogspot :)
[Wear OS Software and Hacking General] YTSec:
Sorry for the late reply, I'm just waiting on a toolkit that works on it, then I'll start ripping it apart to help out! Also, I got that new UI which is great.
[Wear OS Software and Hacking General] VlitalityX:
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well :)
[Wear OS Software and Hacking General] yochananmarqos:
[MENTION=6382516]JaredTamana[/MENTION] Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS

Here's their GitHub.
[Wear OS Software and Hacking General] JaredTamana:
Hiya! Sorry for the lack of updates. I've hit a wall with that Binder error. All documentation online seems to be about x86 machines and ranges from IO errors to SELinux errors. I've already tried compiling without SELinux in a few different ways to no avail. I've tried contacting development channels on IRC, but no one seems to have the answers I need (most times I don't even get a reply...)

I'm still brainstorming. I took a look at the kmsg from the stock build and there's a LOT being sent to logs there that isn't from my kernel. I'm not sure where to go next, and I don't want to go knocking on the door of every single developer that might know the answer. The problem is the Binder errors are so vague about what's causing the failed transaction that I can't even start to understand what's wrong.
[Wear OS Software and Hacking General] JaredTamana:
Thanks! I do remember seeing this. Problem is, if I can't even build a stock kernel, nothing else can be done. I need the device booting first before I can move to system changes.
[Wear OS Software and Hacking General] dave737ng:
Anything going on?

There hasn't been any activity on this thread or on the blog for almost a month and a half. Is the project dead or is it simply on hold?
[Wear OS Software and Hacking General] JaredTamana:
Hey. As of right now, project is on hold indefinitely. I'm looking for developers who better know about these issues, both in person and online. If anyone here is willing to take a look at what's going on here, I'd love to hear from them.

Until the kernel boots, nothing can happen. I don't know enough to build a kernel for this device from scratch, and Quanta's kernel refuses to boot for me due to a binder error. It makes me think either my build environment is screwed, or Quanta didn't upload the correct files, and while the former seems more likely, I think the latter is true.

I haven't looked at it since December, but I'm going to give another look over the logs tonight, maybe try a new build or something. Anything to get variable results.
[Wear OS Software and Hacking General] Charmandrigo:
I have hopes, nothing is impossible with Snapdragon SoC devices, so maybe in a near future maybe a Pie (H Update) rom from another Snapdragon 2100 watch can be ported
[Wear OS Software and Hacking General] davwheat:
Wow. I didn't realise this thread was active -- I thought it was dead like all the others.

My Wear 24 is in the UK post at the moment (bought off of eBay). I'd love to use it for Android Pay and I have some experience with programming so maybe we could get this working?
[Wear OS Software and Hacking General] JaredTamana:
Potentially -- would you be able to sync the code to your machine and try a build? If someone else is able to get farther than me in terms of boot, that means something would be wrong with my build environment. Since you don't have your watch right now, you could shoot me the image if you manage to get it building.

It's not that simple. No kernel, no boot. The ROM isn't the issue right now.
[Wear OS Software and Hacking General] davwheat:
I'd happily give it a go! Send me the code!

My watch just arrived in the post, but I don't feel comfortable taking mine apart just yet because I want to try using it first.

If you already have yours taken apart and a usb 'cable' attached, then if I manage to get it to build I'll send you an image.
[Wear OS Software and Hacking General] JaredTamana:
Google Source: https://android.googlesource.com/kernel/msm.git/+/android-msm-dorado-3.18-nougat-mr1-wear-release

You'll also need mkorenko's TWRP: https://github.com/mkorenko/android_device_quanta_dorado
[Wear OS Software and Hacking General] davwheat:
So all I need to do is build the kernel from the Google Source? No NFC drivers yet or are they included?

====

EDIT: Looks like I've almost got it working! Fingers crossed! I'm starting the kernel build... now!
[Wear OS Software and Hacking General] davwheat:
Kernel is building... don't know if it will succeed or not...

=========

EDIT: And it failed.... I was using the msm8909w-perf_defconfig config file to build.
[Wear OS Software and Hacking General] dgdeepak000:
Looks good

That looks good.
[Wear OS Software and Hacking General] JaredTamana:
Sorry for the late reply! Use the omni_dorado defconfig from mkorenko's TWRP repository. I remember trying to use a default 8909w config and getting nowhere.
[Wear OS Software and Hacking General] davwheat:
I'll try that now. Also made a Discord group for anyone interested: https://discord.gg/8XyTeUC
[Wear OS Software and Hacking General] JaredTamana:
New Image

New build attempt. Finally, got the actual source to build with some tweaks and help from davwheat. And would you look at that -- it's our old arch nemesis, the Android Binder.

Any kernel devs out there able to help us diagnose this one? https://pastebin.com/qezstBmq

Boot image:https://drive.google.com/open?id=1lwiEpHBHFZwWtZEovth1nsiDj6jhpABN. Don't flash it without a backup obviously -- your watch WILL soft-brick.
[Wear OS Software and Hacking General] bensdeals:
Does this help? Same exact error

https://community.nxp.com/thread/489034

---------- Post added at 03:25 PM ---------- Previous post was at 03:14 PM ----------

Well sorry, was on the road. Not exactly the same, close. Let's see what we can do to get more Dev eyes on this to help you out.
[Wear OS Software and Hacking General] dave737ng:
How is this going to work?

Sorry I am a bit unexperienced with flashing roms on watches. I was wondering when it will be done, if there will be any way we are going to be able to flash this thru WiFi or Bluetooth or will we have to open the watch in order to connect it to a usb interface?
[Wear OS Software and Hacking General] Charmandrigo:
It's impossible to use fastboot mode or recovery adb without a direct USB connection to the computer.
[Wear OS Software and Hacking General] sandy8925:
I don't think it's the binder that's the problem, if you look right before the binder errors, you'll see error messages about being unable to load some files, and /data being read-only. I think that's the actual problem.
[Wear OS Software and Hacking General] JaredTamana:
Working on revamping this thread! In the meantime... We have builds FINALLY BOOTING from source. Big thanks to [MENTION=490110]janjan[/MENTION] for repacking our images (PM sent asking for more info on that..)

Next step is to add the NFC components into /system and do some testing. I don't think NFC is registered as a service right now, but I don't know if NFC modules are building into our kernel properly as of now. We have a few points of potential failure and we're going to have to figure out a debugging process.
[Wear OS Software and Hacking General] MIDHUN.V.NADH:
Thanks !.

I am requesting you to make the same for Z4 Smartwatch
[Wear OS Software and Hacking General] JaredTamana:
lol, no. We don't own that smartwatch and have enough on our plate with this one alone. I don't even know of that watch.

In other news, we are asking anyone familiar with building sparse images to shoot us a message. We're getting some SELinux permissions errors that shouldn't be happening.
[Wear OS Software and Hacking General] LidaFlorida:
Hey. Is there any good news after a month?
[Wear OS Software and Hacking General] klewisjohnson:
Just wondering if anyone is still working on getting this going? Just tried compiling but got about same errors? Hope its not dead cause I would really like to use nfc as price of these is just unbeatable! Thanks
[Wear OS Software and Hacking General] qkall:
I'm willing to ship my watch to whomever to help move this project along. Ya just have to pay for shipping.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] MyZ:
Hi All,

I'm new to the PDA-world and the Hermes. I'm trying to Hard SPL my Hermes, but it fails everytime.

When I run 2.10 - Hard-SPL-V7, it kills activesync and my connection is lost and I get always the message "error 260, Update error".

I have the latest framework edition and tried it on 3 pc's (1 Vista, 2 XP)...

What am I doing wrong?

Hope somebody can help me....

Kind Regards,

Micha
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ultramag69:
1). dont connect to active sync. open active sync and untick "allow usb connections".

2). put hermes into bootloader and connect to usb.

3). run ruu_wrapper.exe

should update to hard spl....

dont forget to tick "allow usb connections" again or you wnot be able to sync..

error 260 is an open port error.

if you wish to flash new os would advise to use sd card method. its safer than using the computer. just make sure you have greater than 50% battery power. happy flashing
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] MyZ:
Thnx, will give it a try.

First I have to flash HardSPL before I can flash a new OS, don't I?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ultramag69:
yep, sorry, should have said run the ruu_wrapper for hard spl. My bad...:p
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] IpodLover77:
im having the same problem. I also tried the way ultramag recommended but i also received the same ending. After time i try i get the Error 260 Update error. Im running SPL 2.04 and the HTC WM6 rom from the HTC website. Does any one know what the problem is?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
NOOOOO, that won't work, you need the SSPL to deploy to the phone, if you're running stock HTC bootloader this won't work at all, otherwise we'd have no need for Hard-SPL
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] IpodLover77:
hey olipro, then how would i fix this. Im running the stock rom from the HTC website with no hacks. Im trying to load PDA Corners V9 rom. Any ideas on how to fix? thanks!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mrvanx:
Take a peek at the guide i wrote about updating the hardspl. Theres some explanation about why we need to use SSPL and the procedures.

http://www.mrvanx.org/hermes_guide/hardspl
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] IpodLover77:
thats the guide i used. it still gives me the error. I even unchecked "allow connections" cause i read somewhere that that would help.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] st3v3:
i did this two days ago on my phone, im running windows vista on my home laptop and got any number of errors and problems trying to do it via sync with the phone (even after reading the vista troubleshooter, with the drivers etc)

What i ended up using was the memory card upgrade, dump the file onto the memory card and go into bootloader with the card installed.

worked fine doing that way, maybe less risky as there is no chance of the usb cable coming out.

just make sure you have a good battery charge on the phone.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] blackdog9692:
Help Help Help w bricked 8525

I got into this position trying to upgrade WM5 to WM6 from HTC site.

Process got to 20% and just stayed there.

I reconnected usb cable and got a vendor id error

Then I get the Error [260]: CONNECTION

I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.

I believe this is the bootloader? I have downloaded RUU_signed.nbh, renamed it to hermimg.nbh, installed on root of my SD card and held OK, soft reset and power button:

My display reads:

HERM100

IPL-1.04

HERM100

SPL-2.03

This is where my journey ends.

All post indicate that the device can be reflashed and have the OS reinstalled. I can't get there from here.

Can anyone please help?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] brownianmotion:
How big is your SD card? Flashing only works with cards <2GB. Also, sometimes certain cards just don't work for flashing, and just swapping to a different card fixes the problem.

I assume you searched the wiki, and found the relevant pages on the Hermes (including SD Card Flashing and other things about flashing/upgrading) there?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] blackdog9692:
Still Lost

My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen. When i attempt to flash the rom via PC to WM5 or WM6 i get the Error 260, i also get a vendor ID error sometimes.

How can i find the key 8525 thread that i am told has the answer to my delima? I keep picking up bits and pieces but am missing some key steps and tips.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jdc:
That sounds like the SD card is formatted incorrectly. Make sure it's formatted using fat32, nothing else will work.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] blackdog9692:
Still not there from here

Thanks for your help. Before I formatted the SD FAT32, nothing would happen doing the bootloader reset. OK/ON/reset button.

After format and only the hermimg.nbh file renamed as indicated, I then get what looks like the loading process but back to the bootloader screen.

Q1: This is an AT&T 8525, it was perfectly fine before failure from WM5 to WM6 (process froze at 20%), what is the RUU file that I need to put on SD??

Q2: After "Loading ..." I try the WM5 PC upgrade of ROM via USB cable, I get the load process to appear to work but it gets to 1% and the phone reboots and the PC reports error [294]: Invalid vendor ID. If I do this again I will get the Error [260]. Ive repeated the process several times.

Is this the normal course to take or should the "SD Method" (with the WM5 or WM6 RUU.. file) complete the process to a working OS?

Q3: Is my situation hopeless? ATT will take my out of warrantee 8525 and reflash for $129. Reading the threads it seems that like me this can be done by me, this is my desire.

Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.

The newbe guide has been off line. I will look again. Is there a single place to read about "radio PDAs and the 8525 and understand the software build and custom options?

Sy for the long post. But still want to fix if possible or I will be force to mail in for ATT repair.

Thank you all.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jdc:
Oh boy, you haven't installed HardSPL? You are walking a bit of a line there mate...

HardSPL is a custom boot loader that makes bricking your phone when flashing much harder to do, and helps large amounts in the recovery process if you phone does brick.

Does the phone boot at this point? If so, do not try flashing the phone again. Go get a copy of HardSPL and install it, then try flashing from the SD.