yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Questions before rooting?

I come from Motorolas and too root we just request oem unlock token from Motorola website get email in seconds then put phone in fastboot and run commands

fastboot oem unlock (token key)

(bootloader unlocked)

then to root we download the stock firmware from lolinet and extract the boot.img,

patch with magisk then run command in fastboot mode

fastboot flash boot magisk_patched.img

(bam rooted)

Now i read after we extract the pixel firmware and patch the init.boot.img with magisk okay..

After we patch the init.boot.img do i run the command in fastboot

fastboot flash init init_boot.img ???

Also in case of a mess up i always like to go back to pure stock so for Motorola phones we would manually fastboot flash the stock images to return back to stock.

When i extracted the pixel firmware folder i see similar images like in Motorola downloaded firmware.

Can i also manually fastboot all pixel stock images too?

example: fastboot flash system system.img, fastboot flash sparsechunk 1-16 etc...

making sure i have no soft or hard bricks before attempting modifications..

thanks anyone can chime in :)
[Google Pixel 7 Pro] KC69:
I just got a Amazon refurbished p7 pro . Model number GE2AE. My OEM unlock is greyed out. I haven't put my sim in it yet cuz it's a Verizon sim. I did hook it up to my wifi. I haven't signed in to my Google account yet either. I did do the play services checkin successfully. Several reboots and I'm still greyed out. Do I just wait? Or send it back ?? Or is there a trick I couldn't find reading almost this whole forum? Any help would be great. TIA
[Google Pixel 7 Pro] Fishawy:
I would really suggest steering clear from the manual process - which is more prone to errors - and sticking with Pixel Flasher. Easier, faster, and it just works. Also much easier to reflash stock if something was messed up.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
My oem still greyed out even after factory reset hope it's because I'm on beta 14. If not how to get rid of the connect to Internet or contact carrier oem greyed out message..now my device is unlocked it used to say oem not available on mobile locked devices ..come one wheres my oem unlock option ?

Edit I forgot I disabled some things so I'm reflashing the ota.zip and I'll try again..

EDIT OEM unlockable now had to go back to Android 13
[Google Pixel 7 Pro] KC69:
I still haven't let it update either. I keep killing it before it downloads. Don't know if that's good or not. It's on June 22 still. Says A13 tho. I was hoping the model number might lead one of our gurus to let me know what carrier to call about it as it's supposed to be sim unlocked. As per the Amazon ad.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Hope it's not a 3 day wait period like moto phones for oem unlocking
[Google Pixel 7 Pro] Homeboy76:
Send it back!

If you thought you were purchasing a phone with an

unlockable bootloader

because it was advertised as unlocked and you cannot unlock the bootloader.

The first step to being able to unlock the bootloader is being able to

enable OEM unlock

.

A lot of seller of Google Pixel phones list them as unlocked to deceive a buyer who is looking to purchase a Google phone with an unlockable bootloader. It is

unlocked

Carrier Unlocked, but you cannot root it because the bootloader is

not

unlockable.

Maybe this thread will help: Unlock ANY Pixel from Carrier by #mcl
[Google Pixel 7 Pro] jhjhjhjhjhjh:
I don't like using third party software.

I know adb commands..

Lastly, as long as I can get my phone into fastboot with an unlocked bootloader then I can always restore software.

Are pixel devices environment different in that aspect?
[Google Pixel 7 Pro] aleksgiab:
how can i upgrade without losing my data?
[Google Pixel 7 Pro] synesthete:
delete the -w in the flash-all script. This will prevent it from wiping the device when it flashes over. You can also backup your apps and data using Swift Backup, if you are rooted already.
[Google Pixel 7 Pro] simplepinoi177:
I'll quote what PixelFlasher's creator even says about doing it manually (plus some supplemental observations)

Basically, PixelFlasher is merely a GUI for most of the manual out-of-stock processes you can do (I think the only thing it doesn't is kernel flashing) -- so knowing how to do things manually gives you a better understanding of the program/GUI and how to identify how/what might've gone wrong and/or what would work best with the program.
[Google Pixel 7 Pro] TotallyAnxious:
I get my "error prone" manual process completed in 96 seconds. Never had an issue.

If you're going to "brag" about speed, then get a faster cable first.
[Google Pixel 7 Pro] Fishawy:
Thank you. I started my Pixel journey with the manual process, coming from OnePlus, and I used it for months, then I found out about PixelFlasher, and I'm recommending it for convenience not to disregard the commands knowledge.
[Google Pixel 7 Pro] Fishawy:
Not sure where you got the 'bragging' thought from, no one is bragging about anything. I'm stating it as a convenience element, no need for the harsh tone.
[Google Pixel 7 Pro] supermansaga:
I finally received the file to update to Google Play System update June 1.
[Google Pixel 7 Pro] badabing2003:
Yep, learn the manual steps, understand what it takes and when you're comfortable feel free to use tools.

Having said that, there are people who are not interested in understanding what each command is what it does and why it does what it does, and even if they follow the manual steps, they're just copy pasting and performing what the guide is asking them to do without understanding one bit, and that makes it more error prone which @Fishawy rightfully pointed out.

I'd say the same thing to you, if you're going to brag about performing a monthly update manually in 96 seconds, I challenge you to demonstrate that, I will boldly state that it is impossible unless of course your excluding many of the steps and just measuring one part of it.
[Google Pixel 7 Pro] TotallyAnxious:
Only picture I have on me. But the pixel 7 series supports faster speeds than the stock cable allows.

As I said in my post, sub 100 second flashes require a faster cable.
[Google Pixel 7 Pro] badabing2003:
That's flash time which would be the same regardless of manual or through a tool, where are the manual steps, how long are those taking you?
[Google Pixel 7 Pro] TotallyAnxious:
My original post obviously refered to flashing when I said 96 seconds. But I have commands saved to a file (and I understand which each one does. Copy and paste is faster than typing, especially when I could type an incorrect command) and just copy and paste them. Downloading zip takes a few minutes with 500mb internet and unzipping takes a couple minutes with a 12th gen i7. And I download zip file to phone while doing so on computer so I can patch the init_boot. So doesn't take very long.

I've never said not to use pixel flasher.

I was just contradicting that manual flashing is slower or error prone.

Not sure why you're upset.
[Google Pixel 7 Pro] badabing2003:
You commented on this post.

The the original post read:

for which you replied:

And now you're saying that you only referred to flashing?

The only reason I bothered responding because you accused @Fishawy of bragging where he actually was trying to be helpful and there was not one hint of bragging in there, ironically you were the one that bragged.

Anyways I'm not going to carry one this conversation, I said my piece.
[Google Pixel 7 Pro] TotallyAnxious:
I guess the "quotes" went over everyone's heads...

You're asking me questions, but saying you're not gonna carry on the conversation. Okay 👌
[Google Pixel 7 Pro] justDave:
Ah. I see you're using quotes for emphasis.

I'll just add that even "fairly experienced" manual flashers have been known to forget a step and end up "wiping" their device by accident.

In any case, it's nice to have choices.
[Google Pixel 7 Pro] TotallyAnxious:
I used quotes to emphasize the non seriousness of my words. Almost to denote sarcasm.

Quotation Marks for Sarcasm

Quotation marks can be used to signify sarcasm. More specifically, they are used to mean 'alleged' or 'so-called' or to show that a word is not being used in its literal sense. When quotation marks are used like this, they are known as scare quotation marks.

www.grammar-monster.com

I'll leave this here. English is the "required" language of XDA.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Update...I have a story to tell..

Oem Option available on Spectrum..

I had to go back to public android 13 to get the oem settings to populate in the background..

Thanks to all for this long journey.

Spectrum buys phones directly from Google so after you pay it off it's an unlock and bootloader unlockable device...yay..let's get modding :)
[Google Pixel 7 Pro] jhjhjhjhjhjh:
And I opted out of the beta and the ota downloaded but wouldn't install..

I chatted with Google chat and he sent me an email to wipe the device in recovery then the ota will downgrade...no more needing unlocked bootloader's to opt out of betas...
[Google Pixel 7 Pro] Morgrain:
As a sidenote, 34.0.1 still does not work and will cause a corrupted boot loop.

Use 33.0.3 to update.
[Google Pixel 7 Pro] roirraW "edor" ehT:
34.0.3 is better than 34.0.1, but still has a quirk, so still should still use 33.0.3, as you said.
[Google Pixel 7 Pro] BIGWORM:
Folks, let's keep it friendly in here. People will have their preferred method of flashing, be it manual or automated through programs/scripts. Let's keep it at that and move on. =)
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Has anyone gained R/W access to the /system?

Does the superrepack script work on pixels???
[Google Pixel 7 Pro] roirraW "edor" ehT:
From what I recall - because I don't actually pursue this myself, but I've only witnessed over the last two years with other users talking about it, there is a (or more than one) Magisk Module which does what's preferable to true r/w access, which is where it effectively simulates you having r/w access to /system, and you can through the module dictate changes to /system, which do in fact take effect, as long as the Magisk Module is continued to be used.

i.e. if you disabled or removed the Magisk Module, the "changes" would go away.

Again, since I've only been a witness to other users describing this, I never remember what it's called, but with some proper Googling we might be able to dig up the proper Magisk Module, and my memory could be faulty on some aspects of it, but I think that all is pretty close to what's true.
[Google Pixel 7 Pro] Lughnasadh:
I haven't used it, but here's a Magisk mod that makes most parts of the system partition become read-write.

GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)

Make system partition become read-write (it is also possible without Magisk) - HuskyDG/magic_overlayfs

github.com
[Google Pixel 7 Pro] jhjhjhjhjhjh:
thanks but its not working on A14 yet..
[Google Pixel 7 Pro] roirraW "edor" ehT:
I finally added that to Post #3 - Other, most important resources:

A list of other important apps

And I noted that it's not working with Android 14 as of today's date. Thanks, both!
[Google Pixel 7 Pro] laser03251:
Hi All,

Hoping you can help me out. So I successfully rooted my 7 pro about 5 months ago when I first purchased my phone was able to unlock bootloader, root / install magisk everything was working great. Then today, my phone took an OTA without my realizing it. Phone died and upon rebooting, i noticed that my root was gone. When this OTA installed, my magisk was hidden and i had modules active. I've since spent the last few hours trying to get root back but no luck. When I open magisk now, super user and modules are grayed out. I've reviewed the posts around 01/2023 by @badabing2003 and @Homeboy76 (here: https://xdaforums.com/t/guide-root-...ootloader-pass-safetynet-more.4221133/page-14) where this issue was mentioned but haven't been able to regain root using those suggestions outlined. This is what i've tried so far

1. tried basic firmware upgrade outlined using these instructions found here https://xdaforums.com/t/...-pro-cheetah-safetynet.4502805/#post-87540339 ; specifically post 2 using the firmware from June 2023 (which is what was installed by OTA), platform tools 33.0.3 and latest windows drivers

2. uninstalling my hidden magisk (named settings) and my original magisk (magisk manager) and using the flash.all.bat outlined in the above link

3. booting into safeboot mode, reboot, and seeing root was present - no luck ; then using flash.all.bat from # 1 using patch boot.img

4. I did try directly flashing the patched magisk img file but this caused an unsuccessful boot / bootloop and I was able to boot again using instructions outlined in # 1

At this point I'm not sure what to do. Would welcome any suggestions and can definitely provide more info. Thanks!
[Google Pixel 7 Pro] Homeboy76:
"2. uninstalling my hidden magisk (named settings) and my original magisk (magisk manager) and using the flash.all.bat outlined in the above link".

Excellent!

Suggestion: Disable

Automatic system updates

Settings > System > Developer options > Automatic system updates

If the OTA firmware that installed itself on your phone was the July 2023 OTA, are you flashing the magisk_patched....img that was patched with the July 2023 stock init_boot.img?

When you patched the July 2023 init_boot.img extracted from the July 2023 Factory image, were all the Magisk modules disabled?

If not delete that magisk_patched...img and create a new magisk_patched...img with the installed Magisk app of your choice. If you use the

Magisk Canary app

use 26102 attached.

Did you try flashing the July 2023 Factory image

init_boot.img

to remove the boot loops?

fastboot flash init_boot --slot all init_boot.img
[Google Pixel 7 Pro] simplepinoi177:
I can't remember where I was discussing it, but there was a method (probably a module) that does enable R/W on the system & data partition, but the caveat was that if it wasn't returned back to R/O, it would softbrick/bootloop the system....

Something to consider and should be a consideration as cause for caution...
[Google Pixel 7 Pro] badabing2003:
1- install TB checker from play store, run all options and look for Magisk, it should tell you the package name,

2- uninstall the package it finds

3- rinse and repeat steps 1 and 2 until the are no more Magisks.

4- reboot system

5- get the latest full OTA for your device

6- load it in PixelFlasher, process it to get the boot, then patch with Magisk stable 26.1 (don't use canary)

7- make sure you are using platform tools 33.0.3

8- flash pixel phone.
[Google Pixel 7 Pro] laser03251:
Thank you guys so much!! That all worked and successfully rooted again 👏👏. Going to go disable automatic updates now 😅
[Google Pixel 7 Pro] carlzinhobr:
Anyone could help me? I bought a pixel 4a5g and it's locked for others chip just T-Mobile chip works. Idk what to do! I have tried those ytb tutorials but whenever I connect to the wifi it gives me the same error; I want to unlock it. I'm currently at android 13
[Google Pixel 7 Pro] Homeboy76:
I'm assuming you bought the Google Pixel 4a5(G) from T-Mobile: When you pay it off T-Mobile will remove the Carrier lock.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi and welcome to XDA, @carlzinhobr. The Pixel 4a 5G section is here. There is a Q&A subsection, along with other appropriate sections, if you need any other information concerning your device.

There are one or two already existing, although old threads about it, if you use the Search field in that section to look for thread titles with "TMO" or "bootloader" in them.

Good luck!
[Google Pixel 7 Pro] carlzinhobr:
No! I bought it on AliExp and in my country we do not have US mobile operators
[Google Pixel 7 Pro] roirraW "edor" ehT:
T-Mobile Pixel 4a 5G conversation continued in the other, proper thread that you since posted in.
[Google Pixel 7 Pro] pro_granade:
I am on the Android 14 3.1 Beta with a locked bootloader on a T-Mobile device. I managed to get T-Mobile to permanently carrier unlock my phone tonight, applied the settings and rebooted and OEM unlock remained greyed out. I've tried wiping the phone numerous times. I've tried the dialer code that makes a "checkin succeeded" notification, nothing seems to make the option available. I am sure it's carrier unlocked because I was able to put in a Verizon SIM card and make phone calls. Has anyone else ran into this issue not being able to OEM unlock on the Android 14 beta?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Just within the last day or two, I saw @jhjhjhjhjhjh found that they had to switch from 14 Beta to Stable 13 for OEM unlocking to be ungrayed so that they could toggle it. They might've commented in it here in this thread, or the Android 14 Beta thread here, or both, but it should be straight-forward.

If it does allow you to downgrade, you'd have to opt out of the Beta program, if that's how you received the Beta version, and then you'd receive a downgrade OTA.

Google's Beta firmware programs always say to have an unlocked bootloader before installing it.

Good luck. You might want to continue any Android 14 Beta related discussion there. It's possible those running the Beta might have helpful information I can't think of, and I'd rather the posts related to Beta firmware be separate from this 13 Stable thread.

Edit: Since @jhjhjhjhjhjh had their bootloader locked, too, before downgrading to 13 Stable, it must be possible, and I re-edited this post to reflect that.
[Google Pixel 7 Pro] pro_granade:
yep, that's exactly what I ended up doing last night and it worked out perfectly. I'm back on the Android 14 beta rooted and everything working perfectly. just had to roll back by unenrolling from the beta. I should have updated my post to reflect that. I appreciate you helping me out
[Google Pixel 7 Pro] roirraW "edor" ehT:
No sweat, I'm glad you got it solved. It's nice when a solution actually consistently works.
[Google Pixel 7 Pro] jw6513395@g:
Any advice on best stable custom os for custom apps (as far as custom apps and app mods as well as wifi pass and other crack tools)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Just my two cents - the most stable Android I've run is stock Google, with tweaks for the bells and whistles, as I have outlined in post #3.

I haven't run a custom OS in about seven years, other than trying LineageOS on my old HTC 10, but it made that phone burning hot, and was definitely buggy.

Hopefully, someone else has a more appropriate answer for you, but this thread Custom ROMs would probably be a better place for your question.

Good luck!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Platform-Tools v34.04 is out:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

https://dl.google.com/android/repository/platform-tools_r34.0.4-windows.zip

(both links lead to that latest version).

Warning: I'd advise waiting for others to report back test results of it.

Edit: Take note, there's no changelog at the site yet:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 7 Pro] LLStarks:
Not sure if that extra PATH item is still needed, but the new version works fine. Factory flashed Beta 4. I do like how Google is avoiding fastbootd entirely now.
[Google Pixel 7 Pro] Ghisy:
What do you mean? The entire OS is being flashed while on "regular" fastboot now?
[Google Pixel 7 Pro] simplepinoi177:
That's fascinating....

If so/true, what a waste to have that extra environment for flashing just to not utilize it....I mean, it worked well enough on Pixel 5's and before (just fastboot mode; it's why i'm in the OP because it freaked me out the first time I flashed the Full Factory flash-all and saw this new fastbootd environment)

but then again, if it's bricking devices left and right all over, maybe it's for the best...
[Google Pixel 7 Pro] LLStarks:
Yes, everything is flashed as a super partition after the criticals.
[Google Pixel 7 Pro] supermansaga:
By avoiding fastbootd, you mean the old school command line fastboot mode is preferred? Can't keep up with all the improvement the new version has been trying to bring in. Thx
[Google Pixel 7 Pro] rester555:
This is excellent news. Will update today with 34.0.4.
[Google Pixel 7 Pro] Golf c:
I also noticed it did not enter fastbootd while flashing.
[Google Pixel 7 Pro] zippersmith:
Thank you BadaBing2023 for PixelFlasher. I started years ago on the original droid, droid max and turbos..pixel 2,3,and up until Feb/March was using ADB here on my Pixel 7 Pro. Life has gotten much more busy, and I just want you to know that I appreciate your work, it's made updating my phone so much more simple and easy. Thank you!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Wow, they actually posted release notes for the broken Platform-Tools v34.0.4 after not too long a time:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

@Lughnasadh, @badabing2003
[Google Pixel 7 Pro] badabing2003:
I wonder what they mean by.
[Google Pixel 7 Pro] simplepinoi177:
It mentions fastboot fix for file too large or invalid (sparse files) and yet in THIS INSTANCE here, it skips flashing certain parts of the partition image because it's matching the image/partition sizes wrong (still/again, but in this case not sparse files)...

Man are the devs over there ever gonna catch up...??? always 1 step forward, a couple steps back. Or they focus on some other things, but not on key things...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I was hoping you could tell me. :)

Sigh. :(

They've really got to start having a beta program for the Platform-Tools if things keep up like this for yet another six months.
[Google Pixel 7 Pro] badabing2003:
With all the layoffs, probably an intern is assigned to this.
[Google Pixel 7 Pro] Lughnasadh:
Think this is the commit...

https://android-review.googlesource.com/c/platform/packages/modules/adb/+/2620502
[Google Pixel 7 Pro] simplepinoi177:
That makes things clearer...thanks for that...

So....a whole 5 seconds faster....well, that's something....I guess it does fall under the claim "faster root/unroot"; by 5 secs...
[Google Pixel 7 Pro] GuyInDogSuit:
You mean this isn't the beta channel?
[Google Pixel 7 Pro] supermansaga:
I thought rooting usually takes just under 3 sec?
[Google Pixel 7 Pro] simplepinoi177:
god, imagine if rooting was only as easy & fast as how adb apparently achieves root access in a terminal and all we just simply had to do would be an adb command (now not with a 5 second delay); instead of downloading Full Factory image, extracting init_boot, Magisk, booting into the bootloader, and a fastboot command....!🤯
[Google Pixel 7 Pro] bird333:
Is there a way to stop Android from nagging me about updating? It is happening everyday now. I am rooted btw.
[Google Pixel 7 Pro] roirraW "edor" ehT:
In Developer options, do you have "Automatic system updates" disabled?

If that, or that and rebooting doesn't help, there's this from last September, that I've been saving in a browser window waiting for me to make a note of it somewhere that I'll be able to find it when I need it:

https://xdaforums.com/t/how-do-i-bl...ng-up-every-single-day.4489915/#post-87427181
[Google Pixel 7 Pro] GuyInDogSuit:
I think an ADB command to disable it would suffice though.
[Google Pixel 7 Pro] bird333:
Thanks. Yeah I have automatic updates disabled. I might just go ahead and update but they ought not bug you about it over and over. After 3 reminders they should just stop.
[Google Pixel 7 Pro] Morgrain:
I was running my P7 Pro on March update (rooted) till July, and not only was the phone nagging me about the "updating" thing, but somehow the phone actually activated the "Automatic system updates" automatically in the background. I only noticed by chance when changing bluetooth developer settings. It seems that Google can somehow set the toggle on, if you run old software for too long.