Related
Hello! I've read that LG Panther have an update which supports copy/paste, but zune writes me that my phone is up to date (my current build is 7003). I've tried to change a region and tried to sign in using different accounts, but that was hopeless... Any opinion?
proplayer666 said:
Hello! I've read that LG Panther have an update which supports copy/paste, but zune writes me that my phone is up to date (my current build is 7003). I've tried to change a region and tried to sign in using different accounts, but that was hopeless... Any opinion?
Click to expand...
Click to collapse
I've heard the same thing, and as far as I know, it's not going out via Zune (I've not got it, or seen it on either a Taylor or a Panther). I think we'll just have to wait...
Same here. My zune and phone both don't detect updates.
fb401 said:
Same here. My zune and phone both don't detect updates.
Click to expand...
Click to collapse
I think regularly checking the Connect site might be the best option for finding new builds.
l3v5y said:
I think regularly checking the Connect site might be the best option for finding new builds.
Click to expand...
Click to collapse
Microsoft Connect? I've tried to search there and failed...
proplayer666 said:
Microsoft Connect? I've tried to search there and failed...
Click to expand...
Click to collapse
The update isn't there yet, but I suspect it'll go there before anywhere else.
i've searched in google about this and understood that zune must flash this update, but it haven't caused. I think a special version of zune exists (not 4.7).
proplayer666 said:
i've searched in google about this and understood that zune must flash this update, but it haven't caused. I think a special version of zune exists (not 4.7).
Click to expand...
Click to collapse
I very much doubt you'll find an update, and I'm even more sceptical that it'll be on Zune. 4.7 is the latest version I know of, there might be some linking to Live IDs, or maybe only some devices/LiveIDs get the update.
Hello All,
I just wanted to chime in and say that I also have a GW910 and it also claims to be 100% up-to-date on version 7.0.7003.0
I just wondered if you lot all think that we will even get the update in 2011 at all.
Also... do any of you know what will happen regarding firmware updates (radio etc)?
I ask because I have a problem here in Luxembourg where my phone loses connection to HTTPS sites after a while. It can still connect to the internet but to anything related to HTTPS (SSL etc).
I know that it isn't a fault with the phone itself (Hardware) because it only happens when I am travelling around and my phone has to change between 3G and Edge quite often. It I stay at home, there is no problem at all.
Comments anyone??
nebc100 said:
Hello All,
I just wanted to chime in and say that I also have a GW910 and it also claims to be 100% up-to-date on version 7.0.7003.0
I just wondered if you lot all think that we will even get the update in 2011 at all.
Also... do any of you know what will happen regarding firmware updates (radio etc)?
I ask because I have a problem here in Luxembourg where my phone loses connection to HTTPS sites after a while. It can still connect to the internet but to anything related to HTTPS (SSL etc).
I know that it isn't a fault with the phone itself (Hardware) because it only happens when I am travelling around and my phone has to change between 3G and Edge quite often. It I stay at home, there is no problem at all.
Comments anyone??
Click to expand...
Click to collapse
I think we probably will get an update, there's not much point having developer hardware if we're developing on software that's out of date.
Radio updates etc I'm less sure about, my Taylor says the radio is from August, though the OS is much more recent.
That sounds like an issue with the general OS, and it may be being patched anyway, I'd see if you can submit that as a bug (via Connect) or via the on device feedback mechanism (can't remember how to access it, but I remember it being there).
According to this thread http://forums.create.msdn.com/forums/t/77100.aspx, no dev phones will be updated.
fb401 said:
According to this thread http://forums.create.msdn.com/forums/t/77100.aspx, no dev phones will be updated.
Click to expand...
Click to collapse
and what about mango? also no update?
screamer333 said:
and what about mango? also no update?
Click to expand...
Click to collapse
You need NoDo in order to get Mango, so no. I still have my Panther, I'm just waiting on the next batch of hardware this fall so I can change over.
I found a copy of the ChevronWP7.Updater and was able to update my pre-release LG GW910 build 7004 to NoDo. After I did that I was able to install Mango beta 2.
cmcginnis said:
I found a copy of the ChevronWP7.Updater and was able to update my pre-release LG GW910 build 7004 to NoDo. After I did that I was able to install Mango beta 2.
Click to expand...
Click to collapse
How did you get to 7004, I can read on my phone that I am on 7003.
cedtat said:
How did you get to 7004, I can read on my phone that I am on 7003.
Click to expand...
Click to collapse
Here is how I was able to get Mango installed on my pre-release developer phone (LG GW910).
NOTE: These directions are slightly modified to work as if you were starting from build 7004 (maybe 7003). After I the Chevron update I to install Mango beta 2 but received a 80180048 error. I used the backup that was created to get it back to the state just prior to the Mango update process.
The steps I took starting out with build 7004.
Run the ChevronWP7.Update twice to bring the phone up to build 7390 (NoDo)
Use the "Walshed" Phone support tool to put the device in a state where it can receive official updates - http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Be sure to follow the instructions and select ALL of the languages the keyboard supports.
Then following the Mango beta 2 installation instructions.
Mango beta 2 should install without any issues.
IMPORTANT: Uninstalling the Zune software will DELETE your backup. I created a RAR archive of the backup but kept it in the same folder and everything was wiped out.
cmcginnis said:
Here is how I was able to get Mango installed on my pre-release developer phone (LG GW910).
NOTE: These directions are slightly modified to work as if you were starting from build 7004 (maybe 7003). After I the Chevron update I to install Mango beta 2 but received a 80180048 error. I used the backup that was created to get it back to the state just prior to the Mango update process.
The steps I took starting out with build 7004.
Run the ChevronWP7.Update twice to bring the phone up to build 7390 (NoDo)
Use the "Walshed" Phone support tool to put the device in a state where it can receive official updates - http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Be sure to follow the instructions and select ALL of the languages the keyboard supports.
Then following the Mango beta 2 installation instructions.
Mango beta 2 should install without any issues.
IMPORTANT: Uninstalling the Zune software will DELETE your backup. I created a RAR archive of the backup but kept it in the same folder and everything was wiped out.
Click to expand...
Click to collapse
Hello,
I have tried what you say, but sadly the ChevronWP7.unlocker doesn't seem to work.
I get the Black screen where is asks what language, and whatever I select the screen simply closes.
What OS did you use? Was it a 64bit OS or 32bit OS?
I want to try it again, but at the moment I am stuck.
Thanks
nebc100
P.S. would you be willing to send me a copy of the ChevronWP7.unlocker that you used?
If so PM me, and I will send you my e-mail address.
nebc100 said:
Hello,
I have tried what you say, but sadly the ChevronWP7.unlocker doesn't seem to work.
I get the Black screen where is asks what language, and whatever I select the screen simply closes.
What OS did you use? Was it a 64bit OS or 32bit OS?
I want to try it again, but at the moment I am stuck.
Thanks
nebc100
P.S. would you be willing to send me a copy of the ChevronWP7.unlocker that you used?
If so PM me, and I will send you my e-mail address.
Click to expand...
Click to collapse
If you have tried it, disconnect your phone, reboot it, then connect it and wait for Windows to tell you the device has been correctly installed (if that hasn't happened yet). Then try ChevronWP7.Update again.
I used the 64-bit version. I'll find and post the link I used to download the app.
cmcginnis said:
If you have tried it, disconnect your phone, reboot it, then connect it and wait for Windows to tell you the device has been correctly installed (if that hasn't happened yet). Then try ChevronWP7.Update again.
I used the 64-bit version. I'll find and post the link I used to download the app.
Click to expand...
Click to collapse
There seems to be a misunderstanding in your communication. It seems as if you had a Panther that already HAD 7004 loaded on to it, which allowed you to updated all the way to post-Nodo.
There is currently no way possible for the Chevron Updater to bring a 7003 Panther up to 7004. Useless Guy even opened up the source code and tried to force the program into update his device and it did not work.
fb401 said:
There seems to be a misunderstanding in your communication. It seems as if you had a Panther that already HAD 7004 loaded on to it, which allowed you to updated all the way to post-Nodo.
There is currently no way possible for the Chevron Updater to bring a 7003 Panther up to 7004. Useless Guy even opened up the source code and tried to force the program into update his device and it did not work.
Click to expand...
Click to collapse
I am sorry if I did not communicate that correctly. Yes, I started with a Panther which already had build 7004 on it.
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.
Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.
michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.
Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this
You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.
ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Google has implemented a rollback prevention system on their devices. You cannot install an earlier version of Android over a later one. Attempting to do so generates an error message and the device will not boot. I believe this applies regardless of the lock status of the bootloader, but I'm sure someone more knowledgeable will chime in.
Sell your device on Swappa. Then purchase an unlocked model off Swappa, if available. No sane person is going to trade their unlockable device for your Verizon model.
if you unlock the bootloader, and wipe the device, you can downgrade to any version that google has published for the device.
If you do NOT unlock the bootloader, it is not possible.
@uicrnen: He has a Verizon device, so he can't unlock it.
Strephon Alkhalikoi said:
@uicrnen: He has a Verizon device, so he can't unlock it.
Click to expand...
Click to collapse
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
uicnren said:
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
Click to expand...
Click to collapse
Which is why I gave your post a thumbs up. Rollback protection then is similar to Factory Reset Protection in this regard. So long as OEM Unlocking is enabled in developer options and the bootloader unlocked, neither will kick in.
uicnren said:
if you unlock the bootloader
Click to expand...
Click to collapse
Please can you recommend the safest/most reliable way to accomplish this.
uicnren said:
...and wipe the device, you can downgrade to any version that google has published for the device.
Click to expand...
Click to collapse
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
IconBoy said:
Please can you recommend the safest/most reliable way to accomplish this.
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
Click to expand...
Click to collapse
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
1. BACKUP. Save anything you deem important, as your device will be erased.
1a. Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts.
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images ***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Worth mentioning to him if he's on Verizon, it isn't gonna work.
Upgraded anyway. Handful of issues but not enough to regret it. I do regret buying through Verizon though...
forwardthinking said:
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Click to expand...
Click to collapse
Sell it on swappa ms buy what you want.
uicnren said:
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
Click to expand...
Click to collapse
Unlocked Pixel 2 XL bought from Google Store.
uicnren said:
Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Will 15 Second ADB be sufficient, as I've always had success with that...?
Hopefully the ADB Fastboot file from Android Developer I can unzip and copy the updated contents to 15 Second ADB as their batch file installs system wide which is so helpful.
uicnren said:
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts
Click to expand...
Click to collapse
Done that already. :good:
uicnren said:
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images
Click to expand...
Click to collapse
As my device is unlocked and not specific to any carrier, am I correct in choosing the sixth from bottom from the list:
Taimen 8.1.0 (OPM2.171026.006.H1, Jul 2018)?
uicnren said:
***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
Click to expand...
Click to collapse
Duly noted!
uicnren said:
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
Click to expand...
Click to collapse
Once the device first boots from doing all this, is it okay if I skip all the Google account setup and just enable Developer Options and enable OEM unlock?
uicnren said:
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Click to expand...
Click to collapse
So the file I chose from the Android Developers Images page above, would be 100% stock?...and I can just go ahead and relock bootloader?
Should I factory reset after bootloader is relocked?
Thank you for clarifying the steps.
V 12.0.2.0 QGGMIXM --just got a notification.
Anybody try it out yet?
I'm interested in knowing if the upgrade slows down the phone. Since it is difficult to downgrade, I'm waiting to here from others
No upgrade in the UK yet.
DON'T DO IT
It will slow down your phone and you're stuck with it
jshames said:
DON'T DO IT
It will slow down your phone and you're stuck with it
Click to expand...
Click to collapse
Sometimes a factory reset after a big update is a good idea
blaccqnes said:
Sometimes a factory reset after a big update is a good idea
Click to expand...
Click to collapse
According to at least one post, that didn't help
blaccqnes said:
Sometimes a factory reset after a big update is a good idea
Click to expand...
Click to collapse
I did it cause I always do it after a big one is out, but it doesn't help at all. This firmware looks good, it has several very nice features...but it needs more polishing if you ask me. My phone was the best with Android 9 firmware, after Android 10 update it was also OK but not that nice as before...now it is even worse...
Years ago I had a Sony Experia phone. At some point an major update became available. However, along with the release notes was a explicit warning that the resource use of the update is greater, and that the performance of the phone may degrade. Further it warned that this would be irreversible as reverting was not possible.
I don't know if Sony still does this, but I think all manufacturers should. Even Apple IOS degrades performance after a few upgrade cycles on old devices, which is also irreversible unless an unlock hack is released.
Each person should be informed and be able to decide. Do I want the latest features and security, and willing to sacrifice speed?
pujolsk said:
I did it cause I always do it after a big one is out, but it doesn't help at all. This firmware looks good, it has several very nice features...but it needs more polishing if you ask me. My phone was the best with Android 9 firmware, after Android 10 update it was also OK but not that nice as before...now it is even worse...
Click to expand...
Click to collapse
jshames said:
Years ago I had a Sony Experia phone. At some point an major update became available. However, along with the release notes was a explicit warning that the resource use of the update is greater, and that the performance of the phone may degrade. Further it warned that this would be irreversible as reverting was not possible.
I don't know if Sony still does this, but I think all manufacturers should. Even Apple IOS degrades performance after a few upgrade cycles on old devices, which is also irreversible unless an unlock hack is released.
Each person should be informed and be able to decide. Do I want the latest features and security, and willing to sacrifice speed?
Click to expand...
Click to collapse
Yes, that is the point. In this case speed is not that much compromissed, but it feels ugly..
So you're taking about mainly and aesthetic issue? No lag?
pujolsk said:
Yes, that is the point. In this case speed is not that much compromissed, but it feels ugly..
Click to expand...
Click to collapse
jshames said:
So you're taking about mainly and aesthetic issue? No lag?
Click to expand...
Click to collapse
I dont know how to describe, it is more like stuttering animation. It just doesn't look nice. Icons also make some strange thing if you make them bigger.
This firmware looks like the first major iOS beta, if you ever had iPhone....
Just installed it. It feels okay, as advertized. But I don't have it's main attraction on my device. WHERE IS MY SUPER WALLPAPER????
And about downgrading, you can dirty flash your phone to any version (but don't downgrade your Android version, as some apps may render useless) via MiFlashtool. Use "save user data" option. Anti Rollback is not exist on Begonia. God thanks they didn't **** this phone further.
Edit: I've been using super wallpaper long before tho and applied via quick shortcut maker, but it didn't appear in wallpaper picker as it should be.
kekesed97 said:
Just installed it. It feels okay, as advertized. But I don't have it's main attraction on my device. WHERE IS MY SUPER WALLPAPER????
And about downgrading, you can dirty flash your phone to any version (but don't downgrade your Android version, as some apps may render useless) via MiFlashtool. Use "save user data" option. Anti Rollback is not exist on Begonia. God thanks they didn't **** this phone further.
Edit: I've been using super wallpaper long before tho and applied via quick shortcut maker, but it didn't appear in wallpaper picker as it should be.
Click to expand...
Click to collapse
So you say I can flash back to Android 10 and MIUI 11?
If yes, can you point me to some tutorial?
Thanks
pujolsk said:
So you say I can flash back to Android 10 and MIUI 11?
If yes, can you point me to some tutorial?
Thanks
Click to expand...
Click to collapse
My device have Magisk, EdXposed, and OrangeFox installed.
As flashing by custom recovery may render bootloop, and flashing by fastboot mode via MiFlash Pro reject downgrade, the only solution left is either XiaomiFlash or SP Flashtool. But SP Flashtool is locked to service account, so your only choice is XiaomiFlash.
I've red every flash command on XiaomiFlash, and the "Save user data" option format every partition EXCEPT user data (/data and emulated storage), basically the same operation to be performed when you install any rom via any custom recovery.
Fastboot flash leave the data intact for upgrading, but rejects downgrade. But in XiaomiFlash, as I wrote above, it should work bidirectional.
And don't worry about Anti Rollback. Since I've bootlooped over and over, I've performed countless Downgrade and Upgrade. But do at your own risk tho.
Hope that help.
kekesed97 said:
My device have Magisk, EdXposed, and OrangeFox installed.
As flashing by custom recovery may render bootloop, and flashing by fastboot mode via MiFlash Pro reject downgrade, the only solution left is either XiaomiFlash or SP Flashtool. But SP Flashtool is locked to service account, so your only choice is XiaomiFlash.
I've red every flash command on XiaomiFlash, and the "Save user data" option format every partition EXCEPT user data (/data and emulated storage), basically the same operation to be performed when you install any rom via any custom recovery.
Fastboot flash leave the data intact for upgrading, but rejects downgrade. But in XiaomiFlash, as I wrote above, it should work bidirectional.
And don't worry about Anti Rollback. Since I've bootlooped over and over, I've performed countless Downgrade and Upgrade. But do at your own risk tho.
Hope that help.
Click to expand...
Click to collapse
Thanks, now I know what my only option is.
Just to be clear, before I use XiaomiFlash, I have to unlock my bootloader, right?
pujolsk said:
Thanks, now I know what my only option is.
Just to be clear, before I use XiaomiFlash, I have to unlock my bootloader, right?
Click to expand...
Click to collapse
Of course
kekesed97 said:
Of course
Click to expand...
Click to collapse
Thanks, I will go and check it out...
So it turns out, according to the company website, that this is a "beta global stable release" sent to limited users:
https://c.mi.com/thread-3218614-1-0.html
Which explains why most people haven't gotten it.
The company doesn't give a link to download but if you google it you can find it.
Does anyone know when EU QGGEUXM version comes out?
jshames said:
So it turns out, according to the company website, that this is a "beta global stable release" sent to limited users:
https://c.mi.com/thread-3218614-1-0.html
Which explains why most people haven't gotten it.
The company doesn't give a link to download but if you google it you can find it.
Click to expand...
Click to collapse
That makes sense, as it feels like it is a beta, an early one. I just hope they will fix it and make it feels nicer for everyday use, but knowing Xiaomi and how many devices they make on a daily basis, I am not that sure...
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
granosalis said:
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
Click to expand...
Click to collapse
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
roirraW edor ehT said:
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
Click to expand...
Click to collapse
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
granosalis said:
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
Click to expand...
Click to collapse
You're welcome! It's at least 50/50 chance that it would be better to wait. I have no problem on the .017 December firmware, but plenty of folks do, and I haven't had much of a problem at all with any of the firmwares so far.
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
Because it fixes some things for some people.
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
granosalis said:
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
Click to expand...
Click to collapse
You'll have to allow the phone to boot up first since you'll need access to the OS to perform some commands on your PC. You can just allow the phone to boot and skip a lot of the setup process, only because flashing the most recent factory image will put you back to stock, AKA wipe your phone back to where it was when it left the factory, and then once the new image has been installed you can do a proper phone setup from scratch.
If you're not familiar with using terminal commands and don't want to run the risk of messing up your phone, I suggest you use the Android Flash Tool since it'll do everything for you and is fairly simple. Just connect your device over USB and visit the Android Flash Tool using the link below. Android Flash Tool works with any Web browser that supports WebUSB, such as Chrome or Edge. The Android Flash Tool guides you step-by-step through the process of flashing your device - there's no need to have tools installed, but you will need to unlock your device and enable USB Debugging from Developer Options.
I've provided a link on how to enable USB Debugging and Developer Options, here - https://source.android.com/setup/contribute/flash
To flash the latest January Stock image on your device, simply visit this link - https://flash.android.com/build/8030436?target=raven-user&signed
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
RetroTech07 said:
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
Click to expand...
Click to collapse
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
They do the same thing, however the android flash tool is much easier to use.
granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
I forced it on day one and I guess I was one of the lucky ones that didn't have any issues.
granosalis said:
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
Click to expand...
Click to collapse
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
RetroTech07 said:
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
Click to expand...
Click to collapse
No my phone should arrive in about 10 days if everything goes as planned.
It is not easy to take a P6P 256gb white from italy , this model, in fact, is not sold in europe for what I know.
While waiting I try to keep myself informed. It's been a long time since my Galaxy Nexus.