Database Info

[Q] Moto G Telus/Koodo, screwed up 5.0.2 update : please help..!

Hello Android gurus
I tried to find the answer to my problem in the other threads, but I'm still not 100% sure if I should proceed.
. I had rooted xt1032 moto g prior to 5.0.2 OTA that came out yesterday.
I used full unroot with supersu prior to applying the OTA thinking it would be ok. I guess I screwed up, my phone is soft bricked.
I can get in stock recovery but otherwise it is on boot loop and ends up with 'no command'.
I have the moving line problem on the bootloader white screen which seems to imply a diferent version of kernel and bootloader, (which I do not full understand)
.. Which makes we wonder if it is unsafe to flash the stock rom 4.4.4 image of my phone.
And if it is safe, will I be able to update via OTA after that?
What are my options? Thanks in advance!

The moving line issue is probably due to the fact that you have the 41.18 bootloader on your phone.
I also have a Koodo xt1032 with the 41.18 bootloader and was able to flash back to stock Telus 4.4.4. Do not flash stock 4.4.2 as other XDA members have said that flashing 4.4.2 would brick your phone.
I'm checking for OTA updates but I keep getting the message that my phone's software is up to date.

UK Nougat update just arrived

Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.

m+a+r+k said:
Just checked and my Style is offering me Nougat with August security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
Woohoo! I think I shall downgrade my reteu-flashed Nougat to retgb 6.0 this weekend in preparation for it then.
If you happen to have an unlocked bootloader, do you mind capturing the OTA via TWRP? The way to do it is the following, if you have downloaded the OTA but not yet installed it:
Install ADB drivers (Windows): https://adb.clockworkmod.com/
Get the ADB command line (Windows): https://forum.xda-developers.com/showthread.php?t=2317790
Download the latest twrp .img for clark: https://dl.twrp.me/clark/twrp-3.1.1-0-clark.img.html
Turn on USB debugging on your phone: https://developer.android.com/studio/run/device.html
Disconnect the phone's USB connector (e.g. to a charger) if connected.
Turn off the phone.
Start the phone into the bootloader by holding down Volume Down as you power up the phone, and then releasing it.
Connect it to a PC or Mac via USB. On Windows, wait for it to be recognized.
On the command line, verify that it is available to fastboot by running the command
Code:
fastboot devices
and verifying that it shows up.
From the ADB/Fastboot command line, run
Code:
fastboot boot \path\to\twrp-3.1.1-0-clark.img
.
Wait for TWRP to start.
Once it is started, from the ADB/Fastboot command line, issue the command
Code:
adb shell find / /data /cache -xdev -name 'Blur_Version*' -print
; you should see at least one file with that name appear.
From the ADB/Fastboot command line, issue the command
Code:
adb pull /path/to/Blur_Version_....zip \path\on\pc\Blur_Version_....zip
Issue
Code:
adb reboot recovery
which should reboot the phone into the stock recovery, assuming your ROM is stock 6.0 including the stock recovery.
Once it is started, issue
Code:
adb sideload \path\on\pc\Blur_Version_....zip
. This will attempt to flash the OTA via adb sideload.
Once you have the OTA, you could put it somewhere useful (e.g. find a way to get it to prazaar's site) for the rest of us!

Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.

US needs this terribly.

m+a+r+k said:
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
All good. Update was reasonably quick and no problems at all. No settings or software lost.
Very happy.
Shame it is only 7.0 and not final version 7.1.2.

i could do with the Blue and Red boot logo now

Just got August Security update.
Blimey, what's going on? Nothing for over half a year then Nougat and a security update in 2 days!!!

Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)

obs3rv said:
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
Click to expand...
Click to collapse
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Maybe it has something to do with your experience. Someone else noticed it?

Edvin73 said:
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Someone else noticed it?
Click to expand...
Click to collapse
Yes. In fastboot, the existing Nougat bootloader is able to protect itself so you get the preflash verification failed error. If you continue to flash the MM firmware, it does boot, and does offer OTAs. One of these OTAs (the one that goes from 24.221.4 to 24.221.5) then flashes the aboot partition from within the OTA update.zip in the stock recovery. At that point, the bootloader is inactive so cannot protect itself from being effectively downgraded. This replacement of the aboot/emmc_appboot is what hard bricked my phone. So be careful!
Probably the better thing to do would be for people with retgb or retfr firmware, and an unlocked bootloader, to upgrade to the retgb/retfr Nougat firmware with August 2017 security patch, then boot (but not flash) twrp using
Code:
fastboot boot /local/path/to/twrp-3.1.1-0-clark.img
, and then create a backup of boot and system, then post it somewhere for others of us who are on the reteu firmware to use. This way we do not meddle with the bootloader but can still receive OTAs. (I captured a TWRP backup of the reteu version in this manner before I bricked my phone by attempting to switch to retgb.)
I have also managed to capture the intermediate OTAs between RETEU-UK-FR_6.0_MPH24.49-18 and 24.221.5 by successively downloading OTAs, starting up the bootloader and using TWRP via fastboot boot to copy them out of /cache on the device via adb pull. As far as I can tell, no one's ever made them available via web before. I have these:
24.49-18 to 24.201.3 (named with 24.11.18)
24.201.3 to 24.221.4 (named with 24.201.3)
24.221.4 to 24.221.8 (named with 24.221.4 -- this hard bricked my phone on flashing the bootloader)
But please be extremely careful with these -- don't use them if you've ever had newer stock firmware versions via fastboot or OTAs via stock recovery (of any region).
@Prazaar, @dzidexx -- any interest in putting these in your archives?

Not that I care, but...
smallmj said:
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
Click to expand...
Click to collapse
There's still hope for the peanut gallery. I heard that Verizon's HTC One (M9) just recently got a software update for Android N. That puts Motorola neck-in-neck with HTC and only about six months behind Samsung.

So Moto Alert has gone ? **** sake I actually used that so my girlfriend knew I was on my way back from biking and could stick my tea on.

Xt1543 full brick

Hi, about three days ago my phone had a failure so try to put a rom (a few days ago was a complete inexperienced) and install a rom that had nothing to do with the model, then my phone was left in a brick, to get information that my phone was an xt1543 download the correct rom but trying to install it does not leave me, just shows this on the CMD screen "version downgraded" to think that the error came from the rom, probe with all the rom of xt1543 ( I do not remember the latest version of android that had this cell phone) but with all I get the same error, it does not let me install absolutely any rom, researching in pages a solution could be to unlock the bootloader and then install a rom but it does not let me unlock the bootloader. In a nutshell the xt1543 is in a brick that does not let you install any rom or unlock the bootloader, help!

No Setup Wizard after reflashing, factory reset

I've bricked my phone while trying to roll back from Oreo update, then used DC Unlocker to unbrick my phone and return everything to normal (including IMEI, SN...) but I don't have initial phone setup after factory reset (first boot). Do you have any suggestions?

aleksp994 said:
I've bricked my phone while trying to roll back from Oreo update, then used DC Unlocker to unbrick my phone and return everything to normal (including IMEI, SN...) but I don't have initial phone setup after factory reset (first boot). Do you have any suggestions?
Click to expand...
Click to collapse
I had been in the same situation as you are to use DC Phoenix to unbrick my phone. If you have successfully boot to nougat (emui 5) then follow these steps;
1. Unlock bootloader,
2. install TWRP
3. Rebrand your device to your original brand
4. install the rollback package by dload method
5. install the OTA updates as received.
Your phone will be back to normal. It worked well for me.

Hi,
Thanks for your reply.
I don't think that you understand the problem that I'm having. I have returned everything back to normal with those same steps that you wrote. The only problem that I have now is the initial setup wizard app. It doesn't start when I factory reset the phone (you know that screen for logging into google account, connecting to wifi, etc...). I was on marshmallow, then I updated to Nougat via official OTA.

aleksp994 said:
Hi,
Thanks for your reply.
I don't think that you understand the problem that I'm having. I have returned everything back to normal with those same steps that you wrote. The only problem that I have now is the initial setup wizard app. It doesn't start when I factory reset the phone (you know that screen for logging into google account, connecting to wifi, etc...). I was on marshmallow, then I updated to Nougat via official OTA.
Click to expand...
Click to collapse
Yes i understand your problem, so insiting on rebranding your device to your brand again. Means if your phone originally is FRD-L02C675 (e.g.) then rebrand to that again and then follow dload method. After installing via dload method do factory reset. This will help you solve the problem and you will have normal startup with initial setup.

But I did that already. My device model is c432, and I managed to install russian firmware without rebranding. When I used dc phoenix and then flashed via dload I didnt have to rebrand because my device was slready c432.

Then i am not sure what could be troubling your phone to run the setup wizard. May some other member could help you to resolve this.
Are you able to login to google services?

Yes, Im able to login and use my phone normally

aleksp994 said:
Yes, Im able to login and use my phone normally
Click to expand...
Click to collapse
you may have installed the firmware badly, before installing it do a wipe of the data partition from the twrp, restart it in recovery and try to install the firmware again..

Firmware partitions question???

i've never flashed firmware partitions before on my other 2 moto devices, i understand having read the install of lineage that this step is req'd for this model.
i'll be using the lineage recovery to install the rom flash, this is the method ive done before. My question is once i sideload the firmware partitions, will this automatically asign which partion the rom will be written too or do i have to tell it which one, im understanding that it will be either A or B partition??
I'd like to wipe/erase as much of the stock rom off the phone, remove everything and then flash the operating rom to a clean phone. Am i understanding this correctly or missing anything? Is there anything that i need or should know or do when at this step? any help/advice would be greatly appreciated.
This is a brand new phone out of the box, is there other ways that any of you would approach this phone to totally wipe it, i'm hoping that ill get the android 11 update immediatley over ota, i understand that i will have to go through intial setup, to get to unlocking the bootloader, wish i didnt have to do that, also i dont believe kiev has an official android 12 oem/factory rom but lineage has 19.1, im thinking install 18.1 and then later reflash android 12 when it comes out. Im talking to much.... any advice be great. TIA

First things first, know your device. Is it an XT2113-2 RETUS variant or something else? As long as the bootloader can be unlocked, it seems any kiev (qualcom) variant should work with lineageos - just best to know what you started with in the event you need to ask for assistance or you want to revert back to stock.
My suggestion assuming you are starting from a new phone out of the box with the plan of putting official lineageos (either 18.1 - android 11 or 19.1 - android 12) on it:
Have the phone ota update to the most recent stock firmware. For XT2113-2 RETUS at the time of this post, this is android 11 version RZKS31.Q3-45-16-8-3 released 2022.06.30. Lineageos currently uses the binary blobs from this version. I suspect having the latest stock radios and bootloader on your device will result in fewer issues and may likely make your life easier later.
After updating to the most current stock version, request the bootloader unlock key from the moto www site. You may need to wait 24-72 hours or longer before the phone will allow unlocking. Leave the phone on, connected to your (primary) carrier, and use your carrier data (i.e. not wifi) during this time.
After updating to the most current stock version, put all the sims in the phone for the carriers you plan to use and let the phone provision the carriers (I've read this can only be done on stock firmware - switching carriers without having done this step apparently requires going back to stock). Test that you can swap sims and use the phone as you need to (e.g. wifi calling, try visual voice mail, try 5 G, etc).
Unlock the bootloader. Be sure to leave the oem unlocking toggle to allow after unlocking the bootloader.
Most important: when coming from stock (either now or in the future), follow the instructions on the lineageos www site. In particular, flash the copy-partitions.zip following the sequence described in the lineageos instructions. Don't worry about the A/B partitions for now, the device will take care of itself. You only need to flash the copy-partions.zip when comming from stock (either now or if you reflash stock in the future and then want to go back to lineageos).
Flash official linageos 18.1, android 11 (not 19.1- android 12). 19.1 is the newest version; however it may have issues. 18.1 works great (for me) and it will likely be easier for you to check if everthing is working as you expect. Upgrade (via ota) to lineageos 19.1 in a month or two.
Updating official lineageos via ota, the device will flash to the appropriate A or B partition. You should not need to do anything unless there is an issue.
I'd like to wipe/erase as much of the stock rom off the phone ...
Click to expand...
Click to collapse
Following the lineageos installation instructions will accomplish that.
Good luck.

notmyrealhandle, thanks for your time and reply, perfect write, i understood everything you said. i never thought of doing ota via data as opposed to wifi, thanks. perfect​