Database Users

After Rooting my Nexus S, my phone freezes on reboot.

This may be a noob question but i am concerned that i may have bricked my phone.
I followed this guide
http://forum.xda-developers.com/showthread.php?t=878446
with the exception that i downloaded recovery-clockwork-3.0.2.4-crespo.img
and used that instead of the 3.0.0.0 the guide says to use...
unfortunately when i finish doing the steps in the guide, when i reboot the phone, it's stuck on the google with the open padlock image. I have been waiting 30 minutes and no change.
my phone is a rogers nexus s running 2.3.3.
can anyone help me?

mm144 said:
This may be a noob question but i am concerned that i may have bricked my phone.
I followed this guide
http://forum.xda-developers.com/showthread.php?t=878446
with the exception that i downloaded recovery-clockwork-3.0.2.4-crespo.img
and used that instead of the 3.0.0.0 the guide says to use...
unfortunately when i finish doing the steps in the guide, when i reboot the phone, it's stuck on the google with the open padlock image. I have been waiting 30 minutes and no change.
my phone is a rogers nexus s running 2.3.3.
can anyone help me?
Click to expand...
Click to collapse
If your phone powers on, it isn't bricked...
power up the phone holding the power button and volume up and tell me what happens.

it goes into the bootloader.
saying it is in fastboot mode, and is unlocked.

mm144 said:
it goes into the bootloader.
saying it is in fastboot mode, and is unlocked.
Click to expand...
Click to collapse
Yeah you're fine. Just flash recovery again.
Open terminal
cd to the directory where fastboot is
./fastboot devices (to verify your phone is connected)
./fastboot flash recovery recovery.img (the recovery image needs to be in the same folder you cd to, where fastboot is)

ok then. I downloaded a new recovery file 3025-i9020.img based on this forum:
http://forum.xda-developers.com/showthread.php?t=1031760
and installed the su-2.3.6.1-ef-signed.zip
and it still doesn't go beyond the google and the padlock screen.
in fact, now, my carrier info is wrong. the bootloader detects my phone carrier as att...

mm144 said:
ok then. I downloaded a new recovery file 3025-i9020.img based on this forum:
http://forum.xda-developers.com/showthread.php?t=1031760
and installed the su-2.3.6.1-ef-signed.zip
and it still doesn't go beyond the google and the padlock screen.
in fact, now, my carrier info is wrong. the bootloader detects my phone carrier as att...
Click to expand...
Click to collapse
Okay, so the recovery image is flashing fine.
What model is your phone? Is it i9020?
Flash a stock ROM for your model.

I've been trying to, however, whenever i try to install a rom (any rom) from the recovery...
i get this:
E:connot find misc
finding update package...
opening update package...
installing update...
assert failed: write_raw_image("/tmp/boot.img". "boot")
E: Error in /sdcard/rom.zip (status 7)
installation aborted.
I should also note that i now get errors popping up every time i use a menu item in recovery.
the error stems from can't mount /cache/recovery/last_log
Also i am 100% certain i have a GT-I9020A as i found my manual.

mm144 said:
I've been trying to, however, whenever i try to install a rom (any rom) from the recovery...
i get this:
E:connot find misc
finding update package...
opening update package...
installing update...
assert failed: write_raw_image("/tmp/boot.img". "boot")
E: Error in /sdcard/rom.zip (status 7)
installation aborted.
I should also note that i now get errors popping up every time i use a menu item in recovery.
the error stems from can't mount /cache/recovery/last_log
Also i am 100% certain i have a GT-I9020A as i found my manual.
Click to expand...
Click to collapse
Hmm, that's a weird issue. Go to mounts and storage and make sure everything is mounted. If it still doesn't work, try redownloading the recovery and flash again.

I just wanted to post that i redownloaded recovery and su and did it all over again and it worked. must have had corrupted files. thanks.

mm144 said:
I just wanted to post that i redownloaded recovery and su and did it all over again and it worked. must have had corrupted files. thanks.
Click to expand...
Click to collapse
Great to hear. Make sure to check md5

mm144 said:
in fact, now, my carrier info is wrong. the bootloader detects my phone carrier as att...
Click to expand...
Click to collapse
FYI, it's supposed to say ATT if you have a Rogers phone. It just means the phone is using the AT&T band (same as Telus, Fido, Koodo, Bell, etc). If you have a Wind or Mobilicity Nexus S it will say something like TMO for the T-Mobile band.

Update Signature Verification Failed | Restoring ADB Backup on v4.4.2 GT-i9505

RE: "Update Signature Verification Failed"
I've searched and read the other topics.. One person responded to someone else's question that there are "hundreds of answers on this", yet only 2-3 topics with a related subject and posts. None that say they found the solution mention the topic that held the magic solution, and topics discuss other issues being the cause which don't match my scenario...
PROBLEM:
In Android System Recovery mode on KOT49H...... and attempting to recover an ".ab" backup made via command prompt on the computer with ADB from 2012 I used with a Sony Tablet S...
Using the command prompt, the restore completes after only a minute or so, and then the phone thinks the restore was successful... Tried cmd command prompt method both via Android and Recovery.
Size is 416 MB (436,330,412 Bytes) or 426 MB in Windows. Device has lots of free space - over 2GB.
I've tried Sideloading the restore in Recovery mode.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb sideload Samsung.S4.v442.2015.05.01.Backup.ab
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
C:\Users\User\AppData\Local\Android\android-sdk\platform-tools>adb restore Samsung.S4.v442.2015.05.01.Backup.ab
Now unlock your device and confirm the restore operation.
< click button on device to continue >
< then nothing! >
Click to expand...
Click to collapse
The backup has resided on my PC since it was created via ADB. Is it a USB-related problem? I have attempted recovery via 2 x USB cables: 1 x Premium USB 2M cable plus 1 x Cheap 1M USB cable. hmmm...
??? Ideas? The '.ab' file backup is from 8 months ago on the SAME OS version and system. It is a stock ROM.
Help! Can anyone share their '.ab' backup from a Samsung Galaxy S4 GT-i9505??? e.g. I9505XXUGNH6? (OPS?)
Thank you!

Normally you can just flash the backup with a custom recovery like TWRP.
I don't have any experience in making and restoring backups with the method you used. You could try to see if you can flash it with TWRP.
Why don't you just flash a stock rom with Odin? Are there files in the backup you need? If so, then you can just extract the files you need on your pc.
e.g. http://forum.xda-developers.com/showthread.php?t=2011811

adb sideload "Zip signature verification failed!"

I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.

Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.

v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?

D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?

5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.

D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.

How to get past
adb sideload "Zip signature verification failed!"​Disable signature verification

xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"​Disabilita la verifica della firma
Click to expand...
Click to collapse
How?

FUBAR - Bricked - Cannot enter Fastboot - Only Stock TWRP

Hello, I am in bad shape, this never happened to me before,
I own a A2017G and I tried to go to Nugart. But every thing went south and FUBAR.
I do not know how to fix it. The problem is that I cannot do a adb reboot edl and option 2 pushing +- does not get me into EDL either.
Therefore I cannot instal TWRP and I have the stock and I get the linux pinguin.
1. I tried to upload into the sd card a update.zip with a stock 09 but the Stock TWRP tells me that I cannot install from SDcard
2. I go to install through ADB , and that gets me into sideload.... however every file I try to update which is large 2.5gig fails and the small ones (recovery.img in a zip) tells mes that I have the wrong header.
What can I do?
Is there a way of sideload twrp???
Thanks for any support!!!

The error I get when uploading a Zip through TWRP from ADB:
Finding update package...
Opening update package....
Verifingy update package....
E: footer is wrong
Update package verification took 0.0 s (result 1)
E: Signature verification failed
Instalation Aborted

https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552

marcus.linkenbach said:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Click to expand...
Click to collapse
I new te risks.. I am willing to brick... Done it 1000 of times in my first xperia x10, xperia Z2 and ZTE axon 7...just the first time I do not know if to fix it...
If I just get into edl.... No pain no gain

Let me know if it worked for you.

marcus.linkenbach said:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Click to expand...
Click to collapse
Like always there is away, knowledge is the power to do things that others cannot

j77moduss said:
Like always there is away, knowledge is the power to do things that others cannot
Click to expand...
Click to collapse
The magic words... Usb modified cable.. Deep flash cable...
This will allow me to get into Edl and re flash TWRP and flash a zip and be safe...
Knowledge is blitz!!!

Unable to sideload LineageOS 19.1 to my LG G6

Hi! I'm currently trying to revive an LG G6 that I had lying around and was pleasantly suprised that there are recent builds of LineageOS available for the device.
Steps I took:
Download latest build (lineage-19.1-20230529-nightly-h870-signed.zip), boot.img and recovery.img
Installed boot image via `fastboot flash boot boot.img`
Installed recovery via `fastboot flash recovery recovery.img`
Reboot via `fastboot reboot`
Boot into recovery (via Vol Down + Power, Release Power, press power againg)
In Lineage Recovery, choose Apply update and Apply from ADB
Sideload image via `adb sideload .\lineage-19.1-20230529-nightly-h870-signed.zip`
Upload starts but stops at ~47%
Error message shown on phone:
Code:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 39,4 s (result 0):
Installing update...
Comparing TZ versions:
Max TZ version: TZ.BF.4.0.1-1865684
assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1"
E:Error in /sideload/package.zip (status 1)
Does anybody have an idea what could be the problem here? I had an older version of LineageOS installed on the device (bootloader is still unlocked), but I completely wiped the device prior to trying to install the latest version.
Thanks!

Hackysack said:
Hi! I'm currently trying to revive an LG G6 that I had lying around and was pleasantly suprised that there are recent builds of LineageOS available for the device.
Steps I took:
Download latest build (lineage-19.1-20230529-nightly-h870-signed.zip), boot.img and recovery.img
Installed boot image via `fastboot flash boot boot.img`
Installed recovery via `fastboot flash recovery recovery.img`
Reboot via `fastboot reboot`
Boot into recovery (via Vol Down + Power, Release Power, press power againg)
In Lineage Recovery, choose Apply update and Apply from ADB
Sideload image via `adb sideload .\lineage-19.1-20230529-nightly-h870-signed.zip`
Upload starts but stops at ~47%
Error message shown on phone:
Code:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 39,4 s (result 0):
Installing update...
Comparing TZ versions:
Max TZ version: TZ.BF.4.0.1-1865684
assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1"
E:Error in /sideload/package.zip (status 1)
Does anybody have an idea what could be the problem here? I had an older version of LineageOS installed on the device (bootloader is still unlocked), but I completely wiped the device prior to trying to install the latest version.
Thanks!
Click to expand...
Click to collapse
Look's like someone else had the same exact problem: link, and the corresponding solution: link. Hope this helps!
(I found this solution by searching: "assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1" ")

ethical_haquer said:
Look's like someone else had the same exact problem: link, and the corresponding solution: link. Hope this helps!
(I found this solution by searching: "assert failed: msm8996.verify_max_trustzone("TZ.BF.4.0.1-176180") == "1" ")
Click to expand...
Click to collapse
Hi,
thanks for you reply.
I'm not 100% sure about the terminology: Does bootstack mean kdz file?
If that is the case, I already tried to apply it to the device, but neither LGUP or LGFlashTool did work for me... On top there are so many versions floating around that I'm unsure which of the flashing tools is the right one to use on Windows 11. Do you happen to know where I should look for the latest version of one of these tools? (Besides googling, which as mentioned I already tried )

Hackysack said:
Hi,
thanks for you reply.
I'm not 100% sure about the terminology: Does bootstack mean kdz file?
If that is the case, I already tried to apply it to the device, but neither LGUP or LGFlashTool did work for me... On top there are so many versions floating around that I'm unsure which of the flashing tools is the right one to use on Windows 11. Do you happen to know where I should look for the latest version of one of these tools? (Besides googling, which as mentioned I already tried )
Click to expand...
Click to collapse
I honestly don't know, as I only have a Samsung. If you search for the same thing I did in that thread I linked to there were a few more results, you could check those: link.