Question Rooted Pixel 6 Pro - no longer receiving updates - Google Pixel 6 Pro

Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.

Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.

Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?

zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk

So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.

Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!

zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse

Related

Remove completely Experience ROM

Hi all,
I bought an old Oneplus 3 which have been flashed Experience ROM (https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259). Now I want to remove it completely.
I can enter fastboot then run command to boot recovery (http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img) then adb sideload to flash (http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/).
Stock ROM works well but the boot screen still is Experience ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that causes some problems with my later development.
Please help me to find out which partition of flash may not reset to original, or is there any way to flash completely as stock production?
Thanks all.
I think you need to just flash the original boot logo.
Wipe System, Data, cache and sideload stock from then you will be full stock for sure!
https://forum.xda-developers.com/oneplus-3/themes/mod-custom-boot-logo-pack-op3-t3525143
You can try one of these... They are way too good or you can flash the original one given in the OP.
Hope it helps... Thanks!
I wonder if there is any way to flash all flash of Oneplus 3 as stock. That mean flash all recovery, boot, system ...
Puddi_Puddin said:
Wipe System, Data, cache and sideload stock from then you will be full stock for sure!
Click to expand...
Click to collapse
This does not work. I've tried it before. Complete stock sideload, both OB11 and stable.
FYI: Jamal has removed the bootlogo on his latest releases
Shresth45 said:
This does not work. I've tried it before. Complete stock sideload, both OB11 and stable.
FYI: Jamal has removed the bootlogo on his latest releases
Click to expand...
Click to collapse
Boot logo and animation is stored on the System partition. By wiping it and overwriting it by flashing stock rom it should dissepear.
200791 said:
I wonder if there is any way to flash all flash of Oneplus 3 as stock. That mean flash all recovery, boot, system ...
Click to expand...
Click to collapse
There is a tool that's used to unbrick the op3, this tool flashes every partition to full stock again.
You need to look at the mega unbrick thread and use the full unbrick tool that wipes everything.

Android OS using lots of data

Noticed my Android OS is using almost 1gb of which doesn't seem right.
https://m.imgur.com/p1bAilv,XvmBuaw
Any ideas?
Edit 3: Updating will fix this properly.
Edit 2: That didn't fix it...
Edit: I've seemed to "fix" it. From my reading it is a background service trying to do a seamless update in the background. I disabled "com.qti.service.colorservice" using titanium backup and restore and it seems my background data usage has stopped. No negative consequences so far but it may prevent seamless updates. Another fix would probably be updating to the latest patch version...
Idk but I hope you get an answer... Been killing my battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also seems to hit Wi-Fi...
for me the issue did not go away until I did a factory reset
danw_oz said:
for me the issue did not go away until I did a factory reset
Click to expand...
Click to collapse
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
jhs39 said:
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
Click to expand...
Click to collapse
It has been a while but I'll reply so anyone else who comes will know. My state before and after was the same. All that changed was my OS version. Flashed the flash-all.sh after removing the -w, flashed the April bootloader (so no boot signing stuff, not the safest or recommended thing), booted TWRP, flashed twrp, flashed supersu, and then rebooted. No other mods besides adaway.
Are you on stock, rooted or unlocked bootloader? I had the same issue on stock (unlocked bootloader) where it was trying download an update repeatedly. I had to actually flash a custom rom to make it stop. Verizon did credit me back for the data it used.
Feel free to read my forum post there and try those steps. - https://community.verizonwireless.com/message/1500910#1500910
Don't ask me how I know but this is a backdoor to access your device. Be careful!
paulJW said:
Don't ask me how I know but this is a backdoor to access your device. Be careful!
Click to expand...
Click to collapse
downloading the security update(s) is a backdoor in?
Riiiight
y2grae said:
downloading the security update(s) is a backdoor in?
Riiiight
Click to expand...
Click to collapse
he said dont ask him how lol
I had to factory reset before this stopped

unable to install or launch TWRP

Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.

update v12.0.3.0.QJZMIXM for Redmi Note 9 Pro

anyone updated to the latest update care to comment, thanks in advance
I can't do it (on a rooted device: Note 9 Pro)
The update file is 616.8MIB
miui-blockota-joyeuse_global-V12.0.2.0.QJZMIXM-V12.0.3.0.QJZMIXM-41e0213a6b-10.0.zip
Impossible with the MIU installer or with TWRP 3.5.0_10-0
Always a error message
I also need some help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vin100 said:
I can't do it (on a rooted device: Note 9 Pro)
The update file is 616.8MIB
miui-blockota-joyeuse_global-V12.0.2.0.QJZMIXM-V12.0.3.0.QJZMIXM-41e0213a6b-10.0.zip
Impossible with the MIU installer or with TWRP 3.5.0_10-0
Always a error message
I also need some help
View attachment 5296013
Click to expand...
Click to collapse
I'm not sure where this OTA update could be used with custom recovery. even for the stock recovery it seems the whole recovery flash image is required
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
vin100 said:
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
Click to expand...
Click to collapse
i think so, although i havent done that myself
vin100 said:
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
Click to expand...
Click to collapse
no
just know that fastboot and recovery update methods are not the same
Thanks @koshikas, I know. That's why I'll wait some more experienced people here. I'm afraid to loose some data in the operation. If you've a good link for a ultra safe backup & easy restore I'll love it
vin100 said:
Thanks @koshikas, I know. That's why I'll wait some more experienced people here. I'm afraid to loose some data in the operation. If you've a good link for a ultra safe backup & easy restore I'll love it
Click to expand...
Click to collapse
MiFlash has options to flash with & without wiping. You can backup with the built-in tool or try Alpha Backup on play store.
Your recovery is outdated and is the reason for the failed flash. Try orangefox or dungphp's TWRP/Pitchblack.
Finally you can force a download of the full rom and not just the update from the updater app. It's in the menu at the top right. If you don't see it tap the 'currently installed' text a bunch.
Or just click here to download

Question How to get out to TWRP bootloop

I forgot to disable my encryption when I flashed TWRP now im stuck with bootloop on twrp
do we have option to disable encryption or this needs to be hard reset?
confirming hard reset that would be
advanced wipe
tap on
delvik
meta
data
then swipe to wipe right?
that shouldnt remove my stock room or brick my stock room right?
im sorry, im new to this.
Thanks in Advance!
It is not any rule to disable encryption when flash TWRP, so if you did the flash operation right that bootloop is not normal. Can you enter in TWRP? If so, try to delete Delvik only and try to reboot to system. If it returns to TWRP, you may need to do a Format data (yes) in advanced wipe section (this will erase all data from your phone) - reboot to TWRP (not absolute necessary, but I always do it) - reboot system.
Try Clean Flash custom Roms step 16: https://forum.xda-developers.com/t/4288121/post-85137963
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thank you for your swift response.
unfortunately it reboot back to twrp.
i might need to flash this over with miui.eu 12.5 using fastboot hopefully it get sorted.
i'll wait for your response before doing so though.
Try flash the Rom again. Confirm the Rom is downloaded correctly without interruption.
You shouldn't need to wipe or format other parts before flashing a Rom.
Before boot up, do the step as the picture.
Will do.
I will try to follow this guide: https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
astigjohn said:
Will do.
I will try to follow this guide: https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
Click to expand...
Click to collapse
If you are following that, you don't need to do as the picture I posted earlier.
mate, just an update. I was able to successfully installed global.eu room and booted it. i guess we move forward with disabling any password first before flashing TWRP and installing Magisk.
I appreciate you checking on this, man this community is awesome!

Categories

Resources