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
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
I was on Android 5.0 lollipop when something glitched and my phone wouldn't get out of bootloader mode, so i flash stock android. When it then finished and went back to 4.4.4 i tried flashed the factory images again to lock the bootloader, but it wouldn't let me because it kept saying "downgrading" or something along those lines. Now my phones sysetem version is 21.11.17.titan_retuaws.retuaws.en.Us which is the one of 5.0 when im clearly on 4.4.4. I am currently rooted with a custom recovery, any ideas on how i could possibly get back to android L?
ErikG1999 said:
any ideas on how i could possibly get back to android L?
Click to expand...
Click to collapse
Two possible ways:
A. the stock method
Download these files:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip from motofirmware.com
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0)
Blur_Version.22.21.16.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0.1) (both from this forum)
install the first via fastboot, (ignore errors given by gpt.bin and motoboot.img), reboot
install the second via stock-recovery, reboot
install the third via stock-recovery, reboot
B.
flash The Titan Prime ROM, reboot
doppelhelix said:
Two possible ways:
A. the stock method
Download these files:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip from motofirmware.com
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0)
Blur_Version.22.21.16.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0.1) (both from this forum)
install the first via fastboot, (ignore errors given by gpt.bin and motoboot.img), reboot
install the second via stock-recovery, reboot
install the third via stock-recovery, reboot
B.
flash The Titan Prime ROM, reboot
Click to expand...
Click to collapse
the A method doesn't work, ive tired it before. It doesn't let me relock the bootloader because it thinks im downgraded the system. I think ill try the B method. In order to instal the custom rom would i have to use a custom recovery? how would i go about doing it (P.S. XT1064 rooted with TWRP)
ErikG1999 said:
the A method doesn't work, ive tired it before. It doesn't let me relock the bootloader because it thinks im downgraded the system. I think ill try the B method. In order to instal the custom rom would i have to use a custom recovery? how would i go about doing it (P.S. XT1064 rooted with TWRP)
Click to expand...
Click to collapse
currently I BELIEVE if you have flashed MOTOBOOT.img (bootloader) from a 5.0 version you can not go back to a 4.4.4 version, but you can still run a 4.4.4 rom on a 5.0 bootloader. a locked / unlocked bootloader should not stop OTA updates. Having the wrong recovery will stop OTA installing. and mismatched bootloader / recoveries MAY cause problems.
to flash titan prime rom use TWRP (make backup 1st) place zipped tp-rom on sdcard and gapps.zip and following instruction in the rom thread
So, A method (blur versions) will always fail if you have TWRP installed, you need stock recovery that matches your rom on phone now , the 1st from moto firmware should work via mfastboot method.
ErikG1999 said:
It doesn't let me relock the bootloader
Click to expand...
Click to collapse
Why would you want to do that? There's absolutely no reason for relock.
help!!!
doppelhelix said:
Two possible ways:
A. the stock method
Download these files:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip from motofirmware.com
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0)
Blur_Version.22.21.16.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0.1) (both from this forum)
install the first via fastboot, (ignore errors given by gpt.bin and motoboot.img), reboot
install the second via stock-recovery, reboot
install the third via stock-recovery, reboot
B.
flash The Titan Prime ROM, reboot
Click to expand...
Click to collapse
i did what you said and flashed the firmware and know my phone wont boot up. i can access the bootloader and twrp, please help!
ErikG1999 said:
i did what you said and flashed the firmware and know my phone wont boot up. i can access the bootloader and twrp, please help!
Click to expand...
Click to collapse
PM me, if you have some time, so we can go through the whole process step by step without overflooding this thread
ErikG1999 said:
i did what you said and flashed the firmware and know my phone wont boot up. i can access the bootloader and twrp, please help!
Click to expand...
Click to collapse
If you flashed the firmware correctly you should not have twrp.
Android The Greek said:
If you flashed the firmware correctly you should not have twrp.
Click to expand...
Click to collapse
ya i dun goofed, i fixed it now its all good
I'm surprised that nobody else has uploaded any of the OTAs yet, so I thought I'd start.
I uploaded it on 2 servers, in case one is down:
Blur_Version.91.2.26001.XT890.Retail.en.EU.zip:
wicked fast: https://mega.nz/#!FU4TBDyb!Cl3OB3M2GTvG-gcDK0vWQNzI090EFJ60suqJpzPsiQo
also fast: http://180upload.com/ag1ccjfznluh
Again, this is stock Razr I EU OTA from 4.1.2 to 4.4.2
This should be very handy for the ones who still haven't received the OTA so you can flash it manually.
Please note that the GPT gets flashed, so a downgrade to 4.1.2 can be tricky after taking this update.
Can i flash this with rsd-lite when i already have kitkat OTA? I would like to flash again kitkat, because i had reboots with the stock.
ansa1234 said:
Can i flash this with rsd-lite when i already have kitkat OTA? I would like to flash again kitkat, because i had reboots with the stock.
Click to expand...
Click to collapse
No, those are not fastboot files, only the OTA. There are no released fastboot files available for kitkat so there is nothing you can flash with RSD
Can sombody give me a alive link? not sure why its posted here cus I ment for the twrp installer
Tried to flash in CWM no luck ?
How to force this OTA without delete all data?
I'm on 4.4.2 but Brasil, and want to got to EU.
Thanks!
dornz said:
Tried to flash in CWM no luck
Click to expand...
Click to collapse
CWM can't flash the stock update. U will need the stock recovery to get it working.
MaliMravac said:
How to force this OTA without delete all data?
I'm on 4.4.2 but Brasil, and want to got to EU.
Thanks!
Click to expand...
Click to collapse
The ota shouldn't delete any data at all afaik.
Hazou said:
CWM can't flash the stock update. U will need the stock recovery to get it working.
The ota shouldn't delete any data at all afaik.
Click to expand...
Click to collapse
Thanks for reply? how do i revert to stock recovery so ?
dornz said:
Thanks for reply how do i revert to stock recovery so ?
Click to expand...
Click to collapse
The stock recovery can be extracted from a RSD-Lite package. Than reboot in fastboot and use the command "fastboot flash recovery <recovery>". Now u will have the stock recovery instead of CWM.
Do know that going from 4.1.2 to 4.4.2 with the OTA update requires no modification to the system partition, except from adding files. Modifying files or deleting files from the system partition will make the update fail. So if u only have root installed through recovery then there is a hugh change everything works. But if u deleted some bloatdware, then it most likely will fail.
Hazou said:
The stock recovery can be extracted from a RSD-Lite package. Than reboot in fastboot and use the command "fastboot flash recovery <recovery>". Now u will have the stock recovery instead of CWM.
Do know that going from 4.1.2 to 4.4.2 with the OTA update requires no modification to the system partition, except from adding files. Modifying files or deleting files from the system partition will make the update fail. So if u only have root installed through recovery then there is a hugh change everything works. But if u deleted some bloatdware, then it most likely will fail.
Click to expand...
Click to collapse
Hi again thanks for info. My xt890 has root but i never flashed any roms on it i did mes it up one time so i flashed 4.1.2 stock jb with RSD lite to fix it. Will try later on and hope it works ?
Edit: flashed 4.1.2 In RSd and after reboot i got 4.4.2 ota update all sorted except no root any way to root on 4.4.2
dornz said:
Edit: flashed 4.1.2 In RSd and after reboot i got 4.4.2 ota update all sorted except no root any way to root on 4.4.2
Click to expand...
Click to collapse
Just flash a custom recovery and installatie supersu or soms other superuser app
Hazou said:
Just flash a custom recovery and installatie supersu or soms other superuser app
Click to expand...
Click to collapse
Awesome will try later thanks for reply?
dornz said:
Awesome will try later thanks for reply?
Click to expand...
Click to collapse
Here i thought i had to root first then flash custom recovery ?
Can I apply this OTA update over a standard 4.1.2?. I am using 4.1.2 from Personal Argentina , recovery is stock, but only I have root. I know that is not update to 4.4.2 of my versión so I should go to retail BR or EU but if I flash via RSD I will lost all my settings.
So if I update using this OTA (or BR OTA) to go to 4.4.2 from other 4.1.2, can be a problem?
Regards,
Claudio.
Hazou said:
Just flash a custom recovery and installatie supersu or soms other superuser app
Click to expand...
Click to collapse
Hi tryed flashing twrp and cwm.img in fastboot on xt890 4.4.2 no luck..on adb UI after flashing.img it finish s but on phone it says flashing image and stays like that. After ota update i have no root so maybe thats whats up..?
dornz said:
Hi tryed flashing twrp and cwm.img in fastboot on xt890 4.4.2 no luck..on adb UI after flashing.img it finish s but on phone it says flashing image and stays like that. After ota update i have no root so maybe thats whats up..?
Click to expand...
Click to collapse
If you are in fastboot mode, the recovery's should flash just fine If u have an unlocked bootloader. Should not be more than 5-10 seconds to finish. If something goes wrong it will say it on screen and even in the terminal on your PC.
Hazou said:
If you are in fastboot mode, the recovery's should flash just fine If u have an unlocked bootloader. Should not be more than 5-10 seconds to finish. If something goes wrong it will say it on screen and even in the terminal on your PC.
Click to expand...
Click to collapse
Hi thanks for quick reply. Ya im pretty sure im in fastboot.in adb i type reboot bootloader and that brings up fastboot menu on phone (all black with blue bars highlighting option s use vol up and down to scroll trough options) yellow txt down below on black when flashing. I done this flash before on 4.1.2 with cwm .img don't no whats going wrong now ?
Hazou said:
If you are in fastboot mode, the recovery's should flash just fine If u have an unlocked bootloader. Should not be more than 5-10 seconds to finish. If something goes wrong it will say it on screen and even in the terminal on your PC.
Click to expand...
Click to collapse
About to try again is this fastboot ?
Hazou said:
If you are in fastboot mode, the recovery's should flash just fine If u have an unlocked bootloader. Should not be more than 5-10 seconds to finish. If something goes wrong it will say it on screen and even in the terminal on your PC.
Click to expand...
Click to collapse
Heres 2 pics of this as you can see in first one it sends .img but in second pic flashing recovery on phone and it hasn't changed yet ?
I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778975696 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Cheetah1024 said:
I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Click to expand...
Click to collapse
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Evolution_Tech said:
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Click to expand...
Click to collapse
Oh, so it's normal that flash-all doesn't work?
Cheetah1024 said:
Oh, so it's normal that flash-all doesn't work?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Cheetah1024 said:
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Click to expand...
Click to collapse
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Evolution_Tech said:
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Click to expand...
Click to collapse
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Cheetah1024 said:
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, you helped me big time mate! Thank You! :laugh:
Can someone explain this to me as to why https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip gives me the following error shown in the attach picture?
Looks like it should match correctly but sideload is errorring out saying otherwise
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>adb shell getprop ro.build.fingerprint
google/shamu/shamu:5.1.1/LMY47Z/1860966:user/release-keys
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
david279 said:
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
Install the stock recovery in fastboot, you can download it from the factory images or just search for it
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
danarama said:
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
Click to expand...
Click to collapse
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
JimSmith94 said:
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
Click to expand...
Click to collapse
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
danarama said:
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
Click to expand...
Click to collapse
There is an LYZ28J factory image available, here > https://developers.google.com/android/nexus/images
danarama said:
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
Click to expand...
Click to collapse
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
JimSmith94 said:
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
Click to expand...
Click to collapse
It will lose root, but you just flash supersu from recovery
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
doublejz said:
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
Click to expand...
Click to collapse
Just flash the system.img then