Database Users

How to reload OTA update after clearing cache?

I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?

Dave_Ro said:
I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?
Click to expand...
Click to collapse
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?

wantabe said:
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?
Click to expand...
Click to collapse
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.

Dave_Ro said:
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.
Click to expand...
Click to collapse
Sorry! I should have received a notification email that you had responded. For whatever reason, lately, the notification works some of the time but not always. I had no idea the bootloaders had gotten so effing screwed up! I bought my daughter a 2012 N7 for Christmas and no wonder I had to let it do an OTA before it would let me flash a factory image. I vaguely remember getting a bootloader invalid state error. My brothers bone stock 2012 N7 is on 4.4.4 with no issues, he would have called me otherwise. ; )
If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor you use (I use editpad lite or notepad) and remove the -w from the text it won't wipe your device. You will keep your settings, installed apps and storage. Extract the factory image into the same folder as your adb.exe and fastboot.exe, you should see these files if you have the 3G version;
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-krt16s.zip
radio-tilapia-1231_0.18.0_0409.img
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.

wantabe said:
...I had no idea the bootloaders had gotten so effing screwed up!
Click to expand...
Click to collapse
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
]If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor...
Click to expand...
Click to collapse
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.
Click to expand...
Click to collapse
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?

Dave_Ro said:
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
Out of curiosity I looked at the bootloaders and even though they say v4.23 a crap load of them are different sizes. Just as an example jwr66v is 2,150,992 bytes and ktu84p is 2,151,068 bytes. Don't have a clue what is going on. I can tell you that the bootloaders on the N5 and 2013 N7 are the exact same size across os versions that state the same bootloader version number.
---------- Post added at 02:19 AM ---------- Previous post was at 02:00 AM ----------
The vast majority of the time I also fastboot flash the images separately, I make a few too may changes in the system files to be able to use an OTA unless it's a very small one. I would flash the images for krt16s, bootloader, boot, system, recovery and radio. Then let it do a couple OTA's. 4.4.2 has a different size bootloader (4,005,632 bytes) and 4.3, 4.4.3 and 4.4.4 have the same size (2,151,068 bytes).
---------- Post added at 02:26 AM ---------- Previous post was at 02:19 AM ----------
Dave_Ro said:
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
I would think flashing the system image would clear it out but I guess not. If you were rooted you could run SDMaid and I think that would clear it. If you were rooted you could sideload the OTA and put it in /cache and see it that works. Sorry, I don't have a lot of experience running OTA updates, I usually have to fastboot flash images.

Well, in the end I successfully reflashed it to 4.4 (KRT16S), erasing user data. It then did 3 OTAs to 4.4.4 in quick succession.
Along the way it said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
tos? ISTR that was on the Atari ST
Thanks for the suggestion. I don't need half these apps anyway - it's good to have a clearout!
Dave

[Q&A] [FXZ}[DELTA] XT907 Google Play Edition 55 Languages (Unlocked Bootloader)

Q&A for [FXZ}[DELTA] XT907 Google Play Edition 55 Languages (Unlocked Bootloader)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FXZ}[DELTA] XT907 Google Play Edition 55 Languages (Unlocked Bootloader). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Mobile Network Problem
I was having problems with the network signal after i flashed CM12 then back to GPE (Luge) version, so i installed stock KK but still no signal. Luckily i downloaded the file that was previously atached to GPE ROM post.
Text from the Gpe post:
"NOTE: if you're currently on anything other than 185.46.10, download and flash the 185.46.10 FXZ from the link at the bottom of the op.
security versions for partitions are not upgraded from 183.46.10, so you can always flash back to 183.46.10 if you want to."
Apparently Luge GPe modifies partition security and it prevent from downgrade, fastboot use to show me up the error "downgraded security version".
The file tha FIX my problem was:
VERIZON_XT907_4.4.2_KPA20.10.1_cid2_BASE_1FF.xml.zip
if anybody need it i would help.

Pixel_McFly said:
I was having problems with the network signal after i flashed CM12 then back to GPE (Luge) version, so i installed stock KK but still no signal. Luckily i downloaded the file that was previously atached to GPE ROM post.
Text from the Gpe post:
"NOTE: if you're currently on anything other than 185.46.10, download and flash the 185.46.10 FXZ from the link at the bottom of the op.
security versions for partitions are not upgraded from 183.46.10, so you can always flash back to 183.46.10 if you want to."
Apparently Luge GPe modifies partition security and it prevent from downgrade, fastboot use to show me up the error "downgraded security version".
The file tha FIX my problem was:
VERIZON_XT907_4.4.2_KPA20.10.1_cid2_BASE_1FF.xml.zip
if anybody need it i would help.
Click to expand...
Click to collapse
I removed that attachment because there is a link to the full fxz in the op.
You probably didn't need to reflash anything.
The commands in the xml that likely fixed your issue are:
Code:
fastboot erase modemst1
fastboot erase modemst2
These commands erase stored modem data.
If you still have radio issues, you can reflash NON-HLOS.bin and fsg.mbn.
Also, as mentioned in the op, the security version for 185.46.10 is NOT upgraded from 183.46.10.
I am able to flash back and forth without any issues.

NO IMEI
Q9Nap said:
I removed that attachment because there is a link to the full fxz in the op.
You probably didn't need to reflash anything.
The commands in the xml that likely fixed your issue are:
Code:
fastboot erase modemst1
fastboot erase modemst2
These commands erase stored modem data.
If you still have radio issues, you can reflash NON-HLOS.bin and fsg.mbn.
Also, as mentioned in the op, the security version for 185.46.10 is NOT upgraded from 183.46.10.
I am able to flash back and forth without any issues.
Click to expand...
Click to collapse
Somehow I screwed up everything again, now im stuck on 4.4.2 without IMEI (IMEI 0).
I only can flash:
VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml
VERIZON_XT907_4.4.2_KPA20.10.1_cid2_CFC_1FF_SVC.xml
I'm on unlocked BL and able to flash custom recovery, I tried:
fastboot erase modemst1
fastboot erase modemst2
And flashed:
NON-HLOS.bin
fsg.mbn
But stiil NO IMEI (IMEI 0)

Does anyone have an alternate link to VERIZON_XT907_4.4.2_KPA20.10.1_cid2_CFC_1FF_SVC.xml.zip ? motofirmware.com seems to be down.

Pixel_McFly said:
I was having problems with the network signal after i flashed CM12 then back to GPE (Luge) version, so i installed stock KK but still no signal. Luckily i downloaded the file that was previously atached to GPE ROM post.
Text from the Gpe post:
"NOTE: if you're currently on anything other than 185.46.10, download and flash the 185.46.10 FXZ from the link at the bottom of the op.
security versions for partitions are not upgraded from 183.46.10, so you can always flash back to 183.46.10 if you want to."
Apparently Luge GPe modifies partition security and it prevent from downgrade, fastboot use to show me up the error "downgraded security version".
The file tha FIX my problem was:
VERIZON_XT907_4.4.2_KPA20.10.1_cid2_BASE_1FF.xml.zip
if anybody need it i would help.
Click to expand...
Click to collapse
I'm having very very similar issues can't get my phone to register properly on Verizon it will say its connected but no data then drop to no service however when it says its connected it won't send and receive calls or texts.. Also After test driving lollipop. Link to the firmware that saved your phone would be awesome! Thanks in advance.

motofirmware.com appears to be up and running again; it's not as elaborate as before, just a simple ftp folder.
i've added the names of files to search for to the gpe op...

how to flash the delta..
tomfoolery galore for me. have edited this post 3 times now. Looks like I am back to where I wanted to be. Mods delete this please.
[previously multiple questions about updating the delta, realizing I needed to go to luge, realizing that luge thing had over-written and deleted data unlike the limited upgrades of earlier GPE updates..then was stuck on Luge as recovery was gone...took a while to learn/get there but restoring nandroid I made at the start]

want to root after 4.4.2 KDA20.62-15.1 UPDATE
i have update motorola 4.4.2 KDA20.62-15.1 AND WANT TO DOWNGRADE AND ROOT ALSO ANY WAY TO DOWNGRADE TO 4.1.2

rat hacker said:
i have update motorola 4.4.2 KDA20.62-15.1 AND WANT TO DOWNGRADE AND ROOT ALSO ANY WAY TO DOWNGRADE TO 4.1.2
Click to expand...
Click to collapse
You can't downgrade if you have a locked boot loader.
Sent from my HTC6525LVW using Tapatalk

then how i unlock bootloader
I tried every possible condition to unlock bootloader of my motodroid razr m i tried official bootloader unlock method and also try motocyclps and any other way to unlock bootloader of motodroid razr m or any way to root this android version

rat hacker said:
I tried every possible condition to unlock bootloader of my motodroid razr m i tried official bootloader unlock method and also try motocyclps and any other way to unlock bootloader of motodroid razr m or any way to root this android version
Click to expand...
Click to collapse
No!
We've been lucky in the past and had an exploit that was discovered for another device, but right now THERE IS NOTHING.
Sent from my HTC6525LVW using Tapatalk

IMEI 0
HamBone625 said:
I'm having very very similar issues can't get my phone to register properly on Verizon it will say its connected but no data then drop to no service however when it says its connected it won't send and receive calls or texts.. Also After test driving lollipop. Link to the firmware that saved your phone would be awesome! Thanks in advance.
Click to expand...
Click to collapse
That file only worked for me one time, later i reflashed other rom and lost imei again. But at the end i fixed my XT907 IMEI 0 error flashing a ICS "baseband" NON-HLOS.bin. Maybe i will make a post of how to ecover your lost IMEI haha.

how can i flash motorola by command on fastboot mode
how can i flash motorola by command on fastboot mode\
example :::fastboot oem rebootruu

Great work, thanks for sharing!

*edit
---------- Post added at 06:37 AM ---------- Previous post was at 06:32 AM ----------
is that the final and latest build sir?
im running jbbl 4.1.2 right now.. can i just flash this room use rsd lite? or i should upgrade to KK?
*ijust download VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip, is that correct firmware to use this DELTA GPE room sir?

eenkiinkeenk said:
is that the final and latest build sir?
im running jbbl 4.1.2 right now.. can i just flash this room use rsd lite? or i should upgrade to KK?
*ijust download VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip, is that correct firmware to use this DELTA GPE room sir?
Click to expand...
Click to collapse
yes this is the final build. flashing instructions available here -> http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-official-fxz-t2659682

i download from mirror here.. http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14381292207348&key=f0a7f91912ae2b52e0700f73990eb321&libId=ico100qx01000n4o000DAfivpxiyq&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D2761322%26page%3D35&v=1&out=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F0B7nTxiBEdPfmYVhxWUUzWFoyZk0%2Fview%3Fusp%3Dsharing&ref=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D2761322%26page%3D3&title=%5BDELTA%5D%20XT907%20Google%20Play%20Edition%2055%20Languag%E2%80%A6%20-%20Pg.%2035%20%7C%20Motorola%20Droid%20RAZR%20M%20%7C%20XDA%20Forums&txt=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F0B7n...ew%3Fusp%3Dsharing
it doesnt have .xml file.. so i assumed flash it with twrp.. but it stuck at android logo.. can you help me sir?

eenkiinkeenk said:
i download from mirror here.. http://click.xda-developers.com/api...drive.google.com/file/d/0B7n...ew?usp=sharing
it doesnt have .xml file.. so i assumed flash it with twrp.. but it stuck at android logo.. can you help me sir?
Click to expand...
Click to collapse
That's not the correct one. I've uploaded the correct one for you here.

is that the final build sir? i already download it.. sorry for the noob question.. the system.img so big 900mb.. anw thanks for the respond

[IMG][5.0.2][Lollipop]RETCN XT1085 LXE22.92-18

The IMG is made for Moto X 2nd Gen sold in China mainland aka " XT1085" which was released a week ago. Major retailers in China have started to sell since Feb 5.
I can confirm the system also works well on my XT1095 pure edition,however Moto engineers have removed almost all of the google apps and services and implemented some key features with native chinese apps,like Moto Voice. Most of the bloatwares can be easily removed except a security app of lenovo and a voice assistant named Linxi.
You can get the full IMG from a mirror server in china or file factory
Mega
md5sum: 95306D8D80B1F60285E14D2A6FD7F4F0
XT1095 pure edition users can flash the boot.img and system.img via Fastboot utility.(1.Please backup your data before doing this!
2. Just flash the boot.IMG and all system image chunk files. Don't flash other partitions especially GPT and Bootloader,otherwise you would upgrade BL to 0x6012.)
As the Google apps, we can find many flashable zips in the forum,like @TKruzze's PA Gapps packages.

This work in xt1097? And how about root?

xarcom said:
This work in xt1097? And how about root?
Click to expand...
Click to collapse
It should work since there is almost no big difference in android system between 1095 and 1097. However, you should unlock BL first.
As the ROOT, chainfire's CF-Auto-ROOT image still works or you can flash TWRP recovery to your device via fastboot, and flash the root binaries from within TWRP.

I downloaded but how install? Sorry i'm noob , i have unlock bl

xarcom said:
I downloaded but how install? Sorry i'm noob , i have unlock bl
Click to expand...
Click to collapse
0.Backup your personal data.
1.Unzip the image.
2.Put your phone in AP fastboot mode.
3.fastboot flash boot boot.img
4.fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk. 3
5.fastboot -w
6.fastboot reboot

Does the Moto Voice works in other languages? Also the system is all in Chinese or we can change it to English or in my case Spanish.? Thanks.
Auto reply
Nop, the moto voice is not working with any language besides chinese, what I did was to uninstall via Titanium the moto voice, reboot and install the normal apk and everything is great now

No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?

alexfiorani said:
No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?
Click to expand...
Click to collapse
5.0.1 has fixed the memory leak bug.

purejoy said:
5.0.1 has fixed the memory leak bug.
Click to expand...
Click to collapse
Memory bug is still present
And Google knows about it
They are set to fix it in 5.1.

I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735

mercado79 said:
I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735
Click to expand...
Click to collapse
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.

purejoy said:
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.
Click to expand...
Click to collapse
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.

zhangyang_haha said:
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.
Click to expand...
Click to collapse
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error

juliospinoza said:
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error
Click to expand...
Click to collapse
each time i flash, it says that the image is too large. I tried different times but it doesnt work

zhangyang_haha said:
each time i flash, it says that the image is too large. I tried different times but it doesnt work
Click to expand...
Click to collapse
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.

juliospinoza said:
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.
Click to expand...
Click to collapse
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.

zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.

zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
we have to wait till some 5.0.2 version is released, in the meanwhile the OP should warn all the users about upgrading the bootloader
thanks

Steve-x said:
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.
Click to expand...
Click to collapse
except for the boot loader? Do you mean that motoboot.img?

zhangyang_haha said:
except for the boot loader? Do you mean that motoboot.img?
Click to expand...
Click to collapse
Don't flash the bootloader partition otherwise you would upgrade BL to 0x6012. Just flash the boot.IMG and all system image chunks.

Modified XT1095 OTA

I took the OTA update zip from my phone and modified the updater-script to look for:
motorola/victara_tmo/victara:5.0/LXE22.46-11/11:user/release-keys
Click to expand...
Click to collapse
This should allow the OTA to be sideloaded if you used the Motorola 5.0 Lollipop factory image that they recently published.
DISCLAIMER:
This is untested by me. I have no idea if it will work. Be sure you can return to stock if you need to. DO NOT flash this if your bootloader is locked!
Still here? Then if you want to be a guinea pig, you must be on the factory image from lollipop and the fingerprint must be motorola/victara_tmo/victara:5.0/LXE22.46-11/11:user/release-keys.
Url removed. Motorola has fixed the 5.0 images. Download them again.

Honestly I'd rather not do this. The check is there for a reason.

alvareo said:
Honestly I'd rather not do this. The check is there for a reason.
Click to expand...
Click to collapse
True. But Motorola hasn't been too good with their checks already. The only part that concerns me would be the sbl update at the end of the script.

I think the official 5.0 image Motorola posted was put together in a rush or something. After I flashed it, the software status in the bootloader always showed: modified. When I didn't see the OTA popping up after checking for updates yesterday, I tried a logcat and it was spitting out errors about build fingerprint mismatch (that made sense), but also errors about root being present? I had not rooted after flashing the 5.0 image... The OTA was clearly available from Motorola's servers (I could see the download link and manually download it if I wanted). It was just determined to be incompatible, so the phone just kept saying software is up to date...
After flashing the previous 5.0 I had laying around, the software status showed as official in the bootloader as well.

Very good info. Sounds like they botched the build and now it's causing issues for everyone. I bet when they compiled the image they had something extra in the /system and that caused it to increment the build fingerprint and the status to show modified

Anyone get this to work? Comes up invalid file for me.

I don't think it will work. If I remember correctly otas need a signature, which only motorola has. Since it's a modified ota, the signature won't match.
Sent from my XT1095 using Tapatalk

Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~

colourfuldays said:
Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~
Click to expand...
Click to collapse
I just read up on it some more. We are both correct. Yes you can modify an ota file but if it is not signed by motorola it can only be used on an unlocked bootloader. Anyoneone that has a locked bootloader will not work.
Sent from my XT1095 using Tapatalk

colourfuldays said:
Actually it will work. Chinese people had successfully modified ota of 5.0.2,he reduced BL's version and gpt's level. So if u flash that ,it would not update your BL version and also gpt level. because of this modified ota u can easily downgrade ~
Click to expand...
Click to collapse
In the other 5.1 thread they posted IMG files for everything but bl and gpt. I fastbooted just the system and boot files and now am on 5.1 may try the modem files at some point but didnt see a need so far. One disclaimer in the same thread i gave explicit directions to another user who said it didnt work at all but he was not on a pure edition and had a different bl version.
So why post all this here.... to agree with the above that with the script correctly modified it should work perfectly.

After flashing phone changed from G4 Plus to G4

I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.

You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695

That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.

Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.

GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.

sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.

Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !

sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...

bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.

bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar

gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.

echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes

gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.

gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch

gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.

echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands