yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend Mate 2] MikeyLee:
Thanks for the suggestion. I may do that later on. As of right now I have Location Services and com.qualcomm.location frozen with SD Maid and it's fine for now. WHen I have more time I'll do another back up and try Linage and see how it is
[Huawei Ascend Mate 2] Bratzilla:
If I'm not mistaken, Lineage IS CM. IIRC CM was "retired" and became (was branded) Lineage officially starting with version 14.1.

Make a full TWRP backup first, of course, but I think you can safely dirty flash LOS 14.1 over 14.1. That's how I upgraded.
[Huawei Ascend Mate 2] dkblue:
VWsy au tx,,qawwwwwwwwweaaaaAaT@XZZz
[Huawei Ascend Mate 2] EndlessFall:
Thought it was obvious to most XDA users that LOS is the successor to CM. My reference to a "source code connection" says enough. Erm... why do you think they chose to call it "lineage" (look up the definition of the word). Besides, the point wasn't whether you could dirty flash, but whether you should.

On the topic of LineageOS: MDMower's 09/22 build was just released, grateful that it includes Sept security patch. With critical vulnerabilities such as BlueBorne, this security update is one of the most important in a long time... but don't take my word for it:

https://www.xda-developers.com/android-security-bulletin-september/
[Huawei Ascend Mate 2] divhandyman:
Thanks for the Heads Up on the new release.:good:
[Huawei Ascend Mate 2] divhandyman:
Thank You MDMower for keeping us up to date on our Devices. :D
[Huawei Ascend Mate 2] Orzmud:
Great! I was one of those impacted by the boot loop. Was previously using Lineage OS from 201703 and upgraded to the unofficial release from MDMower 9/22. So far is working fine.

Thanks everyone for finding the workaround and for integrating it into the build.
[Huawei Ascend Mate 2] Orzmud:
Update: The boot loop came back after a week of regular usage (MDMower 9/22 release with recent GApps), did this happened to others as well? It was working just fine and one day around 11AM it started re booting by itself, then the boot loop happened, tried to go into recovery without avail. I left it connected the whole night that day and tried to go to recovery the next day, nothing! I put the phone off into my desk and started using an Oukitel U8 as a temporal replacement for the last week.

Last night I was planning to spend some time trying to find another alternative to revive the phone and put the MT2L03 to charge, while connected to the power supply the phone kept turning on and as soon as the Huaweii logo showed on the screen it kept rebooting, attempting to access recovery was futile.

I then disconnected the phone USB cable from the power adapter and connected it to a USB port in my laptop. To my SURPRISE... the phone went into booting normally... WWTTFF???? I kept the phone connected on USB to my laptop and attempted multiple reboots, all attempts the phone booted fine without any problem. Since it was off for little more than a week, a few apps were due for update and I went ahead with all the updated, rebooted after that and is still working.

Has anyone experienced the bootlop after using MDMower 9/22 release?

I have not inserted the SIM card that I'm using on the Oukitel U8 back into the MT2L03 just because I don't want to be without phone in case this bootloop came back.

I'll keep monitoring the MT2L03 phone and forcing reboots for another week.

Also, since I was looking for another route to revive the phone, I found that MDMower has made a few other releases, the latest one being 20171024. I have not tried that update yet, but wanted to let others know just in case.

Cheers!
[Huawei Ascend Mate 2] divineBliss:
Orzmud,

I'm using the 10/24 build with no issues.

What recovery are you using and how did you try and go to recovery? Next time try "adb reboot recovery" from a PC during bootlooping.

There is also a new TWRP version in the other thread, but I have no idea what changed.
[Huawei Ascend Mate 2] Orzmud:
divineBliss,

The MT2L03 has twrp-3.1.1-0, I used that one to load MDMower's 9/22 release (lineage-14.1-20170922-UNOFFICIAL-mt2.zip). Tried going to recovery by the usual Power + Vol Up key combo.

When the bootloop happened, I couldn't see traces of the phone being detected by the laptop:

$ sudo watch -n0 "adb devices"

showed nothing.
[Huawei Ascend Mate 2] divineBliss:
Did you try entering TWRP with the buttons? :

https://xdaforums.com/showpost.php?p=74213391&postcount=3

See new TWRP versions and newest 7.1.2 builds:

https://androidfilehost.com/?a=show&w=files&flid=40887

I'm using N1 TWRP and 10/24 ROM.
[Huawei Ascend Mate 2] Orzmud:
In my case, when I was holding Power + Vol up keys, the phone only rebooted, there was no second vibration, just rebooting. Any case, that's not an issue anymore, I can go to recovery now that the phone "decided" to work again :)

I just made a backup and will try 10/24. Is it safe to go from 9/22 to 10/24 without data/system cleanup?

Regards,
[Huawei Ascend Mate 2] divineBliss:
There won't be any second vibration unless you hold the buttons in until the second vibration.. ... and it's a good idea to master how to get into TWRP before it becomes an urgent necessity ;) .

As long as you made a full backup, yeah, it should/will probably work. I went from CandySix to LineageOS 14.1 without wiping data or system - just wiped Dalvik/cache.
[Huawei Ascend Mate 2] Orzmud:
I just sideload-updated to the 10/24 build, it's working as usual.

# cd /tmp; F=lineage-14.1-20171024-UNOFFICIAL-mt2.zip; wget "https://de1.androidfilehost.com/dl/DFwbnP6ykgiBP27huB9wPQ/1509479524/673791459329056031/$F"; mkdir /tmp/$$; 7z x $F -o/tmp/$$ -y; sed -s '/^assert/d' -i /tmp/$$/META-INF/com/google/android/updater-script; 7z a -tzip $F-noassert.zip /tmp/$$/*; adb push $F-noassert.zip /sdcard/; adb reboot recovery; sleep 120; adb sideload /tmp/$F-noassert.zip; sleep 60; adb reboot

I kept a copy into the device /sdcard/ folder in case I want to refer back to it from TWRP.

Thanks divineBliss for confirming status of 10/24.

Regards,
[Huawei Ascend Mate 2] Orzmud:
I'll keep the device rebooting for the next 2 days, we'll see if anything interesting comes out of this.

REBOOTS_COUNT=-1; REBOOTS_BAD=0; REBOOTS_GOOD=0; TOTAL_BAD_REBOOTS=100; TOTAL_REBOOTS=1000; [ ! -x $1 ] && [[ $1 =~ [0-9]* ]] && TOTAL_REBOOTS=$1; [ ! -x $2 ] && [[ $2 =~ [0-9]* ]] && TOTAL_BAD_REBOOTS=$1; DEV=$(adb devices | grep -v List | head -1 | awk '{print $1}'); [ ! -x $3 ] && DEV=$3; [ -x $DEV ] && echo "Device Serial required!"; while [ ! -x $DEV ] && [ $REBOOTS_COUNT != $TOTAL_REBOOTS ] && [ $REBOOTS_BAD != $TOTAL_BAD_REBOOTS ]; do REBOOTS_COUNT=$(($REBOOTS_COUNT + 1)); echo "Total Reboots: $REBOOTS_COUNT"; echo "Successfull Reboots: $REBOOTS_GOOD"; echo "Unsuccessfull Reboots: $REBOOTS_BAD"; DEV_STATE=($(adb devices | grep -v List | grep $DEV | awk '{print $1, $2}')); [ ! -x ${DEV_STATE[0]} ] && [ $DEV == ${DEV_STATE[0]} ] && [ ${DEV_STATE[1]} == 'device' ] && REBOOTS_GOOD=$(($REBOOTS_GOOD + 1)) && REBOOTS_BAD=0 && adb -s $DEV reboot && sleep 180 && continue; [ ! -x ${DEV_STATE[1]} == 'no' ] && echo "No ADB permissions, enable ADB on device." && break; [ -x ${DEV_STATE[0]} ] && REBOOTS_BAD=$(($REBOOTS_BAD + 1)) && adb kill-server && adb -s $DEV reboot && sleep 180 && continue; echo "Shouldnt reach here."; break; done

UPDATE: Completed the reboot cycles and no issues seen.

Regards,
[Paranoid Android Q&A] sessionLayer3:
PA latest for Note2 gtn-7100
[ONE Q&A, Help & Troubleshooting] SasBro:
Hi all,

Since a couple of days my OPO is doing crazy things on the display. Unfortunately I cannot post here any pics or video.

BUT you can find a video of my screen issue if you search for "OPO touchscreen error, lagged response, only showing piled fragments" on forumsDOToneplusDOTnet

It started out of nowhere, sometimes it goes back to normal and works flawless for some minutes only.

Issue: Touch responses are lagged, it's hard to impossible to navigate on the screen, the display changes constantly showing random fragments of the same piled up.

Has anyone seen something like this before?

Is it rather a hardware or a software issue?

Any suggestions of how to repair it?

Thanks a lot.
[ONE Q&A, Help & Troubleshooting] Mr.Ak:
Did you tried reflashing your current ROM?
[ONE Q&A, Help & Troubleshooting] SasBro:
Thanks for your suggestion.

I haven't tried reflashing, but will do if I don't hear of another solution.

You can find a video of my screen issue if you search for "OPO touchscreen error, lagged response, only showing piled fragments" on forumsDOToneplusDOTnet
[ONE Q&A, Help & Troubleshooting] Mr.Ak:
Try that,then only we can confirm if that's sw or hw.
[Moto G4 Plus Questions & Answers] sublimeace:
Hey guys,

I can't send or recieve MMS in Viper OS 3.0. The settings are fine and the helpline people said that there's no back end issue. CAn someone please help me understand the problem? thanks
[Moto G4 Plus Questions & Answers] MisterSteve:
Are you running Adblock Plus? I was unable to send or receive MMS when I used ABP. I first thought it was the ROM I was using at the time, but through trial and error (and Google), discovered it was Adblock Plus.
[OnePlus 5 Questions & Answers] Saelee:
Anyone experience the audio/video being out of sync WITH THE BUILT IN SPEAKER? I understand that on some bluetooth there could be a slight delay but I am talking about the phone's built in speaker here. I use BT speakers as well but I haven't noticed any delay with bluetooth speakers.

My phone is all stock with the latest update. This happens when I am watching a video form Youtube or facebook. The delay can range from half sec to 3 sec delay. Even if I close the app and re-launch it, the delay will still be there. The only way to fix this is if I reboot the phone. I watch video almost every day on this phone and half of the time I am using just the stock speaker. This would happen once every week or two.

Anyone experienced this?
[OnePlus 5 Questions & Answers] saad780:
If you have Viper4Android. Try turning it off. Worked for me.
[OnePlus 5 Questions & Answers] beningodfrey4:
Same here, in Facebook and YouTube.

Yeah I have the same issue here. If I restart the video, it plays in sync for a couple of seconds after which the video pauses for a second making the audio lead.
[OnePlus 5 Questions & Answers] Saelee:
I never downloaded that app.
[8125, K-JAM, P4300, MDA Vario General] evilwise:
Okay I just bought this Wizard used. It had a dead battery when I got it so I charged it completely before I started messing with it. I was having a lot of problems upgrading it. First the loader wouldn't work at all but I started using the noID version and got it to upgrade to 99% but it kept giving a communication error at that point. From what I've read so far I guess it's probably because this is a G4 Wizard and it has the CID-Lock that's preventing it from taking these roms. Anyway, I put wizard_love on it and it did boot up which made me pretty happy but then I started a flash of XDA WM6 v5 on it and went to sleep while it was upgrading. I guess it again failed at 99% but then when I woke up the phone was completely unresponsive. I tried removing the battery and reinserting, including holding the camera button while pressing the power button. No response. I reinstalled Activesync on my laptop and then the VERY first time I plugged the phone in, it went to the bootloader screen and I was a little bit relieved but then just a second later it went black again before I had a chance to begin the wizard_love flash again. What happened? Did the battery die and now it doesn't want to charge? What's the fix for this? I feel like it's not completely bricked since I did see the bootloader screen for a second but I can't figure it out for the life of me. I searched and read the whole flashing thread. Can someone point me in the right direction? There's SO much about this device here. Not like my old Wallaby. Oh, also this Wizard is a Cingular 8125 if that matters.
[8125, K-JAM, P4300, MDA Vario General] evilwise:
Ugggghh... I think I have some strange USB cable action going on.... I have one USB cable that I originally used to charge the phone but it wouldn't sync correctly... Just to be having something to do I tried pugging that cable back into the phone and it did go into the bootloader screen with THAT cable but no USB connection indicator. I unplugged that cable and plugged the cable I'd used to sync it in and did get the USB indicator on the bootloader screen so I started flashing wizard_love and it got about half way through and went black again. Now I'm pretty positive that this IS a battery issue being exacerbated by my apparently shoddy USB cables. I'm going to leave the cable that it charged off of plugged in for a couple hours and then try to flash with the other cable again. The phone should be able to take a charge while sitting at the bootloader screen right?
[8125, K-JAM, P4300, MDA Vario General] zabardast_1:
NOPES ! battery cannot be charged via usb cable in bootloaders,charging a battery via usb cable is only possible if you gave a working phone and it loads up into working OS.So to get it charged you need to have a 'wall charger' capable of an charge output of 1.00 amps,only then it'll get fully charged and work or get it charged through a friends phone,ok
[8125, K-JAM, P4300, MDA Vario General] evilwise:
Actually it did charge while in bootloader mode but only with one out of many USB cables I have. It was a thick clear cable with a metal weave visible inside. Interestingly, this same cable won't let the phone sync. Signs and wonders.

I recovered it with wizard_love but I want to put a WM6 rom on it. I'm trying to load xm6r5 right now but it still will only get to 99% and then craps out. Is this because it's a G4 and has this CID lock thing going on? I installed the lokiwiz utility that supposedly removes the CID lock but it still failed at 99% loading xm6r5. What is currently the best method for loading these type of flashes onto G4 Wizards? I've read so many 50 page threads that I'm getting a headache and it's hard to figure out which one is the most reliable/current.
[8125, K-JAM, P4300, MDA Vario General] evilwise:
Once again "dead"

Okay now I tried to downgrade to Button's ROM CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe in order to get the lokiwiz program to unlock the cid but after it installed, when it started it stayed on Button's splash screen with the beer for like five minutes so I tried to hard boot it and now it once again won't come on, even with the silver usb cable. Whats up with that?
[8125, K-JAM, P4300, MDA Vario General] evilwise:
Man I have this terrible fear that even though I read about this rom in threads about how to remove CID locks from G4 phones that I've bricked it by putting something on it that has the G4 killing data in it. Can someone tell me what happened?
[8125, K-JAM, P4300, MDA Vario General] evilwise:
Alright... I guess that rom WAS intended only for G3 phones and I made a big mistake. It's time to start shopping for a replacement motherboard I guess. I think I'll try to get a G3 one this time.
[8125, K-JAM, P4300, MDA Vario General] zabardast_1:
What ? !!! Did I Hear Yet Another G4 "bricked"

OMG !

This has been at least more than 1000 times posted...WARNED...SCREAMED...YELLED...BEGGED..PLz PLZ never flash a Rom with IPL/SPL in it to a G4 device, it'll "BRICK" it :mad::mad:

HURRAH ! man congratulations ! you have a shiny expensive paper weight decorating your table :p
[8125, K-JAM, P4300, MDA Vario General] morshwa:
hi, please! need help... after I've flash the Wizard_Love_2.26.10.2_WWE_Novii_CF2 on my G3 device the rom is very slowly and my PC doesn't recognized my wizard when it connected with the USB cable.

any solution how can I change this rom?

many thanks

moran
[8125, K-JAM, P4300, MDA Vario General] morshwa:
maybe i need a driver?
[8125, K-JAM, P4300, MDA Vario General] Myrddin Wyllt:
Wrong version of ActiveSync?
[8125, K-JAM, P4300, MDA Vario General] morshwa:
No, i was try with 3 different PC...

:confused:
[8125, K-JAM, P4300, MDA Vario General] Myrddin Wyllt:
I'm not talking about the PC version, I'm talking about the version of ACTIVESYNC. You should be using either 4.1 or 4.5. Make sure you are. Let us know...
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
​

This is ViperOS

Disclaimer:

About:

​

Features:

Bugs:

FM Radio app is broken Fixed in 3.0.2

2600mAh battery info Fixed in 3.0.1

low speaker incall audio Fixed in 3.0.3

2nd sim incall audio

Bt audio

You tell me

Instructions:

1.Download ROM, GApps and Addons-SU / Magisk

2.Reboot to Recovery

3. Wipe System, dalvik, cache, data preload, persist, android secure

4.Flash ROM, Gapps and Addons-SU

5.Reboot

6.Enjoy

Download:

Direct Download (Google Cloud)

AFH

Google Drive

GApps (I use nano) : OpenGApps

Addons-SU : Addons-Su arm

Magisk : Magisk

Older Versions:

AFH 3.0.2: Download

AFH 3.0 : Download

AFH Viper Folder with older versions : Download

Credits & Thanks:

All ViperOS Team

LineageOS team

ResurrectionRemix team

crDroid team

And all other open source Devs/Teams I may have missed!

Other links

Galaxy MSM8916 Telegram channel

Viper Telegram channel

Google+ community

ROM source

Tree of all official devices

XDA:DevDB Information

ViperOS, ROM for the Samsung Galaxy J5

Contributors

bluedogerino, EsromG5, GeneticEngineer

Source Code: https://github.com/therootlord/android_kernel_samsung_msm8916/tree/cm-14.1-testing

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

ROM Firmware Required: 6.0.1 Marshmallow

Version Information

Status: Stable

Current Stable Version: 3.0

Stable Release Date: 2017-08-24

Created 2017-08-24

Last Updated 2018-01-30
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Reserved
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] jordi003:
Thank you for sharing!

do you have wifi reboot bug?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
No,it doesn't , it's fixed.
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] BlackAxiom:
apparently we succesfully kicked that bug out from this forum
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Lol,yup :D
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] jordi003:
believe me, for every 5 roms and tested 4 have that bug,
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] BlackAxiom:
my next rom does not have that issue. also updating some of the oldies
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Try it and see for yourself
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] jordi003:
proves it, again, thanks for sharing!

:good:
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] krisz035799:
Helló ! battery2600mAh . battery fix? call low speaker..
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Fix for that tomorrow :D
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] lemlis:
and fix incall audio 2sim .
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] BlackAxiom:
Sniiiifiiinggg wee needdd youuu:D

---------- Post added at 06:05 AM ---------- Previous post was at 06:05 AM ----------

I knew this was coming
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] jordi003:
There are no reboots, good job ;)
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
If u know how to fix it, please do it by all means

Oh yeah, I forgot you don't have a J5(2016), well then stfu. So get off my thread
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Try this for audio fix
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] lemlis:
:D:D

you are ridiculous kid wich i know.Tell me please wher you thief META-INF ,why you use Xperience rom meta inf?? for Viper

its not right .this Meta inf have in mx folder Xperience rom release keys and updater script have xperience rom ota lines no needed here.its wrong.

package_extract_file("META-INF/mx/xperience/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/mx/xperience/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");

Next time you must use this Template to porting Rom. i think you know what did wit him.And not deleting install folder.

View attachment 4252103

You may thank for the lessons,-act like a pig is wrong.

you right- i not have J5 2016,and this is last my help to community j5 2016.

Bye for all. ;)
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
I didn't use yours, SpamMachine sent me the file :P
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] lemlis:
I never have my own maked files,all what i post is taked or thiefed from other authors Roms.all what i posted and puted in AFH you can use and make threads

:laugh:
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] KRou705:
soporte otg

Al conectar un usb y da a cada rato errores y mouse, teclados no los reconoce :confuso:
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] xXnaxoXx2:
Bt audio

You can fix the bt audio bug?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] robinfive:
who build the costum kernel for j5 2016 ???
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] N1ck31:
Can you?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] N1ck31:
Will you fix the BT audio bug?

---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] Flegmon:
Uhm which Kernel ? I think you wrote in the wrong thread.
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] N1ck31:
Dont worry about the kernel thing
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] xXnaxoXx2:
if you can teach me, probably, why not?:confused:
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] N1ck31:
Idk how to
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] N1ck31:
[MENTION=8353520]bluedogerino[/MENTION] when will the final build come out?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] MrKostaz:
non stop checking for updates

i installed to my phone the rom succesfullt and it stucks on "checking for updates" forever like i left it all night and nothing i tried restarting and tried mobile networks nothing can someone help?:rolleyes::rolleyes:
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Did u try not turning on network, or ejecting sim card?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] N1ck31:
When is a new update coming out been waiting for a long time
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] TheMadScientist:
Closed at OP request
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Dude, I asked for permission to post this, I don't see your point, I'm not gonna post your ROMs.

If someone else will that's fine. This has nothing to do with this ROM. And honestly u make what u want, I don't really care about it.

Thank you for the knowledge. I don't see why u constanly posting replies if u left this device. :p
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] csaba4569:
BT audio working?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] shreyas1221:
Tried to install this rom on j510f, phone wont boot just vibrates
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
Nope
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] bluedogerino:
I don't own this variant, so I'm not sure why it won't boot. I own the global Dual SIM variant (J510FN)

What baseband do u have?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] shreyas1221:
Currently I'm using EXTREME UX ROM V9

Baseband : J510FXXU2AQC1
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] BlackAxiom:
Try AQD3
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] aghias:
Is the screen flashing fixed?
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] krisz035799:
BT.audio ok :)
[Samsung Galaxy J5 (2016) ROMs, Kernels, Recoveries] Paulo Belfort:
The phone is very hot. :(