Hey my name is David and i have a axon 7. i was doctoring yesterday about 10h on this phone and finished a open phone fastboot secureboot and twrp...problem was? i had always a error 7 if i want flash an rom...after waking up morning i tryed new method...i tryed to go to an other twrp...now? now its all wrong its now the mifavor interface if i oush power and + i cant do anything oin adb....
there is no chance to reinstall like adb reboot edl etc.
if i do adb sideload xxx.zip he cancel in 25%with error failed to verify whole-file signatur and signature verification failed
if anyone can say me what to do it would be so nice for help..
P.S: sry 4 bad english if this is nobody understanding i better use translater.
i cant sending pics now at this moment cause this is my only 1 client who can do pics
b10 i was in original rom before
i now loadet a b10 2017g zip and wanted to sideload that hoped i get any rom on this phone to get it started to start adb reboot edl for ptrw...but nothing...read so many threads here...anyone 1 idea? today evening in germany time i can send a few pictures for better understanding maybe my problem
twrp 3.0.4-1
i have the twrp back in version 3.0.4-1....
that was hard work but know i have the same error 7 mistake in installation like yesterday...anyone a idea to get there a 7.1 linage os is?
in the 21.2 nightly version of axon 7 comes always asserts failed and error 7
Related
1. I am a newbie and I am I am attempting to flash a new recovery image (Clockwork-6.0.3.8) onto my nexus 10.
I believe the one I have is corrupted or bad or whatever? When I try to update to a newer version on CM I get an immediate error. The tablet starts with a re-boot and immediately when the first step of the update starts I get an error with the image of the android laying down with a yellow or red triangle depicting the error??? So I figure I should reflash the recovery.
I have gotten the nexus connected to my pc and I have fastboot working properly but when I attempt to flash the new image i get the error "cannot load recovery.img : Unknown error" on the PC
I get the error "FASTBOOT STATUS FAILInvalid partiton" on the nexus. I have searched this last error high and low and cannot find anything concrete explaining it.
Apologies if I am posting this in the wrong forum, thanks in advance for any assistance
Nexus 10 with Android 4.2.1 with the following version CM: 10.1-20130120-NIGHTLY-manta. I am trying to update to 10.1.3 and get rid of this nightly.
chuckb74 said:
1. I am a newbie and I am I am attempting to flash a new recovery image (Clockwork-6.0.3.8) onto my nexus 10.
I believe the one I have is corrupted or bad or whatever? When I try to update to a newer version on CM I get an immediate error. The tablet starts with a re-boot and immediately when the first step of the update starts I get an error with the image of the android laying down with a yellow or red triangle depicting the error??? So I figure I should reflash the recovery.
I have gotten the nexus connected to my pc and I have fastboot working properly but when I attempt to flash the new image i get the error "cannot load recovery.img : Unknown error" on the PC
I get the error "FASTBOOT STATUS FAILInvalid partiton" on the nexus. I have searched this last error high and low and cannot find anything concrete explaining it.
Apologies if I am posting this in the wrong forum, thanks in advance for any assistance
Nexus 10 with Android 4.2.1 with the following version CM: 10.1-20130120-NIGHTLY-manta. I am trying to update to 10.1.3 and get rid of this nightly.
Click to expand...
Click to collapse
Go into flashboot and make sure you have no typo's. Redownload your CWM recovery, rename it "recovery.img", and make sure your command line has no typo's. I had issues with a typo and "Unknown errors" and "Invalid Partition", and I had to reboot the tablet a couple times, then retype the command line. Also give TWRP a shot if CWM just won't work
Dear Members
After i wanted to install die Android 5.0 OTA over my 4.4 i hade following problem.
creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip
status 7 installation aborted
So now what i can do. Is only start in Stock recovery Mode. I have Wipe my Device few times and still the same Error status. Also tried to install other zips like 4.4 ota's but i never wannt to work.
My biggest Problem is i cant start in fastboot mode. Everytime i tried it restart. that meen i can only start in stockrecovery and start the adb sideload. In the adb sideload it understand only the "adb sideload" command all other it comes the "error: closed"
Sorry for my bad English.
Cheers
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
amartinss said:
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
Click to expand...
Click to collapse
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
yasin0005 said:
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
Click to expand...
Click to collapse
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
amartinss said:
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
Click to expand...
Click to collapse
Ok...take u r time
yasin0005 said:
Ok...take u r time
Click to expand...
Click to collapse
I can not upload files yet .. I am new to XDA have less than 10 places .. sorry but I can not post the image of the error message. But this is the message that appears on the device ...
Error picture this link amartinss.com.br/sing/IMG_20160101_123536.jpg
OR described below
"Now send the package you want to apply to the device with 'adb sideload <fillenme>'...
Finding update package...
Opening update package...
Verifying update package...
Installing update package...
assert failed: !less_than_int(28686307, getprop("ro.build.date.utc")) || greate_than_int(getprop("ro.build.date.utc"), 1392739200)
return code 8E: Error in /sideload/package.zip
(Status 8)
Installation aborted."
This happens when I try to downgrade the sideload...
To fix your issue, you need to:
1) Update your Recovery to the Latest STOCK version
2) Reinstall your ROM downloading full firmware from ASUS site
The issue is that your ROM/Recovery is not up-to-date to run the update package.
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
patrick.bitencourts said:
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
Click to expand...
Click to collapse
have you found a solution to your problem ???
I am also facing same issue while updating with adb sideload..
if you have got a solution please post it..
Have you tried to acces fastboot with the adb command: adb reboot fastboot ?
Then you could try again to flash your updated recovery.
There is a CWM modified recovery you should try.
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!!!
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding