[Q] Rooted Nexus 5 - 4.4.3 Cannot apply system update - Nexus 5 Q&A, Help & Troubleshooting

System update cannot be applied:
1) download system update
2) tap reboot and install
3) start installation
4) got error message "Error!" after 5 seconds
/system/bin/app_process has unexpected contents
E:Error in /cache/blablablanumbershere.signed-hummerhead-KTU84M-from-KOT59H.d174d546.zip
Status 7
1) Tried to wipe cache data
2) Then install ADB update - not success after an hour
Did somebody have the same problem?

Hey, hope this help.
Install this from the play store
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Use it ONLY to install the recovery at this stage.
After it's done reboot, make sure you're still rooted.
Apply update as per normal, should work with this new recovery .

yons88 said:
System update cannot be applied:
1) download system update
2) tap reboot and install
3) start installation
4) got error message "Error!" after 5 seconds
/system/bin/app_process has unexpected contents
E:Error in /cache/blablablanumbershere.signed-hummerhead-KTU84M-from-KOT59H.d174d546.zip
Status 7
1) Tried to wipe cache data
2) Then install ADB update - not success after an hour
Did somebody have the same problem?
Click to expand...
Click to collapse
If you're rooted, do not bother wasting time with OTA updates
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.

Related

If I can get into the Fastboot screen I am not fully bricked??

I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.
give members more details [what did u flash etc], so they can help u.
No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard
I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access
I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND
magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.
This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:

I think failed rooting on N5 causes issues

I flashed, unlocked and tried to root my phone with this guide:
http: //wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
Why I think rooting failed is that that I followed the guide through to the last step and after the last step clockwork mod said that rooting failed and I had two options to root or go back (but judging by the system messages the SU zip was installed). I think here I made the mistake to choose rooting "again". I read later in another guide but concerning twrp that this situation where the SU zip gets installed but the message says Installation failed a bug is and that I should not do what I did.
Anyway root was not achieved as I checked with the root checker app. The recovery mode now looks a bit strange. And I cannot install the current patch for marshmallow because it is an unsigned zip.
Where do I go from here reflash the recovery? And install SU again
Flash twrp, then flash the latest supersu from twrp.
will this wipe my device?
No, it should not wipe the device.
If there is data on your phone that needs to be saved, you could try flashing TWRP, boot to TWRP, mount the data partition, and copy the required data to a computer. Once copied, flash supersu and try to boot.

Stuck on bootloop TWRP without decryption, help.

Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
sapalot said:
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
Click to expand...
Click to collapse
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
reaper000 said:
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
Click to expand...
Click to collapse
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
sapalot said:
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
Click to expand...
Click to collapse
Don't mess with stock recovery if you already have TWRP and Magisk aboard.
Here's how to update to 9.5.9 (or whatever) when it arrives:
- download your 3 zips: the latest full ota ROM, the latest Magisk, and the latest TWRP installer.
- boot to TWRP recovery
flash the ROM and TWRP installer
- reboot to TWRP recovery
flash Magisk
wipe dalvik
- reboot to system
There's a possibility after these steps and you're happily on the ROM, you might find that you're not rooted (it's more likely on a custom ROM than OOS). In which case you just reboot to recovery and flash Magisk, and then reboot to system. Done.
Discussion:
If you want a clean flash, you'd simply do a TWRP factory reset (standard wipe) instead of wiping dalvik.
Consider flashing both slots (A and B) whenever you update OOS, for two reasons. First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base. The second reason is more compelling: the way the data partition changes encryption every update has obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck

lineageOs 17.1 oct 4 2020 update issues.

Hi; just a heads up I'm running 17.1 rom on moto xplay 1562 i think it is north america version p2c is hardware verrsion.
on the latest update from installed os it just downloads gets to 99% then verifies and shows download on install it does first reboot then shows installing icon then screen goes blank hold power screen comes back shows same installing icon goes a bit then screen shuts off.
I have to hold down power button till it reboots and delete download if it's still there. 2nd time i did this it was not.
have extra mem card installed. no twrp .
Don't forget to back every partition.
[/COLOR]Clear cached data system and dalvic then install and reboot.
whats your recovery? lineage-recovery?
the update is ota? or are you trying to install it manually?
for me ota works without problems!
R!ffRaff said:
whats your recovery? lineage-recovery?
the update is ota? or are you trying to install it manually?
for me ota works without problems!
Click to expand...
Click to collapse
it's via wifi for me .
Androvishal said:
Don't forget to back every partition.
[/COLOR]Clear cached data system and dalvic then install and reboot.
Click to expand...
Click to collapse
i'll have to try this and go step by step
thak you all btw
thank you all btw
Hi; I got it to work after a wipe of the device just twrp issue now . it is replaced by LineageOS recovery on reboot after flash
dnickel said:
Hi; I got it to work after a wipe of the device just twrp issue now . it is replaced by LineageOS recovery on reboot after flash
Click to expand...
Click to collapse
the recovery is only activated when updating if this is set in the developer option.
for me the lineage recover works for ota. with twrp there is a bug since may what the image no longer starts after update.
either use older recovery or the latest from lineage. you can also use the twrp to save, install and set up everything. when that is done and running you can create a backup and then install the lineagerecovery as a zip. so ota works and has a backup.
alternatively you can also install the lineage recovery and only start the installation / backup twrp via adb / fastboot.
if you want to install the recovery you have to execute this command:
Code:
fastboot [B]flash[/B] twrpname.img
if you want the recovery boot you have to execute this command:
Code:
fastboot [B]boot[/B] twrpname.img
I hope it helps you a bit
freak sorry this is old now jeez .can close. this went way beyond this and back to 17.1

2022 SM-G930V Update To Latest Firmware And Keep Root Rev4-Rev10/A Odin Flashable

This Will Safely Update Your Rev4 Through Rev10/A Firmware To Last Build Released G930VVRSBCTC1 And Allow You To Keep Root With Odin Flashable Firmware. This Will Only Update Firmware That Is Safe To Update And Keep Current Bootloaders​Root For Rev11/B Bootloader Can Be Found Here
​Downloads:
G930VVRSBCTC1.7z​USERDATA_AIO_G930_REV4_10_PERSIST_ROOT_11_01_22.tar.md5 --This is file that roots the phone​Odin3_v3.14.1_3B_PatcheD.7z​Verizon S7 Edge Files Found Here
Instructions For Installing New Firmware And Rooted All At Once This Will Wipe Phone
1. Reboot phone too download mode Pwr + VolDwn + Home
2. Load Firmware in appropriate slots use regular CSC file not Home CSC and load Userdata file in the UserData slot in odin and flash
3. Phone will reboot too recovery and process the csc files then reboot on its own
4. When phone reboots back too recovery and you see the error screen then the recovery options screen you will need too Wipe Data/Factory reset.
5. Click reboot system.
6. Go through setup and check that you are rooted.
Rebooting Too Safestrap Recovery
1. Reboot phone as you would too boot stock recovery Pwr + VolUp + Home. It takes up too 40 seconds too boot recovery. Ignore the mount system errors on info screen
2. Enter recovery.
3. Too leave just reboot system ignore no system installed message if you get it
4. There is screen lag issues on scrolling in recovery. There is aroma file manager that takes care of this issue while in recovery but selecting zips too install may present a problem for this you can use the kernel manager recovery flash option while phone is booted too system. Simply select zip too flash and phone will reboot too recovery and flash it and reboot back too system. Most other function in recovery should work the issue is just scrolling too select files.
5. Flashfire is installed as an alternative as well
Features:
1. SuperSu Root- Do not try and update to make disable app notifications too get rid of update notice.
2. Safetrap recovery-Still working out scrolling issue
3. Flashfire
4. Kernel tweaks CPU governor set too Conservative
5. Entropy/Swapiness set to High
6. Build Prop tweaks to combat lag
7. Bloat removed from rom
8. Knox removed from rom
Bugs:
Eng Boot Image causes lag
Safestrap Recovery has scrolling issues
Random Reboots will most likely happen
Safetynet will not pass
Battery life may not be optimal
SuperSu cannot be updated
Flashfire may need date changed too 2016 to function if it just keeps closing on you
mine
I have not rooted my phone yet. Odin always fails for me. Do I need to remove the FRP lock first or something?
error
sw rev check fail : [boot]Fused 11 > Binary 10​
my version is R16NW.G930VVRSBCTC1
baseband G930VVRSBCTC1
model number SM-G930V
Hardware version REV0.6
I guess I have bootloader 11 (B). I think this means no root unless I have marshmallow combination rom. I guess I cannot install a LineageOS rom since there is no twrp for 11/B?

Categories

Resources