Related
Hello,
I own the 32gb h791 nexus 5x and the phone is bootlooping after android 7.0 update.
so basicly the phone showing google logo and then reboot back..
My bootloader is unlocked, so I tried to flash marshmellow without any success.
I can not access the recovery.
I saw a thread about flashing tot but i read in the thread that It is re lock the bootloader.
I dont have efs backup..
Any help?
Thanks,
Nimrod
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
But that's a hardware bootlop no software
How many files had been flashed when you've tried to flash it? If any, have you done any modifications like root etc ?
If no, just lock bootloader and send RMA
If you can send to Google, you don't have to lock bootloader.
If your warranty expired, try to talk to Google may they will give you a replacement anyway, if not Google, you can try to LG because of 15mo warranty from production date
TypNguy said:
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
Click to expand...
Click to collapse
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
His problem is a hardware issue not software. Might get lucky and volte it back to life but I highly doubtful . LG notorious for certain models that infinite bootloop issue g4 was the worse.
Yes, the root toolkit worked for me. I still don't know how to flash correctly, so if you have the right driver's associated with your phone/laptop it should be a breeze. The best part is that there's a log, so you know what the toolkit is doing. For example, it may unroot your phone before it flashes the new stock image for you.
---------- Post added at 02:40 AM ---------- Previous post was at 02:36 AM ----------
Just found wugfresh's answer to your question I think.
Link
Address: http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
Hi guys.
I finally got the notification I was dreading: I can now do a system upgrade to Pie. But shall I?
Even disregarding the learning curve and the mixed comments, I'm weary that one or more of my apps would not be fully compatible yet and would give me trouble.
So my question is: if I decide to go back for any reason, can I do so by simply flashing an Oreo factory image and get to keep my data, or maybe by restoring an Oreo nand backup?
Or is it more complicated by that because of the rollback protection thingy I've been hearing about?
BreadedChicken said:
Hi guys.
I finally got the notification I was dreading: I can now do a system upgrade to Pie. But shall I?
Even disregarding the learning curve and the mixed comments, I'm weary that one or more of my apps would not be fully compatible yet and would give me trouble.
So my question is: if I decide to go back for any reason, can I do so by simply flashing an Oreo factory image and get to keep my data, or maybe by restoring an Oreo nand backup?
Or is it more complicated by that because of the rollback protection thingy I've been hearing about?
Click to expand...
Click to collapse
Interesting question that has two answers. There are those that say you can by clean fastbooting the factory image, and there are those that say you can't because of the bootloader and google's stupid roll back prevention. I've read about people rolling back before, but have never tried it personally. I suppose you could fastboot the last DP5 to get a taste of 9.0, then roll back to 8.1 if you don't like it. Your call my friend.
I have also never tried it but if it works it's likely not that easy because of the mentioned Bootloader Lock.
Either way my approach would be to find out if those apps that are important to you would work on pie by searching the Forums or play store comments.
Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
Badger50 said:
Interesting question that has two answers. There are those that say you can by clean fastbooting the factory image, and there are those that say you can't because of the bootloader and google's stupid roll back prevention. I've read about people rolling back before, but have never tried it personally. I suppose you could fastboot the last DP5 to get a taste of 9.0, then roll back to 8.1 if you don't like it. Your call my friend.
Click to expand...
Click to collapse
That question does not really have two answers; you *can* roll back the system/bootloaders/firmware, you *cannot* roll back the userdata, which means that in order to retain the majority of your data, you would have to restore userdata from a backup, and that, of course, will only contain the data up to the point that the backup was made.
Anti-rollback features really only apply to someone trying to take advantage of an old security vulnerability by "upgrading" to an older system build. You can't do that on a locked system.
For what it's worth: Yes; if you have an unlocked bootloader.
Code:
fastboot unlock_critical
is a must (flash-all writes over the bootloader)
If everything is unlocked, it is as simple as:
(from the directory the 8.1 factory image is extraced to)
Code:
adb reboot bootloader
fastboot -aa
flash-all
(hold down vol-dn button when it gets to userdata and release once it boots back into bootloader)
Code:
fastboot -ab
flash-all
Once complete it should boot into Oreo.
...obviously this will not work on Verizon devices.
Thank you gentleman. Now I have ammo for when someone says your can't downgrade!
Anyone been able to successfully receive an OTA to the beta yet? Enrolled my device last night the moment I got it home and nothing so far.
Disclaimer: I'm using a carrier and bootloader locked T-Mobile version; still hoping I can eventually get TForce to carrier unlock this for me sooner rather than later otherwise i'll just return it and get one direct from good old El Goog.
Did they get magisk for the 3XL yet; last I read over there they didn't have it for Q on the XL.
This true. I spent a couple hours on this last night and it does not work. I went back to pie.
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
That's pretty much what I figured, but wasn't certain. Good to have some feedback from others; sounds like we can pretty much confirm that it isn't being pushed to the 3a devices yet.
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
DanRyb said:
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
Click to expand...
Click to collapse
Yep. It's possible they are withholding the OTA from carrier devices...
P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
alphahere said:
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
Click to expand...
Click to collapse
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
P$udo said:
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
Click to expand...
Click to collapse
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Looks like Pixel 3a and 3a XL were removed from eligible devices on the beta sign up page.
I wonder what's up?
if anyone is looking for the download you can find it here
alphahere said:
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Wow. Thanks for that. I thought fastbootd was a mistype when they were compiling. I didn't know that it was a whole other thing. Seems to be more akin to what recovery previously was on some older devices.
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
elpindian said:
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
Click to expand...
Click to collapse
I did not get the OTA. I downloaded the firmware image and flashed it.
Android q beta isn't ready for the pixel 3a/3a xl until June
An FYI... I just wandered over to Papajohnwu's Twitter and he is saying he'll be ready for Q.That's some good news, hate to be stuck on Pie forever.
If you have a 3a (xl) from a carrier like T-Mobile where to boot loader is locked, if you're able to use adb/fastboot to flash beta 3, you very well may not be able to revert the phone to Pie. I'm stuck as I got mine on the day TMO put them on sale, then opted in to the beta expecting to be able to opt out, well considering they removed that option, I'm now stuck on Q..
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
I'm curious how you got it unlocked from T-Mobile. I picked mine up on release day and when I got around to checking, OEM Unlocking was greyed out. Did you do this before installing a SIM?
Thanks!
PhoenixPath said:
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
Click to expand...
Click to collapse
It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks
Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.
Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.
Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).
relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.
ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.
The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!