What is the In-Depth Test APK? - OPPO A72 Questions & Answers

This seems to be used for unlocking the bootloader on ColorOS sometimes. I have found a few APKs but I don't want to use them on my phone before understanding what exactly they do and where they come from.
It seems that there is a queue or verification-like system to them. If so, has anyone tried reverse engineering them to skip that process?

Related

SHARP INFOBAR C01: Rooting, Unlocking, Installing ROMs

I need some help with this, and seeing that people have worked on the Infobar A01/02 I would assume there's people here who can tackle this. I have no idea how you would go about Rooting or Unlocking a SHARP device, let alone a Japanese one and I don't see the C01 listed anywhere.
I'd also like to know how I would go about installing a ROM alongside the default one on here.
Sokky said:
I need some help with this, and seeing that people have worked on the Infobar A01/02 I would assume there's people here who can tackle this. I have no idea how you would go about Rooting or Unlocking a SHARP device, let alone a Japanese one and I don't see the C01 listed anywhere.
I'd also like to know how I would go about installing a ROM alongside the default one on here.
Click to expand...
Click to collapse
Anyone at all? The least I'd need to know is how to boot into recovery mode. I found one site that talks about the power and volume buttons at startup but nothing happens. I've gotten into recovery with a G1 but that's about it. Do I have to like inject my own recovery bootloader or something?
Bumping, still no luck on finding a GingerBread 2.3.4 rooting option.
I'm trying to inject su and Superuser manually but I can't mount with the recovery menu, so I'm trying to install CWM but I need root to do that, but that gives me root to give myself root. l:L
I'm in a vicious cycle, pls send hepl im dyign
What's a universal root method for GingerBread 2.3.4?
Just found out you can't get a universal root for 2.3.4 and that you have to have a custom method. Ho how would you go about making a root method at all?
I also think that the phone has a locked bootloader which would explain why I can't access the recovery menu options. I feel a bit silly, I suppose that's a large reason why some of this stuff isn't working at all. If anyone knows some Infobar bootloader stuff just feel free to post.
I just found a thread about someone else trying to figure out all of the things I'm trying to figure out only it's not on an Infobar but another Sharp device on KDDI. I think they eventually found someone else had made a root, but I kinda didn't read the entire thread. Still wondering if anyone has already got a solution.
Much the same
I have a c01 here in the UK, still wearing factory stickers. A very poor buy, considering I can't make a call with it. I have looked high and low but can't get anywhere with it. Sharp/kddi/AU I have asked them all. No can do. Although I read a Canadian chap had his unlocked by them, they simply won't at any cost.
I can't even get a phone shop to look at it.
To be honest, I know about as much as my gran about mobiles. I'm a quick study, but would rather pay, if there was somebody to pay.
Any positive direction would be much appreciated. Best advice so far is to bin it and try to forget.

[Q] How to root my E5803?

i've tried using alot of method, but still, i can't understand how to do it, it's not that simple. can anyone tell my in the simpliest way? or maybe someone has the prerooted rom to flash. thanks
You've said it yourself, it's not that simple. The concept itself is actually simple, we want root that we can "undo", so we need to backup the DRM keys before we unlock the bootloader and patch the kernel to gain root access. The execution however is complicated mostly because of the DRM backup part.
You mentioned that you've tried multiple times, what have you actually done so far?
Honestly though, the rooting guides that can be found on this forum are all quite detailed, if you can't even follow those instructions that are already simple and clear, I think it's better for you not to have root at all.
I say this because having root privilege without knowing what you're doing and unable to follow directions can really mess up your phone, and usually not easily recoverable. In the likely event that you failed to do whatever it is you want to do with your root access, you will probably need to employ even more complicated procedures to fix it, which I am guessing would be too much for you to handle. Proceed with caution my friend.
I was rooting a new Z5C yesterday and decided to document the process for reference and ended up making a new guide, hope this helps you.
https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388

Problems understanding how to Root

Maybe the problem is that I don't know how to properly ask for what I want/need. First off, I am new, so let's pretend I know nothing about modding phones. Second, what I am trying to achieve is the following:
Marshmallow OS or newer (I have lollipop and I highly dislike it)
Complete removal of all AT&T software/bloatware from my M8
Ability to try out different ROMs (are those the same thing as operating systems?) like cyanogenmod.
Those are the highlights to my endgame.
I have found there are several steps to this, and it seems like each step has at least one prerequisite or sub-step and I get overwhelmed when reading up on how to achieve the above goals. Feels like I'm doing taxes for a poorly run business. Apparently I need TWRP on my phone. No clue why or what it does. In order to install it, I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful. Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray. Anywhere I have read up on this, when it says download/install _______, I cannot determine whether that means download/install on my PC, or on my phone, bc it doesn't specifically say what goes where in every instance. To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it. I asked once for a step by step tutorial or a link to one, and I was given something that was just as confusing as what I have already found. These tutorials seem to be written for ppl who know a lot by ppl who know a lot. I am not one of those ppl. I am a green noob, still wet behind the ears. I apologize in advance for not knowing, but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed. Would greatly help me if I had a list of ingredients needed before I begin, and a sequence, much like a recipe for a cake. Again, I apologize for not knowing, and I'm sure all of you reading this were, at one point, uneducated on the matter. Thank you for any advice and/or reading my TL/DR post.
See my responses below, in red font:
Damagj said:
Apparently I need TWRP on my phone. No clue why or what it does. In order to install it,
TWRP is a custom recovery, and what that is, is explained in "that" thread I linked you to: https://forum.xda-developers.com/showthread.php?t=2744194
Think of TWRP as a kind of small installer program and backup/recovery tool. You need it to flash custom ROMs, and you can also use it to backup the current ROM. It's not used within the Android OS, but rather you can boot into it separately. Which is obviously handy, if for whatever reason you can't boot to Android OS, and need to "recover" (restore the OS).
I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful.
Don't go by the install instructions on the TWRP website, they are not device specific (to the M8) and may misguide you (every Android device has it's own nuances).
To install TWRP, you need to unlock the bootloader. The bootloader is "locked" by default, which by definition means you cannot install a custom recovery. The following is a good step-by-step guide to unlock the bootloader and install custom recovery. Note, that you do not need to root, in order to install TWRP, or flash a custom ROM. So stop before you get to the step of root (flash SuperSU). Also, the version of TWRP you install should be current (3.1) or alternately 2.8.7 (which is a known "old reliable) version).
https://forum.xda-developers.com/showthread.php?t=2799796
Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray.
No, you actually can't. Your fear of bricking the phone (permanent damage) is unfounded. As with s-on, this phone is nearly impossible to brick. The phone is fully recoverable even if you screw up; since for what you describe, you are only touching a limited number of partitions (system which is the OS, and recovery). As long as you don't mess with "critical" partitions like hboot and radio, you can't actually brick this phone. And those partitions are actually protected, and you can't modify them even if you wanted, unless you s-off. So all the more reason to stay s-on, as I described in the other thread you posted in here: https://forum.xda-developers.com/showpost.php?p=74107487&postcount=100
To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it.
but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed.
That part is difficult. While possible, doing what you describe is somewhat risky with no other device for internet. At some point, it's almost inevitable for anyone tinkering these phones, that something will go wrong. Either you forget a step, or you can't boot for no mistake of your own, at all. Even having done this stuff for years, it still happens to be, once in a while. It just happens. So without a way to ask for help, or download files, you can get stuck in a bad jam. You'll need to have some backup plan, even if it's a friend or family, letting you use their computer as a last resort.
Click to expand...
Click to collapse
Stick with it. Keep reading up, and trying to learn the basic terms, concepts, tools, and methods. I know it seems overwhelming, but it will all start to make sense. You really can't (and shouldn't) try doing these things, until you have some basic understanding. You wouldn't ask someone to tell you how to tear the engine out of a car, without knowing how any tools work, or what any of the parts of the car are called.
I would also suggest you refer to my (AT&T M8) index thread. It has a lot of links and basic info, you may find useful: https://forum.xda-developers.com/showthread.php?t=2751432

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.

Usage of Samsung Galaxy Tab without Android, without modification of the bootloader

Hello out there,
it might be an easy question for some of you, so please be so kind and help me out: I highly appreciate your answers.
--
The Samsung Bootloader, which can't be changed due to the burning of the eFuse (yet I do not understand, why one can't use the same method of digitally signing an own bootloader and load it onto the flash without burning the eFuse) boots from a certain file on the flash, which should be Linux-Standard /boot/vmlinuz.
Why can't one backup the whole flash with Samsung Tools and install an own Linux System to boot from?
I now know that the kernel protection is based on a google development, where several virtual machines are loaded and one of those is then the Android System and Kernel, with a Platform where the Apps can be started from (Dalvik) and this virtual machine can be checked for manipulations - so to speak: Software protection = of no use for me or my choice to implement or program my own version of such a protection, but it has nothing to do with a hardware based (knox) protection. Is this correct?
(I do not want to blow the fuse, but use a custom rom. Any solution for this?)
--
I could analyse the open source code of Android and maybe able to initialize an update process, which might replace the whole file system, but doing so might be a bit dangerous if you don't know what you're doing.
Thanks for answering.
TheLazyGuyDE
TheLazyGuyDE said:
(...)
(I do not want to blow the fuse, but use a custom rom. Any solution for this?)
(...)
Click to expand...
Click to collapse
You have already received an answer in your previous threads.
So I don't understand why you keep asking the same thing.
Let me specify my question:
I asked the question in relation to a customization of the bootloader, but I didn't ask it in relation to probably existing Tools, maybe from Samsung (I don't know), which might backup the flash and may be able to put something onto the flash or is this not possible? Why should I change the bootloader (and blow the fuse) if I have all the functionality I need already on the phone? - That's the question.
I've heared something about "download mode" where you can communicate with the smartphone and I've watched a custom rom installation.
I think the installed bootloader is able to backup and restore. But will installation of a custom rom do anything that isn't reversible (like blowing the fuse)?
Or is it fully reversible if I some day re-install the backup I made prior to installing the custom rom?
Is it possible to directly mount the flash under Linux?
Is the bootloader itself directly in the knox-chip? How should the chip otherwise recognise that the bootloader changed?
(a brief overview would be nice)
As you can see: I am very careful and I don't want to do anything wrong, which I'd definitely repent later on. "Just go ahead" without careful planning is not my style. That's the reason why I want to know everything before I start.
I appreciate every answer.

Categories

Resources