Rooting galaxy on8 (j7xlte ) - Samsung Galaxy J7 Questions & Answers

ROOTING GALAXY ON8 J710FNDD
Also known as Samsung Galaxy On8 SM-J710FN/DF
NETWORK
Technology GSM / HSPA / LTE
LAUNCH
Announced 2016, September
Status Available. Released 2016, October
BODY
Dimensions 151.7 x 76 x 7.8 mm (5.97 x 2.99 x 0.31 in)
Weight 169 g (5.96 oz)
SIM Dual SIM (Micro-SIM, dual stand-by)
DISPLAY
Type Super AMOLED capacitive touchscreen, 16M colors
Size 5.5 inches (~72.3% screen-to-body ratio)
Resolution 1080 x 1920 pixels (~401 ppi pixel density)
Multitouch Yes
PLATFORM
OS Android OS, v6.0.1 (Marshmallow)
Chipset Exynos 7580 Octa
CPU Octa-core 1.6 GHz Cortex-A53
GPU Mali-T720MP2
MEMORY
Card slot microSD, up to 256 GB (dedicated slot)
Internal 16 GB, 3 GB RAM
CAMERA
Primary 13 MP, f/1.9, 28mm, autofocus, LED flash
Features Geo-tagging, touch focus, face detection, panorama, HDR
Video [email protected]
Secondary 5 MP, f/1.9, LED flash
SOUND
Alert types Vibration; MP3, WAV ringtones
Loudspeaker Yes
3.5mm jack Yes
COMMS
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot
Bluetooth v4.1, A2DP
GPS Yes, with A-GPS, GLONASS
NFC Yes
Radio FM radio, RDS, recording
USB microUSB v2.0
FEATURES
Sensors Accelerometer, proximity
Messaging SMS(threaded view), MMS, Email, Push Mail, IM
Browser HTML5
Java No
- ANT+ support
- MP4/WMV/H.264 player
- MP3/WAV/WMA/eAAC+/FLAC player
- Photo/video editor
- Document viewer
BATTERY
Removable Li-Ion 3300 mAh battery
Talk time Up to 17 h (3G)
Music play Up to 82 h
Kingroot is rooting this device not permanently

It seems Samsung cannot make their mind up what to call this device, so it's causing a lot of confusion.
Many servers are pointing to the wrong firmware for the J7XLTE and instead link to J7XELTE which is the J710F.
Even Samsung themselves don't seem to know what to call the device on their own Servers.
Looking at the source code they still call it the J710F!
If it's a J7 why didn't they just call it the J7 in the first place instead of On8?!
Honestly Samsung! :silly:

So futher to the above, it appears some f...wit in Samsungs development department didnt tell the guy in there that had a day off that they'd released a device called the Galaxy ON8 and this device was going to be called the SM-J710FN.:silly:
Unbeknown to Jonny Choi who was off that day when the On8 got released, he decided on his return to release another model, called the J7(2016) and also decided to call that one the SM-J710FN.
So now Jimmy choi has a model called the Galaxy ON8, model name SM-J710FN, device name J7XLTE.
Jonny Choi (Jimmy Choi's brother) has another device called the Galaxy J7(2016), model name SM-J710FN, device name J7XELTE (notice the addition of the E)
Anyone following this, I don't blame you if you're lost?
So what's the problem here, aren't they the same devices you ask? Well you would think so with the same model name, but oh no.
Because you see Jimmy Choi and Jonny Choi don't really talk to each other much nowadays due to falling out over a bowl of Kimchi many years ago and have never really talked since.
The problem is that due to Jonny and Jimmy's lack of communication they have decided to use different SOC's.
The pretend J7 the Galaxy ON8 has the Exynos 7580 SOC and the real J7 has the Exynos 7870 SOC. Now Jonny, it seems, had the good sense to release the source code for the real J710FN on Samsungs open source website. :good:
However, unfortunately Jimmy, due to his failing memory caused by not having enough Kimchi when he was younger (because as said Jonny was a greedy little 욕심쟁이 and pinched it all off his brother), seems to have forgotten to release the source code for his pretend J7 the ON8.
Due to this there is no source code to compile a custom kernel for TWRP.
However maybe, due to those crazy little guys in Samsungs development/marketing dept. who like to confuse the bejaysus out of the rest of the world and just love releasing the same device with different names, it maybe possible to use the kernel source from the J700T which uses the same Exynos 7580 SOC. :fingers-crossed:
As long as the hardware isn't too different theres a chance it may be able to boot at least recovery. So we will see. :cyclops:

Can't flash any recovery of samsung j7 twrp exynos 7580 by any way,tried all methods.
Kindly help.
Also tried twrp of j7 2016 exynos 7870.
Ofcourse didn't work.

thnks for reply
ashyx said:
So futher to the above, it appears some f...wit in Samsungs development department didnt tell the guy in there that had a day off that they'd released a device called the Galaxy ON8 and this device was going to be called the SM-J710FN.:silly:
Unbeknown to Jonny Choi who was off that day when the On8 got released, he decided on his return to release another model, called the J7(2016) and also decided to call that one the SM-J710FN.
So now Jimmy choi has a model called the Galaxy ON8, model name SM-J710FN, device name J7XLTE.
Jonny Choi (Jimmy Choi's brother) has another device called the Galaxy J7(2016), model name SM-J710FN, device name J7XELTE (notice the addition of the E)
Anyone following this, I don't blame you if you're lost?
So what's the problem here, aren't they the same devices you ask? Well you would think so with the same model name, but oh no.
Because you see Jimmy Choi and Jonny Choi don't really talk to each other much nowadays due to falling out over a bowl of Kimchi many years ago and have never really talked since.
The problem is that due to Jonny and Jimmy's lack of communication they have decided to use different SOC's.
The pretend J7 the Galaxy ON8 has the Exynos 7580 SOC and the real J7 has the Exynos 7870 SOC. Now Jonny, it seems, had the good sense to release the source code for the real J710FN on Samsungs open source website. :good:
However, unfortunately Jimmy, due to his failing memory caused by not having enough Kimchi when he was younger (because as said Jonny was a greedy little 욕심쟁이 and pinched it all off his brother), seems to have forgotten to release the source code for his pretend J7 the ON8.
Due to this there is no source code to compile a custom kernel for TWRP.
However maybe, due to those crazy little guys in Samsungs development/marketing dept. who like to confuse the bejaysus out of the rest of the world and just love releasing the same device with different names, it maybe possible to use the kernel source from the J700T which uses the same Exynos 7580 SOC. :fingers-crossed:
As long as the hardware isn't too different theres a chance it may be able to boot at least recovery. So we will see. :cyclops:
Click to expand...
Click to collapse
I think j7 2015 is same config. With galaxy on8 ?can we root it. plz help
Thnks in advance

ashyx said:
It seems Samsung cannot make their mind up what to call this device, so it's causing a lot of confusion.
Many servers are pointing to the wrong firmware for the J7XLTE and instead link to J7XELTE which is the J710F.
Even Samsung themselves don't seem to know what to call the device on their own Servers.
Looking at the source code they still call it the J710F!
If it's a J7 why didn't they just call it the J7 in the first place instead of On8?!
Honestly Samsung! :silly:
Click to expand...
Click to collapse
We can find stock rom for galaxy on8 at sammobile just search in the seach box j710fn and they will show 4 roms j710fnddu1apj1 is galaxy on 8

hhaawwkk said:
We can find stock rom for galaxy on8 at sammobile just search in the seach box j710fn and they will show 4 roms j710fnddu1apj1 is galaxy on 8
Click to expand...
Click to collapse
It's not the stock rom that's needed, it's the kernel source code.
Apart from SamMobile who have the correct firmware for the On8 many do not and simply have the incorrect J710F firmware.
Anyone not aware of this could potentially flash this firmware and wonder why their devices got bricked.
If indeed the J710F firmware does work on the ON8 then great I can use the kernel source, but I doubt it.

its working ??
ashyx said:
It's not the stock rom that's needed, it's the kernel source code.
Apart from SamMobile who have the correct firmware for the On8 many do not and simply have the incorrect J710F firmware.
Anyone not aware of this could potentially flash this firmware and wonder why their devices got bricked.
If indeed the J710F firmware does work on the ON8 then great I can use the kernel source, but I doubt it.
Click to expand...
Click to collapse
Yes i downloaded and flashed those roms and its working
(I tested cf-autoroot of j700h for galaxy on8 so it gone brick so i downloaded j710fnddu1apj1 and flashed via odin and my device working great) and i always use this rom for unbrick galaxy on8
J710fndd is galaxy on8 stock rom.

hhaawwkk said:
Yes i downloaded and flashed those roms and its working
(I tested cf-autoroot of j700h for galaxy on8 so it gone brick so i downloaded j710fnddu1apj1 and flashed via odin and my device working great) and i always use this rom for unbrick galaxy on8
J710fndd is galaxy on8 stock rom.
Click to expand...
Click to collapse
You misunderstand, yes THEY are the correct roms for On8, but if you search other websites it will not have the correct firmware for J7xlte, but for J7XELTE.
Such as here, all for J7XELTE not J7XLTE yet still called J710fn.
http://updato.com/firmware-archive-select-model?q=J710fn+&exact=1

yes
ashyx said:
You misunderstand, yes THEY are the correct roms for On8, but if you search other websites it will not have the correct firmware for J7xlte, but for J7XELTE.
Such as here, all for J7XELTE not J7XLTE yet still called J710fn.
http://updato.com/firmware-archive-select-model?q=J710fn+&exact=1
Click to expand...
Click to collapse
Yes right but j710fndd as i told stock rom we can find boot.img as a kernel and stock recovery. its perfect for compile TWRP for on8. I edited these files and cheked build.prop file i found for j7xlte written in file. But i modified this rom as pre rooted with some tools. Su injected into xbin and odin is not flashing this modified rom. I have poor knowledge about it

hhaawwkk said:
Yes right but j710fndd as i told stock rom we can find boot.img as a kernel and stock recovery. its perfect for compile TWRP for on8. I edited these files and cheked build.prop file i found for j7xlte written in file. But i modified this rom as pre rooted with some tools. Su injected into xbin and odin is not flashing this modified rom. I have poor knowledge about it
Click to expand...
Click to collapse
The problem is not obtaining the stock kernel, the problem is it probably won't work properly in TWRP.
Stock kernels are enforcing SELINUX which causes all sorts of issues with custom recovery.
Some will not even boot with the stock kernel. I need the source code to compile a custom kernel and remove SELINUX.
I will compile TWRP with the stock kernel, but its likely to cause issues.

ashyx said:
The problem is not obtaining the stock kernel, the problem is it probably won't work properly in TWRP.
Stock kernels are enforcing SELINUX which causes all sorts of issues with custom recovery.
Some will not even boot with the stock kernel. I need the source code to compile a custom kernel and remove SELINUX.
I will compile TWRP with the stock kernel, but its likely to cause issues.
Click to expand...
Click to collapse
Stock recovery
https://mega.nz/#!lxMmAYpD!tnbp0exnmQ_6jGodCYNSyLSWJnv5XM7Snjt9Pv2zCZw

Help
hhaawwkk said:
I think j7 2015 is same config. With galaxy on8 ?can we root it. plz help
Thnks in advance
Click to expand...
Click to collapse
Have tried all twrp variants fir j7 2015 on ON8 but none worked,apllied all tricks, none worked.
Wanna root and custom twrp for this.
It has exynos 7580,same as of j7 2015.
Only a red warning message is displayed on flashing twrp
RECOVERY NOT SEANDROID ENFORCING.
Please help
Highly obliged.

abrol_mighty said:
Have tried all twrp variants fir j7 2015 on ON8 but none worked,apllied all tricks, none worked.
Wanna root and custom twrp for this.
It has exynos 7580,same as of j7 2015.
Only a red warning message is displayed on flashing twrp
RECOVERY NOT SEANDROID ENFORCING.
Please help
Highly obliged.
Click to expand...
Click to collapse
Our friend is working on it wait for twrp and cmw for gaalaxy on8 j710fn

Good luck to u and all requesting here
hhaawwkk said:
Our friend is working on it wait for twrp and cmw for gaalaxy on8 j710fn
Click to expand...
Click to collapse
Really a reviving news
Good luck to u and all requesting here
Thanks
Eagerly waiting

hhaawwkk said:
Our friend is working on it wait for twrp and cmw for gaalaxy on8 j710fn
Click to expand...
Click to collapse
abrol_mighty said:
Really a reviving news
Good luck to u and all requesting here
Thanks
Eagerly waiting
Click to expand...
Click to collapse
I'm doubtful this will boot, but if it does it will probably have issues. If it does boot please post the recovery log file.
twrp_3.1.0-1_sm-j710fn_21417
.

ashyx said:
I'm doubtful this will boot, but if it does it will probably have issues. If it does boot please post the recovery log file.
twrp_3.1.0-1_sm-j710fn_21417
.
Click to expand...
Click to collapse
First thanks a lot bro
Its booting fine
I'm very happy but it's not mounting sd card and internal storage. I will try wipe all data of device I think it will work.
Again thanks a lot bro
Thnks thanks thanks

I have the same phone and succesfuly rooted with latest version of twrp 3.1.0 via odin. Then latest version of supersu 2.79 on a microsd card installed via twrp. I had to hit install button twice. First time not succesfuly rooted, after damn, it worked.( with enabled OEM unlocked , USB debugging and Unknown Sources from developer options ) No problems so far. Works great

l3o4nn said:
I have the same phone and succesfuly rooted with latest version of twrp 3.1.0 via odin. Then latest version of supersu 2.79 on a microsd card installed via twrp. I had to hit install button twice. First time not succesfuly rooted, after damn, it worked.( with enabled OEM unlocked , USB debugging and Unknown Sources from developer options ) No problems so far. Works great
Click to expand...
Click to collapse
But mine is not mounting sd card, internal and otg
All option is enabled oem unknown and debugging
Here is some screen shots and remind one thing never off oem form developer option.
Logs of twrp
Thanks to ashyx for great work

hhaawwkk said:
But mine is not mounting sd card, internal and otg
All option is enabled oem unknown and debugging
Here is some screen shots
Logs of twrp
Click to expand...
Click to collapse
Mine didn't mounted anything too. Only worked with a microsd card. I first put the microsd card with the phone turned on,downloaded supersu and just moved it to microsd. But you can also try to download it and install from internal storage. Anything readable.Anyway root its working. The big problem its recovery

Related

[Firmware] G935UUEU4API3 Odin Files & Modded Odin

I know there's another thread for this but it's an absolute cluster F*** to make heads or tails of. I wanted to simplify things.
Simply download files, download modded Odin and put files in proper slots in Odin.
This is will give you stock U firmware with the latest PK1 modem. Root isn't what it used to be so I don't bother with it, please don't ask me for root files and instructions of this firmware.
BL: https://drive.google.com/file/d/0B2xxd5WoIhEwVm9Jc09JM3FZdTg/view?usp=sharing
AP: https://drive.google.com/file/d/0B2xxd5WoIhEwaUFKWlVIZWlPeG8/view?usp=sharing
CP (PK1 Modem):https://drive.google.com/file/d/0B2xxd5WoIhEwT2p4VVdwdkttdkE/view?usp=sharing
CSC: https://drive.google.com/file/d/0B2xxd5WoIhEwUWUwczg3WmREdzA/view?usp=sharing
Here's the modded Odin that I used. This is from the root thread and never once failed to flash anything on any device I've thrown at it: http://d-h.st/gsDA
Thank you for simplifying this process.
You're welcome. I'm here to help.... The other thread was too much of a mess!
Thanks joe3681, for all of your efforts.
Where online can I find a list of updates or a version history for the Samsung S7 Edge (T-mobile)?
so this will work with the latest update from November? and also what are the benefits of U firmware? I haven't been able to find any good info anywhere. i have rooted and flashed before lol i just haven't been in the game for a while
U firmware seems smoother, it's bloat free. Only real downside is no advanced messaging.
serendipityguy said:
Thanks joe3681, for all of your efforts.
Where online can I find a list of updates or a version history for the Samsung S7 Edge (T-mobile)?
Click to expand...
Click to collapse
http://dl.pars-hamrah.com/index.php.../G Series/G935T - T-Mobile Galaxy S7 Firmware
ivananaya1 said:
so this will work with the latest update from November? and also what are the benefits of U firmware? I haven't been able to find any good info anywhere. i have rooted and flashed before lol i just haven't been in the game for a while
Click to expand...
Click to collapse
No, the U firmware is still the September security patch level. It's so much smoother/faster though. Especially rooted.
Thank you so much, this was obviously 100x easier to follow than the other thread.
DOMF said:
No, the U firmware is still the September security patch level. It's so much smoother/faster though. Especially rooted.
Click to expand...
Click to collapse
Not so sure about that.. Seems laggy still compared to stock and gets hot easier even after cpu fixes
nitroevo said:
Not so sure about that.. Seems laggy still compared to stock and gets hot easier even after cpu fixes
Click to expand...
Click to collapse
I followed the O.P. in the post root issues thread, doing nothing more and nothing less than what they said to do. No lag, normal temperature.
Thank you
OP thank you for the easy to follow instructions. I just bought my SM-G935T from ebay. I noticed some lag with the S7 Edge and of course all the Samsung and T-Mobile bloatware.
I flashed all of the files then did a system cache wipe. I have not noticed lag so far and now have 20 GB of the 32 GB free.
One question though. Where will the phone check for updates? Will it get updates from Samsung or T-Mobile?
TWRP help
.
I just got my T-Mobile Samsung Galaxy 7 Edge and have been doing a lot of reading here on XDA about this device. I have had all the galaxy's since Galaxy II.
I have rooted / custom recovery / custom ROM all of them. I know there basically is not much out yet as far as ROMS go for the S7e, but I would like to instal
TWRP and root the phone. I can not seem to get a straight answer as to how to do this exactly. Each "How-To" that I run into are a little bit different and scares
me a bit. If you could help me with any answers or links to my question(s) I would sure appreciate it.
1) I would like to odin into the phone the latest TWRP but I am not 100% sure which file to flash.
2) I would like to ROOT the phone if it is fairly safe at this point in development, but again I have heard of at least 2 different methods to do this.
3) Please advise on which file to use and/or method. My phone DOES connect up with my PC just fine via USB and I have ADB working also.​
.
Current Phone
[*]T-Mobile Samsung Galaxy S7 Edge
[*]Device Status
[*]Official
[*]Model Number
[*]SM-G935T
[*]Android Version
[*]6.0.1
[*]Security Patch Level
[*]November 1st, 2016
[*]BaseBand Version
[*]G935TUVU4APK1
[*]Build Number
[*]MMB29M.G935TUVU4APK1
[*]OEM Unlock
[*]ON
[*]USB Debugging
[*]ON
Thibor69 said:
.
I just got my T-Mobile Samsung Galaxy 7 Edge and have been doing a lot of reading here on XDA about this device. I have had all the galaxy's since Galaxy II.
I have rooted / custom recovery / custom ROM all of them. I know there basically is not much out yet as far as ROMS go for the S7e, but I would like to instal
TWRP and root the phone. I can not seem to get a straight answer as to how to do this exactly. Each "How-To" that I run into are a little bit different and scares
me a bit. If you could help me with any answers or links to my question(s) I would sure appreciate it.
1) I would like to odin into the phone the latest TWRP but I am not 100% sure which file to flash.
2) I would like to ROOT the phone if it is fairly safe at this point in development, but again I have heard of at least 2 different methods to do this.
3) Please advise on which file to use and/or method. My phone DOES connect up with my PC just fine via USB and I have ADB working also.​
.
Current Phone
[*]T-Mobile Samsung Galaxy S7 Edge
[*]Device Status
[*]Official
[*]Model Number
[*]SM-G935T
[*]Android Version
[*]6.0.1
[*]Security Patch Level
[*]November 1st, 2016
[*]BaseBand Version
[*]G935TUVU4APK1
[*]Build Number
[*]MMB29M.G935TUVU4APK1
[*]OEM Unlock
[*]ON
[*]USB Debugging
[*]ON
Click to expand...
Click to collapse
Spend more time reading around the forums before you try anything, but to answer your questions:
1) TWRP not possible on TMobile S7/S7E
2) Root is possible, see here: http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
make sure to read the entire thread and note the issues you may run into
3) See #2 above, has all that info in the thread
fl_gator_dad said:
OP thank you for the easy to follow instructions. I just bought my SM-G935T from ebay. I noticed some lag with the S7 Edge and of course all the Samsung and T-Mobile bloatware.
I flashed all of the files then did a system cache wipe. I have not noticed lag so far and now have 20 GB of the 32 GB free.
One question though. Where will the phone check for updates? Will it get updates from Samsung or T-Mobile?
Click to expand...
Click to collapse
@fl_gator_dad, it will check with Samsung. Mind you they dont update this as often as carrier versions release their incremental updates
snpalavan said:
Spend more time reading around the forums before you try anything, but to answer your questions:
1) TWRP not possible on TMobile S7/S7E
2) Root is possible, see here: http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
make sure to read the entire thread and note the issues you may run into
3) See #2 above, has all that info in the thread
Click to expand...
Click to collapse
Hello,
thank you for replying. I have been using TWRP on my past 6 phones. Is there some reason why
it wont work on this one ? I did a little more reading and found this
https://twrp.me/devices/samsunggalaxys7edge.html
Support Status: Current
Maintainer: jcadduono
Code Name: hero2lte
Also ... if TWRP isn't working then what custom recovery are you and all using ? Clockwork ...?
.
Thank you
Thibor69 said:
Hello,
thank you for replying. I have been using TWRP on my past 6 phones. Is there some reason why
it wont work on this one ? I did a little more reading and found this
https://twrp.me/devices/samsunggalaxys7edge.html
Support Status: Current
Maintainer: jcadduono
Code Name: hero2lte
Also ... if TWRP isn't working then what custom recovery are you and all using ? Clockwork ...?
.
Thank you
Click to expand...
Click to collapse
Well if you continue searching and reading some more, you will see that twrp only works on non locked bootloaders. Any carrier driven Samsung device has a locked bootloader and twrp will not work. We have the snapdragon and not the exynos. If you need to have twrp then you need to get an S7 edge Exynos version. There is no working custom recovery for the snapdragon version phones as of yet.
galaxyuser88 said:
Well if you continue searching and reading some more, you will see that twrp only works on non locked bootloaders. Any carrier driven Samsung device has a locked bootloader and twrp will not work. We have the snapdragon and not the exynos. If you need to have twrp then you need to get an S7 edge Exynos version. There is no working custom recovery for the snapdragon version phones as of yet.
Click to expand...
Click to collapse
.
Wow I see, Ok thank you for your time.
.
joe3681 said:
@fl_gator_dad, it will check with Samsung. Mind you they dont update this as often as carrier versions release their incremental updates
Click to expand...
Click to collapse
Thank you. That is a shame. I would think, incorrectly, that the unlocked GS7 firmware would be the baseline to build the carrier firmware.
fl_gator_dad said:
Thank you. That is a shame. I would think, incorrectly, that the unlocked GS7 firmware would be the baseline to build the carrier firmware.
Click to expand...
Click to collapse
Yeah, you'd think! The international is the one that gets everything first.
The unlocked firmware favors T-Mobile though offering T-Mobile customers features that other users don't get.

Overclock J330FN

Is there any custom kernel that can allow overclocking on the J330FN Oreo?
xda general said:
Is there any custom kernel that can allow overclocking on the J330FN Oreo?
Click to expand...
Click to collapse
Nope. It is highly unlikely that a custom kernel or even rom to be made for this device as no one is developing anything on it. The device has reached end of life considering it is a budget device after all.
thepcwiz101 said:
Nope. It is highly unlikely that a custom kernel or even rom to be made for this device as no one is developing anything on it. The device has reached end of life considering it is a budget device after all.
Click to expand...
Click to collapse
Ok thank you and there is actually one persom he goes by the name of ashynx he made it able to get root and twrp on oreo for this device he also made some custom roms for the nougat version of this device
xda general said:
Ok thank you and there is actually one person he goes by the name of ashynx he made it able to get root and twrp on oreo for this device he also made some custom roms for the nougat version of this device
Click to expand...
Click to collapse
No problem and i am aware since she helped make sampwned32 for the sm-j327t and sm-j327t1 I found the root method that was used on the s8 variant with a locked bootloader and brought it up and even tested the root method on the device and it worked. But a month later samsung released a new update that patched it. If it wasn't for ashyx converting the files from ARM64 to ARM this method would have never worked. Also after samsung patched the root method they only released one more security update and ended up cancelling the android oreo update for metropcs and tmobile after we was told our device would get it. Oh boy i was pretty pissed. Like come on samsung you could atleast unlock the device's bootloader and allow us to make our own custom roms which would be alot better and would be oreo based. It is sad how samsung forgot about us and didn't even bother to release a new phone to the metropcs and tmobile market in the budget area. The mid range J7 Prime got more love than this device did fr.
thepcwiz101 said:
No problem and i am aware since she helped make sampwned32 for the sm-j327t and sm-j327t1 I found the root method that was used on the s8 variant with a locked bootloader and brought it up and even tested the root method on the device and it worked. But a month later samsung released a new update that patched it. If it wasn't for ashyx converting the files from ARM64 to ARM this method would have never worked. Also after samsung patched the root method they only released one more security update and ended up cancelling the android oreo update for metropcs and tmobile after we was told our device would get it. Oh boy i was pretty pissed. Like come on samsung you could atleast unlock the device's bootloader and allow us to make our own custom roms which would be alot better and would be oreo based. It is sad how samsung forgot about us and didn't even bother to release a new phone to the metropcs and tmobile market in the budget area. The mid range J7 Prime got more love than this device did fr.
Click to expand...
Click to collapse
Yes it certainly did

GALAXY J3 2018 (SM-327A) (j3popelteuc) J327AUCU2BRI3

PLEASE HELP ME WITH THIS PHONE LOOKING TO DO ROOT AND RECOVERY ALL THAT JAZZ THERE IS NOTHING ON THE INTERNET TO HELP WITH THAT, INCLUDING XDA!!!!!!!! ITS ALWAYS J3......U, T, T1, P,,NEVER A, ATT, EXYNOS 7570 8.1
OREO:good:
Peoplesarmy said:
PLEASE HELP ME WITH THIS PHONE LOOKING TO DO ROOT AND RECOVERY ALL THAT JAZZ THERE IS NOTHING ON THE INTERNET TO HELP WITH THAT, INCLUDING XDA!!!!!!!! ITS ALWAYS J3......U, T, T1, P,,NEVER A, ATT, EXYNOS 7570 8.1
OREO:good:
Click to expand...
Click to collapse
Bootloader is locked so no root for this device.
REALLY
ashyx said:
Bootloader is locked so no root for this device.
Click to expand...
Click to collapse
really terrible news
Yet I see all the posts on the note 8 and the s5series with locked bootloaders and root weather it be samfail for the note or sampwnd on the s5 and why not with the j3 series? Is it because it's a cheap ass phone and the dev's dont want to waste time to try? I see more j3 and j7 phones flooding the market than the higher end phones so what gives?
krak1nthor said:
Yet I see all the posts on the note 8 and the s5series with locked bootloaders and root weather it be samfail for the note or sampwnd on the s5 and why not with the j3 series? Is it because it's a cheap ass phone and the dev's dont want to waste time to try? I see more j3 and j7 phones flooding the market than the higher end phones so what gives?
Click to expand...
Click to collapse
Those devices had engineering firmware available the J327a does not.
However you may get lucky and be able to the flash the engineering firmware available for the J327T as these devices have the same specs.
https://forum.xda-developers.com/galaxy-j3-2017/how-to/root-sampwned32-samsung-j3-prime-sm-t3761497
bummer
I am working on a similar device to build lineage os for the at&t model, but I can't find the proprietary blobs to make it possible, as it fails with an error "do you have the right repo manifest?", can anyone help me?

No Twrp For Note 10 lite

This device is do popular but has no support here , disappointment!
M7maddmagedd said:
This device is do popular but has no support here , disappointment!
Click to expand...
Click to collapse
If it was popular then there would be threads and TWRP and ROMs but the fact that there's not tells you, it's not....
I think you are righ
I bought s10+ over it
I gave up on it. And the developer that did a Magisk flashable mod I think has also moved on. I tested for him but the device was not very popular. Thinking about trying to sell it or just gifting it to someone. Haven't even turned it on for weeks.
My SM-N935F NoteFE Floyd V5
DEX or HDMI support, is the most important feature for a DEVELOPER TO CREATE FOR NOTE 10LITE!​Hardware wise is capable, but SOFTWARE is not permitting this feature. I hope that a DEVELOPER will be so kind to HELP on that!!!
And propably a valid twrp version to flash it!
maybe someone, i.e. @butchieboy ?, smart is capable of porting twrp to the Note 10 lite with this instruction which seems to be easy for linux users or with those skills. See here: https://appuals.com/how-to-port-twrp-for-android-without-source/
On my side I am a bit familiar with Android Image Kitchen for windows (so far only used for themeing twrp for other devices to my needs, which worked excellent) but the above guide says it should be done with AIK for Linux, so I am afraid to mix (brick) things up....
XDAMaxe said:
maybe someone, i.e. @butchieboy ?, smart is capable of porting twrp to the Note 10 lite with this instruction which seems to be easy for linux users or with those skills. See here: https://appuals.com/how-to-port-twrp-for-android-without-source/
On my side I am a bit familiar with Android Image Kitchen for windows (so far only used for themeing twrp for other devices to my needs, which worked excellent) but the above guide says it should be done with AIK for Linux, so I am afraid to mix (brick) things up....
Click to expand...
Click to collapse
If it was as simple as stated in those instructions I would have had this fixed ages ago, but it is not. It relies on signatures that need to be generated to match the devices vbmeta.img file otherwise it will not boot. I tried this, but got nowhere with the signatures and little support from other devs to help me with creating the signatures. @butchieboy has a Magisk flashable I created to get some mods in the device but other things like screen mirroring or HDMI being fixed need to be done directly on the image of the device. I will release an R version of the latest firmware N770FXXS7DUB1_N770FOJM7DUB1_XSG, which is the one I have and release it soon.
Whats up Javix. I was testing Twrp for another developer a week ago. We got knowhere. I give up on the 10 lite as At&t has blocked it and i can no longer use it on my Network. So I basically have a Mint condition phone that is useless to me. Damn At&t are starting to do this with any F version device when you try to use it on their network it automatically suspends your number as an unauthorized device. I bought a S20FE unlocked bootloader Twrp and rooted. Good luck with 10 lite, mine is back in the box..lol
butchieboy said:
Whats up Javix. I was testing Twrp for another developer a week ago. We got knowhere. I give up on the 10 lite as At&t has blocked it and i can no longer use it on my Network. So I basically have a Mint condition phone that is useless to me. Damn At&t are starting to do this with any F version device when you try to use it on their network it automatically suspends your number as an unauthorized device. I bought a S20FE unlocked bootloader Twrp and rooted. Good luck with 10 lite, mine is back in the box..lol
Click to expand...
Click to collapse
Hi there butchieboy!
If your N10Lite is of no use to you, is there a chance I can help with TWRP and ROMs?
I can help with TWRP (maybe official too) and porting ROMs. You can check my credentials as I have ported many roms to the Galaxy M30.
Let me know if you are interested. Message me on telegram @cha0scl0wn.
Regards,
cha0scl0wn.
Sold it
butchieboy said:
Sold it
Click to expand...
Click to collapse
If I had the option I would sell it
NHK said:
If I had the option I would sell it
Click to expand...
Click to collapse
Well traded it in to Samsung for S20FE...glad I did..I'm rooted with Twrp...well worth it
butchieboy said:
Well traded it in to Samsung for S20FE...glad I did..I'm rooted with Twrp...well worth it
Click to expand...
Click to collapse
S20FE is about $100-150 more expensive than note 10 lite in my place ($450)
With trade I only paid $230

Question TWRP files for g stylus 5g 2022 (XT2215-4)

I have recently acquired a carrier unlocked Motorola G Stylus 5G 2022 (XT2215-4) and have successfully unlocked the boot loader.
I have been looking for TWRP recovery files/images for my device but have been unsuccessful up to this point. I am considering compiling some from source, if need be, at which point I will likely compile lineage from some source for it as well.
Does anyone know if the 2021 (Denver/Osaka) models can or should be used as a template for attempting this? Additionally is anyone looking into porting to this device? I am a bit new to this and wouldn't mind a bit of assistance.
Thanks!
Just got the device the other day but haven't bootloader unlocked it. I'm assuming due to the different processor alone it's likely we'll need our own device tree. I haven't really done that stuff before but maybe if we get a Telegram group going we could get some Moto vets to help out maybe?
I have been able to extract the dtb.* files from the firmware's dtbo.img however I have not attempted to compile it into the dts.img via the dtc utiliity like many of the tutorials on the subject say you need to do. This is because none of the ones I found say anything about having to deal with multiple dtb files like the ones I was presented with when I extracted the dtbo.img from the device firmware. I didnt want to try it and have it be totally wrong.
On the motorola github I have posted an issue requesting the release of the kernel, device tree, and any other pertinent files, pertaining to the stock firmware for the XT2215-4. Hopefully they come back in an reasonable time so that I can move forward with compiling Lineage OS for it.
Rooting:
Once you get the bootloader unlocked, you can root it by flashing the boot.img that has been patched with Magisk using fastboot. Perhaps Ill post a step by step guide for this for the XT2215-4 in the next day or so.
Tokth said:
I have been able to extract the dtb.* files from the firmware's dtbo.img however I have not attempted to compile it into the dts.img via the dtc utiliity like many of the tutorials on the subject say you need to do. This is because none of the ones I found say anything about having to deal with multiple dtb files like the ones I was presented with when I extracted the dtbo.img from the device firmware. I didnt want to try it and have it be totally wrong.
On the motorola github I have posted an issue requesting the release of the kernel, device tree, and any other pertinent files, pertaining to the stock firmware for the XT2215-4. Hopefully they come back in an reasonable time so that I can move forward with compiling Lineage OS for it.
Rooting:
Once you get the bootloader unlocked, you can root it by flashing the boot.img that has been patched with Magisk using fastboot. Perhaps Ill post a step by step guide for this for the XT2215-4 in the next day or so.
Click to expand...
Click to collapse
I would love a guide or at least the boot.img file
IronDwarf said:
I would love a guide or at least the boot.img file
Click to expand...
Click to collapse
Here you go! https://forum.xda-developers.com/t/rooting-the-xt2215-4-motorola-g-stylus-5g-2022.4456545/
Tokth said:
Here you go! https://forum.xda-developers.com/t/rooting-the-xt2215-4-motorola-g-stylus-5g-2022.4456545/
Click to expand...
Click to collapse
Thanks Buddy !
Yes because the chipset differs between 2021 and 2022 models, you cannot use same device trees :/
Just purchased this device, twrp done for it yet ?
PizzaG said:
Just purchased this device, twrp done for it yet ?
Click to expand...
Click to collapse
Nothing yet that I kmow
IronDwarf said:
Nothing yet that I kmow
Click to expand...
Click to collapse
K, I'll get to work on it then
PizzaG said:
K, I'll get to work on it then
Click to expand...
Click to collapse
That sounds awesome, thanks
Tokth said:
I have recently acquired a carrier unlocked Motorola G Stylus 5G 2022 (XT2215-4) and have successfully unlocked the boot loader.
I have been looking for TWRP recovery files/images for my device but have been unsuccessful up to this point. I am considering compiling some from source, if need be, at which point I will likely compile lineage from some source for it as well.
Does anyone know if the 2021 (Denver/Osaka) models can or should be used as a template for attempting this? Additionally is anyone looking into porting to this device? I am a bit new to this and wouldn't mind a bit of assistance.
Thanks!
Click to expand...
Click to collapse
This is a mediatek phone, you will have to wait on the Milan files from Moto directly, and last I checked they haven't released the tree yet.
Moderators feel free to delete this post. Accidental refresh.
Articul8Madness said:
This is a mediatek phone, you will have to wait on the Milan files from Moto directly, and last I checked they haven't released the tree yet.
Click to expand...
Click to collapse
XT2215-4 is not mediatek it's Qualcomm snapdragon SDM695 w same sm6375 chipset as the xiaomi note 11 Pro, I would rather have Orange box recovery cuz I'm spooled to the OTA update block, I was about to bust out studio and Android kitchen myself and see if I could Port it from the xiaomi note 11 Pro but I know the kernel going to have different drivers as the 11 pro has a lot better camera like 100 megapixel versus 50 megapixel a few other small details different LTE bands.. maybe enough to just swap the kernels out and Android kitchen to get a buggy twrp up in there interim as we're I'm waiting the kernel ource code and devised tree Moto has only posted like three of their 12 devices I was about to supposed to request when I saw his already posted I'll try to back him up maybe if we bug the crap out of them the xiaomi people had to do that.. they have ricedroid, PE, lineage evolution x, Sapphire, and arrow all kinds of ROMs for the same chipset Xiaomi note 11 pro / Poco note 4 (apparently the Paco is the same device just different country branded and somehow it's the only one that's allowed to play like pubg battlegrounds and stuff cuz they're trying to push the pacos or whatever) i ran across it all in the telegram and I still don't think they have gotten their source code yet. I'm not sure how they even ported all this. Because the telegram thread with all the ROMs I was looking at ror porting and still requesting people to spam xiaomi' about releasing the source
I dumped and built up a recovery device tree for xt2215-4, then built twrp from source with the twrp 12.1 branch
-STATUS-
twrp boots
touch currently broken
usb currently broken
Will post more when I have more to post
PizzaG said:
I dumped and built up a recovery device tree for xt2215-4, then built twrp from source with the twrp 12.1 branch
-STATUS-
twrp boots
touch currently broken
usb currently broken
Will post more when I have more to post
Click to expand...
Click to collapse
Awesome !
ghettiguru said:
XT2215-4 is not mediatek it's Qualcomm snapdragon SDM695 w same sm6375 chipset as the xiaomi note 11 Pro, I would rather have Orange box recovery cuz I'm spooled to the OTA update block, I was about to bust out studio and Android kitchen myself and see if I could Port it from the xiaomi note 11 Pro but I know the kernel going to have different drivers as the 11 pro has a lot better camera like 100 megapixel versus 50 megapixel a few other small details different LTE bands.. maybe enough to just swap the kernels out and Android kitchen to get a buggy twrp up in there interim as we're I'm waiting the kernel ource code and devised tree Moto has only posted like three of their 12 devices I was about to supposed to request when I saw his already posted I'll try to back him up maybe if we bug the crap out of them the xiaomi people had to do that.. they have ricedroid, PE, lineage evolution x, Sapphire, and arrow all kinds of ROMs for the same chipset Xiaomi note 11 pro / Poco note 4 (apparently the Paco is the same device just different country branded and somehow it's the only one that's allowed to play like pubg battlegrounds and stuff cuz they're trying to push the pacos or whatever) i ran across it all in the telegram and I still don't think they have gotten their source code yet. I'm not sure how they even ported all this. Because the telegram thread with all the ROMs I was looking at ror porting and still requesting people to spam xiaomi' about releasing the source
Click to expand...
Click to collapse
I have a Mediatek variant. I have CPU-Z as a confirmation. I also have made it quite clear in my guides that I have a Factory Unlocked version purchased from Best Buy. So I'm on Milan, Mediatek Helio P65 MT6768 board.
It would behoove you to read and do research before spouting out unconfirmed information.
Articul8Madness said:
I have a Mediatek variant. I have CPU-Z as a confirmation. I also have made it quite clear in my guides that I have a Factory Unlocked version purchased from Best Buy. So I'm on Milan, Mediatek Helio P65 MT6768 board.
It would behoove you to read and do research before spouting out unconfirmed information.
Click to expand...
Click to collapse
I'm unclear what you are responding to. My xt2215-4 is also qualcomm. It also reports the board as holi. Mine was also purchased carrier unlocked from best buy. After sifting through the internal guts of the rom after super and partitions inside have been extracted, it's def a qualcomm device. What is your model # ?
I have also rebuilt the super image to use a GSI rom but I cannot seem to get service fully functional. If anyone would like to help me work on it, join my Telegram Android group and let me know. I have twrp built but also need some help getting the touchscreen script working as well as usb functioning. I know my device is using a Novatek screen as repoted by fastboot getvar all
PizzaG Telegram Android Group
PizzaG said:
I dumped and built up a recovery device tree for xt2215-4, then built twrp from source with the twrp 12.1 branch
-STATUS-
twrp boots
touch currently broken
usb currently broken
Will post more when I have more to post
Click to expand...
Click to collapse
You could wait for Moto to release the trees. Nobody's made a request so that could be the delay.
PizzaG said:
I'm unclear what you are responding to. My xt2215-4 is also qualcomm. It also reports the board as holi. Mine was also purchased carrier unlocked from best buy. After sifting through the internal guts of the rom after super and partitions inside have been extracted, it's def a qualcomm device. What is your model # ?
I have also rebuilt the super image to use a GSI rom but I cannot seem to get service fully functional. If anyone would like to help me work on it, join my Telegram Android group and let me know. I have twrp built but also need some help getting the touchscreen script working as well as usb functioning. I know my device is using a Novatek screen as repoted by fastboot getvar all
PizzaG Telegram Android Group
Click to expand...
Click to collapse
I'm responding to your original post where you insinuated I didn't have a Mediatek device, which I do. I think the issue is, I thought you were referring to my G Stylus 2022, which is
Moto G Stylus (2022) XT-2211 Mediatek Variant.​and not the 2215.

Categories

Resources