Hello,
This is probably a 'noobish' question but I'm a bit confused.
I have an AT&T Sonim XP8 that I flashed with this user debug image since the device got bricked so had to be re-flashed completely.
For reference, the bootloader is also unlocked.
Every time I try to update from AT&T Software Updater, the update downloads but the install will 'interrupt' and then if I try again it says the software is fully updated.
So I tried downloading the OTA updates from here but receive the error 'failed to verify whole-file signature' when I boot into recovery mode and try to install updates via adb.
So what I did next was factory reset the phone, run AT&T Software Updater with adb logcat running so I could try and capture the OTA update. I was able to, and this is the link if anyone wants it.
Then I booted into recovery mode and used this with the adb sideload command, and it still failed with the same failed to verify whole-file signature error. I was kind of confused why this would fail, considering that it's literally from the carrier.
If anyone could help me I would greatly appreciate it.
Related
I had the R33 and downgrade to TC4-RC30 to get my phone modded, now im trying to get the update HardSPL, and:
When I get into Recovery Mode, yes I have SU with the #, it states "E:Can't open /cache/recovery/command"
I try to update but it says:
E:No Signature (442 files)
E:Verification failed
and im also trying to update to multi-touch ,autorotate and new! JFv1.43 but i cant get passed this
RE update:
Just rename it to update not update.zip
I've spent lots of time looking through forums trying to answer/solve my issue so I hope it's not something stupid I've missed. Sorry for the trouble if it is though.
So, my issue is that I simply cannot unlock the bootloader of my Nexus S (i9020T). The phone's connecting to my computer via Samsung Android ADB Interface as seen under the Device Manager. I see the proper device ID when I type "fastboot devices" into the adb command prompt w/ phone in fastboot mode. Then, when I type "fastboot oem unlock" the phone starts the unlock verification process -- I select yes, the phone restarts, but it goes back to the stuck Google screen. Then, if I pull the battery and go into fastboot mode directly, bootloader's still locked. I've tried this quite a few times and same result -- same result trying to unlock w/ some of the toolkits here (WugFresh's NRT, m.sabra's root tool). Haven't tried Odin but from what I've read it would also require an unlocked bootloader to do anything. I've even tried a few other things like pushing recovery and bootloader images onto the phone via adb, but these also failed due to the locked bootloader.
I also cannot enable USB debugging under phone settings either b/c I now can't get past the Google logo/fastboot mode menu. Didn't think this was required to unlock bootloader though.
Background: Phone had the latest auto updated version of Android when the phone all of a sudden turned off in the middle of the night recently. Weird b/c the battery was basically full. It now always gets stuck on the Google logo upon normal restart. It goes into fastboot mode OK if I remove the battery and press power/vol. buttons -- I then first tried the restore and recovery functions there, etc, but no effect.
Any ideas? Or is the phone just dead now?
Thanks! :fingers-crossed:
Edit:
I've now tried what's described as a possible solution here: http://forum.xda-developers.com/showthread.php?p=44753413#post44753413. It didn't work since that also needs bootloader to be unlocked.
I've also tried to solve it w/ all versions of Odin. None of them detect my phone even after installing Kies w/ drivers. I think I have the required drivers though since I can command the phone fine through adb. And Odin should need bootloader unlocked to work anyway...
Edit 2:
To add, one of the first things I tried was to do a manual factory data reset in the recovery menu (selecting 'yes' to erase all data).
And I tried adb sideload of the OTA .zip file. But installation was aborted. The following appeared immediately under the regular adb sideload instruction in the system recovery menu (under "Now send the package you want to apply to the device..."):
Finding update package...
Opening update package...
Verifying update package...
Installing update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
Installation aborted.
Bump w/ more info.
i was on android 4.4 kitat but i wanted to go on 4.1 Jellybeans
so i try to downgrade it, i use Droid Razr Hd Utillity 1.21 to downgrade it to its stock firmware but phone is stuck and now if i try to put any firmware in it
Via RSD LITE its giving error "Failed flashing process 2/20 flash partition "gpt.bin" phone returned FAIL"
But if i try to put firmware Via RSD but with profile Universal its giving me error "Failed flashing process. 11/15 flash boot "boot.img" -> Phone returned FAIL"
i read it some where if i can create profile Via RSDScriptGenerator its gonna make 3 profile Full,Keep Data,Universal
and i have to use universal if i am trying to downgrade but its not working
i even try to put 4.4 in it again but its also not working phone is stuck on Fastboot Flash Mode for now
On other hand on phone error is
"downgraded security version
update gpt_main version failed
preflash validation failed for gpt
Partition (boot) Security version Downgraded
preflash validation failed for boot"
can any one help me because i think its soft bricked
You're getting the error because you tried to downgrade. Is your boot loader unlocked? If it's not, you can't downgrade. There's a thread in the general section with the latest FW, grab that and flash it, you should be good. If you're unlocked, you still need to correct the error. Flash the latest FW and use the guide in the general section to downgrade.
Sent from my HTC6525LVW using Tapatalk
Ok. I'm trying to install CyanogenMod 10.2.1 (From download.cyanogenmod.org/?device=d2vzw&type=stable) via Recovery via the second set of instructions at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw. This is because errors were made and I can only currently access Recovery mode and Download mode. I am not well-versed in this kind of stuff, I'm simply doing this because my phone is otherwise bricked.
In case it's important... My recovery mode differs from what the instructions seem to expect though: I have to select "Apply update from ADB." I send it to the phone using the command "adb sideload cm-10.2.1-d2vzw.zip" and the phone finds, opens, and attempts to verify the update package. That's where the snag is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Do I have a corrupted zip? Am I following the instructions wrong? Help!
Edit: I tried a different version of CM and got the same error.
KalininTest said:
Ok. I'm trying to install CyanogenMod 10.2.1 (From download.cyanogenmod.org/?device=d2vzw&type=stable) via Recovery via the second set of instructions at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw. This is because errors were made and I can only currently access Recovery mode and Download mode. I am not well-versed in this kind of stuff, I'm simply doing this because my phone is otherwise bricked.
In case it's important... My recovery mode differs from what the instructions seem to expect though: I have to select "Apply update from ADB." I send it to the phone using the command "adb sideload cm-10.2.1-d2vzw.zip" and the phone finds, opens, and attempts to verify the update package. That's where the snag is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Do I have a corrupted zip? Am I following the instructions wrong? Help!
Edit: I tried a different version of CM and got the same error.
Click to expand...
Click to collapse
If your phone is on 4.3 or 4.4.2 you cannot install a custom recovery or CM because your bootloader is locked.
Is there any way to unlock or replace the bootloader from Recovery, then? I tried forum.cyanogenmod.org/topic/67061-trying-to-flash-cm-on-d2vzw/#entry369787, but it just says, "error: closed" on the command prompt.
KalininTest said:
Is there any way to unlock or replace the bootloader from Recovery, then? I tried forum.cyanogenmod.org/topic/67061-trying-to-flash-cm-on-d2vzw/#entry369787, but it just says, "error: closed" on the command prompt.
Click to expand...
Click to collapse
As far as I know, there is no way to unlock or replace the bootloader
Hello friends!
I have been trying to install new Rom to Note 5 Sprint, used ODIN and after installing was successful, my phone went to "Android Recovery"
it says DM-Verity Verification Failed Need to check DRK first..
When i try to connect with my PC nothing happens, it cant see the device.
On my phone when i try to APPLY UPDATE FROM ADB- it says "Update from external storage is disabled"
Please help...
install a custom kernel.
What about if you are OEM locked? My device won't boot. Give the DRK message. What are my options? Is there any way to OEM unlock when the device won't boot. I can't flash a recovery or kernel unless it is stock. I have backup files for the EFS but my device won't connect to ADB. Help me please. Lol