yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
Hi Guys,

Anyone know how to fix DRK for SM-N910W8 NOTE 4 CANADIAN??

This phone was working fine up until Samsung's latest update which screwed over EVERYONE and I'm positive it's a software/firmware issue as problems occurred about a year or two ago but now I'm seeing possible solutions pop up for other Note 4's to fix Device Root Key errors.

The research I've found say you need to have a backup of your original efs folder which I unfortunately don't have!

Also found a few supposed solutions on youtube but don't know if it'll work on my phone, nor do I know where they got the software and files to do it: https://www.youtube.com/watch?v=51Ki6eUhIBk

Thanks in advance, any help would be greatly appreciated! :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] bokharimw2:
try flash ur device with software 4 files of ur country

give me name of your country and version android what are u in now
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
Hi, I'm in Canada and running Marshmallow 6.0.1.

I found the files I need on various sites but these bastards are all trying to make money off it. Anyone know where I can get them for free? (it's just a matter of time)

COMBINATION_OYA_FA44_N910W8VLU1AOC2_OYA_3357306_REV00_user_mid_noship_MULTI_CERT.tar.rar

https://firmware.gem-flash.com/index.php?a=browse&b=category&id=1280

n/m, it appears I found the files here:

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

I'll test and report back and/or if anyone has tested before me please post your results!

edit:

hrmmm... not sure how to flash this file.

It's a single file name: COMBINATION_OYA_FA44_N910W8VLU1AOC2_OYA_3357306_REV00_user_mid_noship_MULTI_CERT.tar.md5

What do I select in odin for this? AP??

or do I have to extract this file so I have BL, CP and CSC? (if so, I don't know how to do that)

Any help would be greatly appreciated!

Edit2:---------------------------------------------------------------------------------------------

After seeing a few videos on youtube I tried flashing the combo file selecting AP in odin but got this error message:

Anyone have experience with this?

From what I've seen online so far I'm assuming the combo file contains the BL, CP and CSC files to fix DRK?

Apparently I need the following files:

N910W8VLS1DPK1_OYA1DPK1_V6.0.1_Repair_Firmware_4Files_( FMC Canada (Fido Mobile) ).rar

Model: Samsung GALAXY Note4 SM-N910W8

OS Version: Android Marshmallow V6.0.1

PDA/AP Version: N910W8VLS1DPK1

CSC Version: N910W8OYA1DPK1

MODEM/CP Version: N910W8VLS1DPK1

Region: FMC Canada (Fido Mobile)

Security Patch Level : 2016-11-01

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

Content Of File:

AP_N910W8VLS1DPK1_CL8000148_QB11446490_REV00_user_low_ship_MULTI_CERT.tar.md5

BL_N910W8VLS1DPK1_CL8000148_QB11446490_REV00_user_low_ship_MULTI_CERT.tar.md5

CP_N910W8VLS1DPK1_CL8000148_QB11446490_REV00_user_low_ship_MULTI_CERT.tar.md5

CSC_OYA_N910W8OYA1DPK1_CL8000148_QB11446490_REV00_user_low_ship_MULTI_CERT.tar.md5

info.txt

TRLTE_CAN_OPEN.pit

Any help would be greatly appreciated - thanks again in advance!
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
BUMP - anyone?? :(
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
bumping again....

bumping again....
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
Really? noone out there fixed their Note 4 with the files mentioned in my previous post?
[Galaxy Note 4 Q&A, Help & Troubleshooting] BadBoyRoz:
im in the same thing right now. Posted my own thread and nothing. So far Ive bough a new battery and flashed original firmware and twrp but still in bootloop. havent tried autoroot yet but doing all someone said might fix it so we will see and I WILL keep you updated if there is any change

Note 4 Gods help us out here lol!
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
DRK and Bootloop are two totally different errors. I have a feeling I might need to purchase a Z3X Samsung Tool to fix DRK but they go for around $200 bux! Not sure about your bootloop problem - sorry :(
[Galaxy Note 4 Q&A, Help & Troubleshooting] unic0rnio:
I just bought it from one of those ****s. I'll upload it to drive and send you the link when it's done ;). Just keep it and spread it if you ever see anyone in need :angel:. Hopefully this fixes our problems!:victory:

Btw, firmware.gem-flash. com/index.php?a=browse&b=file-info&id=50192 is the firware I'll be uploading.

Cheers.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ogriv:
Just got this email from the Samsung Class Action lawsuit:

Spread the word!
[Moto G5 Questions & Answers] João Annes:
Good evening. I am from Brazil and I am exactly with this problem. Since I do not speak English (sorry for this) I translated it through Google, but everything was confusing. Does this procedure go back to working the 4G or just backs up earlier to avoid this problem in the future? (but once sorry for not understanding the text) thank you.
[Moto G5 Questions & Answers] Shooting Star Max:
When my Cedric was still alive, I tried to update the bootloader and the baseband to the latest January version using fastboot. I didn't touch the current ROM (LineageOS 15.1 unofficial). I flashed the following files to their adequate partitions: adspso.bin, bootloader.img, fsg.mbn, NON-HLOS.bin, and oem.img. The device worked well and was updated perfectly. Then... my curiosity got the best of me. Since the fastboot ROM includes commands to erase the modemst partitions, I thought it would be good to perform that operation (despite everything working well, stupid me). THIS killed IMEI for me:

fastboot erase modemst1
fastboot erase modemst2

My attempts to recover from this situation led me to try to downgrade to the November update, which ended in a dead device after trying to flash the November full ROM using RSD-Lite. I hope my experience can serve as a warning for others.
[Moto G5 Questions & Answers] Exanneon:
"If it ain't broke, don't fix it."

But then again, I've made that mistake many times as well xD
[Moto G5 Questions & Answers] vatttt4:
Cedric imei

Do I have to erase modemst1 and. 2 to install backup
[Android Q&A, Help & Troubleshooting] Reezaaa:
Hey, can you help me? I can not type "continue" in the data format. I also got a bug that my phone could not receive the signal. Please help me :crying:
[G4 Android Development] steadfasterX:
About

Who needs this?

When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).

This is annoying on the one hand and can cause problems on the other.

These UsU kernels are specific for your model and available for several custom and stock ROMs.

Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).

Guide

(read FAQ #1 if you have the baseband package flashed currently!)

Choose the right UsU kernel (according to the ROM you have)

Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)

If not: Flash a ROM which has an UsU kernel available NOW.

Download the UsU kernel to your PC

Boot device in fastboot mode (check the UsU OP thread for a how-to)

Flash the downloaded UsU kernel (has to be done

again

after a ROM flashing!):

fastboot flash boot <model>_xx_boot_xx.img

(replace "<model>_xx_boot_xx.img" with the real filename)

Reboot and enjoy:

fastboot reboot

Downloads

steadfasterX leech Server

Choose the folder of your device (all the ones named "-UsU" are obviously those of your interest)

Choose the ROM flavor of the ROM you have installed or want to install

Choose the version of that ROM

Download the latest boot image you can find (the higher the build number the newer)

Sources / Changelogs

aoscp | lineageos | rr : nougat

aoscp | lineageos | rr : oreo

stock : nougat

Credits

kessaras - without him the custom versions of the UsU kernels wouldn't be what they are :)

me - I provided the UsU patches included in every UsU kernel, a Jenkins build server, a download server and many of my free time.. so yes I think I can get some credits too ;)

XDA:DevDB Information

UsU kernel versions, Kernel for the LG G4

Contributors

steadfasterX, kessaras

Source Code: https://github.com/Suicide-Squirrel

Kernel Special Features: Making UsU baseband package flashing obsolete

Version Information

Status: Nightly

Created 2018-03-15

Last Updated 2020-04-14
[G4 Android Development] steadfasterX:
Frequently Asked Questions

FAQ

1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?

Pretty simple. Flash the modem partition again in fastboot.

Which one depends...

I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).

Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.

Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)

If not: Flash a ROM which has an UsU kernel available NOW.

Extract the latest MM KDZ of your device model with SALT (do

NOT

use the windows tools!)

Boot device in fastboot mode (check the UsU OP thread for a how-to)

Flash the modem:

fastboot flash modem modem.bin

(or if named img: fastboot flash modem modem.img)

Flash the downloaded UsU kernel:

fastboot flash boot <model>_xx_boot_xx.img

(replace "<model>_xx_boot_xx.img" with the real filename)

Reboot and enjoy:

fastboot reboot

2) Where are the sources for the UsU kernels?

AOSCP - Nougat -> here

AOSCP - Oreo -> here

STOCK - Nougat -> here

3) Are all UsU kernels based on the TITAN stuff?

No. Only AOSCP Nougat / Oreo for now are based on the TITAN kernel.

STOCK is pure STOCK plus the UsU patches.

ZZZ) I miss a UsU kernel for my ROM!! Could you provide it please?

Do not hesitate to ask.. KINDLY. There is no guarantee. Maybe I will add it - maybe not. There are too many out there to build for all of them.

Up to then you are stuck with flashing the baseband package or switch to an UsU kernel supported ROM
[G4 Android Development] sdembiske:
Just a couple of quick questions/clarifications:

- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?

- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?

Thanks,

S.
[G4 Android Development] steadfasterX:
No they are not the same because I had to rebuild all kernel versions .

The stock kernel is only for the nougat based ROM available so if you had v29a before or when creating the backup then yes. But if you were on lollipop or marshmallow then a nougat kernel makes no sense on these.

there is no TWRP stock version available since a long time already.. just flash the latest N preview.
[G4 Android Development] fates13:
Sorry, deleted. Thank you!!!
[G4 Android Development] අධිරාජ (Adhirāja):
I did some research. Read that device drivers are stored in the kernel. So that means no matter what rom, if the kernel is H812, you cannot get the FM radio, right? Unless you can find a way to install H815 fm radio driver onto h812 kernel.
[G4 Android Development] grantdb:
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.

As far as I can figure this is what I should do to get stock Nougat

Don't wipe anything in TWRP

Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,

flash modem.bin from my original SALT backup of original MM modem,

flash UsU kernel h812_stock_boot_build-11-nougat.img

reboot to system and enjoy!

Hopefully this is right!

Edit: Everything works perfectly except calls and corrupted sdcard!

Attached the error log for when making a call.
[G4 Android Development] fil3s:
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?

Edit: I do have a no Sim detection issue with aoscp oreo
[G4 Android Development] steadfasterX:
Checkout faq zzz in the UsU thread.. :(

Well up to you if you flash it or not. If everything is working I see no other reason then cosmetics.

This is a very well known issue for aoscp oreo! Just use the a search in that thread! They also have issues with battery drain etc and I always said oreo is nothing which I can recommend atm. Its a play ground for me even if it boots and most things are working.
[G4 Android Development] grantdb:
All I did for working everything with bootloader unlocked with SALT and baseband flashed on stock MM H812:

First thing I did was follow the following since I allready flashed the baseband after unlocking:

In the above procedure I first used my backup MM modem and calls had no sound then I repeated the same procedure using the N modem and it bootlooped.

Restored my FULL TWRP backup (Boot, Recovery, System, Data, Cache, Firmware image, EFS, BL unlock state, Bootloader, Carrier) to MM stock with root and custom kernel (LuPus).

Booted into the system once to make sure all working.

Boot into recovery.

Mount system partition.

Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).

Reboot into recovery.

Mount system partition.

Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip).

Reboot into system.

Wait for stock rom to fully load (Takes about 15 mins).

SIM and SD card fully working! Network is immediate with no delay only on first boot for some reason then see below.

Reboot into recovery.

Flash Magisk.

Reboot into system.

Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had

to select my provider under APN settings and then my provider under network selection because it auto selected the wrong

but working provider) Network takes a couple of minutes to kick in properly on each reboot.

Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM

Radio app runs but no sound), Dolby Atmos, Magisk all working!

Phone is now a LGLS991 and baseband unknown in settings.

EVERYTHING IS PERFECT!
[G4 Android Development] grantdb:
Do you think I will get any better than what I have by formatting Data?

Thanks!
[G4 Android Development] steadfasterX:
Thx for your report!

so basically u did this (including what we discussed on IRC):

unlocked with UsU

flashed the baseband package

created a full TWRP backup

Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)

flashed your backuped MM modem

flashed UsU kernel: h812_stock_boot_build-11-nougat.img

-> result: booted but calls had no sound

flashed N modem

flashed UsU kernel: h812_stock_boot_build-11-nougat.img

-> result: bootlooped

restored the full backup of the TWRP backup (means also: modem + baseband pkg)

-> result: booted, all working

Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).

Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)

-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had

to select my provider under APN settings and then my provider under network selection because it auto selected the wrong

but working provider) Network takes a couple of minutes to kick in properly on each reboot.

Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)

Flashing Magisk, Dolby Atmos

-> result: all working

Note:

Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.

Is that summary correct?

Cheers
[G4 Android Development] grantdb:
Yes that's it!

Thank you once again for all your work and help!

Cheers!

EDIT: The network only takes 40 seconds to start working on boot.
[G4 Android Development] mwahahaa:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
[G4 Android Development] steadfasterX:
your bootloader stack (all files mentioned in FAQ 18) must be on MM

you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)

you would flash the baseband package

you would boot

everything should work but give it time (15min to fully boot the first time)

you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)

reboot

give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually -

several times

if needed

you may need to set a cell network manually

you may need to reboot again

all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
[G4 Android Development] mwahahaa:
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
[G4 Android Development] steadfasterX:
Yea the backup is gold in many situations...

There is still one thing (at least) you can try :

Do a basic backup in SALT now if you have no backup anymore.

If you have made a backup in the meanwhile ensure you see the modemst1 and modemst2 and misc images there. If not: do a backup NOW and do not proceed until you have these!!

It is also a good idea to do a backup in TWRP including EFS and NO unlock state so you have 2 ways of a backup! Do not skip that. It's done in a second..

Erase the following partitions (part of the EFS and contains network unlock state too! Means you will loose the network unlock if any):

fastboot erase modemst1

fastboot erase modemst2

As said you will loose your network unlock if any and in some circumstances even the imei .

That's why it is important to have the above partitions as a backup.

Boot. Search networks etc.

When booted check imei (*#06# in the dialer), too.

If you loose cell service and imei is still there:

You may need to network unlock the device again and as that may not popup on boot you may must type a secret code in the dialer to open it manually (Google it)

When even that has no positive effect ensure you format data as described in faq zzz and re-do the above erase commands in fastboot afterwards. Then boot again.

You can restore the both partitions and so going back to the current state by either restoring by TWRP the EFS or flashing the SALT backup in fastboot :

fastboot flash modemst1 modemst1.image

fastboot flash modemst2 modemst2.image

This will give you any network unlock back and if lost imei too.
[G4 Android Development] nummer:
I flashed the any ARB stock rom + baseband package and i also have the result of no call audio... I need this!!!
[Tilt, TyTN II, MDA Vario III General] dgduris:
I cannot believe this.

My Tilt has stopped playing MP3 ringtones I had installed.

Evenin if I go to settings>sounds&notifications> notifications...and pick an MP3 file from the list it will not play. Doesn't matter if they are on the SD card or on the phone.

Any ideas anyone?
[Tilt, TyTN II, MDA Vario III General] NotATreoFan:
Need some more info...

Rom Version:

Radio:

Do other sounds play correctly?

Did this start after recently installing something?

Have you tried a soft or hard reset?
[Tilt, TyTN II, MDA Vario III General] dgduris:
Updated Tilt with stock ROM: 1.57.502.2

Radio: 1.27.14.09

Everything plays correctly. I can play MP3 in Core Player 1.2.1 or in Win Media Player.

I run phoneAlarm and can choose the tone in a profile and play it, but when a call comes in the phone reverts to the first non MP3 files it finds. All other profile info works fine, though.

I have uninstalled CP 1.2.1, reset and uninstalled, reset, reinstalled pA followed by another reset (all soft)...and to no avail.
[Tilt, TyTN II, MDA Vario III General] NotATreoFan:
I would suggest you try a hard reset and see if that fixes your problem.
[Tilt, TyTN II, MDA Vario III General] dgduris:
Yeah!

I am afraid that's what I'll have to do.
[Tilt, TyTN II, MDA Vario III General] dgduris:
David,

I couldn't wait! The possibility of hearing some pure cheese ringtone was keeping me up all night. So I went the hard reset route...no-doubt as you were posting this solution.

Likely it will come in handy as I'll be reinstalling whatever app changed that registry line to begin with.

Thanks.

Richard.
[Honor 9i  ROMs, Kernels, Recoveries, & Other Devel] Dipinkainikkara:
Hi please post all bugs here...
[Honor 9i  ROMs, Kernels, Recoveries, & Other Devel] GedeonTaylor:
Hello, please can you share the link of the beta test page/program? I'm interested.
[Honor 9i  ROMs, Kernels, Recoveries, & Other Devel] darshan.devadiga:
Which is the official site for bug reporting?
[Honor 9i  ROMs, Kernels, Recoveries, & Other Devel] Jimmyedagawa78:
Stock Recovery

I have twrp but didn't take a copy of my stock recovery. It would mean a lot if you could upload the stock recovery for honor 9i.
[Huawei Mate 9 Questions & Answers] leapdragon:
Hi all,

I have an MHA-L29 and it is currently running 8.0.0.360(C567). The security update is dated January 2018.

My company requires that my phone not have a security patch more than 90 days old. Is there a ROM compatible with MHA-L29 that has a newer security patch? What is the newest security patch available in any MHA-L29 ROM from Huawei, does anyone know?

And how likely am I to be able to install it? This is a retail US model phone, so far as I know.
[Huawei Mate 9 Questions & Answers] 5[Strogino]:
It's better to buy other phone :)

Your requirement is too hard to satisfy.

You have US region and latest version is 8.0.0.360.

Even if Huawei will post new ROM need 2-3 weeks more to test and approve.

Additionally Mate 9 released at November 2016. 15 months ago. No guarantee that 8.0.0.360 is not last...

Ok. There are other regions with newer security patch, like C636. But you have to rebrand your device (unlock bootloader, install custom recovery, install patched recovery) - so beat your security. Sure, it is temporary, but in advance you have to rebrand back if region C636 will not post next ROM in 90 days...

As I know, region C00 (China) has latest security patch and regularly updates. Rebrand to C00 if you are not confusing by hieroglyphs and specific memory manager (it is very aggressive to background apps)

P.s. to rebrand when using Oreo you have to rollback on Nougat's ROM, then rebrand using oeminfo in HwOta, then upgrade to Oreo.

This way cause oeminfos from Oreo are different with Nougat's files.
[Huawei Mate 9 Questions & Answers] leapdragon:
Gotcha. Thanks!

I was afraid of that. I'm OK with Android and Linux in general, but I don't want to do a lot of hard, risky work over and over again just to keep my phone running. Company is recommending Google Pixel 2 or iPhone. Not exciting, but I'm getting too old and lazy to hack my Android devices once a month. :P

Thanks for your help!
[Huawei Mate 9 Questions & Answers] 5[Strogino]:
Good news!

Version 366 appeared in FF. It has security patch from 1 March. But you need wait till it approved by Huawei.
[Huawei Mate 9 Questions & Answers] leapdragon:
Wow, thank you for letting me know! I'll re-install the app and keep watching! Thanks again!