About "E:failed to verify whole-file signature",

You can use fastboot to flash the recovery.img of the target ROM(unzip and get the recovery.img inside!), then reboot and try to update from ADB or SD card.

Those ROMs from ZTE will check if your phone is US or EU version, so I think you can only flash the EU one.

The ROMs from comebuy will destroy the update channel and give you a wrong recovery.img so you may get more "E:failed to verify whole-file signature". But they are the only ROMs I found which can give the fastboot FireFox logo back.

Oh man, you went from 1.3-> root kit-> 2.0 -> 1.1 You saw -> Cant adb unless run script while Volume down + power -> sdcard and no adb and from sdcard the only error war the prop that is set when the phone is rooted.

Once you root the phone the official zip will show this error. Then you tried to use the 1.1 versions from the previous version of the phone and you still have verification error.

2 questions: -scratch this is a different device issue-

1. What version are you trying to get to? 2.0 or back to 1.3?

That last couple lines here will reset the prop that rooted the phone, you can reverse this to avoid the errors on your second updat * I believe https://github.com/martensms/zte-open.../02-install.sh

However to get you back from the last update, if you can use the sdcard method to grab an image that works with a rooted phone this should get you back on track. I will post back after asking around here as well.

sending 'system' (368640 KB)... [hangs here - then I plugged phone off]

That could potentially brick the phone.  :(

If you put the phone back in fastboot mode ( holding down the vol down button after reboot ) and then do : fastboot devices

What happens?

Ok Back, For back to the ZTE build: You do need to use this base image to unbrick the device http://www.ztedevices.com/support/sma.../65229ec9-3165-424e-a7dd-3759356325fd.html and please follow these instructions http://www.ztedevices.com/support/sma.../65229ec9-3165-424e-a7dd-3759356325fd.html and these instructions will help you with the specific device build documentation: http://wwwen.zte.com.cn/endata/mobile/

For getting back to using adb: Please try the steps in above post from nhirata!

Thank you for your answers! I will start off by answering the questions.

guigs2: What version are you trying to get to? 2.0 or back to 1.3? Ok, as far as I know, 1.3 is stable, 2.0 is kind of nightly build, or git version. 1.4 is supposed to be beta, so that is the version I'd like to go after trying git. Here I'll just say that although I got that version from git is 2.0, versions aren't properly marked in the official guide. (I have no idea where is 1.4, and as you said in your post, guigs2, I was juggling hard with those versions)

nhirata:If you put the phone back in fastboot mode and then do : fastboot devices What happens?

Fastboot works. # fastboot devices a1050b fastboot

I am downloading now zip from http://www.ztedevices.com/support/sma.../65229ec9-3165-424e-a7dd-3759356325fd.html (although I did that already) and will do what nhirata suggested (although again I did that already as well). I will keep you updated.

Update ============================

Steps I have taken:

1. Downloaded zip from link above
2. Unpacked zip using gnu unzip
3. Read through pdf from zip (sorry I didn't, it's the same I've read 2 days ago)
4. Executed `fastboot boot recovery.img` with recovery.img being from said zip
5. I got into recovery mode, although `adb devices` didn't find anything
6. Pulled mSD from phone, put it into laptop and copied update.zip onto it
7. Unmounted mSD and put it back into phone, then waited a minute just to make sure
8. "Apply update from sdcard" > update.zip
9. Got error. Rewritten -> http://pastebin.com/wB59Tc8Z

Unfortunately, as I said, adb can't access the device, therefore guigs2's github link is not applicable.

Waiting for your responses. Thank you.

Ok, the good news is that you still have access.

Do you have adb access at all? Make sure that the device is not in lockscreen mode and that you have the debugging turned on in the developer settings ( if you have flashed a new build then it may have reset ).

Also to note, there could be various reasons why fastboot locked up. One that I am aware of is if the system partition is smaller than the image size. I do not know how to check for it within fastboot; adb shell df to check for it within adb access.

nhirata, as I said. I have no adb access at the moment, although I can get into recovery mode. Making sure lockscreen mode is not on and debugging is turned on, that is kind of insane request to make, since I can't boot into system. As far as I remember, both options where the way you want the last time I managed to boot into ffos PS: in case anyone wonders, I always check copied files with md5sum.

Update ================================

I can access the phone via adb. I've just noticed that if I select the "Apply update from adb" from recovery menu, I get (maybe limited) access from adb:

# adb devices List of devices attached a1050b sideload

Update ================================

Here is adb log: http://pastebin.com/nikZcfRH Since it wants sideload, I decided I'll give it to it!

# adb sideload update.zip sending: 'update.zip' 100%

Phone gave me expected result. It's the very same than the output when I tried to update from mSD: http://pastebin.com/wB59Tc8Z With only two minor differences:

1. Shown path after "Abnormal exit" text is obviously /tmp/update.zip
2. I don't have -- Install /sdcard .... as first line (but "Now send the package you want to apply.......", of course)

amfg:

> Executed `fastboot boot recovery.img` with recovery.img being from said zip

How about `fastboot flash recovery <the path of the recovery.img you just extract>`? In my case, it will fix the recovery and then I can flash the update.zip by using `adb sideload`.

Caasi: # fastboot flash recovery recovery.img target reported max download size of 1073741824 bytes sending 'recovery' (8334 KB)... OKAY [ 0.264s] writing 'recovery'... OKAY [ 0.669s] finished. total time: 0.934s # fastboot reboot During reboot, I held VOLUP button. got into recovery, but adb is still unable to find device. Weird, huh.

Note: `Apply update from adb` still gives limited adb access

I tried to do the same thing with boot:

# fastboot flash boot boot.img target reported max download size of 1073741824 bytes sending 'boot' (7206 KB)... OKAY [ 0.229s] writing 'boot'... FAILED (remote: flash write failure) finished. total time: 10.283s

ADB mode and fastboot mode are different modes on the system that may not necessarily be seen in each of each other's modes... ie adb won't necessarily work in fastboot, fastboot won't necessarily see in adb mode, so it's not too weird that recovery mode doesn't allow adb mode.

Interesting that you found a separate way to get into adb mode.

I wasn't sure if you could even get to adb.  Sometimes you can while the system is still trying to boot even though it won't load fully.  Sorry about that.

It sounds like the boot.img won't flash. That sounds like the boot portion is some how read only via fastboot. Now that you were able to update the recovery portion, can you try going back to recovery mode and try to recover?

amfg:

In my case, I can go into the recovery mode by pressing VOLUP when booting, and go into the fastboot mode by pressing VOLDOWN. In the recovery mode, if you want adb to detect the device, you have to wait for a few seconds after you plug it in.

Also please check your /etc/udev/rules.d again, the following lines should be inside your android.rules or 50-android.rules or whatever:

``` SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev" SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev" ```

The first idVendor is for Google and the second one is for ZTE.

Nhirata: I know the difference between fastboot and adb. As I stated before, and now I repeat myself for at least third time (I know I have posted a lot and it's a drag to read it all but I thought it will be better to post more than less), I am able to get limited access to adb in recovery mode (power+volup) but I am unable to update neither from mSD card nor adb (for convenience I copy the link here, although it can be found in one of my posts as well - http://pastebin.com/wB59Tc8Z -- I have just noticed two mistakes in this link. Sorry for that, obviously I couldn't copy&paste it). So to sum it up - No, I can't recover from recovery mode.

Caasi: I tried waiting for approximately 10 minutes. Nothing changed. My rules are set correctly, I double checked + it was working a few days ago.

amfg:

Hmmm..., I have no idea now.

These are some recovery.img: https://mega.co.nz/#F!ghMnzSDC!iRHh2Nj0TwAv8WMlZNfREA

I hope one of them can help.

OK, you seem to be trapped in almost the same situation I was: https://support.mozilla.org/en-US/questions/1003136

• /system/build.prop seems to be necessary for update, so you need to flash minimal (not functional at all) system.img containing this file just in order to adb sideload
• such a file is https://github.com/martensms/zte-openc-rootkit/raw/master/01-unbrick/raw/system.img - it contains more than necessary but should still fit into the limits of fastboot flush (about causes of which I have no idea)
• if fastboot is unable to flush even this smaller file, try to use different USB port

Hope this helps.

I will try both your suggestions tommorow, at the moment I have no access to my zte. It is still not unbricked so keep posting your thoughts and ideas, something might help. Thank you

Wow Artem! How did you find that system.img? That's awesome.

Thanks for pointing it out.  Hopefully it will work for amfg.

In fact, I created it myself using some google-fu, then we had an e-mail conversation with the repository owner. If you follow the link to my question, it contains instructions for making system.img from a directory.

Unfortunately, no luck - http://pastebin.com/Yp5Lc5nX I will try with different cable (as changing ports doesn't change a thing)

Could you adb sideload the image from the system recovery menu? Or from the sdcard?

guigs2: https://support.mozilla.org/en-US/questions/1007267#answer-595464 - check 2nd update

Different cable doesn't make difference in my case. I've tried original usb shipped with kindle.