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

How to update with TWRP

Hi,
Basically I'm trying to update to lollipop via OTA so I dont lose all my data, but whenever I try and install the update, my phone reboots into TWRP, but then it just goes to the main menu and doesn't update anything.
Just wondering how I should update? Do I have to install the stock recovery? Or will that make me lose my data too?
Cheers,
Jack

I don't think it's a very good idea to update ota when your phone is rooted. I don't think it will update either because you don't have the stock recovery.
What I did personally... I backed up my 4.4 ROM and followed the instructions on bixie's stock ROM. I didn't delete my internal storage and everything carried over.
If you don't have the latest twrp. You can either download flashify from the market or you can use adb/fast boot.
Sent from my Nexus 5 using XDA Free mobile app

So I used TWRP to install that rom but lost my root in the process. Any idea's what I screwed up?
I made sure to backup using TWRP before starting.

Root is removed as the OTA removes it, just root again (if you read any of the guide threads on here you'd know this)

OTA updates when rooted?

How is it with the Pixel 2, when I am rooted and running a custom kernel but still have stock recovery, can I update using OTA or do I still need to do this manually?

xda890 said:
How is it with the Pixel 2, when I am rooted and running a custom kernel but still have stock recovery, can I update using OTA or do I still need to do this manually?
Click to expand...
Click to collapse
Personally, I find it easiest to just download the full factory image and apply it without the wipe data (-w). Then do my normal tweaks. You can always download the ota and manually sideload it but I found it more flaky and do not want to mess around and have to do modifications/fixes to get it to install, only to end up going the factory image route in the end. IMHO

Aaahh, sounds like a good way to do it.. Didn't know I could disable wiping when flashing full ROM but now I know.. Thx.. ?

I just used the ota img and sideloaded with adb was super easy then pulled the boot.img and used magisk to repack ang get root on .25 update.

Ok, but I am modifying the system partition so I guess full ROM is the best way... ?
Sent from my Nexus 7 using Tapatalk