Related
I've got a moto X vzw DE. Upgraded OTA to 4.4. It's unlocked. I'd like to get the 4.4.2 OTA when available.
After looking around, it seems that if I install a custom recovery (TWRP or CWM), then the OTA will fail: the OTA checks to see if any system files, including recovery have changed. Correct???
But if I install SU, does that mess up the OTA?
seandarcy said:
I've got a moto X vzw DE. Upgraded OTA to 4.4. It's unlocked. I'd like to get the 4.4.2 OTA when available.
After looking around, it seems that if I install a custom recovery (TWRP or CWM), then the OTA will fail: the OTA checks to see if any system files, including recovery have changed. Correct???
But if I install SU, does that mess up the OTA?
Click to expand...
Click to collapse
Yes and yes
Sent on my Gummy running Lenoto X
flashallthetime said:
Yes and yes
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I've got the GSM Dev Edition, bootloader unlocked running stock rooted 4.4 with TWRP.
So in order to upgrade to 4.4.2, I'll need to do one of two things...
1) Either wait for a flashable zip that I can flash in TWRP
2) Or flash stock recovery, accept the OTA, then reroot by installing SuperSU
Is that correct?
KentuckyHouse said:
I've got the GSM Dev Edition, bootloader unlocked running stock rooted 4.4 with TWRP.
So in order to upgrade to 4.4.2, I'll need to do one of two things...
1) Either wait for a flashable zip that I can flash in TWRP
2) Or flash stock recovery, accept the OTA, then reroot by installing SuperSU
Is that correct?
Click to expand...
Click to collapse
You need stock recovery and also supersu removed as well, any mods that you installed must be also removed, basically anything that needs root access must be removed
Sent on my Gummy running Lenoto X
flashallthetime said:
You need stock recovery and also supersu removed as well, any mods that you installed must be also removed, basically anything that needs root access must be removed
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Are you sure you need supersu removed? I've not found that to be true on Nexus devices. This is also why I'd really like to be able to just boot into a custom recover rather than having to install it. If you boot into the custom recovery, you can install supersu and then you just have root with the stock recovery. OTA's are much easier at this point.
pboggini said:
Are you sure you need supersu removed? I've not found that to be true on Nexus devices. This is also why I'd really like to be able to just boot into a custom recover rather than having to install it. If you boot into the custom recovery, you can install supersu and then you just have root with the stock recovery. OTA's are much easier at this point.
Click to expand...
Click to collapse
100‰ moto is no nexus device , you're comparing apples to oranges, give it a try and I'll bet you'll end up bootlooping. I've had the moto x since the being and have been through 3 ota's
Sent on my Gummy running Lenoto X
So do you only get the OTA if you're on stock recovery? I mean the notification that its available.. Do I have to flash stock recovery in order to even see it, or can I check and once its ready I can switch back to stock recovery and take it? I'm on twrp now with tmobile moto x and I don't see the update yet..
vikramkhalsa said:
So do you only get the OTA if you're on stock recovery? I mean the notification that its available.. Do I have to flash stock recovery in order to even see it, or can I check and once its ready I can switch back to stock recovery and take it? I'm on twrp now with tmobile moto x and I don't see the update yet..
Click to expand...
Click to collapse
You will receive it if you're running the stock ROM with twrp recovery installed , you can even download it but not flash it with custom recovery and rooted. Again you need the stock recovery and a clean system with all native apps installed, all root mods must be removed ie xposed removed , viper4android and driver removed , just to mention a few. Now this is the important part, if you are already running 4.4.2 bootloader from another firmware package please do not flash the ota, why? It sometimes and almost always results in a hard brick, no safeties existing when ota flash, some how the boot loader and partition table mess up. Ota's are not made to flash correctly over the same bootloader with our moto, so please flash either with mfastboot or rsdlite and or flash the system, boot.img and modem manually
Sent on my Gummy running Lenoto X
Worst case scenario: you flash stock recovery and stock /system image. That will eradicate any existence of SuperSU or anything else that was done to /system. But before re-flashing /system, I'd go into SuperSU ->Settings -> Cleanup -> Full unroot... that may be all you need to do as far as /system goes (assuming you're using SuperSU). If you have Xposed installed, uninstall it via the app. Then flash stock recovery, reboot, and you should be good... theoretically.
I've never had the need to unroot before, so I'm not 100% sure which would work best, but I'm in the exact same boat with my VZW Dev Edition and will have to follow similar steps to accept the OTA.
Or if i'm too impatient to wait for the OTA, I can also go back to stock recovery and download the ota from this thread http://forum.xda-developers.com/showthread.php?p=50086296 right?
It seems like they're saying you don't lose root?
vikramkhalsa said:
Or if i'm too impatient to wait for the OTA, I can also go back to stock recovery and download the ota from this thread http://forum.xda-developers.com/showthread.php?p=50086296 right?
It seems like they're saying you don't lose root?
Click to expand...
Click to collapse
I believe the OTA verifies certain files in /system, so you'll probably need a non-modified /system partition as well. But if others are reporting the non-loss of root, might as well have a go. Worst that could happen is it fails and you then flash stock /system and away you go.
You'll lose root, root binaries are in xbin folder and superuser flashes as a system app , it cleaned completely by the ota, the system files are all new. You need to flash twrp again anyways and it asks if you want root again. Very easy
Sent on my Gummy running Lenoto X
flashallthetime said:
You'll lose root, root binaries are in xbin folder and superuser flashes as a system app , it cleaned completely by the ota, the system files are all new. You need to flash twrp again anyways and it asks if you want root again. Very easy
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Awesome thanks. I just went back to stock recovery and after checking it shows the update available! Not sure if it was stock recovery that did it or the fact that I copied the file into my sd card and it detected that?
here goes!
vikramkhalsa said:
Awesome thanks. I just went back to stock recovery and after checking it shows the update available! Not sure if it was stock recovery that did it or the fact that I copied the file into my sd card and it detected that?
here goes!
Click to expand...
Click to collapse
It was ready for download and after you reflashed stock recovery or the system it always pings moto to check for updates automatically. Good luck
Sent on my Gummy running Lenoto X
flashallthetime said:
It was ready for download and after you reflashed stock recovery or the system it always pings moto to check for updates automatically. Good luck
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I get an error in the middle of the installation.. and it reboots.. then says update installation successful but then it shows me update is available and starts the whole process all over again..
vikramkhalsa said:
I get an error in the middle of the installation.. and it reboots.. then says update installation successful but then it shows me update is available and starts the whole process all over again..
Click to expand...
Click to collapse
Ok , something obviously is not right with your system, does it give you a reason or a warning? Which bootloader are you running, you can get that from the fastboot screen.
Sent on my Gummy running Lenoto X
flashallthetime said:
Ok , something obviously is not right with your system, does it give you a reason or a warning? Which bootloader are you running, you can get that from the fastboot screen.
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not sure if stock recovery flashed properly, when i try to boot into recovery i just get "no command." and the android with !..
I tried to flash recovery again..
I did have xposed but I deactivated all the modules. Should i flash system again maybe?
Not sure what the bootloader is, should be the 4.4 one..
This is what I got when flashing stock recovery.."
"(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.908s]
writing 'recovery'...
OKAY [ 0.958s]
finished. total time: 1.870s"
vikramkhalsa said:
I'm not sure if stock recovery flashed properly, when i try to boot into recovery i just get "no command." and the android with !..
I tried to flash recovery again..
I did have xposed but I deactivated all the modules. Should i flash system again maybe?
Not sure what the bootloader is, should be the 4.4 one..
This is what I got when flashing stock recovery.."
"(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.908s]
writing 'recovery'...
OKAY [ 0.958s]
finished. total time: 1.870s"
Click to expand...
Click to collapse
Recovery flashes it seems. Ok I need to know what mods or any system files you removed or replaced, are you using xposed
Dead andi means stock recovery is installed
Sent on my Gummy running Lenoto X
flashallthetime said:
Recovery flashes it seems. Ok I need to know what mods or any system files you removed or replaced, are you using xposed
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Thanks for the help.
yeah I was using xposed, thats it. I just flashed twrp back, it works. then flashed the xposed disabler. Now flashing stock recovery and trying again. haha
---------- Post added at 03:31 PM ---------- Previous post was at 03:24 PM ----------
I have a custom bootanimation.. does that make a difference?
Same thing is still happening.. starts installing the update and then errors out and reboots.
vikramkhalsa said:
Thanks for the help.
yeah I was using xposed, thats it. I just flashed twrp back, it works. then flashed the xposed disabler. Now flashing stock recovery and trying again. haha
---------- Post added at 03:31 PM ---------- Previous post was at 03:24 PM ----------
I have a custom bootanimation.. does that make a difference?
Same thing is still happening.. starts installing the update and then errors out and reboots.
Click to expand...
Click to collapse
Yap ,think about it, the ota is meant to flash to a noobs phone , a noob who doesn't know what xda is, so your system needs to be 100 % stock any extra apps removes from the apps folder must be removed,
Any apps altered in the pri app folder same thing, any mod to framework folder must be removed, any mod to media folder must be removed
Sent on my Gummy running Lenoto X
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
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
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
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.
PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?
gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?
nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Sorry, meant 4.4.2.
gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.