Database Info

[Q] "Installation aborted" with 4.4.4 OTA and CWM

I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.

bur2000 said:
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
Click to expand...
Click to collapse
You can find all the stock firmware images here:
http://sbf.droid-developers.org/phone.php?device=14
Flash either with RDS (http://forum.xda-developers.com/showthread.php?t=2637338) or fastboot (http://forum.xda-developers.com/showthread.php?t=2542219)

Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.

bur2000 said:
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
Click to expand...
Click to collapse
You can flash any firmware you want, except the ones for dual sim version (but if you want to be totally safe flash the retail de image). 4.4.4 images aren't available currently, you have simply to restore the stock 4.4.2, flash the stock recovery and take the OTA update.
The ROM you linked is for Moto G dual sim variant (XT1033), flashing it will probably cause a soft brick.

I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
2. How can I flash the rom if the phone keeps doing this?
Any help would be much appreciated. Thank you.

fertchen said:
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
Click to expand...
Click to collapse
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
2. How can I flash the rom if the phone keeps doing this?
Click to expand...
Click to collapse
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.

bur2000 said:
After that no problems.
Click to expand...
Click to collapse
Thank you very much. I will try that when I get home next week. Will be a nice exercise in living without a phone for some time...

bur2000 said:
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
Click to expand...
Click to collapse
Just did the same mistake with unlocked & rooted XT1032. I use TWRP and ended up there after every reboot. What I did is use the File Manager under "Advanced" to delete the .zip under /cache. Alternatively you could just wipe cache/ dalvik cache and the update zip should be gone, phone should reboot normally and after app optimization (if you wiped dalvik cache) everything should be back to normal. The first few seconds I got an error when checking for an update, but it went away after a minute.
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...

I was in the same situation, with bootloader active from cmd:
mfastboot erase cache
or whatever you use

Any improvement?
Hello everyone,
I had the same problem and had to restore a backup.
But can anyone tell us why this happens? Is Google aware of this and is a fix on the way?
I've seen that the update would fix the annoying incompatibility problem with the class 10 SDCards so I'd like to install this update.
I have seen that some of the improvements would also be :
- coloured tiles in the phone dialer
- ability to pause when you record a video
But I can already do that with my phone right now (I'm in 4.4.3 on a Moto G 4G), is this normal ?
Thank you.

suiller said:
I was in the same situation, with bootloader active from cmd:
Click to expand...
Click to collapse
Thank you very much, suiller. This:
fastboot erase cache
did it for me.
gnayug said:
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
Click to expand...
Click to collapse
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?

fertchen said:
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
Click to expand...
Click to collapse
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me. Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
...Help?

gnayug said:
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me.
Click to expand...
Click to collapse
My guess is that there are just too many versions of phones out there and too many different prerequisites (differences in how the phone was rooted, which apps might have been de-installed, which rom/recovery installed etc) that it is extremely hard and laborious to provide a truly foolproof way. That might be different if there was one standardized manual/tutorial on "Hot to root foolproof and OTA proof for the future" and everyone would follow that precisely.
gnayug said:
Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
Click to expand...
Click to collapse
There is a page that lists all the available stock Moto G Roms in different versions. It would be great if there was such a page for the recovery as well.
If there was a person that decided to take care of all these issues for the Moto G on this forum, he or she could maintain a page with direct links to all the tools, roms and recoveries as well as one general (foolproof) and possibly a handful of alternate ways and fixes.
That is a lot of work, particularly dealing with people who are not willing to read more than one sentence in order to get what they want. And certainly it must be frustrating for a "freak" or dev to encounter us newbies on a daily basis. A 101/primer on what boot/recovery/rom etc is would be helpful - and it does even exist in the wiki. It's that many of us don't find it. That could be changed by a very well thought-out and structured sticky post that provides all the necessary links and knowledge but not too much so that a beginner is frightened by 10 pages of instructions.
But I am certain that a person would be willing to do that if this forum allows it (which I assume is the case). Maybe this person has not been identified yet. Or maybe we have just missed it. I know I will not be this person simply because it would take me a lot of time to gather the necessary knowledge for such a position and right now I have other priorities and I usually use my phone once every 10 days or so.
I am aware that as a user I am not entitled to anyone providing this service. At the same time I am pretty sure that there is someone, maybe even within this great community, who would be willing to do it.
By the way, here is how I ultimately fixed the rooted-Moto G-OTA-update-problem: http://forum.xda-developers.com/moto-g/help/how-to-update-rooted-moto-g-t2828857/post54528345

Thank you for the link and everything you wrote! I was actually thinking the same the last few days... If only I was qualified enough or had the time to gather and polish all the information. I realize I shouldn't have written "Freaks". They're hard-working, skilled individuals that provide us with all this amazing software for us to use free of charge. I just wish they'd put some effort into explaining and laying out the basics etc. for all the "newbs" they encounter each day, because what good do their stuff do when nobody knows how to use it? All those devs that put out kernels and ROMs and then make a thread with changelogs and download links WITHOUT actually saying what they contain and why anyone should use them - I'm looking at you.
I'll go try to get my Moto G to 4.4.4 without losing my stuff using your link now, thanks again!:good:

Latest Bootloader / Modem?

I never got around to installing any custom roms after I got my nexus 5 back when it was released. I just stayed on stock. However, when 5.0 came out last week I got sick of waiting for the OTA update so I rooted/unlocked my bootloader, installed TWRP, and got on 5.0.
However, I did not upgrade my bootloader. I cannot seem to find a thread that has all of the old modems/bootloaders like I had when I had my Galaxy SIII.
Right now I have the modem: M8974A-2.0.50.2.21, which I believe is the latest (not entirely sure).
My bootloader is: HHZ11a. I see threads out there where this value is up to d? However, I want to make sure I'm on the latest. Is there a thread that has all of this information in there? Or no? If not, and I'm not on the latest, where can I grab the files to update them. I realize I can flash the modem, but I'll need to fastboot the bootloader which I'm ok with.
I've searched the forums and have had little luck, so a point in the right direction would be appreciated.
Thanks.

All the files you need are in the factory image so download it (it's handy to have in case you want/need to go back to stock) and you can flash the files through fastboot
https://developers.google.com/android/nexus/images

Great, thank you. All updated.

In some real trouble, help please (G4 H810)

Hey, I am not sure if I am posting at the right place or should I create a new thread or not, really sorry if I am doing anything wrong, but I am in some real trouble here. I have At&t g4, it was on h81010g stock firmware version, it was working great and I was loving it but I wanted to update it to android 6, so I followed this guide https://forum.xda-developers.com/att-g4/general/lg-g4-h810-upgrade-to-android-6-0-t3323995 to update my version from 10g to 10o and then finally to android 6, 20o, (by the way its a great guide), everything worked fine but I have no signals, I tried to reset the phone and tried a few other things like hidden menu, airplane mode but nothing works,
I couldn't get the signals and shows a small cross above the signal bars, After that I used the LG UP tool to downgrade it to h81010o but still the same, I think my region don't have the upgrades further than h81010g or whatever the reason, I can't find the H81010g stock firmware anywhere, can anyone please share the original h81010g tot or KDZ file with me,
so I can get my phone back in a working state? a question for senior devs, bro if I can't get a h81010g file, what are my options then, any kind of help will be very much appreciated.
Thanks...

anything ?
@hyelton
 @bovoro
 @warri
 @Nirvana Rules
 @faizalotai
anything please?

jasonwebb11 said:
Hey, I am not sure if I am posting at the right place or should I create a new thread or not, really sorry if I am doing anything wrong, but I am in some real trouble here. I have At&t g4, it was on h81010g stock firmware version, it was working great and I was loving it but I wanted to update it to android 6, so I followed this guide https://forum.xda-developers.com/att-g4/general/lg-g4-h810-upgrade-to-android-6-0-t3323995 to update my version from 10g to 10o and then finally to android 6, 20o, (by the way its a great guide), everything worked fine but I have no signals, I tried to reset the phone and tried a few other things like hidden menu, airplane mode but nothing works,
I couldn't get the signals and shows a small cross above the signal bars, After that I used the LG UP tool to downgrade it to h81010o but still the same, I think my region don't have the upgrades further than h81010g or whatever the reason, I can't find the H81010g stock firmware anywhere, can anyone please share the original h81010g tot or KDZ file with me,
so I can get my phone back in a working state? a question for senior devs, bro if I can't get a h81010g file, what are my options then, any kind of help will be very much appreciated.
Thanks...
Click to expand...
Click to collapse
There's no other firmwares other than one ones I uploaded in my guide other than 21y which I'll upload in a few hours which was recently leaked (which is a shocker ). Also remember you MUST be on AT&T for OTA updates to work so that might explain why you cannot update via the phone.
I can't speak for that guide and not having service as I've never used it, you did perform a factory reset after doing that correct?
Did you attempt to try another SIM card in the device? And did you remove and reinsert the sim?
Sent from my iPhone using Tapatalk

LTE Loss, Unable to Recover w/o Factory Reset - with Several Protections in Place

Greetings,
I've been racking my brain and fighting with this for weeks now, but I'll try and keep this short:
GS3 d2vzw
Unofficial Lineage ROM 14.1 (Nougat 7.1.2) and OctOS-N (also 7.1.2)
With, and without, Xposed Framework/XPrivacyLua
AFWall+ (firewall)
When I go into a cell dead zone, I lose LTE and never get back. I'm always stuck on 3G with a little 'x' in the bottom-right corner of my 3G/Signal icon. However, the little 'x' can go away depending on the AFWall settings (i.e. allowing phone services out, or kernel, etc).
The only way I've been able to get LTE back is to backup the ROM, Factory Reset, and then restore the ROM...and even that doesn't always work. It seems to depend on if I do a Factory Reset or Wipe the device including the data partition. Also, this technique seems to only work when I restore an OCTOS Rom. The LineageOS ROM has NEVER recovered LTE. However, the LineageOS ROM still has Xposed installed.
Online, I found a recommendation to "Reset APNs to Default", clear cache, restart. This also has never worked...plus, I don't know what 'cache' they're talking about. I've tried clearing the Phone cache and/or Dalvik/cache from recovery...neither have worked.
I don't believe the problem is with the SIM or HW as a factory reset has always brought back LTE. I also don't believe Xposed is the culprit as I've had the OCTOS ROM without it. This ROM I can factory reset to get LTE back and restore an OCTOS ROM which will then still have the LTE. LineageOS I have yet to try to see if removing Xposed will have any effect.
I was leaning toward the problem being AFWall+ as I block a TON of stuff. However, when I disable AFWall and restart the phone, LTE still does not come back. It's almost as if the radios are somehow dropping to 3G and then unable to recover w/o factory reset...but I have no idea what "factory reset" is doing.
Any and all help would be appreciated as this is my only phone and constantly factory resetting/restoring is not practical simply because I drive through a dead cell zone.
Thanks!
--C64
UPDATE: I adjusted the firewall settings a bit and was successful in restoring the LineageOS after Factory Reset to /keep/ the LTE. Still doesn't solve the recovery if LTE is lost though.

c64whiz said:
Greetings, I've been racking my brain and fighting with this for weeks now, but I'll try and keep this short:...
Click to expand...
Click to collapse
Just a suggestion...
Do you have the latest Firmware Modem installed as reflected on the following thread?
https://forum.xda-developers.com/showthread.php?t=3735628
The Firmware Modem updates are specific for devices to Update the Modems Only without having to flash the whole Firmware to update them (typically for devices with Unlocked Bootloaders).
Keep in mind that Custom Firmwares doesn't update the Modems and leaves them alone. Modems has to be updated separately by the user.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Non-Odin Flashable?
Ibuprophen said:
Just a suggestion...
Do you have the latest Firmware Modem installed as reflected on the following thread?
https://forum.xda-developers.com/showthread.php?t=3735628
The Firmware Modem updates are specific for devices to Update the Modems Only without having to flash the whole Firmware to update them (typically for devices with Unlocked Bootloaders).
Keep in mind that Custom Firmwares doesn't update the Modems and leaves them alone. Modems has to be updated separately by the user.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thank you! Turns out my modem firmware is from 2013! So yes, I would like to flash the latest modems, but these files all point to ODIN. Does anyone know if /heimdall/ under Linux can be used to do this as well??

c64whiz said:
Thank you! Turns out my modem firmware is from 2013! So yes, I would like to flash the latest modems, but these files all point to ODIN. Does anyone know if /heimdall/ under Linux can be used to do this as well??
Click to expand...
Click to collapse
The ones from that thread are customized with only the Modem Update files.
Those modem updates are only flashed in Odin per the OP instructions.
You don't need to reset, recover, etc... your device stays the way it is with an updated Modem. You just flash it via Odin, it reboots and your all set.
That's my DevDB Thread and I tested all of those Modem files to make sure that they worked.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Ibuprophen said:
The ones from that thread are customized with only the Modem Update files.
Those modem updates are only flashed in Odin per the OP instructions.
You don't need to reset, recover, etc... your device stays the way it is with an updated Modem. You just flash it via Odin, it reboots and your all set.
That's my DevDB Thread and I tested all of those Modem files to make sure that they worked.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Bummer. I don't have a Window box for ODIN. I did extract the .tar and found the NON-HLOS.bin file and some research shows Heimdall can flash those to the modem partition. However, I also found this site: https://forum.xda-developers.com/showthread.php?t=2791801
Which says it will lock my bootloader. Now, granted, the file provided is a full modem+ROM flash which is something I don't want to do. However, since the flash name used "VRUDNE1" is the same as the version number listed on your modem list provided by your link, I thought I'd ask and verify: Will flashing just the modem file affect the bootloader in any way? The last thing I want to do is risk locking my bootloader.
Thank again for all your help.
BTW, I downloaded the full 4.4.2 update for the GS3 and figured I'd look for the "modem file". I found this page that shows there are 2 files, one for the LTE modem and one for the 3G modem. Thoughts?
I just want to be extremely cautious about this since I don't have a Windows box and I don't want to lock my bootloader.
--C64

c64whiz said:
Bummer. I don't have a Window box for ODIN. I did extract the .tar and found the NON-HLOS.bin file and some research shows Heimdall can flash those to the modem partition. However, I also found this site: https://forum.xda-developers.com/showthread.php?t=2791801
Which says it will lock my bootloader. Now, granted, the file provided is a full modem+ROM flash which is something I don't want to do. However, since the flash name used "VRUDNE1" is the same as the version number listed on your modem list provided by your link, I thought I'd ask and verify: Will flashing just the modem file affect the bootloader in any way? The last thing I want to do is risk locking my bootloader.
Thank again for all your help.
BTW, I downloaded the full 4.4.2 update for the GS3 and figured I'd look for the "modem file". I found this page that shows there are 2 files, one for the LTE modem and one for the 3G modem. Thoughts?
I just want to be extremely cautious about this since I don't have a Windows box and I don't want to lock my bootloader.
--C64
Click to expand...
Click to collapse
I have a TWRP flashable ZIP of modem NE1.
Get it here: https://www.dropbox.com/s/i15enyq8wm759z9/d2vzw_MF1_firmware_NE1_modem.zip?dl=0
Flashing this file will NOT do anything to the ROM or Bootloader.

[ROM] ZTE Visible R2 Stock firmware

Here is the stock firmware including the firehose needed to flash it
B10 Firmware
Here
B12 Firmware
Here
ZPI file for ZTE SalesMultiDL tool
Here
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8917.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device

Here is the Stock wallpapers in case anyone wants them
https://www.androidfilehost.com/?fid=1395089523397903558

I just got this device a couple days ago and was hoping I could use PDANet/Foxfi to connect more than one device at a time to wifi hotspot but they've evidently blocked the apps.. Do you have any insight to that?

pegb856 said:
I just got this device a couple days ago and was hoping I could use PDANet/Foxfi to connect more than one device at a time to wifi hotspot but they've evidently blocked the apps.. Do you have any insight to that?
Click to expand...
Click to collapse
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.

deadman96385 said:
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
Click to expand...
Click to collapse
Ok thank you for the reply.

deadman96385 said:
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
Click to expand...
Click to collapse
If you WANT to own this device it's currently $19 out the door on visible.com. No Trade required.
https://slickdeals.net/f/13221781-visible-r2-is-now-19-without-service-or-trade-in-requred

I'm gonna see if I can flash Chinese firmware to unlock the bands

Bowsa2511 said:
I'm gonna see if I can flash Chinese firmware to unlock the bands
Click to expand...
Click to collapse
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).

famewolf said:
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
Click to expand...
Click to collapse
https://imgur.com/yOe0vIx

Your elite google-fu obviously exceeded my own. Please make that sharable if you can....megaupload.nz would hold it and is free.

famewolf said:
Your elite google-fu obviously exceeded my own. Please make that sharable if you can....megaupload.nz would hold it and is free.
Click to expand...
Click to collapse
https://mega.nz/#!aRo0CaBA!nm37c3V11tr2260V23wIxb4yZufD5-_f6gID8i3HjSY
Let me know if it's helpful

DISREGARD. Looks like out of date info.

Any of you able to get fastboot working on it? ADB works, but my fastboot doesn't detect the phone.

Nice looking out, just ordered one.

Using one of the hidden activities app from the play store. There is an option to change from LTE to 2G/3G/4G under one of the phone settings. But calling still did not work with either AT&T or T-Mobile.

famewolf said:
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
Click to expand...
Click to collapse
Just a heads-up: even if you found the files for the A0722, you'd brick your R2 if you managed to flash them. The chassis and screen seem to be the same, but they're completely different specs-wise. Given that the A0722 has a different SoC and an eMMC chip 2-4x larger, I doubt you'd get real far in the flashing process in the first place.

FEGuy said:
Just a heads-up: even if you found the files for the A0722, you'd brick your R2 if you managed to flash them. The chassis and screen seem to be the same, but they're completely different specs-wise. Given that the A0722 has a different SoC and an eMMC chip 2-4x larger, I doubt you'd get real far in the flashing process in the first place.
Click to expand...
Click to collapse
In my case my main goal was to use it and the factory software to learn about mbn files. I've dealt with LG's TOT and KDZ files but not the mbn's. Thanks for giving folks the warning though.

Would it be possible for someone to grab the download URL for whatever OTA update is available for the device? I don't think it's anything major but I'd like to poke around at it; the firmware uploaded here seems to be from launch.

FEGuy said:
Would it be possible for someone to grab the download URL for whatever OTA update is available for the device? I don't think it's anything major but I'd like to poke around at it; the firmware uploaded here seems to be from launch.
Click to expand...
Click to collapse
I've got a logcat recorder queued up to be installed and will try to grab an url by starting the download. If that fails there are a couple of alternatives....someone who has DONE the upgrade could rip the rom and make it available if @deadman96385 can point to some instructions on how to rip the rom.
Also you can always let your own upgrade occur because he's already provided the original software and QFIL which would let you restore to original factory and get the update again.
As a last resort I can grab the log from my ROUTER that the phone is connected to and try to get the url that way which I've had to do with SOME devices.

I'll probably end up taking the OTA again anyways as I've been messing around with the firmware from the first post. Honestly, I'd really recommend staying away from flashing it without a good reason. Even when the flasher works, either the logging and/or the flasher hangs and it's close to impossible to tell which without unplugging your phone. If a partial flash leaves you in a state where you can't get to ADB to boot to EDL mode, you'll have to boot into diagnostics mode, use a piece of Chinese software to boot from there back to EDL, and within five seconds or so, close that software and start the flashing process from QFIL before the com port stops responding to requests, leaving you to reboot the phone and start again.
I've been trying to get non-LTE networks and calling working, but it's entirely impossible to tell whether my tweaks are having unintended side effects or if the flashing just crapped out partway through, even when I'm just flashing single partitions.