yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
Your device is still showing 'custom' status.

I suggest re-installing the stock firmware and factory reset.

It should state 'official'
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
Tried it twice, and it's still stating a 'custom' status.

Is there a way to downgrade it to Nougat? Cuz it seems this is a common thing with Oreo. (Losing the stock factory I mean).
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
What is the current firmware build you have installed?
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
Not sure what that is or how to check it. I used the firmware you suggested: (screenshot below)
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
This is the only one I can see that would possibly allow downgrade to nougat :

https://updato.com/firmware-archive-select-model?record=2AC8148EBFDC11E89F15FA163EE8F90B
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
Thanks for the link. It's installed successfully but the phone is stuck in a rebooting loop. I can access the download mode in which it still states: "system status: custom"

And I can access the stock recovery. Which says in the bottom left corner:

No support SINGLE-SKU

Supported API: 3

dm-verity error

Failed code: 0×02

E: failed to find /misc partition.

---------------------------

Can I unlock the OEM through ADB or sideload? In order to flash a custom recovery.

Or is there a better course of actions?
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
You need to factory reset after downgrading.

Is this device a carrier branded model?

System should not be custom after installing official firmware.

No way to oem unlock unless booted.

You will continue to get the FRP error until system is official.

Where was this device purchased?

I suggest using Smartswitch to install the correct firmware.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
I did apply a factory reset right after downgrading it, and it was successful yet followed with

"E: failed to find /misc partition"

And the device isn't carrier branded as far as I know.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
It's a 2nd hand device that came from France I believe.

I'll look into SmartSwitch, even though I don't know what it is :D
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
The Smart Switch says my device isn't supported !! (I connected it in download mode)
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
It always says that. Make sure you put it your device details in caps.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
Where exactly do I put in the details? (screenshot included)
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
It looks like it's changed.

You can still Download Samsung KIES which supports Update and initialization using your model number and serial.

Whether it will support your device I don't know.

Tbh I don't use either Smartswitch or KIES as I hate them both with a passion as they are both pretty useless!:rolleyes:

Edit: sorry wrong thread.

The link below is for the combination firmware (basically an engineering firmware)

This should bypass all the DRK and FRP errors. If it boots to the OS maybe it will fix the custom status.

https://androidfilehost.com/?fid=1322778262904016659

PLEASE NOTE: IT WILL LIKELY WIPE YOUR INTERNAL STORAGE!
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
Flashed it successfully. Got the factory binary up and running. Still snooping around (this is all new to me) but I don't seem to find the "OEM unlock" option in the developer options !

I did though perform a factory reset from within the settings, which seems to have fixed the "custom status" problem. It's now "official". But neither nougat nor Oreo loaded the OS ?.

I'm now back in the factory binary.
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
Restore the entire stock Nougat firmware then factory reset.

Pull the boot.img from the combo firmware then repack it to tar.

Flash it with ODIN in the AP slot.

This hopefully will allow it to boot to the OS as the boot.img has dmverity disabled.

Be mindful of the fact that it can take up to 10 mins for the device to boot after a factory reset.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
It took some flashing and reflashing to finally get Nougat with drk problem and official status.

Got to recovery (w/DM verity error) performed a factory reset.

Flashed after that boot.tar pulled from the combination ROM but it didn't seem to affect the device.

Trying to start the device now just gets me to a recovery mode with a dm verity error ?
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
Are you certain it was boot.img and not sboot.bin you flashed?

Dm-verity relates to wrong or modified firmware.

The combo boot binary has dmverity disabled so should bypass this.

You could try flashing sboot.bin also.

You really need to find the correct stock firmware for this device.

---------- Post added at 03:26 PM ---------- Previous post was at 03:15 PM ----------

Are you certain it was boot.img and not sboot.bin you flashed?

Dm-verity relates to wrong or modified firmware.

The combo boot binary has dmverity disabled so should bypass this.

You could try flashing sboot.bin also.

You really need to find the correct stock firmware for this device.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
So here is exactly what I did:

1- remove ".md5" from the AP file name.

2- Extract it into a folder.

3- Pack "boot.img" into a boot.tar file using Peazip.

4- Open up Odin.

5- Put "boot.tar" in the AP slot.

6- Flash it.

---------------------------------------------

I'll try with sboot as well.

Oh and I tried SmartSwitch again "seeing how the phone status is official now" but it"s still not supported.

Is there another way to find out the correct stock firmware?
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
Seems like you did everything right.

Have you tried to just install everything stock now and see if it's any different now that system is official?

If you can get root with Nougat then this will bypass dmverity and DRK and should allow it to boot as long as FRP doesn't stop you.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
I'll look into rooting the device.

I would like to know though, just to try other firmwares, did you base your suggestion on the "U3" in the firmware name?
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
You won be able to flash anything above U3.

If you can help it don't flash anything above U3 or you'll be locked to that firmware.
[Samsung Galaxy J7 (2017) Questions & Answers] HiSham1d2:
So, the problem is solved lol

I got frustrated with the device, so I started flashing everything I got.

And what solved it was basically (the combination rom + The "AP" file from the nougat Iraqi firmware).

And now I gotta delve into bypassing the FRP.

Thank you so much [MENTION=4899305]ashyx[/MENTION] for your patience and help
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
Good news. :good:
[Xperia Z5 Compact Android Development] trancazo71:
Thank you..!!!.... :good:
[Xperia Z5 Compact Android Development] trancazo71:
bluetooth does not work on my device. Otherwise, incredibly smooth.
[Xperia Z5 Compact Android Development] Sony user 16:
I will look in to it. What Bluetooth thing did you try to connect to?
[Xperia Z5 Compact Android Development] trancazo71:
the short characters is new .... hahaha, it has been when selecting the English language or when recovering the nandroid without wipe.

I will do a format before trying again.
[Xperia Z5 Compact Android Development] trancazo71:
I know it was not necessary but, install clean, all wipes and the result is the same.

the bluetooth switch is dark, I have limited the permissions of the application and the result is the same as all the permits granted or denied.:(
[Xperia Z5 Compact Android Development] trancazo71:
I have recovered the boot.img of lineageos 14.1 and I have flashed it on AEX, the result is a nice animation of endless AEX.

Personally AEX is the rom development that I have used in all my devices for its smoothness and custom settings.

Do not stop trying, Suzuran is a great device that is being forgotten by all developers. I'm waiting for Mokee to work on 8.1 for Z5 compact, but I have no hope that it will happen.
[Xperia Z5 Compact Android Development] Sony user 16:
Why did you flash the lineage 14.1 boot.img? my AEX build is based on that one.

I'm trying to fix the Bluetooth issue right now. Is there any more errors?
[Xperia Z5 Compact Android Development] brordavid:
My fault. I suggested that. :)

I thought it was worth a try. :)
[Xperia Z5 Compact Android Development] trancazo71:
I just dropped the z5 compact ... I know you do not care, but I say goodbye to the forum :( is the third z3-z5 that bursts the screen with a slight fall.
[Xperia Z5 Compact Android Development] Sony user 16:
Sad to hear, hope you find another good device that fit your needs.
[Xperia Z5 Compact Android Development] trancazo71:
Tnx..!!! Something tired limited development Sony. Waiting for an S7 auction for daily use and pocof1 to toast rooms. Jijiji
[Xperia Z5 Compact Android Development] RisingNoob:
Anyone still using this ROM? Any better than stock?
[Xperia Z5 Compact Android Development] Sony user 16:
I don't know how many who are using my ROM. But I would say that this ROM in performance is like the official lineage build but with out Bluetooth and latest security patch( I'm working on it right now I'm on 2018-08-05 but I am not going to realise it untill its 2019-02-05).
[Xperia Z5 Compact Android Development] RisingNoob:
Lineage is often better than stock ROM in performance. But I can't live without bluetooth. Gonna wait for the next build, then...

Does it have voltage control? Snap 810 needs it.

What about temps?

Thanks for your work, with proper development the Z5c can live well. Better then most new low/mid devices.
[Xperia Z5 Compact Android Development] Sony user 16:
The ROM is based on Lineage OS kernel and it keeps the phone in the same temperature as if you would use lineage(much cooler then stock).

Thx, me my self I own a OnePlus 6. But sometimes I miss my Z5C(I use it as a backup phone). It's a really good phone. And it's really hard to find something that good in that form factor.

I don't know when Bluetooth would be fixed beacuse I don't know how to fix it.
[Xperia Z5 Compact Android Development] RisingNoob:
That's great, Snap 810 were really bad with temps. Unfotunately I use BT daily with speaker and car stereo. Then I'm gonna wait.

I have a Mi 5s with broken screen, so bought the Z5 Compact. Once a fix my Xaomi gonna keep the Z5c as backup and play around.

Whoe!!! OP6 from a Z5c is a great upgrade in hardware and size. I can't have big phones, doesn't work for me. The limit is 150x70 mm, always try bigger ones from friends with no success.
[Xperia Z5 Compact Android Development] RisingNoob:
Have you considered a XZ1 Compact or XZ2 Compact at the time you bought the OP6? I like both of them...
[Xperia Z5 Compact Android Development] Sony user 16:
Back then when I bought my OP6 did I not think about the Sony phones. Somehow did they go under my radar. So I did not do much research about the Sony phones. But I think they are pretty good, I hear alot of good reviews.

But actually do I not see so much difference in the OP6 and Z5C performance. I know that the OP6 is much faster on paper. But in regular use googling, watching yt, scrolling through apps and even light gaming are there almost no difference. The only downsides I can see is the ram and battery life (and Android version, I really would like to have 9.0 on it but I know that it's hard to build).
[Xperia Z5 Compact Android Development] RisingNoob:
I hear you, Sony phones have gone under the radar for many people. It's hard to get back on the radar, now with new devices in 2019 it seems Sony is gonna make it and I really hope so. Xperia 1 is very beautiful. Pity it does not have a Compact device of it's own...

Here in Brazil Sony phones are hard to find, pretty expensive with no discounts. Hard to buy in these conditions.
[Xperia Z5 Compact Android Development] RisingNoob:
Are you aware of the WiFi issues with Sony devices? The Z5 Compact I bought has this issue where is keeps looking for WiFi networks but never find any. Can it be fixed with the custom ROM?
[Xperia Z5 Compact Android Development] Sony user 16:
I have not encounter any wifi problems on my z5c. But the wifi problems should be related to the device source code and for this ROM they are based on lineage. So you can expect the same as with lineage.
[Xperia Z5 Compact Android Development] RisingNoob:
My Z5 Compact simply do not finds my home WiFi, I read that it has to do with some protocol introduced on Android 6. On Android 7.1 (that I have) they took out the option to toggle "Use Legacy DHCP" on developer options that seems to solve the issue.

Here at work it detects the WiFi but still didn't connect.

Forgot how was to use a phone this small, so confortable and easy. Reach every corner of the screen.

Thanks for the answer, gonna search on Lineage OS topic for more details.
[Xperia Z5 Compact Android Development] brordavid:
How is the development going? :)
[Xperia Z5 Compact Android Development] Sony user 16:
I had much things going on in my personal life and had to take a small break from the development. But soon there will be a update with latest critical security patches (2019 march).
[Xperia Z5 Compact Android Development] :
Another thing that's not working: Half the cpu cores

edit: also there is a huge gap beetween lockscreen clock and notifications

+ pocket detection doesen't work

Overall, great rom!

If all the major issues get solved it will become my daily driver for sure
[Xperia Z5 Compact Android Development] Sony user 16:
Thanks for the reports. I will see what I can do. Seems like the core problem is pretty critical.

I am upgrading my setup right now(to ssd). So there will be a delay of updates.
[Xperia Z5 Compact Android Development] :
Another bug: if you make a screenshot and then click "edit" on the notification, the markup tool comes up. But you can't cut (this works fine on resurrection remix)

also, one bug i reported earlier was my mistake. The gap was because of the weather option that was enabled but not working.

Yup another bug: The weather doesen't work. But that also didn't work on my older resurrection remix. I don't think it can be fixed, OpenWeatherMap changed some stuff and yahoo weather doesen't exist anymore.

For the rest: even with the big cores missing, it's extremely fast and smooth. And you get tons of free ram, This can become the best rom for this device very easily

Edit: another very big issue: Substratum only works in legacy mode, this version of aex should have full oms support instead

Edit 2: Ambient display doesen't work
[Xperia Z5 Compact Android Development] :
That's not a bug

You selected English (XA) instead of English (USA) or English (UK)
[Xperia Z5 Compact Android Development] Sony user 16:
I have no idea how to fix the screenshot bug but is it possible to cut in another app?

The weather app that is integrated into the ROM is OmniJaws which uses Yahoo weather, So that may explain why it not works.

I am having problems with getting substratum to work. The problem is that aex source files are pointing to a GitHub directory. But the n7x branch has been deleted...

<project path="external/google" name="AOSIP/platform_external_google" remote="github" revision="n7x" />

https://github.com/AOSiP/platform_external_google

I have to look into the Ambient display problem, but me my self does not use this feature because of that this device does not have an amoled display.
[Xperia Z5 Compact Android Development] Sony user 16:
New update!

2019-04-08

Change log;

-Updated critical security patches to 2019-02-05
[Xperia Z5 Compact Android Development] Sony user 16:
Another update,

Testing only!!!

The ROM file can be found in "Substratum(Experimental)" folder in both mega and gdrive. Substratum may work but I need more testing:)

2019-04-09

Changelog:

-Implementing external_google(for substratum support)
[Xperia Z5 Compact Android Development] Sony user 16:
After some research did I find out that its a power saving feature for idling implemented in the los kernel. When the cores are needed they are going to be activated.
[Xperia Z5 Compact Android Development] :
That's how eveet single kernel works.

The problem isn't that the big cores aren't always active, the problem is that they don't exist.

During my 30 minutes of testing, they never appeared
[Xperia Z5 Compact Android Development] Sony user 16:
Interesting, which app did you use?

During my testing where I able to see how the "offline" state switched between the big cores when idling. But when I started a game. All of them was active(after some time).

I use kernel adiutor to measure and was running the substratum test build.
[Xperia Z5 Compact Android Development] :
I only used the pre-installed apps.

As you can see from the screenshots, in resurrection remix the big cores are present, but marked as "offline"

on your aex build, they simply aren't there
[Xperia Z5 Compact Android Development] brordavid:
Nice to hear that you are getting there, almost just the Bluetooth issue left. :) :good:
[Xperia Z5 Compact Android Development] :
What if you teamed up with Berni-0815 to fix the bugs?

He is the best dev in the scene
[Xperia Z5 Compact Android Development] :
Just tried the new build

And i have good news!

1) Substratum oms works without issues (so far)

2) all the cores are working (but they don't show up when you enable "show cpu information" in developer settings)

3) the cropping issue with screenshots disappeared

a new issue i have experienced is that when 2 or more notifications are on the screen the status bar refuses to go up when you scroll from the right side of the screen (i have a video but can't directly post to xda, maybe i'll upload to youtube if needed)
[Xperia Z5 Compact Android Development] Sony user 16:
Yea he are amazing with his development and what he have achieved. And I actually asked him some questions when I started this build. I can try to get in contact with him, but unfortunately I think he have much things to do with he's own builds.

1. Good!, please report if you discover any bugs.

2. I have to look in to which proces are handling the show CPU information and fix it. Tho I will not priorities it high.

3. Please share the video so I can see what's wrong.
[Xperia Z5 Compact Android Development] :
https://youtu.be/OfOQLCtpwkU

Btw don't even think about the little bugs, they aren't worth fixing

Edit: apparently the screenshot cut bug didn't get fixed, it sometimes works and sometimes doesen't

Edit 2: Touchscreen High Sensitivity (also called glove mode i think) is missing from the Display menu

Edit 3: The screenshot cropping bug can be fixed after every boot up by restarting the system ui
[Xperia Z5 Compact Android Development] Sony user 16:
Of course do I think about the small bugs. They are one thing that complete the ROM. But I will prioritize the bigger ones first, right now bluetooth. The screenshot problem do I not know how to fix. Is it possible to log cat the problem?

Isn't the high sensitivity mode Sony proprietary?

Is it in the lineage build?
[Xperia Z5 Compact Android Development] :
If i remember correctly it is, it's also in the resurrection remix rom

It's not a proprietary feature, many phones have it and always works the same way.

Btw this rom just became the one i use daily, it's fast, stable and it has good battery life. The best rom i have used so far, Thanks for your work
[Xperia Z5 Compact Android Development] :
I think i found something!

When starting the editor this is what appears in the logcat:

BitmapFactory: Unable to decode stream: java.io.FileNotFoundException: /storage/emulated/0/Pictures/Screenshots/Screenshot_20190414-224851.png (No such file or directory)

From what i understand, it's like the editor doesen't find the picture (in fact, you can see right through it).

And yes, the picture is captured properly and saved with the same exact name the editor is searching for

Strange that after rebooting the system ui it works properly

---------- Post added at 10:20 PM ---------- Previous post was at 09:50 PM ----------

2 Other minor bugs:

1) Manual brightness set at minimum is brighter than Automatic brightness set at minimum

2) Sometimes when switching from Automatic to manual brightness or viceversa, the quick setting icons "refresh"

(Also the switch is very hard to hit, and that could be related to the same problem)

Video: www.youtube.com/watch?v=Q_YBd8cVWtA
[Xperia Z5 Compact Android Development] Sony user 16:
I found some interesting things about the high touch sensitivity mode in the lineage os git. So I may be able to fix it... But I will prioritize Bluetooth.

Nice to hear:good:

if you use it daily you might be able to find small minor problems

I saw in the device tree some brightness related stuff I will see if I can find more information...

As I have said before am I not an experienced developer so I have to do more research about the screenshot and switching brightness problems. But maybe, can figure something out. But it will take time...
[Xperia Z5 Compact Android Development] :
I am using it daily, it's been 3 smooth days, the tons of issues i have reported are extremely minor and you don't even notice them very much.

You really did da great job with this rom, Coming from the buggy and laggy RR this is waaaaay better.

I have noticed many roms messing this up, i remember Berni's lineage didn't have this issue.

Still keep in mind that it's another very low priority issue, and for not being an experienced developer i love your determination at wanting to correct every little detail :good:
[Xperia Z5 Compact Android Development] :
A major bug: when enabling WiFi hotspot, it remains on "activation" (but it's still visible to other devices and you can connect to it) and when you disable it the notification for connected devices remains untill a reboot.

USB thetering works though
[Xperia Z5 Compact Android Development] Vaisjani:
Thanks for the work. I got this rom installed few days ago. It works very smooth. Same bugs mentioned before, weather app wont work, bluetooth keeps crashing, hotspot bug came to me also. Its an awesome rom, first one I got working on my z5c. Hope to see bluetooth working soon. Keep up the good work!
[Xperia Z5 Compact Android Development] :
Any update on the development?
[Xperia Z5 Compact Android Development] Sony user 16:
I am having a hard time trying to solve the Bluetooth problem but a security patch update will come soon...
[Xperia Z5 Compact Android Development] Sony user 16:
Thanks,

I am trying to fix the small bugs to:)
[Xperia Z5 Compact Android Development] :
Did you read about the Wifi Thetering issue? it should be added to the list.

Also, would you be able to add features such as kcal drivers to the kernel? I am starting to miss them
[Xperia Z5 Compact Android Development] Proker57:
The only quckfix of bluetooth i know is

at first install XPower5.0 ROM and then install AOSP
[Xperia Z5 Compact Android Development] Sony user 16:
Yea I read about the WIFI Tethering problem. I have not personally been able to test the issue but when I get time I will add it to the list (I have much things todo;))

I read a bit more about the kcal feature and implementation and it seems possible to add. But as usual... I will prioritize the Bluetooth issue first.

Does it work with this rom?

Tho do I don't think that it will work because the rom files and device trees are very different.
[Xperia Z5 Compact Android Development] Sony user 16:
New update!

2019-05-12

Change log;

-Updated critical security patches to 2019-04-05

Info

I am still working on the Bluetooth issue and all the other small bugs... And now am I in contact with Berni-0815 so if he has time we might be able to figure something out.
[Xperia Z5 Compact Android Development] :
What's this menu for?

It wasn't in the old build