software updates:signature verification failed - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

i have a sgs4 sprint rooted cwm recovery stock rom, and i am not able to install any software update i continue to receive this error:
E: invalid command argument
E: failed to verify whole file signature
E: signature verification failed
" / system/framework/ services.odex" has unexpected contents
E: error in/cache/e9fcadf8ac862c1b6c99b9fad69b16613a49a6a. user_L720_spt_NAE_csb_user_rp_to_ng2_csb_user_rp_update_fwd.zip status7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

reesemtk61 said:
i have a sgs4 sprint rooted cwm recovery stock rom, and i am not able to install any software update i continue to receive this error:
E: invalid command argument
E: failed to verify whole file signature
E: signature verification failed
" / system/framework/ services.odex" has unexpected contents
E: error in/cache/e9fcadf8ac862c1b6c99b9fad69b16613a49a6a. user_L720_spt_NAE_csb_user_rp_to_ng2_csb_user_rp_update_fwd.zip status7
View attachment 2916698
View attachment 2916699
Click to expand...
Click to collapse
The reason you can't install a software update is because you have to be bone stock. With no mods or custom recovery.
Sent from my SPH-L720

ROMANTiC KiD said:
The reason you can't install a software update is because you have to be bone stock. With no mods or custom recovery.
Sent from my SPH-L720
Click to expand...
Click to collapse
question is there a bone stock file i can flash or odin

reesemtk61 said:
question is there a bone stock file i can flash or odin
Click to expand...
Click to collapse
Look in development.

Related

[Help] Flashing an .SBF [Solved]

Solved by myself. Turns out I had to find and download RSDLite v5.4.4 and it instantly found my Xoom.
Okay, so I've followed the steps to revert back to HRI66 and relock my bootloader (I've also tried to do it on the same version, but with the unlocked bootloader).
I am using RSDLite v5.0 and the latest drivers from Motorola for USB connectivity.
I'm trying to flash the .SBF file from here, but RSDLite keeps giving me errors.
I am on Windows 7 64-bit, but I have also tried to do it on my laptop that has Windows XP 32-bit.
This is what it says when I first start up RSDLite:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it says when I hit "Show Device":
This is what it says when I try to hit "Start":
Any solutions?
This is what my error log is telling me:
23:55:36, October 18, 2011
Line: 2201
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
23:55:36, October 18, 2011
Line: 1041
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
Click to expand...
Click to collapse
I've never used RSDLite. Can you give a bit more detail about your solution?
okantomi said:
I've never used RSDLite. Can you give a bit more detail about your solution?
Click to expand...
Click to collapse
Well, there's really not much else to how I fixed it.
I tried using RSDLite v5.0, and a few other versions below it, and none of them were correctly identifying my Xoom. Then I found v5.4.4 and it worked perfect.

[Q]is it possible to downgrade CWM on SM-N9005 to fix E: signature check issue ?

Hello, I'm a complete noob here, however I have some technical skills and I have already rooted several android phones & tablets in the past.
With my latest device, I went through installation of latest CWM from chenglu n9005-cwm-recovery-6.0.4.4(1011).tar with Odin (both 1.85 and 3.09).
Everything went OK, phone boot normally and in recovery mode CWM seems ok.
However, when it comes to install a ZIP (for instance the root access package - UPDATE-SuperSU-v1.65.zip), the signature check do fail systematically with a E: signature verification failed. No matter the Zip, it ends up with the same error and the installation can't continue.
pic very related:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I have tried to disable MD5 signature check in CWM recovery, so far to no avail.
In This 6.0.4.4 (1011) CWM recovery, there is no way to disable signature check AFAIK. It is normally in the "install from sd card" submenu, but this menu entry is no longer present
So, as older CWM seems to operate correctly with signature check (or at least provide a way to disable it), I've tried to downgrade to an older CWM, for instance n9005-cwm-recovery-6.0.3.7-new-kernel(0925).tar which is confirmed to operate properly.
All the flashing process finishes without error, however I have still the same CWM version that doesn't work.
So Right now I have a phablet with CWM installed, but unable to install any packages. And very strangely, my Knox warranty void is still 0x00 after all this (see 2nd picture)
So, is there a way to disable signature check in the CWM I have used, or a way to downgrade the CWM ?
Thank you.
I have the same problem.

[HELP] Can't update phone after unroot

Unrooted my Samsung S8 running 8.0 and tried to update using smartswitch and am just met with a blue screen saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" i have tried doing that and (at the time of writing this) it has failed once, idk if i can boot to download mode and have tried but its either already in it or its just F'd up...
When i run Odin it says "Added" so thats a good sign right?
At the time of this im currently trying the recovery option so will see if this works...
UPDATE: This failed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tricksyz said:
Unrooted my Samsung S8 running 8.0 and tried to update using smartswitch and am just met with a blue screen saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" i have tried doing that and (at the time of writing this) it has failed once, idk if i can boot to download mode and have tried but its either already in it or its just F'd up...
When i run Odin it says "Added" so thats a good sign right?
At the time of this im currently trying the recovery option so will see if this works...
UPDATE: This failed:
Click to expand...
Click to collapse
Just flash the firmware you need through Odin. If you get any errors during flashing then post them here and I can help.

Need help。。Magisk faceback failed to mount vendor in TWRP。

Need help。。Magisk faceback failed to mount vendor in TWRP。
http://forum.xda-developers.com/nexu...nners-t3206928 Part 10 had finshed...Still reporting an error...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
foreverwithyou321 said:
Need help。。Magisk faceback failed to mount vendor in TWRP。
http://forum.xda-developers.com/nexu...nners-t3206928 Part 10 had finshed...Still reporting an error...
Click to expand...
Click to collapse
Did you flashed it directly after flashing ROM ? If yes then boot up the phone first and then go into recovery again and flash magisk .
hk1271 said:
Did you flashed it directly after flashing ROM ? If yes then boot up the phone first and then go into recovery again and flash magisk .
Click to expand...
Click to collapse
After booting,flash magisk ,Still showing this error~~~~
foreverwithyou321 said:
After booting,flash magisk ,Still showing this error~~~~
Click to expand...
Click to collapse
Which version of twrp are you using ?
Vendor issue easy FIX
download SKIPSOFT TOOL.
HTML:
https://forum.xda-developers.com/nexus-6p/orig-development/tool-skipsoft-android-toolkit-nexus-6p-t3234159
Processes straight forward and later I chose option 9 (restore phone to default) - that how i fixed /vendor image.
Do not ask step by step.
hk1271 said:
Which version of twrp are you using ?
Click to expand...
Click to collapse
3.3.1

《ABANDONED》 ( Updated) Qrom for 105M A10 and A series devices

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thi series of roms is focused tu gain more performance for this series and add some other features to the rom, all of them are based in latest firrmware for each
How To install:
1) install TWRP for your device
2) enter in advance wipe and wipe dalvik, system,data,internal storage and cache
3) format data partition
4) flash the rom
5) 4) flash DM-verity
6) enjoy!!
A10:
Download: mediafire
A20:
Download:mediafire
A30:
Download:mediafire
A30s:
Download:mediafire
A50:
Download:mediafire
A70:
to boot it must format data after install the rom
Download:mediafire
ROM OS Version: 10
ROM Kernel: Stock
ROM Firmware Required: Stock Android 10
Status: Stable
Created 31-08-2020
Last Updated 29-11-2020
In orden to boot the rom you need to flash DM-Verity after install the rom
Telegram Group for support and updates
Is it flashable via Odin or do we have to flash it via TWRP Recovery?
TWRP Recovery !!
1CTea said:
Is it flashable via Odin or do we have to flash it via TWRP Recovery?
Click to expand...
Click to collapse
Flash via TWRP Recovery !!
bro it says failed to mount '/vendor invalid argument
juan29122003 said:
bro it says failed to mount '/vendor invalid argument
Click to expand...
Click to collapse
go it!! fixing and updating, thanks for the report
Thanks for the ROM but I am getting INFINITE LOOP after install. The 705MN

Categories

Resources