This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Your post says 'PC can find the device' but I assume you mean 'PC cant find the device'.
So you have a custom recovery, are you also rooted? A custom recovery means an OTA update wont work. You need the stock recovery. I assume the custom recovery has caused the update to fail in such a way that it just keeps rebooting.
Can you manage to get into CWM via the bootloader (ie choose recovery from bootloader options using volume buttons), if so then wipe cache as this will remove the update file and you should be OK then.
If not then I think you need to get the phone seen by the PC when in the bootloader as otherwise you are stuck. I assume at some point it was seen by the PC for you to install CWM?
If running Windows do you still have the drivers installed (I run linux so Im unsure what you would need). I assume a 'fastboot devices' shows no device at all from what you say?
If you can get fastboot working you can then flash back the stock recovery and this may then allow the update to get past the point its failing at, it may still fail but then you can take it from there.
But first try getting to CWM via bootloader and wiping cache and then reboot.
scott_doyland said:
Your post says 'PC can find the device' but I assume you mean 'PC cant find the device'.
So you have a custom recovery, are you also rooted? A custom recovery means an OTA update wont work. You need the stock recovery. I assume the custom recovery has caused the update to fail in such a way that it just keeps rebooting.
Can you manage to get into CWM via the bootloader (ie choose recovery from bootloader options using volume buttons), if so then wipe cache as this will remove the update file and you should be OK then.
If not then I think you need to get the phone seen by the PC when in the bootloader as otherwise you are stuck. I assume at some point it was seen by the PC for you to install CWM?
If running Windows do you still have the drivers installed (I run linux so Im unsure what you would need). I assume a 'fastboot devices' shows no device at all from what you say?
If you can get fastboot working you can then flash back the stock recovery and this may then allow the update to get past the point its failing at, it may still fail but then you can take it from there.
But first try getting to CWM via bootloader and wiping cache and then reboot.
Click to expand...
Click to collapse
Thank you for your quick reply.
Correct. I mean the PC can't find the device. However via Motorola Device Manager it can.
Yes the phone is rooted
I can't get into the CWM. If I choose recovery from the bootloader, it reboots normally...and the loop starts again...
will try the fastboot.
How are you trying to choose the recovery option from the bootloader?
You MUST select recovery option using the VOLUME UP button (volume down to move between options and volume UP to pick an option).
Do NOT use the power button.
scott_doyland said:
How are you trying to choose the recovery option from the bootloader?
You MUST select recovery option using the VOLUME UP button (volume down to move between options and volume UP to pick an option).
Do NOT use the power button.
Click to expand...
Click to collapse
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
Sent from my Moto G using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
irishpancake said:
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
I think its also important in Windows, to use the Moto fastboot.....when flashing recovery from BL!!!
(search forum for mfastboot.....)
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto G using Tapatalk
...I think I found the problem or better the solution...
As soon as I added AdbWinUsbApi.dll my PC could find the device...at the moment I'm flashing stock recovery. Hopefully this will help. Keep you posted guys! :good:
dutchxl said:
...I think I found the problem or better the solution...
As soon as I added AdbWinUsbApi.dll my PC could find the device...at the moment I'm flashing stock recovery. Hopefully this will help. Keep you posted guys! :good:
Click to expand...
Click to collapse
If you are rooted it will still fail to update. You are best off just clearing cache via recovery. Or delete zip file (if you get booted up) from /cache using a root file explorer.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
irishpancake said:
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
Sent from my Moto G using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
motofastboot is a modified fastboot that allows larger images to be flashed. Normal fastboot will work fine for recovery AFAIK.
scott_doyland said:
If you are rooted it will still fail to update. You are best off just clearing cache via recovery. Or delete zip file (if you get booted up) from /cache using a root file explorer.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
motofastboot is a modified fastboot that allows larger images to be flashed. Normal fastboot will work fine for recovery AFAIK.
Click to expand...
Click to collapse
It's just that mfastboot is recommended by most devs, including Paul O'Brien and flibblesan, on Modaco, and loads of ppl here on XDA, for flashing FW to Motorola devices from BL, so I'd go with it, as it is widely available on either Modaco or XDA.
I don't think an OTA will fail due to root, just if you have modified or removed any system files, or are using a custom recovery.
I think you have to re-root after OTA is applied.
Rooting at 4.4 is easy with Chainfire's SuperSU CWM flasable zip, as explained by flibblesan here:
http://www.modaco.com/topic/368168-how-do-i-root-android-44-kitkat/#entry2188450
flibblesan, on 11 Jan 2014 - 5:05 PM, said:
Easiest way to root would be to boot a custom recovery and flash Superuser through that.
A new build of CWM recovery compatible with 4.4 bootloaders can be found here http://forum.xda-developers.com/showpost.php?p=49333040&postcount=123
Download superuser from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
flash recovery with the special motorola fastboot like
Code:
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
irishpancake said:
It's just that mfastboot is recommended by most devs, including Paul O'Brien and flibblesan, on Modaco, and loads of ppl here on XDA, for flashing FW to Motorola devices from BL, so I'd go with it, as it is widely available on either Modaco or XDA.
I don't think an OTA will fail due to root, just if you have modified or removed any system files, or are using a custom recovery.
I think you have to re-root after OTA is applied.
Rooting at 4.4 is easy with Chainfire's SuperSU CWM flasable zip, as explained by flibblesan here:
http://www.modaco.com/topic/368168-how-do-i-root-android-44-kitkat/#entry2188450
Click to expand...
Click to collapse
superSU updates /system/etc/install-recovery.sh
This file is checked for a hash by the script (updater-script) that installs the update. As the file is different then the script bombs out with an error.
I know this because I am rooted and I by mistake attempted to install the OTA when I got the OTA notification. It failed.
There is a line in the updater-script like this:
apply_patch_check("/system/etc/install-recovery.sh", "b54528cf9ebba39534b768ad9108a4732e1eff4a", "99ffe4a3d0e6612e87cd3f6a62dad642094f0169") || abort("\"/system/etc/install-recovery.sh\" has unexpected contents.");
This is basically checking that file and seeing if it has the expected hash (one/both of those long numbers are the hash).
Interestingly the ORIGINAL install-recovery.sh file has these comments at the start of the file:
# File Name: install-recovery.sh
#
# General Description: This script is used to install software update for
# recovery mode after OTA update. This is modified
# from original Google code to split the code into
# a fixed program while putting the dynamic data
# into a config file.
After superSU is flashed it says stuff about superSU in it and the file is completely different hence why if you are rooted (at least if using superSU) then the update fails. Whether there are also other /system files also updated by rooting I dont know.
I dont know why superSU modifies the file, the file once modified kicks off a daemon called daemonsu. Why it has to be this file to start that deamon I dont know - but obviously there must be some reason its rooted in this way.
scott_doyland said:
superSU updates /system/etc/install-recovery.sh
This file is checked for a hash by the script (updater-script) that installs the update. As the file is different then the script bombs out with an error.
I know this because I am rooted and I by mistake attempted to install the OTA when I got the OTA notification. It failed.
There is a line in the updater-script like this:
apply_patch_check("/system/etc/install-recovery.sh", "b54528cf9ebba39534b768ad9108a4732e1eff4a", "99ffe4a3d0e6612e87cd3f6a62dad642094f0169") || abort("\"/system/etc/install-recovery.sh\" has unexpected contents.");
This is basically checking that file and seeing if it has the expected hash (one/both of those long numbers are the hash).
Interestingly the ORIGINAL install-recovery.sh file has these comments at the start of the file:
# File Name: install-recovery.sh
#
# General Description: This script is used to install software update for
# recovery mode after OTA update. This is modified
# from original Google code to split the code into
# a fixed program while putting the dynamic data
# into a config file.
After superSU is flashed it says stuff about superSU in it and the file is completely different hence why if you are rooted (at least if using superSU) then the update fails. Whether there are also other /system files also updated by rooting I dont know.
I dont know why superSU modifies the file, the file once modified kicks off a daemon called daemonsu. Why it has to be this file to start that deamon I dont know - but obviously there must be some reason its rooted in this way.
Click to expand...
Click to collapse
Thanks for that info......a bit complicated, but I get the gist of why OTA will fail, if rooted using the SuperSU Recovery zip.
I suppose, as you will be un-rooted in any case, unrooting prior to OTA is advisable, I can see that....
when I rooted originally, I used Superboot, as per Paul's Option 1
However, as per the OP, and my attempted OTA, with CWM Recovery intact, and the bootloop problem, etc, etc...and my panic, and not reading what is written in BL....
I never got to flash the OTA, and I just went ahead and learned how to use fastboot, and downloaded the American ROM, flashed it, and CWM Recovery, which works with 4.4 now, and flashed the root zip, as above, and some other zip to give back the H+ for HSPA+ logo, and now I'm happy.....
I'll never have another OTA to deal with now......
When stuff goes wrong we all learn a lot more than if it always went to plan, so its good we have learnt some new things today.
When 4.4.3 is out it'll all be easy now
Everything is working again! With AdbWinUsbApi.dll I could find my device and flash it. And with the help of this topic http://forum.xda-developers.com/showthread.php?t=2542219 I was able to restore the firmware as it was...nearly...I had a Dutch (EU) version, now it's US...no big deal.
dutchxl said:
Everything is working again! With AdbWinUsbApi.dll I could find my device and flash it. And with the help of this topic http://forum.xda-developers.com/showthread.php?t=2542219 I was able to restore the firmware as it was...nearly...I had a Dutch (EU) version, now it's US...no big deal.
Click to expand...
Click to collapse
Man....you did what I did, and ended up with US 4.4.....
I had UK Tesco 4.3, with an OTA sitting in \cache, but tried to flash with CWM Recovery, messed up, panicked, but things are good now, latest CWM, rooted with SuperSU.
There is also a CWM zip to restore your H indicator for HSPA mobile speed, as US ROM only has 3G for this, and it also modifies the cell signal bars back to normal Android width.....
SystemUI_AOSP_Statusbar-signed.zip
Thanks to tilaz and flibbelsan on Modaco
Good luck from here on,
dutchxl said:
This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Click to expand...
Click to collapse
I had the same situation just now. Accidentally confirmed the OTA update prompt, then the phone goes bootloop. After fiddling here and there, turns out the solution was simple. Reboot to bootloader, connect usb to PC, then wipe the cache using fastboot (fastboot erase cache). It will remove the OTA update zip file and stops the bootloop. Now I need to disable OTA update prompt.
just got the same problem!
solution that worked with me: booted in recovery, connected to pc, [left shift]+[right klick] on folder that contains mfastboot.exe, open prompt, type "mfastboot erase cache". done!
system update is now stopped
dutchxl said:
This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Click to expand...
Click to collapse
dutchxl said:
This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Click to expand...
Click to collapse
i repost a solution i have found to install OTA without wiping data, loosing root or flashing stock rom
http://forum.xda-developers.com/showpost.php?p=50513733&postcount=9
black screen after motorola logo
irishpancake said:
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
Sent from my Moto G using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
i am having black screen issue on my MOTO G means i have installed some wrong package.... and it does not start only black screen...after a motorola starting logo so what should i do and my phone is not unlocked bootloader....please i need some serious help im getting error while installing new package via ADB is like " /system/lib/rfsa/adsp/libadsp_denoise_skel.so" has unexpected contents. and then installation aborted"" please help me!!! my phone is on XT1033 dual sim and is on 4.4.4 version when i done all this madness... for unlock bootloader.of this device please help!!! thank you!!!
same problem
bro same problem with me . what should i do now?
I had the exact same problem. Luckily I had the backup and entered the recovery mode of philz touch 6 clockworkmod v6.0.4.7 and recovered.
But I want to know, how to update the unlocked bootloader & rooted moto g xt1033 ? I'm using custom rom, its just unlocked.
Hi
I have a Samsung G920FD mobile phone. It's a few days now that I have the problem of Boot Loop and displaying the phrase "No command". I searched a lot over these days and tried different solutions. But I did not get any results.
I installed many ROM types by odin and twrp, but I did not get any results.
When I install the new ROM using Odin, after the restart, the message "Install System Update" appears, and it progresses to 32%. But then the Erasing message appears and the system will reset, and from then on, enter the Boot Loop phase.
In addition, these terms are written in Download mode:
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
Secure Download: Enabled
Please guide me to solve this problem! Thanks
Just root it via CF-Auto Root.
It will fix this issue.
forumber2 said:
Just root it via CF-Auto Root.
It will fix this issue.
Click to expand...
Click to collapse
Thank you!
I did. But it not work.
Try to flash stock with pit repartition
johnny.goldy said:
Try to flash stock with pit repartition
Click to expand...
Click to collapse
Hi.
again. on 32% of "installing update" failed.
khosravimm said:
Hi.
again. on 32% of "installing update" failed.
Click to expand...
Click to collapse
Did you wipe data/factory reset after flashing?
johnny.goldy said:
Did you wipe data/factory reset after flashing?
Click to expand...
Click to collapse
I did before any flashing.
But after the flash, it immediately restarts and the update installation process begins.
So, if unchecked the auto-boot option, then I need to restart manually.
There is no way to shutdown in download mode so that you can enter recovery mode.
Therefore, I can enter the recovery mode only after the first restart
An important point. My phone has been in the hands of a friend for a while. After that, the problem occurred and I did not know the latest version of the ROM installed on it.
Why always happen at 32%?
"no command" error
installing android 7.0 but everytime it auto enter in recovery mode with "no command" error even that i can't enter into recovery mode no wipe cache option / data factory restore and looping itself
Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
E:failed to clear BCB message: failed to fin /misc partition
Click to expand...
Click to collapse
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!
normsrayn said:
Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!
Click to expand...
Click to collapse
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Just download the latest version of the file (6.0)
Now wait until rom boots
-----------------------------------------------------------------------------------
Please donate and like if you think i deserved it,
If it didnt work you don't have to do it
Happy flashing and good luck
Dont forget to update me after following the steps
I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!
normsrayn said:
I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!
Click to expand...
Click to collapse
Flash the stock firmware again but from download the firmware from Samfirm application. Please use the HOME_CSC too or your device is wiped. If you need the firmware just post modelnumber or name idk and CSC code and i can post a link with the firmware for you. TWRP can't mount /data and you will need to format your phone with means you lose everything.
getting dark error in galaxy j4 smj400F after system update failing
Picklewickle said:
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
but i have done factory reset so how to enable oem /unlock bootloader to flash via odin
HELP
-----------------------------------------------------------------------------------
Click to expand...
Click to collapse
Same issue
I have the same issue. I cant boot into download mode at all to even attempt to flash anything