Related
I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
chuck-fu said:
I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
Click to expand...
Click to collapse
I was in the exact same predicament last night, for different reasons though. No matter what I did, I kept getting that same error. I gave up and just flash one of the Roms from this thread since it includes the kernel, radio and stuff http://forum.xda-developers.com/showthread.php?t=3262242.
Sent from my XT1575 using Tapatalk
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
I have same issue like you guys. I want to root my Moto, and my Wi-Fi won't working. So I downgraded to LL using Restore-To-Stock-Tool and try to upgrade to MM unfortunatelly it isn't work. From OTA I received error, and from recovery also upgrade didn't work? Any ideas how to solve existing problem?
bulsara said:
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
That would be great- looking forward to trying out that file.
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
JoeNeckbone said:
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
Click to expand...
Click to collapse
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
chuck-fu said:
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
Click to expand...
Click to collapse
I'm a little confused, if your trying to go back to lollipop that is the correct modem file, I haven't tried it myself, but I read there should be a tools folder with a hlnos file. If still trying mm then here is the mm modem file.
http://forum.xda-developers.com/showthread.php?p=63574299
Edit: you should verify the md5 for all the files you are using, might have a bad download.
Edit 2: just downloaded the restore zip and took a look, there is no tools folder but filename is
NON-HLOS.bin for lollipop modem.
Sent from my Moto XPE
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
I am in the same issue, but I have the XT1572. Any thoughts?
bulsara said:
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
Click to expand...
Click to collapse
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
chuck-fu said:
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
Click to expand...
Click to collapse
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
bulsara said:
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
I tried that with the same issue as the op to no avail, ended up going with one of the stock roms. Have another issue but I'll be making a new thread with that.
Sent from my XT1575 using Tapatalk
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Thanks for the advice. I'll try that here. Just to be sure, for step 1, I assume you mean to use this tool, correct: (http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905)
Or did you downgrade to moto 5.1 using a different method?
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Also- when you say: "3. reboot bootloader and then flash the file again." Are you suggesting that i should flash my stock MM Rom at that point? If so, just to be clear, i'll need to flash TWRP recovery again, move the MM ROM over, then flash it from inside TWRP, correct?
Or are you saying something different?
Edit: Well, I went ahead and loaded TWRP back on and tried restoring the stock MM Rom. Once again, i got the E: Failure to Mount error when trying to restore (interestingly, i can backup the existing ROM without issue). So, i went ahead and just booted up in hopes that i'd now be able to accept the OTA rom. I just downloaded it, and with stock recover in place, got the same Error and Dead Andy screen.
One note: When i first loaded TWRP, it asks if i want to leave things Read Only and receive OTAs or allow it to be writable. I think in the past i allowed it to be writable (which would've explain the OTA failures of the past), so this time I left it Read Only figuring that would fix my issue. No luck. It still failed.
Any additional ideas would be most welcome. I'm out of ideas here.
JoeNeckbone said:
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
Click to expand...
Click to collapse
Just checked this and system is not checked. I don't think i've ever changed it either.
Issue resolved-
I never figured out how to get around the Error during OTA install, but i did get on MM. I case this somehow helps anyone, here's what i ended up doing.
1) Used the Restore to 511 stock tool (non-rooted)
2) booted into 511 and set things up
3) reformatted my SD card for use (it had previously been set up to be used as internal storage when i had MM working a couple of weeks ago)
4) flashed TWRP 5.1.1
5) rooted using install of SU zip file (rather than TWRP's "do you want to root this device"
6) Rebooted? (maybe i did this. don't remember)
7) Loaded the stock MM rom onto my SD card
8) Went back into TWRP and made my internal partition writeable (Note: i initially tried to say yes to when TWRP asked me if i wanted to root, but this prevented the device from booting after i restored the MM Rom (in the next step), so i just said no to that. If i decide to root later, i will do so by installing SU from zip.
9) Restored the stock MM rom from the SD card
Now up and running on MM. Will not allow my SD card to be used as internal- which is what started this mess.
Currently don't seem to have wifi working. I had this issue when i downgraded to 5.1.1 and needed to flash the NON-HLOS.bin file. I am trying to find out if i need to do the same here.
So my scenario.
I'm on the unlocked B20_boot Build. Rooted. TWRP.
What files are needed to upgrade to B27?
What are the step by step?
I have read through the different threads, but it is confusing at times and rather not make a mistake. It would probably benefit multiple people.
Cheers!
I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.
bhazard451 said:
I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.
Click to expand...
Click to collapse
Change the .up to .zip and try again. This is the safest method to B27.
jkuczera said:
Change the .up to .zip and try again. This is the safest method to B27.
Click to expand...
Click to collapse
Changing it to .zip does not work.
B4oE said:
Changing it to .zip does not work.
Click to expand...
Click to collapse
From stock recovery?
jkuczera said:
From stock recovery?
Click to expand...
Click to collapse
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/downlo...TE A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Maybe verify checksum? That's the method I used (from SD card).
Interesting. ADB Sideload should work if the Apply Update from SD Card method doesn't.
B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.
DrakenFX said:
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.
Click to expand...
Click to collapse
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.
B4oE said:
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.
Click to expand...
Click to collapse
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.
bhazard451 said:
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.
Click to expand...
Click to collapse
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?
swehes said:
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?
Click to expand...
Click to collapse
The best way would be a System Image from ZTE, but we are SOL on that for now.
Hello,
Wondering if anyone can offer some advice. Just got an Axon 7. Was on B27...HiFi settings had a weird buzzing sound when set to "super". Thought maybe I should see if there was an update, but phone just said "Please check your network connection". My wifi was working fine and tried factory resetting multiple times. Finally I downloaded the update.zip off the ZTE USA site that was for B20....thought maybe I could downgrade to B20 and then update to B29, but no luck. Now I am stuck on B20 and still getting the "Please check your network connection". Can do anything data/wifi needed except update. Any thoughts? Phone is non-rooted....haven't even had it long enough to think about it or have time yet.
crash447 said:
Hello,
Wondering if anyone can offer some advice. Just got an Axon 7. Was on B27...HiFi settings had a weird buzzing sound when set to "super". Thought maybe I should see if there was an update, but phone just said "Please check your network connection". My wifi was working fine and tried factory resetting multiple times. Finally I downloaded the update.zip off the ZTE USA site that was for B20....thought maybe I could downgrade to B20 and then update to B29, but no luck. Now I am stuck on B20 and still getting the "Please check your network connection". Can do anything data/wifi needed except update. Any thoughts? Phone is non-rooted....haven't even had it long enough to think about it or have time yet.
Click to expand...
Click to collapse
You can also sideload the OTAs. Put these on your microSD card.
B27 OTA: https://dl1.ztems.com/zxmdmp/downlo...ZTE A2017U/81526/update_P996A01_B20_to_B27.up
B29 OTA: https://dl1.ztems.com/zxmdmp/downlo...ZTE A2017U/82082/update_P996A01_B27_to_B29.up
After you put them on your microSD card, they might show up in the System Update menu, I'm not sure.
If they don't, you can flash them via stock recovery. Rename them to "update1.zip" and "update2.zip" or whatever, boot into stock recovery, flash the first one, reboot into the device to make sure it flashed fine, reboot into stock recovery, flash the second one, reboot and you should be on B29.
xtermmin said:
You can also sideload the OTAs. Put these on your microSD card.
B27 OTA: https://dl1.ztems.com/zxmdmp/downlo...ZTE A2017U/81526/update_P996A01_B20_to_B27.up
B29 OTA: https://dl1.ztems.com/zxmdmp/downlo...ZTE A2017U/82082/update_P996A01_B27_to_B29.up
After you put them on your microSD card, they might show up in the System Update menu, I'm not sure.
If they don't, you can flash them via stock recovery. Rename them to "update1.zip" and "update2.zip" or whatever, boot into stock recovery, flash the first one, reboot into the device to make sure it flashed fine, reboot into stock recovery, flash the second one, reboot and you should be on B29.
Click to expand...
Click to collapse
Hmm...thank you for these! This is the kind of solution I have been hoping for, but they didn't show up in the updater and when I tried stock recovery it said "can't update from sd card".
crash447 said:
Hmm...thank you for these! This is the kind of solution I have been hoping for, but they didn't show up in the updater and when I tried stock recovery it said "can't update from sd card".
Click to expand...
Click to collapse
1- IMPORTANT - enable OEM Unlock under Developer Options ( THIS IS NEEDED IF YOU WANT TO USE THOSE FILE WITH STOCK RECOVERY )
2- change the extension from .up to .zip
3- Move Files to SDCard
4- Boot to Stock Recovery and use UPDATE VIA SDCARD
DrakenFX said:
1- IMPORTANT - enable OEM Unlock under Developer Options ( THIS IS NEEDED IF YOU WANT TO USE THOSE FILE WITH STOCK RECOVERY )
2- change the extension from .up to .zip
3- Move Files to SDCard
4- Boot to Stock Recovery and use UPDATE VIA SDCARD
Click to expand...
Click to collapse
That worked!!! At least from 20 to 27...now to go from 27 to 29!!!! Thank you so much!
DrakenFX said:
1- IMPORTANT - enable OEM Unlock under Developer Options ( THIS IS NEEDED IF YOU WANT TO USE THOSE FILE WITH STOCK RECOVERY )
2- change the extension from .up to .zip
3- Move Files to SDCard
4- Boot to Stock Recovery and use UPDATE VIA SDCARD
Click to expand...
Click to collapse
how do i boot into stock recovery? i tried volume down and power button but there no stock recovery?
Sent from my ZTE A2017G using XDA-Developers mobile app
ayim said:
how do i boot into stock recovery? i tried volume down and power button but there no stock recovery?
Sent from my ZTE A2017G using XDA-Developers mobile app
Click to expand...
Click to collapse
Volume Up + Power Button
Keep in mind that the links and such in this topic are for the US model, the A2017U. You have the global model, the A2017G.
Can any of you upload stock B20 for the a2017u? The link posted by tenfar isn't working and the file hosted on Mega's site is going to take too long to download due to not having a paid subscription?
ronj1986 said:
Can any of you upload stock B20 for the a2017u? The link posted by tenfar isn't working and the file hosted on Mega's site is going to take too long to download due to not having a paid subscription?
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715 download the unlock kit they have here. One of the files they have in it is the stock B20
Anyone have the stock B20 Bootloader? I am unable to lock my bootloader using the 'fastboot oem lock' command. I was able to downgrade to B20 using the kit posted at the link above.
ronj1986 said:
Anyone have the stock B20 Bootloader? I am unable to lock my bootloader using the 'fastboot oem lock' command. I was able to downgrade to B20 using the kit posted at the link above.
Click to expand...
Click to collapse
Grab the B18_to_B20 OTA
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Should be, but it's not safe since you do not know the current root method.
Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse
Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha
tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse
tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse
Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..
tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal
Hi all,
I have A2007U running B35 all stock and locked bootloader.
I'm having problems with MiFlash so I'm trying to find another solution.
Is there a way to downgrade using Sdcard and stock recovery?
you should able to downgrade to B32 with edl tool following this post
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
vic_singh said:
Hi all,
I have A2007U running B35 all stock and locked bootloader.
I'm having problems with MiFlash so I'm trying to find another solution.
Is there a way to downgrade using Sdcard and stock recovery?
Click to expand...
Click to collapse
You can downgrade without a PC. you need to find the official B32 update package, unzip it (there should be an update.zip inside the zip that you downloaded), and put that update.zip on the SD card. Then go to Settings, Updates, and install the B32. It will downgrade the system no problem.
Any reason to roll back from the 35?
Skv012a said:
Any reason to roll back from the 35?
Click to expand...
Click to collapse
I'm having tons of issues with unlocking bootloader. I used the tool but I was only able to unlock fastboot. I can't even install twrp.
Choose an username... said:
You can downgrade without a PC. you need to find the official B32 update package, unzip it (there should be an update.zip inside the zip that you downloaded), and put that update.zip on the SD card. Then go to Settings, Updates, and install the B32. It will downgrade the system no problem.
Click to expand...
Click to collapse
any clue where i can find the image from?
vic_singh said:
any clue where i can find the image from?
Click to expand...
Click to collapse
Well nope. It was on the US servers but they got shut down. Maybe @raystef66 knows?
Choose an username... said:
Well nope. It was on the US servers but they got shut down. Maybe @raystef66 knows?
Click to expand...
Click to collapse
looks like its still there
https://www.zteusa.com/axon-7
At fastboot, you need run a command "fastboot oem unlock", then you should be able to access twrp.
Your twrp is probably already flashed, just can not be access as you have not run the command "fastboot oem unlock".
vic_singh said:
I'm having tons of issues with unlocking bootloader. I used the tool but I was only able to unlock fastboot. I can't even install twrp.
Click to expand...
Click to collapse