Related
About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...
I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.
THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build
Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!
Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones
Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.
Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:
Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.
Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
buzz-27 said:
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
Click to expand...
Click to collapse
Finally the solution it was in the good files versions, I used this one :
- OS : WIN10
- Tools: SP Flash tool V5.1744
- Driver : MTK V1.0.8 and install DRIVER AUTO 1612
- FIRMWARE : ac70-20180912-1740-New
Hello buzz-27, it would be great, if you could tell me, where you can download the Firmware - same problem here Thank you!!!
buzz-27 said:
Hello,
After try to flash the recovery on my device, the device stay lock on secure boot.
I have probably missing a step for the secure boot, well.
Archos send me the firmware and windows driver and DA file, i can link the files if you want.
But after many test with many version of SP flashtools I have always an error
On linux : STATUS_DA_HASH_MISMATCH (-1073283068) , MSP ERROR CODE : 0x00.
Can Help me ?
Thanks
Click to expand...
Click to collapse
Hi,
I have recently bricked my AC70HELLO and tried uncessefully to flash stock firmware (from firmwarefile.com/archos-hello-7 ) but always got STATUS_DA_HASH_MISMATCH (with SP Flash Tools V5.1924 and V5.2020) or STATUS_BROM_CMD_SEND_DA_FAIL (with SP Flash Tools V5.1744) errors (with MTK_AllInOne_DA or DA_PL defaults DA).
Could you please share the Download Agent and the stock firmware from Archos ?
I have asked Archos for it in vain, they respond me "Sorry we don't have any FW available for this device. Thanks for your understanding," which got me a bit mad... I mean if my device's constructor doesn't have its stock firmware then who does ?
Here's the "latest" fimware from Archos http://update.archos.com/AFMv2/downloads/ac70hello_archos/20181101.075911/update.zip
Does anybody happen to have a reliable guides and reliable downloads to flash other firmwares to this Hello 7?
I tried several guides but somehow they are inconsistent, incomplete or simply not working. Some say I need TWRP without a link to a working image, others say I could use fastboot which generates "not allowed in locked state". I found out myself that I could work around that error by running "fastboot oem unlock" but after flashing, my Hello keeps hanging in a boot loop. (also after "fastboot oem lock")
Fortunately with @fraenK 's link, I could revert back to stock.
I have been using the Pixel Experience 10 GSI ROM from Expressluke so far. Other GSI ROMs should work as well. https://forum.xda-developers.com/t/gsi-expressluke-built-gsis.4003457/
fraenK said:
Here's the "latest" fimware from Archos http://update.archos.com/AFMv2/downloads/ac70hello_archos/20181101.075911/update.zip
Click to expand...
Click to collapse
Thanks but this is unusable without a working recovery wich I don't have since I'm bricked (corrupted logo.img so crash before booting in anything) would you know where I could find the download agent to use with sp flash tools ?
Archatos said:
Does anybody happen to have a reliable guides and reliable downloads to flash other firmwares to this Hello 7?
I tried several guides but somehow they are inconsistent, incomplete or simply not working. Some say I need TWRP without a link to a working image, others say I could use fastboot which generates "not allowed in locked state". I found out myself that I could work around that error by running "fastboot oem unlock" but after flashing, my Hello keeps hanging in a boot loop. (also after "fastboot oem lock")
Fortunately with @fraenK 's link, I could revert back to stock.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ -> how to install a GSI (with fastboot or TWRP)
https://forum.xda-developers.com/t/aosp-10-0-2019-12-06-quack-phh-treble.3992559/ -> AOSP with or without gapps and stock GSI rom (if I recall correctly before bricking, the Hello 7 needs an arm64 A-only image)
Hello,
If I can help you, I create a zip file with Driver, Firmware and the compatible SP_Flash for this firmware.
I flashed my Hello with success and I don't sure of all step, cause many test before sucess.
Just put WIN10 in "Test Mode" can help
http://dl.free.fr/getfile.pl?file=/Zn8HQVpO
press "Valider et télécharger le fichier"
Now I am in GSI Android and the Hello work perfectly !
I got same problem with Archos hello 10 version where can i find stock rom for this device? @fraenK @buzz-27 maybe you know?
urkelz said:
I got same problem with Archos hello 10 version where can i find stock rom for this device? @fraenK @buzz-27 maybe you know?
Click to expand...
Click to collapse
http://update.archos.com/AFMv2/downloads/ac101hello_archos/20181114.085412/update.zip
Thanks alot @fraenK downloading now. Anyone got a DA file I can use? Probably will get DA hash mismatch.
Hi everyone,
I bricked my Archos Hello 7 by trying to flash TWRP.
I'm looking to flash my device but it's hard to find informations for this device and nothing works for me.
I tried with SP Flash tool V5.1744 and few drivers versions without results.
I always have STATUS_DA_HASH_MISMATCH or BROM_CMD_SEND_DA_FAIL.
Every time I plug my device, the detected USB is the "Mediatek PreLoader USB VCom", do you think it's the good driver ?
@buzz-27 can you (or someone else) upload your file again, the link on Free is dead.
@Dawnowl444 did you solve your flashing problem ?
Thanks guys.
CameleonTH said:
Hi everyone,
I bricked my Archos Hello 7 by trying to flash TWRP.
I'm looking to flash my device but it's hard to find informations for this device and nothing works for me.
I tried with SP Flash tool V5.1744 and few drivers versions without results.
I always have STATUS_DA_HASH_MISMATCH or BROM_CMD_SEND_DA_FAIL.
Every time I plug my device, the detected USB is the "Mediatek PreLoader USB VCom", do you think it's the good driver ?
@buzz-27 can you (or someone else) upload your file again, the link on Free is dead.
@Dawnowl444 did you solve your flashing problem ?
Thanks guys.
Click to expand...
Click to collapse
Hi,
My AC70HELLO is still bricked unfortunately. I've got a corrupted logo.bin and no way to flash stock rom except with SP Flash Tool. But I can't get passed STATUS_DA_HASH_MISMATCH error.
I tried this utility without much success...
GitHub - MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
With --force I still get STATUS_DA_HASH_MISMATCH and the utility says "Device secure boot: False ; Device serial link authorization: False ; Device download agent authorization: False" wich is weird...
Let me know if you got any more luck with that than me.
If your AC70HELLO is'nt really bricked you can try to flash back stock recovery via fastboot.
Hi Dawnowl444,
Thanks for your tips, I gonna try with bypass_utility but without hope .
Maybe we need to do some hardware tweak to allow to flash the device.
There is here a French tutorial to disassemble the Hello 7. http://rnc.free.fr/hello7/hello7.html
In the firmware I found online, the file Checksum.ini refers to the version 1708 of SP Flash Tool, I tried with itn but without success, maybe it can be successful for you.
Unfortunately, I can't boot into recovery mode, that's why I try to flash with the Flash Tool.
If I succeeded to flash my device I will let you known.
buzz-27 said:
Hello,
If I can help you, I create a zip file with Driver, Firmware and the compatible SP_Flash for this firmware.
I flashed my Hello with success and I don't sure of all step, cause many test before sucess.
Just put WIN10 in "Test Mode" can help
http://dl.free.fr/getfile.pl?file=/Zn8HQVpO
press "Valider et télécharger le fichier"
Now I am in GSI Android and the Hello work perfectly !
Click to expand...
Click to collapse
Hello @buzz-27 , could you upload the file again?
I was try update my Hello 7 and now it restarting continuously.
Hello, is not possible immediately but I try to push the file in a few weeks or before maybe.
Ok thanks. By mistake I'm flashed the Hello 10 ROM in my Hello 7, and now it restarting continuously. I can enter in fastboot but I cannot flash the ROM - error: FAILED (Remote: not allowed in locket state) Do you know another way to flash the correct firmware? I can not enter in recovery mode.
Hello guys for Hello device
Link below with SP tool, Driver and Firmware for Hello 7 this pack work on my Hello 7.
Upload files for free - Restore_Archos_AC70Hello.zip - ufile.io
Download Restore_Archos_AC70Hello.zip for free from ufile.io instantly, no signup required and no popup ads
ufile.io
enjoy !
Thanks buzz-27, unfortunately, it didn't work for me.
Can you tell us which DA did you use ? I have tried all DA from the SP Flash tool with no results.
Maybe we have a different model/revision, mine has the FCC ID : SOVAC70HELLO
Hi guys, I did something very stupid, flashed the wrong boot.img and ended up completely bricking my device. I tried changing the active partition to see if it would boot, that didn't help.
I was on the latest august update of official android 11 . Then I found a boot.img I found online, but apparently it wasn't from the exact same rom. The phone booted but no WIFI.
It wouldn't allow me to flash any update through settings - system update hence I decided to try to use a fastboot rom....tried that, but the process when I hit flash_all.bat gives a lot of FAILED (remote: Flashing is not allowed for critical particions) or FAILED (Error reading sparse file)....what am I doing wrong?
I can't do anything except get in fastboot.
Is there any way I can get the phone to work agan? Needless to say that as the idiot I am the whole phone is wiped so this doesn't matter anymore. As long as I can get it to work.
Please advise and thanks (The phone is OP7T Pro ME european).
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
leginhee said:
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
Click to expand...
Click to collapse
Thanks the problem is i can't get it to start qualcomm edl. I power off, press both vol buttons and conmect to usb but nothing happens. What am i doing wrong?
Qualcomm edl Mode is just a blackscreen
"I can't do anything except get in fastboot."
Your Bootloader was unlocked ?
You can try fastboot reboot edl.
Or you can find a ROM that works, extract all images and flash all of them.
I have a similar problem.. kind of. I just flashed a rooted boot to my phone but there is no wifi at all, and since i dont have a SIM card im not getting any updates. the Boot.img came from the oneplus software update and i did the payload dumper. Since I have rooted it ive lost the wifi capabilites. (its the 7T pro me international.)