yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 Questions & Answers] leondestiny:
gotcha thx, and also i never have issues with smurf.

it's only the built in kernels.. of nearly all the march patched custom roms, they all had that issue for me.

and the moment i flash smurf the problem goes away!
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
[ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0)

​

FOLLOW THESE DIRECTIONS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.

View attachment 4733553 View attachment 4733552

I have given you a freebie by providing the

patched_boot.img.tar,

thus saving you a few steps

All files needed are uploaded to my Drive: https://drive.google.com/folderview?id=1-8CGkYef58I-DrkyOshRFniecO_0dBDc

NOTICE: Patched_boot.img.tar is solely for the J737PVPU1ARG3 software version.

Any attempt to flash to a different version will result in a bootloop

. You

must

patch + flash your own stock boot.img if you are on a different software version.

YOU MUST PAY ATTENTION TO THE FOLLOWING

- In the Bli5zkrieg.zip you extracted, load up Odin_v13.1 (non-patched)

- Load

only

the BL/AP/CP files from your stock firmware into Odin

- As soon as the flashing process ends,

you must reboot quickly back into Download Mode

. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.

Assuming you followed directions...

- Close Odin_v13.1 & unplug your device while still remaining in Download Mode

- Launch Odin_v13.1 [Patched] & load up the patched_boot.img.tar in the AP slot

- Reconnect device & proceed to flash

- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)

- When device reboots to Setup Wizard, skip through it.

Do not add any accounts

(Google or Samsung).

Do not consent to giving any device data for whatever purposes

(they will ask twice; look carefully)

- On the home screen, unlock Dev Options &allow USB Debugging. OEM should already have been unlocked

- Connect device to your pc & in the ZeeToolz folder you extracted, run CMD.exe

- Input adb devices to ensure proper connection

- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device

- Open MagiskManager & make sure everything is good to go (see attached screenshot)

- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access

ĐØΠΞ
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] kinehumane:
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)

note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.

I used the files below.

Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view

Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025

Cheers!
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
No problem man. I didnt think to test sideload or mtp as I always use an SDcard (comes in handy lol). It was a tad bit tedious to get the whole process down due to Oreo. That being said, ensure that you have a backup. Editing any part of the system (ie. Build.prop) will result in failure. I installed the Time Zones update & it failed. As far as MagiskSU goes, I like the Modules but prefer SuperSU root. Will see about incorporating it in the near future
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....

So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me. Can't seem to find one that doesn't do a root-check first, refusing to do the deed if root isn't there yet?

Trying from square 1, to the point that I did a total backup, factory reset, and am starting with a reset phone.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism

Root Essentials won't work as a secondary flasher bc it requires a custom recovery to be installed beforehand. Flashify will be your best bet so try all possibilities to get it to work
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
Hmm... Root Essentials tells me it failed to install the image...

If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.

My understanding from the instructions is that I can't flash this particular TWRP image with Odin...

Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.

---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------

OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Flashing with Flashify is under the assumption that you dont have a lot of 3rd party apps installed. If you are logged into your Google or Samsung account(s) & have your data being backed up, it creates a more sluggish environment.

First, follow the rooting guide I posted above. If you do, you should have root access via Magisk with very little apps installed & you arent logged into any Account(s). After you have that, then install Flashify. Manually set root access if need be. Make sure you have all your device security settings disabled, Dev Options, USB Debugging, blah blah blah

We will get you root access & TWRP installed bud
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
When you go to get root, you will need your stock firmware (BL/AP/CP files). My directions are pretty straight forward. Unzip the tools, load up Odin (non-patched), flash BL + AP + CP in their respective slots. Make sure that after you flash the stock, you instantly reboot back into Download Mode. Close the current Odin & open the patched Odin. Load the patched_boot.img.tar I provided to the AP slot & flash. It will reboot with a Verification Failure, thus forcing you to format your device. When your device reboots, skip through Setup Wizard, dont link any Google or Samsung accts. On the home screen, use cmd terminal on your pc to install the MagiskManager.apk. Once sideload, you will see root access & more than likely a toast notification asking you to update Magisk.

Rashr (View attachment 4737540) works as a good substitute for Flashify. You just need to move the TWRP.img to the root of your sdcard (/emulated/0/sdcard) & flash it through the Recovery from Storage option. Reboot into TWRP &continue following the instructions I've posted
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...

As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.

I get this happening, you make it to Albuquerque, and I owe you a few beers...

---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------

OK... missed the immediately into download mode... Once more, with feeling.

When all else fails, go back and read the instructions CAREFULLY... <lol>

Reflashing the stock files and starting over...
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Lol The directions are on point. They're solid. You just have to pay attention ?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
Here's the old fart with another question....

After flashing the stock files as instructed, I immediately hit the download mode as soon as the screen went black. Flashed the patched boot as instructed, and, as you stated, it would go immediately into recovery due to verification error.

I wiped the cache and hit factory reset, then reboot.

It's now sitting at the boot logo screen, and has been there for more than 1/2 hour.

Honest! I followed your instructions to the letter, and I recall first boot after rooting taking a while to come up into the system on other devices I've had, but I don't recall first boot taking anywhere this long.

I'm stumped.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
You seem to be rebooting into Recovery an awful lot. You shouldn't be booting into recovery mode at all when attempting to root. Recovery mode only needs entered during either process whenever you attempt to flash TWRP. Luckily for you, I dont have sh¡t to do tonight so I can help you until you get it right lol Shoot me an email at koloradokiller848@gmail.com & we can get started. I dont want to clutter up this feed with a revised how-to guide lol
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Vyp3r M0dz:
Other Variants

I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.

for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.

do you have any recommendations on what to modify in your procedure for my variant?

my specs are as follows:

Model - SM-J737P

ROM - J737PVPS2ASA1

Android - 8.0

SDK - 26

Kernel - 4.4.13-14521356 dpi@SWDH2519 gcc 4.9.x 20150123

Processsor - armv8l

I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.

I am comfortable with beta experimentation within reason.

on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
I have since revised my instructions for root, starting that my guide is very device specific & you will have to tweak instructions in order to accommodate your version.

As far as TWRP goes, did you boot into TWRP twice? Once for the initial install to format the /data partition & the second to secure TWRP along with flashing the files? You need to do it simultaneously & in order otherwise it won't work
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
It's a happenin' thang!!!!

Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!

(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Not a problem buddy. Was fun & if you have any more questions, you have my contact info
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] LowTier:
Sent you a pm, but having trouble rooting the same variant
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Droidriven:
I've done it, but it has been a few years, I'm fairly sure there are some things that have changed in android since then that would require me to do additional research to get things completely correct.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
I'd be willing to try, my friend... Guarantee it won't be an all-night thing, this time... :D
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Droidriven:
As with all things here, there are no guarantees. We all use what is here at our own risk.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] pauljulian:
Well aware of that... just that Kolorado and I were working long-distance all night one night until my device was rooted...

Was just saying that I'm a little more adept at his process and instructions than the last time... :)
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
This is a stab in the dark, from left field attempt - Don't flash the BL file of your firmware. Flash the AP, CP, & CSC files only. Do so with a Pie specific version of Odin. It will be a version of 3.13 or greater but has to be for Samsung devices running Pie OS.

Please copy/paste Odin's response here.

I'm not usually in favor of corner cutting techniques but this corner doesn't feel so sharp so it may work out
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Prophetless:
Sure. Will try this today after work. Will post results.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Adding onto what Droid said, we are a community here. We help find solutions to anything Android. Nothing is guaranteed but that shouldn't mean we have to stop trying. Sometimes the most off-the-wall idea is the right answer. Who knows, you may be helping out other folks in the future by contributing your issue here.:laugh:
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Droidriven:
I also thought of trying that since the firmware is already a 4/5 part firmware. It would seem that just flashing everything except the Oreo bootloader should work, maybe just flashing the AP without all the others would work since the AP file is where the system.img is located, that's really all that needs to change is the android system itself, in theory.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
It also contains the vendor.img. If you really wanted to, you could dissect the tar file & re-tar just the partitions you need. That's kinda what I was going to explain lol
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Prophetless:
<ID:0/006> Added!!

<ID:0/006> Odin engine v(ID:3.1301)..

<ID:0/006> File analysis..

<ID:0/006> Total Binary size: 4088 M

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Set PIT file..

<ID:0/006> DO NOT TURN OFF TARGET!!

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

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

<ID:0/006> NAND Write Start!!

<ID:0/006> SingleDownload.

<ID:0/006> boot.img

<ID:0/006> recovery.img

<ID:0/006> system.img

<ID:0/006> vendor.img

<ID:0/006> carrier.img

<ID:0/006> userdata.img

<ID:0/006> modem.bin

<ID:0/006> Transmission Complete..

<ID:0/006> Now Writing.. Please wait about 2 minutes

<ID:0/006> Receive Response from boot-loader

<ID:0/006> modem_debug.bin

<ID:0/006> Transmission Complete..

<ID:0/006> Now Writing.. Please wait about 2 minutes

<ID:0/006> Receive Response from boot-loader

<ID:0/006> cache.img

<ID:0/006> odm.img

<ID:0/006> omr.img

<ID:0/006> RQT_CLOSE !!

<ID:0/006> RES OK !!

<ID:0/006> Removed!!

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

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

Only problem is, now my phone restarted after and is stuck on the Samsung Galaxy J7 Refine secured by Knox screen when you first turn on the phone. is it bricked?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Not necessarily. Reboot to download mode & only flash the (Oreo 8.0) BL file now
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Prophetless:
<ID:0/006> Added!!

<ID:0/006> Odin engine v(ID:3.1301)..

<ID:0/006> File analysis..

<ID:0/006> Total Binary size: 6 M

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

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

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

<ID:0/006> NAND Write Start!!

<ID:0/006> SingleDownload.

<ID:0/006> sboot.bin

<ID:0/006> param.bin

<ID:0/006> cm.bin

<ID:0/006> RQT_CLOSE !!

<ID:0/006> RES OK !!

<ID:0/006> Removed!!

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

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

Now, im in Android recovery. the options are:

Reboot system now

Reboot to bootloader

Apply update from ADB

Apply update from SD card

Wipe data/factory reset

Wipe cache partition

Mount /system

View recovery logs

Run graphics test

Power off

Do i reboot?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Droidriven:
Flashing via Odin does not always wipe the data partition during the flash process, sometimes, this data that is left over from before the flash causes issues after flashing, resulting in a bootloop.

One known solution to bootloop after flashing via Odin is to boot into stock recovery and factory reset then wipe cache partition, then reboot the device.

This may not be your issue but I've had to do this more than once after flashing via Odin.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Prophetless:
Rebooted phone after phone entered recovery mode, and

SUCCESS!!!

Phone is back to 8.0.0 Oreo! Thank you everyone who helped, especially ☆KØŁØЯΛĐØ☆

I'm so happy to be back
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Good deal my man. Glad we was able to help. If you have any more questions, ask here
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Im sure others will have the same issue so to recap, the past few pages have been how to downgrade the Galaxy J7 Refine from Pie 9.0 to Oreo 8.0 firmware.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Droidriven:
Would you consider posting a new thread correctly detailing the steps that you worked out from the assistance you received to successfully downgrade from 9.0 Pie to 8.0 Oreo. A new thread with the steps involved would be easier for others to find/follow than just these last few posts, a thread dedicated to the procedure would be much more visible to those that need it.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
If he doesn't then I will here soon. Not tonight though lol
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] david021188:
Android 9.0 Pie SM-J737p TWRP

I'm having issues with the files you provided. The ODIN v 3.12 and the TWRP 3.2 aren't working. When I load the .tar file into ODIN AP, nothing happens. It stays on file analysis indefinitely.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
You dont flash TWRP the ol fashion way this time. You have to root before you flash TWRP & you have to use a root app capable of flashing partitions. Read my guide buddy. Also the TWRP version provided was ported specifically for Oreo. I cant say for sure it will be portable to Pie so another version of TWRP may need to be made
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
I'm going to follow these directions to root my brothers j7 Refine. he's running Oreo, if i follow the directions in the op i should be good right?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Ensure you have stock firmware handy. The guide isnt an exact step by step so a little tech knowledge is required but if you have any questions I'm always around to help
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
Which build is stock for this device? For my j3 it was apl1 but im guessing for his it is ARG2?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
I cant remember. Any Oreo 8.0 version will suffice. The most recent Oreo firmware I have linked a couple times. The most recent being in one of my recent posts. So long as he doesn't update to Pie 9.0 before you root, you'll be good
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
Awesome, thank you! ?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
I ended up bricking his phone. He is on the april first update ACS2. I used odin this morning and installed the newest magisk manager this morning and allowed unknown sources and grabbed the stock boot image from the odin files, it was named boot. Img.lz4 so i removed tge lz4 part and tried to patch the boot image but it fails to repack every time ? I'm not so much concerned about flashing twrp as it is root access that we need. Do you have any suggestions? The patched odin and unpatched don't appear to work on my windows 10 machine, it pops up and crashes each time. He traveled a long way to get to me so i have a day to figure this out. Please help
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
.lz4 is a compression. You have to use an .lz4 img extractor to get the partition you need. Surf through this forum. Learn some sh*t my man. Most of these recent questions have already been answered. Same goes for getting Odin to work. I told you this wasnt a step by step guide lol
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
I get that. I got the boot.img extracted using lz4 v1 and ill give magisk manager another go with the correct boot img this time lol
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
Try using Magisk 18.1 or older, then just update after you root
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
Just an update, i went back and followed the directions to a T, i patched my stock boot.img with magisk after i flashed the phone back to stock ASC2 and every time i selected the option in magisk to create a tar file it would only spit out a magisk patched boot.img so i used 7zip to tar it and each time i flashed stock, rebooted download mode without booting into android, like you instructed and tried to flash the patched boot.img for my build using the patched odin it would open and start the process and would hang. There is a pie update available but im hesitant to take it as i don't want to worsen the situation. So as of now, it's flashed back to stock ASC2 with no root. Didn't mean to sound noobish earlier, I've been working on Android for many years. I spearheaded development on the j3 here on XDA and that wasn't easy by any means, but this process is ridiculous especially when you left out steps and also have the twrp directions before root. It's completely backwards lol
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] ☆KØŁØЯΛĐØ☆:
I know its backwards but I cant change it lol Where did you grab the ASC2 stock firmware from?

If you do update to Pie, it's very possible to port back to Oreo. We just helped a fellow member with that issue a few days ago so no worries there buddy
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Sands207:
I had to buy it. But as far as pie goes, which build are people rolling back to? I'm unsure of what build this j7 came with but i tried to downgrade to the build that another user posted 3 or 4 posts down on the first page but that was an immediate fail in odin so I'm wondering if another newer build behind the one im on will work. With the j3 we had to originally flash back to apl1 which was the original firmware my phone came from, most of my roms were also based from that build. I appreciate your help, I'll try with another firmware if i can find it. I don't give up very easy