Database Info

Trying to update to 4.4.2 via TWRP Flash getting error

I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?

On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful

tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.

matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update

jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.

matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format

jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything

http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk

Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.

jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?

matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it

jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks

How to install Android 5.0.1 to Nexus 5 without wiping data

I recently unlocked my Nexus 5's bootloader and flashed Android L on it, which wiped all my data. I just downloaded the Google image for Android 5.0.1 for my device from the Android site, and need someone to point me in the right direction on how to apply the update without wiping my user data. I just checked on my phone for an OTA update and it didn't find one. I have AT&T, but bought the phone from Google Play Store.

Edit the flash-all.bat and remove the "-w" bit in the "fastboot -w update image-hammerhead-lrx22c.zip" line
Delete the userdata.img in the image-hammerhead-lrx22c.zip file (you can do this in 7zip or the built-in Windows zip tool)
Flash as normal using the flash-all.bat once your phone is in the bootloader.
Just done the above myself and it has upgraded fine without losing my data.

ianm said:
Edit the flash-all.bat and remove the "-w" bit in the "fastboot -w update image-hammerhead-lrx22c.zip" line
Delete the userdata.img in the image-hammerhead-lrx22c.zip file (you can do this in 7zip or the built-in Windows zip tool)
Flash as normal using the flash-all.bat once your phone is in the bootloader.
Click to expand...
Click to collapse
Thanks for the quick response! I'll try this.
Edit: It worked!

You also could have extracted the image files and done
Code:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash boot boot.img

rootSU said:
You also could have extracted the image files and done
Code:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
Are these the only .img files you need to flash? Why not the others? I know flashing userdata.img will erase your data but the others? Is nothing else updated, e.g. recovery or bootloader?

The factory image is to return it all to stock so you can start again but you only really need those three if you want to keep your custom recovery. Personally, I flash everything and set my phone up fresh with every factory image but then again most of my data is in the cloud these days so I don't mind wiping data

EddyOS said:
The factory image is to return it all to stock so you can start again but you only really need those three if you want to keep your custom recovery. Personally, I flash everything and set my phone up fresh with every factory image but then again most of my data is in the cloud these days so I don't mind wiping data
Click to expand...
Click to collapse
It worked great. Used the same method on my Nexus 7 2013 the other day sans flashing radio. I have too many apps so I gladly avoid the hassle of re-installing everything and signing in on 20+ different apps. I know I can use titanium or other methods to backup all data etc, but I think the fastboot method is the most convenient if you don't have limited bandwidth.
If someone want's a guide on how to use the non OTA fastboot method without loosing data I made a separate one here: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-update-5-0-to-5-x-loosing-t2975174

update to 5.0.1
I'm on root, stock rom and custom recovery. I got the notification for 5.0.1 update and I'm not sure how to do the update. Can I flash the image from TWRP custom recovery?

g33kos said:
I'm on root, stock rom and custom recovery. I got the notification for 5.0.1 update and I'm not sure how to do the update. Can I flash the image from TWRP custom recovery?
Click to expand...
Click to collapse
no you can not. You have to sideload the ota in the stock recovery. This is different than before. You also have to be stock recovery, system, kernel and radio
Sent from my Nexus 5 using XDA Free mobile app

Droid Ultra Bricked on su6-7.3 4.4.4

i've been trying to unbrick this thing for hours after failed root attempt....i'm trying to use rsd lite to flash back to stock.....i now have access to fastboot and recovery and whatnot.... i cant seem to find the firmware i need to unbrick it. the latest i can find is su6-7.2! if someone found su6-7.3 i feel like that would fix it and id be so happy!!!!!!!rsd fails with 7.2

Su6-7.3 is just the security update.
Just use fastboot to flash the partitions with su6-7.2, you will get the update notification after you're up and running.
I had issues with rsdlite and my ultra when I had it.
Look for Minimal adb and fastboot, you will also need mfastboot to flash the system partition, as its too big for fastboot to handle. If you need instructions on how to manually flash the device, a quick search will reveal easy to follow directions.

Shovales said:
Just use fastboot to flash the partitions. I had issues with rsdlite and my ultra when I had it.
Look for Minimal adb and fastboot, you will also need mfastboot to flash the system partition, as its too big for fastboot to handle. If you need instructions on how to manually flash the device, a quick search will reveal easy to follow directions.
Click to expand...
Click to collapse
but were do i get the stuff im flashing back onto the phone...im pritty sure its system is blank right now

Minimal adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Mfastboot:
https://www.androidfilehost.com/?fid=95916177934532795
Firmware:
http://motofirmware.center/files/file/208-cfc-obake_verizon-user-444-su6-72-release-keysxmlzip/
Instructions:
http://forum.xda-developers.com/showthread.php?t=2580060

Shovales said:
Sorry see the my edited post above
Click to expand...
Click to collapse
ok cool im going to try mfastboot now fyi my bootloader is locked still

You're flashing a stock firmware which is signed for the device, so the bootloader being locked isnt problem.
Also mfastboot is used for the system.img to the system partition, you can use fastboot for the other img's.

Shovales said:
Minimal adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Mfastboot:
https://www.androidfilehost.com/?fid=95916177934532795
Firmware:
http://motofirmware.center/files/file/208-cfc-obake_verizon-user-444-su6-72-release-keysxmlzip/
Instructions:
http://forum.xda-developers.com/showthread.php?t=2580060
Click to expand...
Click to collapse
i downloaded that firmware already and when i go to extract it its corrupted... i downloaded 3 from the website and still all were corrupted wile unzipping the system image... i redownloaded just to make sure....any other places i can get the firmware?

What are you using to extract the files with?

Shovales said:
What are you using to extract the files with?
Click to expand...
Click to collapse
i tried windows native extract and 7-zip

Winrar I've never had an issue with any file from motofirmware
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
Wait, you said the system image? Do you mean the actual system.img file?

Shovales said:
Winrar I've never had an issue with any file from motofirmware
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
Wait, you said the system image? Do you mean the actual system.img file?
Click to expand...
Click to collapse
i downloaded the zips off of that website already and i was wondering if i can just get links to flash everything individually through fastboot

logan71f100 said:
i downloaded the zips off of that website already and i was wondering if i can just get links to flash everything individually through fastboot
Click to expand...
Click to collapse
Unless you can find the individual files somewhere the firmware zip file that you have is all you got. I downloaded and extracted that same file no more than 2 weeks ago, and nev
er had one bit of trouble with it..

Shovales said:
Unless you can find the individual files somewhere the firmware zip file that you have is all you got. I downloaded and extracted that same file no more than 2 weeks ago, and nev
er had one bit of trouble with it..
Click to expand...
Click to collapse
well im downloading the file again and i installed winrar...would you by chance be able to upload that old file you have to google drive i can give you a link to my drive so you can upload it if you have it

logan71f100 said:
well im downloading the file again and i installed winrar...would you by chance be able to upload that old file you have to google drive i can give you a link to my drive so you can upload it if you have it
Click to expand...
Click to collapse
i just downloaded it again this is the winrar error im getting
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: Checksum error in C:\Users\Logan\Downloads\system.img. The file is corrupt
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: The archive is corrupt
both om my pcs get the same error wile extracting

logan71f100 said:
i just downloaded it again this is the winrar error im getting
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: Checksum error in C:\Users\Logan\Downloads\system.img. The file is corrupt
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: The archive is corrupt
both om my pcs get the same error wile extracting
Click to expand...
Click to collapse
I'm having the same problem. I actually need SU6-7 but at this point I'd take SU6-7.2 just to get my phone working again

arcaios26 said:
I'm having the same problem. I actually need SU6-7 but at this point I'd take SU6-7.2 just to get my phone working again
Click to expand...
Click to collapse
do you need the firmware i used to unbrick mine?....btw i got SU6-7.2 to unbrick my SU6-7.3 device.... it is fixed and rooted successfully!

that would work, I bricked mine on 6-7.3
what root method did you use? I'm having a hard time finding one that doesn't require files I can't seem to get downloaded fully

I can try and make a tutorial for you to follow with all files you need in a Google drive for easy access how's that sound?

logan71f100 said:
I can try and make a tutorial for you to follow with all files you need in a Google drive for easy access how's that sound?
Click to expand...
Click to collapse
sounds perfect actually. This phone has given me so many more problems doing this than my old HTC incredible 4g but the phone is far better than that old one.

he only ****ty part us the bootloader is locked and I can't find a way to unlock it. One day there will be a way and I will find it

[Q] Is it safe to take the OTA when the bootloader is unlocked and rooted?

Is it safe to take the OTA when the bootloader is unlocked and rooted?

tommy7115 said:
Is it safe to take the OTA when the bootloader is unlocked and rooted?
Click to expand...
Click to collapse
Bootloader unlocked is not a problem. With root though the update will likely fail. At least it used to. You can sideload OTA or flashall with -w removed (my prefered way).
Sent from my Pixel using Tapatalk

milan187 said:
Bootloader unlocked is not a problem. With root though the update will likely fail. At least it used to. You can sideload OTA or flashall with -w removed (my prefered way).
Click to expand...
Click to collapse
Do you literally just delete the 2 digits "-w" and disregard all of the code before and after that?

maflin18 said:
Do you literally just delete the 2 digits "-w" and disregard all of the code before and after that?
Click to expand...
Click to collapse
Yes that's all. Edit the file. Delete those 2 characters and save.
This flashes all partitions and leaves your usedata untouched.
Cleanest way to update. It's full update instead of OTA patch.
Sent from my Pixel using Tapatalk

milan187 said:
Yes that's all. Edit the file. Delete those 2 characters and save.
This flashes all partitions and leaves your usedata untouched.
Cleanest way to update. It's full update instead of OTA patch.
Click to expand...
Click to collapse
Am I right in both if these statements? (With -w removed)
1) if you use flash-all with same build number you're already on, it will basically remove any modifications (root, TWRP, etc) fix any issues with that, and allow you to try again without removing any apps or data.
2) if you use flash-all with higher build than you're already on, it does the same above but also updates you to the newer build. (Eliminating need to sideload eta)

milan187 said:
Bootloader unlocked is not a problem. With root though the update will likely fail. At least it used to. You can sideload OTA or flashall with -w removed (my prefered way).
Click to expand...
Click to collapse
How do you flash all with the -w removed?

maflin18 said:
Am I right in both if these statements? (With -w removed)
1) if you use flash-all with same build number you're already on, it will basically remove any modifications (root, TWRP, etc) fix any issues with that, and allow you to try again without removing any apps or data.
2) if you use flash-all with higher build than you're already on, it does the same above but also updates you to the newer build. (Eliminating need to sideload eta)
Click to expand...
Click to collapse
Yes to both. I actually use both methods. Sometimes to clean system other times to update. Updating will remove modifications as well such as root, TWRP pretty sure you knew that.
Sent from my Pixel using Tapatalk
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
tommy7115 said:
How do you flash all with the -w removed?
Click to expand...
Click to collapse
Right click and edit the flashall file with a notepad. Near the end remove -w and save. Run the file.
Sent from my Pixel using Tapatalk

tommy7115 said:
How do you flash all with the -w removed?
Click to expand...
Click to collapse
In the unmodified flash-all.bat file, there's a command that begins with "fastboot update -w xxxxx.zip". If you want to retain user data, use a text editor to delete '-w'.

Also once you update with flashall you can take OTA updates again.
Try not to downgrade with this method. Downgrading does not always work without wiping user data. Though it very rare you want to downgrade.
Sent from my Pixel using Tapatalk

That is to say, ever one month when new build available, we have to fastboot flash the full image and, then install twrp & root.
Am I right.
milan187 said:
Yes to both. I actually use both methods. Sometimes to clean system other times to update. Updating will remove modifications as well such as root, TWRP pretty sure you knew that.
Sent from my Pixel using Tapatalk
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Right click and edit the flashall file with a notepad. Near the end remove -w and save. Run the file.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

bush911 said:
That is to say, ever one month when new build available, we have to fastboot flash the full image and, then install twrp & root.
Am I right.
Click to expand...
Click to collapse
If you want TWRP and root yes. Flashall will put you back to 100% stock. It's not that bad though. Takes a few minutes to TWRP and root again.
Sent from my Pixel using Tapatalk

thank you dude. This new phone with two slots makes me a little bit scared, as the 1st time I tried to install TWRP and ended up losing all my user data, after that I rebooted and cleared the pattern and reinstalled twrp and finally rooted.
milan187 said:
If you want TWRP and root yes. Flashall will put you back to 100% stock. It's not that bad though. Takes a few minutes to TWRP and root again.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

bush911 said:
thank you dude. This new phone with two slots makes me a little bit scared, as the 1st time I tried to install TWRP and ended up losing all my user data, after that I rebooted and cleared the pattern and reinstalled twrp and finally rooted.
Click to expand...
Click to collapse
Yeah I know what you mean. In the beginning I was doing flashall every few days because I would mess something up. I think I've got it down. Having the 2 slots will likely give us some benefits in the future. People are already doing some dual booting. Though it's not perfect.
Sent from my Pixel using Tapatalk

Going to have to flash-all (w/o -w) back to stock due to issues with my GPS. Previously, there was some dispute over the "correct" way to get RC1 and sr5.
1) is there now a common consensus on the correct method to obtain rc1 and sr5?
2) if yes, what is that method?
3) if no, what are my options?
Note: personally, I have never messed with flashing anything to a specific slot, and never messed with or deleted any 'fstab' file, and currently have RC1 and sr5 functioning properly.

maflin18 said:
Going to have to flash-all (w/o -w) back to stock due to issues with my GPS. Previously, there was some dispute over the "correct" way to get RC1 and sr5.
1) is there now a common consensus on the correct method to obtain rc1 and sr5?
2) if yes, what is that method?
3) if no, what are my options?
Note: personally, I have never messed with flashing anything to a specific slot, and never messed with or deleted any 'fstab' file, and currently have RC1 and sr5 functioning properly.
Click to expand...
Click to collapse
New method: boot TWRP rc1, flash TWRP rc1, flash latest 2.79 SuperSU zip (SR1)
Sent from my Pixel using Tapatalk

joetheshmo said:
New method: boot TWRP rc1, flash TWRP rc1, flash latest 2.79 SuperSU zip (SR1)
Click to expand...
Click to collapse
Thank you. Do I need to worry about booting or not booting between any of those steps? ( Previously you could not reboot b/t installing rc1 and sr5 or there would be issues)

maflin18 said:
Thank you. Do I need to worry about booting or not booting between any of those steps? ( Previously you could not reboot b/t installing rc1 and sr5 or there would be issues)
Click to expand...
Click to collapse
I don't believe you have to worry about that but I always flash everything together
Sent from my Pixel using Tapatalk

joetheshmo said:
I don't believe you have to worry about that but I always flash everything together
Click to expand...
Click to collapse
After executing flash-all.bat (w/o '-w'), everything should be just the way it was before, minus root&twrp, correct?

maflin18 said:
After executing flash-all.bat (w/o '-w'), everything should be just the way it was before, minus root&twrp, correct?
Click to expand...
Click to collapse
Correct. You'll be fully stock
Sent from my Pixel using Tapatalk

joetheshmo said:
Correct. You'll be fully stock
Click to expand...
Click to collapse
Apps, settings, data, wallpaper, launcher, etc etc... Not affected by flash-all at all? (If -w removed)

Cannot use fastboot

Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?

Xdevillived666 said:
Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?
Click to expand...
Click to collapse
Is there a "modem.img" that you extracted from the factory image?

Badger50 said:
Is there a "modem.img" that you extracted from the factory image?
Click to expand...
Click to collapse
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/

Xdevillived666 said:
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/
Click to expand...
Click to collapse
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.

Badger50 said:
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.
Click to expand...
Click to collapse
Nope. Long story short I'm trying to use qpst and pdc tool. Getting a qmi error and read on a German thread that sometimes reflashing modem will fix it. Problem is that I can't flash individual images aside from radio or bootloader with fastboot -_-

Are your platform tools up to date?

jsauder2 said:
Are your platform tools up to date?
Click to expand...
Click to collapse
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't

Xdevillived666 said:
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't
Click to expand...
Click to collapse
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.

jsauder2 said:
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.
Click to expand...
Click to collapse
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.

The factory image does flash the modem. It doesn't say so in the bat or sh files, but you'll also notice that it doesn't mention the boot, system, or vendor files either (along with many other things), even though those are most certainly flashed during an update. That's because those are all inside the image zip that is referenced in the last line of the bat or sh (where you remove the -w). It flashes everything inside of that, including the modem.
If a screwed up modem is your problem, flashing the factory image will fix it. If that doesn't fix it, then the modem is not your issue.

Xdevillived666 said:
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.
Click to expand...
Click to collapse
I don't know if this will work. I also don't know what the fastboot update command does under the hood. But the flash-all batch file does flash the modem image using the fastboot update command. What if you created a zip file with your modem image in it and then tried to flash it with the update command, or possibly replace the modem.img in the zip in the factory image with your image?
Sent from my [device_name] using XDA-Developers Legacy app