Related
Hello xda, I unfortunately have an issue with flashing the android 4.4 factory zip. I know there are many different problems including the "status 7" issue which is ticking of some people. But I have a different error,
no md5 file found..
verifying current system..
"/system/app/Currents.apk" has unexpected contents.
E: Error executing updater binary in zip...
Can someone please explain this error and the solution for me? I have tried everything I could find, I'm rooted with trwp and I even tried cwp and adb side load to flash the android 4.4 factory zip but the same error always appears.
Someone help me.
I must of deleted Google currents by accident. And I couldn't even flash the android 4.3 factory zip without getting the same error.
Sent from my Nexus 7 using XDA Premium HD app
Please help guys
Sent from my Nexus 7 using XDA Premium HD app
the same as me
GoldenNexus7 said:
Please help guys
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I also receive update via OTA but it still error, so i try adb sideload but the error is
Code:
"/system/app/Currents.apk" has unexpected cotents
Error (status 7)
Installation aborted
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
GMPOWER said:
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
Click to expand...
Click to collapse
Not sure how to change permissions but I'll try that thanks.
Sent from my Nexus 7 using XDA Premium HD app
GMPOWER said:
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
Click to expand...
Click to collapse
That worked well but then when I tied to flash it again in both twrp and cwm recovery it gives a new error,
"/System/bin/app-process" has unexpeted contents
E:error in /tmp/update.zip
PLEASE HELP ME ON THIS,SOMEONE SAID THIS MIGHT HAVE SOMETHING TO DO WITH XPOSED AND I SHOULD DELETE FRAMEWORK FIRST. not sure what he meant by remove framework.
Sent from my Nexus 7 using XDA Premium HD app
GoldenNexus7 said:
That worked well but then when I tied to flash it again in both twrp and cwm recovery it gives a new error,
"/System/bin/app-process" has unexpeted contents
E:error in /tmp/update.zip
PLEASE HELP ME ON THIS,SOMEONE SAID THIS MIGHT HAVE SOMETHING TO DO WITH XPOSED AND I SHOULD DELETE FRAMEWORK FIRST. not sure what he meant by remove framework.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
GMPOWER said:
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
Click to expand...
Click to collapse
Alright, thank you , I'll try to flash the ROM but if the same error appears again when I flash it I'll let you know.
Sent from my Nexus 7 using XDA Premium HD app
I have similiar issue on 2012 3g, stock, locked, no root, stock recovery. Did a side load, but during system verification i got "/system/media/bootanimation.zip" has unexpected contents. Error in /sdcard/0/ update.zip. (Status 7)". I'm on jrw66y tried to reflash, successfuly, tried 4.4 ota again, same error. I recived two OTA's for 4.3 and had no issues. I can understand errors for apks, but for a stock bootanimation i just can't... Does someone have a idea what next? Thanks in advance.
Востани Сербие, востани царице
GMPOWER said:
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
Click to expand...
Click to collapse
OK I reinstalled the old android 4.3 factory zip and then updated to the second 4.3 update and then the 4.4 , when I update I'm quarter way, it said error, boot animation has unexpected contents, I need the old boot animation back because when I turn on my nexus it doesn't have the traditional "x" boot animation anymore. I guess this new boot animation is from the JWR66V factory zip for rooted devices you gave me from before. Can you please give me the old boot animation file, I hope this is the only error I'm gonna get.
Sent from my Nexus 7 using XDA Premium HD app
Now You have same issue as i do. I tried to dig it from several roms but in vain - couldn't find appropriate. Next question is if i get that file, can i put it to /system/media w/o root. I think i can't. Anyway @GoldenNexus7, if You aquire that bootanimation pls notice me, I'll notice You if I get it first.
Востани Сербие, востани царице
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Will the flashing system.img and boot.img wipe the data?
Unlocking bootloader wipes data. Flashing system and boot won't . But, sometimes device won't boot if data is not wiped. Now, as i wage lurking around for a solution or rooting and wipe data, I'm much closer to 2nd solution.
Востани Сербие, востани царице
slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
I installed the OTA and I don't know what happened, I got stuck on the Kitkat logo screen (boot animation). I am unlocked and have CWM installed. Now I can't get past that screen. I can access adb and also CWM recovery.
I am also planning to try this method now. Is it okay if I have CWM Recovery installed? Do I have to remove it in order for this to work?
Loreane Van Daal said:
Now You have same issue as i do. I tried to dig it from several roms but in vain - couldn't find appropriate. Next question is if i get that file, can i put it to /system/media w/o root. I think i can't. Anyway @GoldenNexus7, if You aquire that bootanimation pls notice me, I'll notice You if I get it first.
Востани Сербие, востани царице
Click to expand...
Click to collapse
Not sure if it would make a big difference, it will probably give me a different error once I try to update to 4.4 again.
SIGH
Sent from my Nexus 7 using XDA Premium HD app
slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Which factory image should I download? Is it the kit Kat one?
Sent from my Nexus 7 using XDA Premium HD app
alfred_heaven said:
Will the flashing system.img and boot.img wipe the data?
Click to expand...
Click to collapse
No. "userdata.img" wipes your data. I had that fear, but no problem.
hardikrajgor123 said:
I installed the OTA and I don't know what happened, I got stuck on the Kitkat logo screen (boot animation). I am unlocked and have CWM installed. Now I can't get past that screen. I can access adb and also CWM recovery.
I am also planning to try this method now. Is it okay if I have CWM Recovery installed? Do I have to remove it in order for this to work?
Click to expand...
Click to collapse
The Factory Image include 4 files: boot.img, system.img, userdata.img (this wipes your data) and recovery.img (if you use a Custom Recovery, you don't have to flash this, if you don't, you must to flash it. In addition, your recovery isn't important. You only have to reboot your device in bootloader mode (Turn on pressing Power+VolUp+VolDown) and connect it to your PC. Finally you have tu follow the steps. Simply and clear. Your device has been updated.
GoldenNexus7 said:
Which factory image should I download? Is it the kit Kat one?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
You must to download KitKat image.
nakasi (Wi-Fi): https : // dl. google. com /dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
nakasig (3G): https : // dl. google. com /dl/android/aosp/nakasig-krt16s-factory-1e882585.tgz
Erase spaces. I can't publish links.
Hope this help you
slif24 said:
No. "userdata.img" wipes your data. I had that fear, but no problem.
The Factory Image include 4 files: boot.img, system.img, userdata.img (this wipes your data) and recovery.img (if you use a Custom Recovery, you don't have to flash this, if you don't, you must to flash it. In addition, your recovery isn't important. You only have to reboot your device in bootloader mode (Turn on pressing Power+VolUp+VolDown) and connect it to your PC. Finally you have tu follow the steps. Simply and clear. Your device has been updated.
You must to download KitKat image.
nakasi (Wi-Fi): https : // dl. google. com /dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
nakasig (3G): https : // dl. google. com /dl/android/aosp/nakasig-krt16s-factory-1e882585.tgz
Erase spaces. I can't publish links.
Hope this help you
Click to expand...
Click to collapse
For some reason I lost root, but my nexus 7 is still unlocked so I can root again using root tool kit.
Sent from my Nexus 7 using XDA Premium HD app
GoldenNexus7 said:
For some reason I lost root, but my nexus 7 is still unlocked so I can root again using root tool kit.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have the same problem. I've tried to flash it from Custom Recovery (TWRP) and no root. I'm investigating that. I post if I found a solution. Recovery maybe the guilty.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC
stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app
Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.
I still cannot root the Nexus10..
Any one can help?
Thanks in advance!
XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.
fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...
I'm looking at taking my Nexus 4 back to stock. I'm running TWRP, CM11, modified modem files, etc and for some reason I'm getting terrible battery life I'd just like to go back to stock. Can anyone tell me if I can keep root and Xposed and still get OTA updates?
Thanks
There is an app called OTA RootKeeper. Try it out, but from what I know this app doesnt support 4.3+
Instructions from Other Guides Available on xda
@jcicora Did you just want to flash stock radio and kernel? Or just wanted to start over with stock ROM?
Stock Radio and Kernel
Grab the official Android 4.4.4 image for the Nexus 4 here along with Android Studio here
Extract the occam-ktu84p-factory-b6ac3ad6.tgz and open folder to extract image-occam-ktu84p.zip
Open into platform-tools of Android Studio (Android Studio>sdk>platform-tools)
Copy radio-mako-m9615a-cefwmazm-2.0.1701.03.img and boot.img into platform-tools
Open command window inside platform-tools (Shift+Right click)
With USB Debugging enabled on your phone, use commands adb reboot bootloader, fastboot flash radio "radio.img", and fastboot flash boot "boot.img"
Stock ROM
Grab the official Android 4.4.4 image for the Nexus 4 here along with Android Studio here
Extract the occam-ktu84p-factory-b6ac3ad6.tgz
Open into platform-tools of Android Studio (Android Studio>sdk>platform-tools)
Copy all files extracted from occam-ktu84p-factory-b6ac3ad6.tgz into platform-tools
Open command window inside platform-tools (Shift+Right click)
With USB Debugging enabled on your phone, use commands adb reboot bootloader and flash.all
That's a lot of steps. Just extract the factory image, boot into the bootloader and double click the flash-all.bat while connected to your pc
Sent from my Nexus 5 using XDA Free mobile app
A Little OCD about my Files
@jd1639 Same thing! I just like keeping my things organized, so I keep all my img files, SuperSU, TWRP, and kernels inside of platform-tools folder.
To as answer the original question, rooted will let you get OTAs, xposed will cause them to fail - but you can just disable xposed then re enable after the update.
Sent from my Nexus 7 using XDA Free mobile app
Follow up question, this will completely wipe my phone right? "SD card" included?
jcicora said:
Follow up question, this will completely wipe my phone right? "SD card" included?
Click to expand...
Click to collapse
Yes. You might want to keep a backup.
kittuboy said:
Yes. You might want to keep a backup.
Click to expand...
Click to collapse
Ordinarily I would do a nandroid backup, however since I won't have a custom recovery is there another method I should use?
Titanium backup works great. Requires root.
Sent from my Nexus 4 using XDA Free mobile app
But will it create a file I can flash over to restore everything, ROM, recovery, apps, etc? Or should I just make a nandroid backup and use MTP to transfer it over to my pc?
A flashable zip is creatable, but Titanium Backup only back up applications and the data of the applications. Flashing the zip will restore your app and app data only. The only way to backup the ROM and all that other stuff is through a nandroid, which you said you don't have access to. In this situation I believe Titanium Backup is better than nothing.
Sent from my Nexus 4 using XDA Free mobile app
a
Hard
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.
Why not just download the image and flash it? Plenty of guides on how to do this
lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?
I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine
I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)
Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.
would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance
The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.
efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...
etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.