Related
This guide will help you to convert your device to OEM totally and permanently. After this procedure you will be able to flash firmware and recieve OTA updates for non CC devices.
Don't be afraid to brick your phone, if something will go wrong, you'll be able to revert back changes without any consequences.
Follow these steps exactly, one after other:
Make backup of all your personal data because they all will be erased. But do not use twrp for backup!
Download full B148 firmware. You can get it from here: https://drive.google.com/folderview?...00&usp=sharing
Extract package with firmware to your sdcard. You should get dload\UPDATE.APP in root directory of your sdcard. If there was update to Lolipop previously, delete it first!
Copy this repacked TWRP in your adb/fastboot directory https://yadi.sk/d/xWXOpG_3hf4iu
Copy this zip-archive to your sdcard https://yadi.sk/d/gw45fwwfhfKU2
Open command shell in your adb/fastboot directory and execute:
Code:
adb reboot-bootloader
your device will reboot in fastboot mode.
Flash TWRP that you downloaded in step #4:
Code:
fastboot flash recovery twrp.img
Disconnect device from PC and power it off by holding power button untill screen off.
Boot into TWRP: press and hold vol+ and power buttons simultaneously untill you'll see boot logo.
In TWRP make backup of oeminfo partition - press "Backup" and mark "OEMinfo". Save backup to sdcard.
Return to main menu, press "Install" and select OEM.zip which was copied to your sdcard in step #5. Swipe to confirm to install package.
This package will patch your oeminfo partition and flash stock recovery. Don't press "Reboot" button after completion.
Disconnect your device from PC or charger if it was connected, power off device by pressing and holding power button untill screen off.
Power on device by three buttons method: press and hold power, vol+, vol- simultaneously untill you'll see boot logo.
Update process should be start.
After successful update to B148 you are good to go to Lollipop.
How to revert back in case if update to B148 will fail:
Switch your device in fastboot mode: power off device, then press and hold vol- and connect device to PC.
Flash repacked TWRP as was mentioned in step #7.
Boot into TWRP, press "Restore" and restore your backup of oeminfo partition made in step #10.
Reboot in system.
If you are brave and desperate enough, you can go much shorter way:
Install TWRP if you had not yet.
Install OEM.zip from step #5.
Update to Lollipop.
Note that in this way you will not have backup and ability to revert back changes and it's not a fact that Lolliip update will proceed, it was not tested, but I presume it will.
I'm not taking any responsibility if you brick your phone, all you will do with your device is on your own risk.
Requirements:
Unlocked bootloader.
I want say thanks to:
@ArkAngel06 for testing, providing me oeminfo and his patience.
@xordos for providing me his oeminfo.
@tdamocles for testing and his responsiveness.
P.S. Sorry for my poor english, it's not my native language.
I have successfully installed Lollipop, the new TWRP and rerooted. A huge thanks to Kostyan_nsk for making this possible for us, CC users and to SHM for providing TWRP for Lollipop. You guys are awesome !! We couldn't thank you enough !
Edit:
I forgot to thank xordos too . . . who has always been a huge help to HAM2 users !
Great, finally, this is another milestone. Dont know how to say in words. and Lollipop... ** Cheeeeeers **
Man, now I am thinking to get a backup phone, after one year, I still not find any other phone at this price level. I mean battery and screen size.
Hat off and Thanks all the hard work.
xordos said:
Great, finally, this is another milestone. Dont know how to say in words. and Lollipop... ** Cheeeeeers **
Man, now I am thinking to get a backup phone, after one year, I still not find any other phone at this price level. I mean battery and screen size.
Hat off and Thanks all the hard work.
Click to expand...
Click to collapse
This is all a little off track, but..
Yeah, I bought mine(CC) off ebay-used-$150/ no charger. Not in bad shape with a small nick on one corner.
This phone runs tons better than my wifes Galaxy s4 with the SD600 on lollipop. The s4 lags like hell. I tried using the s4 with the touchsquid remote app and it was unusable/laggy. The Huawei works great with touchsquid remote app.
where is all CC users?
Anyone think that this will also work for the Wind Mobile version?
Sent from my MT2L03 using Tapatalk
jscrimshaw said:
Anyone think that this will also work for the Wind Mobile version?
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
Yes it works, I did it with my WIND Mobile HAM 2
Each time I try to flash the oem.zip file in TWRP I get:
E: Unable to open zip file
Error flashing zip 'sdcard/OEM.zip'
Updating partition details...
Any ideas please?
johndubs said:
Each time I try to flash the oem.zip file in TWRP I get:
E: Unable to open zip file
Error flashing zip 'sdcard/OEM.zip'
Updating partition details...
Any ideas please?
Click to expand...
Click to collapse
Trying to open your zip file on your PC to make sure it's not corrupt.
medwatt said:
Trying to open your zip file on your PC to make sure it's not corrupt.
Click to expand...
Click to collapse
Thanks Medwatt. I tried thatand all seems to be fine. Is it possible to upload each file individually and flash each of the files in turn?
johndubs said:
Each time I try to flash the oem.zip file in TWRP I get:
E: Unable to open zip file
Error flashing zip 'sdcard/OEM.zip'
Updating partition details...
Any ideas please?
Click to expand...
Click to collapse
Check file permissions and make sure zip file signature verification disabled.
Thanks! This works!
Worked the first time. I have a stock "CC" Ascend mate running L now! Thanks again!
johndubs said:
Thanks Medwatt. I tried thatand all seems to be fine. Is it possible to upload each file individually and flash each of the files in turn?
Click to expand...
Click to collapse
in es file explorer (or you can use other tools in pc), select oem.zip, property, and calc the md5 checksum, it should be
27fed6aca60059671a0208e6f190d3cb
also, you can try different sdcard
xordos said:
in es file explorer (or you can use other tools in pc), select oem.zip, property, and calc the md5 checksum, it should be
27fed6aca60059671a0208e6f190d3cb
also, you can try different sdcard
Click to expand...
Click to collapse
Thanks for your help. MD5 checksum revealed faulty SD card!
when i try to fastboot flash recovery twrp.img I get an error: cannot open 'twrp.img' .... what can be the problem? I downloaded the one in the guide and moved it to my ADB folder and overwrited my old one that was there.
Nevermind, I got it to work on my MT2-L03 SAMPLE. I ended up following the shortcut at the bottom of the guide and used my old TWRP to flash. Thanks for the help dude you're awesome!
GadgetStrutter said:
when i try to fastboot flash recovery twrp.img I get an error: cannot open 'twrp.img' .... what can be the problem? I downloaded the one in the guide and moved it to my ADB folder and overwrited my old one that was there.
Click to expand...
Click to collapse
Sounds like your typing the name of the file wrong....Download again, before moving it into your ADB folder rename it twrp2.img, then move it, then
Code:
fastboot flash recovery twrp2.img[/img]
For those new to convertion (just did it today),
1. Remember to enable USB debugging in Settings
2. Install Adb installer (to use with adb and fastboot commands)
xordos said:
where is all CC users?
Click to expand...
Click to collapse
Worked perfectly on my HAM2 and my wife's. Thanks for all your work on this!!!
OptimusPrimous said:
Worked perfectly on my HAM2 and my wife's. Thanks for all your work on this!!!
Click to expand...
Click to collapse
Thats all @Kostyan_nsk great work that successfully patched CC to OEM, every CC user should press the thanks button in the 1st post if not done that yet.
Went about installing adb and fastboot. Successfully boot unlocked and now when I am trying to flash the update package for B148 the update seems to be going no where.
It did change my CC logos to Huawei one so OEM partitions may have been correctly flashed.
The screen is now stuck at usb update starting...
What can be wrong? Is it safe to reboot at this screen. I suspect the update didnt initialize properly.
I have the update.app copied to the root folder of my microsd and thats what i selected.
Please help. Thanks
Never mind folks, rookie mistake i didnt have the update.app in a dload folder just copied the file itself.
The update is now in progress.
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Same problem here
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Thanks mate, I'll give it a try.
pappapishu said:
Thanks mate, I'll give it a try.
Click to expand...
Click to collapse
any chance?
Fixed it with honor 6 multi-tool, huwaeiupdateextractor and fw b100.
Now i'm installing the b121 right away.
@evilmumi: hope you fixed it as well.
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
evilmumi said:
any chance?
Click to expand...
Click to collapse
sorry, i didn't see your previous post.
yes, i figured out:
- downlaod the fw b100 version
- download honor 6 multi-tool (yes, even if it's made for the 6, it worked for 7 as well) and follow the "unbrick" procedure
if you have any question please ask
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here ...
Follow the instructions in the included documents.
Click to expand...
Click to collapse
thanks
you are my hero.
back in business
i hope i can use titanium backup to restore my old data w/o root
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Alphasampei said:
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
Click to expand...
Click to collapse
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
evilmumi said:
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
Click to expand...
Click to collapse
nope! still boot in twrp, i have no system inside the phone
sometimes we have this problem in our german forum too! More on rooted devices!
reflashing the full B100 or B121 rom help
we do it like your user described it here:http://forum.xda-developers.com/showpost.php?p=63070827&postcount=9
BTW: Where we can find the "updateextractor"? All versions of it that i have found, doesn’t work for H7 Roms!:crying:
Back to System boot
evilmumi said:
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Click to expand...
Click to collapse
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
stalfst said:
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
Click to expand...
Click to collapse
I realized that when I plugged the charger to phone and then powered it, it went off the TWRP boot loop. I fdon't know if any others have same issue.
When I updated my phone I had same kind of problem so I flashed stock recovery and then made the force upgrade following the rom's intructions.
Now eveything works again.
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
kjettern said:
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
Click to expand...
Click to collapse
I had no problems at all, no bootloops or any other weird stuff. Perhaps because I wiped cache + dalvik after supersu installation?
have the same problem, what should i do?
sugarray21 said:
have the same problem, what should i do?
Click to expand...
Click to collapse
Read instruction HERE
Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
• Step 1: Turn off the phone.
• Step 2: Press Volume UP + Power Button For 10 seconds while connecting the USB cable from your device to your computer. That must make you boot into the bootloader mode.
(Update: A user has reported that holding the power button is optional on some models. Thanks to @sminki for pointing that out).
• Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/show....php?t=2433454
• Step 4: Download the latest complete update file (B121) from:
http://www.modaco.com/forums/topic/3...s-121115-b140/
Then, extract it and get its UPDATE.app file.
• Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
• Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
• Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
• Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
• Step 9: Reboot your device using the following command >
Code:
fastboot reboot
• Step 10: You must be able to boot successfully into the system.
(Noten this model, the "fastboot erase [Partition]" command has been reported by two users that it is not working. Thus, flash the image files directly and if it did not work, then check with the Huawei support center to fix your device. Thanks to @sminki for reporting this).
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
TWRP Terminal Emulator command method.
I followed the steps here, http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ Thanks to the Author... hash_brown.1855790
Which is actually for LG, but slightly altering for Honor7 it works!!
for Honor 7 the commands to be run from TWRP Terminal command emulator will be
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/fota
Click to expand...
Click to collapse
Hit GO/enter(return)...wait, takes a few seconds
Now input this
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/misc
Click to expand...
Click to collapse
Hit enter (return)...wait again.
When its complete, reboot.
:good:
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
I had the same problem with twrp i can walking through how to unbrick your phone happy to help
This is for Marshmallow B13. However, I can confirm that installing twrp using tenfars tool still works even on latest B17 nougat or B08 mifavor 5.
However, some users don't have luck with it.
I advise to check first on Axon Toolkit located here:
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
I made this guide for users who haven't unlocked and rooted their A2017 B13 chinese version.
After reading so many guides here from @tenfar, @DrakenFX, and many others, I finally unlocked bootloader, rooted, installed TWRP and Xposed.
I take no responsibility if anything happens to your phone while doing this process. Just follow every step stated here and hope you don't mess around. Please READ all the instructions here first before doing anything.
Backup all your important data before you do any steps below. This process will delete all contents of your phone except external sdcard.
Step 1: Download the zip file and extract all files to your local disk in one folder.
TWRP recovery 3.1.0-0
axon7root.zip
TWRP_UnlockBootloaderPackage_by_DrakenFX.zip do not extract this file.
Step 2: Enable USB debugging and OEM unlocking under Developer options. to show Developer options, go to Settings, About phone, tap Build Number 7x.
Step 3: Open Windows Explorer and browse to the folder where you extracted the files downloaded above. Press and hold SHIFT key then right click and choose Open Command Window here. type:
Code:
adb reboot edl
This will reboot the phone in edl mode where it's just black screen.
Step 4: Install the Qualcomm's driver .
Download Qualcomm driver to your local disk ,extract and install it
Qualcomm 9008 driver : http://d-h.st/35tx
in the install process choose WWAN, the first option.
Alternative: you could just also install the native drivers provided by the phone. If you have done step 2 already, just long press Power button for about 10seconds to reboot to its system. Once booted, connect your phone to your pc via usb and swipe down from the notification. Choose "install drivers" from the connect options. Open your Windows Explorer and find the new drive containing the driver. After installing, repeat step 3.
Step 5 : open your PC's device manager and find out the com port number which your phone is from COM ports & LPT tree.
Code:
Usage Example: axon7root.exe -p COM4 -b -r
Options:
-p Port number eg: COM8 or 8
-b write boot.img only
-r write recovery.img only
-d dump boot.img and recovery.img from phone(not impl yet)
Step 6: in the command window from step 3, type:
Code:
axon7backup.exe -p COM# -d
replace # with the number of your COM PORT.
This will save the backup files for you stock boot and recovery image.
Step 7: to install TWRP, type:
Code:
axon7root.exe -p COM# -r
Step 8: reboot to TWRP by holding POWER + UP buttons.
Optional:
Step 8a: Copy twrp-3.1.0-0-ailsa_ii.img to your sdcard/extsd. Update to latest TWRP. Install -> IMG (lower right button) -> choose twrp-3.1.0-0-ailsa_ii.img. (Don't reboot to system yet)
Step 8b: From the TWRP, find Reboot to recovery. verify that you have version 3.1.0-0 already.
Step 9: Copy TWRP_UnlockBootloaderPackage_by_DrakenFX.zip to your sdcard/extsd.
Step 10: Back-up and pull current fastboot image. Type:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb pull /sdcard/fbop_lock.img
Step 11: Flash/Install TWRP_UnlockBootloaderPackage_by_DrakenFX.zip. (do not reboot yet)
Step 12: Type:
Code:
adb reboot bootloader
Step 13: Now let's Unlock the Bootloader. (THIS WILL WIPE DATA+INTERNAL STORAGE)
Type:
Code:
fastboot oem unlock
Confirm yes from your phone.
Step 14: You'll boot in TWRP. once there do the following:
Code:
* tap CANCEL
* tap WIPE
* tap FORMAT DATA and Follow the Instructions
Step 15: Once done, REBOOT system. Follow the setup wizard to gain access to your phone. enable USB debugging again.
Optional: To install root, Boot to recovery again and install/flash SUPERSU 2.79. download at UPDATE-SuperSU-v2.79-20161211114519.zip and copy to your sdcard.
To install Xposed (for MM only), flash xposed-v87-sdk23-arm64.zip and install the apk XposedInstaller_3.1.1.apk.
Do not REBOOT after installation of Supersu and Xposed. Instead, go to Terminal and type:
Code:
reboot disemmcwp
Credits to all the great minds here in xda for doing all their best.
UPDATE: TWRP flashable zips available. Credits to @parazite69 and the russians for these.
parazite69 said:
Hi just used from a russian website , Flashable b13 zip!
ZTE_A2017V1.0.0B13_BootStack_by_djkuz.zip https://mega.nz/#!AwpE3Lyb!vQuJlu6apdIrqdBqqgxEHsiKdy3Aje3vdqXJupa9A4s
CRC32: CEE662FD
MD5: 67635E2EEE51BFF0E3B6F73591BA88B8
SHA-1: DAC1646FD8B0349CF262C7FD4C15987D5F700304
ZTE_A2017V1.0.0B13_StockSystem_by_djkuz.zip https://mega.nz/#!gpJyGCiC!0CkXk0yj17HK-JTkvkM5JuKflqeeCugZQosmbGj9xPk
CRC32: 79D0419A
MD5: DDD785A98FD32144920970B6B6BE8089
SHA-1: C96EDFE8F414A0D6904DAB1ED8673591D8DE496B
I am using it and it works! I Have just updated the bootstack and then installed the ZAD rom, but if you like the stock just install them both!
Click to expand...
Click to collapse
I'm stuck at B11 A2017 chinese version, can you give me a link for B13 for twrp flash?
danromania said:
I'm stuck at B11 A2017 chinese version, can you give me a link for B13 for twrp flash?
Click to expand...
Click to collapse
I would like this as well.
danromania said:
I'm stuck at B11 A2017 chinese version, can you give me a link for B13 for twrp flash?
Click to expand...
Click to collapse
BlazingBullets said:
I would like this as well.
Click to expand...
Click to collapse
I suggest do a full update to b13 using sdcard update first..
the file can be found on this thread.
https://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
When I got my phone, it was also on B11 rooted. but I upgraded it to B13 without problems.
otaconremo said:
I suggest do a full update to b13 using sdcard update first..
the file can be found on this thread.
https://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
When I got my phone, it was also on B11 rooted. but I upgraded it to B13 without problems.
Click to expand...
Click to collapse
doesn't work if you are unlocked or not using the stock recovery
BlazingBullets said:
doesn't work if you are unlocked or not using the stock recovery
Click to expand...
Click to collapse
I can confirm it's not working, root, unlocked and TWRP.
If somebody can compile B13 for TWRP will really help us.
Thanks!
You're right. You'll need stock recovery to do a full update though. I haven't backed up my B11 stock recovery but I do have the B13 stock boot and recovery. Message me if you want those files.
Sadly no one else wants to make a twrp update for B13. And I don't know how. I already asked from draken a couple of months ago but i think he has never got a time for it.
Can you help me,
I try to step by step but step 8
Went i push POWER + UP volume, i have a black screen, not TWRP, i can not do any thing
I would love to try this since I want to try installing a2017U nougat ora2017 G software instead Chinese stock but the link for axon7backup: http://d-h.st/Ienb is timing out and dead. I can't seem to get any twrp recoveries working with the other axon7tool method https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 and also the signed twrp is gone. I need a working recovery the files from here. Will try reinstalling b10 and then try find b11 for the current recoveries to see if any work instead of giving me a black recovery screen.
Hello was wondering about the terminal reboot portion. I've been rooted with SU for a few days now can I just flash Xposed and install the apk without the worry of using terminal? Thanks
Sent from my ZTE A2017U using XDA-Developers Legacy app
thanhtri87 said:
Can you help me,
I try to step by step but step 8
Went i push POWER + UP volume, i have a black screen, not TWRP, i can not do any thing
Click to expand...
Click to collapse
try pressing just the power and Up buttons until it reboots and release when you see the ZTE logo. that should enter you into recovery.
yvgamer94 said:
I would love to try this since I want to try installing a2017U nougat ora2017 G software instead Chinese stock but the link for axon7backup: http://d-h.st/Ienb is timing out and dead. I can't seem to get any twrp recoveries working with the other axon7tool method https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 and also the signed twrp is gone. I need a working recovery the files from here. Will try reinstalling b10 and then try find b11 for the current recoveries to see if any work instead of giving me a black recovery screen.
Click to expand...
Click to collapse
the links were up okay as I opened them now. you may want to disable your antivirus too since this will trigger it false positive.
also, all the files I used were posted in the links i posted. credits to the owners btw.
HTC55555 said:
Hello was wondering about the terminal reboot portion. I've been rooted with SU for a few days now can I just flash Xposed and install the apk without the worry of using terminal? Thanks
Sent from my ZTE A2017U using XDA-Developers Legacy app
Click to expand...
Click to collapse
have you tried your method without the terminal command? personally, I don't know if that works without the command but I just used it since it won't harm anyway.
danromania said:
I'm stuck at B11 A2017 chinese version, can you give me a link for B13 for twrp flash?
Click to expand...
Click to collapse
Hi just used from a russian website , Flashable b13 zip!
ZTE_A2017V1.0.0B13_BootStack_by_djkuz.zip https://mega.nz/#!AwpE…siKdy3Aje3vdqXJupa9A4s
CRC32: CEE662FD
MD5: 67635E2EEE51BFF0E3B6F73591BA88B8
SHA-1: DAC1646FD8B0349CF262C7FD4C15987D5F700304
ZTE_A2017V1.0.0B13_StockSystem_by_djkuz.zip https://mega.nz/#!gpJy…uKflqeeCugZQosmbGj9xPk
CRC32: 79D0419A
MD5: DDD785A98FD32144920970B6B6BE8089
SHA-1: C96EDFE8F414A0D6904DAB1ED8673591D8DE496B
I am using it and it works! I Have just updated the bootstack and then installed the ZAD rom, but if you like the stock just install them both!
parazite69 said:
Hi just used from a russian website , Flashable b13 zip!
ZTE_A2017V1.0.0B13_BootStack_by_djkuz.zip https://mega.nz/#!AwpE…siKdy3Aje3vdqXJupa9A4s
CRC32: CEE662FD
MD5: 67635E2EEE51BFF0E3B6F73591BA88B8
SHA-1: DAC1646FD8B0349CF262C7FD4C15987D5F700304
ZTE_A2017V1.0.0B13_StockSystem_by_djkuz.zip https://mega.nz/#!gpJy…uKflqeeCugZQosmbGj9xPk
CRC32: 79D0419A
MD5: DDD785A98FD32144920970B6B6BE8089
SHA-1: C96EDFE8F414A0D6904DAB1ED8673591D8DE496B
I am using it and it works! I Have just updated the bootstack and then installed the ZAD rom, but if you like the stock just install them both!
Click to expand...
Click to collapse
Great find! Do you mind if I put this in my OP so that others can use it too? Seems like a lot of other users can't manage to get my method well.
otaconremo said:
the links were up okay as I opened them now. you may want to disable your antivirus too since this will trigger it false positive.
also, all the files I used were posted in the links i posted. credits to the owners btw.
Click to expand...
Click to collapse
Thanks for replying. The link works until you try to download it. When you get past the ads, you get to this http://fs1.d-h.st/download/00237/Ienb/axon7backup.zip Did you also try downloading it? Either I am doing something wrong? Thanks.
yvgamer94 said:
Thanks for replying. The link works until you try to download it. When you get past the ads, you get to this http://fs1.d-h.st/download/00237/Ienb/axon7backup.zip Did you also try downloading it? Either I am doing something wrong? Thanks.
Click to expand...
Click to collapse
Yes I did download my files using those links. Try installing adblock plus on your browser. Or try other browsers.
otaconremo said:
Great find! Do you mind if I put this in my OP so that others can use it too? Seems like a lot of other users can't manage to get my method well.
Click to expand...
Click to collapse
Sure go ahead.
otaconremo said:
Yes I did download my files using those links. Try installing adblock plus on your browser. Or try other browsers.
Click to expand...
Click to collapse
It's probably just my pc or browser. It's ok though since I managed bootloader unlock and flash twrp with this guide instead:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/
Thanks for your help though
I have one (stupid) question for which I can't find answer: I stuck at step 2 when I need to enable OEM unlocking. Problem is that some PIN is required but I don't know it and don't know where to find it? Many thanks!
Man every phone I get, I brick!! Im stuck in a BLU boot loop. Can't find any files out there for this model. Well did see one here
http://clangsm.com/ftpdemo/index.php?dir=Flashes/BLU/Studio%20XL%202/
They want $$ for the download :crying:
Anyone a member there that could get me this file?
Thanks for the help
Try this
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
what version is this?
dougunder said:
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
Click to expand...
Click to collapse
is this firmware v08? it rendered my phone inoperable. no cell, no camera and several other issues. the phone came installed with v09
Anyone ever find V09??
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
crmcc said:
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
Click to expand...
Click to collapse
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
mrmazak said:
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
Click to expand...
Click to collapse
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
killer13666 said:
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
Click to expand...
Click to collapse
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
mrmazak said:
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
Click to expand...
Click to collapse
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
killer13666 said:
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
Click to expand...
Click to collapse
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
mrmazak said:
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
Click to expand...
Click to collapse
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
Click to expand...
Click to collapse
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
Click to expand...
Click to collapse
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
mrmazak said:
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
Click to expand...
Click to collapse
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
killer13666 said:
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
Click to expand...
Click to collapse
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
mrmazak said:
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
Click to expand...
Click to collapse
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
killer13666 said:
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
Click to expand...
Click to collapse
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
mrmazak said:
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
Click to expand...
Click to collapse
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
killer13666 said:
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
Click to expand...
Click to collapse
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
mrmazak said:
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
Click to expand...
Click to collapse
So in other words, it won't let you flash anything that'll modify the data partition as well?
killer13666 said:
So in other words, it won't let you flash anything that'll modify the data partition as well?
Click to expand...
Click to collapse
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
mrmazak said:
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
Click to expand...
Click to collapse
Please do let me know how that goes.
Hi guys,
for those on system/bootstack by tron1, this is what i did to flash B02 with root and fastboot working.
Thnx to @wineds , @tron1
In detail this is what i did ( because i couldn't update the .zip from sd nor update through adb sideload after i installed stock recovery 711 - @wineds could flash the .zip over SD though - thats up to you to choose)
1. I redownloaded fota B02 (to be sure ) from : http://dl1.ztems.com/zxmdmp/downloa...ages/HK/ZTE/ZTE A2017G/401379/fota_B02_B04.up
2. I didn't change .up to .zip. Put it in ADB folder (you know how...)
3. reinstalled Bootstack B01 tron1 via TWRP ( i reuploaded it here because some users had zip problems : https://www.androidfilehost.com/?fid=457095661767157153 )
4. reinstalled System B01 tron1 via TWRP ( i reuploaded and checked it again because some users had zip problems : https://www.androidfilehost.com/?fid=529152257862722738 )
5. installed stock recovery from factory img 7.11 , I uploaded it here https://www.androidfilehost.com/?fid=745425885120725539
6. in TWRP reboot to recovery----> you will reboot in stock recovery
7. update from ADB sideload ( adb sideload yourupdateB02file.up)
8. let it update...will take +-5 min in my case, in my case it was hanging a while on 47% (i thought it froze and tapped on power once, it continued...perhaps you don't have to and wait )
9. reboot system----> you'll have B02
10. use adb again, use ADB REBOOT EDL (https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379), use command ' axon7tool -w recovery' just to reflash TWRP 3.0.2.2 (if needed : https://www.androidfilehost.com/?fid=529152257862720446) . It will reboot system ok. Reenter TWRP 3.022 again and stay there.
11 to get fastboot again, use same thread as above under B ( leave TWRP running), in ADB you'll see you're in recovery mode, that's ok.
12. refollow steps 6 to 14. Reboot to fastboot will be ok again !
13 now in ADB type : fastboot flash recovery 'yourlatestrecovery 3.1'.img (if needed : https://www.androidfilehost.com/?fid=529152257862720448)
14. fastboot reboot
14. your system will reboot without the anoying " blah blah blah unlocked"
15 reenter TWRP 3.1 again and flash SU2.79 again
16 done
17 pls comment/feedback if you succeeded as well
@raystef66
Your links in steps 1 and 10 are invalid due to copy/paste ellipsis (...).
dnlilas said:
@raystef66
Your links in steps 1 and 10 are invalid due to copy/paste ellipsis (...).
Click to expand...
Click to collapse
Some of them were...weird, i never had this problem reffering to other threads..
Did update links. Check them out to verify pls.
Thnx !
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
S0wL said:
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
Click to expand...
Click to collapse
Have you tried in stock recovery to update with sd instead of sideload with adb? You also could try changing . UP to . ZIP
raystef66 said:
Have you tried in stock recovery to update with sd instead of sideload with adb? You also could try changing . UP to . ZIP
Click to expand...
Click to collapse
I tried with stock recovery with sideload and with sd as well. with .up and .zip too and I get the same error .
@raystef66 thanks for ur guide
I need to update to b02 but I don't have courage to lose root
Anyone please report after success
Sent from my ZTE A2017G using XDA-Developers Legacy app
tuiyaan said:
@raystef66 thanks for ur guide
I need to update to b02 but I don't have courage to lose root
Anyone please report after success
Sent from my ZTE A2017G using XDA-Developers Legacy app
Click to expand...
Click to collapse
this method has been tried originally by @wineds - he only updated via SD, that's all and changed .up into .zip
In fact you have nothing to fear because when f.e. you're in stock recovery and things won't update as expected, you always can go back in ADB and flash recovery again with axon7tool (EDL) etc...there's always a way out. And have root back....
When your update succeeds after all, you WILL obtain root again as i discribed. Just follow the steps carefully.
I managed to do this in 1 take
S0wL said:
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
Click to expand...
Click to collapse
Yes rename FOTA as a .zip file and try update from SD card in stock recovery. The fIle needs to be on your external SD. However the error seems to indicate one of your partitions has been modified.
Isn't it easier to
-update to B02
-axon7tool -w recovery
-disconnect before the Success, rebooting countdown ends
-boot TWRP??
Someone made a flashable fastboot zip. haven't tested yet but I guess it will get us fastboot easier
Choose an username... said:
Isn't it easier to
-update to B02
-axon7tool -w recovery
-disconnect before the Success, rebooting countdown ends
-boot TWRP??
Someone made a flashable fastboot zip. haven't tested yet but I guess it will get us fastboot easier
Click to expand...
Click to collapse
Nope, did that too and was a no go. That would have been one of the options to do (i made a thread for this too) but in this case fastboot didn't want to boot with that method strange enough. But you could try and see for your self.
For me this method worked great and i stay 100% stock despite other flashable b02's which are customized.
raystef66 said:
Nope, did that too and was a no go. That would have been one of the options to do (i made a thread for this too) but in this case fastboot didn't want to boot with that method strange enough. But you could try and see for your self.
For me this method worked great and i stay 100% stock despite other flashable b02's which are customized.
Click to expand...
Click to collapse
Yeah, fastboot doesn't want to boot because it isn't there... I mean get to EDL then flash TWRP from there with axon7tool.
I used this method on my guide and it's been working flawlessly
Choose an username... said:
Yeah, fastboot doesn't want to boot because it isn't there... I mean get to EDL then flash TWRP from there with axon7tool.
I used this method on my guide and it's been working flawlessly
Click to expand...
Click to collapse
To get fastboot back you have to downgrade aboot to b01 version :
https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
wineds said:
To get fastboot back you have to downgrade aboot to b01 version :
https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
Click to expand...
Click to collapse
Yeah, and you can flash that once you get TWRP
I'm going to update that guide, but the XDA app doesn't let me edit, and I'm far away from a computer. I'll write the process and see if I can try to get fastboot with that zip storming did. For now the process i have in mind is:
Get axon7tool, adb reboot edl, install Zadig qusb_bulk drivers, reload edl with 3 buttons, axon7tool -w recovery (after a backup ofc), disconnect before the tool restarts the phone (you get stock recovery), flash that zip.
Choose an username... said:
Yeah, and you can flash that once you get TWRP
I'm going to update that guide, but the XDA app doesn't let me edit, and I'm far away from a computer. I'll write the process and see if I can try to get fastboot with that zip storming did. For now the process i have in mind is:
Get axon7tool, adb reboot edl, install Zadig qusb_bulk drivers, reload edl with 3 buttons, axon7tool -w recovery (after a backup ofc), disconnect before the tool restarts the phone (you get stock recovery), flash that zip.
Click to expand...
Click to collapse
Or use my method
Works too you know :laugh:
Never mind how you do it every method is ok.
I kept it to the basics every one should know by now. In fact performing the steps to get fastboot again lasts no more then a minute. Just copy paste...
Btw, don't brick your phone again! :cyclops: as i remember you came from the other side of the moon...
raystef66 said:
Or use my method
Works too you know :laugh:
Never mind how you do it every method is ok.
I kept it to the basics every one should know by now. In fact performing the steps to get fastboot again lasts no more then a minute. Just copy paste...
Btw, don't brick your phone again! :cyclops: as i remember you came from the other side of the moon...
Click to expand...
Click to collapse
Lol I wiped system and data and was holding the power button... Can't believe I was that silly.
My guide actually turned out pretty huge too. So whatever man
Choose an username... said:
Lol I wiped system and data and was holding the power button... Can't believe I was that silly.
My guide actually turned out pretty huge too. So whatever man
Click to expand...
Click to collapse
Cheers mate and...happy flashing! :good:
Hi, when I try to flash stocksystem by tron1, TWRP tell me that the zip is incorrect and he can't flash it. I tried to download it again and again but still doesn't work.
fabro91 said:
Hi, when I try to flash stocksystem by tron1, TWRP tell me that the zip is incorrect and he can't flash it. I tried to download it again and again but still doesn't work.
Click to expand...
Click to collapse
Dont think the zip is incorrect. Flashed it without any errors. Others too. You're on latest 3.1.0.0 and SU2.79? Is zip in root of sd/internal?
No on external sd
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
Didn't work with sideload anymore