Database Info

[Q] [OTA][KK]Rooted and new 4.4.2 OTA update

After I received the first 4.4.2 OTA update I rooted my Moto G and installed TWRP as recovery.
I just received a newer 4.4.2 OTA update. Can I accept this? I am afraid my TWRP & root will fail
Current version 174.44.9
{
"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"
}
New OTA update 175.44.1

vandermark said:
After I received the first 4.4.2 OTA update I rooted my Moto G and installed TWRP as recovery.
I just received a newer 4.4.2 OTA update. Can I accept this? I am afraid my TWRP & root will fail
Current version 174.44.9
New OTA update 175.44.1
Click to expand...
Click to collapse
If you have twrp it won't work if you try and update , also if you flash stock recovery and update it will remove root,but you will need to have an unmodified system for update to apply,which means a full unroot is needed before update can work

Flash stock recovery, unroot, then ota.

As you already received the correct answer I can't help you more, but could you upload the ota please?
Sent from my phone

Yes, instead of going back to stock, try to catch the update file, do a backup of it and share it with the community.
Thanks.

New update! No one knows what this has. What if it fixes the camera noise reduction?

I read some German forum, translated of course.
I read one of the posts. Apparently his battery went from 1%, to 50%, to 100%.
You know when we first updated to kitkat and our battery dropped like 20-30%, and if you reverted to 4.3 it's back up 20-30%? I think that fixes that calibration problem.
Take it with a grain of salt.

Bricked Moto G (maybe)

Happened in beginning of December- Okay, I have a XT1028 (it's the same thing as a XT1031) and tried to upgrade to CM13 using TWRP (also, I have bootloader 41.19). Unfortunately, I did not make a backup (stupid me!), because CM13 does not support CDMA devices on the Moto G because they are fixing LTE issues or something like that. So, I restored my phone using the 4.4.2 firmware. I used the guide right here: http://forum.xda-developers.com/showthread.php?t=2542219 But, there were lines going up the screen and stuff like that so I kept on trying it again. Oh yeah, after five minutes there's a boot loop. Then I read somewhere that the firmware has to be 4.4.4 or higher to get it to work on the 41.19 bootloader. Well, I flashed it, forgot the link but it involved MotoBoot and running some bat file. Then, when I boot it up, it has a black screen, and it's stuck on it. Well, I did something and it is now stuck on the Motorola logo, like this:
{
"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"
}
So help me.

I also downgrade from CM13, but to a 5.1 firm, and it didn't work too.
Reading some post, I decided to try a 4.4.4 firm, and yes, when I flash boot.img by fastboot the phone reboot and stuck on that Motorola logo. When I flashed againg 5.1, just for try, I've stuck on the bootloader messege.
Good luck, I'll follow this theard, maybe I found my solution here.

Samsung Galaxy S7 doesn't boot / bluescreen with yellow t

Hello everybody,
As the update on my Samsung Galaxy S7 (SM-G930F) failed, it does not start properly.
When I try to switch it on, it starts with a blue screen, saying "Installing system update...",
http://forum.xda-developers.com/picture.php?albumid=13616&pictureid=54196
{
"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"
}
but then it displays a dead android guy with a yellow triangle above.
http://forum.xda-developers.com/picture.php?albumid=13616&pictureid=54198
After that it starts the stock recovery mode.
http://forum.xda-developers.com/picture.php?albumid=13616&pictureid=54197
The Stock Rom does not start, so I am not able to get into the phone settings.
Unfortunatelly OEM is not unlocked.
There is no root on my phone. I can only acces the stock recovery mode and bootloader.
I already tried to repair the phone via SmartSwitch, but nothing has changed.
I have also tried to flash the stock firmware via Odin.
And of course I tried to wipe cache and factory reset.
Can anyone of you please help me?

The only time I had the screen turn a different color was when I flashed a Kernel that was for a different model.
This happened to you after an official update?

gaston_garcia said:
The only time I had the screen turn a different color was when I flashed a Kernel that was for a different model.
This happened to you after an official update?
Click to expand...
Click to collapse
Thanks for replying.
Yes, it happend after the OTA update...
In bootloader it said "SYSTEM STATUS: Official" before I flashed a stock rom via odin. Now it says custom, even after flashing with SmartSwitch.
What I am wondering is the fact, that the recovery says "Applied CSC code: DBT"
The phone is an european version, shouldn't it say then OXA or something like that?
I guess therefore "Appling Multi-CSC..." is correct then.

Doesn't anyone have any ideas?

General Problems updating to A13.

If I check for an update it shows there's an update to android 13. I've tried several times to update and it always says there was a problem installing the update. I start the installation and then says it's paused. I resume and it says the installation will continue when the device isn't being used. I again hit resume and it says there was a problem. Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
{
"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"
}
Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.

Rooted is the issue. Flash back the stock kernel or just flash 13 manually

You're trying to take an OTA while rooted and asking why it doesn't work? If you want to run a rooted phone, you have some learning to do before you brick your phone.

If root is the problem, it's not a big deal. Taking the OTA and then using Magisk to flash to the inactive slot has always been the easiest solution. The Oneplus never cared about root. Pixel 2 XL was my last pixel device I used but I always had a rom installed. So this is new to me.

Be careful...if/when you DO get updated and reboot into 13, make sure u flash the new bootloader to the other partition.

Question Pixel 6A bricked after last OTA update (5th may)

Hello,
I was running Android 13 stock image (I think it was the february or march build) + rooted with magisk method explained here
I upgraded to last version. Everything was fine after upgrade, the phone booted normally. So I downloaded stock boot image and patched it with Magisk. After flashing it with fastboot, the phone is stuck at Google logo.
I tried to install last Magisk APK on another phone and to patch again the boot.img, same result.
I tried to flash the stock boot.img, I have a message "Your device is corrupt".
What can I do ? I wish I don't have to wipe !!
I hope so much someone can help me.
Thank you for your 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"
}

Start with reflashing the factory image. Worst case youll need to do a factory reset, but I doubt that will be necessary.

ctfrommn said:
Start with reflashing the factory image. Worst case youll need to do a factory reset, but I doubt that will be necessary.
Click to expand...
Click to collapse
What method do you recommend ?
fastboot update image-bluejay-tq2a.230505.002.zip ?

frans0023 said:
What method do you recommend ?
fastboot update image-bluejay-tq2a.230505.002.zip ?
Click to expand...
Click to collapse
IT WORKED !!! Thank you so much for your help @ctfrommn !!