Stock,unlocked & rooted,updating to 4.3 - Nexus 7 Q&A, Help & Troubleshooting

Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2

steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.

Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help

steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.

i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.

forgot to attach the screenshots

GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app

Related

MOTOACTV ROMs

Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.

[FAQ] for Kit kat and How to prepare for it (All Carriers)

If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.
With the Verizon Kit Kat roll out, and now that there is an ATT Kit Kat soak starting soon, so undoubtedly they and the other carriers will start getting it, I wanted to summarize some of the information found in these two main threads ->
http://forum.xda-developers.com/showthread.php?t=2534060
http://forum.xda-developers.com/showthread.php?t=2525495 (start at the back and work your way front because of some of the fluff from before the OTA hit)
This might make it easier for those Verizon users who haven't received Kit Kat yet, or those of you on other carriers as Kit Kat starts rolling out. These are the most common issues and questions I've seen asked....
You will lose root when you take the KitKat OTA.
There is no way to retain root while upgrading to Kit Kat Updated Root for KitKat released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
If your phone has a LOCKED BootLoader, you will not be able to root KitKit at this time. UPDATED Root for KitKat 4.4 has been released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Note: If you have an unlocked boot loader, or developer edition, root is obtainable. (see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP )
You must be unrooted, reverse the impacts of PwnMyMoto and/or RockMyMoto or you will be stuck in a boot loop when the OTA. (how to fix posted later)
Once on Kit Kat, you can't flash back to past firmware, unless you have an unlocked boot loader. (see the updates section below, and the SlapMyMoto threads)
You must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
there are several options to get back to "stock" without loosing your data. (posted later in this thread), some are more techincal, some are more noob friendly.
If you want to thether "for free", FoxFi doesn't work. Any past hacks that require root wont work, unless your phone has been Rooted update:see the EDITS & UPDATES section at the bottom of this post)
Kit Kat brings some style and status bar changes to be aware of. Like everything being WHITE, no more blue, no data traffic arrows, etc For more info please see -> http://www.androidpolice.com/2013/1...nd-only-shows-connectivity-in-quick-settings/
Note: If you have flashed your phone with another carrier's ROM, or have tried the previously leaked T-Mobile or ATT pre-release roms, these steps may not work!!
Motorola Fastboot, mFastboot, and android SDK fastboot... what's the difference?
When you install the ADB and Platform Tools from the AndroidSDK, you will also get a fastboot.exe. This standard fastboot.exe is compatible with most, if not all, Android devices to flash parts or partitions with. Unfortunately, that standard fastboot is limited on how big of files it can properly flash. In recent android devices, Motorola has surpassed the limits of fastboot, as such they have an "upgraded" or "tweaked" fastboot.
Having two fastboot.exe files, one that comes with the AndroidSDK install, and one from Moto, can get confusing, and presents a challenge. You can't put the Moto one into your PlatoformTools folder with the AndroidSDK one due to the same name. If you overwrite the AndroidSDK one with the Moto one (keeping the same file name of fastboot.exe) it could be overwritten with a future update of the Android SDK. Because of this, some have renamed the Moto fasboot.exe to mfastboot.exe. So if when you see reference to mfastboot.exe, they are talking about the Moto tweaked version of fastboot.exe that has been renamed so as to not overwrite the one included with AndroidSDK. Simple, right??
So, where can you get the Moto Fastboot.exe, or mfastboot.exe?
You can grab the Moto Fastboot.EXE from -> https://www.dropbox.com/s/kyqjzpjgamrepf1/fastboot.exe (Thanks to Cell Zealot) Note: you will want to rename this one before putting in your PlatformTools folder so future updates to the Android SDK doesn't overwrite it. Alternate download -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 Another way to get it is to request the GSM Developer Edition recovery image directly from Motorola (HERE) as they recently added the updated fastboot.exe along with minimal ADB support.
I take no responsibility for any issues, errors, problems, etc. you encounter while attempting to unroot, get back to stock, etc or using these instructions. Please backup your data BEFORE you attempt anything below!!
How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8 users have had issues.
You will need...
To know what version ROM is on your phone before you touch anything. On Phone... App Drawer -> Settings -> About... Make note of the build number.
Motorola Device Drivers -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Adb Drivers, Android Platform Tools from the Android SDK, some good tutorials -> http://forum.xda-developers.com/showthread.php?t=1830108 or see -> http://www.xda-developers.com/android/lightweight-adb-and-fastboot-installer/
Updated Moto fastboot if you will be doing things manually See above!
MicroUSB Cable.
NOTE: the GSM Moto X Developer Edition recovery image available by request from Motorola (HERE) has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need for the Adb Drivers and Android Platform Tools from the Android SDK.
NOTE2: The T-Mobile XT1053 Retail and Moto Maker versions use the same Rom/Recovery Image as the GSM Developer Edition X. The Verizon XT1060 Retail and MotoMaker versions use the same Rom/Recovery Images as the Verizon Developer Edition phones. The the recovery images are available by request directly from Motorola (HERE). Unlockibility of the bootloader is NOT part of the ROM or Recovery Images that we can flash, so flashing the Developer Edition ROM/Recovery images will NOT have an impact on unlocking your bootloader. This tip is just in case you would feel more comfortable downloading the ROM files directly from Motorola, or if sbf.droid-developers.org has problems again.
Then select from one of the following options...
Option 1 The "Moto X Tool Kit"
See -> http://forum.xda-developers.com/showthread.php?t=2477132
It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for yor phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.
Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).
Option 2 Fastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept the KitKat OTA without losing data/apps.
You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.
You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.) See above.
Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)
steps would be... (mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you unziped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and and be ready for the update.
NOTE: to combat a 401 ERROR while doing the update, some users have also had to flash do the following
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings
NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.
Follow this guide -> http://forum.xda-developers.com/showthread.php?t=2446515 using the latest ROM from your carrier. HOWEVER, before as part of STEP 4, while editing the XML file, also remove the line that says...
<step operation="erase" partition="userdata" />
Failure to remove this line will result in your data/apps/settings being erased from your phone.
Option 4... Fully flash your phone using RSDLite
Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.
Follow this guide -> http://forum.xda-developers.com/showthread.php?t=2446515 using the latest ROM from your carrier.
Option 5 Using mFastboot to manually flash your phone's firmware (without wiping data).
This is the same as using option 3, but usese Moto fastboot instead of RSD. This will not erase your data and apps.
You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.
You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.)
Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)
steps would be... (note: mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)
Unplug phone
Power down phone.
Hold Volume Down button and Power button.
After a few seconds release Power, you should be in fastboot menu on phone.
Connect phone to PC.
open command prompt and change to the folder you unziped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready for the update.
Main issues encountered during the Kit Kit upgrade install...
Boot loop while trying to install the update. This is usually caused by having used PwnMyMoto or RockMyMoto to root. Those tools replace the stock recovery which is needed to install the OTA. You must re-install the stock recovery with one of the above options.
Error 252 reported by the "update". Again this is related to having been rooted but not restoring to Stock
Error 401. One of your files still isn't stock. See the NOTE in option 2 above, or see -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315
Some apps haven't been upgraded to be Kit Kat Compatible... Foxfi, HBOGo, and others. You have to wait for the app vendor to update.
Some apps partially work.. WellsFargo app, I can't deposit a check via camera, but rest of app works. Again, we have to wait for the vendor to update it.
Hope this helps!!
EDITs & Updates: Here are a few more things found since the initial posting...
For those running the T-Mobile Pre-Release leak, I just wanted to link to this thread here -> Oficial tmobile KK over tmobile leak It pretty much summarizes the ability of using Option 3 and/or 4 above to flash TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip over the leaked T-Mobile pre-release rom. (Thanks beelzebu)
There are reports of Verizon Moto X (non-developer) users who took the KK 4.4 update yet were able to flash back to the previous 4.2.2 w/camera fix rom. Please see -> [Q] Return to JB from kitkat on Verizon Moto X (locked) for more details.
Be sure to keep up on the [BOUNTY/PLEDGE/NON-DEV VARIANTS] ROOT 4.4 for MOTO X ($325) as there is some rumblings that a root for Non-Developer Edition KitKat 4.4 might be being worked on.
Tethering options for ROOTED KitKat 4.4 (currently limited to unlocked bootloader)... so far there are two....
On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
(per -> http://forum.xda-developers.com/showthread.php?t=2449534 )
See -> Native tether for VZW DE 4.4 <- This works for rooted with locked boot loader too!!
Root for KitKit users who have a locked bootloader has been released. See -> SlapMyMoto 0.5c Beta (4.4 root, RW to system) (thanks Jcase!!)
When I re-downloaded the GSM Moto X Developer Edition KitKat recovery image recently, available by request from Motorola (HERE) I noticed it has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need to download the Adb Drivers and Android Platform Tools from the Android SDK.
If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.
well done sir! hopefully people actually read this because it will clear up a lot of the clog going on in the threads about kit kat. It was getting ridiculous trying to answer the same simple question a dozen times. Good write up.
thread Title changed. (forgot I had to be in advanced mode..)
Thanks, I stole your idea for thread title.
KidJoe said:
Looking at the thread title I wish I would have called it... Some lessons learned while preparing for and taking the kit kat update.
Click to expand...
Click to collapse
change it then ha. you can change your thread title sir.
i would call it something different personally. Like FAQ for Kit kat and How to prepare for it or something. there is a lot more than just lessons learned. This is a answer to all your simple questions thread. Or call it Read This before Asking Any questions about kit kat ota lol
Should help many people
Sent from my XT1058 using Tapatalk
fyi there are reports that you can downgrade to 4.2.2 on a locked bootloader from 4.4. I didn't think you could but i haven't tried but others are saying on another thread that you can
http://forum.xda-developers.com/showthread.php?p=47698477#post47698477
jayboyyyy said:
fyi there are reports that you can downgrade to 4.2.2 on a locked bootloader from 4.4. I didn't think you could but i haven't tried but others are saying on another thread that you can
Click to expand...
Click to collapse
My understanding is...
After taking OTA KK, there is no way (with locked bootloader) to revert to 4.2.2.
If you used T-Mo or ATT leaked pre-release 4.4, it depends on what/how you flashed it. i.e. Full Flash, used RSDLite to flash entire FXZ, or just used fastboot to flash "parts"
I am sure there were other posts discussing it. Just too busy at work right now to search for them.
KidJoe said:
My understanding is...
After taking OTA KK, there is no way (with locked bootloader) to revert to 4.2.2.
If you used T-Mo or ATT leaked pre-release 4.4, it depends on what/how you flashed it. i.e. Full Flash, used RSDLite to flash entire FXZ, or just used fastboot to flash "parts"
I am sure there were other posts discussing it. Just too busy at work right now to search for them.
Click to expand...
Click to collapse
thats what i thought as well but the link i posted in there shows someone saying he was on locked vzw which to my knowledge, they could only have taken the 4.4 ota from verizon, because the tmobile variants out there are not flashable with a locked bootloader.
jayboyyyy said:
thats what i thought as well but the link i posted in there shows someone saying he was on locked vzw which to my knowledge, they could only have taken the 4.4 ota from verizon, because the tmobile variants out there are not flashable with a locked bootloader.
Click to expand...
Click to collapse
So it seems. Weird. And totally not what I remember. But I don't mind being wrong about this one!!
Can I consider option 4: Factory Reset (in settings ) before install kit Kat OTA? (Bootloader locked and no root)
Enviado de meu XT1058 usando Tapatalk
rod.gui said:
Can I consider option 4: Factory Reset (in settings ) before install kit Kat OTA? (Bootloader locked and no root)
Enviado de meu XT1058 usando Tapatalk
Click to expand...
Click to collapse
If you are not rooted, and therefore haven't used any root needing apps to remove or otherwise mess with system files, there is no need to do anything.
KidJoe said:
So it seems. Weird. And totally not what I remember. But I don't mind being wrong about this one!!
Click to expand...
Click to collapse
flip side it seems that we will be able to have root since verizon may be the only carrier that allowed you to downgrade back to 4.2.2 and jcase is putting something together for it. I WILL BE SO STOKED. Verizon does a quick release, and royally screws up hahaha
this post saved me from wiping my phone :3
jayboyyyy said:
flip side it seems that we will be able to have root since verizon may be the only carrier that allowed you to downgrade back to 4.2.2 and jcase is putting something together for it. I WILL BE SO STOKED. Verizon does a quick release, and royally screws up hahaha
Click to expand...
Click to collapse
You do know that VERIZON has nothing to do with the security, boot images, or system files on the device. Though I could care less if people can go back/forth or if jcase releases a root. Also I love to bash Verizon as much as the next but in this instance, well, you seem to be barking up the wrong tree.
jimmydafish said:
You do know that VERIZON has nothing to do with the security, boot images, or system files on the device. Though I could care less if people can go back/forth or if jcase releases a root. Also I love to bash Verizon as much as the next but in this instance, well, you seem to be barking up the wrong tree.
Click to expand...
Click to collapse
ya i have no idea. didn't try to sound like i did. Just assumed since i thought that ATT couldn't go back to 4.2.2 that meant that the carrier must have something to do with it if Verizon's release of 4.4 does allow you to go back to 4.2.2. I used logic not knowledge so I really don't have an idea at all.
Added a few more things to the Initial post.. See.. Edits & Updates...
What if you have an unlocked rooted GSM Developer Edition with TWRP installed? There is an update available, but I can't find a flashable version yet nor a stock ROM or recovery to revert to so I can accept the OTA.
KidJoe said:
Added a few more things to the Initial post.. See.. Edits & Updates...
Click to expand...
Click to collapse
Non developer edition on 4.4 now has root
And it is possible to downgrade to 4.2.2. I've done it multiple times already when testing.
Added a couple updates to the OP
jayboyyyy said:
ya i have no idea. didn't try to sound like i did. Just assumed since i thought that ATT couldn't go back to 4.2.2 that meant that the carrier must have something to do with it if Verizon's release of 4.4 does allow you to go back to 4.2.2. I used logic not knowledge so I really don't have an idea at all.
Click to expand...
Click to collapse
AFAIK, u can downgrade the ATT phone back to 4.2.2, but the post-camera ota one.
robsw said:
What if you have an unlocked rooted GSM Developer Edition with TWRP installed? There is an update available, but I can't find a flashable version yet nor a stock ROM or recovery to revert to so I can accept the OTA.
Click to expand...
Click to collapse
The GSM DE uses the Retail (TMO) ROM.

[Q] I need help with the latest OTA

Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Could someone help me? It's really just the constant "You have an update" that is bugging me. I don't think anything fun happens in this latest OTA. Hopefully this is the last OTA for me as I want the predicted new Nexus come December!! And it would be great to get a Nexus phone I can actually get OTA updates for without issue!!
I haven't backed my data up in a while, I probably should do that too. (Also, regaining root after a flash, anyone have a reliable method for that? And for tethering on T-Mobile.)
thehyecircus said:
Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Click to expand...
Click to collapse
In case:
a. the bootloader is unlocked and you can start Nexus 4/7 in fastboot mode
b. N4/7 is connected to a PC
c. you can get response from N4/7 with a command in a Dosbox: fastboot devices
You could flash the update manually.
Download the required factory image and the Nexus Root Toolkit (NRT) of Wugfresh.
Install NRT and extract the required factory image in a directory of your choice.
In that directory you need the files: fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll
Copy those files from the NRT.
From the extracted factory image you need the required zip file extracted from the factory image.
Example Nexus 4: image-occam-ktu84p.zip
Connect the phone to USB. Use NRT to put the phone in fastboot mode.
Open the above directory in a dosbox as administrator.
Type the required command to update.
For N4: fastboot update image-occam-ktu8p.zip
Remark 1.
After that root is gone. Reroot with the NRT of wugfresh.
Remark 2, flashing the radio.
When you extract the factory image for N4 there is also an update image for the radio.
You can flash the N4 with: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
But on my N4 the LTE tricks does not work. For LTE you need an older version of the radio image.
Remark 3.
I used this manually method to avoid the hassle of backup and restore.

[Q] cannot update to 5.0. File mismatch

OK I'm trying to update to 5.0 on my Nexus 7. I have the OTA file on both my PC and my Tablet. I'm rooted and unlocked. I'm using TWRP and Wug's
When I try to flash the file it gives me this message before bombing out
Code:
Package expects build fingerprint of google/nakasi/grouper:4.4.4/KTU84P/1227136:user/release-keys or google.nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper/grouper:4.4.4/KTU84P/eng.dees_troy.20141028.111642:eng/test-keys
How do I fix this so I can get the OTA flashed. I don't care about losing root because I can use Wug's to get it back.
Im getting the same :S
seems to be complaining about your custom recovery (TWRP?) note the "dees_troy" string in the message.
if you have an unlocked bootloader, you could flash the stock recovery from KTU84P* into your recovery partition, and then take the OTA**. After that, just use fastboot to flash your custom recovery back into place.
cheers
* assuming you were on rooted-KTU84P to begin with.
** attempting to run an OTA on a modified ROM generally only works correctly on very lightly rooted stock, and sometimes not even then. If you have removed stock (system) apps, diddled with the stock frameworks, or installed something that replaced a system shared library (.so), it is pretty unlikely that the OTA will succeed. Take full backups before you start.

Manual OTA Update process step-by-step (Stock/Rooted/Xposed)

For stock rooted/TWRP users, this is a step-by-step process of manually updating your Moto involving flashing stock firmware, updating, and restoring TWRP, root, and apps afterwards.
Benefits:
**It's really simple- once you get familiar with this process, you can do it fairly quickly.
**Take the time to read through and get everything set up and you'll be set for future updates.
**No begging the internet for flashable zips.
Preface:
So my situation is i'm running stock, bootloader unlocked, rooted, and xposed on my US XT1540 2GB Moto G. I went through the process this morning of updating to the new 23.46.4 update. Thought I'd share what I did for anyone out there wanting to update with questions ; hopefully some can be answered here. I'm familiar with flashing firmware files from my previous Moto X's '13 & '14 so trust me it's not a big deal to flash back stock firmware to update. This process should be applicable to any variant of the Moto G and and to any future updates as well, not just the one mentioned here as of 09/19/15. Just be mindful of your phone's version and use the appropriate firmware.
1) BACKUP
First, make sure everything worth keeping is on your microSD. Flashing stock firmware will wipe your phones internal memory so pictures, music, downloads, SMS, etc need to migrate. Also make sure you have SuperSU and Xposed on your microSD for re-installation. This might be obvious for some and you might have everything going to your microSD (sdcard1, EXTsdcard) already, but one thing you might miss is Titanium Backup...
Save apps in Titanium to microSD: Menu>Preferences>Backup folder location>Click to change>Ext. SD card>Create a new folder>Use current folder
Nandroid in TWRP to microSD: toward the bottom click on "Storage: Internal storage" and choose "Micro SDcard"
If you're super smart, after making that backup you'll copy that to your pc.
2) DOWNLOADS
Get the most recent firmware for your device from lost101's firmware thread (thank him threads like this are so helpful)- http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download and install the drivers for you phone, I believe the generic android driver will work but you can also get them from Motorola Device Manager: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download mini-sdk.zip, attached to the the bottom of this post. Useful light weight sdk containing adb & fastboot which should cover all your flashing needs. If you're not developing apps, full blown android sdk is bloatware
3) SETTING UP ADB/FASTBOOT
Enable USB debugging in Developer options
Extract mini-sdk.zip to a folder. Extract and add the contents of your firmware to that folder.
Open a cmd prompt on the mini-sdk folder (shift + right click, "Open Command Window Here")
Let's verify that adb sees the device:
Code:
adb devices
Should see "XXserial#XX device". If you get "offline", be sure to check your phone for the adb authorization dialog.
We're ready to flash firmware so reboot into fastboot:
Code:
adb reboot bootloader
4) STOCK FIRMWARE INSTALLATION
Once phone is in fastboot, enter the following commands in the cmd prompt (open on the mini-sdk folder containing the firmware files) one at a time. Let the current flash command finish before entering the next, especially at the img_sparsechunck steps because they take a 10-15 sec each. Also make sure all of the filenames match what you have; substitute accordingly.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
5) UPDATE
When you reboot, if you don't get prompted for update check for it- About phone>System updates
Download & install update
When update is finished and phone boots back up, enable Android debugging in developer options.
6) FLASH BACK TWRP/ROOT/XPOSED
Place TWRP img file in mini-sdk folder. Boot back into fastboot and flash TWRP.
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-osprey-2.8.7-test1.img
Vol up/down in bootloader to boot recovery.
Once in recovery flash Supersu & xposed (optional of course) from your microSD and reboot.
Install Titanium from play store, go back into preferences and point to backup folder on the microSD and restore apps.
When xposed and modules are reinstalled through Titanium, you will need to reboot to enable. After that you'll need to tweak your preferences in system options like notifications or display, but any settings in modules (like gravity box) will be restored as long as you backed up app+data in TB. Easier than a custom rom clean flash in that aspect.
So that's it, with that you should be back up and running. Let me know if I missed some steps or if you have questions about the process.
*****
BTW, Installing xposed from scratch for those confused on what files to do what with: http://forum.xda-developers.com/show....php?t=3034811
Flash this one in recovery: xposed-v74-sdk22-arm.zip (or most current)
Install this apk after you reboot: XposedInstaller_3.0_alpha4.apk (or most current)
Please Delete
agleroy said:
Thanks for the guide. Still gonna wait for a flashable zip though.
Click to expand...
Click to collapse
You're better than that. Trying to empower you here...
Please Delete
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
a.cid said:
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
Click to expand...
Click to collapse
I took all the color out and tweaked it a bit. I was using the dark theme and everything looked pretty good, but when I switched to the light theme... yeah annoying.
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Why does every single guide say to erase the userdata partition??? This is totally unnecessary. Instead, boot into twrp and wipe your userdata. The difference is in your internal storage. If you follow the guide you wipe your internal storage in the very last command. My way, you just do a factory reset on the data partition which doesn't wipe the storage
Also, flashing stock recovery is an unnecessary step when it's being immediately replaced by twrp again.
Selmak said:
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
This isn't a custom rom...it's the official motorola firmware update
Thanks for this guide , it's good to know, but I would have to wait for a flasheable UPDATE.zip because my phone's configuration (XT1543, dual sim, 16gb storage, 1gb ram) doesn't have a stock firmware download link in the main thread... and also I don't want to reinstall my apps , haha.
If it works like the other 2 generations of moto g, and at least with the first moto x (all from my personal experience) just skip the erase userdata part and you'll keep your personnal data.
Ota update will go smoothly, no need to restore anything afterwards except root and recovery, indeed.
A backup is always a good thing, sure just in case, but i never used mine on all the ota's I installed on those 3 phones (moto g 2013 16gb, moto g 2014 and moto x 2013)
I don't own a moto g 2015 but my gf does, a 16gb/2gb ram one, she just got it so she installed the update before rooting. If nobody tries it before I'll try it with the next update .
cannot access filehost to get xt1541 5.1.1 any alternative link?
after I updated to 6.0 my computer is not recognising the device? any solutions?
Please add "fastboot flash system system.img_sparsechunk.6" to the top post. This could prevent idiots from sitting in a boot loop for an hour, while they try furiously to find a way out, an error in the download, revert to a previous firmware... Yeah, that was stressful.
Is this the same for the XT1548 virgin mobile 1G of ram and 8G of memory. I understand that it's probably not the same file I just don't really want to wait for the flashable .Zip. But I also don't want to mess up my only device as of now.
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
csumanth16 said:
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
Click to expand...
Click to collapse
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
acejavelin said:
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
Click to expand...
Click to collapse
MrTooPhone said:
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
Click to expand...
Click to collapse
No... If your rooted the /boot partition has been modified.
acejavelin said:
No... If your rooted the /boot partition has been modified.
Click to expand...
Click to collapse
And does it remain notably changed even after going through a full unroot via SuperSU?
MrTooPhone said:
And does it remain notably changed even after going through a full unroot via SuperSU?
Click to expand...
Click to collapse
No, doing a full unroot will return the original /boot partition, but be aware this will not undo any changes you made to /system with root access (such as debloating or Xposed modules), and even if you undo those changes, the Android system has already marked the /system partition as tampered so a check will fail.

Categories

Resources