[Q] Nexus 4 can't update to 4.4.3 OTA - Nexus 4 Q&A, Help & Troubleshooting

I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.

Hey,
Download the stock nexus 4 factory image and flash only the system image through fastboot. This will revert your system partition to stock and it will allow the installation of the ota to continue without any loss of user data. You can wait for the next update prompt or you can just download the ota from the ota thread and flash it yourself through TWRP.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)

ninjames said:
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Click to expand...
Click to collapse
The update process usually goes through even if you have TWRP.
You can try flashing the stock recovery through fastboot.

Which is the stock Nexus 4 factory image? You mean what it launched with, or do you mean the factor 4.4.2 image since that's what I'm on? Also I'm not sure how to flash through fastboot at this point. Will that remove my custom loader or just remove my root?

You can get the latest factory image from here https://developers.google.com/android/nexus/images
Flashing only the recovery will not remove root. It'll only replace the custom recovery (loader).
Sent from my Nexus 4
---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------
You can follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Flash only the recovery (refer section D, sl no.12 in the above guide)
Sent from my Nexus 4

I don't believe the reason for your OTA failure is a custom recovery, it is most likely a modification to the system partition. You should extract the system partition image from the factory image and flash that through fastboot, which will remove your root but you can get that back by flashing the SuperSU zip. Then after restoring back to a stock /system partition, take your OTA like normal.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)

I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.

ninjames said:
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
Click to expand...
Click to collapse
So, have you got your adb and fastbooot drivers set up?
Sent from my Nexus 4

I think so, yeah. Sorry for the delay in my posting but I'd really like to get this figured out in advance of 5.0 so I can, you know, use it.

So I mean, I'm willing to wipe everything, go back to stock, whatever I need to do to set myself up for getting all the OTAs all the way to 5.0. I just need a little bit of help with that ... I backed up all my stuff, so.

Why don't you just go ahead and flash android lollipop? Since you've already backed up all your data, you can start afresh.
1. Download the factory image from Google's developer site.
2. Extract the contents to the folder android/SDK/platform tools.
3. Connect your phone via USB, boot into bootloader and check if it is recognized by using a command prompt and using command fastboot devices, it should return a value.
4. Run the file flash-all.bat which you can find from the extract.
5. It'll take care of the rest and you'll be good to go.
But it'll wipe all data and bring it to an out of the box state.
Sent from my Nexus 4

Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?

ninjames said:
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZK6hYVuKNlw - This one works perfect just replace the file he tells you with
https://dl.google.com/dl/android/aosp/occam-lrx21t-factory-51cee750.tgz < Factory 5.0
Hope this helps
Hit The Thanks if it did

I couldn't really figure out that video .. he was talking about installing APKs and stuff and I didn't know which file from the factory image I was supposed to use? So I extracted it into a directory with the fastboot stuff as per another guide, hit flash all and it said it all worked ... and it did! So ya'll got me started and I stumbled my way to the finish. THANKS SO MUCH!

Related

[Q] Long time no Flash :D

Hey guys,
Its been a very long time since I flashed a rom on my N7. I was busy with the damn uni but now that summer is here I can play with my N7
Let me make this quick, I have unlocked the N7 using the tool kit long time ago and Im not sure if it still exists on my PC
Im currently running - CM10 4.1.2
Modle - GT-I9000
-Bootloader-
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
UNLOCKED
Recovery - i think CMW
Now I want to update to 4.2.2
Can I just flash a ROM with 4.2.2 or I have to do something with bootloader?
And btw just after going to the bootloader today which I didn't see long time ago the N7 didn't boot when I choose start then I held the power button till it rest and it worked but now a random reboot occurred :|
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Westervoort said:
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Click to expand...
Click to collapse
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
mr.dj26 said:
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
Click to expand...
Click to collapse
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Westervoort said:
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Click to expand...
Click to collapse
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
mr.dj26 said:
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
Click to expand...
Click to collapse
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
eddiehk6 said:
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
Click to expand...
Click to collapse
okay m8
thank you all for being very helpful ^^
Great im on 4.18
now ill get in to recovery and erase every thing then ill flash a new recovery and a new rom

KRT16O (KitKat 4.4) discussion/resources thread

Code:
KRT16O Factory Image available in Downloads section (below)
KRT16O OTA (flo/WiFi) available in Downloads section (below)
As first mentioned by mandrsn1 in this post KRT16O "KitKat" is rolling out now.
I did not want to hijack that thread, but wanted to have a simple continuously updated first post that summarizes experiences and consolidates resources like OTA URLs, Factory Image flashing, etc.
You will soon be seeing comments from folks about how KRT16O affects the remaining Multi-touch and Random freeze/reboot issues on google product forums:
Google Nexus 7 product forum
KRT16O touchscreen experiences (near the end of thread)
KRT16O touchscreen experiences (2nd thread)
Mixed improvement with WiFi turned on and Bluetooth keyboards
pil-gss wakelock issue appears fixed
If you need to refer to the old JSS15R thread, it is here.
Initial impressions
Magnetic smart wake when wifi lost or deep sleeps appears to be fixed
Fix is in 4.01 bootloader - not necessary to flash 4.4 KitKat ROM (thx meekrawb)
Some bluetooth keyboard improvements
GPS/pil-gss wakelock issues appears to be fixed
New touchscreen software.
Mixed results, will likely depend on screen, some fixed, some not, improvement from JSS15R
ghost touches with aligned fingers mostly gone
stuck touches seem to be gone or greatly reduced
may still have missed touches
may still have slight jitters with aligned finger dragging
Does NOT include GEL (Google Experience Launcher)
install extracted N5 GEL and new Google Search if you want the new experience (thx jxr94)
use Nova Launcher if you want transparent status bars
Root can be installed in the same ways as 4.3
If you use NRT (Nexus Root Toolkit) follow this procedure (thx ruggie0)
Logistics (only for people trying to downgrade or mix/match rom/kernels)
You cannot "dirty" flash from 4.4 rom/kernel back to 4.3 rom/kernel, you'll need to wipe data/factory reset
4.3 kernels will not boot 4.4 rom
New FLO-04.01 bootloader.
New boot animation, sounds, icons.
New Easter Egg (thx magnumlove)
settings->about tablet->android version (rapidly tap 4 times)
Tap "K" a few times to make it spin, then see the final prize
New ART (Android Run Time) replacement for Dalvik VM
Enable using settings->developer options->select runtime
Apps should be odexed (stock is odexed)
First boot will take a while (possibly 15+ minutes)
New cloud/network print options
The new tap and pay setting only shows up if you already have NFC enabled. (thx albundy2010)
To get tap and pay working you need to get the N5 version of Wallet (thx ruggie0)
Quick benchmark1, benchmark2 of 4.4 and stock Dalvik (thx Vanillalite)
Quick benchmark1, benchmark2 of 4.4 and ART (thx Vanillalite)
Change summary:
JSS15R(4.3_r2.3)->KRT16O(4.4_r1.1) AOSP - TBD
Bootloader version: FLO-04.01
Android version: 4.4
Build/ROM version: KRT16O
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
Mini guides:
adb sideload (install OTA using stock recovery, no need to unlock, preserves user data)
flashing factory images (factory image restore, must be unlocked, option to preserve or wipe user data)
restore stock recovery (if you've installed custom recovery and want to go back to stock)
installing OTA-compatible root/SuperSU (will install SuperSU and fix so that it works with OTAs)
entering safe mode, bootloader, stock recovery (button press sequence can be tricky for fallen android)
Universal ADB drivers (use these if you have trouble with adb recognizing device)
Downloads:
KRT16O
KRT16O Factory Image - flo/WiFi (thanks Zaphodspeaks)
KRT16O Factory Image - deb/LTE (thanks Zaphodspeaks)
Source: pure stock
Format: flash in fastboot/bootloader
Guide: flashing factory images
Caveats:
requires unlocked bootloader
options to wipe or preserve user data
JSS15R->KRT16O OTA - flo/WiFi (thanks kenned88)
Source: pure stock
Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM
Guide: adb sideload
Caveats:
MUST be running unmodified JSS15R
does NOT require unlocked bootloader
if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.
if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery
preserves user data
KRT16O repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so will not work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
Stock kernel/recovery (unzip and flash via fastboot/bootloader)
fastboot flash boot boot.img
fastboot flash recovery recovery.img​
flo/WiFi
stock JWR66N kernel
stock JSS15J kernel
stock JSS15J recovery
stock JSS15Q kernel
stock JSS15Q recovery
stock JSS15R kernel
stock JSS15R recovery
stock KRT16O kernel
stock KRT16O recovery
deb/LTE
stock KRT16O kernel
stock KRT16O recovery
Bootloader - flo/deb (unzip and flash via fastboot/bootloader)
fastboot flash bootloader [filename]​
Bootloader v3.14
Bootloader v3.15
Bootloader v4.01
Root/SuperSU
UPDATE-SuperSU-v1.75.zip - install in TWRP or CWM for root (recommended for 4.4)
UPDATE-SuperSU-v1.55.zip - install in TWRP or CWM for root
Custom Recovery (unzip and flash via fastboot/bootloader)
fastboot flash recovery twrp.img​
TWRP 2.6.3.1 (recommended for 4.4)
Stock missing/modified JSS15R files
flo/WiFi
update-JSS15R-debuggerd.zip
update-JSS15R-thermald.zip
update-JSS15R-audio.a2dp.default.so.zip
Very Nice! I appreciate you taking the time to put this together and explaining things in detail as always! I now see why Nexus was always the way to go!
I installed this using the nexus root toolkit and it was successful. Appears TWRP is still installed as it used TWRP to install the zip. Will continue to do things to see what works and what doesn't.
Edit - Shutdown and chose to boot to recovery mode, got an android and red exclamation mark. Trying to see if I can reinstall Twrp now.
Finally! Thanks:good:
sfetaz said:
I installed this using the nexus root toolkit and it was successful. Appears TWRP is still installed as it used TWRP to install the zip. Will continue to do things to see what works and what doesn't.
Edit - Shutdown and chose to boot to recovery mode, got an android and red exclamation mark. Trying to see if I can reinstall Twrp now.
Click to expand...
Click to collapse
If you install the SuperSU update.zip immediately (prior to reboot) after you install the KRT160 update.zip, you will preserve root and preserve TWRP.
Initial impressions
New FLO-04.01 bootloader.
New boot animation.
New touchscreen software.
Change summary:
Bootloader version: FLO-04.01
Android version: 4.4
Build version: KRT160
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
The new tap and pay setting only shows up if you already have NFC enabled.
Still downloading..
Sent from my Nexus 7 using xda app-developers app
Added link to TWRP/CWM flashable KRT160 ROM (does not require you to be on stock)
KRT160 repackaged TWRP/CWM-flashable (thanks scrosler)
Source: slightly modified stock - Format: flash in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so will not work with future OTAs
this is rooted with init.d support
odexed and deodexed versions
preserves user data
Does anybody else get stuck on the boot animation when enabling ART?
touch is NOT fiexd!
It does boot with art enabled.
Does boor-ts-10 stil woks if enabled again ?
iPWNtehNOOB said:
Does anybody else get stuck on the boot animation when enabling ART?
Click to expand...
Click to collapse
Are you deodexed or running stock odexed?
im on supersu 1.69...
should i have to reflash to 1.55 as noted? or i cab simply reflash 1.69 after kitkat?
juuz wanna be certain
oTeMpLo said:
touch is NOT fiexd!
Click to expand...
Click to collapse
There is new touchscreen software included with this release.
Time will tell how it affects the various screens out there.
On the unit I'm testing on, the ghost touches when aligning fingers are pretty much gone. However there are still missed touches and slight jitter when sliding with fingers aligned. As with previous releases, best to let it settle in. Some problem might go away or other problems might show up.
lomonic said:
im on supersu 1.69...
should i have to reflash to 1.55 as noted? or i cab simply reflash 1.69 after kitkat?
juuz wanna be certain
Click to expand...
Click to collapse
1.69 should be fine. 1.55 works fine also. Only 1.51 and earlier have issues. There was a 1.6x release that had a placeholder update.zip from the author, but that is probably fixed by now.
thx sfhub for all that you've done.
system installed and is now rebooting. optimizing apps screen now.
I have also booted with ts-unlock prior to install... lets see how the new touch software works
oTeMpLo said:
touch is NOT fiexd!
It does boot with art enabled.
Does boor-ts-10 stil woks if enabled again ?
Click to expand...
Click to collapse
I've heard it could take a while for the initial boot when switching to ART
Sent from my Nexus 7 using Tapatalk 4
sfhub said:
Are you deodexed or running stock odexed?
Click to expand...
Click to collapse
Completely stock odexed.
Added KRT16O stock recovery/kernel to first post (unzip and flash with fastboot)
stock KRT160 kernel
stock KRT160 recovery
My update fails becaus audio_effects.conf has been modified. Could someone please send me the audo_effects.conf file from stock 4.3 please?

[Q] What to do for gaining Root on 5.0?

Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
amangupta53 said:
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
Click to expand...
Click to collapse
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks Ged.
Seems like I missed CF-Auto Root Method in my list. But I guess it's essentially the automated format of option 1 I listed above. I've already switched to SlimROM 0.8 F2FS which included the M-Kernel and thus easy to root. (A friend pointed it out to me, I took the plunge for F2FS)
Thanks again for the detailed solution. I'm sure it'll be useful for anyone looking to root Stock Lollipop with Stock Kernel.
Cheers!

[REF][How To] Return to STOCK Recovery (IF rooted) and sideload OTA

By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.
Good work KidJoe :laugh::good:
I guess this will be more relevant as Soaks start heading out for the 2013 X...
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
there any way to make a dump the stock recovery in Lollipop, without the need root?
ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.
Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.
upload the stock recovery lollipop please!!!!
Good work, love your detailed explanations always .

[HELP]: XT1644 Keeps Rebooting to TWRP After Moto Security Update

Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
You messed up your rom by installing official update on custom kernel. Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
strongst said:
Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
Click to expand...
Click to collapse
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
mel2000 said:
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
Click to expand...
Click to collapse
You can also flash the latest available for your device with June security patch. After that you can root again with ex kernel if you want https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Make sure to mount storage within twrp first and save your internal memory before flashing stock rom!
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
Click to expand...
Click to collapse
This 100%. Boot into bootloader and choose start from there. I ran into the same issue last night whilst trying to update my XT1644 and figure this out through trial and error. Once I got it back up though, flashing many stock recoveries that I found online couldn't get the update to work either. It would error out a few seconds after booting into the stock recovery and starting the update. I finally resigned to re-flashing a stock image of marshmallow and updating it all again from there. I wanted to pull the stock recovery before I replaced it with TWRP again but I couldn't find a way to do that. Any method I found required having root access already, and of course I can't get root access without flashing a custom recovery first.
echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally.[/url]
Click to expand...
Click to collapse
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
mel2000 said:
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
Click to expand...
Click to collapse
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
strongst said:
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
Click to expand...
Click to collapse
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
mel2000 said:
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
Click to expand...
Click to collapse
You need to flash twrp after you flashed the stock rom cause the stock rom flash the stock recovery. Copy the whole internal memory, better to save everything when you don't know exactly what you need
Restore the whole internal memory isn't good, just restore what's missing if you recognize it. Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble. Make backup of your apps with titanium backup instead.
Just to clarify - are you on the Amazon software channel (amz) or do you have the Amazon Prime edition of the XT1644 (with the ads on the lockscreen)? I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
EDIT - seen a couple of users reporting they've received it on the retus channel, so maybe more widespread to US users, maybe to include the Verizon emergency calling patch that the G5 Plus got too?
tmp000 said:
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
Click to expand...
Click to collapse
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
mel2000 said:
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
Click to expand...
Click to collapse
Sorry, I'm not an expert, so I can't say much about precautions. What I will do is tell you what I did to get my phone to its current state now is:
Backup my data
After failing to apply the NPJ25.93-14.5 update many times through a bunch of different stock recoveries that I found online (including versions extracted from full stock ROMs), I found a way to downgrade back to the stock ROM of Marshmallow for the XT1644. I applied all the OTA updates, all the way to NPJ25.93-14.5.
At this point, I flashed TWRP recovery again. At the same time, right after running the command to flash TWRP with fastboot, I also flashed logo.bin to get rid of that unlocked bootloader message. I then booted into TWRP and then backed up the system and boot partition as it was (so stock kernel and no root).
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
After that, I rebooted into system and everything booted up just fine. I had root access and all of my data was intact. Your steps 2 and 3 would be:
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot. DO NOT WIPE INTERNAL STORAGE
Then continue on with step 4 from above. And of course, I can't emphasize enough to back up your data. Not just through TWRP, but any photos, etc that you can copy onto your computer first. I'll PM you a link to my backup.
strongst said:
Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble.
Click to expand...
Click to collapse
Thanks for the advice. However, I'm having trouble determining exactly what I need to backup before the firmware flash.
Which folders from the Root dir of internal memory need to be saved?
Do I need to save the SDCARD directory?
Can I use TWRP to restore individual apps within the Nandroid backup instead of the whole archive?
Just trying to be extra careful to preempt things from going sideways. Thanks.
echo92 said:
I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
Click to expand...
Click to collapse
I have the retail version of xt1644 and hope that NPJ25.93-14.5 is intended for or compatible with that.
tmp000 said:
I'm ready to do the NPJ25.93-14..5 update. For clarity, I reordered your steps for the update:
Backup my data
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot.DO NOT WIPE INTERNAL STORAGE
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
Click to expand...
Click to collapse
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
mel2000 said:
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
Click to expand...
Click to collapse
Yes, wipe then restore the backup. Sorry for the terrible instructions with missing steps.
mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
DgnrtnX said:
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
Click to expand...
Click to collapse
Thank you for your reply DgnrtnX. It matches the successful solution I received from exho92 on 09/01/17. The only issue is that I need to boot via that method each time. I no longer boot directly into my system. However I plan to update to NPJ25.93-14.5 shortly so I'm hoping the reboot issue will go away if that upgrade goes well.
USB debugging and OEM unlock were already enabled and remain so.

Categories

Resources