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!

[ROM] [US996] US99610k/10l/10n/10o/10p/20f Stock ROM TWRP Flashable Zip KEEP ROOT!

with very little activity lately for the LGV20, especially with the unlocked US996 variant, I created a TWRP flashable package for the recent US99610k release. this zip flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! because I have not tested this yet, I can't verify whether 10k is rootable or not or if there's Anti-RollBack (ARB), so you need to be root'd before flashing this! failure to do so will probably cause you to lose root and/or lose TWRP! if 10k does have ARB you won't be able to downgrade. stay tuned on this.
NOTE1: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
NOTE2: boot partition has been modified only to remove rctd, nothing else so I consider this to still be stock
Instructions:
download US99610.zip file listed below and put on microSD card
download your choice of root and put on microSD card, choose from either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v14.0 is recommended.
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
FLASH YOUR CHOICE OF ROOT - Flashing root is VERY IMPORTANT BEFORE REBOOTING!
reboot
profit!
Download:
US99610k.zip md5sum: 26da82660579673e5486e0361ff8c6e6
US99610l.zip md5sum: 01423ade5ba4977e1e8ae6d5bc244ecf
US99610n.zip* md5sum: bbde6e972305918712b3c51f03a1be10
US99610o.zip md5sum: 6019e92c6e0b3691689820b43b2b0c5d
US99610p.zip md5sum: 9875e4da163168c84ce479509bf7e19d
US99620f.zip* md5sum: 3AEBED11462D0F4A18D3FB9A4FDE95EB
* - unlocked non-US Cellular
for 20f (Oreo) please see this comment about updating TWRP and /data encryption https://www.reddit.com/r/lgv20/comm...s99610k10l10n10o10p20f_stock_rom_twrp/ed5olp6
Flashing Process (what flashing this zip does):
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)

On your instructions portion it says h91810q.

storm68 said:
On your instructions portion it says h91810q.
Click to expand...
Click to collapse
haha, thank you for helping me correct that!

Hmmmm. Not tested you say.... Nervous I am. Have time to fix using computer I do not.

I've been running 10k for almost a week now and haven't seen any issues. I can't necessarily speak for this ZIP, though. Taking a glance at it things look good.
One thing I'd like to point out is an issue I saw reported by another user. They stated that after they flashed US Cellar US996 updates their Unlocked US996 device was being picked up as the US Cellular device when attempting to use the LG website bootloader unlock. This is most likely due to the US Cellular bootloader being flashed and the device reporting a US Cellular device ID. This hasn't caused any issues when your device has already been bootloader-unlocked but I would not suggest that users re-lock their bootloader when running this US Cellular firmware as you may risk running into problems unlocking. The same user had also reported that they just flashed the 10f kdz with LGUP to correct the problem but not a risk I'd like to see anyone take. Just a word of caution.

McNutnut said:
....
Click to expand...
Click to collapse
Thanks for the heads up.
Can you confirm what security patch 10k is up to on the 996? Any other documented updates/fixes?

nickthaskater said:
Thanks for the heads up.
Can you confirm what security patch 10k is up to on the 996? Any other documented updates/fixes?
Click to expand...
Click to collapse
September 1st
No documented changes that I've seen.

No issues flashing for me... didn't wipe data, works well.. not sure what the changes are though, looks like the same

leonzwrx said:
No issues flashing for me... didn't wipe data, works well.. not sure what the changes are though, looks like the same
Click to expand...
Click to collapse
If it's just a security update there won't be any visual differences.
I just installed and everything is as it was on 10h, save for the security date.

Thank you.
I flashed from US99610h to US99610k with no issues. I did not flash supersu or magistick after flashing the firmware because I need to use uverse app. So far 24 hours with no issue or crash.

I extracted this modem (actually I just removed everything else from the zip and modified the script file) because I wanted to see if the newer modem fixed some streaming issues I had. I'm on Lineage, but it looks like the modem keeps crashing. It works fine for a few minutes while streaming music but then crashes and takes the WiFi and LTE with it for a few seconds.
Shouldn't this updated modem work with 7.1?
Doug

Hello, my phone stuck in Logo LG. But before I was in the red triangle and I thought that installing this would work well. But now the bootloader has been blocked and I can no longer enter recovery. And I have happened to install by fastboot the recovery stock but I can not find that file anywhere.
Somebody can help me please?
Edit. The LGUP detect the phone but with unknow model. I put the dll in common and doesnt work. I dont know how to unbrick my phone
Edit 2: I think the OEM is blocked, because I tried the "fastboot oem lock" command and it says it was already blocked, then try to unlock it "fastboot oem unlock" and says: FAILED (remote: unknown command). I think it's because the box was unchecked in Settings> General> Development, but the problem is that I can not boot to activate it.

10l has been released for the US Cellular 996: https://lg-firmwares.com/lg-us996-firmwares/
I confirmed with a US Cellular rep that 10l includes:
KRACK Wi-Fi vulnerability fix
BlueBorne fix (for SPLs September 1 or later)
Anyone with enough brains and heart to put together a .zip for the plebs?

nickthaskater said:
10l has been released for the US Cellular 996: https://lg-firmwares.com/lg-us996-firmwares/
I confirmed with a US Cellular rep that 10l includes:
KRACK Wi-Fi vulnerability fix
BlueBorne fix (for SPLs September 1 or later)
Anyone with enough brains and heart to put together a .zip for the plebs?
Click to expand...
Click to collapse
thanks for the update... I've updated the first post to reflect a 10l TWRP ZIP that works just like 10k that you can flash... tested working on my own US996

dimm0k said:
thanks for the update... I've updated the first post to reflect a 10l TWRP ZIP that works just like 10k that you can flash... tested working on my own US996
Click to expand...
Click to collapse
Thank you very much!

Hey, I'm still on Dec 2016 stock using us996 us cellular. I can flash and keep root? That's what it sounds like but just confirming. If I do a clean flash, Magisk 14 works fine? Thx

strifej said:
Hey, I'm still on Dec 2016 stock using us996 us cellular. I can flash and keep root? That's what it sounds like but just confirming. If I do a clean flash, Magisk 14 works fine? Thx
Click to expand...
Click to collapse
Just follow the instructions in the OP. You need to reflash the Magisk 14 image immediately after flashing the 10L zip.

Anyone know if the radio in either one of these is improved? - I have an unlocked US996 (from B&H photo, not US cellular) and regardless if I am using Verizon or AT&T, my current ROM's (US99610f) radio is very weak in weak signal areas - much crappier phones get much better signal in weak areas. I am hoping a new radio has solved this. It is the only thing I dislike about the V20
Also, with my standard unlocked US996 (already bootloader unlocked via LG developer website) am I better off with 10k or 10l ?

WTF? said:
Anyone know if the radio in either one of these is improved? - I have an unlocked US996 (from B&H photo, not US cellular) and regardless if I am using Verizon or AT&T, my current ROM's (US99610f) radio is very weak in weak signal areas - much crappier phones get much better signal in weak areas. I am hoping a new radio has solved this. It is the only thing I dislike about the V20
Also, with my standard unlocked US996 (already bootloader unlocked via LG developer website) am I better off with 10k or 10l ?
Click to expand...
Click to collapse
Be careful, when I flashed this to my unlocked US996 on Verizon I lost all data, and furthermore could not restore stock without uppercut. I think it's bound to US cellular, these firmwares.

R-T-B said:
Be careful, when I flashed this to my unlocked US996 on Verizon I lost all data, and furthermore could not restore stock without uppercut. I think it's bound to US cellular, these firmwares.
Click to expand...
Click to collapse
I'm not sure what you did, no, you shouldn't have lost your data nor is it bound to US Cellular devices. I have the 10L zip running on my unlocked 996 without any issue. I flashed it via TWRP from 10K and didn't lose anything.

Motog8 plus root

Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel

No source from motorola, nor updates yet.

Hello you can root your moto with magisk.

Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs

Thanks by the way. I found i way to root my Device.

Please do tell, how?

Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs

http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method

Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.

This is what I did. Yes..

Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.

Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl

carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.

THANKS!

Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.

successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google

esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.

a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.

Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.

yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant

recovery.img for T-mobile oneplus 7 pro

i have looked everywhere.
i am trying to find the stock recovery for oneplus 7 pro
- t-mobile version (if required)
10.0.1 oos
Honestly this phone has been the worst experience ever.
From t-mobile not allowing me access to files to fix my device, to forums being dead, sluggish and from several developers not caring about the issues others experience. to a single phone with 7 different variations. and the one I'm stuck with has 0% help.
ive seen multiple request for these files to go look and see "nvm i just flashed international rom..."
honestly it should be illegal for companies to not provide these files.

ivoe said:
i have looked everywhere.
Click to expand...
Click to collapse
That is because you are looking for something that does not exist. This phone doesn't have a recovery partition. On A/B partition devices, the recovery resides on the boot.img partition (along with kernel and ramdisk). The A/B partition scheme is very confusing if it is new to you (as it is to a lot of folks). You can possibly fastboot flash the stock boot.img partition, depending on what exactly you are trying to accomplish.
I don't buy carrier branded phones anymore, for some of the reasons you are experiencing. Converting the T-Mob 7 Pro to be "international", seems to be a pretty popular thing.

This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.

CosmicInsight said:
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
Click to expand...
Click to collapse
i have had to many issues with international that i msm back to tmobile.
i just didnt want to lose everything over an over doing this when things go wrong
i believe i have dumped the boot.img
i just hope it works when i do need it again.

Here's what I did whenever T-Mobile update to Android 10.0.1 I downloaded the OTA Update from off the internet then extracted it on my desktop then I used the payload-dumber-win64 to get the recovery and boot.img to use Incase I needed them. I used the extracted boot.img from the payload-dumber-win64 and followed instructions on how to use magisk patcher to patch my own boot.img. search Google for the T-Mobile update then use the tools to extract the whole thing.

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 ?