yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J7 Questions & Answers] IsaiahWade:
Correct. Thanks ill try that.

is it normal that my carrier switches to sprint when i flash the stock rom? when i flash CSC it switches back to boost :confused:
[Samsung Galaxy J7 Questions & Answers] IsaiahWade:
The memory card thing worked! i forgot i had formatted it as adoptable storage before.

after formatting it actually let me flash the zip this time :o

only thing is i got an error right at the very end

Unable to repack boot image!

-unmounting partitions

Updater process ended with ERROR: 1

Error installing zip file '/sdcard/Magisk-v16.0.zip

updating partition details

. . . done
[Samsung Galaxy J7 Questions & Answers] peter couniaz:
J727P

Ok do the firmware thing then factory reset in the stock recovery ! Then flash twrp in Odin with auto reboot unchecked in options ! Then pull an replace battery ! Then boot right into twrp an flash superSU SR5 2.8.2 zip an reboot ! Or you can boot twrp an Rom instead !
[Samsung Galaxy J7 Questions & Answers] dodo2244:
Glad to be of help. Peter's tricks should solve your final hurdles.
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Reserved 1
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Reserved 2
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
This is going to be useful. Personally I just want to run custom O as primary and N as a secondary. Mainly because O doesn't have properly working Daydream and for a couple of games that aren't compatible anymore with O. If I'm only trying to attach LOS14.1 as secondary I wouldn't need to patch anything extra O from this guide? Though I can't install the patched ROM it gives an error.

Edit: Oops missed reading from the old guide the primary ROM needs to be stock. I guess I need to patch then. Do I need Linux to do all the editing?
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Actually yeah, if your custom O is primary you don't need to patch it(the kernel, I mean)! You still need to patch the ROM so that it doesn't wipe /system when you OTA update your custom O, which means you need an unpatched custom O stock kernel flsshable zip(sorry for the mouthful). But if you don't OTA update then no need :) The last I tried, using stock ROM as secondary worked for me though? Didn't find any issues. But I might just be lucky, be careful if you try that.

As for your last question, nope all these commands are meant for Terminal Emulator app on an Android phone! Just use the binaries in the attached files.zip, they are all compiled for Android and do not work on Linux desktops. All the best :) If you need help just ask here!
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
Figured out the error after dual boot patch on LOS14.1 was my mistake in modifying the update-script incorrectly. Nothing to do with N/O/this guide. However now I tried installing it to data slot so dirty flashing and restoring the system partition won't be complicated. The issue is trying to boot primary it vibrates five times at ZTE logo and goes to recovery. Trying to switch to primary in dualbootutilities gives an error something like (from memory) data/media/0/boot.img cannot be found. I guess DBP installed even on data changes the structure of boot and primary on O doesn't fit so can't boot. Just want your advice, it probably means patching O when O is primary is necessary then?
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Oh you mean you flashed custom O, and after that you flashed you N data slot ROM? You're partially right, if you flash your data slot ROM after a non-patched ROM, you'll have the data slot kernel installed i.e. the LOS 14.1 stock kernel, which cannot boot an O ROM. This is because DBP works by storing multiple kernels on your /data/media/0/Multiboot folder, when you 'switch ROMs' actually what happens is DBP flashes the kernel of the ROM you're switching to. Obviously a N kernel cannot boot an O ROM so you cannot boot. Unfortunately, DBP only stores kernels that you flash with patched zips(i.e. if you flash a DBP-patched ROM/kernel zip, only then will DBP store the kernel in its custom Multiboot folder). So because you didn't patch your O primary ROM, its kernel is not saved and you cannot use DBPUtilities. What you can do is either make your own non-patched kernel zip file for your O ROM's stock kernel that you flash everytime you want to switch to primary, or you patch your primary ROM and then you can use DBPUtilities. However B01 kernel has a slightly different precedure for adding DBP support that this guide doesn't explain(I'm sorry) :( I'll update it when I find time. Don't follow this guide to patch B01! It won't boot, I tried :( But I know what changes to make when modifying a B01 kernel don't worry
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
lost this post when I pressed reply. This RR-O Kranoner 20180511 has the fstab.qcom and init.qcom.rc still on root / directory. But patching only DBP patching hellsgate kernel after having LOS14.1 on data slot 1 still has the same issue. Alternatively installing the mod boot.img allows primary to boot but after using DBP utilities to switch to data slot 1 (onscreen says success) the data slot 1 gets stuck on ZTE logo with 5 vibrates instead. Even tried flashing the final Beastmode 14.1 kernel DBP patched to data slot 1 after switched, five vibrates to recovery.

Lost Magisk install after step nine. Just reinstalling it is fine. Did you forget the flashable zip template by the way?
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Oh hmm did you install the right version of Hellsgate for your data slot 1? I think LOS 14.1 needs a very old version(R2.1? I think). I'm not sure about beastmode kernel though, I'm sorry :( And thanks for the reminder about the zip template, o dear I forgot about it I'll upload it now!
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
Sorry that post was worded poorly due to rushed recalling. I meant RR-O primary had Hellsgate kernel patched by this guide, which shouldn't be necessary as the two issue ROM files are still on root directory (patching with DBP instead didn't work as I posted before)? Still had to install the mod boot.img to manage to boot but then data slot 1 LOS14.1 won't boot. I was going to try patching with this guide the kernel I intend for LOS14.1 but it's lacking the image.gz-dtb file, I'd only patched it with DBP and that should be enough as it's an N ROM. I guess I could use an older hellsgate suited to N but Beastmode was updated til a little later so I'd prefer it.

Thanks for the zip template. Just checking, it's not actually needed if I can just install the modded boot.img directly in TWRP anyway?
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Oh you're right, if the 2 files are still present you don't have to patch using this guide. Just checking, what version of hellsgate are you using for primary? And yes you're right! N ROMs/kernels don't have to be patched with this guide for DBP :) I'm not very sure why you can't boot and get the 5 led flashes though :(

As for your last question, you're right no need this zip in you install using TWRP.
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
The last B32+10 hellsgate v3.0. Dunno but the guide did manage to allow primary to boot whereas it wouldn't before. Both N hellsgate and beastmode are lacking the image.gz-dtb so I can't patch them. I guess I'll try stock next, I really wanted KCAL to use on Daydream tho ::crying:. If that fails I might try stock N as primary when I'm about to clean flash update O.
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Oh dear I'm sorry to hear :( Just checking are you using LOS 14.1 builds from 2018? I might know what's wrong
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
yeah latest official
[ZTE Axon 7 Guides, News, & Discussion] haoyangw:
Oh I probably should add this in the OP, Nougat builds with 2018 Security patch level behaves the same way as Oreo ROMs, they also have the init.qcom.rc and fstab.qcom in /system. So I would believe that latest LOS 14.1 also needs the exact same patching method as Oreo(if you can check and confirm this that'll be great). I haven't analysed the Nougat hellsgate and beastmode kernels so I'm not sure how to patch them, I'll let you know asap when I find out something. Sorry about the mistake, I didn't realise there's still a Nougat ROM being regularly updated
[ZTE Axon 7 Guides, News, & Discussion] Infy_AsiX:
Great thanks for the guide and mods. Sorry for the late follow up, it did take awhile to get working. After some confusion and trouble with figuring out how some O ROMs still don't use the early mount method. While N ROM and kernels don't in fact need patching by this guide. Also B12 can't be dual booted with any N ROMs due to bootstack incompatibility (flashing bootstack after a DBP install doesn't seem to take effect to help). My target kernel was Hellsgate 3 for B32+10, which oddly needed fstab.qcom modded per guide but not init.qcom.rc all despite the kernel being for non early mount ROMs. Yes really, after all of that figured out, I got it working!

I'm glad to report it works as intended with the right setup. Now with B12 ROMs currently all affected by the wired audio cpu extra 50% load bug, using B32+10 is a working fallback. The trade off being apparently dual-sim issues (reported by some as present, some not), no GCam HDR support and improper hi-res audio support (though hi-fi DAC was already working and hi-res is debatably useless). In any case if dual booting O with N is desired B32+10 is the latest supported available with above stated differences. This is the only way presently for using a stable-ish O ROM and N's fully functioning Daydream and a couple of AAA games deprecated after N such as Fahrenheit: Indigo Prophecy and Jade Empire. Now I can also play around testing Kranoner's N Vertex EAS supported ROM and kernel.

I've attached the B32+10 Hellsgate 3 modded per this guide using Kranoner's 180511 RR-O for anyone interested in getting it straight working without the mess. A few pointers. The zip still needs needs to be patched to primary/secondary/whatever chosen slot before use. Magisk has to be reinstalled after installing the modified kernel, primary Magisk zip does not need DB patching. Using secondary slot, to fill up like huge wasted space 6GB system partition is smart if you're not installing many apps.
[ZTE Axon 7 Guides, News, & Discussion] chaopac:
////[removed]////
[ZTE Axon 7 Guides, News, & Discussion] Deleted member 5437200:
Tried this with my device and it didn't work. Alcatel Tetra with 8.1 Stock. Runs GSI images up to 10. MT6739 SOC. Doesn't boot if you simply remove the entry. Couldn't even change ro to rw and have it boot. I was able to remove verify and that was about it. I was able to get the fstab and init file migrated back to ramdisk and it booted once i modified the init file to point to the right locations. I got DBP supporting my treble device properly. The last step is to figure out how to disable/remove the system early mount. This topic seems dead but I figure it's worth a try. I've been working on this Project on and off for 2+ months now and would really like to hit paydirt.
[ZTE Axon 7 Guides, News, & Discussion] mrrocketdog:
you do realize this is an Axon7 thread , yes?
[ZTE Axon 7 Guides, News, & Discussion] LgPWN'd:
I'm Sure he's not lost .

U realize this is a place Dev's take ideas from each other and try to port it to other devices Right?
[ZTE Axon 7 Guides, News, & Discussion] :
Nicely put, thanks for the backup
[Treble-Enabled Device Guides, News, & Discussion] Jax:
I love the Oxygen OS navigation gestures,can someone build gsi of this OS.
[Treble-Enabled Device Guides, News, & Discussion] BLINGER-PC:
Yeah that would be great
[Treble-Enabled Device Guides, News, & Discussion] Jax:
Yes
[Treble-Enabled Device Guides, News, & Discussion] awells845:
Sadly Oxygen OS is OnePlus's proprietary software, optimised for there devices. I wouldn't know why you would want it in GSI form for other devices as you can get GSI roms that are close to AOSP and some with dark mode theming features.
[Treble-Enabled Device Guides, News, & Discussion] Jax:
I want that oxygen os gestures with those animation,i heard that oxygen is is open source
[Treble-Enabled Device Guides, News, & Discussion] BLINGER-PC:
Though there are gesture in rr rom but they don't have any animation
[Treble-Enabled Device Guides, News, & Discussion] Jax:
They are bit slow,looks glitchy
[Treble-Enabled Device Guides, News, & Discussion] steven360:
Hmmmm, I'm actually very interested in this request. This seems like a really unique idea. I know [MENTION=1844875]CosmicDan[/MENTION] is working on a MIUI port, so hopefully we get some support for this too.
[Treble-Enabled Device Guides, News, & Discussion] Yozak:
This will never happen as OxygenOS is closed source. If you want the navigation gestures check out this app: https://play.google.com/store/apps/details?id=com.ivianuu.oneplusgestures
[Treble-Enabled Device Guides, News, & Discussion] Jax:
Tried it
[Treble-Enabled Device Guides, News, & Discussion] fxsheep:
MIUI is closed source too.
[Treble-Enabled Device Guides, News, & Discussion] Saxithon:
If it's closed souce, then what's that

https://github.com/OnePlusOSS/android/branches/all

Gesendet von meinem LG-H930 mit Tapatalk
[Treble-Enabled Device Guides, News, & Discussion] Ani96:
Miui is open source since 2012 and Oxygen os also is an open source android os since 2016.
[Treble-Enabled Device Guides, News, & Discussion] Twisted Prime:
MIUI is open source
[Treble-Enabled Device Guides, News, & Discussion] Jax:
No miui sources are closed after miui 8 marshmallow
[Treble-Enabled Device Guides, News, & Discussion] Yozak:
This is just the kernel source that they are legally required to release. A simple Google search will reveal that.
[Treble-Enabled Device Guides, News, & Discussion] VincentJoshuaET:
:facepalm:
[Treble-Enabled Device Guides, News, & Discussion] aswin_a_s:
https://xdaforums.com/lenovo-zuk-z2/development/oxygen-os-beta11-port-z2plus-t3815067

It's treble. But not GSi:rolleyes:
[Treble-Enabled Device Guides, News, & Discussion] IndifferentBear:
because we do? i mean i have resurrection remix on my blu vivo Xi+ but i would still like to possibly have a port of that, and its already happening right now. search it up up xda lol
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] thomas.raines:
Greetings all!

Introducing LightningZap! kernel for the Moto Z2 Force. It is based off Pantheon kernel with some of my own little tweaks and enhancements to improve performance and battery life.

Pantheon features:

Upstream kernel from source

Edits to avoid Safetynet/CTS (If you have root, it will fail signature check inherently without SUhide or Magisk hide)

Disabled CRC check

Disabled dm-verity

Over Clock / Under Clock on CPU Frequencies added:

Little CPU: 175 MHz, 230 MHz, 2035 MHz

Big CPU: 175 MHz, 230 MHz, 2476 MHz; 2592 MHz

Slight undervolt (our device is overvolted compared to other msm8998 devices)

UC GPU (added 180 Mhz step for battery savings when web browsing, low GPU usage)

OC GPU (changed 710 MHz to 750 MHz)

Same Adrenoboost tweaks as the Pixel 2 ElementalX kernel.

Wakelock fixes by Boeffla

Added Zen, FIOPS, BFQ, and SIO IO schedulers

LigthningZap! Features:

Insane readahead tweak: No need to raise readahead cache with a kernel tweaker. With this tweak all partitions are set to their maximum readahead possible and is handle by the io-scheduler. This tweak is best used with FIOPS (set by default), BFQ and SIO schedulers. I haven't ran many tests on other schedulers.

LightningZap! sysctl tweaks: Adjust values for kernel system controls for better performance and battery life.

Lionheart governor added: This is the recommended governor for LightningZap! kernels. I have set the dbs_tuners_ins.sampling_rate and min_sampling_rate to 100 (lowest value)so the end user can adjust the values in their favourite kernel tweaker add to suit their needs. It's very simple, when setting the sampling rates, a high number will improve battery life but performance will take a slight hit, and a lower number will increase performance but battery life will take a small hit. Values for these range between 100-1000. This governor is not set by default, but can be set with you favourite kernel tweaking app

Aroma Installer: Same options as in Pantheon kernel for now. More to come as I work them in.

Compiled with Linaro 4.9 only (no clang here)

See second post for fixes, improvements, changelogs, and downloads

Source code: LightningZap! kernel for nash

Flashing Instrcutions:

Device must be rooted with custom recovery (TWRP)

Place LightningZap! kernel for nash on sdcard

Reboot to recovery and flash .zip

Follow on screen prompts

Re-flash root (Magisk)

Reboot, wait 15 minutes, and enjoy

For further adjustments, I recommend Kernel Toolkit

I wasn't going to post this kernel, but since there is very little other support and options going on with this phone, I changed my mind. I ask everyone to keep things civil, do your best to stay on topic, be patient when asking/answering questions, try to search for an answer before you post a question, and PLEASE make a backup.

Special thanks to Uzephi for the base source code (Pantheon Kernel)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] thomas.raines:
Fixes, Improvements, Changelogs, and Downloads

LightningZap! kernel for nash v1.0 (Download link)

Insane readahead tweak (v2)

LightningZap! sysctl tweaks

Lionheart governor

Aroma Installer

Compiled with Linaro 4.9 only (no clang here)

USB Tethering fixed
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] matheusgcdj:
Working on LineageOS?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
He used my LOS base. Will work on LOS, but not other AOSP ROMs. [MENTION=4145127]thomas.raines[/MENTION], you might want to start merging from o8x-caf. Your kernel is at 4.4.132 latest stable is 4.4.138. (Just going off your git). It might make WiFi break with LOS, but [MENTION=5848265]npjohnson[/MENTION] stated they will be merging those caf commits in the very near future where you don't need two forks anymore.

Thanks for the USB tethering fix as well. Merged into mine today and sending a release shortly.

Edit: oh, yeah, verity bypass isn't in my kernel anymore, so if you want to add it, you might want to pick it from EX, Franco, or Kirisakura kernels. Didn't see the point, so when I rebased, I didn't pick it in.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] thomas.raines:
Haven't tested. Would be nice if you tested for me...

I'm using your AOSP branch (I thought)... It's working on AOSiP flawlessly. Thanks for the heads up on the verity bypass. I'm actually working on that now, but not sure if I'm going to or not... Glad I could help with the USB thethering...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Pantheon branch is stale, o8x-caf is current.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] KelleyCook:
Motomods?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
If it comes off my source, Motomods should work.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Removed the stale branch. My source just got 4.4.139 merged into it. I use Nathan Chancellor's msm-4.4 tree if you ever don't want to wait for jbats or I to push the Linux-stable commits.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] thomas.raines:
Just merged the 08x-caf branch... Thanks
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] McRoberts:
So if flashed on stock and it broke my Wifi how do I go about fixing it? This Moto Z2 force is like starting all over. I thaught i was good at this once? Other than no WiFi the kernel works great. Thanks for the development this phone needs all it can get.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] zZLord:
I got a bootloop. Any advice?

I'm on Lineage OS 15.1-20181106.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Unless OP updated for Treble (mounting /vendor instead of /oem) this won't work on Treble. Any LOS built after August is Treble enabled. Try with DU official.
[Nokia 6.1 Plus (X6) Questions & Answers] Gin.Or.Juice:
Hi guys,

I just got a Nokia X6 on Android One shipped from China and for some reason it defaults continuously to H+ instead of LTE on my Cricket network. On my Network Type option in the Setting In only have 3 options 2G, 3G and 4G and I have 4G selected, but still H+ is being used by default even in areas where I used to get full LTE signal.

I have tried however to get into the Android Testing Menu (by dialing *#*#4636#*#*) and change the Preferred Network Type to a few options like LTE/UMTS auto (PRL), but for some reason is the H+ that is picket all the time. even in areas where I know the LTE signal is strong. If I select "LTE only" from that menu, then I'm getting on LTE but as soon as I go into weak signal region, the signal drops completely, while not the same thing I can say about the other option, when the H+ connection is present in the same weak signal area.

Another thing that I see in the Android Testing Menu is that my VoLTE provisioned option is Off and I can turn it on.

Do you guys have any ideas on how can I get this device connected to LTE when the signal is strong?
[Nokia 6.1 Plus (X6) Questions & Answers] iSingle:
I have a Nokia X6. I put two SIMs into it, both show 4G.
[Nokia 6.1 Plus (X6) Questions & Answers] zaid0102:
I have some problem to connect data or mobile internet. Grammen phone provider.
[Nokia 6.1 Plus (X6) Questions & Answers] AndG404:
I was ready to purchase one, however, was curious if this would work on t-mobile. If so, would the Wi-Fi calling work?
[Nokia 6.1 Plus (X6) Questions & Answers] sandalks:
Did you already checked if your 4g network band compatible with your phone?
[Nokia 6.1 Plus (X6) Questions & Answers] Xkernels:
Android One:confused: TA-1099 or TA-1103?

For TA-1099

Network 900MHz, 1800MHz, 850MHz, 1900MHz, 800MHz, 2GHz, Band 38, Band 39, Band 40, Band 41 (2555-2575 MHZ, 2575-2635 MHZ, 2635-2655 MHZ), Band 1, Band 3, 1.9GHz, I , II, V, VIII

Data Service LTE Cat. 4, 150Mbps DL/50Mbps UL
[Nokia 6.1 Plus (X6) Questions & Answers] brunonemer:
Could someone upload the bands for this phone? I'm not sure about get it, I need to know if TA-1103 have the LTE B4, in some sites said yes and other no.
[Nokia 6.1 Plus (X6) Questions & Answers] Xkernels:
TA-1103 LTE Band 1, 3, 5, 7, 8, 28, 34, 38, 39, 40, 41

https://imgur.com/a/SqSj1Tg

https://imgur.com/a/oDBAiOe

https://imgur.com/a/QAnFBVG

https://imgur.com/a/glcUhMc

https://imgur.com/a/SXYMKfM
[Nokia 6.1 Plus (X6) Questions & Answers] Bookworm Yevgen:
So, have you solved your problem?

If the ROM of your phone is "CN" you could try to flash the phone to the global ROM 2_29(WW) or wait for a new update of the firmware. You haven't noticed the firmware's version. Have the phone got any updates?
[Nokia 6.1 Plus (X6) Questions & Answers] Gin.Or.Juice:
I just returned the phone and got an LG G7 instead. The X6 that I was using also had a problem with Bluetooth as I was never able to turn it on.
[Nokia 6.1 Plus (X6) Questions & Answers] Edwinc:
Manually switch the preferred network type.

I am using the latest Stock Android version on Nokia 8 and struggled with this issue too. I tried everything I could possibly do.

The simplest answer is to go into network settings and select 2G, give it a minute to find it. Do it for 3G too. Give it a minute to find it. Then 4G, same thing. Finally select 4G as preferred network type and that should do it.

It looks like the default preferred network type is 3G from the factory.
[Nokia 6.1 Plus (X6) Questions & Answers] salah khan najmi:
guys i cant even access my mobile data connection can anyone tell how access it

thanks

By salah