Database Info

Converting Verizon Pixel to Google Store Version

I recently bought a verizon Pixel and have already unlocked the bootloader and flashed a stock image NDE63V that comes directly from google. I'm using it on T-Mobile. If I relock the bootloader at this point will everything be ok? I've read something about people saying it would brick the phone if you relock after flashing unsigned code, but the official stock images from google are signed. Will I get official updates for the unlocked google store version of the Pixel?
-edit- I decided to live dangerously, re-locked the bootloader, and now I have a completely stock google store pixel

My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app

brainymd said:
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't think anyone knows. Right now I flashed stock google ROM through fastboot which replaced bootloader image, I am using it with T-Mobile, and I relocked bootloader. I'm going to assume it would get stock google updates.

I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.

mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
I also have a Verizon version. Is there an advantage to flashing the Google version of updates as opposed to Verizon? For the moment I have an unlocked bootloader with TWRP and SuperSU installed. I tried installing an OTA update and it failed.
If I want to install one of the image updates posted (such as NDE63X from Verizon available right now) do I need to run the "flash-all" script? Could I just flash system or something else? Or should I expect it to overwrite my custom recovery and I'll have to restore that?

As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.

mruno said:
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
Click to expand...
Click to collapse
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.

mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.

ohioDroid said:
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
Click to expand...
Click to collapse
If the gestures were not in that update, they should be soon in an upcoming OTA according to reports. I am currently using the double-tap gesture with the ElementalX kernel (enabled within its app).
Edit: I think this app can enable lift to wake. I bookmarked it after finding a post about it here until I read Google will be adding this feature soon.
fink.nottle said:
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
Click to expand...
Click to collapse
I am not sure as I haven't had a nexus device since the Samsung Galaxy Nexus on Verizon .

On a lot of their devices Verizon likes to update bootloaders to only accept new updates. It's likely that if they patch out the ability to use dePixel8 in a future update, they will prevent people from flashing older builds. C'Est la Vie I guess

Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?

Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?

aholeinthewor1d said:
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Click to expand...
Click to collapse
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
tobalaz said:
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
Click to expand...
Click to collapse
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.

jmartin72 said:
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
Click to expand...
Click to collapse
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc

aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I bought my Verizon Pixel yesterday. Unlocked in 20 seconds and within a few minutes TWRP 3.0.2-0 for sailfish is installed and SuperSU 2.78-SR5 has been flashed. Works perfect.

aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I feel your pain! I'm also coming from the S5 for 2.5 years. Had everything (almost) perfect with systemless root, twrp, xposed, adaway, etc. (but no Android Pay) . Now with this Pixel and Verizon-depixel8 unlocked bootloader, I'm trying to piece together the best plan for having the most stuff working.
So far, bootloader unlocked, and I flashed the full 7.1.1 images from Google. Then I tried using the setup wizard and it brought over my account info and wifi passwords and such from my S5 by directly connecting the phones, and it downloaded my apps from google play, but I need app-data.
So, now I'm thinking this would be the process if you want to have a rooted pixel, and be able to reboot into a "clean" boot for Android Pay?:
1) boot TWRP alpha2 (since RC1 having problem rooting?)
2) install TWRP alpha2 zip
3) install stock-safetynet kernal to boot_a
4) boot into boot_a
5) setup Android pay, add credit cards, etc.
6) boot into TWRP and install root with SR5 to boot_b
7) boot into boot_b and restore other app backups with Titanium Backup, install Adaway/hosts
8) no Xprivacy /Xposed available yet, right?
9) restore backed up apps from old phone with Titanium Backup (from cloud, etc.)

I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app

bobhinkle said:
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you can still use it on Verizon. Advanced Calling is a feature i am not too familiar with. Is that HD Calling? If so then yes that will work as well works on my phone without issue.

So from here I can flash Google's bootloader and Google image and then when updates come out just use the Google ones
Sent from my Pixel using XDA-Developers mobile app

Question for those with a Play store version of the Pixel: what is your bootloader version on the 7.1.1 software?
For reference my Verizon store Pixel has BL version 8996-12001-1610061102.
Thanks in advance!

DON'T upgrade to Nougat by OTA!

This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...

I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?

xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.

xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...

those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc

enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.

hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...

aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards

iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.

Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?

How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?

yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).

I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.

I found a simple fix, get Titanium Backup and freeze that crap app, done.

yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...

saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.

True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?

sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.

rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux

rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it

Huawei wants to stop users from rooting?

A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.

Pomaraczowy said:
A tweet from John Wu a person who created Magisk:
"I am informed that a new Huawei OTA will make installing Magisk unable to boot at all. At this point I might just simply ignore this brand even exists."
First they stopped providing us codes for unlocking bootloader and now we won't be able to root our phones?
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Sent from my Honor 9 using XDA Labs

hujialun2002 said:
Already in AL varient.Won't boot after magisk installation.As for now we can flash custom roms but I read that Honor is going to remove FRP lock switch,which will make you unable to flash at all.To be honest this brand is nothing but rubbish in terms of Android tweaking etc.
Click to expand...
Click to collapse
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?

Pomaraczowy said:
So what now? Even if we're going to get Android Pie update, we can't install it cause it would turn our phones into useless Chinese spying bricks?
Click to expand...
Click to collapse
We have already had a taste of Pie now,so for anyone who dont care EMUI 9 they can simply do with Treble Pie GSIs.Who cares about the ugly UI of Huawei?PE 9.0 and OpenKirin Pie AOSP are both doing quite great.
Sent from my Honor 9 using XDA Labs

Pomaraczowy said:
Is root necessary for flashing custom ROMs on our device? As I remember I only needed to unlock bootloader to do that on a Samsung phone.
Click to expand...
Click to collapse
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?

streetu said:
No, you don't need to have root to flash custom. But you have to have access to PC to flash it through fastboot
And i prommised to myself after that, that this was my lasy Huawei device. I paid for device that can be unlocked and rooted and now thay are taking this back from me. I wonder is it legal? Maybe we could give phones back now?
Click to expand...
Click to collapse
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0

Pomaraczowy said:
So can I update safely with OTA if somehow we get 9.0 update and then just flash recovery image through CMD and then flash custom ROM?
I kinda don't want to do it now cause it's a pretty new phone and still there's a chance that I'm gonna brick it but I really want that 9.0
Click to expand...
Click to collapse
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.

streetu said:
IF huawei wouldn't lock anything else - yes. But on Huawei you flash ROM directly through fastboot (since all custom roms are treble ones), not in recovery.
However i wouldn't wait, because maybe next OTA will lock something else. and you will be forced to use EMUI.
Click to expand...
Click to collapse
Probably gonna do it soon.
Thanks for help.

For now, I'm up to B372, and still able to do whatever I want, fyi.

Keep on updating... and supporting the Apple wannabees of the Android world. They learned and stole the ideas they wanted from the community and now will completely lock out the devices, bootloaders, root methods, anti-rollback measures, etc.
Oh, and as for that "spying" part? Just search for "Huawei D.U.B.A.I.". Every single aspect, action, usage and telemetry of your device is logged and sent to Huawei's Big Data Analytics servers, and it's embedded on kernel and can't be disabled. Most i could do on my kernel was disabling it on GPU framework, but the rest remains. If i turn it off on kernel or eliminate it, the mobile comms framework is killed and sim card doesn't even get activated, turning your device into a small tablet at most... so you either accept it or get yourself another phone.
Since using Treble Roms gets rid of the "system" part of EMUI, like their store, services, etc, it's possible that the Analytics part is somewhat suppressed but i can't be sure of that.
My advice is, stop updating EMUI and go Treble. Or just sell your device and get another. Or just resign to the new Huawei's reality and forget this community.

General Got my Edge S, unlocked bootloader and Magisk root

Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.

HopelesRomantc91 said:
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
Click to expand...
Click to collapse
Wow, thanks for all this info. That is great that you were already able to root and get Magisk on there with minimal issues. This is pretty much what I do with my phones right out of the box. Regarding that link for Gapps, I read through the start of that thread and the package is definitely what we'll probably need for this phone. But, without a working recovery at this point, I don't think there is another way to install it.

That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.

syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.

CCivale said:
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
Click to expand...
Click to collapse
It's worth noting that I cancelled my Giztop purchase and bought from Aliexpress instead. Can't remember if I actually said that or not.

there is twrp, it is experimental

Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
I couldn't find it, can you link it?

Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
Can you link it?

syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?

ktitimbo said:
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
Click to expand...
Click to collapse
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.

@HopelesRomantc91
Can you share the URL for unlock code request?
I couldn't unlock with global website...

I think I just used the global one here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/

Hello, I have patched boot img to my moto edge S 5g Chinese version and I have magisk root ok but if I restart the motorola it is lost and I have to reinstall boot parched, do you know why?

HopelesRomantc91 said:
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
Click to expand...
Click to collapse
Thanks for info . İs flashing g100 rom need root device or unlocking bootloader ?

Question Motorola Edge (2021)

Hello, Can any smart person because I'm slow lol help me get the Recovery or the Boot.img for a Motorola Edge 2021, My version is 12 (S1RMS32.48-18-11-2-3). Thanks

You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com

ruq said:
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
Click to expand...
Click to collapse
I understand that yes but my problem is that I don't have a laptop or PC to run the program so I'm trying to find another way to get the firmware for my Edge 2021, And if I can't do that is there any custom ROM compatible with this device that I could use to patch it with magisk?

So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com

oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.

ruq said:
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
Click to expand...
Click to collapse
I already solved that problem I use another phone to flash the images

ruq said:
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
Click to expand...
Click to collapse
My firmware is android 12 so would it be alright if I install this android 11 image?

Imparel said:
My firmware is android 12 so would it be alright if I install this android 11 image?
Click to expand...
Click to collapse
An android DOWNGRADE might cause issues...

ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
Okay I understand, I'll just take my chances and hopefully I don't brick my device...

ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
I did try it but instead of fully flashing the img I just did fastboot boot so that it would only boot into it one time and it didn't work at all so my only chance of rooting my device is using a PC to get the firmware of my phone, And thanks for the help.