Related
Hi Team,
Coming from a Nexus 4 . I am about to buy the Oneplus ( chinese Variant ) preloaded with CM11s . Reason for buying this variant is that the international version is no where to be found in the country. Before picking up the phone i have a few question
1-) Besides the OS are there any other hardware level changes in amongst the two variants ?
2-) Will the preloaded CM11 get OTAs ?
3-) Will i be able to flash the custom roms which are for the international version on the chinese variant ? ( this is a big concern )
4-) How would you rate the phone overall out of 10 ( just for fun )
This has been asked a few time already but here goes:
1.) Besides the "Cyanogenmod" branding on the back of the device and a slight variation of supported LTE bands there are NO hardware differences.
2.) There is no reason it shouldn't,mine did, came with CM11s installed on a Chinese variant,and had an OTA update as soon as i turned it on.
3.) YES absolutely
4.) 9.0 - 9.5 IMO
PS: Depending on where you reside you might just wanna look into the LTE bands situation to ensure the device will work with your carrier.
Hope that help.
S M G said:
This has been asked a few time already but here goes:
1.) Besides the "Cyanogenmod" branding on the back of the device and a slight variation of supported LTE bands there are NO hardware differences.
2.) There is no reason it shouldn't,mine did, came with CM11s installed on a Chinese variant,and had an OTA update as soon as i turned it on.
3.) YES absolutely
4.) 9.0 - 9.5 IMO
PS: Depending on where you reside you might just wanna look into the LTE bands situation to ensure the device will work with your carrier.
Hope that help.
Click to expand...
Click to collapse
Thanks bro ! that was the feedback i was looking for !
Lowresolution said:
Thanks bro ! that was the feedback i was looking for !
Click to expand...
Click to collapse
No problem at all. :good:
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
So it looks like the OpenKirin site is finally here and they have their Lineage based ROMs available for download.
Now it does say the 970 is a supported chipset, but it doesn't list the P20/Pro as a device.
From what I can see it looks like EMUI camera and gallery are fully supported.
I'm not rooted etc. but does anyone know who's working on this project or if it can be tested on our device at all?
Would be keen to see a nice working Lineage ROM with full support of the EMUI camera.
Here's the site: OpenKirin.net
MrDanMak said:
So it looks like the OpenKirin site is finally here and they have their Lineage based ROMs available for download.
Now it does say the 970 is a supported chipset, but it doesn't list the P20/Pro as a device.
From what I can see it looks like EMUI camera and gallery are fully supported.
I'm not rooted etc. but does anyone know who's working on this project or if it can be tested on our device at all?
Would be keen to see a nice working Lineage ROM with full support of the EMUI camera.
Here's the site: OpenKirin.net
Click to expand...
Click to collapse
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
dladz said:
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
Click to expand...
Click to collapse
It seems that it's treble via fastboot only. We have to w8 and see for confirmation, I guess.
dladz said:
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
Click to expand...
Click to collapse
1 - YNWA
2 - what would be the advantage of the Treble releases? My dream would be that its more like stock but ..
YNWA
Treble is just a system image, probably won't completely work for every device, probably won't ever be fixed for every device.
Whereas a full ROM, usually only has to be fixed / tweaked once.[
When you install a ROM you flash most of the device and it's generally in a zip format, whereas a treble ROM is an IMG and you flash it only to the system partition leaving everything else intact.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
@MrDanMak
You do know that we have lineage in the ROM section right? And that the camera had been ported and its working?
P20 camera.
dladz said:
YNWA
Treble is just a system image, probably won't completely work for every device, probably won't ever be fixed for every device.
Whereas a full ROM, usually only has to be fixed / tweaked once.[
When you install a ROM you flash most of the device and it's generally in a zip format, whereas a treble ROM is an IMG and you flash it only to the system partition leaving everything else intact.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
@MrDanMak
You do know that we have lineage in the ROM section right? And that the camera had been ported and its working?
P20 camera.
Click to expand...
Click to collapse
YNWA indeed! Nice to see fellow redmen in here.
Yeah I know there is a Lineage ROM, but I was under the impression the camera isn't fully working right? It still has the gallery issue doesn't it?
If you read the FAQs you will see that they mention you shouldn't flash the current downloads on the P20/Pro. They will provide builds for this phone at a later date.
MrDanMak said:
YNWA indeed! Nice to see fellow redmen in here.
Yeah I know there is a Lineage ROM, but I was under the impression the camera isn't fully working right? It still has the gallery issue doesn't it?
Click to expand...
Click to collapse
Yea that's true but at the same time, the fact that the p20 camera app actually starts is great news.
I'm sure the gallery app can be used, haven't looked into it myself but it should be fixable.
dladz said:
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
Click to expand...
Click to collapse
Hi mate I am using a UK c782 any custom rom you would recommend?
Sttrory said:
Hi mate I am using a UK c782 any custom rom you would recommend?
Click to expand...
Click to collapse
So there's very few custom ROM's here for the Pro, there's one called Romaur and a Lineage ROM, haven't flashed either.
All i did was unlock bootloader, install TWRP and Root, then i've tweaked the OS so that it's faster and more stable.
Themed it and for me that's enough.
I did debrand though so you may want to look at that first, the c432 device is the EU one i think or whats predominantly used in EU countries, mine was the c782 L09 which is the single sim variant from EE.
Changing over to c432 has allowed me to get the latest updates like 120 - 128 and i think at some point b131 will drop.
The c782 afaik is still on 110 which is a bit crap.
Check the guide here to debrand: https://forum.xda-developers.com/showpost.php?p=76785704&postcount=152 if it's something you want to do.
Guide to install OTA updates when you have TWRP installed and are rooted etc: https://forum.xda-developers.com/showpost.php?p=76844754&postcount=254
Hopefully there will be more ROM's but at the moment it's extremely quiet.
Treble is a bit of an issue for us i think because the installation method requires the use of TWRP to wipe and i've read somewhere that it can't wipe correctly so it fails when you flash a treble IMG.
There's a few great guides to install treble in one of the threads over in the project treble section, take a look.
I'll get around to installing treble img's at some point but can't today.
dladz said:
So there's very few custom ROM's here for the Pro, there's one called Romaur and a Lineage ROM, haven't flashed either.
All i did was unlock bootloader, install TWRP and Root, then i've tweaked the OS so that it's faster and more stable.
Themed it and for me that's enough.
I did debrand though so you may want to look at that first, the c432 device is the EU one i think or whats predominantly used in EU countries, mine was the c782 L09 which is the single sim variant from EE.
Changing over to c432 has allowed me to get the latest updates like 120 - 128 and i think at some point b131 will drop.
The c782 afaik is still on 110 which is a bit crap.
Check the guide here to debrand: https://forum.xda-developers.com/showpost.php?p=76785704&postcount=152 if it's something you want to do.
Guide to install OTA updates when you have TWRP installed and are rooted etc: https://forum.xda-developers.com/showpost.php?p=76844754&postcount=254
Hopefully there will be more ROM's but at the moment it's extremely quiet.
Treble is a bit of an issue for us i think because the installation method requires the use of TWRP to wipe and i've read somewhere that it can't wipe correctly so it fails when you flash a treble IMG.
There's a few great guides to install treble in one of the threads over in the project treble section, take a look.
I'll get around to installing treble img's at some point but can't today.
Click to expand...
Click to collapse
Many thanks mate
Sttrory said:
Many thanks mate
Click to expand...
Click to collapse
no worries man, but id say read up before committing, this phone is so different to any device i've ever had.
Sttrory said:
Many thanks mate
Click to expand...
Click to collapse
May I know what does debrand means ?
olygopoly said:
May I know what does debrand means ?
Click to expand...
Click to collapse
If you bought you're device in the UK it's highly likely it's branded (even if there's no visual indications that it is) to a mobile network. Mine was bought via Mobiles.co.uk on 02 network and I assumed it was completely unbranded as there was no bloatware or 02 branding but apparently any updates from Huawei need to go though 02's checks before being pushed out and so updates are slooooowwww. debranding is essentially removing any ties to a network thus you get the Huawei updates as soon as they push them out.
Deano1889 said:
If you bought you're device in the UK it's highly likely it's branded (even if there's no visual indications that it is) to a mobile network. Mine was bought via Mobiles.co.uk on 02 network and I assumed it was completely unbranded as there was no bloatware or 02 branding but apparently any updates from Huawei need to go though 02's checks before being pushed out and so updates are slooooowwww. debranding is essentially removing any ties to a network thus you get the Huawei updates as soon as they push them out.
Click to expand...
Click to collapse
Thanks for the explaination
Previously I have owned phones by Vivo Oppo and Oneplus but I am new to Realme. What are the chances that this phone gains TWRP and/or any custom ROMs? Thanx
Really hard to say. The custom rom / twrp development has been really slow on the Realme X2 Pro, which means that not a lot of devs are working on Realme hardware.
On the other hand. The development of the XT is quite Good.
I don't think it's coming any soon
Also I think realme doesn't allow unlocking bootloader in EU.
I just hope they don't follow the footsteps from OPPO, which unlocking bootloader is a pain of the butt.
Is any possibility to get MIUI here ... i'm gonna pre order that thing but really want MIUI.
Be a little patient. Its gonaa be a while before we see something here.
Kernel Source out just about 12 hours ago...
https://github.com/realme-kernel-opensource/realmeX50pro_AndroidQ-kernel-source
Kernel Source
Yes I made a post about it because someone wanted my help if they ran into issues on an X50 custom kernel I thought they meant X50 Pro and found the source code. Anybody attempt compiling it yet?
Regarding roms.... I compares network bands in Chinese and global versions. Look same so if I buy Chinese version can I upgrade software with EU rom (realme UI already) and get multilanguage? Or it will brick device?
It's not possible to flash global ROM on CN device.
tidschi said:
It's not possible to flash global ROM on CN device.
Click to expand...
Click to collapse
Are you sure? Can you please tell us some details regarding this?
I'm, wasn't possible on X2 Pro, which I had before this device and is still not possible on X50 Pro. I tried myself...
On X2 Pro people said because of different partitions or / and sizes.
Working on custom rom?
Hi,
Are you already working on one or more custom rom?
I would be very happy to get an answer!
Realme x50 pro said:
Hi,
Are you already working on one or more custom rom?
I would be very happy to get an answer!
Click to expand...
Click to collapse
Why can nobody give me information or is nobody interested in the cell phone?
TaRsY said:
Are you sure? Can you please tell us some details regarding this?
Click to expand...
Click to collapse
Can you even find fastboot roms for this phone? I found a site with the roms, but they're all the recovery roms. I'm thinking of buying the new X50 Pro Player variant, but I don't have a lot of information regarding custom roms for the X50 Pro which isn't a good sign for the X50 Pro Player.
is there anyone who can post me a fastboot rom for rmx 2076 version? thanks
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.