yashsingh1/xdaforums huggingface dataset:
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Guides, N] Oniwab4n:
Thank you for this camera but its not working on havoc rom
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Guides, N] BrimoFan123:
Can the OP author provide information what huawei camera's version it is? Is it for instance com.huawei.camera Version 8.0.0.200 or com.huawei.camera Version 8.0.0.301 or what? Also it would be fair if OP author will collect and inform on first page on which Huawei devices with what ROM that huawei camera app works.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Guides, N] The Harmony Weaver:
file not found
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Guides, N] flamedrops:
link updated, due to askuccio deleted his file on xda. new link available.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Guides, N] The Harmony Weaver:
Not working it crashes
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Guides, N] LucXas:
someone hast the file?
[OnePlus 5T  Questions & Answers] Youtube_Ll0r3nt3:
Can anyone who is in the latest beta version upload all the system framework, I think I accidentally deleted the clipboard ... thanks
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Rekovni:
Hey all.

I just flashed my Qtek 2020(T-Mobile) with the nk.nbf and Radio_.nbf files from C_ShekharWM6.1.1cR16.P32_public without any errors. Everything works great except GPS. Every time when I use GPS in TomTom now the whole device freezes. I get the following message in GPS Test before the device freezes.

Scanning COM2:

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

Connect To

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

'38400 Default

Status: Opening Port

Cancel | Hide Status

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

I'm using a cable to connect to the GPS device. Any help on this subject is highly appreciated.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Jadel:
What sort of GPS device are you using?

And where are you connecting the cable to on the XDA?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Rekovni:
Well, the GPS device doesn't have any brand or serial number on it so I really don't know. But it was working fine before the flash. I'm using the connector at the bottom of the device.

I think it has something to do with flashing the Radio_.nbf file because I've successfully flashed this device multiple times before with only the nk.nbf file from different releases.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] muckelmaus:
Serial Cable GPS

Normally Cable/Serial GPS are connected to the COM 1 Port 4800 Baud.

Remember to uncheque Settings/Connections/Beam because IR uses the same.
[General Questions and Answers] Pawprints1986:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
[General Questions and Answers] KIBS2173:
Try This

Hi there,

Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you

You can try and use this website as I Prefer this website than Sam mobile

The website is www.updato.com
[General Questions and Answers] Droidriven:
First of all, if the bootloader is locked, you can't flash a custom ROM, so that shoots that idea in the head.

Second, a custom ROM is basically only a system.img and kernel. Even if you were able to flash a custom ROM, your stock bootloader is still there. Flashing a custom ROM will not change whether or not you can downgrade the bootloader, the part of your device where bootloader is located is unaffected by any custom ROM or system.img.
[General Questions and Answers] Pawprints1986:
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?

Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares
[General Questions and Answers] KIBS2173:
Try This

Hi there,

well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0

I was however able to update the phone from version 5.0.2 to 6.0 using ODIN

and the phone rebooted with new boot loader, recovery, and even it has a new downloader.

The phone was working alright but it didn't had any playstore.

I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason

So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.

And it was flashed successfully.

And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.

And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.

Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.

So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version
[General Questions and Answers] Droidriven:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
[General Questions and Answers] KIBS2173:
Try this

Hi there,

Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong

BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE
[General Questions and Answers] Droidriven:
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.

What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
[General Questions and Answers] KIBS2173:
TRY THIS

Hi there,

Yeah they were for the exact phone and model. For some reason SpFlash Tool bricks Mediatek Devices. I think someone should create another version of spflash tool just like ODIN. Odin is actually a great software to flash all Samsung devices I Had no problems with it.

But Spflash tools are still in Beta mode. The software is not reliable.

I had to get a new motherboard for my device because of the hard brick however my pc is still able to detect the device but it won't install the firmware. Keeps on giving me error 4032 something like that.
[General Questions and Answers] Pawprints1986:
Can you lead me to anywhere explaining how to do this in detail?

I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...

I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.

Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
[General Questions and Answers] Droidriven:
Here is a guide to extract the two firmware files.

Extract one firmware in a folder of its own and extract the other in its own folder.

https://www.rwilco12.com/forum/showthread.php?tid=74

You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.

https://xdaforums.com/showthread.php?t=2446269

Or this guide

https://www.rwilco12.com/forum/showthread.php?tid=92

***NOTE***

Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
[General Questions and Answers] Pawprints1986:
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night :)

I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! :) it sounds safer than just leaving components out completely
[General Questions and Answers] Droidriven:
Also, do some Google searches for:

"How to port Samsung stock firmware"

Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
[General Questions and Answers] Pawprints1986:
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.

Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
[General Questions and Answers] Droidriven:
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
[General Questions and Answers] Pawprints1986:
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.

I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
[General Questions and Answers] Droidriven:
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
[General Questions and Answers] Pawprints1986:
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.

Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.

I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.

The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.

so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there.

ETA: So I just decided to go through everything once more, and decided to keep certain files as bin files like original, and the other files as img, as they were originally within the oreo rom. I was mistakenly thinking that all files had to be either img or bin, but upon another check through i did notice that the file type within the same rom can vary. I feel better about that now :) Still just working on the courage to flash it. I didnt truly edit any of the files. I only either renamed the extension thereby converting types of files. otherwise i only decompressed and then recompressed things. I didnt do any true open notepad and edit type stuff. Just sticking with the basics here :)
[General Questions and Answers] Droidriven:
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.

I can't say that I'm 100% certain about this, but..

As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.

I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
[General Questions and Answers] Pawprints1986:
This is becoming so beyond frustrating... I went though tonight, deleted my previously modified files... I wanted to go through and only undo the lz4, without all that renaming I had done. Did that just fine.

Gather up the guts to finally try it in odin though? Well, i dont even know what the error is. In odin 3.13, it gets to "file analysis" and just sits there. I unplugged and was still even able to restart the device back in to the oreo that was still on it, it did nothing at all. So i did a little bit of searching and it seems that an older version of odin fixes this. So i downloaded the recommended 3.09... Odin gets to the same point and then the program straight up shuts down! Ive even tried compatibility mode for windows 7 thinking maybe. I had ran it as administrator each time.

so the phone is fine.... but i cant get the program to even try it let alone give me any kind of error to work with....

ive given up for tonight!

The other idea i had was to check "phone bootloader update" in odin and just try to flash the straight up marshmallow rom, but googling that gets mixed results.
[Treble-Enabled Device Questions and Answers] lqqsdz:
My mobile phone is lgv30 (vs996), and the mobile phone system is PixelExperience P GSI. The problem is that after the mobile phone restarts, the status of the SIM card is not in the service. Others can't notify me by phone. How to solve it? Thank you
[OnePlus 6 Questions & Answers] ChrisChris123:
I am currently on Open Beta 3 for Android P, and I am confused about if I have to revert back to OOS 5.1.11 to get Android 9.0 official update, or I have to wait till I get it in my settings -> update on Open Beta 3
[OnePlus 6 Questions & Answers] ChrisChris123:
I just downloaded the (incrememental update) from oxygen updater and I am not rooted without twrp. Should. Just straight update it in settings with the downloaded update? Or do I download the full package and go into recovery and wipe. Please reply ASAP with detailed explanation.
[OnePlus 6 Questions & Answers] jeromejeremytay:
Just use Oxygen Updater, download the incremental package. When it's done, go to settings, software update, local updates.

Did this yesterday night, no root.
[OnePlus 6 Questions & Answers] ChrisChris123:
Do you need to wipe in recovery afterwards? And also I tried but it says you cannot downgrade on settings and update
[OnePlus 6 Questions & Answers] yashpatel99:
You would be on a stable release. We are talking about upgrading from beta to the stable pie release.
[OnePlus 6 Questions & Answers] ChrisChris123:
So would I have to downgrade back to stable 5.11 Oos? If so, how?
[OnePlus 6 Questions & Answers] VEndymionV:
I'm also on Open Beta 3. I hope OTA comes out without having to make a factory reset...
[OnePlus 6 Questions & Answers] kobon100:
I have the same problem. I'm on BETA3 after downloading the last version with Oxygen

updater I tried to install getting a message that the version I try to install is older then what I have
[OnePlus 6 Questions & Answers] RiTCHiE007:
Thats because you cant update the beta with this official release so you have to flash it from twrp
[OnePlus 6 Questions & Answers] GuestK0062:
For those of you who are on open beta builds ,you would need wait for the download link to be published on downloads.oneplus.com , and as mentioned in the beta posts ,Moving back to the Official OTA path from the Beta path will require a full install and clean flash (full wipe of all data and cache).

Source
[Xiaomi Redmi 3s Questions & Answers] SS Technical:
I download mini arm 64 gapps from opengap official website but it's name like this 'open_gapps-arm64-9.0-mini-20180922.zip.crdownload' then I removed crdownload and make it zip but when I select this gapps in twrp and swipe to flash then it's show its corrupted

What I do guys

Art my English is bad

Thank u
[Xiaomi Redmi 3s Questions & Answers] Darkstar085:
because it is not downloaded fully.. Redownload
[Xiaomi Redmi 3s Questions & Answers] Yaseen Yash:
No need to edit/remove that .crdownload extension... It will automatically disappeared when it is completely downloaded
[Xiaomi Redmi 3s Questions & Answers] SS Technical:
Thanks guys problem is solved
[Xiaomi Redmi 3s Questions & Answers] Bayu099:
Its mean your download is interrupted, Download using adm app, you can download this app from playstore,
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] klabit87:
ONLY FOR Qualcomm SM-N9600

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

This will trip knox to 0x1, your phones warranty will be voided, flash at your own risk. Also, this process will wipe your personal data!

HOW TO INSTALL:

0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled.

1. Boot into download mode by pressing: bixby, volume down and power

2. Download the latest Odin version, open it

3. Download the recovery file from below and put it into the AP tab

4. Untick "auto reboot" in odin and flash the file

5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop).

6. In order to fully and properly root, you will need to flash my kernel found here and flash Magisk.

7. To disable encryption you need to flash this RMM_patch+forceencrypt_remover.zip for pie or multidisabler.zip and forceencrypt_disabler_q.zip for Android 10 and format data. (can opt out of the forceencrypt_disabler if you want but internal storage will be inaccessable)

DOWNLOAD:

https://twrp.me/samsung/samsunggalaxynote9qcom.html

BUGS:

- Samsung encryption is NOT supported

DONATION:

Via PayPal

https://www.paypal.me/klabit87

Contributors

klabit87

Source Code: https://github.com/TeamWin/android_device_samsung_crownqltechn

Version Information

Status: Stable

Current Stable Version: 3.3.1-0

Stable Release Date: 5-12-2020
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] klabit87:
Reserved #1
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] jrkruse:
Nice job
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] Mentalmuso:
Awesome. Good stuff.
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] jal3223:
Yeah [MENTION=4168602]klabit87[/MENTION] Awesome work man! Thank you so much for doing this for us!

Everyone that uses this needs to donate to this guy. He doesn't even own the device and still went out of his way to compile and test this for us. He's a great developer.
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] klabit87:
Mtp and adb do not work right now. I will work on that this weekend.
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] craazy82013:
Klabit on a roll. Whoop whoop
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] Albe96:
Good Job Buddy! QCOM users can have some fun now! ?
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] klabit87:
Thanks! Just remember this is a beta so don't judge harshly please [emoji23]
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] Albe96:
I'm Exynos user.Just congratulating for bringing up.For fixing MTP,ADB I advice you adding USB Configs in Ramdisks and also make sure partition name is correct in fstab.Good Luck,Hope you'd contribute Qualcomm user with some ROMs they could enjoy !
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] ALUCARD4DEAD:
Incredible news!

There already roms compatible with snapdragon variant? or only root?

And nobody knows if this model are on project treble?
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] TheUndertaker21:
All 8.0 phones are treble compatible.

Phone that shipped with it anyway
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] suzook:
Should have no issues with treble roms. Snap int s9 runs aosp roms.
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] clarkcant:
I thought that you were not able to unlock the bootloaders on Snapdragon Samsung devices (I have an S8)?
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] Cozzeck:
Yeah, what SD model has the OEM unlock option in the dev options?
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] shoeprano27:
i cant use this on my sm-n960U1, can i?
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] woahh:
Could we flash a magisk img and root like that through your TWRP? Thanks babe!
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] TheMadScientist:
This thread has been cleaned now let's keep the rude off-topic comments down
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] klabit87:
Yes imgs work fine as recommended in the op
[Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, ] woahh:
Wow you're so awesome! I know you said this in your post saying it cant flash zips, do you have any tips and tricks on flashing magisk through twrp ?