Database Info

[Q] Which unlock tool to unlock v4.1.1?

Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks

v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?

berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?

WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions

Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.

Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope

Desperate need of help with my device

I’ll make this short.
I was successfully rooted. But I couldn’t update to 9.5.6.
I updated but it keeps failing. I switch to slot A and I was on 9.5.6 but WiFi didn’t work and apps would crash randomly, and it was laggy. I would go back to slot b and WiFi worked and everything was great but I’m on 9.5.3. And I would try to update again and it would fail and sometimes I would have to have in fastboot and reflash twrp to reboot to restore. I restored the device multiple times, removed root but it still happens. I used to always use android but I was on iOS for years and I’m used to jailbreaking and Apple IOS. Please help me. How can I restore and start from scratch? Or how can I fix this? It’s very annoying. I have my info backed up so I don’t care what I have to do. I love this phone but I had the Verizon iPhone bug when people call me and I answer it fails on there end. Or else I would deal with 9.5.3. All help is greatly appreciated.

You need to read the threads better, it's already been explained that wifi can end up being disabled because the rooted boot.img is older than your current rom version. Flashing one of the kernels available usually fixes this. You can also extract the boot image from the rom you downloaded and patch that boot.img file using Magisk, then when you apply that everything should work correctly.
From reading your post it would appear you're on T-Mobile (US) so you would need to download the 9.5.6 package and then extract the boot.img, then patch that using Magisk and push it to the phone using fastboot, once you reboot everything should be rooted and working.

Android One XT1900-1 WiFi/SIM Not Working After Stock Flash

I have the Google Fi Android One X4 XT1900-1, and I made the mistake of trying out Lineage OS, which was great on my last couple phones but a bit underwhelming here. So I wanted to go back to stock. I tried following the threads here and here (just the return-to-stock part, not the Pie update), using the Linux shell script. And everything worked great! EXCEPT! Neither the WiFi nor the SIM card are working. I tried using the firmware from Motorola-Firmware-Team on Android File Host that were marked as Fi, both the most recent and a few versions back. And everything works except the modems.
Any suggestions? I don't really want to be stuck with this meh version of Lineage.

https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flash the latest release (XT1900-1_PAYTON_FI_9.0_PPW29.69-39-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with your shell script, I guess you flashed stock oreo instead of pie and going back to oreo with pie modem is not a good idea

First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Code:
#!/bin/sh
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
fastboot --set-active=a
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem_a oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot
Maybe there's something missing, or something I should take out?

It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..

trixter42 said:
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Maybe there's something missing, or something I should take out?
Click to expand...
Click to collapse
ElijahUSA said:
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
Click to expand...
Click to collapse
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore

SyberHexen said:
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
Click to expand...
Click to collapse
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.

trixter42 said:
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
Click to expand...
Click to collapse
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions

SyberHexen said:
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
Click to expand...
Click to collapse
Still having trouble...
I did format everything in TWRP before flashing it. I've tried this a bunch of times, in a bunch of different variations, but I've made sure not to carry Lineage data over into the stock ROM.
I tried flashing the Pie Fi stock from lolinet and then flashing your Pie Fi firmware, but then it just bootlooped. I tried it with the retail firmware too, just in case it was some weird rebranded old stock thing, but the same thing happened. It was a good thing to try, though!
Ultimately, the stock ROM just isn't reading my IMEI for some reason, even though Lineage sees it just fine. I do have my IMEI, is there a way to enter it into the stock ROM manually? I've also been playing around with the official Moto tools over in Windows, but no luck there either.
I really appreciate all the suggestions though!

I'm hitting the exact same problem. I have a Google Fi variant, went to Lineage to try it out, tried to revert to stock, and wireless and radio are not working. I followed the guide at https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265, but accidentally skipped the step to install "Copy Partitions Zip". I've been trying to figure out what that file does, but haven't made much progress. I don't know if it's related or not to stock not working.

I lost all data/wifi/cell service after doing a clean flash of the April update. During the setup phase of the initial flash, I had no 4G, device was failing to acknowledge that I even had a SIM card inserted. Wifi was so intermittent that I couldn't enter my password to restore my Google account to the device. After this I tried out numerous stock flashes of the earlier Pie factory firmwares, LineageOS, HavocOS, none of them having any success..
After getting in a bootloop trying to restore the full backup I made right after unlocking my bootloader, I decided to again do a factory firmware flash of the April update and only restore the backups I made of the EFS and Persist partitions, at the initial boot, that didn't seem to work. I decided to go ahead and proceeded with my normal routine of flashing TWRP and the latest Magisk. Thought maybe a Magisk module could kickstart service. Booting after that, I finally had both Wifi and 4G LTE w/ voLTE on Total Wireless again.
Definitely a pain, especially the full backup I had made turning out to be a waste of time.
Just backup your EFS/Persist partitions. Lenovorola's gross mishandling of the EFS partition on nearly every recent device makes this step nearly vital before doing anything to the phone.

Is there any progress towards a solution on this? I experienced this for the first time while trying to re-flash stock April ROM.

Can the same EFS and Persist partitions interchangeable, as in can I use yours? I've been using the re-flash stock, accept OTAs, re-root/twrp method for months now and this is the first time this has happened. Its only bluetooth capable right now. lol

Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.

hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
Neffy27 said:
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
Click to expand...
Click to collapse
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.

NeoandGeo said:
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
Click to expand...
Click to collapse
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight

JustDJ_From_Da_Swamp said:
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
Click to expand...
Click to collapse
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.

Comby_sk said:
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Click to expand...
Click to collapse
Awesome, I'll try it now. I greatly appreciate that
---------- Post added at 02:16 PM ---------- Previous post was at 01:39 PM ----------
Hey.. umm.. where can I find that new ROM?.. lol I know, it's a shame

I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ?...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help

JustDJ_From_Da_Swamp said:
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
Click to expand...
Click to collapse
Glad you got your problem sorted out. Honestly the best ROM for this device has always been Plain Stock w/ Magisk for root. Everything just seems to work without issues, all of the custom ROMs have the odd issue here and there that really prevents the device from being able to be run trouble free.

same problem on 1900-7 version

XT1900-1 November security patch link request

Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,

You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.

NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.

lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.

I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*

KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.

If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.

Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.

SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!

I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.

That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.

If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.

Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1

No idea why this posted twice.

Thanks!

The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.

39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...

(FIXED) Bootloader Locked but Device Won't Boot

I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.