Related
Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.
Can someone walk me through how to Unlock the bootloader, root, and install TWRP? I'm so confused. I tried to do the newbie way, even though I'm not a newbie, and I lost my B29 Stock Recovery and can't find the download for it.
Sent from my ZTE A2017U using Tapatalk
I haven't done it yet but I've done a lot of reading and this seems to me the best guide.
Head over to this link which is the TWRP thread. https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
Once you're in there go to bootloader unlock section. Download all the necessary files and on the bottom of the guide there will be instructions link which will take you here https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
Follow that and that should do it.
When i get a weekend off ill be using this method to get the Lineage OS 14.1 on my device.
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
amphi66 said:
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
Click to expand...
Click to collapse
greatzt said:
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
Click to expand...
Click to collapse
This was back last Nov, but I followed the guide, using the recommended files (was on B29, but used the B27 OK, then reflashed B29 at the end).
The warning involved backing up and then restoring the EFS partiton with tenfar's tool. DON'T! If you stick with system, data, and boot partitions you should be fine.
Good luck. You may want to check with @nolimit78. He has done this much more recently.
Yes, I agree with you @amphi66 that there is a lot of different places to get information about how to root/flash recovery for A2017U B29. Here's what I've done with two different A7's and both have worked each time.
1. Boot the phone to EDL Mode (Both Vol+Power on boot it'll quick flash the red notification light and then act like it's off.. it's not)
2. Use tenfar's tool to flash the recovery. (I renamed the updated TWRP img and named it "recovery". This used tenfar's tool to flash the updated TWRP on your device.
3. Once in TWRP, run the command (reboot disemmcwp and relaunch TWRP) and flash the package to use modifiable bootloader from B20.
4. Once that flashes now you can send the command in Fastboot "fastboot oem unlock" which will unlock the bootloader that doesn't trip anything notifying ZTE
5. At this point you can flash a B29 rom and have a grand ol' time. However, I would recommend using the LineageOS Rom that's available. Trumps everything else out there IMHO.
6. To do that You'll need to flash the Nougat Bootstacks for that rom to boot prior to flashing the Rom itself. I would recommend flashing the nougat bootstacks, reboot to TWRP, flash LineageOS, reboot.
Like I said, I've done with this with two different devices (Thanks ZTE) and both worked out just fine. I did this method with a device with b27 and b29, both ended up updated and flashed with CM/LineageOS with ZERO issues. This post here should also be pinned as the one true guide (THE KING OF THE NORTH) for unlocking/rooting a stock Axon 7. I spent probably about 4-5 hours working, trying to figure out how to get my device unlocked/rooted. However.. at the very end I wrote out instructions trying to help those who would come after me.. I searched the threads to make sure there wasn't already a thread out there.. and then.. it turns out there was.
Someone have the 5 files to unlock the bootloader 2017u on drive
Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..
Hi all
So it was all running nice and stable, before the evil b25 update that destroyed my axon 7 completely and made it useless, I'll tell how
so after updating I figured out I can't access fastboot to flash anything, and I figured out I wasn't the only one with this "meme" that zte made.
so I decided to roll back to b19 using Miflash and b19 edl package, I thought my problem would end here.
Then I flashed twrp via fastboot, and upgraded to b25 using b25 bootstack + b25 zip by drakenfx, all good.
then I tried to root b25 the good ol' way by flashing supersu zip, only to find that I'd end up with this newer meme, "unable to find su binary"
seems like the sort of thing you'd get if you had a locked bootloader, which is suspicious, judging that no one was able to get fastboot on b25
I also figured out I wans't the only one as people from "root b25" threads know that you can't root b25 even if you had twrp
so I rolled back again to b19 using miflash....you know the story
now here comes the interesting part, the meme, didn't go away, I tried to root my b19 a2017u by flashing supersu
I tried everything, flashing b19 bootstack, formatting data flashing different supersu versions etc.
, either ended up with a bootloop, or the famous "su binary is not installed"
I never had this before updating to b25 and now I can't get rid of it even without b25
can someone guide me to root stock b19 properly and get rid of this meme? (bonus if you know how to root b25 properly because I liked b25 more, there is a7x kernel for b25 so I guess we can root b25? maybe not? )
note that I don't want magisk, I just want the good ol' supersu, nothing more nothing less.
My opinion is the new b25 somehow messes the bootloader and now it's locked again, but this time you can't unlock it even if you downgrade and flash edl bootloader unlock via miflash.
guys, I think zte is just trolling us atm, you would not believe how much time I wasted flashing, I think my axon 7's nand is going to die soon.
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
Holding power and both volume keys at the same time for ~15 seconds (until the LED flashes) restarts EDL without actually having to get out y'kno.
Just saying
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
UPDATE ON THE SITUATION:
It didn't... *sigh*
but...it worths to mention 1 thing I noticed after booting (regardless of supersu version flashed)
That su permissions get granted, but for a limited periods/times only, and then I get the "root undetected/su binary not found" error afterwords.
which was suspicious, so I ran "su" command in terminal emulator with the supersu you provided and this is what I got
ailsa_ii:/ $ su
WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e054ffff68 arg 0xaa1403e2d2800081
Basically a bunch of warnings like the one above, like a dozen of this line ending up with this specific note:
CANNOT LINK EXECUTABLE "sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
Im losing hope, but at the same time I think I found a thread, only need a dev to help me currently
I'll post this in supersu thread and see, maybe I get a helpful reply
I will also try changing to ext4 because I'm heavily doubting that the reason for all this is my use of f2fs on data partition only.
Ghostface009 said:
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
buksua said:
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
Click to expand...
Click to collapse
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
Ghostface009 said:
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Click to expand...
Click to collapse
no fastboot on b25 but fastboot on b19
remember to flash B19-NOUGAT_FULL (Nougat 7.1.1) first than VERY IMPORTANT part is to flash B19-NOUGAT_TWRP (Nougat 7.1.1) right after.
just do step 1 and 2.
don't flash b25 yet if you want fastboot
if you want b25 and b25 root just follow step 3
buksua said:
no fastboot on b25
Click to expand...
Click to collapse
Yeah, not a big surprise
and I'll try everything later when I get enough time, but for now I look for a firmware flash-free method because I don't want to kill the ufs.
UPDATE FOR EVERYONE:
I FINALLY GOT SUPERSU WORKING (atleast this far)
sadly f2fs was the reason behind this error
Special thanks for @J0nhy
for providing the correct supersu version to flash :3
Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
The file is no longer available through this link... is there another source?
zachstarmer said:
The file is no longer available through this link... is there another source?
Click to expand...
Click to collapse
wew, It's been a long time since my last login here.
afaik it was 2.79 su.
But why you're still on b25 when you can flash newer firmware? when I flashed b32 via edl, I got rid of all these probs (except f2fs, because zte decided that their stock firmware only supports ext4 )
I got fastboot and everything, root xposed etc, if you want the edl package you can search it in drakenfx's androidfilehost account :good:
make sure to backup internal storage manually and backup apps with TB for restoring after edl-flashing b32. I also suggest updating to b35 before rooting and restore since b32 was helluva buggy update
This is exactly why I won't run ZTE's stock ROM, it seems that only Magisk works on B32 and beyond. I have grown to hate Magisk over the years, due to a number of bad experiences with it on various ROMs/devices. On stock, Magisk makes my exFAT SD appear as corrupt, I refuse to format to vfat, fat32. I tried Phh's Superuser and SuperSU, either the device won't boot or I get errors about su not being available. So it's custom AOSP-based ROMs only for me. Which are far superior to stock in most ways.
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
The toolkit guide is probably the easiest one.
Read the whole thread and try again.
Sent from my ZTE A2017U using Tapatalk
runninghamster said:
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
Click to expand...
Click to collapse
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
I will try this today, thank you for your time in typing this
runninghamster said:
I will try this today, thank you for your time in typing this
Click to expand...
Click to collapse
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
raystef66 said:
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
Click to expand...
Click to collapse
Thank you so much, will try today!
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
Followed your steps and managed to unlock the bootloader successfully. Afterwards I tried to flash TWRP using the Axon Toolkit and this error appears. Have 0 clue why. A little help please.
View attached >>>
EDIT: nevermind, tried to boot into recovery and twrp booted, not sure why the error appeared though. thanks for the help!