yashsingh1/xdaforums huggingface dataset:
[Motorola Atrix HD] drksam:
Follow up

Ok so I found that the .xml file can be loaded with RSD lite in windows. Since I use linux I found the script for flashing xml files with fastboot from root junkie. I followed the instructions and got it to start flashing. During the first file upload it returns an error md5 mismatch. So I found another "stock" image and tried again to the same end. I then compared the md5 sums to the ones in the .xml file and they are correct so there downloading to the pc fine.

Today I borrowed a windows computer and downloaded RSD lite and the "stock" roms. When RSD tries to flash to the phone I get the same md5 mismatch but it adds "phone returned fail". I can still flash back to cwm useing fastboot and boot in to cm just like before I started this.

Any ideas as to why the stock images won't flash?

I'm beginning to wonder if the usb cable could be questionable. Is it posable that it may load cwm over a kinda bad cable?
[Motorola Atrix HD] drksam:
I tried removing the md5 sums from the xml file. It then flashed to the device with a few errors. Now the phone just boots directly to fastboot it says reason flash fail. But now I can't flash cwm back I keep getting FAILED (data transfer failure (value too large for defined data type)).
[Motorola Atrix HD] drksam:
Now I have bought another motorola atrix hd rooted ubl and installed cwm. I created a zip of its image from cwm and installed it on my old atrix. I know thats a little much to have to do but i couldnt find a working image for the atrix hd. Now the phone comes on and most things work good But I have now LTE radio no WiFi and no bluetooth they worked in cm before all of the trying to get back to stock. Im not sure if the problem was caused by the install from the cwm zip or from some of the messing around i did first. I have found info about flashing "NON-HLOS.bin" but when i try i get the following.

$ fastboot flash modem NON-HLOS

.bin

(bootloader) Variable not supported!

target reported max download size of 31457280 bytes

Invalid sparse file format at header magi

sending sparse 'modem' (28172 KB)...

OKAY [ 2.509s]

writing 'modem'...

(bootloader) Unknown chunk type

FAILED (remote failure)

finished. total time: 4.414s

I have read that there is a special mfastboot for windows but i only have ubuntu. I suppose this could be why the flash from RSD for linux didnt work. Could that be possible?

Am i going to have to get a windows computer to do this?

After trying to reboot post failure of modem flash I had fastboot forced because of a failed flash. I tried to flash the logo file from the same image as the modem file and the logo worked fine then the phone booted fine but still no radios :(
[XDA Assist] Mallos31:
I have spent the last few hours researching and though I have rooted a good number of phones in the past, this one is stumping me. There's a number of "single click root" applications but for one, I don't often trust those, and two, most say they're for android 4.1.1. My phone was 6.0.1 stock out of the box. I have the SDK I have adb working just fine, but I can't get too much further with the root. Any help is greatly appreciated.
[XDA Assist] xanthrax:
Hi !

I won`t recommend any rooting methods unless they are described and well supported here on XDA but , unfortunately , your device doesn`t show up here so better try a Google search and carefully read it

A good start you can have here https://xdaforums.com/android/help

Good luck !
[ZTE Axon 7 Questions & Answers] ramnkc:
Folks,

Anyone facing issues screen color over saturated with stock rom? Any one had any tools or apps which can re-calibrate or fix it?
[ZTE Axon 7 Questions & Answers] Oki:
If you have rooted your Axon 7, then you can install the Color Control app. This app will allow you to calibrate the screen color. Should this app doesn't work, flash the KCAL kernel patch for adding this feature to the stock kernel.

Enjoy!
[ZTE Axon 7 Questions & Answers] ramnkc:
If i'm not rooted then is there any other apps i can use? Thanks anyway ! :)
[ZTE Axon 7 Questions & Answers] Oki:
No, the kernel doesn't support this hardware feature and the app requires root access to modify the settings. So the only way is unlocking the bootloader and rooting the device.
[ZTE Axon 7 Questions & Answers] ramnkc:
noted, probably need to read thru some threads to make sure how unlocking and rooting works as mine is A2017G version.....
[ZTE Axon 7 Questions & Answers] ALeX850:
Isn't changing the default setting to "natural" enough though? I find the color quite washed out with that mode. TBH the main problem for me isn't saturation but rather contrast: colors seem to "melt" with one another, particularly on 3D games
[ZTE Axon 7 Questions & Answers] ThePublisher:
Display --> screen effect.

I keep mine on gorgeous and normal and it looks great. I like punchy colors. Shows off this great AMOLED screen.
[Moto Z Questions & Answers] aviwdoowks:
Vzw phone so no root access. Note my phone is a Play version.

Solid Explorer, the new one, works and shows path of : /mnt/media_rw/0EB0-0FF1. It also asks for permissions and you can successfully grant them. Yet you cannot see this folder/drive while exploring /mnt. It creates it's own shortcut and browsing is fine that way..

Neutron sees the drive and tries the get permissions but you never get to grant them.

Google Player (stock), Player Dreams, Jetaudio, Hiby and Kamerton do not see the drive at all.

Has anyone had success with any player accessing OTG drives?
[Moto Z Questions & Answers] regenwurm16:
I'm having the same problem, I couldn't access my NTFS formatted stick with neither using stickmount nor the Paragon app.

After reformatting my stick to FAT32 it's mounted by the system but only accessible and usable by the integrated android file manager.

I now tried total commander and the Paragon plugin and this way you can access files and play them in your standard player and it's even able to load subtitles to a movie but this way it's not even mounted as separate device anymore and therefore not visible to anything.

I'm using the TurboZ kernel and already wrote the creator about the NTFS problem.
[Moto Z Questions & Answers] aviwdoowks:
I take it you are still on MM.

I found some better filers but still no players.

MM is a tricky one for Dev's to get OTG right. I read many stackoverflow comments, hence the shortage of apps. I think N might be worse.

See here and other recent post of mine.

https://xdaforums.com/showthread.php?t=3533577
[Moto Z Questions & Answers] regenwurm16:
Yes I'm still on MM

It's not the file managers fault but more that there's no reliable/functioning way to actually mount an NTFS or even FAT32 OTG stick in a manner that it's easily visible for apps and such under marshmallow.

I tried a few of your suggested apps but only x-plore and "file manager by scavengers" offered an access to the USB stick prompt but didn't actually display it then (probably because of NTFS) or offer a real mount option so they are not helping with my problem but thanks anyway for the help/suggestion.

Actual mounting isn't supported under marshmallow anymore (as far as I found out) so USB OTG is pretty useless now because I don't want to use a file manager to access the files and hope it's able to combine the video with the subtitle file.
[Moto Z Questions & Answers] aviwdoowks:
Right no hard mounts anymore.

But I use xfat and all app suggestions do work. FX is best but it does not let you use all the app on your phone. But these are Dev growing pains.
[Moto Z Questions & Answers] regenwurm16:
I actually just managed to mount it like it used to with stickmount but with an app called "USB OTG helper" by "Ray of light"

I tried it before and it gave me the error that it couldn't create the folder where it wanted to mount the stick so it didn't work but now after installing it again it worked flawlessly.

I suspect it's because I used the "external SD card full access" option from the xposed module "installeropt" because now it didn't write any error messages and worked as expected even with an NTFS USB stick.
[Windows 10 Mobile] pijalaccount:
ASK where is registry key for "Aghost.exe" and "BackgroundTaskHost.exe" ?

i need to change registry config for "aghost" and "backgroundtaskhost" handle task by them, where is registry key/value for these ?

or if anyone have registry file from ffu please upload those one for me..it should help too.

thanks.
[Nexus 5X Q&A, Help & Troubleshooting] hilla_killa:
Delete
[8525, TyTN, MDA Vario II, JasJam ROM Development] RanDomIze:
Hi.

i need a litle help in hex convert.

in Bepe threads i fond this.

- nb file: 0x000001F5: short value + 0x48 (e.g: 0xA7+0x48=0xEF)

- nb file: 0x000001FB: short value + 0x48

A7 00 + 0x48 = EF 00

DB 05 + 0x48 = 23 06

i dont know if that is correct or not but if yes wath the value for this?

A2 01 + 0x48 = ??????

Thx and regards
[8525, TyTN, MDA Vario II, JasJam ROM Development] kc_hubbard:
I think you are not adding the columns correctly here. See your examples below along with a base 10 (the way we normally count) example (notice the numbers are lined up just as you would if you were adding base 10 numbers, from the least significant column to the most significant column, right to left)

A7 00 DB 05 100 (base 10 example)

+ 48 + 48 + 10

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

A7 48 DB 4D 110

A7 + 48 does add to EF, but that is leaving out 2 entire orders of significance at the end of the A7 00 number.

So, the answer to your next question then would be:

A2 01

+ 48

------

A2 49

Also, just FYI here, the Calculator program that comes w/ Windows based computers will do Hex arithmetic for you. To get it to hex mode, start the Calculator, click on the View menu and choose Scientific. The calculator will then change it's view so that you can do Hex, Decimal (base 10), Octal or Binary arithmetic.

Hope that makes sense. If not, ask and I'll try to do a better job explaining.
[ONE General] henrikh1998:
The builds are only weekly builds, but its the first official.

You can find it on their download page:

OmniRom find7op Downloads

Includes:

January Security Patches

OTA

Other Features from Unofficial Builds

Edit:

Cause some people dont seem to know

Omni doesnt use Bacon as device Name

It is find7op (op = oneplus)

find7 would be the build for Oppo Find 7
[ONE General] trqnwr:
Screenshot?
[ONE General] dragsterman:
Does the High Resolution mode (50 Megapixel) work with Bacon camera or ColorOS camera in this ROM?
[ONE General] C4SCA:
This?
[ONE General] C4SCA:
Screenshot fixed
[ONE General] clevebb:
This is the OnePlus One (bacon) forum. That ROM is for the OPPO Find 7
[ONE General] C4SCA:
No it isnt oppofind7op is oneplus one, oppofind7 is OPPO find 7.

Im running this build on my OPO
[ONE General] daniga74:
Could you descrive rom's features?
[ONE General] clevebb:
Well then, downloaded and about to try it. What gapps do you use? Do you use root? Does android Pay work if not rooted?
[ONE General] LTMendarynas7:
Pico,yes,idk
[ONE General] henrikh1998:
Can't tell exactly, because im not using Android pay, but it should work as omni doesnt include root by default
[ONE General] clevebb:
Pay didn't work, but it was cool trying something else, booted fine. I used micro gapps. I'm back on CM, but its nice to know there are other ROMs. Is omni a fork of CM?
[ONE General] wilee1928:
so, if I doesn't install SuperSU, will it be fully unroot? (I want to be able to run Pokemon GO).
[ONE General] henrikh1998:
As omni is based on AOSP it is unrooted by default

PkmnGo should work, afaik.

Give it a try and tell us if it worked.
[ONE General] wilee1928:
yes! i'll do a back up right away.

thanks.
[ONE General] clevebb:
Safetynet did not pass, clean install meaning just flashed ROM and gapps, signed in and installed Pay and SafetyNet helper.
[ONE General] wingedpanther:
I request installed users to provide a review.
[ONE General] C4SCA:
Led control, Qs custom tiles, navbar, custom power menu.

Go check on youtube Game Of Roms review on oneplus 3

Pokemon go doesnt work eventhough it doesnt come rooted nor has traces of root but the build is userdebug (think thats the issue)

Used nano opengapps.

And my banking app didnt worked so went back to my old MM rom...
[ONE General] wilee1928:
Thanks for letting me know, it was worth to try it.
[ONE General] SirSoviet:
Custom kernels don't work without breaking camera or Wi-Fi (or both), we need the Omni version of Lightning kernel updated.
[ONE General] hyper_davide:
hi the lighting kernel omni v4 works well whit nougat, but if they would update it would be better
[ONE General] Ratheesh6:
How about the battery performance in this ROM, Is it stable enough for a healthy daily drive?
[ONE General] ShinnAsuka:
Is anyone experiencing intermittent losses in cell signal with this ROM? Had this issue on the 1-4 build and updated to the 1-8 build with the same issues.

It will show a certain number of bars but an "x" will appear o the bottom right of the cell signal icon. I have to turn cell data on and off again to fix it.

Thanks.
[ONE General] wingedpanther:
Yes it is.! I got 4.45 screen on time with 1 day 17 hrs uptime

---------- Post added at 01:42 PM ---------- Previous post was at 01:39 PM ----------

[YOUTUBE]o0lFOLm2RSc[/YOUTUBE]
[ONE General] tzelbruezler:
Hello,

Since I'm using Omni MM right now, I have the question whether someone dirty flashed Nougat over the MM security release? ..and if it worked?
[ONE General] digitalpig82:
I know that the first unofficial builds over at G+ used ColorOS blobs. What about the official weeklies? Did the ColorOS blobs get implemented here as well?
[ONE General] DerRomtester:
Dirty flashing will not work correctly. e.g. force closes, incompatibility etc.
[ONE General] tzelbruezler:
Thank You

In the meantime I've just done a clean flash and restored data - works fine 'til now.
[ONE General] AKHIL.cochin:
Hi

Is Lightning kernel new 52 is compatible with omni 7.1.1
[ONE General] Anghirrim:
Anyone knows how to access the omniswitch parameters?
[ONE General] digitalpig82:
It's in the app drawer.
[ONE General] Anghirrim:
Looked everywhere but here :D
[ONE General] solar666:
Just look one page back and you will find following answer:

https://xdaforums.com/showthread.php?p=70421516
[ONE General] Gabeloooooo:
Thank you so much for this ROM! It is the only 7.1.1 I've tested that almost works with AirPods. AOSP and LineageOS both have terrible issues with AirPods, but Omni works fine a lot more often.

I still have the occasional volume is too low when connecting the AirPods, but somehow much less frequently than with AOSP/Lineage. (the issue NEVER happened on official cyanogenOS 6.0.1 before, so I'm guessing something with the 7.1.1 bluetooth seems wonky?)
[ONE General] arh2o:
2 quick questions for those that have this ROM.

1) Can you bind hardware keys to a custom action (single-tap, double-tap, long-press)

2) Can you hide the brightness slider in quick settings?

Thank you!
[ONE General] galaali44:
How can I hide the headphone icon left above?
[ONE General] daniga74:
It's possible to know last changelog or where I can found it?

thank you
[ONE General] Gabeloooooo:
Did something change with the Bluetooth and/or sound between 01-22 and 01-29?

With 29, AirPods are completely busted again (like with Lineage and AOSP roms), whereas with 22 it works (mostly) fine.
[ONE General] Enzissimo:
For people using coloros camera in this rom, is the hd (50mpx) plugin working? Are the photos 8160x6120?

Inviato dal mio A0001 utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] FrankARC:
Hello everyone. Thanks for opening my post. Especially the experts on this ...:D:o:highfive:

I have compiled Cyanogenmod 13 (If I compile as lineage os) unofficial. For my Galaxy J2 device (J2LTE) Using the files on my phone that are in "Github".

Successfully compiled. But use the kernel sources of another device that handles "universal3475" exynos. Installs correctly, but when trying to "boot", it does not pass the Samsung Logo. And if I use a custom kernel "KudKernel" does not start and if I put the stock kernel on and off.

I re-compiled the ROM using a prebuilt kernel and the already-mentioned "KudKernel". And everything is installed well. But it restarts in recovery. I show the device shows the logo goes off and enters the recovery.:(

Why is this error?:confused:

Will be Ramdisk?:confused:

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

I am new to this and my device has never had any ROM like this. And I try but nothing :crying: :(

The only problem is the kernel I imagine since even installing the kernel with the ROM stock does the same of restarting in recovery.

Thanks for reading I hope your answers and / or help.

Posts: My device has android Lollipop and uses kernel 3.10.9 in stock and in custom is 3.10.22.

Sorry for my bad english. (Google translator)
[Android Q&A, Help & Troubleshooting] sijosony:
Download link plzz
[Android Q&A, Help & Troubleshooting] akash14darshan:
There might be two issues regarding your case.

i)The kernel is no match for your device

ii)You have ported the correct kernel incorrectly.

If you could send me the stock kernel of your device and the kernel from which you ported(original) , i think I maybe able to help you.

---------- Post added at 11:01 AM ---------- Previous post was at 10:55 AM ----------

I think you are providing a wrong information buddy.

I myself have Lineage OS based on CM13 on my MT6592M.

And btw the issue he has is not bootloop , actually his device is stuck at BootLogo.

This may indicate different problems.

i)Rom is ported incorrectly.

ii)Gpu Driver isnt the correct one

iii)Kernel issue

His kernel has the wrong information of partitions and thus because of not able to find /system files , it reboots into recovery.

Maybe fstab has to be modified. And if still problem persists , Maybe we have to look deeper.
[Android Q&A, Help & Troubleshooting] FrankARC:
boot

Well I previously compile the ROM using this kernel "https://github.com/jcadduono/android_kernel_samsung_universal3475/tree/stock-6.0" since the stock of my device gave me error in timauevent when compiling and other errors but the kernel that I mentioned in the link it did not give me any error when compiling, but the moment I install the ROM it stays in the bootlogo of my device. And then try using my stock kernel the one my device has at the moment and it was compiled well it installed everything fine but when I rebooted my device showed the samsung logo for a few seconds and then rebooted in the recovery, you need me to That I can help :). And thank you very much for responding, I do not want to give up.
[Android Q&A, Help & Troubleshooting] FrankARC:
have error building prebult kernel

usage: mkbootimg

--kernel <filename>

[ --ramdisk <filename> ]

[ --second <2ndbootloader-filename> ]

[ --cmdline <kernel-commandline> ]

[ --board <boardname> ]

[ --base <address> ]

[ --pagesize <pagesize> ]

[ --dt <filename> ]

[ --ramdisk_offset <address> ]

[ --second_offset <address> ]

[ --tags_offset <address> ]

[ --id ]

-o|--output <filename>

make: *** [/home/frank-dev/cm13/out/target/product/j2lte/boot.img] Error 1
[Android Q&A, Help & Troubleshooting] FrankARC:
its is the boot.img compile with cyanogenmod (using prebuit kernel)

kernels compiled with cyanogenmod 13
[Android Q&A, Help & Troubleshooting] akash14darshan:
It would be better if you provide the stock kernel too :D

Would be helful cauz i dont own the specific device.

I'll try my best

Cheers

EDIT

See the culprit?
[Android Q&A, Help & Troubleshooting] sijosony:
Download link please
[Android Q&A, Help & Troubleshooting] akash14darshan:
Seriously?
[Android Q&A, Help & Troubleshooting] FrankARC:
I got this

Unpack the recovery twrp and I see that there is an init that is so.

Init.recoverysamsungexynos7420.rc. I do not know if I have to see something like that.

You think it could be solved if I use the files you mentioned in the screenshot of my Kernel stock. Anyway here I attach 2 boot.img and 2 recoverys.

Boot-stock kernel 3.10.9

Boot-KudKernel update to 3.10.22

Recovery-Stock remove it from the firmware for odin of my device

Recovery-Twrp Latest version for my device.

And thank you very much for helping me with this. :highfive: :fingers-crossed: :angel: :svetius: :cool: :good:

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

I found this in the twrp fstab.goldfish

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev wait,check
/devices/platform/goldfish_mmc.0 auto vfat defaults voldmanaged=sdcard:auto,noemulatedsd

I think it's not the same as the boot.img or is it?
[Android Q&A, Help & Troubleshooting] akash14darshan:
:victory:

I may have figured out the work around , with the reference of your stock kernel , I've modified the kernel.

There are 3 possibilities kernels that may work. Im sorry but you have to try all.

First try boot1.img and then boot , if it fails , try boot2.img.

If boot2.img fails , finally try boot.img.

Im pretty sure atleast one would be compatible with your rom.

After kernel flashing, wipe /data partition too , along with /cache and dalvik-cache

Please try and Let me know

Also , I may sound crazy , but could you confirm that your ROM was installed in the correct partition?

Cause your fstab is properly configured , so the kernel is looking in the correct directory for system files , but it is missing , hence it boots to recovery

To check if the rom is intact and is installled in correct dir, in adb shell after unmounting /system in recovery

type

-cd /
-mkdir testdir
-mount -o bind /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM /testdir

Hopefully after this command if you see all your system files (like build.prop , App,priv-app) I think you should be fine.

If you dont the recovery may be having bad mount points, If you used recovery to flash.
[Android Q&A, Help & Troubleshooting] FrankARC:
First Boot :'D with error D:

I tried the boot1 and it restarts in recovery. The boot2 and the same is restarted in recovery. But the boot.img if it passes the samsung logo shows the bootanimation but it suddenly goes out and starts the cell again in bootanimation, I do not know if I did the wipa data, I just did the wipe cache or because that boot.img only Is compatible with cyanogenmod By the way, install the boot using the stock ROM. I do not know if that has anything to do with it.. Thank you for responding, you're the best :). I hope your soon answers:highfive::laugh:

I have a question, I just unpacked the boot.img, and between the files I see that I have the same ones of the boot stock, and they are not those of the init.cm.rc and others of the boot compiled in cyanogenmod, because? Or is this boot for ROM stock?

Thanks for your help: D
[Android Q&A, Help & Troubleshooting] sijosony:
Please made lineage os for Samsung Galaxy j200g