Search results

This is the first time I am trying this out. I recently rooted my Galaxy Tab S5e LTE with the SD660 and the script fails stating "Device appears not to be made by Samsung". Wondering whether it can work on this device.

I had to go back to 17.1 as well since Screen Cast too is not working on 18.1. Guess 18.1 needs a lot more time to be up to scratch. Might try it next when it gets to nightlies.

I dirty flashed 18.1 over 17.1 along with NikGappsR and MagiskR. Booted fine and I had to update Magisk once from within the already installed app. Did not need to flash the other zip file.

I unlocked the bootloader yesterday and set everything up. Magisk on stable channel leads to a blank screen bootloop and on beta channel it only boots to download mode. Fortunately, it works well with 17.1, so I am sticking to that. Thanks for your effort in maintaining LOS for this device.

Any kind of Widevine support I try out Bliss on my Dell Venue 11 Pro 7140 every few months and generally only the stable releases work for me. In that regard, great job with v11 as almost everything works apart from the headphone jack which is not a concern as I can use bluetooth. However...

I had unlocked the bootloader and tried a couple of custom ROMs a few months back but decided it isn't worth it because my main hindrance of adblocking is addressed using DNS and any unneeded app can be disabled using adb. On the flip side, I need Widevine L1 for Netflix/Prime and no custom ROM...

On my Dell Venue 11 Pro 7140, 12.3 booted fine but 12.4 boots to the home screen with a black screen and only the NavBar. Same with Vulkan enabled. nomodeset doesn't go beyond the console. Anything else I can try? Edit: The last 12 alpha that booted fine was probably 12.1 as neither 12.2 or...

Thanks. Any idea then on how I can switch to Headphones. I remember in the past there used to be simple controls for Speakers and Headphone and I could mute/unmute one or the other. However, the controls are now different and I am unsure which ones to work with and what to change. Probably I am...

Switching audio output I am trying Bliss OS after more than a couple of years on my Dell Venue 11 Pro 7140. The good thing is everything seems to work on Android 10. While the the audio works fine out of the tablet speakers, I would like to be able to switch it to Headphones or HDMI. This is...

I rooted the phone a month or so back to use a custom kernel, install AdAway and even tried out OmniROM which was quite buggy and essentially a step down from OxygenOS. More importantly, it wasn't worth it because of losing Widevine L1 which is needed in my case for Netflix and Prime Video, as I...

The A50 differs from the other A-series devices in terms of having an Exynos 9610 which has seen practically zero development and poor GSI compatibility. However, finally we have an Android One device with practically the same chipset. The Motorola Action One comes with the Exynos 9609 which is...

Type-C as a standard is a mess. I don't think you are required to support alternate modes in USB 3.1, so I suppose there are USB 3.1 Type-C devices that still don't output video. Regarding audio, there is Audio Accessory Mode for Type-C and the concept of active and passive headphones/dongles...

There were quite a few posts about MIPI fail concerning the S7, so you can check for that. The identifiers used to be labelled as the MID and PID, so it might be that instead of being addresses. The common solutions stated doing a NV Rebuild and/or replacing the FEMid component. Not sure how you...

I always get a video of 8s 333ms with a bitrate of 11.5 Mb/s and a size of 11.5 MB. The minimum and maximum framerate is 30 as displayed in MediaInfo in my case. However, since Samsung advertises the Super Slow-mo as 960 fps for 0.4s on S10 and 0.2s on the S9, 480 fps for 0.4s on the A50 sounds...

Haven't checked it yet, but with this release the QR scanner has been integrated in the camera app, so like iOS you just need to point the camera at a QR code for it to open a page. Earlier, it could only be done through Bixby Vision.

It has only been released for INS CSC as of now. It will most likely follow for others. If you are on INS CSC, then OTA may be staggered to reduce load.

There is a reason why every online article attributes the source. All I requested him to do was to include the source link as it is copyrighted content and there are limitations to how much of the content you can copy-paste as-is without ownership. Also, I posted about the firmware release 7-8...

If you are going to simply post the news, then rather than copy-pasting just share the link to the source. https://www.sammobile.com/2019/06/28/galaxy-a50-june-update-india-night-mode-super-slow-mo/ ---------- Post added at 11:26 PM ---------- Previous post was at 10:33 PM ---------- This...

No, it is still at Level 3 and it is unlikely it will ever change since Samsung uses its own APIs and provides its own limited camera SDK. Best hope is a hack of some sort as normal methods won't work.

Whatsapp on iOS backs up only to iCloud.

ASF2 for INS with June security patch is now available, although not yet updated on the Samsung website.

If you are logged in to your Samsung account, then try Find My Mobile. The Unlock option only wipes off the screen lock info and biometrics. Google's Find My Device is more limited in that respect, but you can check it out as well.

A50 Camera is at Limited, so I am not talking about any level other than those 4. What I am saying is that Samsung has locked the Camera at Limited level irrespective of build.prop values. Seems a deliberate move on Samsung's part to perhaps hobble the camera further in a mid-range device.

For the record, the value remains at 1 and does nothing on a rooted system. Meanwhile, edit to get Samsung Health functional works fine. Even something like Widevine Level 1 is not impacted by Knox. The apps impacted by Knox specifically display an error message after Knox is tripped. The...

It can be periodically unstable resulting in reboots and WiFi disconnections. However, the frequency of these issues has reduced considerably with recent Magisk/firmware updates.

This has been asked so many times that you can get the link by searching. John Wu's method works on any Samsung 2019 device released with Pie. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

Any stock firmware can be rooted using Magisk. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

FP reader posts are dime a dozen in this forum. To provide my opinion, the FP reader was extremely poor in March, significantly improved in April and now seems to be working at the level allowed by the hardware. It takes less than a second to completely unlock using the FP reader, but for that...

Did you rename the file as mentioned in post #10? This is what caused the reboot to stock recovery in my case. It subsequently led to triggering of Vaultkeeper which prevents flashing of unauthorized files. You will need to flash the stock firmware and verify the OEM unlock option to once again...

The script and the commands work fine. Make sure you are running the commands as sudo on the linux distribution. If using the script, you can add "sudo" to all the commands. However, as I mentioned, the image didn't work for me and my phone simply went in to a bootloop irrespective of whether I...

SamFirm is also a third party tool which is officially marked as deprecated by the author, though it still works in most cases. The download source and file is identical for both, so there is no benefit either way. Just posting another full-speed option since a lot of people would land up on...

Most of the sites listing Samsung firmware provide "Unlimited Speed" download as a premium option and limit the free download to a pitiable 15 KB/sec. IMEI.info allows you to download the firmware at full speed. It will initially download a 11MB file called Samsung Hard Downloader after you...

The A-only GSI didn't work either and is constantly going in to a bootloop. Regarding the Windows driver, the one shown in your screenshot doesn't seem to exist by default, so where can it be added from?

I was about to go back to stock using Odin but I flashed the image again. However, is there any way to get the log from within TWRP as it seems the logcat command doesn't work when in recovery? I had used phhusson's v114 A/B image with gapps and su. Also wanted to mention that MTP doesn't work...

The bin partition only has a [email protected] file. I deleted that anyway and wiped data but still stuck in a bootloop. For reference, this is how my stock.img looks like. ---------- Post added at 02:11 AM ---------- Previous post was at 01:54 AM ---------- If you...

I prepared the stock.img file using phhusson's v114 A/B image on Ubuntu and it came out to be close to 5.2 GB. The image seems proper as I can see the file structure within. Since the adb command to shift to /data/media failed due to permission error, I moved it using adb push to internal SD and...

Since I was messing around with the new TWRP, I thought I'd give the GSI images from phhusson a go. The A-B variant simply reboots to Download mode whereas the A variant puts the phone in a bootloop. In short, GSI doesn't work on the A50 with the current TWRP.

Don't waste your breath on him as he is completely clueless. He is still unable to fathom that the script he has posted does nothing more than add "persist.camera.HAL3.enabled=1" to build.prop which doesn't work for the A50. On top of that there was no working TWRP to flash the file with when...

You can always install Magisk with stock recovery for any firmware using topjohnwu's guide over here. However, Magisk installation will always trip Knox. Also, TWRP might be helpful in flashing various patches, especially for GSI releases that you cannot do with the stock recovery.

Not much use for non-Magisk TWRP I am afraid. So I am going back to Magisk with stock recovery for now since I chiely use Titanium backup. I am on the ASE2 firmware and since this TWRP boots it up fine, I am assuming it is the same kernel version as used in the stock version since its source...

TWRP is permanent but it always boots to TWRP irrespective of key combination and from there one has to reboot to System. Also, I patched the recovery image with Magisk and it doesn't seem to work. When rebooting to recovery from TWRP the first time, it leads to a blank screen and on rebooting...

I had to first boot in to the OS and check for updates to register the device with the OEM unlock option enabled once again before the "official binaries only" message disappeared. Thereafter things worked out fine as per your instructions and I have permanent TWRP. Will try out Magisk-patched...

Thanks, that's the combination I was looking out for. I did that combination without the USB connected and used some other combination when the USB was connected. After a fresh ODIN flash, I was able to boot in to TWRP without any issues, so great job with the recovery. Update 1: After powering...

I had removed all accounts and formatted data/cache partitions before flashing the TWRP file. However, the first time I missed booting immediately in to recovery and the OS started booting instead. So, I rebooted in to recovery and it is stuck on the TWRP splash screen since then. So, did the...

You just needed to post proof that this works and instead you are going on a rant for some delusional reason. Not going to bother responding again. Good for those who benefit from your pointless post.

On booting to recovery using the key combination, my phone got stuck at the TeamWin splash screen and won't go beyond it. Now it just boots to that screen when using the normal key combination as well instead of Android. Anything I did wrong or is there any other issue? I was using Magisk with...

And yet you have not provided any proof that it is working for you. That was the essence of my post which seems to have completely gone over your head. There is no question of politeness here but rather the need of evidence in support of any tutorial that's posted. At the time of my reply, your...

As I mentioned previously, the HAL3 command doesn't work on the A50 as I have tried it with root access. Why are you posting futile instructions that require people to reset their devices without any benefit? Unless you have successfully tried it out yourself, it makes no sense to copy-paste...

Just wanted to bring to attention that Samsung published the ASE2 kernel sources following my request from last week. So, we now have the latest kernel sources which can at least be used to get twrp working, in case there is any developer around.

I had requested Samsung to publish the ASE2 kernel sources last week and got a response today. So all the ingredients to compile the latest TWRP for the ASE2 firmware are there provided someone knows what to do.