Hello,
I fixed my previous issue that caused my phone to unfortunately not boot after Magisk patching kernel instead of ramdisk, but now my problem is a lot weirder and seems even more complex.
I wanted to patch YouTube with Lucky Patcher once again as the patch seemed to be not working now. After the patch has been applied, a communicate was shown saying that it couldn't make some file because blah blah and that firmware got messed up. I didn't care much, but then I wanted to uninstall YouTube's updates and it hung, YT was unavailable and Play Store was showing that it is still uninstalling, so I wanted to reboot. After that my phone started to bootloop. Flashed system.img and ramdisk.img again via fastboot, but didn't fix the issue. Tried using HwOTA to reinstall the whole system and then the party has started. Download recovery showed that it couldn't install the package. I couldn't reboot anyway nor enter eRecovery, so I forced reboot. Since then I can only enter recovery, broken eRecovery and fastboot. Trying to boot system just brings that broken eRecovery too.
Any way to fix that, or am I forced to install stock ROM, lock the bootloader and try sending phone on warranty (if possible, either way to the service)?
I am so pissed off that I'll probably sell the phone if servicing is needed and buy Xiaomi Redmi Note 5 Pro.
Thank you in advance.
SevenUp9 said:
Hello,
I fixed my previous issue that caused my phone to unfortunately not boot after Magisk patching kernel instead of ramdisk, but now my problem is a lot weirder and seems even more complex.
I wanted to patch YouTube with Lucky Patcher once again as the patch seemed to be not working now.
Click to expand...
Click to collapse
Why patch youtube app? To make it adfree?
Fyi, there's this mod app called Youtube Vanced that has black/dark mode and adfree which is awesome.
Edit: you can also install Youtube Vanced along side with the original playstore downloaded youtube.
Well, just to make it black and available to play in the background.
I know there is YouTube Vanced, I used that before, but just for some reason wanted to have original YT app. Not important. Just my weirdness Next time I'll just install Vanced, less problems.
But the thing that simple patching could brick my device... Oh boy. This is really strange.
oh, the irony of your bad luck with lucky patcher
i feel no pain for anyone stealing apps. amazing that the same person stealing apps bricks his phone in the process, and rather than spend time fixing it wants huawei to just replace it.
guys like you are driving up the cost of these devices.
guys like you are also responsible for huawei feeling the need to lock down bootloaders.
WaxysDargle said:
oh, the irony of your bad luck with lucky patcher
i feel no pain for anyone stealing apps. amazing that the same person stealing apps bricks his phone in the process, and rather than spend time fixing it wants huawei to just replace it.
Click to expand...
Click to collapse
No stealing. Simple mod to make YT dark-themed and play in the background, that's all. Believe me or not, some of the songs I listen to on YouTube are not available on Spotify or SoundCloud, and Lucky Patcher had its beggining here, on XDA, right? Same applies to YT Vanced. No need to be pissed.
Huawei may not directly be responsible for the issue, but the fact they are shutting down the bootloader unlocking site, they want to kill modders and that's partially why I don't know how to recover. Modding scene for this phone is growing poorly. Only one custom kernel available that is not bugless... And a few ROMs, mainly because of Treble.
If it's irrecoverable, okay, I'll pay for a repair then, but after that I won't be willing to support Huawei anymore. I expected more care for their more advanced, geeky users...
And no, I want to recover it alone, but I am tired already cause this phone has already caused me problems for over 20 hours (8h debranding and installing Oreo, 12h debricking after Magisk patched kernel instead of ramdisk, and some time for kernel testing, fixing, Magisk stuff). I am just tired and have no idea what to do. And if I wanted to just go for an easy way and send on warranty/to repair, I would do it instead of creating this topic... Repair in a service is mentioned here in case it's irrecoverable. Clear enough.
SevenUp9 said:
No stealing. Simple mod to make YT dark-themed and play in the background, that's all. Believe me or not, some of the songs I listen to on YouTube are not available on Spotify or SoundCloud, and Lucky Patcher had its beggining here, on XDA, right? Same applies to YT Vanced. No need to be pissed.
Huawei may not directly be responsible for the issue, but the fact they are shutting down the bootloader unlocking site, they want to kill modders and that's partially why I don't know how to recover. Modding scene for this phone is growing poorly. Only one custom kernel available that is not bugless... And a few ROMs, mainly because of Treble.
If it's irrecoverable, okay, I'll pay for a repair then, but after that I won't be willing to support Huawei anymore. I expected more care for their more advanced, geeky users...
And no, I want to recover it alone, but I am tired already cause this phone has already caused me problems for over 20 hours (8h debranding and installing Oreo, 12h debricking after Magisk patched kernel instead of ramdisk, and some time for kernel testing, fixing, Magisk stuff). I am just tired and have no idea what to do. And if I wanted to just go for an easy way and send on warranty/to repair, I would do it instead of creating this topic... Repair in a service is mentioned here in case it's irrecoverable. Clear enough.
Click to expand...
Click to collapse
background play is a paid service on youtube. you're stealing.
if you can get to recovery or fastboot, it's not irrecoverable.
you should really consider sticking with stock from now on. no one should feel sorry for you because you bricked your phone and had to work to fix it.
Do I convince anybody to feel sorry that I bricked my device? No.
Do I feel irresponsible for bricking it by my own? No.
Do I reccommend stealing? No.
I just have no money on my own, also previously there was no background play option on YT. Okay, maybe I wanted to crack, but it should be in my bussiness. Thousands of other people do the same, even here.
And yeah, I know it should be recoverable because I can boot into TWRP and fastboot, question is how, because I am already out of my mind. I'm not saying that I am tired to make others feel sorry for me but just to inform I can't handle this on my own atm and need some help.
I am on stock, that is right, not yet needed to flash customs imo as the phone runs just good.
Let's not offtop any longer. I just want to get some possible solutions. Right now I am going to flash all the system files via fastboot or TWRP once again. The problem is that I can't flash anything eRecovery-related.
OK, actually eRecovery and everything related to it such as dload, low-level reset etc. is broken. Even stock recovery, I can't even shutdown or reboot system. It is probably something deeper in whole framework, device is simply not available of doing simple tasks using its own functions. I am afraid it's not what I am able to fix. It's the first time when I have such problem.
I'm going on holiday on Sunday not bringing my PC with me, so I won't be capable of fixing it for around 1,5-2 weeks. But if anyone's got any idea, I am here to listen.
If it is more complex than a fellow mobile user can fix, I'll just leave it for specialists in a service to fix the issue. I hope it's recoverable with any tool just flashing firmware, either way my wallet will be hurt so much, I suppose.
Wait what? Now all the time my phone boots into TWRP from HwOTA, even if I flashed CATUVA21's version.
I mean... Booting after I just power it on, it just boots HwOTA's TWRP like it was eRecovery...
did u flashed the images that is same with your version?
or did u tried flashing kernel before flashing system img?
I had a similar problem when i used HwOTA, remember that HwOTA8 is when you got oreo and HwOTA7 is for nougat. Using the wrong one will boot to twrp if i remember correctly.
summerblaze said:
did u flashed the images that is same with your version?
or did u tried flashing kernel before flashing system img?
Click to expand...
Click to collapse
Yeah, I did both.
Anyway, phone's back from repair shop, quite disappointed that they've charged me for $80 when I could do it for $20 using the same tool they did (DC Phoenix), but whatever. Lesson for me - never ever overuse Lucky Patcher and don't believe that repair shop might be cheap. Also never buy Huawei anymore as it is extremely painful to recover it for nerves and for wallet. I'll be more careful now with this phone, still thinking about selling it and buying Xiaomi Redmi Note 5 or Mi8 because there's a good offer where I can get that phone for ~$380.
I'm going to do last mod to this phone - reflashing OS. The OS I got after the phone's been repaired looks a bit sketchy, because OS version is System 8.0.0.046(07P2) instead of RNE-L21 8.0.0.xxx(C432). Firmware Finder sees no updates for that so I expect OTA isn't working as well. Hope it doesn't get bricked again... Wish me luck.
petanque said:
I had a similar problem when i used HwOTA, remember that HwOTA8 is when you got oreo and HwOTA7 is for nougat. Using the wrong one will boot to twrp if i remember correctly.
Click to expand...
Click to collapse
Yeah I know. I used proper version (HwOTA8), but it flashed TWRP in eRecovery partition which made the phone complete brick because no dload mode. Hope that it doesn't make such mistake now as I'm going to install proper Oreo for EU locale.
Nah. I'll have to beg for a free (or cheap) repair once again because this piece of crap got bricked again. Thank you Huawei for providing so much pain while flashing your devices.
Whatever, a few days ago I realized the issue was way simplier than I expected. Just flashed oeminfo from HwOTA7 instead of 8, as the one in 8 seems broken and the device won't boot up. $80 repair wasn't worth it... Damn.
Related
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening
The Sony Xperia Z2 tablet has got to be the most horrible device in android history to root or install a recovery on it. The process and the complexity of it is just horrible. You daren't ever make the slightest change to a rom or anything in twrp as it just screws everything up on this device. I can't count the amount of roms i've put on it just to totally trash the device and you have to start from scratch. Either you put a new rom on, it wipes the recovery, you have to piss about using flashtool to flash some other ftf on just to get into recovery, then you have to then flash another tft to get root, the list just goes on and on. I don't even know why sony mobile even bother offering the bootloader unlock option in the first place, it's an absolute nightmare. It's basically you can have root with the official stock firmware, if you want a custom rom spend the next 2 weeks trying to get supersu installed on it. The most horrible device I've ever come across.
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
BabelHuber said:
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
Click to expand...
Click to collapse
I've tried Carbon and would love to use it but it just screws up the tablet after install and recovery gets wiped so you can't even go back to restore a back up. You then have to reflash using Emma then back into flashtool to reflash the tft to get recovery to work again because flashtool ends up reporting back that the current tft is not compatible with the device. It's a finicky device to root. It's got to be the worst out of all android devices. E.g my Samsung s9 had it rooted and flashed with a custom rom in around 5 mins. No matter what firmware is installed. Sony decided that after 23.1.A.575 or whatever rooting was not possible after that. Also every method on here telling you how to do it is different to each other and inconsistant. I tried 23.1.A.575 root for UK and it would not allow for twrp to be booted into. I had to use xperiafirm to download the Taiwanese version so I could get the batch script to allow recovery so holding down power on volume down would allow twrp to load. It's just a painstakingly horrible device to root to get something so simple. But yes your right probably best time to get rid and something different. Sorry for the rant it's just been a frustration for me.
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
BabelHuber said:
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
Click to expand...
Click to collapse
I've followed so many without much success. I tried the solution by kulvertti to the letter and the tab was having non of it. I think the problem also is that a lot of the links are dead to the specific tft you need to download so getting the exact version is tricky. The only one that has worked for me is the Taiwanese rom then using the recovery script by danalec to get Marshmallow flashed which is what I'm running now. So I made a back up today and thought OK let me try carbon because I can get all the nice customization options like being able to choose a dark theme for the settings menu instead of piercing white. What is it with manufacturers wanna make every thing bright and painful on the eyes. Anyway downloaded gaps wiped system etc installed rom and once it loaded the system was all unstable and lost root and recovery. So I give up now and have to accept I can only have marshmallow on it.
Danalec has a very simple root method for Marshmallow in the general section. This is one of the best tablets out there by far. Build quality doesn't come close with other brands.
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
I think root is possible, but until now I have not been able to find out exactly whether the Fastboot is locked or not. it is my first OPPO and so I have no experience with OPPO. even if it's BBK. it's not an OP 8. We can only hope that someone might want to open it here. But from the root on youtube and other websites I would be careful. I also couldn't find any firmware for the flash via MSM tool or download tool ... so at the moment with an unbrick it is not possible to restore it.
__NBH__ said:
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
Click to expand...
Click to collapse
Factory reset should revert if the apps dont have revert option.
I'd like to see them show rooting an X2 Pro, rather than an A5s (CPH1909)
ordered one anyway... first phone without root in 11 years.. i hope i made the right decision.
It depends what you root for I guess. For me I currently root for adaway, viper, substratum themes and to change my font plus I recently run a module for various tweaks.
I used viper for my old wireless earbuds, I recently got new ones which sounds great without viper. Lots of apps now have a dark mode and I hear this phone has a beta mode that can turn other apps dark. Not changing font I can live with and the tweaks module is fun but not essential. Adaway I will miss. But for the first time in a while I'm not so fussed about root. I understand some people like it because you can flash ROMs when the device gets older. I survived for 18 months with a Samsung S8 plus without root so I know I can do it!
I need to decide whether to pre order the phone today or I miss out on the pre order bonus, I like it but don't think I can trade in my 7 pro, I love it a bit too much.
First and foremost adblock though you can do that without root. Second Sony Music magisk module for Android Auto. Third to debloat. 4th for some advanced Tasker tasks. I'm pretty sure I can get workarounds for most
Sage said:
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Click to expand...
Click to collapse
I don't see how this can be legit. The video shows a different device and also the rooting tool is for mediatek based devices. The Oppo find x2 pro is based on Qualcomm chipset.
Can anyone confirm if VMOS work this phone? It may be the only way to use root.
Never heard of vmos sounds interesting!
Yeah VMOS is like running VMware or Parellel on Mac. It's easier than rooting an actual android device, but it also gives more battery drain and less intuitive. I have it on my Mate 20 pro, does anyone know if it works on find x2 pro?
Videos been removed. I really wish this phone had working twrp and magisk it'd be literally the ideal phone
I'm just waiting for a oneplus phone with a periscope camera, that will be the one to get as it will be like this phone but with working root.
Yeah miss root. First phone in a decade I have bought without it. Though mostly I use it for adblock though private DNS works very well
Really missing root on this phone. I wish it were available considering the Snapdragon processor
EE
So far, i have been able to Enable USB Debugging and OEM Unlocking, this on the EE Network. Seems there is no TWRP Build Avail for the X2 Pro Yet. And i am unaware of any other way of Flashing the Magisk Zip Safely any other way.
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
bhomie28 said:
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
Click to expand...
Click to collapse
How did you manage to Patch the Boot IMG?
Thanks Man!
I download the OTA ozip file from oppo. Decrypted the ozip, extracted the boot image & patch it with magisk manager:laugh:
Easy going but how I can flash the file:crying:
I wonder if we can get a GSI working! Anyone wanna try?
I'd love that. But I'm not seeing much love for many Moto phones. Mostly because those that get Moto are happy with what they get. And most devs don't bother with budget Moto.
Even with my limited time, I was considering to see if I could learn how to build port for a ROM. But without a recovery I thought it be best to flash stock, root and try to costumize it. Replace the apps I don't want with alternative. I already use Samsungs Internet in as Chrome replacement. Tho I do have a full set of browsers depending on what I'm gonna do.
That said, I did look into a TWRP.
Okay, so, our Moto G Play (2021) has same chip as the G10, E7 Plus and Lenovo K12 although with 1GB less RAM and half the storage. E7 Plus has no TWRP or ROMs yet, nor the G10, naturally, since it just released. The K12 however, supposedly have a working unofficial TWRP. But since I've only come across it on a handful of sites I have not experience with.
IS unofficialtwrp(dot)com legit? Cause there's a guide there for the Lenovo K12 that has the files for it. I mean, I have multiple devices that run with "unofficial" TWRP, but since I got them here, I always though it was some local dev that made it and share it. Never thought there was a website that was grouping them all. If it was here, I'd had no doubts. But here, the K12 hasn't even pop up.
I have consider trying it out. But flashing has because such a hassle with some phones not in the mood for trail and error 10 times. Between verity, stabs, vbmeta and where what flashes. My previous device was a V40 that not one single method worked for fully setting up the phone without breaking something. Had to mix and match like 3 guides. I don't know, maybe my device had issues. I'm grateful for 9008 + QFIL and its partition manager.
Thinking of first trying to replace my V40 battery. (Bloated so bad 3 sides are already separated of the back cover) And if all goes well star using the G Play as guinie pig.
I could try, if you could send the link
Omizuke said:
I'd love that. But I'm not seeing much love for many Moto phones. Mostly because those that get Moto are happy with what they get. And most devs don't bother with budget Moto.
Even with my limited time, I was considering to see if I could learn how to build port for a ROM. But without a recovery I thought it be best to flash stock, root and try to costumize it. Replace the apps I don't want with alternative. I already use Samsungs Internet in as Chrome replacement. Tho I do have a full set of browsers depending on what I'm gonna do.
That said, I did look into a TWRP.
Okay, so, our Moto G Play (2021) has same chip as the G10, E7 Plus and Lenovo K12 although with 1GB less RAM and half the storage. E7 Plus has no TWRP or ROMs yet, nor the G10, naturally, since it just released. The K12 however, supposedly have a working unofficial TWRP. But since I've only come across it on a handful of sites I have not experience with.
IS unofficialtwrp(dot)com legit? Cause there's a guide there for the Lenovo K12 that has the files for it. I mean, I have multiple devices that run with "unofficial" TWRP, but since I got them here, I always though it was some local dev that made it and share it. Never thought there was a website that was grouping them all. If it was here, I'd had no doubts. But here, the K12 hasn't even pop up.
I have consider trying it out. But flashing has because such a hassle with some phones not in the mood for trail and error 10 times. Between verity, stabs, vbmeta and where what flashes. My previous device was a V40 that not one single method worked for fully setting up the phone without breaking something. Had to mix and match like 3 guides. I don't know, maybe my device had issues. I'm grateful for 9008 + QFIL and its partition manager.
Thinking of first trying to replace my V40 battery. (Bloated so bad 3 sides are already separated of the back cover) And if all goes well star using the G Play as guinie pig.
Click to expand...
Click to collapse
I tried it booting wise and tried to backup booting itself worked perfectly but I wasn't able to properly test backup and restore because I didn't have enough storage...
I've been trying. I did see a thread about repacking due to storage space necessary for unlocking rw on the system partition. Whcih GSI were you able to boot?
stoag said:
I've been trying. I did see a thread about repacking due to storage space necessary for unlocking rw on the system partition. Whcih GSI were you able to boot?
Click to expand...
Click to collapse
Late and not OP, but I was able to get phhusson's ROM booted with gapps. The secure version does not work, I guess because it uses vndklite and I have not taken steps to unlock r/w.
Update: I got the secure version working! I Needed to flash vbmeta.img
I followed these instructions... https://forum.xda-developers.com/t/guide-phh-gsi-flash-aosp-12.4328891/
New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.