New Software Update QZKS30.Q4-40-95-4 Nov 1 - Moto G 5G Questions & Answers

Just wondering if anyone else got a official system update notification today (Dec 24) called QZKS30.Q4-40-95-4 which says "Includes android security patches through Nov 1st 3021", wondering if this is a official update or of my phone is hacked since I have all system updates off.

It's an official update for comcast variants, I suppose you didn't disable the updater successfully.

I received this update and am with TMobile. My auto update is off as well but I am still stock.

Well, not that update if you have a TMO phone. And you didn't disable updates either.
You need to remove the Motorola OTA updater apk to disable updates. It will not honor Android settings and can not be disabled.

That is exactly the update I received.
{
"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"
}
fddm said:
Well, not that update if you have a TMO phone. And you didn't disable updates either.
You need to remove the Motorola OTA updater apk to disable updates. It will not honor Android settings and can not be disabled.
Click to expand...
Click to collapse

Afaik that update was still pending for TMO, but I guess my manifest was stale. Sorry if I confused you.

Not a problem. I noticed it wasn't even listed on the website as well. Wondering if this little phone will even get 11.

Hi there i have the Moto one 5g ace xt2113-2 AT&T and i was trying to update it to android 11 it did not work as well as bricked my device. Now i am trying to return it to the stock android 10 but i am unable to find the right firmware. Some how the fastboot is not allowing to flash anything with (bootloader) permission denied written on the screen constantly. I tried Rescue and smart assistant that did not work, i tried manually flashing a firmware using fastboot and that also did not work.
Need Help Urgent...

You must unlock the bootloader. However, I don't think AT&T bootloaders can be unlocked. I think you are out of luck.

RETIEF said:
You must unlock the bootloader. However, I don't think AT&T bootloaders can be unlocked. I think you are out of luck.
Click to expand...
Click to collapse
Finally, flashed the android 11 without unlocking bootloader. Now i just need a method to root it, without unlocking the bootloader.

Related

J3 Emerge stuck on "CUSTOM BINARY BLOCKED BY FRP" - CANT FIND STOCK FIRMWARE/ROM

J3 Emerge stuck on "CUSTOM BINARY BLOCKED BY FRP" - CANT FIND STOCK FIRMWARE/ROM
Hi everyone,
I have some experience rooting, but not in recent years. So I was able to root with no issue. but I started having an issue and I tried to reset basic settings and I got stuck on this screen
{
"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 know I have to unroot and flash back to stock rom. No matter where I look, I cannot find it. I am expecting calls from jobs and I'm 3 months pregnant and my phone is a BRICK. I've had the worst luck. Can someone please point me in the right direction?
I have BOOST MOBILE.
SM-J327P - J3 EMERGE
I was running 6.0.1 prior... not sure if that makes a difference?
please help someone. I am losing my mind. :'(
Hi does this help? http://androidromupdate.com/firmware-samsung-us/sprint-samsung-galaxy-j3-emerge-sm-j327p-firmware/If you have twrp recovery or odin you may be able to get yourself unbricked!
Sands207 said:
Hi does this help? http://androidromupdate.com/firmware-samsung-us/sprint-samsung-galaxy-j3-emerge-sm-j327p-firmware/If you have twrp recovery or odin you may be able to get yourself unbricked!
Click to expand...
Click to collapse
I tried that already.... i get a error message in Odin
I cannot access my TWRP recovery
"Secure Check Fail : aboot"
Do you know how I can fix the secure check fail?:crying:
vivianajeanty said:
I tried that already.... i get a error message in Odin
I cannot access my TWRP recovery
"Secure Check Fail : aboot"
Do you know how I can fix the secure check fail?:crying:
Click to expand...
Click to collapse
I work primarily on LG's so i don't? I'll keep looking though and if i find anything ill pass it on. Have you considered re rooting and reflashing twrp thats here on xda and then flashing the stock firmware in twrp instead of odin? I know that sounds backwards but your devices twrp has that ability. I'll try to help if i can ?there are ways to bypass FRP on LG'S running marshmallow so it could be possible for you as well
I know I have to unroot and flash back to stock rom. No matter where I look, I cannot find it. I am expecting calls from jobs and I'm 3 months pregnant and my phone is a BRICK. I've had the worst luck. Can someone please point me in the right direction?
Click to expand...
Click to collapse
Updato is a great place to get Samsung stock ROMs. They even had the updates to the firmware of my J320P and my now J327P before any other site. Just load the app, search you model, pick either Odin or Kies and the app will judge the best CSC version for your phone and take you to it's download page

update procedure - choosing RUU CID: EVE_001

Hey sorry for my noob questions
I am late to the party, just recently I got my u11, coming back to HTC after 5 years from a sony background
This device is a lot more complicated to flash, I am reading all TUT threads and users posts multiple times trying to understand the proper way to backup/updates/restore.. but I haven't found a clear answer to my questions, I just want to make sure that I am not doing something wrong
CID= EVE_001 (which I believe is UK variant)
I am running stock 2.33 bootloader is locked / S-ON everything is untouched -yet-
(OTA from updates center says no update available and that I am running latest version)
After doing Nandroid backup to ext SD to the stock system in order to update the firmware
1- I understand that I can not flash a firmwares with different CID/MID and that will cause soft brick right ?
2- From the downloads spead**** to upgrade my fw I need to flash this file, is that right ?
Code:
30.01.2018 2.33.401.10 2PZC10000 HTC__001, HTC__M27, HTC__002, HTC__034 UHL (Single SIM) EMEA
3- This is out topic but, did someone actually succeed in re-locking the bootloader and restoring the device to stock state on this device ? because I've seen posts about some users struggling doing that
{
"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"
}
No need to upgrade 2.33.91.X is the latest firmware available. There will be an update sometime during the next weeks. But it might not be a major QMR, as it is quite sure just an SMR (Security Maintenance Release) to provide some Google patches. Next and last major QMR might be the update to Android 9 P.
Sent from my HTC U12+ using XDA Labs
Bootloader and s- status do not matter. The firmware is still flashable regardless. You do not need to change them back once unlocked.
All you do is download the current firmware, rename it, copy to external sd and boot to download mode. It will prompt you from there.
To be able to flash another firmware region you need s-off and change the cid via fastboot & download mode. Your region is currently 91. You need to s-off and change the cid before you can flash another region (ie the 401 region you pointed to)
Flashing a nandroid will most likely kill the device. Should you need to reset the phone and start over you should flash the stock firmware. If the nandroid image isn't a perfect copy of your stock system image, which it won't be, the risk of brick is very very high.

Galaxy S7 G930F bootloader problem

Helllo to everyone. On my galaxy s7 I have officail OTA updated 8.0 Oreo (DHR), never before I did not installing any ROM-s, root or something like that. This is my first experience with flashing. Yesterday I tried to install official 7.0 android (DHR) from Sammobile but after putting phone in download mode and start operation on Odin I get these errors.
{
"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 serval tries with different versions of firmware( oreo btu, oreo dhr....) I gave up. Before putting phone in download mode I enabled USB Debugging, but saw on Internet that many people enable OTA unlock (bootloader unlock) also. Should I enable OTA unlock or not because Samsung says that phone will lost all security features like samsung knox, samsung pay etc.. I flashing official ROM not some custom ROM and everything should work corectly without enabling bootloader unlock but doesn`t work, always I get that fail. Some ideas?
Sorry on my bad english I am not English native speaker and I hope that my problem is clear to understand. Thanks in advance
studentcro said:
Helllo to everyone. On my galaxy s7 I have officail OTA updated 8.0 Oreo (DHR), never before I did not installing any ROM-s, root or something like that. This is my first experience with flashing. Yesterday I tried to install official 7.0 android (DHR) from Sammobile but after putting phone in download mode and start operation on Odin I get these errors.
After serval tries with different versions of firmware( oreo btu, oreo dhr....) I gave up. Before putting phone in download mode I enabled USB Debugging, but saw on Internet that many people enable OTA unlock (bootloader unlock) also. Should I enable OTA unlock or not because Samsung says that phone will lost all security features like samsung knox, samsung pay etc.. I flashing official ROM not some custom ROM and everything should work corectly without enabling bootloader unlock but doesn`t work, always I get that fail. Some ideas?
Sorry on my bad english I am not English native speaker and I hope that my problem is clear to understand. Thanks in advance
Click to expand...
Click to collapse
Link to screenshoots of problem (2 pictures): https : // imgur. com /a / yiGtV2B - separated because I am new user

moto g pure fastboot magisk_patched image error

i have a moto g pure from xfinity mobile i found a stock zip file using the lenovo rsa i then copied the boot image then ran it through the magisk app i then fast boot it and this is the error i get i did oem unlock in settings and also fastboot oem unlock it sends to phone then starts to write and this is the error can someone smarter please 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"
}
moderater sorry im new please foward to appropiate forum thank you
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
jwoegerbauer said:
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
Click to expand...
Click to collapse
not a driver problem its a failed verification on the stock patched.img through magisk diferent verifiction key for the two images
OK
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
No I never did how did you get your bootloader unlocked?
Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
Newportswag74 said:
No I never did how did you get your bootloader unlocked?
Click to expand...
Click to collapse
There is your boot img
Newportswag74 said:
There is your boot img
Click to expand...
Click to collapse
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Agent_Orange1488 said:
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Click to expand...
Click to collapse
Really when I tried that at the Lenovo website it said my pure wasn't eligible
did patching that boot work?
i managed to patch the latest firmware with march security update, and root the stock rom, now i need to mess with gsis

Bootloader already unlocked but I cant flash it? [Solved: Phone is SM-G970N not SM-G970F]

I got an s10e from an ebay refurbisher but couldn't get OEM unlock to show up no matter how many times I did all the steps (connect wifi > change date > disable auto updates in dev options > tap download updates etc). At some point, I happened upon a tutorial that showed how to unlock the bootloader with computer usb + volume down + bixby on boot. To my surprise, it only gave me the option for *locking* the bootloader.
{
"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"
}
The OEM unlock option still doesnt even show up in the options however, not even grayed out. I do wonder if the refurbisher flashed their own vanilla rom onto this since it says the binary is custom . I imagine this is probably good to go?
I then tried to flash both stock firmware and that same firmware flashed with magisk with no success. I want to install /e/ android onto this, which like a lot of other rom installation guides, explictly says that I should update to latest firmware. In this case, the latest android 11 firmware available, or else downgrading from stock 12 to /e/ 11 could cause problems (according to the /e/ instructions).
Odin just didnt work. I tried multiple usb ports, multiple firmwares, multiple cables, multiple versions of Odin. The only consistent behavior is that trying to flash using odin freezes on startup, with a red error text showing up on the download screen. Using home CSC makes a SECURE CHECK FAIL : (BOOTLOADER) error show up, using factory wipe CSC makes a SECURE CHECK FAIL : (PIT) error show up. Some articles say to try using the pit option, but the odin warning of DO NOT USE THIS TAB has me apprehensive. This is as far as I've gotten.
So the problem turned out to be that I was sold the wrong product. Not cool refurbisher, not cool, maybe not even legal. Anyways, as you can tell in the download mode, this is not the SM-G970F that I was sold, its a SM-G970N. Still runs an exynos chip, but it's a korean model. Not certain how the refurbisher got the phone to show up as a F skew without the "THIS ISNT OFFICIAL SAMSUNG FIRMWARE" warning and all that.
Flashing firmware specificaly for the N skew worked just fine. I flashed the latest verison of android 11 KTN firmware for the phone and it worked, just needed a factory reset from recovery after I flashed the firmware. After I did so, the OEM unlock option showed up in developer options, already greyed out and turned on.
I next decided to try flashing /e/ android using the build madefor the F skew, and it worked without any fuss! I am now happily running a custom firmware like I planned to do when I bought this. I may get a weird boot screen in korean, but that's the least of my concerns.

Categories

Resources