Hey, does anybody have a surefire way of unlocking the bootloader and installing a custom recovery for the Axon 7.
I've tried every guide I could find but none of them seem to work.
I've tried installing the .zip files provided to me using both stock recovery and adb sideload but I just get...
-- Install /sdcard/(Insert .zip file here) ...
Finding update package...
Opening update package...
Verifying update package...
Update package verification took 46.0 s (result 0).
Installing update...
Warning: No file_contextsThis package is for "ailsa_ii" devices; this is a "".
E:Error in /sideload/package.zip
(Status 8)
Installation aborted.
Is there anything I can download specifically for ailsa_ii boards?
Donte Dub said:
Hey, does anybody have a surefire way of unlocking the bootloader and installing a custom recovery for the Axon 7.
I've tried every guide I could find but none of them seem to work.
I've tried installing the .zip files provided to me using both stock recovery and adb sideload but I just get...
-- Install /sdcard/(Insert .zip file here) ...
Finding update package...
Opening update package...
Verifying update package...
Update package verification took 46.0 s (result 0).
Installing update...
Warning: No file_contextsThis package is for "ailsa_ii" devices; this is a "".
E:Error in /sideload/package.zip
(Status 8)
Installation aborted.
Is there anything I can download specifically for ailsa_ii models?
Click to expand...
Click to collapse
Every axon is "ailsa_ii" afaik. it's just failing.
One thing you didn't talk about is what model it is. If it is an A2017G you have to use axon7tool to flash TWRP, then use it to flash a zip. No idea for another models. But be VERY SURE about what model it is, using a guide for another model on your phone will kill it!
Choose an username... said:
Every axon is "ailsa_ii" afaik. it's just failing.
One thing you didn't talk about is what model it is. If it is an A2017G you have to use axon7tool to flash TWRP, then use it to flash a zip. No idea for another models. But be VERY SURE about what model it is, using a guide for another model on your phone will kill it!
Click to expand...
Click to collapse
In the title I said it was the A2017U.
I even tried to use the Axon7Toolkit but I can't get all the the dependencies to download.
Donte Dub said:
In the title I said it was the A2017U.
I even tried to use the Axon7Toolkit but when trying to download the dependencies (twrp-3.1.1-0-ailsa_ii.img) it was download failed, and when I try to retry or import it it still doesn't work.
Click to expand...
Click to collapse
A couple of comments:
The XDA app doesn't display the full title, it just cuts at ZTE axon 7. Jus saying
If the download fails, go to the A2017G download center and download the TWRP 3.1.1-0, then put it inside Axon7Development and a folder inside that should be called TWRP or something. It should detect it and work. otherwise try cutting your internet. Also, I think it needs fastboot, so if you're on the latest and greatest Nougat for A2017U, ZTE got rid of fastboot... downgrade to a much older version the official way (download zip, go to Updates and install it)
Choose an username... said:
A couple of comments:
The XDA app doesn't display the full title, it just cuts at ZTE axon 7. Jus saying
If the download fails, go to the A2017G download center and download the TWRP 3.1.1-0, then put it inside Axon7Development and a folder inside that should be called TWRP or something. It should detect it and work. otherwise try cutting your internet. Also, I think it needs fastboot, so if you're on the latest and greatest Nougat for A2017U, ZTE got rid of fastboot... downgrade to a much older version the official way (download zip, go to Updates and install it)
Click to expand...
Click to collapse
Ok so I got the .img and the SuperSU files to work but when trying to install the www.mega-debrit.com_A2017U_FASTBOOT_UNLOCK_EDL.zip file the Hashcheck gets a mismatch...
Donte Dub said:
Ok so I got the .img and the SuperSU files to work but when trying to install the www.mega-debrit.com_A2017U_FASTBOOT_UNLOCK_EDL.zip file the Hashcheck gets a mismatch...
Click to expand...
Click to collapse
i guess the download failed some... download it again and try. Are you using axon7toolkit, or MiFlash? If you have the TWRP image you can put it in the folder like i told you and axon7toolkit should work
Choose an username... said:
i guess the download failed some... download it again and try. Are you using axon7toolkit, or MiFlash? If you have the TWRP image you can put it in the folder like i told you and axon7toolkit should work
Click to expand...
Click to collapse
I'm using axon7toolkit and I did like you said and have the TWRP image in the TWRP folder and the SuperSU zip in the root folder but I can't get the A2017U_FASTBOOT_UNLOCK_EDL zip to work and idk if there's anything after that that I need to download.
Donte Dub said:
I'm using axon7toolkit and I did like you said and have the TWRP image in the TWRP folder and the SuperSU zip in the root folder but I can't get the A2017U_FASTBOOT_UNLOCK_EDL zip to work and idk if there's anything after that that I need to download.
Click to expand...
Click to collapse
sorry, no idea. Have the A2017G and you do most of this with axon7tool instead. Maybe head over to the 4th category brick repair guide, then go to 4pda from the MiFlash download link, and find the A2017U unlock edl file, download, try...
Dunno why it would tell you that though. MiFlash refusing to work is not uncommon at all. if it still doesn't want to flash then try using another PC, usually it solves all your trouble
Choose an username... said:
sorry, no idea. Have the A2017G and you do most of this with axon7tool instead. Maybe head over to the 4th category brick repair guide, then go to 4pda from the MiFlash download link, and find the A2017U unlock edl file, download, try...
Dunno why it would tell you that though. MiFlash refusing to work is not uncommon at all. if it still doesn't want to flash then try using another PC, usually it solves all your trouble
Click to expand...
Click to collapse
Thanks, I'll try it.
Related
I get a failure when trying to flash a new ROM. I have three different zips (ROMs) on my phone. None of them will install for some reason and I get a failed error and it puts something about an error when updating binary script? How could I fix this on my nexus 4?
If I need to update twrp could I do so without using goomanager to do this? Goomanager won't download the recovery so I have to use another method
You probably need to update to the latest TWRP version. Use the TWRP link in my signature and get the latest version in the "mako" folder.
Use fastboot to flash it, use the command:
fastboot flash recovery twrp.img
(replacing twrp.img with actual file name)
If you don't know how to use fastboot, use the 3rd link for guide on installing custom recoveries.
dreammaster252 said:
I get a failure when trying to flash a new ROM. I have three different zips (ROMs) on my phone. None of them will install for some reason and I get a failed error and it puts something about an error when updating binary script? How could I fix this on my nexus 4?
If I need to update twrp could I do so without using goomanager to do this? Goomanager won't download the recovery so I have to use another method
Click to expand...
Click to collapse
had the same error and resolved it like this:
installed ROM Installer vom play store
installed cwm, and then twrp again from rom installer.. worked perfectly!
BUT WHATCH OUT! i think the error you get is called "error 9".. or something like that, it appears, when you try to install a zip, and the updater-skripts cancels the installation process, e.g., because it is not hte right zip for your phone!
so look at first, if you have the right zip downloaded
Hello
I have formatted the system in twrp and I can't do nothing except going into twrp. I want to flash the stock system but it says:
Updater process ended with ERROR: 8
Error installing zip file 'external_sd/update.zip'
So where I can find the stock recovery to be able to flash the original system recovery.
Thank you.
roucoups said:
Hello
I have formatted the system in twrp and I can't do nothing except going into twrp. I want to flash the stock system but it says:
Updater process ended with ERROR: 8
Error installing zip file 'external_sd/update.zip'
So where I can find the stock recovery to be able to flash the original system recovery.
Thank you.
Click to expand...
Click to collapse
Just FYI , Next time you create a thread asking for things , you NEED to use the SEARCH feature of this forum.
http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Those files are TWRP flashable zips.
DrakenFX said:
Just FYI , Next time you create a thread asking for things , you NEED to use the SEARCH feature of this forum.
http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Those files are TWRP flashable zips.
Click to expand...
Click to collapse
I already tried several times and each time I start flashing zte_a2017.b03_bootstack_by_drakenfx.zip it says:
Updater process ended with ERROR: 6
Error installing zip file 'external_sd/ZTE_A2017G.B03_BootStack_by_DrakenFX.zip'
So what do I do now????
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
EDIT: I tried to install it through firmware finder and it didn't pass the verification at the end
https://drive.google.com/open?id=0B4baHcoSeBbgY21CVjlPNk45YlE
https://drive.google.com/open?id=0B4baHcoSeBbgYTZiR1ZDeUpoWnc
https://drive.google.com/open?id=0B4baHcoSeBbgV0g3ejBlMXlzdkk
I have downloaded the 3 zips in this update and verified the md5 they are all good if someone figures out how to install this
krchi said:
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
Click to expand...
Click to collapse
I found the same... Gonna try!
Jessooca said:
How did that work out for you Jorge??
Sent from my FRD-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
JorgeCS said:
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
Click to expand...
Click to collapse
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Well the good news I see out of this even if we cannot install is that the update is finally coming after 2 months of the other versions enjoying it for that long. Hopefully it fixes the battery drain.
Sent from my FRD-L04 using Tapatalk
Received the OTA update for the B380 version on my FRD L09C185 yesterday. But no notable change in the battery life till now.
krchi said:
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Click to expand...
Click to collapse
Yep, you can't install this...
Can you install the full firmware from B162 though?
Gus194 said:
Can you install the full firmware from B162 though?
Click to expand...
Click to collapse
You can try and tell us
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Jessooca said:
So the 622mb update file is the correct B385 update file? Can i push it to the phone via adb? Or what's the best way to install it??
Click to expand...
Click to collapse
Likely you'd push both update.zip and the region specific zip to where the stock recovery is expecting, then from a powered-off state use the key combinations to force-udpate. I'm unsure why there are 3 zips this time though since B360 was only 2 zips, I haven't had time yet to look at the contents.
Telperion said:
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Click to expand...
Click to collapse
Mines was just the OTA files you have the full ota files
Jessooca said:
Did you install the update you found?
Click to expand...
Click to collapse
I tried.
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
usmcnyc said:
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
Click to expand...
Click to collapse
Tried that, compatibility error.
Telperion said:
Tried that, compatibility error.
Click to expand...
Click to collapse
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
usmcnyc said:
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
Click to expand...
Click to collapse
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Telperion said:
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Click to expand...
Click to collapse
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
usmcnyc said:
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
Click to expand...
Click to collapse
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Telperion said:
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Click to expand...
Click to collapse
There's a 1.9gb OTA on firmware finder...I'd download it here at work but the internet is too slow, it'd take hours.
I have an HTC U Ultra that has been bricked. I'm able to boot the phone into download mode. This is the info I have on download mode:
*** UNLOCKED ***
*** FUSED (PRODUCTION) ***
htc_oceuhl PVS S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v24.0.8996.00007_1206_OCE
OS-2.21.617.1
Mar 15 2018, 12:20:29(1031237)
I'm new to being able to reimage the phone with stock os. Can someone guide me to which files I need to install? I have the HTC sync manager, I have also tried numerous RUU files and I can't seem to find the correct file to install the stock OS. Please help!
Thanks
lucab617 said:
I have also tried numerous RUU files
Click to expand...
Click to collapse
You should try only one - 2.21.617.1 or eventually newer but it would have to be for your model (US, SingleSIM my best guess).
Take the 2.21.617.1, save it properly named on the SD Card and boot into update.
And be more specific - what is the "brick" according to you?
QDT said:
You should try only one - 2.21.617.1 or eventually newer but it would have to be for your model (US, SingleSIM my best guess).
Take the 2.21.617.1, save it properly named on the SD Card and boot into update.
And be more specific - what is the "brick" according to you?
Click to expand...
Click to collapse
The OS is completed wiped from the device, there is no user data and I can't boot into the phone. There is nothing on it except that I can boot into recovery mode using twrp. Where do I find the 2.21.617.1 version? I have scoured the internet and can't find the file. I have the US singlesim model. Please help.
lucab617 said:
The OS is completed wiped from the device, there is no user data and I can't boot into the phone. There is nothing on it except that I can boot into recovery mode using twrp. Where do I find the 2.21.617.1 version? I have scoured the internet and can't find the file. I have the US singlesim model. Please help.
Click to expand...
Click to collapse
I went ahead and tried the following file:
2PZFIMG_OCEAN_NOT[email protected][email protected]
I get the following
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Installing zip file '/external_sd/2PZFIMG_OCEAN_NOT[email protected][email protected]'
Checking for Digest file...
Skipping Digest check: no Digest file found
Verifying zip signature...
Zip signature verification failed!
Error installing zip file '2PZFIMG_OCEAN_NOT[email protected][email protected]'
Updating partition details...
...done
I don't know how to put it without offending you too much.
I said, you need a RUU of same or higher revision - you are showing me an older version.
lucab617 said:
2PZFIMG_OCEAN_NOTE_UHL_N70_SENSE80GP_NA_Gen_Unlock_1.64.617.3[email protected][email protected]
Click to expand...
Click to collapse
The second message is even clearer:
lucab617 said:
Zip signature verification failed!
Click to expand...
Click to collapse
It is not HTC file. Someone has been playing with it.
Third one:
lucab617 said:
There is nothing on it except that I can boot into recovery mode using twrp.
Click to expand...
Click to collapse
If you can get into TWRP you could simply install LeeDroid 2.1 that is for single and double SIM recovery installer and save all the hustle.
QDT said:
I don't know how to put it without offending you too much.
I said, you need a RUU of same or higher revision - you are showing me an older version.
The second message is even clearer:
It is not HTC file. Someone has been playing with it.
Third one:
If you can get into TWRP you could simply install LeeDroid 2.1 that is for single and double SIM recovery installer and save all the hustle.
Click to expand...
Click to collapse
I was able to downgrade to 1.64.617.17, however when I now go to update OTA the phone says
Can't update software
There was an unexpected error and the file system may be corrupted. Please contract HTC support for further assistance.
How do I fix this?
lucab617 said:
I was able to downgrade to 1.64.617.17, however when I now go to update OTA the phone says
Can't update software
There was an unexpected error and the file system may be corrupted. Please contract HTC support for further assistance.
How do I fix this?
Click to expand...
Click to collapse
First - explain, how have you managed to perform the downgrade?
Second - do you have TWRP? If yes - OTA won't work! It has to have the original HTC recovery to handle the upgrade package.
Flash TWRP, If you already have it. Just boot to recovery and flash new custom rom or if you want stock rom so you can downgrade to nougat and then update to Oreo.