Related
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.
Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks
Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.
Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172
I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??
Can you try to ADB Sideload the ASUS ROM?
sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.
Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases
Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy
I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script
Hi,
I'll test it, and will give feed-back
Thanks
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I used to be difficult to use TWRP menu, then the menu advanced Wipe Wipe then select all topics except the MicroSD and then manage Otg Wipe it !! Flash Stock Recovery to be done to make Flash official rom first official rom files onto the MicroSD example, I was. UL-ASUS_Z012D-WW-13.20.10.79-user. To change its name Then insert the MicroSD MOFD_SDUPDATE Recovry Mode, then select update to zip and then choose File. "MOFD_SDUPDATE.zip" I will wait a little longer for the update firmware and set up virtually everything is not lost through the OTA.
ผมเคยเป็นแก้ไม่ยากใช้ TWRP แล้วเข้าเมนู Wipe แล้วเข้าเมนู advanced Wipe ทำการเลือกทุกหัวข้อ ยกเว้น MicroSD และ Otg แล้วจัดการ Wipe ครับ!! เสร็จแล้วให้ทำการ Flash Stock Recovery เพื่อที่จะใช้ Flash official rom ก่อนอื่นทำไฟล์ official rom ลงไปยัง MicroSD ผมยกตัวอย่างเป็น UL-ASUS_Z012D-WW-13.20.10.79-user ให้เปลี่ยนชื่อเป็น MOFD_SDUPDATE แล้วนำใส่ MicroSD แล้วเข้า Recovry Mode แล้วเลือก update to zip แล้วทำการเลือกไฟล์ "MOFD_SDUPDATE.zip" แล้วรอสักพักอาจจะนานหน่อยเพราะเป็นการ update firmware ข้อมูลและการตั้งค่าทุกอย่างจะไม่หายเสมือนอัพผ ่าน OTA
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
I got the same issue, where did you get these files?
roosevelt84 said:
I got the same issue, where did you get these files?
Click to expand...
Click to collapse
I have the exact same error. Same here. Please someone can post download link.
SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I found a solution, and now my ZF3 is working but its showing a second screen with a error when it boots.
1 - download a zip file rom from asus site
2 - open it with winrar or another of your choice
3 - go to \META-INF\com\google\android
4 - open the updater-script with a text editor
5 - search for all the words WW_Phone and replace it for omni_ze552kl
6 - save the change and close, update the file inside the compressed zip
7 - put the zip rom inside your phone and flash it through twrp, done!
*sorry about english, its not my native lang.
Hi SuperDizor,
The issues you are having are both caused by the installation of TWRP 3.0.2. that was compiled for the Zenfone 3 using omni_ze55kl as the device type instead of WW_ZE552KL or CN_ZE552KL. I assume that the person that compiled it tried to make TWRP as universal as possible (instead of making two different versions, one for each device type - the TWRP code would have been the same except for this string...). However, the updater checks for this device type string and fails (unless you modify the updater config file as described in the post above). This is also why flashing stock recovery solved your issue.
The second error message you have, the one with dm-verity not being in enforcing mode was caused by having you install TWRP and allowing it to modify the system partition. This was necessary in the past but not anymore. When you flash TWRP, the first time you start it, it ask for your permission the make the system read-write, and you should refuse, as TWRP will function anyway and you will not get the dm-verity error. The dm-verity thingy is a software module in the bootloader (aboot to be precise) that checks the integrity of the system partition. TWRP has to force it in non-enforcing mode since it modifies the system partition and your device would not boot if it left dm-verity in enforcing mode. When you don't let TWRP modify the system partition (ie staying read-only), it does not change the dm-verity mode and you don't get warning messages. Don't worry, TWRP will still enable you to root your device and do whatever it does even if it is in "read only" mode.
Hope this helps !
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Niemer said:
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Click to expand...
Click to collapse
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same. Thanks
SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
but how to flash? its not booting in recovery mode.
I flashed the new*B336 update for EMUI 5 and when i got into it i saw that there were not any system apps, i checked why and it appeared i had to install another*full_data file or smth, is there any way i can do it now ???
Btw when i try to boot into TWRP it says Your device is booting now... and does nothing
The situation is now even worst, why can`t nobody help?
Please someone help. i really need my phone back and i can`t take it for repairs.
When i try to install stock rom of EMUI 4 the install says error code - 7
failed to mount /vendor (invalid argument)
failed to mount /product (invalid argument)
I have no OS installed and i cant use HiSuite to recover using fastboot.
dload mode says the app update package does not exist when there is a corrent update.app in the dload folder on my SD card
and*i also am sure i*used the right OEMinfo file ;(
please respond someone.
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Abdulla7 said:
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Click to expand...
Click to collapse
Okay, i will try and see what happens and report back to you. Thanks for the response
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
theAuxify said:
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
Click to expand...
Click to collapse
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Schlengge said:
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Click to expand...
Click to collapse
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
theAuxify said:
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
Click to expand...
Click to collapse
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Schlengge said:
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Click to expand...
Click to collapse
Yea, says :
Phone unlocked
FRP Unlock
And if i use the command adb devices in fastboot mode no devices appear at all*D:
EDIT : I managed to flash boot.img and recovery.img without errors with the device not showing on the list of devices.
Says everything is okay
But when i try to flash system.img it shows this
C:\Users\Auxify\Desktop\Huawei\Huawei-P9-Lite>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445202 KB)...
OKAY [ 14.775s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 14.828s
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Schlengge said:
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Click to expand...
Click to collapse
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Schlengge said:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Click to expand...
Click to collapse
Yeah.*I can boot into recovery N B9 but when i try to flash/wipe/do anything it says cant mount /vendor /product /version
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Schlengge said:
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Click to expand...
Click to collapse
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
theAuxify said:
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
Click to expand...
Click to collapse
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Schlengge said:
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Click to expand...
Click to collapse
Yea, but thats not for /vendor /product /version*xD
P.s : Happy 2017 ;P
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Schlengge said:
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Click to expand...
Click to collapse
Meh, i guess ill just drive out and get it fixed xD Its a loooong way though DD
Thanks for all your help brother ;p
theAuxify said:
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
Click to expand...
Click to collapse
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
jkmaziku said:
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
Click to expand...
Click to collapse
The best, is to try to install twrpmeticulus, wipe all except external storage property, install oeminfo.zip badwolf, go back to reboot, shut down.
Restarts Dload bxxx.
I only see her.
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?