Related
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X
Right now, my phone boots with boot animation (Motorola animation ->Verizon logo) then goes completely blank. This happened after I tried applying the official OTA 4.4.4. VZW update and failed. I tried applying the official OTA 4.4.4 over the 4.4.4 soak test.
I can boot into fastboot -> recovery which is good news. I tried clearing cache partition which ran for a good 5 minutes before reboot. No success. I tried reinstalling the 4.4.4 soak test zip, failed. Tried installing the official OTA 4.4.4, failed.
I would like to exhaust all options before SBF. Any ideas what I can do to retain my data?
lippstuh said:
Right now, my phone boots with boot animation (Motorola animation ->Verizon logo) then goes completely blank. This happened after I tried applying the official OTA 4.4.4. VZW update and failed. I tried applying the official OTA 4.4.4 over the 4.4.4 soak test.
I can boot into fastboot -> recovery which is good news. I tried clearing cache partition which ran for a good 5 minutes before reboot. No success. I tried reinstalling the 4.4.4 soak test zip, failed. Tried installing the official OTA 4.4.4, failed.
I would like to exhaust all options before SBF. Any ideas what I can do to retain my data?
Click to expand...
Click to collapse
You realize that the soak test build is the final official build. Are you sure you didn't flash the wrong file to your moto x? You can try clearing cache in stock recovery. Otherwise you're stuck with a full reset through rsd.
Where did you get the official OTA?
mawells787 said:
You realize that the soak test build is the final official build. Are you sure you didn't flash the wrong file to your moto x? You can try clearing cache in stock recovery. Otherwise you're stuck with a full reset through rsd.
Where did you get the official OTA?
Click to expand...
Click to collapse
No, I did not realize that . I download the zip file from the comment section of Droid-Life http://www.droid-life.com/2014/07/2...e-now-available-to-all-here-is-the-changelog/. Direct link to said file: http://www.mediafire.com/download/j...sion.164.55.2.ghost_verizon.Verizon.en.US.zip
I already tried clearing cache via fastboot (both through the phone UI and through terminal).
EDIT: Can I do a full reset via RSD using 4.4.2 files found on http://sbf.droid-developers.org/? Even though I was on 4.4.4...
lippstuh said:
No, I did not realize that . I download the zip file from the comment section of Droid-Life http://www.droid-life.com/2014/07/2...e-now-available-to-all-here-is-the-changelog/. Direct link to said file: http://www.mediafire.com/download/j...sion.164.55.2.ghost_verizon.Verizon.en.US.zip
I already tried clearing cache via fastboot (both through the phone UI and through terminal).
Click to expand...
Click to collapse
Patience is a virtue. Always wait for a reliable source like XDA or AP for sbf's,APKs ECT. The comments section especially without an md5 is not a place to download files from and flash. Just try to do a factory reset from recovery see if that works. Otherwise flash the sbf.
Try this: http://forum.xda-developers.com/showthread.php?t=2827307
Thanks. Tried that as well didn't work.
Can I SBF 4.4.2 from http://sbf.droid-developers.org/ if I was on 4.4.4?
IF NOT and I have to SBF 4.4.4, can I SBF file found here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307/
Do not sbf to 4.4.2.
Thanks all, will SBF to FXZ 4.4.4 tonight. Need to use a Windows machine.
lippstuh said:
Thanks all, will SBF to FXZ 4.4.4 tonight. Need to use a Windows machine.
Click to expand...
Click to collapse
Wanted to follow up in case anyone has a similar issue. Yes, using RSDlite worked.
Hey guys, I just got the 4.4.3 to 4.4.4 update notification on my XT1058 (Movistar, Chile). The thing is, I have TWRP so I know I can't take it right now. The device is not rooted nor it has xposed installed. My question is, how do I safely go back to stock recovery? Thanks in advance
Extract the recovery.img from your carriers 4.4.3 sbf and flash just the recovery image via fastboot. Commands should look like this.
fastboot flash recovery recovery.img
Travisdroidx2 said:
Extract the recovery.img from your carriers 4.4.3 sbf and flash just the recovery image via fastboot. Commands should look like this.
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
There's only 4.4.2 available on the sbf list to download. Is it ok or should I take another step?
chalocesped said:
There's only 4.4.2 available on the sbf list to download. Is it ok or should I take another step?
Click to expand...
Click to collapse
They are the same (the 4.4.2 / 4.4.3 recoveries).
Hit the THANKS button under the posts of those who have helped you...
samwathegreat said:
They are the same (the 4.4.2 / 4.4.3 recoveries).
Hit the THANKS button under the posts of those who have helped you...
Click to expand...
Click to collapse
I see! Thank you
I managed to flash the stock recovery, but now I'm unable to turn on wifi. Any thoughts?
chalocesped said:
I managed to flash the stock recovery, but now I'm unable to turn on wifi. Any thoughts?
Click to expand...
Click to collapse
Did you take the OTA? How did you flash stock recovery? It sounds like you borked your /persist partition...
samwathegreat said:
Did you take the OTA? How did you flash stock recovery? It sounds like you borked your /persist partition...
Click to expand...
Click to collapse
No I haven't, as I can't download it via mobile network. I downloaded the 4.4.2 stock firmware, took the recovery file from the zip and did fastboot recovery recovery.img. After booting and realizing I couldn't turn on the wifi (slides immediately to off) I did a factory reset but it didn't solve it
chalocesped said:
No I haven't, as I can't download it via mobile network. I downloaded the 4.4.2 stock firmware, took the recovery file from the zip and did fastboot recovery recovery.img. After booting and realizing I couldn't turn on the wifi (slides immediately to off) I did a factory reset but it didn't solve it
Click to expand...
Click to collapse
Have you tried wiping cache and dalvik, then rebooting? That used to solve a similar problem on another phone.
gokart2 said:
Have you tried wiping cache and dalvik, then rebooting? That used to solve a similar problem on another phone.
Click to expand...
Click to collapse
Unsuccesful, sadly. Will try to restore a previous backup made with twrp
OTA 4.4
Do you have to go back to stock recovery if you're using TWRP recovery? Or is there a way to apply the update while using TWRP? I downloaded the update, told it to install and it rebooted to TWRP. The only zip I found was the old update under cache. Is there a way to do this or where do I find the newly downloaded file to install?
When I couldn't find the file I just rebooted. After booting up the phone attempted to reboot and install about 3 or 4 times before saying unsuccessful and operating normally.
TKil9 said:
Do you have to go back to stock recovery if you're using TWRP recovery? Or is there a way to apply the update while using TWRP? I downloaded the update, told it to install and it rebooted to TWRP. The only zip I found was the old update under cache. Is there a way to do this or where do I find the newly downloaded file to install?
When I couldn't find the file I just rebooted. After booting up the phone attempted to reboot and install about 3 or 4 times before saying unsuccessful and operating normally.
Click to expand...
Click to collapse
You have to use stock recovery.... Just flash TWRP back on afterwards.
Sent from my XT1058 using Tapatalk
superp32 said:
Could it be because he downgraded from 4.4.3
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Who downgraded? The OP doesn't appear to have downgraded - he only flashed the stock recovery from 4.4.2 (which is the same as the 4.4.3 stock recovery). I'm confused.
samwathegreat said:
Who downgraded? The OP doesn't appear to have downgraded - he only flashed the stock recovery from 4.4.2 (which is the same as the 4.4.3 stock recovery). I'm confused.
Click to expand...
Click to collapse
I am in the process of deleting it I didn't see your post about them being the same. He has to have an unlocked bootloader to have twrp correct?
Sent from my XT1058 using Tapatalk
superp32 said:
I am in the process of deleting it I didn't see your post about them being the same. He has to have an unlocked bootloader to have twrp correct?
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Yup, although safestrap recovery (for locked bootloaders) is based on TWRP, it isn't the same. So at least he will be able to root again afterwards. Being unlocked doesn't affect the ability to take an OTA though. I've seen some people confused about that and tell people that they need to re-lock before taking an OTA. This is NOT the case. Stock recovery is required though.
Don't want to confuse anybody though. Just ignore the above. All that really matters is you must have stock recovery and no significant modifications to /system (no Xposed, etc.).
I'm on 4.4.2 for Sprint, i got the update to install 4.4.4, after reading this thread and the guide to flash OTA i see I have to return to stock recovery. My question is in the guide it says '' if you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO''...... my bootloader says 30.B4 , so should i take the OTA?
reds28heem said:
I'm on 4.4.2 for Sprint, i got the update to install 4.4.4, after reading this thread and the guide to flash OTA i see I have to return to stock recovery. My question is in the guide it says '' if you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO''...... my bootloader says 30.B4 , so should i take the OTA?
Click to expand...
Click to collapse
Hmm I'm thinking that what you read might have been for another variant....I'm not familiar with the bootloader version.
Regardless, if you are concerned, you are completely safe to flash the ENTIRE stock 4.4.2 SBF, then you can SAFELY take the 4.4.4 OTA with no risk. And if you take the OTA immediately after flashing the entire SBF, you'll already have stock recovery and you can just flash TWRP and re-root AFTER you are on 4.4.4.
:good:
(The above instructions ONLY apply to the Sprint variant. Not any of the variants that received 4.4.3.)
samwathegreat said:
Hmm I'm thinking that what you read might have been for another variant....I'm not familiar with the bootloader version.
Regardless, if you are concerned, you are completely safe to flash the ENTIRE stock 4.4.2 SBF, then you can SAFELY take the 4.4.4 OTA with no risk. And if you take the OTA immediately after flashing the entire SBF, you'll already have stock recovery and you can just flash TWRP and re-root AFTER you are on 4.4.4.
:good:
(The above instructions ONLY apply to the Sprint variant. Not any of the variants that received 4.4.3.)
Click to expand...
Click to collapse
Yeah that's what i was planning on doing completely flashing to stock then taking the OTA, just wanted to make sure I dont brick my phone
Problem, im trying flash stock but i keep getting this.
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 907079228 bytes
error: cannot load 'system.img': Not enough space
reds28heem said:
Yeah that's what i was planning on doing completely flashing to stock then taking the OTA, just wanted to make sure I dont brick my phone
Problem, im trying flash stock but i keep getting this.
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 907079228 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
System.img is too big for the standard Fastboot.exe included in the Android SDK/PlatformTools. You must use the Moto tweaked fastboot (aka mfastboot) -> http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
I am having trouble flashing 5.0.1 onto my N6. I'm on a mac and tried doing the flash-all.sh then got stuck on the spinning color screen because it gave a system.img error. Then I tried flashing manually and still had no luck. I have tried flashing back to 5.0 and have had no luck. I finally flashed twrp and flashed Pure Shamu back on. I then tried to go back to 5.0.1. So I'm beginning to feel like my only hope to get back to stock is a flashable zip. I wondered if anyone knows if there's one coming?
Try method 2 in step 5 - http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
waywardsojourner said:
I am having trouble flashing 5.0.1 onto my N6. I'm on a mac and tried doing the flash-all.sh then got stuck on the spinning color screen because it gave a system.img error. Then I tried flashing manually and still had no luck. I have tried flashing back to 5.0 and have had no luck. I finally flashed twrp and flashed Pure Shamu back on. I then tried to go back to 5.0.1. So I'm beginning to feel like my only hope to get back to stock is a flashable zip. I wondered if anyone knows if there's one coming?
Click to expand...
Click to collapse
NRT will flash you back to stock.
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
jj14 said:
Try method 2 in step 5 - http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thank you!!! You saved me. I had to modify it slightly because the recovery sent me to the android with the red exclamation so I flashed twrp, wiped, and now I'm back! Thanks so much for the quick response!
Hello guys,
I recieved the 5.0 OTA update for Moto G 2nd Gen(India) but update failing on rooted phone with TeamWin recovery. Any suggestion?
Thanks
Flash stock recovery...
Unroot your phone....
Flash stock Kitket ...
Then lock your boot loader... And try to update
Sent from my XT1068/69 using XDA Premium 4 mobile app
amritmalviya said:
Flash stock recovery...
Unroot your phone....
Flash stock Kitket ...
Then lock your boot loader... And try to update
Sent from my XT1068/69 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think locking the bootloader is not necessary.Stock recovery is the most important part.
Thanks bro, that's what I thought was the problem(recovery mostly). Will back up my data and give it try.
Sent from my XT1068 using XDA Free mobile app
Hey guys, I have a very similar problem.
I have a Moto G2, I unlocked the boot loader, installed TWRP and rooted it.
Today I received the Lollipop update OTA. The update seems to have downloaded fine, but at the moment of installation, the phone enters TWRP and does nothing. If I boot the phone, it boots normally but after a few seconds, the phone restarts itself.
Did this 4 or 5 times and finally came up with the message the update failed.
Do I also need to flash stock? Any other way this may be done?
Right now the update is downloading again but I'm not updating just yet.
vargas7 said:
Hey guys, I have a very similar problem.
I have a Moto G2, I unlocked the boot loader, installed TWRP and rooted it.
Today I received the Lollipop update OTA. The update seems to have downloaded fine, but at the moment of installation, the phone enters TWRP and does nothing. If I boot the phone, it boots normally but after a few seconds, the phone restarts itself.
Did this 4 or 5 times and finally came up with the message the update failed.
Do I also need to flash stock? Any other way this may be done?
Right now the update is downloading again but I'm not updating just yet.
Click to expand...
Click to collapse
Try flashing the stock recovery.For the constant rebooting issue, try wiping your cache and dalvik cache.
mobile_maniac said:
Try flashing the stock recovery.For the constant rebooting issue, try wiping your cache and dalvik cache.
Click to expand...
Click to collapse
Is there a tutorial to do this? Can it be done without re-loading the whole rom?
Just for the recovery: Choose a link for your firmware here on XDA (for example: http://forum.xda-developers.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1068-dual-t2983295 ) ,extract the recovery.img out of it and flash it. Also use the fullunroot-function of superSU. It´s important to remove any changes made to stockfirmware like removing sytemapps or xposed things.
If that doesn´t work you´ll have to flash whole stock firmware like in this thread: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657