Hi,
I believe my nexus 5x is "soft bricked" or in a "boot loop" (sorry newb here). The phone will restart and turn off during the boot animation. I am able to get into recovery mode and have attempted to use adb sideload to apply the latest 7.1.1 OTA zip from google's website. During that process (50% through) it said I could not update it because I needed to load a current or newer version. I realized I am on beta 7.1.1 NPF26F but am unable to locate the OTA zip for this.. I did download one online (seemed legit) but got an error E: signature verification failed, E: error 21. At this point I am a bit lost and unsure what to do.. any help would be appreciated.
Mike
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
es0tericcha0s said:
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
Click to expand...
Click to collapse
I do not believe my bootloader is unlocked. I tried to go through the " fastboot oem unlock " steps today but I need to turn on USB debugging on the device (which I cannot do) to even have that option. Will I need to wait until the OTA.zip is released or is there another way ?
http://storage.googleapis.com/andro.../preview/bullhead-npf26f-factory-0e9ab286.zip
is this the factory image or the OTA?.. guessing by the size its the factory image. I am unaware how to flash this if my USB debugging is LOCKED. Please help
Related
I'll give you a little pre-story.
Short version:
I have CWM recovery on android 4.12 but when I try to flash either PACman Rom or CM It gives me assert: failed getprop error. After removing the first line of the updater script in the zipfile I don't get the assert error, it just states
Finding update package...
Opening update package...
Installing update...
Installation Aborted.
Long version:
Initialy I was running Android 4.04 (ICS) with CWM recovery. I decided to flash the PACman rom(http://forum.xda-developers.com/showthread.php?t=2388267). I did the following.
1. Rebooted into CWM recovery.
2. Did a factory reset.
3 Wiped Dalvik cache.
4. Flashed ROM
5 Flashed Kernel
After completing these steps I rebooted my phone to find a "Security Error" message under the LG logo. It would automaticlly shutdown after 20 seconds. So what I initially tried was to flash the 10G KDZ which didn't work out because the LG tool is ****. However the 20B KDZ did work (which is Android 4.1.2). After the flashing had completed my phone booted normally. I was able to root my phone using this guide http://forum.xda-developers.com/showthread.php?t=2173465. I was also able to install CWM recovery. Now the following problem is this when I want to flash the PACman rom or the CM ROM I get the following error assert failed: getprop("ro.product.device") == p760 || getprop ("ro.build.product") == "p760" E:error in (path to zipfile) (status 7) Installation aborted. I got around that by removing the first line of the of the updater script. I don't get the error but it just states "Installation aborted".
Thanks in advance.
BausDroid said:
I'll give you a little pre-story.
Short version:
I have CWM recovery on android 4.12 but when I try to flash either PACman Rom or CM It gives me assert: failed getprop error. After removing the first line of the updater script in the zipfile I don't get the assert error, it just states
Finding update package...
Opening update package...
Installing update...
Installation Aborted.
Long version:
Initialy I was running Android 4.04 (ICS) with CWM recovery. I decided to flash the PACman rom(http://forum.xda-developers.com/showthread.php?t=2388267). I did the following.
1. Rebooted into CWM recovery.
2. Did a factory reset.
3 Wiped Dalvik cache.
4. Flashed ROM
5 Flashed Kernel
After completing these steps I rebooted my phone to find a "Security Error" message under the LG logo. It would automaticlly shutdown after 20 seconds. So what I initially tried was to flash the 10G KDZ which didn't work out because the LG tool is ****. However the 20B KDZ did work (which is Android 4.1.2). After the flashing had completed my phone booted normally. I was able to root my phone using this guide http://forum.xda-developers.com/showthread.php?t=2173465. I was also able to install CWM recovery. Now the following problem is this when I want to flash the PACman rom or the CM ROM I get the following error assert failed: getprop("ro.product.device") == p760 || getprop ("ro.build.product") == "p760" E:error in (path to zipfile) (status 7) Installation aborted. I got around that by removing the first line of the of the updater script. I don't get the error but it just states "Installation aborted".
Thanks in advance.
Click to expand...
Click to collapse
Is your phone booloader unlock? You must unlock your phone boot loader before flash any custom rom.
artit said:
Is your phone booloader unlock? You must unlock your phone boot loader before flash any custom rom.
Click to expand...
Click to collapse
Well I assume since I have CWM Recovery that my phone's bootloader is unlocked. Correct me if I'm wrong.
BausDroid said:
Well I assume since I have CWM Recovery that my phone's bootloader is unlocked. Correct me if I'm wrong.
Click to expand...
Click to collapse
No. Please look for how to unlock bootloader in L9 General & Q&A forum, and select thread that match your phone model.
artit said:
No. Please look for how to unlock bootloader in L9 General & Q&A forum, and select thread that match your phone model.
Click to expand...
Click to collapse
Turns out bootloader was locked. I have followed the guide and unlocked it but the same problem still occurs. [Did factory reset , cache wipe , dalvik cache wipe.
Thanks for your input
BausDroid said:
Turns out bootloader was locked. I have followed the guide and unlocked it but the same problem still occurs. [Did factory reset , cache wipe , dalvik cache wipe.
Thanks for your input
Click to expand...
Click to collapse
If your phone bootloader is unlocked and you also remove assert model check line from installer, you shouldn't get that error status 7.
Please try to make sure that your phone bootloader is unlocked by boot your phone in S/W update mode. The bootloader unlock text will print at the top of that screen.
artit said:
If your phone bootloader is unlocked and you also remove assert model check line from installer, you shouldn't get that error status 7.
Please try to make sure that your phone bootloader is unlocked by boot your phone in S/W update mode. The bootloader unlock text will print at the top of that screen.
Click to expand...
Click to collapse
I can confirm that it is unlocked. The text in the upperleft corner reads "Bootloader Status: Unlocked".
BausDroid said:
I can confirm that it is unlocked. The text in the upperleft corner reads "Bootloader Status: Unlocked".
Click to expand...
Click to collapse
If you still unable to flash any custom rom please try to flash stock kdz or use LG mobile support tool to recover your phone. Once my phone is in strange condition, I can flash custom rom but I cannot boot it (My bad, I use wrong update script when I test my rom). My phone always stuck at LG logo. Flash kdz, restore CWM and flash rom don't help. The last thing that make my phone boot up again is LG mobile support tool.
BTW if you phone model is not P760 you should restore your old baseband by flash you original kdz. (You flash P760 to unlock your boot loader right?)
artit said:
If you still unable to flash any custom rom please try to flash stock kdz or use LG mobile support tool to recover your phone. Once my phone is in strange condition, I can flash custom rom but I cannot boot it (My bad, I use wrong update script when I test my rom). My phone always stuck at LG logo. Flash kdz, restore CWM and flash rom don't help. The last thing that make my phone boot up again is LG mobile support tool.
BTW if you phone model is not P760 you should restore your old baseband by flash you original kdz. (You flash P760 to unlock your boot loader right?)
Click to expand...
Click to collapse
Well the problem is that I can't flash the stock 10G KDZ because the LG Mobile Support Tool only allows me to install 20B KDZ. Your question could be interpreted in two ways so I will give you two awnsers .
Q Why did I flash my p760?
A Because after flashing PACman rom on android 4.0.4 I got a security error
Q How did I unlock my bootloader?
A I first rooted the device. Installed CWM recovery, then did adb reboot oem-unlock
So the question is how do I flash 4.0.4 KDZ if the LG mobile support tool does not allow me?. Or how do I resolve the ROM installation issues?.
Thanks again
BausDroid said:
Well the problem is that I can't flash the stock 10G KDZ because the LG Mobile Support Tool only allows me to install 20B KDZ. Your question could be interpreted in two ways so I will give you two awnsers .
Q Why did I flash my p760?
A Because after flashing PACman rom on android 4.0.4 I got a security error
Q How did I unlock my bootloader?
A I first rooted the device. Installed CWM recovery, then did adb reboot oem-unlock
So the question is how do I flash 4.0.4 KDZ if the LG mobile support tool does not allow me?. Or how do I resolve the ROM installation issues?.
Thanks again
Click to expand...
Click to collapse
For flashing ICS
In JB rom offline flash program cannot detect your phone in S/W update mode. Most people stuck at about 15% and the program told them that their phone is not connect. If you want to flash 4.0.4 ICS kdz you should
- boot your phone up (if it can boot up),
- connect usb cable and put your phone in LG software mode.
- Do an offline flash again but select DIAG instead of EMERGENCY. You phone should reboot into S/W update mode automatically. After that it will get pass 15%.
But If you cannot boot your phone up, you need to flash you phone model ICS u-boot and x-loader via fastboot. After that offline flash program can detect your phone in S/W update mode.
For rom istallation, I'm sorry I don't understand why you cannot flash custom rom. Maybe your download is corrupt? Please check file md5 with rom uploader.
artit said:
For flashing ICS
In JB rom offline flash program cannot detect your phone in S/W update mode. Most people stuck at about 15% and the program told them that their phone is not connect. If you want to flash 4.0.4 ICS kdz you should
- boot your phone up (if it can boot up),
- connect usb cable and put your phone in LG software mode.
- Do an offline flash again but select DIAG instead of EMERGENCY. You phone should reboot into S/W update mode automatically. After that it will get pass 15%.
But If you cannot boot your phone up, you need to flash you phone model ICS u-boot and x-loader via fastboot. After that offline flash program can detect your phone in S/W update mode.
For rom istallation, I'm sorry I don't understand why you cannot flash custom rom. Maybe your download is corrupt? Please check file md5 with rom uploader.
Click to expand...
Click to collapse
I did the above but I get a page error(only with the 4.04 kdz). When my phone was bricked I had the same problem thats why I flashed 20B. Thanks for your time.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks
I have the T mobile H901 Like just about everyone else. I got it with android 6.0 and I wanted to root it. Now i didn't really know what to do, so I tried following some guides on here. I got my bootloader unlocked, but TWRP would not install, and I kept getting some "unknown command" error. So I installed this via LGUP: https://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
That gave me twrp, but I could no longer boot into system. From there I tried installing stock 6.0 .zip files, Installing .kdz files through LGUP, but nothing was working.
So then I tried this thread: https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
I installed the V10_H901_V20L_Update_P1.zip, then the V10_H901_V20J_Stock_Custom_2e_FULL-signed.zip both though TWRP 3.0, and followed the rest of the instructions until I got to: "Once in Fastboot type this command "fastboot oem unlock"" BUT my phone already WAS unlocked. So I (not really thinking) typed "fastboot oem lock" and then it said "erasing data" like it was supposed to. But after that, I can do longer get into my recovery, Boot to system, and If I don't enter fastboot OR download mode, It stays in a bootloop where it says: "boot verification fail!! - Cause : MISMATCH_SIG_LEN
Please if anyone could help I would be so happy.
EDIT: I should also mention that when I try and flash the stock 6.0 rom with LGUP (The "H90120e_00_0316") It gets to 9% and fails with the error: Error Code - 0x2000, TOT antirollback version is smaller than device version.
OK I fixed my phone by using LG Bridge firmware update while my phone was in download mode. The only problem is NOW I can't root. I hope someone can get a Nougat root working.
BuildMineSurvive said:
OK I fixed my phone by using LG Bridge firmware update while my phone was in download mode. The only problem is NOW I can't root. I hope someone can get a Nougat root working.
Click to expand...
Click to collapse
Working with some Korean friends on that now. No promises but early testing is progressing well. Hopefully it works for 20 & possibly 30
BACKUP YOUR DATA FIRST
Only for zs570kl 2.15ghz CPU; NO zs570klPRO 2.4ghz device.
Hi all,
official image to flash Android 8 Oreo.
HOW TO:
Method fast 1
1.Extract ZIP
2.Go into the fastboot (key vol + and power on)
3. On the folder extract open update_image.bat
Wait to done 2/3 minut and ENJOY android Oreo
Method 2
Flash using Asus Flash Tool
to download and info
https://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html?m=1
Update file Android 8 Oreo 15.0210.1804.47:
https://drive.google.com/open?id=1U5SBXDpezUIIxisDPY8qm85LoGNfS5i6
I take no responsibility for brick device.
Have testeted the rom and work fine.
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
tecnicopascoal said:
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
Click to expand...
Click to collapse
official Asus, no only in fastboot mode
Has anyone suffering battery drain? I've updated my ZS570KL to 8.0 with Asus official but phone became hot and battery drain is dramatical…. obvious reset many time to factory default and wipe all…. The problem appears from the beginning…. starting the initial setup. Thanks.
grean said:
official Asus, no only in fastboot mode
Click to expand...
Click to collapse
So is this rootable or is it pre-rooted? I also am wondering if this Oreo update fixed the Quickcharge limit (where QC is disabled)?
It is the only way to update?? Except ota
EDIT. Guys, the other way you can update to oreo is flashing oreo stock recovery and then install the firmware
Wheres the MAGIC
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Aussiewaterdragon said:
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Click to expand...
Click to collapse
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
BahaStriker said:
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
Click to expand...
Click to collapse
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
karlnorth said:
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
Click to expand...
Click to collapse
Tried all means, I just gave up
I'm happy to say that I got it working. It appears the Unlock tool gives the "Can't unlock your phone right now" error if your phone is already unlocked.
Previously, I was running the Turbo ROM 6.01 found in the ZF3 Deluxe thread. My phone was BootLoader unlocked and Rooted. I upgraded to 8.0 by running the very straightforward "Update_Image.bat" command found in the 8.0 ROM folder. I figured the update would re-lock my BootLoader, so I ran the 8.0 version of the Unlock tool. Then I ran into the previously mentioned error. In my frustration I just said 'screw it, I have 4 of these phones'. So I booted the phone into fastboot mode and flashed TWRP 3.2.2. I expected it to fail; however, it WORKED! I then booted the TWRP 3.2.2 image and flashed SuperSU v2.82 SR5. That worked! I then flashed the Xposed v90-sdk27-arm64-beta3 zip and THAT worked! I rebooted the phone and it loaded up pretty as you please.
I've followed this procedure with all 4 of my ZF3 Deluxe phones and they are all happily on 8.0.0, Rooted, and have Xposed running
A new Update for the ZenFone 3 Ultra is finally here. OTA Updates are live for eligible devices. This is not the Android 8.0 Update I was hoping as the Version number still shows 7.0 so lets hope I am wrong. Given the size I thought it might be the Android 8.0 Oreo Update but does not appear to be.
I have the WW Version and got the update notification this morning. It is 470.75MB in size and hopefully soon the full Firmware package will also be available for offline install.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
DJMRLONG said:
I got it this morning as well, didn't think it was Oreo but hoping to see better performance........
Click to expand...
Click to collapse
So, is Ultra getting Oreo or not? What i hear are all rumours, nothing from the horses mouth.
australia here, today got OTA and now i have WW_14.1010.1804.74_20180605
still android 7.0
AWFRONT said:
A new Update for the ZenFone 3 Ultra is finally here.
Anyway, lets see how the firmware is and hope it fixes previously identified issues such as battery drain and others.
Enjoy!
Click to expand...
Click to collapse
not for my case, the update doesnt fix anything.
the battery drain is AMAZING. congrat Asus!
charged overnight, pull it at 100% in the morning, open 2 websites clicks 2-3 links, and battery down to 98%. whatttttt???
(not website with FHD photos, just normal websites with texts)
so anyone know wat the update about ?
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
lucian1983 said:
I downloaded the update from Asus website and installed it manually cause my Ultra is rooted and didn't receive OTA. After downloading the zip file I placed it in the root of the phone (no folder), I rebooted the phone and after the boot I received a notification "update available". I taped on it and the whole process was automatic, the phone rebooted into twrp and from there it booted back into Android. After the first boot I didn't had installed anymore Magisk (no root) so in went to the PC and flashed once again the twrp image using fastboot mode (twrp was replaced with the stock recovery image during the update). From there (twrp) I flashed once again Magisk and everything was ok, I regained root access. With the exception of the security patch, witch is now from April 2018, everything seems to be the same as before the update.
Click to expand...
Click to collapse
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
mac231us said:
Hello. I would like to know how you rooted and installed twrp (without unlocking bootloader?)
Since to get update available, you need locked bootloader from what I understand.... so if you got update available, it appears your bootloader is still locked. But you are rooted and have custom recovery also. Thanks appreciate how you managed to root and install twrp without unlocking the bootloader.
Click to expand...
Click to collapse
I got my Ultra second hand and it camed with bootloader unlocked and magisk allready installed, so it was rooted and running latest firmware from Asus website at that time, several months ago, the firmware ww_1010.1804.64. in fastboot mode it said "unlocked" for the bootloader, so probably the seller used the unlock tool from Asus website to unlock the bootloader and after he flashed TWRP with the computer, by putting the phone in fastboot mode. You can find the TWRP zip file on a Indian site and download it with the Mega app. Just search on Google "TWRP zenfone 3 ultra".
Several days ago, I downloaded the new firmware from Asus website, ww_1010.1804.75 and placed the zip file in the root of the internal storage, under all the other folders. When I used the update system feature in the settings it didn't detect any update available, but after I rebooted the phone it appeared a notification message with "update available", I taped on it and the update was installed with TWRP and the phone rebooted. After reboot the TWRP image was replaced with the stock recovery from Asus and I had to go to the computer to flash TWRP image once again with the help of fastboot mode (also it said "unlocked " for the bootloader even after the update). From there (TWRP) I flashed back Magisk 16.0 zip file and everything is back to normal for me, I have the latest firmware from Asus and root.
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
mac231us said:
understand now..thanks. So it did not do an ota update (my confusion) but did an update since you had the rom already in storage (hence the prompt for update available) ok thanks!
Click to expand...
Click to collapse
Anytime!!! Yes, that's it, it was no OTA update, only a notification prompt because I put the rom in the root of storage.