Question Questions before I root with Magisk - Xiaomi Mi 11 Lite 5G

1. Looking at the Magisk guide, It says i need to flash vbmeta. Do I just use the stock version?
2. Do I need to do anything with vendor boot?
3. WIll this work without TWRP, as I am running android 12?
4. Is TWRP stable enough? I know it doesn't support 12, but would it still work?

1. Yes
2. No
3. Don't know, I don't use twrp.
4. Same as 3.

3. Yes, Rooting and Custom Recovery is 2 different situations.
4. Yes, if there's official build for ur device.
And again, pls consider to find out more before what u wanna do before take any further actions, since I think u r not yet clear about what u r doing!

I agree with the above member, please read, research, understand what you're about to attempt and do those again before trying any modifications on your device.

CamoGeko said:
I agree with the above member, please read, research, understand what you're about to attempt and do those again before trying any modifications on your device.
Click to expand...
Click to collapse
Yep, thats why I was asking. I know for a fact that there are people with loads more experience than me, and I don't want to brick my phone when I don't have a fallback.

LinhBT said:
3. Yes, Rooting and Custom Recovery is 2 different situations.
4. Yes, if there's official build for ur device.
And again, pls consider to find out more before what u wanna do before take any further actions, since I think u r not yet clear about what u r doing!
Click to expand...
Click to collapse
So an A11 build will work with A12? I thought there was issues with reading storage.

TheDaysOfYore said:
So an A11 build will work with A12? I thought there was issues with reading storage.
Click to expand...
Click to collapse
Problem with encrypted storage applies only to TWRP on Android 12
But for installing Magisk you don't need TWRP at all. Get informed about patching the boot img from Magisk app and flashing it through Fastboot - you see, there is no word about flashing anything through TWRP, hence no problem with Magisk on A12

zgfg said:
Problem with encrypted storage applies only to TWRP on Android 12
But for installing Magisk you don't need TWRP at all. Get informed about patching the boot img from Magisk app and flashing it through Fastboot - you see, there is no word about flashing anything through TWRP, hence no problem with Magisk on A12
Click to expand...
Click to collapse
I knew that much from reading the Magisk documentation, but thanks for confirming it for me anyhow! I do want to install TWRP aswell, so that was where that came from. I read somewhere that it was why there is no support for flashing to Android 12, so I was just making sure.

TheDaysOfYore said:
So an A11 build will work with A12? I thought there was issues with reading storage.
Click to expand...
Click to collapse
So far as I know, none of current TWRP builds for Renoir ( both official and unofficial ) is supporting A12.

TheDaysOfYore said:
I knew that much from reading the Magisk documentation, but thanks for confirming it for me anyhow! I do want to install TWRP aswell, so that was where that came from. I read somewhere that it was why there is no support for flashing to Android 12, so I was just making sure.
Click to expand...
Click to collapse
You can have a look again here : https://androidfilehost.com/?w=files&flid=318170
It's a collection of almost every Xiaomeme devices' TWRP

TheDaysOfYore said:
I knew that much from reading the Magisk documentation, but thanks for confirming it for me anyhow! I do want to install TWRP aswell, so that was where that came from. I read somewhere that it was why there is no support for flashing to Android 12, so I was just making sure.
Click to expand...
Click to collapse
If TWRP would boot (IDK, I did not want to upgrade to A12), you could then even use TWRP (for flashing something) but instead of putting the zip you want to flash to Internal memory, you would need to put it to OTG USB stick or to the SD card that you insert to the SIM2 slot.
Those storages are not encrypted, hence no problem for TWRP to read them

zgfg said:
If TWRP would boot (IDK, I did not want to upgrade to A12), you could then even use TWRP (for flashing something) but instead of putting the zip you want to flash to Internal memory, you would need to put it to OTG USB stick or to the SD card that you insert to the SIM2 slot.
Those storages are not encrypted, hence no problem for TWRP to read them
Click to expand...
Click to collapse
Huh, nice to know about the external storage. Sucks that I have both sim trays occupied right now, cause booting from an sd card is probably an infinitely better solution for right now.

TheDaysOfYore said:
Huh, nice to know about the external storage. Sucks that I have both sim trays occupied right now, cause booting from an sd card is probably an infinitely better solution for right now.
Click to expand...
Click to collapse
I don't say that you boot from SD card. Just that you copy the zip file you want to flash in TWRP to SD card (or to OTG stick) - then you boot to TWRP, select SD card or mount and select OTG as your storage, then browse to find the zip file there and flash it

So sorry for asking, but am totally new here and I never rooted, customized or unlocked a bootloader of any phone but I've watched videos which I don't find enough explaining. But I totally know what rooting and unlocking bootloaders mean even though I don't understand how it's done practically. So luckily I landed on xda where y'all big brain reside. So am requesting you to open the door for me. My mission is rooting my Nokia x10 and other devices

Visionu said:
So sorry for asking, but am totally new here and I never rooted, customized or unlocked a bootloader of any phone but I've watched videos which I don't find enough explaining. But I totally know what rooting and unlocking bootloaders mean even though I don't understand how it's done practically. So luckily I landed on xda where y'all big brain reside. So am requesting you to open the door for me. My mission is rooting my Nokia x10 and other devices
Click to expand...
Click to collapse
Find the subforum on XDA for your Nokia model and read and ask there. Unlocking BL, issues with TWRP and many other things are specific/different for different vendors, and in some cases even phone models and ROM versions
This is Xiaomi Mi 11 Lite 5G subforum and eg I never had a Nokia phone (wrong: I did have but ages ago when Nokia smartphones had Symbion OS, not Android) hence it would be totally meaningless to advice you anything about Nokia

Thanks for enlightening me, kindly drop me any links for Nokia forums about rooting and bls. Because am really need that knowledge. I can't forget say am totally fresh...... sorry.
Another thing which is not the same topic: if Nokia and everyone told me that my Nokia x10's bootloader can't be unlocked plus the device can't be rooted. Is it all false because there is some company called "MKOPA" this company provides these kind of phones on loan and Incase you run out of credit/payment expires the phone will automatically be locked by mkopa's app which is preinstalled in the device's software on start. Why am saying all of this is because I believe : If some unofficial company can modify the device's default software builds and rebuild it with their billing and auto lock software it means they are eventually able to unlock the bootloader because am sure there is no way they can install custom files if the device can't be unlocked.
Sorry for my poor English,am not good at it. And kindly help me with that info

Visionu said:
Thanks for enlightening me, kindly drop me any links for Nokia forums about rooting and bls. Because am really need that knowledge. I can't forget say am totally fresh...... sorry.
Another thing which is not the same topic: if Nokia and everyone told me that my Nokia x10's bootloader can't be unlocked plus the device can't be rooted. Is it all false because there is some company called "MKOPA" this company provides these kind of phones on loan and Incase you run out of credit/payment expires the phone will automatically be locked by mkopa's app which is preinstalled in the device's software on start. Why am saying all of this is because I believe : If some unofficial company can modify the device's default software builds and rebuild it with their billing and auto lock software it means they are eventually able to unlock the bootloader because am sure there is no way they can install custom files if the device can't be unlocked.
Sorry for my poor English,am not good at it. And kindly help me with that info
Click to expand...
Click to collapse
OMG. What if you google for:
XDA Nokia X10
One of the first hits would be:
Nokia X10 / X20
The Nokia X10 is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm SM4350 Snapdragon 480 5G chipset is paired with 4/6GB of RAM and 64/128GB of storage. The main camera is 48+5+2+2MP and the selfie camera is 8MP. The battery has a 4470mAh capacity. The Nokia X20 is a is a 6.67"...
forum.xda-developers.com
There, one of the first topics/threads on the list is named:
How do I unlock the bootloader for Nokia X10?
Frankly, I didn't read because I'm not interested about.. But it's about your phone, hence read, learn and post your further questions there

zgfg said:
OMG. What if you google for:
XDA Nokia X10
One of the first hits would be:
Nokia X10 / X20
The Nokia X10 is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm SM4350 Snapdragon 480 5G chipset is paired with 4/6GB of RAM and 64/128GB of storage. The main camera is 48+5+2+2MP and the selfie camera is 8MP. The battery has a 4470mAh capacity. The Nokia X20 is a is a 6.67"...
forum.xda-developers.com
There, one of the first topics/threads on the list is named:
How do I unlock the bootloader for Nokia X10?
Frankly, I didn't read because I'm not interested about.. But it's about your phone, hence read, learn and post your further questions there
Click to expand...
Click to collapse
Surprisingly it's helpless. It say "the bl can't be unlocked" which returns to my question

Visionu said:
Surprisingly it's helpless. It say "the bl can't be unlocked" which returns to my question
Click to expand...
Click to collapse
Please, please, please, stop missusing/spamming our Xiaomi subforum with your out-of-topic Nokia. Someone may thing that BL cannot be unlocked on Xiaomi, what's not thuth
Use the Nokia threads for your Nokia comments, questions, etc
If you are newbie to the XDA forum, read the guides how to behave on the forum

zgfg said:
I don't say that you boot from SD card. Just that you copy the zip file you want to flash in TWRP to SD card (or to OTG stick) - then you boot to TWRP, select SD card or mount and select OTG as your storage, then browse to find the zip file there and flash it.
Click to expand...
Click to collapse
Ah, that clears it up a bit more for me. So I can still use it, just not install it. Good to know.

Related

Just ordered Redmi Note 3 Pro - Some questions

Hi,
I'm currently waiting for my Xiaomi device and I have some questions before rooting the phone and doing some other mods.
First of all I'll mention that I've got huge experience in flashing roms, modding etc (just not with Xiaomi), so you don't have to use noob-friendly language.
1)I bought the "Pro" variant, with 16MPx, sdcard expansion and snapdragon 650.
So can I flash any rom that is included in this section: http://forum.xda-developers.com/redmi-note-3/development or is there a difference between Redmi Note 3 Snapdragon & Note 3 Pro?
According to this thread: http://forum.xda-developers.com/redmi-note-3/development/snapdragon-note-ensure-threads-titled-t3351620 it's the same, but I just want to be 100% sure as I just bricked my previous device by flashing a wrong ROM (from other device)
Oh, and I hope the storage option doesn't really matter for ROM flashing, right?
2)I've seen some 2 methods of unlocking bootloader. First one is official, where we sometimes have to wait for some longer time to get the code and the second one is unofficial.
Are there any (dis)advantages using both of the methods, and do I have to use developer ROM to unlock it the official way? Which one is safer?
3)In case my phone would be stuck in a bootloop, can I use MiFlash to repair it?
Do I need to have modified boot.img to do this?
4)Let's assume I have China ROM stable edition. Will I be able to install via update menu the dev version (with locked bootloader) and obtain root by doing this?
5)Can I use FlashFire to flash any zip (of course not a ROM), like some audio mods etc, or am I only allowed to install Xposed with it?
6)Let's say I just flashed a ROM through TWRP but forgot to delete the emmc_appsboot.mbn file. I didn't reboot the phone yet. Will flashing a new ROM (with deleted file), restoring old backup or just deleting the file from system partition (If it exists there) prevent it from bricking?
7)What's with the modified boot.img? I don't quite understand what it's for and when to use it.
Ok, so I think that's all for now. I know these are a lot, but I just want to have some basic information about the phone before I start rooting it.
If you know some good threads that will answer my questions, please post them as an answer.
1.you can't use roms from Redmi Note 3 for Redmi Note 3 PRO;they have differnt CPU;first is equipped with an Mediatek CPU,second one is equipped with an Qualcomm CPU
2.safer method is official method;but why you need this;look around and you will see many people screaming after unlocking BL,installed TWRP,so on and finally BRICK.So my advice:Stay Safe.MIUI OS offers to you all what you needersonalization,good battery life,speed,security.Additionaly unfinished roms and not fully tested software can damage hardware of device
3.you can use MIFlash to repair device,it does exist many guides here or on MIUI Forum
4.yes you can;from China stable----->China developer and from Global stable------>Global developer;this is the order
5.i suppose that ,when you have BL unlocked and root acces,it might be possible
6.i guess not because files chianges occur after OS reboot
7.http://forum.xda-developers.com/showthread.php?t=2587462
1) If you're on the Pro, you're on the Pro. You can only flash for that specific model. The PRO have Snapdragon cpu/gpu, and the non pro version have Mediatek, which make it completely different device. Always be sure that you flash roms that have KENZO in their filename. If you flash ROM made for Mediatek, you'll possibly have a 180 grams brick.
2) I'm still waiting for official unlock code, but after 11 days still haven't got it. Unlocked it by the unofficial way and because I wasn't aware what bastards Xiaomi are, I'v managed to hard brick it so I had to open it and use the two pins for flashing. Please follow the guides in here. The disadvantage of the unofficial way is that EVERY time before you flash new rom, you have to open the archive of the rom, enter the firmware-update folder and delete the emmc_appsboot.mbn. Failing to do that will get you with locked bootloader and the only way to fix the device is by the method I've used (the story above).
3) Better reflash with TWRP. I haven't used any other tool since unlocking the bootloader and flashing the twrp recovery
4) No
5) Yes
6) No. You've already overwritten the mmc_appsboot.mbn the first time. Always check for that file and delete it before flashing. Always.
7) I don't get it also. Some people have problems with wifi without modified boot.img (kernel). Haven't got such problems by now.
ok.
So regarding the point 1. Yes, I know that there's mediatek version also.
But the link I've provided redirects to Note 3 Snapdragon forum.
The thing I wanted to know if there are only 2 types of devices:
a)mediatek, 13mpx, no sdcard,etc
b)snapdragon,16mpx, sdcard
c)snapdragon, 13mpx, no sdcard - it does not exist right?
So for eg. this rom: http://forum.xda-developers.com/redmi-note-3/development/rom-resurrectionremix-v5-6-7-xiaomi-t3365872 is for option b right?
Regarding #2. If I unlock the bootloader official way, do I also have to delete emmc... from the zip before flashing?
#2. Ok, so if I don't get TWRP, how may I backup the whole ROM?
As we know flashing some zip files, or even android itself may not boot after some time. So is there any alternative to TWRP backup (that would copy whole system)?
The snapdragon one is with 16 mpx camera and sd slot (or second sim). It comes in two variants - 2gb ram and 16 gb internal storage or 3gb ram and 32 gb of internal storage. The camera and the cpu are the same in both versions. That's why I've told you to only flash roms that have Kenzo in its name
For non rooted devices,it does exist MI PC Suite for create backup/restore from back-up
Exactly see the fourth question getting different answers.
Too many threads, conflict.... Answers,... ****ty bootloader, my advice if u don't understand things ,don't go 4 unlock.
Dont buy if you not yet ordered
Why not?
I'll receive it on monday probably, so it's too late anyway.
the thing is, that I like modding the phones and unlocking bootloader in Xiaomi will be just a matter of time, that's why I want to learn some basic stuff about this phone.
Because he hadn't read what all the guides say and then end up with hard bricked devices
The phone is a beast.
Yeah, you're probably right. I hope the N3PRO will be at least as good as my z2
Could you tell me one thing. Do I need to delete emmc... file from zip, when I've unlocked the phone official way?
Edit: I think I've got my answer here: http://forum.xda-developers.com/showpost.php?p=66618701&postcount=5
After official unlock, you should be able to do whatever you like. I'm still on the unofficial way, but got unlock permission today. Will let you know what is going on tomorrow (probably, if I have time to reflash).

[GUIDE]How to root Moto G4 (Moto G 2016) the right way or fix a bad attempted root

Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.

Looking for custom rom for Ulefone Armor X Oreo 8.1

I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.

Question Moto G Pure - XT2163-4 vs XT2163-2 - LTE bands

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.

Question [ROM] e/OS

Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Thank you, that's helpful
PsYk0n4uT said:
you have nothing to worry about with the updates if u have a gn2200 atleast as far as i know you should be abe to follow any of the root guides posted here
Click to expand...
Click to collapse
Is this still the case? I read another thread that says this may be the reason it no longer works.
oromis995 said:
Hello, just bought the One Plus Nord N20 unlocked version with the intent of rooting it and installing a ROM. I haven't turned it on because I don't want it to upload the latest security patch and make itself unrootable, so I have nothing to backup. Ideally I would want to install e/OS, but have not rooted nor unlocked the bootloader of a device since 2012, so I essentially know nothing. Can someone please explain if:
- Is this is possible?
- If it is, is it a bad idea?
- Is the GSI for e/OS absent for this phone, and is this an issue?
- Is using a GSI a placeholder until a true custom ROM is made?
- Should I wait until the process is more mature?
- I am told to wait until I know what I am doing. Where should I learn / practice since there is still little documentation for this specific phone?
Thank you for your time!
Oromis995
Click to expand...
Click to collapse
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
mobile_sensei said:
If you think you don't need a backup because "you've not turned your phone on yet", you should probably think twice about trying to flash custom software. Especially GSI...
Just trying to save you some heart ache down the road. Cheers
Click to expand...
Click to collapse
I meant data. I know that I need the partitions
oromis995 said:
Is this still the case? I read another thread that says this may be the reason it no longer works.
Click to expand...
Click to collapse
if you decide to use the security patch it came with stock then be sure not to connect tp the internet at all because once its unlocked and rooted and downloads an update dsu sideloader will not work until that update is dealt with and system updates wont work while bootloader unlocked and definitely not going to work if any partitions are modified(not stock such as magisk patched boot image). im not sure about the september update but some did have issues with the august patch although others were successful so it may have just been user error. my suggestion is to just put dsu sideloader and a prerooted gsi on an sdcard or transfer via pc/usb cord to internal storage but don't connect to the internet and use that to gain root long enough to pull your full stock partitions backups. this would be playing it safe. then ifnyou want you can relock your bootloader and update to september/newest and pull another full backup so you have it in the case that ypur successful and if not then your bases are covered to downgrade and downgrading will be as easy as simply reflashing all the stock images you pulled the first time though you shouldnt have to reflash ALL of them but in case you want to / need to then u have them. I cant stress backups enough. I use Partitions Backup & Restore by Wanam from playstore or wherever u want to download it unless u prefer to dd everything but i like the gui its just easier. read my post on how to root any n20 as there are somegood tips there and a great response detailing the procedure and dmtec also posted a much more detailed guide. i still havr a device on May patch and the other on July

Categories

Resources