Database Info

[Q] How Do I Prep My Device For JB Installation?

OK, so the MotoDev team advised me to return my phone to stock before installing JB, which will be pushed to my phone tomorrow morning...
What do I need to insure my system won't crash?
I have an unlocked bootloader, and am rooted. I already did a factory reset on my device. Some system apps are gone though, as I have deleted them (mostly Google stuff though, nothing crucial). Will I be good to go? (And yes, I will save the SBF and post it, no worries, have a Dev Host account and will upload).

In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:

hagforz said:
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
Click to expand...
Click to collapse
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10

galacticservant said:
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
If you want to grab the update package and save it you should prevent it from being deleted. I know that twrp could not install asa14 OTA update when I got it so it was just hanging there in /cache along with md5 (or sha1, I can't remeber) checksum file.
I do not know if there are other ways of saving the update package nor if devs actually need it. But ASA14 got to my bootloader unlocked, gsm modded, rooted stock rom and after booting to recovery it just stayed there, no install happend (I installed it manually) because twrp did not pass the command properly or what ever the reason.
This update is coming from motorola directly, not sprint, right?
Anyway, perhaps someone can give you more accurate details. I personally would flash twrp and see if updated arrives. Because /cache is wiped by the update installer after installation. All automated process. After device boots to recovery it installs the package, wipes caches and reboots, if I am not mistaken.

I believe for the past updates we had the best luck by reverting the recovery back to stock as well. You have missing APKs that you removed so those will very likely be looked for by the update and will fail the update process if missing.
So if all goes well this should be the bare minimum I'd say for getting the update to work:
MAKE A BACKUP, don't want to have a bricked phone yeah? I mean you could have Jelly Bean on it finally... but still bricked...
Revert the recovery to stock if you installed TWRP or ClockworkMod, adb reboot bootloader | fastboot flash recovery recovery.img
Restore any and all apps you deleted from the stock image, either by restoring fully to stock or putting them back manually, wouldn't hurt to do another update check in the play store for them as well.
Temp unroot with OTA Rootkeeper
Download the update, reboot it, do a song and dance, ???, profit.
Now, you might try to restore root asap, it may or may not work, we won't know till we try.... I'm using Superuser 3.1.3 and on their website it claims its for arm devices 2.0-4.1 so maybe it'll work. Your bootloader should still be unlocked I'd imagine, so you can reflash your custom recovery and make a new backup.

Update Rooted Nexus

I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?

ILowry282 said:
I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?
Click to expand...
Click to collapse
Since your post was made today, and the update was released yesterday I'm assuming you are thinking that you will be getting the update over the air? You won't. When you have a custom recovery (TWRP) you won't get OTA's.
But don't be disheartened, not in the LEAST. Unless you've removed or altered the default system apps (you would know if you did) all you have to do is download the update to your phone, boot into TWRP, flash the update, and let the phone reboot.
Due to how the OTA updates are rolled out, even if you had not loaded a custom recovery onto your phone, you might not have had it pushed to you for a couple of weeks.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2523217
From what you have described you are "scenario 2". Proceed directly to step B. Like many people, I was also step B. It is easier than making toast.

So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?

ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
1. If you flash a custom ROM via TWRP it is generally recommended you do a clean wipe beforehand (and before doing that, obviously create a backup). There are cases where you can go straight to flashing without wiping, which is called a dirty flash. Although this is used when you're flashing an updated version of the ROM you're currently running. Following instructions under Section B won't cause you to lose data.
2. You won't lose root because ROMs will generally take this into account. However, if you do happen to lose root, just download and flash SuperSU and you're back on track.
3. Just flash the zip file.

ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
The first part of the reply above is certainly correct, (the rest is also, but I'm just speaking to the first part of it) but I feel it is just going to confuse you.
You did not flash a custom ROM, you flashed a custom RECOVERY. Two different things. When you copy the update onto your phone, in the form that exists in the thread I linked earlier, it is not an entire image. It is an UPDATE to the stock image, which you are already using. As for your concern of losing root, it shouldn't be a concern. As was mentioned in the reply above mentioned, while you are in recovery you can simply just flash SU again.
In fact, I'd be willing to bet the file to flash SU is still on your phone.
As for me personally, I happened to have unlocked the pro version of SU (because why not...it's only $2.50 and I like the app) and just toggled the "survival mode" option. But even if I had not, it would have been a very small thing to loading SU again.
In short, don't worry about losing root. When you first rooted this phone, most of the steps involved were not in rooting the phone, but in unlocking the bootloader. Loading this update has nothing to do with that, so in your case, since you didn't flash a custom ROM (Such as CyanogenMod) and you didn't make any modifications to the system apps...quite literally all you have to do is copy the stuff onto your phone, load into TWRP, fire up the update, and either fire up SU, or have survival mode already enabled, and reboot the phone.
(and no, you don't have to unzip the file pasted in the thread, just copy it directly) The instructions in that thread are really simple, and that's probably giving you a bit of pause, but seriously, it really is that simple in your case, as it was mine.

So I updated but lost root. How do I flash SU?

ILowry282 said:
So I updated but lost root. How do I flash SU?
Click to expand...
Click to collapse
Do you still have custom recovery cwm or twrp? If so download su zip from either of those posts and flash in recovery if not you can flash recovery with adb or flashify and then flash su zip.
Sent from my Nexus 5 using Tapatalk

Worked perfect. Thanks

4.4.3 Download failed

I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5

JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.

robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.

charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota

There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk

Updating while rooted

I want to update to the new 12.1-YOG7DAS2K1 and I haven't found any tutorials or anything that really actually helped so could anyone tell me how I could do it and keep root I tried just going and updating with TRWP but I got an error which I think it because I'm using the latest version of TWRP which I can fix that but I can't find anything saying if I will lose root or stuff like xposed if I update

If I'm not mistaken, the full flashable zip is not released yet, so your best bet is to update it OTA, which will remove root. You can then re-flash TWRP recovery and SuperSU to regain root. I can't comment on Xposed as I don't use it.

I always believed in not taking OTA updates while rooted. I know it's different with cm and o²os and all, but it's just good habits. Wait for a twrp flashable of the update

lucaboox said:
I want to update to the new 12.1-YOG7DAS2K1 and I haven't found any tutorials or anything that really actually helped so could anyone tell me how I could do it and keep root I tried just going and updating with TRWP but I got an error which I think it because I'm using the latest version of TWRP which I can fix that but I can't find anything saying if I will lose root or stuff like xposed if I update
Click to expand...
Click to collapse
Check here the full flashable zip has been available for awhile now. Wipe system and flash ROM + supersu and profit.
http://forum.xda-developers.com/showthread.php?t=2906746
oble said:
If I'm not mistaken, the full flashable zip is not released yet, so your best bet is to update it OTA, which will remove root. You can then re-flash TWRP recovery and SuperSU to regain root. I can't comment on Xposed as I don't use it.
Click to expand...
Click to collapse
OTA will never work on a rooted phone FYI. You need a stock system with CM recovery for it to pass the OTA checks and for it to successfully flash
Sent from my A0001 using Tapatalk

Renosh said:
Check here the full flashable zip has been available for awhile now. Wipe system and flash ROM + supersu and profit.
http://forum.xda-developers.com/showthread.php?t=2906746
OTA will never work on a rooted phone FYI. You need a stock system with CM recovery for it to pass the OTA checks and for it to successfully flash
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Can I just flash it without reseting and keep all my apps and what not or do I have to do a reset? Also this will reset Xposed right?

You can flash this via twrp recovery
cm-12.1-YOG7DAS2K1-bacon-signed.zip
From
http://forum.xda-developers.com/showpost.php?p=63421581&postcount=3
You can backup your apps in titanium backup after flash above ROM you can restore them.
Official cm 13 came up. Aren't you know ? That can also twrp flashable. I get in CyanogenMod website.

I flashed one of them and got it updated no apps reset or anything have everything along with Xposed and Root
https://download.cyanogenmod.org/?device=bacon would the newest nightly be the right thing to do and I don't really know what has changed in CM 13 anything removed that was big?

Update Build W/O a Computer

Ok, let me start by saying that I'm fully capable of updating my phone with a computer, I'm just hoping there is a better way. So far every time I've downloaded a new firmware, update the flash-all.bat and run it, something will fail towards the end of the update and the only way I've been able to successfully update is by using one of those tool kits (forget which one, it's on my computer). I'm not that concerned about all of that with this thread. I'm wondering if there is a way to do it without a PC.
I'm on NMF26O (root, ElementalX, etc) and tried flashing Pure Nexus over the weekend. Since it's based on NMF26V, I kept receiving an error on boot about updating my vendor.img. So I downloaded that firmware, extracted it, and flashed the vendor.img in TWRP. That led to a plethora of other issues that I couldn't resolve by flashing the boot.img, reflashing the rom, ect. Several hours later I ended up flashing the boot.img and vendor.img for NMF26O, restoring my backup, re-installing Elemental, and rooting again.
Since these updates will be coming out every month, and roms will always be based on the latest update, I feel like I'll be pulling out the computer every month, downloading the updates, modifying the flash-all.bat, and running it through the tool, just to be able to update my rom. The first time I forget to update flash-all.bat, I'll lose the 60+ GB's I keep in internal storage. There has to be an easier way. TWRP is capable of flashing images. Has anyone been able to update without using a computer? I don't care if my radio is out dated, or something is mismatched as long as my phone works as intended.
Sent from my Pixel using Tapatalk

Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though

aholeinthewor1d said:
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
Click to expand...
Click to collapse
I'm on NMF26O. What's the difference between it and NMF26U and why would the vendor image from NMF26V work with NMF26U but not NMF26O?
Seems like all you would need is the /system from the rom, the vendor image, and maybe the boot image (or a custom kernel). I think I'm missing something here.
Sent from my Pixel using Tapatalk

If you install PN its based on NMF26V. So unless you are already on that then you would need to flash the ROM, reboot back to recovery, then flash the NMF26V vendor image.

I'll play devil's advocate here... Yeah there is an easier way, use your Pixel stock and take OTA's. Enjoy a phone that always works, with or without a laptop!
I understand my audience and realize this isn't a popular mantra here but I felt exactly like you did with my 6p and vendor images. I got to the point where I sacrifice root now just for my own sanity. My phone works for me, not the other way around.

What I do is side load the full OTA ( which you can get from the same place you get the factory images ). I only use the fastboot boot version of TWRP so that my stock recovery stays in place. Then all you have to do is boot into the stock recovery, adb side load the OTA file and re root. Then you're fully up to date without worries of your data being wiped :laugh:!
( Although if you look in the flash fire thread from Chainfire, he's working on a version that will let rooted pixels flash otas like normal ones :fingers-crossed: )

I think you guys are missing the point. I have no desire to ever be stock, which rules out the possibility for an OTA in any form.
What I'm trying to figure out is exactly what is necessary to make a custom rom (based on the latest OTA), work if flashed over an older build, without first somehow applying the full OTA. Or is it impossible?
On just about every other phone I've owned, we could piecemeal the files needed for minor updates, along with a custom rom. The only time we'd have to flash a full update is for major updates ( 4 to 5 to 6, etc).
Sent from my Pixel using Tapatalk

Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Sent from my Pixel using Tapatalk

joshw0000 said:
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Click to expand...
Click to collapse
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU

aholeinthewor1d said:
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
Click to expand...
Click to collapse
I've done it several times tonight. Went from O to U to V, flashed Pure Nexus, screwed up the rom, restored to O, then O flashed back to U and V.
Just flash it like a rom in TWRP RC1. Make sure you flash TWRP again before rebooting if you want to keep it.
Sent from my Pixel using Tapatalk