Hi, my problem is with the L31,
I've trying to downgrade from Nougat to MM. I saw on the thread this steps and i followed:
"Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Then I flashed badwolfs recovery b2 as that one lets me transfer files from pc to phone and followed instructions from htcmania from here".
The problem is that i didn't reach to downgrade and when i try to reinstall Nougat by TWRP i get this error messages:
" E: Unknow comand (errno) update_huawei-pkg_from_ota_zip: update package from zip failed"
"Updater process ended with error: 7
Error installing zip file '/external_sd/DLoad/Update.zip'
Updating partition details...
...done"
Now my phone stays freeze on the huawei logo and the flashtool doesn't even recognize my device.
Can someone help me with this matter, please?
try to flash stock recovery and do a factory reset
simo255 said:
try to flash stock recovery and do a factory reset
Click to expand...
Click to collapse
Problem solved.:good:
aalmeida1972 said:
Problem solved.:good:
Click to expand...
Click to collapse
how did you flash a stock recovery please ???
darth_us37 said:
how did you flash a stock recovery please ???
Click to expand...
Click to collapse
I followed the steps that someone advice me. Like above.
"I had to first extract the nougat firmware with huawei firmare extractor and flash everything by fastboot
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Booth files you can find it in this page.
http://forum.xda-developers.com/huawei-p9lite/development/android-nougat-dev-build-huawei-t3488360/page33"
To flash img. i used the file that i attached.
Good luck
so now i restored twrp , i put the update app in sd card and it doesn't want to flash , i'm still trapped in bootloop but i have access to twrp now what to do now ?
I found the old twrp is okey for downgrade,
Just put b161 update.app into sdcard/dload and press volume down + power key.
but flash badwolf's twrp will get stuck in fastboot, though It's not really bricked.
hi, maybe you also have a solution for my problem.
i installed a wrong update via sd card (dload etc.), now my phone is just black no signal nothing. and it seems like a fastboot loop always when i plug into the pc im in fastboot without doing anything
when i try to unlock the bootloader i get "failed command not allowed")
and also when i try to flash the extracted files from update.zip i get the same error ("failed command not allowed")
by the way i didnt active usb debuggin or oem unlocking
please help thank you
Hi,
is it possible to relock the bootloader to original factory mode.
fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.
After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?
I am interested in a tutorial about going back to stock for G model
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.
Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse
dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.
i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?
Any help for the G modell ?
dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.
Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.
@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.
how can i flash my original recovery. what is the command for cmd ?
Please help restoring back original recovery.
dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.
I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?
Hi guys,
I'm just finalising restoring an A2017 (China) to stock for warranty exchange.
I have gone back to stock OS, locked bootloader but I still have the TWRP recovery.
I believe all I need to do is flash a stock recovery.img though TWRP and voila I should be finished, but I can't find a download link that definitely points me to what I should use.
Could someone point me in the right direction?
Thanks!
EDIT - Actually wait a minute can I just install full A2017 factory OTA update through MiFavor stock OS which I believe contains recovery, does that mean that everything goes back to stock (including recovery)?
https://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
EDIT2 - When I try to install the A2017 B13 update.zip through MiFavor it says update failed. Should I install it through TWRP?
EDIT3 - Refused to update the whole image (update.zip) through MiFavor within the ZTE OS. I flashed the default recovery.img through fastboot, then I used the MiFavor recovery (not in OS) to manually flash the full image.
Anyway, got it to stock!
Where did you got the recovery.img?
MagicSeeker said:
Where did you got the recovery.img?
Click to expand...
Click to collapse
In the link from my post above. Download the original stock ROM you want, unzip, one of the files is the recovery.img. FYI I had A2017 B11, installed B13 recovery.img and it worked fine.
I tried to flash recovery.img but it says: FAILED (remote: Partition flashing is not allowed)
What do I do? I'm on B13 stock with locked bootloader. I want to get rid of TWRP and back to stock recovery so I can get OTA updates again.
FuzzyDunlop9 said:
I tried to flash recovery.img but it says: FAILED (remote: Partition flashing is not allowed)
What do I do? I'm on B13 stock with locked bootloader. I want to get rid of TWRP and back to stock recovery so I can get OTA updates again.
Click to expand...
Click to collapse
The first step in flashing anything is to unlock the bootloader, flash TWRP recovery, root, custom ROM etc. The inverse is the same. You are trying to flash an image to the recovery partition with a locked bootloader, which isn't going to work. I'd suspect you need to unlock your bootloader again, flash the stock recovery from the B13 stock image, and re-lock the bootloader. I am fairly new to the Axon 7 but I would consider yourself lucky if your bootloader is in fact locked. Typically locking the bootloader with anything but stock recovery is messy...
jdgesmlls said:
The first step in flashing anything is to unlock the bootloader, flash TWRP recovery, root, custom ROM etc. The inverse is the same. You are trying to flash an image to the recovery partition with a locked bootloader, which isn't going to work. I'd suspect you need to unlock your bootloader again, flash the stock recovery from the B13 stock image, and re-lock the bootloader. I am fairly new to the Axon 7 but I would consider yourself lucky if your bootloader is in fact locked. Typically locking the bootloader with anything but stock recovery is messy...
Click to expand...
Click to collapse
You usually end up with a DFU brick, sometimes only with fastboot. Very messy
There are flashable recovery zips for the A2017G, maybe @tron1 can make you one?
Hi I was on viper rom I relocked my bootloader and went s-on. So now my phone won't let me boot because the software has been tampered and all my efforts to flash a new ruu has failed.
I'm trying to follow method 3 from here
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
If i use htc_fastboot command it is not recognized, so i remove HTC_ and just use fastboot and it'll boot to ruu mode but when I use "fastboot flash zip" it tries to flash and fails I've tried the newest ruu I've tried
2.41.605.20 Full Stock Firmware with stock boot.img and stock recovery included(will replace/remove Twrp/will wipe/encrypt)
from
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
as well as (2.41.605.20_FULL_Stock_firmware.zip) and the hboot for 1.65.605.8
I'm currently downloading the ruu exe for 1.82.605.6 since that is the version I am on, hoping that works does anyone have any good news for me?
next ... After unlocking the bootloader of my g4 plus bike, I made the installation of the rom and an update arrived via ota ... I placed to make the installation and after made the cell phone hung up and did not call any more ... then I did the blankflash and the mobile came back in fastboot mode with the boot blocked again, now I can not install any rom and nor unblock the boot by not having the option oem unlock checked ... my question is the following have some way to enable the option unlock boot without starting the system, by adb or something, or do the installation of some rom with the boot blocked? Thank you very much in advance
Which ROM did you flash onto your device?
As far as I understand, you cannot enable the OEM unlocking option without booting to system, and as your bootloader is set to OEM_locked by the blankflash, you need to flash the stock ROM firmware to get your system working.
I'd suggest looking into flashing the latest stock ROM firmware, follow this unbricking guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
If that doesn't work, then you may have to wait for a newer firmware or submit your device for an expensive service repair.
For future reference, if you did flash an older stock ROM firmware, please delete that and only flash stock ROM firmware as new or newer than your bootloader. If you do want to flash older stock ROM firmware, do not use OTA updates please. Old OTA updates corrupt your bootloader and thus lead to a hard brick.