Related
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
If your device is getting the update, it doesn't matter which runtime, ART or Dalvik, you are running. You'll get it when you get it.
Sent from my XT1060 using XDA Premium 4 mobile app
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I noticed you're using 1052. I'm not 100% but I thought the current soak test was only for XT1060
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
As already advised, it doesn't matter. But please be sure to post in the correct sub-forum next time. Questions belong in Q&A, NOT General. See the 2nd stick post at the top of the General Sub-forum...
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Me to Still waiting for OTA for my XT1052(Rooted).... I could not find the OTA Capture zip
treyf711 said:
I noticed you're using 1052. I'm not 100% but I thought the current soak test was only for XT1060
Click to expand...
Click to collapse
Moto X (XT 1052) phones in India have already started receiving the 4.4.4 update
Here in Portugal nothing, and this update I is missing here, to fix the S. O. Battery drain.
At least I hope so...
Sent from my XT1052 using XDA Free mobile app
yekollu said:
Moto X (XT 1052) phones in India have already started receiving the 4.4.4 update
Click to expand...
Click to collapse
Have you seen anyone having the 4.4.4 on an Indian X? Moto announced about the update kinda quickly.
devilsdouble said:
Have you seen anyone having the 4.4.4 on an Indian X? Moto announced about the update kinda quickly.
Click to expand...
Click to collapse
Yep!!! Not much of a cosmetic difference though. Phone appliccation looks a little different, there is the new alert app and also the Google+ app (with accompanying Photos)
Not much difference compared to 4.4.2 I hope it gives better battery life. light user interface of dialer, camera tweaks, added pause button in video recording.
Sent from my XT1052 using XDA Free mobile app
Update 4.4.4 Xt1052
Today morning, when i woked up and checked my phone, there was a update notification of 4.4.4. I was pretty much exicted looking that and i start the update process.
Now when the download was completed i clicked on Install the update, phone automatically powered off and rebooted into the TWRP and does nothing with that update. I selected that zip update file from cache folder and failed to install from TWRP as well. Then i rebooted the phone and after some time like 1 minute phone again rebooted into TWRP this time i removed CACHE so that next time the phone will not reboot and it works fine but i can't install the update
Please tell me how should i update now from 4.4.2 to 4.4.4, , if you did on your rooted moto x. I only unlocked bootloader and din't change the rom. Rom is still the same which i got at the time of purchase
vijayid_94 said:
Today morning, when i woked up and checked my phone, there was a update notification of 4.4.4. I was pretty much exicted looking that and i start the update process.
Now when the download was completed i clicked on Install the update, phone automatically powered off and rebooted into the TWRP and does nothing with that update. I selected that zip update file from cache folder and failed to install from TWRP as well. Then i rebooted the phone and after some time like 1 minute phone again rebooted into TWRP this time i removed CACHE so that next time the phone will not reboot and it works fine but i can't install the update
Please tell me how should i update now from 4.4.2 to 4.4.4, , if you did on your rooted moto x. I only unlocked bootloader and din't change the rom. Rom is still the same which i got at the time of purchase
Click to expand...
Click to collapse
........flash back 4.4.2 stock recovery.....
samwathegreat said:
........flash back 4.4.2 stock recovery.....
Click to expand...
Click to collapse
Bro i had mentioned that i din't changed the rom, its already the stock one which i got with it. I had just unlocked the bootloader.
Do i still need to go to Stock
vijayid_94 said:
Bro i had mentioned that i din't changed the rom, its already the stock one which i got with it. I had just unlocked the bootloader.
Do i still need to go to Stock
Click to expand...
Click to collapse
Stock ----recovery----. You specifically said it rebooted into TWRP - which means you HAD to have flashed custom recovery. So flash stock recovery back on - from the 4.4.2 sbf of your carrier:
fastboot flash recovery recovery.img
and assuming you haven't made any significant modifications to /system, the OTA will install without issue. You data will be intact.
Recovery does not = ROM. Two different things.
Correct! Stock recovery must be present or the OTA update will fail.
If you have Xposed with any module you must remove them too.
Flashed stock recovery and still unsuccessful with 4.4.4 OTA upgrade
This is for Verizon Developer's Moto X with an unlocked bootloader.
I forgot that I loaded TWRP on my wife's phone so I tried to take the update and it failed. I also had the modified vzwentitlement.apk loaded so that she could use native tethering. So here's what I did:
- Deleted the modified vzwentitlement.apk
- Removed the ".bak" from the original vzwentitlementservice.apk.bak and the vzwentitlementservice.odex.bak files
- Unrooted the phone using SuperSU's Permanent Unroot option in settings (not sure that was required but didn't want to take any chances
- Downloaded and unzipped the Moto X 4.4.2 from the Motorola firmware site
- Copied the unzipped recovery.img to the Minimal ADB and Fastboot directory
- Flashed the stock recovery back to the phone
I did all that and the phone went into recovery with the little green Droid guy with the hatch open. The blue progress line got about halfway done when the phone rebooted and said it was unsuccessful.
Any ideas what I'm missing? I'd hate to have to flash back to 4.4.2 and lose all her settings, but I will if no one has any better suggestions.
benjamin1492 said:
This is for Verizon Developer's Moto X with an unlocked bootloader.
I forgot that I loaded TWRP on my wife's phone so I tried to take the update and it failed. I also had the modified vzwentitlement.apk loaded so that she could use native tethering. So here's what I did:
- Deleted the modified vzwentitlement.apk
- Removed the ".bak" from the original vzwentitlementservice.apk.bak and the vzwentitlementservice.odex.bak files
- Unrooted the phone using SuperSU's Permanent Unroot option in settings (not sure that was required but didn't want to take any chances
- Downloaded and unzipped the Moto X 4.4.2 from the Motorola firmware site
- Copied the unzipped recovery.img to the Minimal ADB and Fastboot directory
- Flashed the stock recovery back to the phone
I did all that and the phone went into recovery with the little green Droid guy with the hatch open. The blue progress line got about halfway done when the phone rebooted and said it was unsuccessful.
Any ideas what I'm missing? I'd hate to have to flash back to 4.4.2 and lose all her settings, but I will if no one has any better suggestions.
Click to expand...
Click to collapse
Use the FXZ instead. It is a "keep data" FXZ which means that all here data and apps will be intact. It will require re-flashing TWRP, and re-rooting afterwards. You will also need to re-do the entitlement hack. It's very easy. You can use RSD Lite, and you should be back up and running with everything intact in less than 15 minutes from start.
The FXZ method does not use a manifest since it replaces your partitions completely - except for /data (where all your apps and settings are stored).
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Hey guys.
I had download stock recovery for my Moto X.
The zip contain many files as seen into the image below.
Please someone tell me the procedure of flashing them into my phone. I don't know actually how to go now. Do i need to wipe all the data from the phone or just have to wipe system only.
Is the below commands are enough or i have to do some other things as well.
adb reboot bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Sent from my XT1052 using XDA Free mobile app
samwathegreat said:
Use the FXZ instead. It is a "keep data" FXZ which means that all here data and apps will be intact. It will require re-flashing TWRP, and re-rooting afterwards. You will also need to re-do the entitlement hack. It's very easy. You can use RSD Lite, and you should be back up and running with everything intact in less than 15 minutes from start.
The FXZ method does not use a manifest since it replaces your partitions completely - except for /data (where all your apps and settings are stored).
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Click to expand...
Click to collapse
That did the trick, or at least a variation of it did the trick. The post said that the new 4.4.4 FXZ actually DID wipe date, so I followed the RSD Flasher instructions but kept data with a fresh 4.4.2 flash instead. Then I downloaded the 4.4.4 OTA. This time it took. I have re-rooted and got my tether hack back in place. Thanks for all your help.
vijayid_94 said:
Hey guys.
I had download stock recovery for my Moto X.
The zip contain many files as seen into the image below.
Please someone tell me the procedure of flashing them into my phone. I don't know actually how to go now. Do i need to wipe all the data from the phone or just have to wipe system only.
Is the below commands are enough or i have to do some other things as well.
adb reboot bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery.IMG
Should be sufficient. If you still can't take the ota, then also do:
mfastboot flash system system.img
Now you should be able to accept the ota without losing data. You will need to flash TWRP back and re-root.
If anything goes wrong, you will run all the commands you listed but that WILL erase all of your data.
Good luck :good:
Hi guys!
I've flashed faux kernel but I'd like to go back to stock..
Where I can find the stock kernel?
Thanks a lot!
daede86 said:
Hi guys!
I've flashed faux kernel but I'd like to go back to stock..
Where I can find the stock kernel?
Thanks a lot!
Click to expand...
Click to collapse
It's the boot.img file in whatever SBF you are running. You MUST use the boot.img from the exact same SBF file (for YOUR version/variant) that you are currently on.
Flash it using fastboot: fastboot flash boot boot.img
samwathegreat said:
It's the boot.img file in whatever SBF you are running. You MUST use the boot.img from the exact same SBF file (for YOUR version/variant) that you are currently on.
Flash it using fastboot: fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks man
Can't I use flashify to flash the boot.img? Right now I don't have a pc with me..
daede86 said:
Thanks man
Can't I use flashify to flash the boot.img? Right now I don't have a pc with me..
Click to expand...
Click to collapse
Sure. The main function from flashify is to flash IMG s.
nexuspur said:
Sure. The main function from flashify is to flash IMG s.
Click to expand...
Click to collapse
Downloading right now
Thabks again
If I'm on krypton 4.4.4 ROM on a xt1053 T-Mobile variant can I use the 4.4.3 T-Mobile sbf boot.IMG or the Verizon 4.4.4 sbf boot.IMG?
dobbs3x said:
If I'm on krypton 4.4.4 ROM on a xt1053 T-Mobile variant can I use the 4.4.3 T-Mobile sbf boot.IMG or the Verizon 4.4.4 sbf boot.IMG?
Click to expand...
Click to collapse
Maybe....but why would you do that?
One way to find out -- try it. If it doesn't work or causes issues, flash the boot.img from krypton back on.
i think i made a mistake...
i thought i had the 4.4.4 stock firmware on my sd, so i've flashed the boot.img.. but after that, my moto stopped working properly! it completly changed the color scheme, the boot anymation is broken and it keep rebooting after few seconds/minutes.
So i realized i've flashed the 4.4.2 boot.img!!
i temporarly solved this problem flashing a custom rom (using slimkat right now) but i really want to go back to stock!
How should i proceed?!
i have a german moto x xt1052
thanks a lot!!!
daede86 said:
i think i made a mistake...
i thought i had the 4.4.4 stock firmware on my sd, so i've flashed the boot.img.. but after that, my moto stopped working properly! it completly changed the color scheme, the boot anymation is broken and it keep rebooting after few seconds/minutes.
So i realized i've flashed the 4.4.2 boot.img!!
i temporarly solved this problem flashing a custom rom (using slimkat right now) but i really want to go back to stock!
How should i proceed?!
i have a german moto x xt1052
thanks a lot!!!
Click to expand...
Click to collapse
You shouldn't have flashed that custom rom. Now you have to wait for the full sbf to be leaked which could take weeks or months. By flashing the custom rom, you overwrote /system.
If you didn't do that, you could have simply flashed the boot.img from the 4.4.4 OTA file.
Your only other option is to find someone with the same variant as you have on 4.4.4 and ask them to do a twrp backup of just system and boot. Then flash that backup.
Remember: you can't downgrade without great risk of bricking - either immediately or in the future.
Thanks a lot..i hope to find someone with 4.4.4 german moto x!
samwathegreat said:
You shouldn't have flashed that custom rom. Now you have to wait for the full sbf to be leaked which could take weeks or months. By flashing the custom rom, you overwrote /system.
If you didn't do that, you could have simply flashed the boot.img from the 4.4.4 OTA file.
Your only other option is to find someone with the same variant as you have on 4.4.4 and ask them to do a twrp backup of just system and boot. Then flash that backup.
Remember: you can't downgrade without great risk of bricking - either immediately or in the future.
Click to expand...
Click to collapse
i've found an user so kind to share with me his system and boot backup!!
so how should i proceed?! this time i want to be sure
to use my moto in the past days, i flashed kripton rom! so should i just restore from recovery the backup (after a factory reset)?
thanks a lot!!
daede86 said:
i've found an user so kind to share with me his system and boot backup!!
so how should i proceed?! this time i want to be sure
to use my moto in the past days, i flashed kripton rom! so should i just restore from recovery the backup (after a factory reset)?
thanks a lot!!
Click to expand...
Click to collapse
You should be able to boot to twrp, and flash the backup using restore button. Make sure you erase userdata afterwards.
Before you start, you need to copy the backup to your internal storage in the twrp backup folder, of course.
Don't erase userdata until after you have restored the backup otherwise you will erase the backup! Everything on the internal memory will be erased, so save anything important such as pictures to your PC first.
could you share boot.img with me please ?
My phone wont boot anymore
XT1052 on 4.4.2
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
I'm not sure you can be rooted on lollipop to take updates. That could be the problem. Try unrooting.
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
doitright said:
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
tcrews said:
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
Click to expand...
Click to collapse
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
Hey doitright
So I can download the 5.1.1 (For Sprint, USC ONLY) (LMY47Z) even tho its saying US Only, and this was the one I received on the system update!!!
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. To "update" your system to the next version with factory images you would flash bootloader, restart the bootloader, flash the radio, restart the bootloader then flash boot.img and system.img and then reboot the phone. Re-root after.
All Done
Thanks to everyone, all done now, and special thanks to "tcrews" all sorted out now mate, I used fastboot to flash 5.1 (recovery, bootloader, boot and system) then did the same thing for the 5.1.1. I didn't lose any data or apps all working perfectly fine. I had to "Root" the device after, then flashed the "Xposed Firmware". :good: :good:
Yes, thanks as well! I had this issue when the OTA showed up on my Nexus 6 yesterday. Did what vampire_8_7 indicated above, and everything is working with no loss of data or apps. Thanks everyone!
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
You cannot flash the OTA. You can only flash stock. I also have no idea if you're doing something wrong. Probably though, that is usually the case.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
- Fastboot erase system
- Fastboot flash system system.img
- Fastboot flash boot boot.img if you have a custom kernel
- Fastboot flash recovery recovery.img if you have a custom recovery
- Fastboot erase cache and then fastboot flash cache cache.img.
Reboot and sideload the OTA and that should do it because you still have have modified system files on your phone.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
Hey mate
The idea is to go complete stock before you flash any OTA, and this can be achieved by just flashing the "System.img" and the "bootloader.img" file to you device.
DON'T FORGET TO TAKE A FULL BACKUP Note: This warning above is more precaution thing, and this method never wiped any data but its good to have the backup always.
You need to download the official stock image for your device, if you have that's fine keep reading through.
Factory Images
You have to extract the image and get the "system.img" and "bootloader.img"
Copy and Paste the "System.img" and "bootloader.img" files in the fastboot folder.
Open the cmd as admin navigate to the directory where the fastboot resides, then start typing these commands.
fastboot flash bootloader bootloader-XXXX.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Now you have to copy (Boot.img , bootloader.img, system.img and the radio.img) from the OTA image you have and paste it in the fastboot folder, then you will run the previous 2 commands in addition to these 2 commands below.
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
After performing this you should have 5.1.1 on your device without wiping any of your personal data or apps.
vampire_8_7 said:
...
Click to expand...
Click to collapse
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
mar1nasr said:
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
Click to expand...
Click to collapse
No Problems bro. Happy to hear that it worked. XDA is always the place where you can get help
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
mar1nasr said:
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
Click to expand...
Click to collapse
All official updates encrypt.
tcrews said:
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. .
Click to expand...
Click to collapse
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
ikirilenko said:
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
Click to expand...
Click to collapse
I always place these img`s in the /android/sdk/platform-tools/ folder, or extract them and right-click/shift copy to path. Then with cmd in fastboot erase system then flash system system.img and fastboot flash recovery recovery.img. Dowloadlink below in my signature Phantasmagoria and extract the downloaded file until you see the img`s.
gee2012 said:
Then with cmd in fastboot erase system then flash system system.img
Click to expand...
Click to collapse
Out of curiosity, why do you erase system first?
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Sesamechicken said:
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Gus Ghanem said:
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Click to expand...
Click to collapse
Forgot to quote sorry
Sesamechicken said:
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Click to expand...
Click to collapse
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Gus Ghanem said:
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Click to expand...
Click to collapse
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Sesamechicken said:
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Click to expand...
Click to collapse
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Gus Ghanem said:
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Click to expand...
Click to collapse
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Sesamechicken said:
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Click to expand...
Click to collapse
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Nevermind! I am so f****ng stupid!!!!
I NEVER ACTUALLY SELECTED USING UP VOLUME I ALWAYS CLICKED THE POWER BUTTON WHICH REBOOTED. I AM ACTUALLY SO STUPID.
Thanks anyways!
Sesamechicken said:
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Click to expand...
Click to collapse
Since we don't know for sure what's causing it not to boot, might as well flash the whole fimware, I think you can paste all the commands at once, or create a batch file in the firmware folder, flash.bat, shift+right-click, open command window here... type flash.bat
Or you can use RSD Lite
If/when you lose signal/data/wifi you can try flashing just the modems from stock:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?] EDIT: NO. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted. EDIT: I think I didn't wait long enough.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick). EDIT: TWRP backup does not work. I'll eventually file a bug about this.
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway? EDIT: Nobody ever got back to me about this.
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible? EDIT: The ext4 partition must have been made with slightly different options that allowed everything to be packed into the tiny partition
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone? EDIT: I may have flashed to _b instead of _a. In any case I was later able to fix this by flashing the newer firmware quoted below.
SojPapus said:
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?]. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick).
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway?
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible?
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone?
Click to expand...
Click to collapse
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
ptn107 said:
Go here: androidfilehost.com /?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Thank you. Do you happen to know how I can go about checking the cryptographic signatures for these downloads? EDIT: I never managed to do this. I'm considering re-locking my bootloader, which should presumably allow this guarantee to be made. But then I risk bricking the phone. I'm not afraid to go digging around a little bit in the images (I can mount an ext4 filesystem or run simg2img no problem). EDIT: I did go mucking around, and I don't have the public key to go about verifying the bootloader. So that's probably a dead-end.
Also, is resetting user data after every upgrade just SOP when running rooted? Is there some approach to making that less painful that I don't know about? EDIT: NO CLUE. Nobody helped me with this. Also, TWRP doesn't seem to support encryption after the upgrade, so I wasn't able to try restoring from my backup. EDIT ON EDIT: Restoring a TWRP data backup went fine. However, right now TWRP 3.2.1-1 isn't supporting decryption for OPW28.1, so that's another complication. (Just remove the password, and everything seems to work)
EDIT: I've tracked down otacert.zip (containing ota.x509.pem), the key presumably used to sign the OTAs, but the images on firmware.center and androidfilehost don't seem to be signed. Were those signatures stripped out? Is it possible for me to capture those OTA directly (my phone should be receiving these)? My question still stands: how do I force my phone to download the new OTA. I'll deal with flashing it once I can get my hands on it. ANOTHER EDIT: I was able to capture the OTA, but it still isn't installing.
EDIT2: I think I've got a better link.
ptn107 said:
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Flash how? From TWRP?
edufur said:
Flash how? From TWRP?
Click to expand...
Click to collapse
from fastboot
TWRP will be removed upon flashing.
ptn107 said:
from fastboot
TWRP will be removed upon flashing.
Click to expand...
Click to collapse
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
This is not an update zip or rom that can be flashed from TWRP. You will have to do the following:
1. Flash this firmware via fastboot which gets you 8.1.0 w/ April update. (Note: you will lose TWRP and root)
2. Boot the new stock 8.1.0 and take the may security update which will be offered almost immediately.
3. Once on 8.1.0 may update you may reinstall TWRP and a root solution. Be aware that if you do then OTAs from here on won't work. So if you want the June update you will have to re-flash stock 8.1.0 and start over.
Flashing stock will automatically remove whatever twrp or root you have.
To flash this firmware:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
ptn107 said:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
SojPapus said:
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
Click to expand...
Click to collapse
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
edufur said:
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
Click to expand...
Click to collapse
I had no problem getting the 28.1 flashable firmware (cited earlier) working on my phone. I would be sure to only flash to the currently disabled slot--and I'd also be sure to backup the data partition before-hand (and move it off-phone). If you're not touching your active slot, there really shouldn't be any way to mess up the phone (just make sure you're able to get into fastboot with both slots first). If something goes wrong, you can just reset the active slot to the old one.
28.1 doesn't have functioning ADB, so you might also consider setting up Termux and an ssh server on the phone so you can still get a command line on it if needed.