yashsingh1/xdaforums huggingface dataset:
[Magisk] John877:
ODIN log using your file [MENTION=8340552]jenslody[/MENTION]

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1203)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> boot.img

<ID:0/003> RQT_CLOSE !!

<ID:0/003> RES OK !!

<ID:0/003> Removed!!

<ID:0/003> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

Also noticed on bootup there was a message in yellow. Something like, Warranty Bit : kernel

Now as I type this Im seeing a lot of messages about Google Services Framework stopping, Samsung Notes, Knox. They just keep coming.
[Magisk] jenslody:
The "Warranty Bit: kernel" message is normal, about the other messages, are this just force-closes of the apps ?

Did you check [MENTION=4667597]Didgeridoohan[/MENTION]'s troubleshooting thread ?
[Magisk] 白い熊:
The warranty bit warning is expected behavior.

Is Magisk installed and functioning? Do you have root?
[Magisk] John877:
Yes theyre a bunch of "__________ has stopped" messages. I have not but will now.
[Magisk] John877:
Yes and yes.
[Magisk] jenslody:
And a "patched_boot.img.tar" created on your device does still not work ?

Which of "my" images did you use ?
[Magisk] John877:
When I posted that Im an idiot, its cause I must have patched before selecting the output format. Once I did the correct output format, and patched again it worked fine.

The file of yours I used however was the img.tar file, not the md5 one.

Also Im currently recording a logcat while it does all the such and such has stopped messages. I have also gone and uninstalled and reinstalled the Android Webview, Chrome stable and Chrome beta apps in hopes itd change anything. It hasnt.

Also on my phone I dont see the Webview thing under Dev Options thats mentioned on the support thread under the section of apps force closing.
[Magisk] John877:
Heres the logcat that was generated while a bunch of things were force closing. Im not sure what it tells about anything. I scanned through and theres a few sections with connectivity lines. and a WHOLE LOT of something with D/TextView(12730): setTypeface with style : 0 whatever that means.
[Magisk] John877:
Ive since gone back to stock boot img and think im gonna uninstall magisk at least for now. All those force closes just got impossible to even use the phone.

Will try again maybe once theres a definite solution to all those.
[Magisk] jenslody:
Did you try it with a "patched_boot.img.tar" created on your phone ?

There is a very small chance it is patched differently (as far as I remember, there should not be a difference, but just to be sure, I would give it a try.
[Magisk] John877:
I did not. I am just trying to get rid of all the force closures at this point now. I've since flashed the original boot.img that I tar'd using 7zip. I still am getting them. I've tried going to recovery and wiping cache partition and even went as far as putting on unlock to off. I've not restarted since doing that though.

My next steps I think are to factory reset in recovery or maybe just backup and flash the stock room back on.

If I do try rooting this in the future I just may do the custom recovery and flash the SU the regular way.
[Magisk] jenslody:
If you have TWRP you can directly flash the stock boot.img, just click on "Install image" on the bottom right, after chosing install. Then you can try to flash the Magisk-zip through TWRP. The Odin (or fastboot on other devices) method is much more complicated and only useful if you don't want to use a custom recovery or if it is not available for your device,
[Magisk] 白い熊:
I'd recommend a factory reset—it'd be interesting if it works cleanly with root after that.
[Magisk] John877:
I was doing it this way cause I wanted to preserve the stock recovery for the sake of future OTAs and such.

Also the last thing I just remembered is the magisk uninstaller zip file. Will report back when Ive done that.

EDIT: Apparently you can't flash the uninstaller from stock recovery. It can't mount the SD card and can't see the internal. Only options are adb and SDcard too.

How can I make the uninstaller zip an Odin flashable file?
[Magisk] John877:
Heres another logcat that has more information than the last one. This was taken during a series of "Google Play Services Framework has stopped working" error messages.
[Magisk] jenslody:
Two question:

are you absolutely sure the stock boot-image, you used for magisk (and reflash), is the exact same version you had before ?

And did you try it with a boot-image patched on your phone (not with "mine") also ?

Cleaning cache and dalvik/art-cache might also help. There is a thread somewhere on xda to do it without custom-recovery, but it needs working root as far as I remember.

If the boot-image is back to stock, Magisk is gone, except for some files left in /data (e.g. magis.img) and possible /cache and of course MagiskManager stuff if it is not uninstalled. So it should not do any harm.
[Magisk] koko115:
This method trip knox ?
[Magisk] John877:
When I reflashed the stock boot.img it was the one taken from the firmware file. Granted it wasnt taken directly off the phone itself though but it was, or should be the same exact file as was on the phone since when I got the phone 2 weeks ago and turned it on the first time, it updated to 6.0.1 QF4. I didnt think to check what it was prior to the OTA being installed. So since I knew it to have QF4 installed and I grabbed the QF4 firmware from sammobile, I assumed they were identical.

While playing with this I did clear the cache partition in recovery as thats the only thing it lets you do in sotck recovery other than wipe /data to do factory reset.

btw I bit the bullet so to speak as those force closing messages were getting really annoying, I backed up and have since does the factory reset. So I am essentially back to complete out of the box except that while I did have magisk root working I did uninstall the Amazon apps. Also I have also since looked into using adb to "uninstall" system apps without root but I dont like how that works cause it still leaves the apk and odex files in /system. Its just a more thorough Disable function ultimately.
[Magisk] Brianmagoon:
Shot in the dark. But will this method work getting root on SM-G935P on the latest firmware? I have been around the world looking for a root method that works. I think Im screwed because of the binary 5 thing. I really hope not. I need to get root. I feel naked without it lol. I tried doing it through odin but got denied.
[Magisk] ForeverYangGo:
when I reboot phone ,It get in looping

I use ODIN AP and choose patched_boot.img.tar

It flash OK

but when I reboot phone ,It get in looping
[Magisk] mattman1978:
I'm having the same problem. Or similar at least. I downloaded the stock firmware for my Samsung galaxy J7 Sky pro, SM-S727VL. There are two varients of this, with two different firmware packages available for download as seen in this link:

https://updato.com/firmware-archive-select-model?q=S727VL&exact=1

I checked the baseband version of my phone in developer options and matched up the number: S727VLUDU1AQB5

Downloaded the correct one to my windows box and used 7zip to unpack it. I Found the 5 .tar.md5 files and found the boot.img in the AP file. I extracted my boot.img file and then transferred it to the phone via the USB cable that came with it. I changed the setting in Magisk to create an odin-flashable image. I used Magisk manager to patch the file, which it did. I then moved the patched_boot.img.tar back to my computer using the same USB cable.

I flipped the OEM UNLOCK to unlock.

I fired up the most recent version of Odin (I already have the samsung drivers installed). Odin3_v3.12.3 I right-clicked and selected "Run as Administrator" just in case.

Turned off my anti-virus protection.

I put the phone in download mode.

Phone displays

FRP LOCK: OFF

SECURE DOWNLOAD : ENABLE

QUALCOMM SECUREBOOT: ENABLE

(some other stuff that looks pretty normal)

Connect to the USB cable and ODIN finds the phone. (Added!!)

Selected the Patched_boot.Img file in the AP box and click Start.

I get this as a response:

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1203)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> boot.img

<ID:0/005> RQT_CLOSE !!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Phone still boots normally and works fine, but obviously, the flash fails every time.

I have tried older versions of ODIN, including 1.something.

I honestly believe I have followed all the instructions to the letter and I am not successful.

Here is a download link for the PATCHED image from my dropbox:

https://www.dropbox.com/s/f60m5ek3q99dbuf/patched_boot.img.tar?dl=2

This is the UNPATCHED, stock boot.img from the factory firmware download.

https://www.dropbox.com/s/ws9q1dmpm7v7kx9/boot.img?dl=2

There is no TWRP for my phone (at this time). Any help with this Magisk method would be GREATLY appreciated.

Thank you
[Magisk] Jopponius:
Am on the same boat.

Wondering if anyone has success to flash Magisk through Odin WITHOUT having Twrp on a S7 exynos.
[Magisk] mpadhu:
I am facing the same issue now too. Did you go thru it?

Anyone else succeeded with ODIN flashing?
[Magisk] varadinum:
odin fail

Hi,odin can not flash patched_boot.img. With magisk the patched_boot.img created. Odin launched -AP selected-patched selected-start-fail. Why does not work? can someone help me?

Thanks

Samsung A9 2018 A920F Bootloader unlocked

the mobile phone must be switched on or be off in download mode?
[Magisk] partcyborg:
Woah ok hold up a second. There is some bad information in 5hid thread. Let me clear that up first, then I will help who is he until issues. .

it doesn't, all the slots are identical the only reason they are labeled is so you flash things in order as sometimes flashing out of order could be potentially problematic. This has nothing to do with why he was having problems. The reason it was not working was that he was trying to flash a boot image file renamed with. .tar at the end instead of a boot image in a tarball. Just want to make sure everyone is clear on that: it does not matter which slot you flash a single .tar or .tar.md5 Odin handles them all exactly the same way. Odin actually uses the name of the .img file to decide where to write the image into memory, so the file inside has to always be named boot.img exactly. The .tar or .tar.md5 can be named whatever though

Wiping the cache partition (on a Samsung at least, but I'm pretty sure every modern phone is this way) does not wipe the dalvik cache. In fact, it doesn't actually wipe anything that would help a rom not have issues at all. Everyone has been doing this out of habit and not realizing it does literally nothing to fix issues, as nothing is stored in /cache but some log files and on some devices ota updates. To wipe dalvik you need to use twrp, or if that isn't an option you will have to boot up to the is and use something like L speed or flashfire to do it. If you're stuck unable to boot, I can give you a command to run over adb to do the wipe manually but it's dangerous because if you don't enter the command EXACTLY, character for character as what I tell you to enter you could easily delete everything in your phone.

Whatever is going wrong with your phone, the way you flashed Magisk isn't causing it. My guess is thw firmware you downloaded to extract a boot image to flash is newer than the firmware on fire on how phone and not compatible with what is already there. This leaves you with 2 options on how to proceed:

1) look up the rom and baseband versions currently running on the device and download the same version to extract a boot image for modifying with Magisk

2) install the new stock firmware the came with the boot image you tried to mod and flash, with a stock boot image first, then once everything is working on the new stock rom, take a fresh copy of the new stock boot image and mod it in Magisk and try again.
[Magisk] mobileuser2018:
Hi,

I'm having the same boot image patching problem. I followed the instruction given by [MENTION=4470081]topjohnwu[/MENTION] at the link https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root but to no avail. My mobile is samsung J7 duo and its stock rom is downloaded from https://www.sammobile.com/firmwares/galaxy-j7-duo/SM-J720F/XSP/download/J720FDDU3ARJ3/243170/. Attached are the screenshots. While patching with magisk manager 7.2.0 did not show error, the flashing of the patched boot image stalled.
[Magisk] mobileuser2018:
This is a follow up of my last post. Good news is I managed to root my J7 Duo using topjohnwu's system as root procedure. Here's the link again https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root. The problem was suspected to be the mobile's download mode. I suspect my mobile wasn't in proper download mode when I tried to flash the patched boot image, though the downloading screen did show up. I started out by putting the mobile into download mode by using micro usb jig dongle as the 3 buttons combination didn't work on my mobile. Here's the link of a similar one https://www.ebay.com/itm/Micro-USB-...ng-Galaxy-S4-S3-S2-S-Note-3-2-1-/111378442299. Using the jig, the mobile showed the downloading screen with some status on the top left. See attached example for illustration. The flashing of the patched boot image stalled in odin by putting the mobile to download mode via usb jig. On the other hand, if I used the tool from Chimera to flash the patched boot image, it will put mobile into download mode but less the status on the top left. See attached image. I'm not sure whether there are different state of download mode for samsung mobiles. The flashing via Chimera was successful and magisk was installed into the mobile with root access. Please follow topjohnwu's procedure.

Chimera tool is a commercial product and it cost 11.9 euro for a start license. It could do most of the procedure including removal of RMM except rooting of J7 Duo. It may be able to root other mobile model, though not J7 Duo. Hope this help.
[Magisk] spike1970:
s10 bricked by odin

s10 bricked by odin MagiskManager won't work on windows should i start smashing it now ? so upset nothing can be done as already had in 2 shops they say cant do nothing with it stuck in download mode and attempt to exit download mode only restarts it all over again and again no escape no hope every gude says s6 im like wtf s10 or just do this do that set fire to phone smash with lump hammer i just do not know what to do help please

---------- Post added at 12:02 PM ---------- Previous post was at 11:53 AM ----------

i lost my charger ordered new phone went dead new charger came all seem fine charging but pin unlock stopped working so i though oh hard reset did that s10 rebooted still stuck on pin which i could not remember changing so after searching found odin did that left phone for 2 hours in odin stuck on download mode ever since always gets stuck on boot.img not patched stock from samsung and no back up made so i guess im fecked unless some knows how to do it as so far im lost now thanks in advance
[Magisk] ayyash_tarar:
Dear i am also in same problem. A307FN with Android 11.

Odin say Invalid LZ4... (I patched with Magisk and rename it then .img to .lz4 and after .lz4 to .tar and flash with Odin)

Pls Help
[Google Pixel Questions & Answers] salsa1976:
hi all,

Has anyone managed to Root the Google Pixel on version 8 ? I'm on the UK EE Network . Thanks guys x
[Android Apps and Games] Quantum42:
I like this new game, it's very simple and fun, on Google Play store, try it.

"search in Google Play by Umlet"
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] abhirajsinghofficial:
FIRE BURNS AND PHOENIX HOUNDS

FireHound is a Custom ROM developed focusing on Stability + Features. FireHound is made from cherry-picking commits from many great ROMs. Our main goal is to satisfy users as best as possible and to raise a community. So without being much sense, we will head towards main part now…

FireHound Features:

FireHound Ashes

https://raw.githubusercontent.com/Ma...n7.x/README.md

Download

ROM : https://www.androidfilehost.com/?fid=961840155545594245

Gapps : opengapps.com

SOURCE

ROM:- https://github.com/XOSP-Project

Kernel:- https://github.com/LineageOS/android...anogen_msm8916

Device Tree:- https://github.com/LineageOS/android_device_yu_jalebi

Thanks

[MENTION=8426240]iamsj7[/MENTION]

[MENTION=6992223]mayu19[/MENTION]

XDAevDB Information

FireHound, ROM for the YU Yunique Jalebi

Contributors

Abhiraj Singh

Source Code: https://github.com/FireHound

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

Based On: LineageOS

Version Information

Status: Stable

Current Stable Version: 1.1
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] Andy2290:
Seriously thanks a lot for porting all these amazing ROMs to yunique. Your work is much appreciated dude. Will give this a try soon
[OnePlus 3T Questions & Answers] Vixiebalistic:
Hi nice guys here, since 2 days ago my google app stop working and i unable to open google app (only google app), meanwhile other gapps still working. I dont know whats wrong and even restoring nandroid backup is not helping. SS of what i got on log cat is attached. Advise and help is highly appreciated.
[Magisk] alessio89g:
I made the two modules attached in this post using the new module template, but after installing them, at the reboot the phone stuck on "pre-bootanimation screen" (Google logo).

The issues started when I updated Magisk v13.3 to v14, whit the same issue, but the modules used the previous template (they worked with Magisk v13.3). So, thinking the issue was caused by the template version, I updated them whit the newest, but nothing changed.

I also tried to install them one at time, without the other… same situation.

What's wrong?

Nexus 5, Screw'd ROM 7.1.2 with its Kernel, no other mods.
[Magisk] Didgeridoohan:
You have left the placeholder file in the system folder. That then get's Magic Mounted to /system, which didn't used to be an issue, but from v14.0 (and the betas v13.4-6) adding new files to the root of /system causes a bootloop. It's under investigation...

Remove those files from your zips and you should be good to go.
[Magisk] alessio89g:
Thank you, now they work!

I think that "DeleteMe" could be a better filename for the placeholder file! ?
[Xiaomi Mi MIX  Questions & Answers] shantanil:
I don't know if this has been answered anywhere and I am sincerely sorry if it has been.

I am faced with a peculiar problem with my 18K Mi Mix. The phone came with 8.2.5.0. When no updates were forthcoming I decided to root and install a custom ROM. Everything went fine and the phone booted up and I installed my apps. I was using 7.8.31 version of the Beta ROM. However I was faced with a problem of a crackling or static like noise in the background while making calls. The speakerphone and headphone or Bluetooth headset has no problems. Only the call speaker. So I imagined it to be a hardware problem and went back to stock. To my surprise, the problem vanished in stock ROM and any ROM based on Android 6.0. It is only present in Android 7.0. So I guess it might have something to do with the Android 7 ROMs themselves.

Has anybody here faced such issues. If you have kindly help me. I am kinda addicted to the 7.0 ROMs and wish to stay on them if I can get rid of this issue. I was using the Global stable ROM earlier.

Thanks for any help.
[Xiaomi Mi MIX  Questions & Answers] james1089:
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
[Xiaomi Mi MIX  Questions & Answers] shantanil:
Thanks. Will give it a try.
[Xiaomi Mi MIX  Questions & Answers] shantanil:
Finally cracked the problem. As I had suspected, this is a software flaw. The whole issue was being caused by the proximity sensor. The moment I turned the proximity sensor off all problems have vanished. Have replicated the problem a number of times, so am pretty sure that is the cause. Thanks everyone for your help and suggestions.
[Xiaomi Mi MIX  Questions & Answers] fred1311:
you don't fix the problem we need the sensor
[Xiaomi Mi MIX  Questions & Answers] shantanil:
You do need the sensor.

But since the problem is not happening with any of the stable version ROMs (I have tried Global stable 8.2.5 and China Stable 8.5.4), I am very sure its not related to hardware. So for the time being I am more than happy keeping the proximity sensor off and using Nougat 7.0 on my Mix. I am pretty sure this has something to do with drivers or firmware and will be taken care of, once the stable versions of 7.0 are released.
[Xiaomi Mi MIX  Questions & Answers] Atharkhan101:
Even my Redmi Note 4 has that cracking or scattering sound when bluetooth calls are made. I found temporary solution that is Turn off the WiFi. Looking for permanent solution.
[Lenovo P2 Questions & Answers] eried1:
Does anyone know where the battery files are stored? Usually the path begins with /sys/devices, but from there I'm lost.

Also looking for the directory of the LED settings. In some devices this path begins with /sys/class.

Edit: Think I found the battery files in /sys/class/power_supply/battery. LED in sys/class/leds.
[X Style (Pure) Q&A, Help & Troubleshooting] m3kgt99:
My phone is rooted with xposed installed. I've been like this for a year and half now with no issues. I am running Kernel Version 3.10.84-perf-g6898f68.

The last few months I have noticed apps being super slow. I never really connected it until now I just realized that it's mainly when my phone is plugged in.

I have installed CPU-Z just now to see what is possibly going on but the only thing is that I hardly ever have RAM.

My CPU usage goes from 8-20% when unplugged to 25-90% when plugged in and stays that way. Maybe I just need to update my build?
[X Style (Pure) Q&A, Help & Troubleshooting] fliperpl:
they are slow because u are using turbocharge that makes phone temps go higher than normal, and cpu is throttling.
[X Style (Pure) Q&A, Help & Troubleshooting] AsquareX:
As fliperpl said, that's correct. Also do not use your phone when it gets hot, especially this phone because I've read multiple times the area near the navigation bar starts getting dead if the phone/screen is pushed to higher temperatures.
[X Style (Pure) Q&A, Help & Troubleshooting] aybarrap1:
Increased CPU usage during charging, assuming your hands on usage is the same when not charging, could be several things. By chance do you have anything at to run only when charging (i.e. pictures/video backup)? This could use cycles while charging.
[X Style (Pure) Q&A, Help & Troubleshooting] m3kgt99:
I flashed crDroid then used TIB to restore all my data. I had to flash an old version of TIB because it would crash upon startup every time. Anyways... my phone is like brand new again. I love it!

No I didn't have those settings on. The only weird setting is that I don't auto-update apps. I want to do them when the time is right, not just whenever I'm connected to WiFi.

Yeah my phone screen started turning yellow in the top left portion of the screen. I didn't know what it was until just a couple days ago. Thanks for the heads up. I will remove my phone case when in heavy use and be careful not to overheat it any more.