Related
Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
You're not alone. Several threads on this in general forum and Q&A. Consensus so far is hang tight and the update should resurface.
Sent from my Nexus 6 using XDA Free mobile app
Factory image is still on Google website. Grab it there.
bluh5d said:
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
Click to expand...
Click to collapse
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
If I manually flash the image will it change where my future otas come from ? Like doesnt a motorola nexus 6 updates come from a different server than a google play nexus 6 ?
Same thing for me, except I was waiting to be able to charge up my phone before installing. By the time I got to a charger it was gone. I'll probably just wait for it to resurface.
Same same here. Fully stock. Is the common theme for people experiencing this that they are on VZW? I am. Tmo bought phone with VZW sim.
Fyi, rebooting and charging havent helped.
I know i can manually update, but I'm hoping to confirm that the OTA process still works correctly with my stock phone running on VZW.
Its not only VZW.. I'm T-Mobile and the same happened
SirRastusBear said:
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
Click to expand...
Click to collapse
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
mlevin said:
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
Click to expand...
Click to collapse
Flashed each separately.
Flash bootloader image
Reboot bootloader (important)
Flash radio image
Flash recovery image
Flash boot image
Flash system image (takes a while)
Flash userdata image ONLY if you want to wipe your own data
Reboot when done
Flash custom recovery
Install SuperSU from custom recovery
Reboot
Profit
Cheers
Those like me who don't want to manually flash.. I just got off the phone with Google, and apparently within 24-48 hours the update will be available again for those devices affected by this hiccup. I'll wait.
Hey guys!
So I really wanted to try out Xposed and get some modules working on my phone. So I unlocked the bootloader by following the directions from Motorola. I then used the moto x 2014 multitool to install twrp recovery and to root (#2 and #7).
I then installed the Xposed apk and flashed the zip file. All Seemed well until I started getting massive amounts of lag if my phone was on for more than 2 minutes. I thought it might be Xposed so I uninstalled it (and the 2 modules that I had installed -- youtube ad blocker and xmultiwindow). That didn't fix it though. So then I thought it might be supersu, so I updated that. That didn't work either.
So then I went back to the multitool and I chose #5... and now it won't boot. It shows the "warning bootloader unlocked" screen and then shows the motorola boot screen for 20 seconds, then shuts off. I also can't boot into fastboot by pressing down the power and volume down buttons.
Any help would be super appreciated!! I'm really not experienced with this stuff but, I had a nexus s with cyanogenmod on it which I loved and then I rooted my note 4 but that's it...
Thank you!!!
EDIT: I can get into fastboot mode, so far I just tried to select 'factory' and it went through the same "bootloader unlocked" then motorola boot for 20 seconds before shutting off...
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
dictionary said:
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
Click to expand...
Click to collapse
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
If you're on 5.1:
First, go here http://forum.xda-developers.com/showthread.php?t=3034811
You will need to download the XposedInstaller_3.0_alpha4.apk and the Xposed-v74-sdk22-arm.zip. It wouldn't hurt to go ahead and download the xposed-uninstaller-20150831-arm.zip either, in case you have problems.
Now you need TWRP. Flash it using fastboot by typing fastboot flash recovery (name of recovery image file.img) from a terminal. Or download TWRP Manager from the Play Store and flash it from there.
Finally, flash the Xposed-v74-sdk22-arm.zip in TWRP. Reboot and install the XposedInstaller_3.0_alpha4.apk.
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
dictionary said:
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
Click to expand...
Click to collapse
Care to share why?
Phoenix232 said:
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
Care to share why?
Click to expand...
Click to collapse
I'd used it a lot when I had my htc m7 with sense, and lg g3 with stock. All I used it for were really mods to make it more AOSP like. There were some features that I miss, like FakeWifi, and App Settings, to name two, but overall with AOSP ROMs out, I haven't had as much desire.
Ok... so the update bricked the phone even more I didn't see the threads that said to not do the OTA update from 4.4.4.
I connect it to the computer and see the qhsusb_bulk. I installed the drivers and now I see the qualcomm 9008. I tried using a couple of blankflash files to fix it, but none of them work. Even ones that say they're for the moto x 2014. Is there anything I can do? I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Can I send it into motorola for a warranty repair? I have a pure edition and I live in the US. I don't know if unlocking the bootloader and rooting will cause motorola to not repair it.
HinaPanda said:
I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Click to expand...
Click to collapse
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
mikeoswego said:
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
Click to expand...
Click to collapse
Thank you! But I actually did try holding down the power button alone and also the power + vol down for like 2 minutes or 30 seconds, etc. The 2 minutes worked the first time, but now it won't It just blinks a green light. Does that mean it's out of battery? I left it plugged into a wall charger overnight though.. how can I tell it's charging?
It sounds like you have a hard brick. Only way to fix it is to send it to a repair center.
Sent from my XT1095 using Tapatalk
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
HinaPanda said:
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
Looks like information is all over the place. Bummer. Hope it works out for you, especially since it was an ota. They could be cheats and try to say it failed due to the unlocked bootloader, and if you'd had root, but that would be a lie. If this rep denies you, just call back and speak to someone else.
Just got a update for my LG G Flex D950 from AT&T. I didn't think twice, and hit update. Now my phone will only go to TWRP. I'm using TWRP v2.8.6.0 any suggestions? All I've done is root it, it has the original ROM it came with.
mine is also soft bricked
I was not rooted and the update installed fine. Just curious what it was....
Edit:
Oh wait this explains everything
(Not really, not at all actually)
http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB423840&cv=820
Update summary**
Effective September 17, 2015, AT&T released a software update for the LG G Flex (D950). This update will be available via Firmware Over The Air (FOTA)*using a Wi-Fi connection.****
*
What's changing?
Device security improvements
What to expect after the update**
Although there should be no impacts to settings or data, we recommend that you back up your important files and media prior to upgrading the software.
bryanizmir said:
I was not rooted and the update installed fine. Just curious what it was....
Click to expand...
Click to collapse
My mom, uncle, and I all have the same phone, the only difference is mine is rooted with TWRP, so something with it being rooted, or with TWRP has screwed it up, and I have no idea which it is
try the steps here. scroll down to the terminal commands and that will get you going.
http://www.androidayos.com/2014/10/0...download-mode/
(How to Fix bricked LG G2 stuck in Recovery after taking OTA update
If you have LG G2 rooted and installed with TWRP recovery then suddenly and automatic OTA update came around but then its too late that your phone just stuck in TWRP Recovery. If you bricked your phone after doing an OTA Update with root and TWRP installed and happens that it stuck at recovery. This can be fixed either by installing the official firmware via flashtool using the KDZ file but sometimes your phone can’t boot into Download mode and it won’t connect to the computer, so this could be a very frustrating situation.
Before doing anything else you may first try this, this has been reportedly worked on some LG G2 users at Androidcentral forum and thanks to the folks at XDA-developers for this workaround.
On your TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot.)
I have the same problem. Rooted/TWRM and soft brick.
I get to terminal window, but no keyboard
tap on select when in terminal
---------- Post added at 05:10 PM ---------- Previous post was at 05:05 PM ----------
That should open the keyboard
I don't have select, I have home, back and the icon that put me in the terminal window from the folders
Do you see this?
Full phone
Sonny beach, trying it now
Got it, now how do I get that software update to go away?
Your phone should keep the update... at least mine did
Mine didn't, in fact it just bricked again, because I accidentally hit the update again
Hi Guys, I have the same problem although I have CWM instead of TWRP. I got the D950 ATT version rooted on stock 4.4.2 and the updated came up on my phone yesterday but I kept on clicking remind me later. Until last night I noticed my phone was booted on CWM and when I tried to reboot, it just went back again to recovery. Also tried restoring from my backup, goes normally and completes but after reboot it just goes back to CWM again. I hope there is someone who can help coz I have pictures and files I need from it...
Those same commands should work. Those are Linux commands for the base system
Texas_Dave said:
Those same commands should work. Those are Linux commands for the base system
Click to expand...
Click to collapse
I guess you are right, although I did it via fastboot it still worked and got all my files back. Thanks for the quick reply. And by the way the update notification is still active, do you think I still have to unroot before installing the update or would it be ok not to unroot and just defrost all the bloatwares that came with the stock OS then accept the update? I am just afraid that it might brick my phone if I went through with it...
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Texas_Dave said:
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Click to expand...
Click to collapse
I just wish IOroot had a way to support the G flex on android 4.4.2 so we do not have to go back to JB just to root. At least from KK we only have to do this new software update, then root the device, install recovery and we are good to go. I guess that would be too much to ask right now on a low activity device like ours. For now all I did to stop the update nag, I froze the software update file from Titanium backup rebooted and now the nag is silenced for a while until we get news that it's ok to do the update on our rooted devices running KK.
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Asisentr said:
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Click to expand...
Click to collapse
I'm in the same boat (although mine is not dev edition, I have unlocked the bootloader & rooted running xposed) and would love an answer!
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
You can't update if you've modified the system partition, ex. being rooted, having xposed etc.To update you need to be completely stock.
I received the same notification on my XT1060DEV. I chose to ignore it.
Anyone know what the update is for? Someone posted in the general section to "never update a rooted unlocked XT1060 ever" because it bricked it or something. My guess is they didn't know what they were doing. I've been having issues lately with my XT1060 not wanting to connect to 2.4GHz wireless networks, only 5GHz. I've tried removing apps one-at-a-time but no luck. Maybe a reset back to square one and the update is due.
Not sure what the update is for though.
So I'm unlocked and rooted on 5.1 with TWRP... but I don't have stock recovery. XT1060 verizon dev edition doesn't have a stock recovery for anything but 4.4.4. So how do I flash recovery to take the update? I'm assuming that flashing recovery from 4.4.4 is a bad idea? If so, what's the solution?
i have 2 1060s one is retail 16 gb (one daughter) the oher is 32 gig dev tooted twrp expoesd. dev daugher tried to do the update it failed and hten she rebooted. it kept tying to apply booting to recovery after 3 minutes and and failing until I removed the update form cache.
I shoul have captured it so I could examine and fix the script.
retail 16 gb updated just fine.
anybody know what this is?
if it not an image maybe we can apply the frixes directly
Mike7143 said:
Anyone know what the update is for?.......
Not sure what the update is for though.
Click to expand...
Click to collapse
Its the security update patch upto 1st April, 2016.
https://motorola-global-portal.cust...detail/a_id/110538/p/30,6720,8696/reg/1417809
I'm on completely stock 5.1 ROM but I have TWRP 2.8.7.0, Xposed installed. So in order for OTA to succeed I'll have to undo all the modifications including the removal of Xposed? The other changes I've made to the system are the removal of some of the Motorola bloatware.
The trick is now to get the right SBF from Motorola.
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Mike7143 said:
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Click to expand...
Click to collapse
Marshmallow?!
So far it's not to bad.
What do you mean by Marshmallow update!? This is just a security update so it should still be Lollipop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
If you are boot-looping after trying the update with TWRP, you will have to delete the update file using TWRP.
From the TWRP main menu, Choose Advanced, then File Manager.
Go into /cache, and delete the Blur_Versionxxxxblahblahblah.zip file.
That'll stop your boot loop.