TWRP-Backup on 7.1.1 B25 bl-locked A2017U possible? - ZTE Axon 7 Questions & Answers

Hi there,
I want to root my A2017U with latest Andrpid 7.1.1 B25 update and therefore need to unlock my bootloader first (except if there is a way to root without unlocking)...
But my problem is that I'm veeeery short on time and can't afford to reinstall and reconfigure all my apps...
So is there a way to "inject" twrp and make a full backup with locked bootloader (maybe with tenfars or tennears tool), then start the unlock process and simply restore the backup afterwards (I wan't to stay on stock rom)?
Because as far as I understood I can't prevent a whole device format to unlock the bootloader... Please correct me if I'm wrong...
Thx folks!
@mods : sorry I posted in wrong section, please move to question & answers

Short answer: No.
Sent from my Axon 7!

I really think you should find the time to do things properly. It might take an hour to set everything up perfectly, but it will save you the hours of frustration of doing something wrong by trying to keep your bl locked and keep your apps. Google will reinstall most of them automatically, so that's convenient..

Related

Rooting?

I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
What version are you running? B20/B27/B29
If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.
S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.
No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.
Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA
totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with
I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system
rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.
rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis

Easiest root possible

Hi everyone,
I just got my Huawei Nova and i wonder if there is any easy rooting-guide or app like KingRoot.
I used this app for Honor 7 and others and it's a great one, but i don't know if it's working for the Nova.
If possible, i don't want to change recovery/rom, only small root that allows me to really control my phone.
Thanks yall
At the moment, there are no automated tool or any application on XDA unfortunately...
The easiest way is unfortunately the ADB/Fastboot way.
It's not that hard, but you have to be a bit careful going through each step:
- Install ADB/Fastboot tools, and the drivers
- Unlock bootloader (you'll need an unlock code)
- Flash TWRP recovery
- Flash Root.
You'll find pretty much all the info needed in the Nova forums, but it is a bit of research. Nothing that is worth having is easy to get!
Yes, all info is in the TWRP post under development forum. Weird issue with data partition in TWRP.
Thank you for your replies. I've seen the TWRP post with all the instructions, i just don't want to take any risks with my brand new phone for now.
That's why i used King Root app before, one tap and it does everything, without flashing anything.
Anyway, i'll wait for some time then.
Again, thank you very much.
Is re-locking the boot loader after rooting possible without losing root again?
Found the tool?

A2017G (6.0.1) B08 - Root without Unlocking possible?

Hi there,
I found there is a thread describing how to root the US/Chinese model without unlocking the bootloader -
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
However it mentions that this'll brick the European model because of the included TWRP version and unfortunately I'm on a ZTE A2017GV1.0.0B08 (Android 6.0.1, Kernel 3.18.20).
Is there any news if this can be done now with the international variant -
I'm not interested in a custom ROM or updating Android, I'm happy at the moment with the 6.0.1 version I have, but really would like root for xposed framework, Titanium, Tasker ...
Is there a different TWRP version that can be used or is it not working due to the ZTE's signature key used?
Alternatively is there a way for the A2017G to re-lock the bootloader that's 100% working/safe, if you don't apply a custom ROM?
Thanks a lot for your help!
The answer you will find here
https://forum.xda-developers.com/showthread.php?t=3441204
This is the way I did it with my first A7
sent from zte axon 7 with tapatalk
Hi.
It didn't really answer the question : Is unlocking necessary to root, or can we root without unlocking ?
Every tutorials founds all follows the same paths : Unlock first, then root. But why ? is there a reason for that, or is it just a "since i'm rooting, let's unlock it while i'm at it" thing ?
(edit : Sorry 4 my english ... i hope i've been clear enough)
marcus.linkenbach said:
The answer you will find here
https://forum.xda-developers.com/showthread.php?t=3441204
This is the way I did it with my first A7
sent from zte axon 7 with tapatalk
Click to expand...
Click to collapse
Hallo Marcus
Danke fuer die Antwort -
Maybe I didn't fully comprehend the thread - I was under the impression that it bricked some A2017G, while not others and didn't want to take the risk.
Reading through the instructions - which of these steps did you take (and in what order)?
I read it that you do not need to flash TWRP? So can I just root the phone without bricking it and all is good as long as I stay with my 6.0.1 B08 version?
I understand the instructions as
- boot into edl
- install Qualcomm driver
- run axon7root to already root the device (backup seems to be done in the next step?! according to instructions).
However there is no axon7root version for the A2017G (B08) as it was removed due to TWRP?!
All I can find is the axon7backup tool (would you actually do this before you run the axon7root the first time?)
If you run the axon7root, did you do 'axon7root.exe -p 4 -b'
so that it only flashes the boot.img (not TWRP recovery) and therefore this is safe?
Sorry for the long essay, help is really appreciated!
Hey, sorry for the delay.
I am quite busy. I really don't know the procedere anymore. It is a long time ago. But if you would give me some time, I will have a look on it and will let you know. But why won't you unlock your bootloader? Without unlocking not everything runs as it should with unlocked BL.
OK. I will let you know.
Marcus
Sn8K said:
Hi.
It didn't really answer the question : Is unlocking necessary to root, or can we root without unlocking ?
Every tutorials founds all follows the same paths : Unlock first, then root. But why ? is there a reason for that, or is it just a "since i'm rooting, let's unlock it while i'm at it" thing ?
(edit : Sorry 4 my english ... i hope i've been clear enough)
Click to expand...
Click to collapse
Theoretically, yes, you can root w/o unlocking the bootloader. This is how things are done typically with certain manufacturers (LG, Samsung) that rarely offer BL unlocking. To be able to flash TWRP on a locked BL is even more difficult, as it would require a BL-level exploit. The reason that's not an option here is the ability to unlock, which precludes such development.
Hi Marcus,
Thanks a lot, that would be really great.
Regarding Bootloader unlock - I didn't buy the phone in the EU, hence my warranty would be void if I unlock it. And my warranty even comes with screen replacement (not that I ever cracked a screen, but there's always a first).
I have to admit that I'm tempted by Lineage OS, but for now (as I just bought the phone) - if there's a reasonably safe way to root without unlock, I'd prefer to just root and then maybe in a year's time or so switch to Lineage OS...
For now I managed to have my phone recognized as QUSB_BULK and I can boot into edl.
I was trying to use the axon7toolkit (1.1.1), but for whatever reason I cannot use it in commandline mode (maybe as there seem to be different versions, or maybe cause I am on Win7 32bit, no idea).
Any help would be really great!
Hi jeboo, Hi Sn8k,
Hope above explained my motivation, regarding root without unlocking - there's a thread about this
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
HOWEVER there are two problems:
1) The bootloader can stay locked as it's using a signed version of TWRP, which can brick your device (A2017G)
2) The linked axon7root.exe is not for my device (A2017G B08).
Having said that, some users have been successful with rooting this version, so there seems to be a way, if you get the steps right.
Whoooo? said:
Hi Marcus,
Thanks a lot, that would be really great.
Regarding Bootloader unlock - I didn't buy the phone in the EU, hence my warranty would be void if I unlock it. And my warranty even comes with screen replacement (not that I ever cracked a screen, but there's always a first).
I have to admit that I'm tempted by Lineage OS, but for now (as I just bought the phone) - if there's a reasonably safe way to root without unlock, I'd prefer to just root and then maybe in a year's time or so switch to Lineage OS...
For now I managed to have my phone recognized as QUSB_BULK and I can boot into edl.
I was trying to use the axon7toolkit (1.1.1), but for whatever reason I cannot use it in commandline mode (maybe as there seem to be different versions, or maybe cause I am on Win7 32bit, no idea).
Any help would be really great!
Hi jeboo, Hi Sn8k,
Hope above explained my motivation, regarding root without unlocking - there's a thread about this
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
HOWEVER there are two problems:
1) The bootloader can stay locked as it's using a signed version of TWRP, which can brick your device (A2017G)
2) The linked axon7root.exe is not for my device (A2017G B08).
Having said that, some users have been successful with rooting this version, so there seems to be a way, if you get the steps right.
Click to expand...
Click to collapse
Did you figured out a method to root the A2017G without unlocking?
I just got mine and need root for transferring all the apps from my old Nubia Z7....
Thx.
catadoxy said:
Did you figured out a method to root the A2017G without unlocking?
I just got mine and need root for transferring all the apps from my old Nubia Z7....
Thx.
Click to expand...
Click to collapse
You can't. Don't even try it if you don't want to face DFU...
Just use the same app that the phone comes with, I think it's WeShare or something like that. It should let you transfer all of your crap via a LAN wifi transmission (If you use a 5GHz hotspot it'll be fast as heck).
Or just unlock the phone. But don't relock it if you do, because you can make a huge mess

Help I wanto to Re-Lock the bootloader

Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
sorry for my english..
Thanks
ross92 said:
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
sorry for my english..
Thanks
Click to expand...
Click to collapse
Check this thread, and follow local update method, then you need only of a command to lock the bootloader:
https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795
I just locked the bootloader for my OnePlus 6t. Follow the steps given below.
1. Backup all the important data. I am not responsible for any data loss!!!
2. Remove security lock screen (pin/pattern) or any thing
3. Download the stock rom from https://oxygenos.oneplus.net/OnePlus6TOxygen_34_OTA_020_all_1904032212_38e22c8b9abd42e3.zip
and transfer it to your phone.
4. Boot into twrp recovery.
5. flash the downloaded zip
6. Once done, reboot the system.
7. Now, boot back into the fastboot. (you can enable advance restart from developer mode for easy boot into fastboot)
8. Run fastboot oem lock
9. You will be presented with two options on phone screen. Select the one that says lock the bootloader.
10. It will wipe everything.
11. Once you in the system, enable developer mode and make sure that oem unlock is turned off. If not, turn it off and restart your phone.
And, you are done.
Let me know if it helps or if you have any question/concern.
MDM Tool in my opinion the easiest and quickest way to go back to 1000% stock. It will re-flash every partition on the phone so it's like brand new again. Using the MSM Tool guarantees that everything is back to stock and should restore the Widevine version back to L1 or whatever it was originally.
A question please
Once you lock again your phone, does it loose the root????
I mean, I have a Xperia 10 with the bootloader unlocked , it is root as well. Now root permissions for special aps work fine, but Google Pay is unusable, it does not work anymore. I hid root with xposed framework and rootCloak, but Google Pay still does not work now because the bootloader is unlocked...
As you should know, it is possible to lock the phone again... and many of those phones that relock their bootloaders keep the root permissions...
However , in my case, with Xperia devices (bq and xiaomi happen de same) is you lock the bootloader again, the phone resets, everything dissapear and root is eliminated. What is a really disaster.
As you have heard, the majority of phones, if you lock them again the root continues working, at least the apps that you gave them root permissions they continue working as they used to. But in my case this is different....ç
So please,
Is there any possibility to Lock my bootloader again without loosing the Root in my Xperia?????
Thousand of thanks!!!!
Bardok84 said:
A question please
Once you lock again your phone, does it loose the root????
I mean, I have a Xperia 10 with the bootloader unlocked , it is root as well. Now root permissions for special aps work fine, but Google Pay is unusable, it does not work anymore. I hid root with xposed framework and rootCloak, but Google Pay still does not work now because the bootloader is unlocked...
As you should know, it is possible to lock the phone again... and many of those phones that relock their bootloaders keep the root permissions...
However , in my case, with Xperia devices (bq and xiaomi happen de same) is you lock the bootloader again, the phone resets, everything dissapear and root is eliminated. What is a really disaster.
As you have heard, the majority of phones, if you lock them again the root continues working, at least the apps that you gave them root permissions they continue working as they used to. But in my case this is different....ç
So please,
Is there any possibility to Lock my bootloader again without loosing the Root in my Xperia?????
Thousand of thanks!!!!
Click to expand...
Click to collapse
Go ask in Xperia threads
Striatum_bdr said:
Go ask in Xperia threads
Click to expand...
Click to collapse
Yes I did:
https://forum.xda-developers.com/xperia-10/development/help-how-to-lock-bootloader-loosing-t3965829/post80203451#post80203451
Also I asked for help here:
https://forum.xda-developers.com/android/help/how-to-lock-google-pay-xperia-rooted-t3965637
https://forum.xda-developers.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993/page66
https://forum.xda-developers.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993/page66
This is the only Thread where I could find some information about locking a bootloader again. Yes , this is dedicated to xiaomi 6t, but locking bootloaders is something common.
The only thing I want is to lock my Bootloader again without loosing Root permisions. Xperia devices seem to RESET everything when you lock the booloader automatically...., but perhaps there is another way.... a possibility to lock the bootloader without the phone is reset (loosing root permissions) ....
I asked for some help here. I regret any inconvenience that could may be caused on this thread with my message.
Regards
Nobody have your phone here how could we help you? Each phone has its specific behavior
If you relock a OnePlus phone you reset everything, like when you unlock it and it's logical. A locked bootloader is meant to ensure safety of data, safety that can't be provided with root access. Locked BL and root are antinomic.
Striatum_bdr said:
Nobody have your phone here how could we help you? Each phone has its specific behavior
If you relock a OnePlus phone you reset everything, like when you unlock it and it's logical. A locked bootloader is meant to ensure safety of data, safety that can't be provided with root access. Locked BL and root are antinomic.
Click to expand...
Click to collapse
Thank you for your message and understanding. So in Oneplus devices happen the same. So once you unlock the bootloader you loose Google Pay forever because it does not work wit BL unlocked...
Some users suggested me to lock again the bootloader,
Imagine:
- I become Root. Then I modify some apps
- I give to some apps root permissions.
- I lock the bootloader again.
- I won't be able to modify my phone anymore, but all those apps that were given root permissions, Will they be kept in the phone although it has BL locked again.
would it be like this?
or all changes you did while being root would dissapear with everything?????
If So... there is no exit what I see..., We have to choose between being Root users.... or being stock with Google Pay. It is a Pity.
I was not sure if all Phones reset and erase everything when you lock the bootloader .... but as I can see here, this is the reality. Root users loose Google PAY definitely.
Is there any option to solve this??
thanks again for your attention.
regards
Bardok84 said:
Thank you for your message and understanding. So in Oneplus devices happen the same. So once you unlock the bootloader you loose Google Pay forever because it does not work wit BL unlocked...
Some users suggested me to lock again the bootloader, but if I do that, as you have said, the Root and everything will be erased because the phone resets everything. So... there is no exit what I see..., We have to choose between being Root users.... or being stock with Google Pay. It is a Pity.
I was not sure if all Phones reset and erase everything when you lock the bootloader .... but as I can see here, this is the reality. Root users loose Google PAY definitely.
Is there any option to solve this??
thanks again for your attention.
regards
Click to expand...
Click to collapse
I'm unlocked and rooted c and Google pay works perfectly with Magisk
Striatum_bdr said:
I'm unlocked and rooted c and Google pay works perfectly with Magisk
Click to expand...
Click to collapse
Does google pay work??? What did you do in magisk exactly to achieve that???
I rooted my xperia using Magisk..., is there any tutorial or info that you suggest to me to follow ? or what should I do in magisk options???
I have 10 days with my phone stopped, trying and trying to make Google Pay works....Maybe this is happening to me because my Xperia uses Android 9.0.... or Magisk should make google pay work even being in android 9.0?
First Google pay recognized Root, and the app stopped working. I hid it using xposed and RootCloak
Then, Google pay recognized Bootloader. But now... I dont know what to do to hid bootloader unlocked for Google..., Google pay recognises it is unlocked... a disaster and a nightmare for me, I dont know what to do...
Thousand of thanks, I really thankfull for your help.
Regards

Mi A1 Downgrade from Pie to Oreo questions

EDIT 2: ISSUE SOLVED. Go to the bottom of this comment for how to get it done right. Credits to @rizkyxculture and @orma1
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
EDIT 2: Sorry for necroing this thread, but just to clear things up a bit, from my own experience, and include and clarify what @orma1 said below in this thread so you don't have to scroll down. Before all this, make sure you have SYSTEM WIDE ADB AND FASTBOOT INSTALLED for simplicity's sake.
All credits go to @orma1 and @rizkyxculture for your amazing efforts into this <3. None of it is mine, so thank them in their respective comments/threads if you wish to.
1. REMOVE ALL PASSWORDS AND FINGERPRINTS BEFORE PROCEEDING WHILE IN PIE, and do CLEAN DATA WIPE (do not choose the relock bootloader in Mi Flash Tool).
2. Do everything in that guide sent, and at the end, where rizky mentions flashing November update after the TWRP restore, don't do it. Instead, re-flash the March update. Thanks @orma1 for your comment. If your phone just straight up boots like mine did, without bootlooping, just power it off and go to fastboot again. Link to guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624.
3. Once your phone boots normally, go to developer options, and uncheck the automatic system updates to prevent it from going to pie automatically later on. in the future. Install GCam at this stage if you wish (follow manual installation guide on XDA). Link: https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
4. After you've installed GCam (which is why you're probably doing all this in the first place, or not, regardless), chances are you still want to keep your warranty (and for security reasons) and therefore you should relock your bootloader, else the servicemen are just going to see that BIG warning at your phone's boot, and are likely revoke any warranty straight up. To do this, simply go back to fastboot and type the command below in Command Prompt and WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON (or copy paste the line below WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON):
fastboot oem lock
Once it says okay, type the following command:
fastboot reboot
Done. Now reboot, go to system update, and download and install the November update. Enjoy your still in warranty Mi A1 with Oreo and/or GCam (just make sure you uninstall the apk when giving it to the service center should you ever need to service it). Also, the power down button press prevents the auto data wipe function from activating. Have fun.
Also I have verified this works even on the April 2019 update. Just don't update any further, else I can't be sure.
Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Guess I'll just stick to pie and bite the sand and live with it till someone gets a solid, working method...
As a second thought, if I make a backup of everything (system, boot, etc. etc.) in TWRP and then carry out the flashing process, will reflashing those backups restore my device in case of a brick?
Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
Just flashing oreo from pie should cause IMEI loss.
I used the method from here: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
although I had to do his method a little differently.
also make sure if you can to backup your data as you can lose it in the process.
first of all, after oreo march update flash, my phone did boot but with no IMEI.
second of all, flashing November update after restoring IMEI caused bootloop, instead you need to flash march update again. afterwards your phone should boot with the correct IMEI (you can double check with the one on your phone's box) . worked for me with two Mi A1s.
after all of this I was able to update to 8.1 November update via system update in the settings.
and lastly I made sure to disable automatic system update from developer settings.
Good luck!
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Meme :D said:
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Click to expand...
Click to collapse
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Thanks, will see about all this.
orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Nafis-ul-Islam said:
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Click to expand...
Click to collapse
I used the backup from this thread
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
It's a backup of someone else's efs and boot patiotions. At first I thought too that restoring someone else's backup should result in me getting his IMEI.
But after trying to restore through this backup My IMEI changed from 0 to the one on my phone's original box meaning I got my own IMEI. the method there worked perfectly for me and now I am rocking 8.1 Oreo November update with Magisk and TWRP. the only thing is that following step 10 in the tutorial there resulted in a bootloop for me. Instead I followed the suggestion of one of the comments saying that instead of flashing November update after restoring IMEI you need to flash the same March update you flashed before. this time my phone booted with IMEI and I updated to 8.1 November through OTA.
Did you downgraded succesfully?
Meme :D said:
Did you downgraded succesfully?
Click to expand...
Click to collapse
I was able to downgrade successfully following this guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
In step 10 you need to flash oreo march update again and not November update as mentioned as flashing November update caused me bootloop.
afterwards you can update to November update via System update in the settings.
besides this I followed the tutorial exactly and was able to downgrade two Mi A1s.
I have successfully downgraded my Mi A1 with this thread
"Tutorial Downgrade 9.0 to 8.1 No EDL, No IMEI Problem & No Signal Problem"
Also im a 14 Yr old nearly 15 on April 20.
I was afraid too, now I'm on Nougat )
Just follow this tutorial : https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Before doing anything, boot TWRP and create a full backup of your system, after that transfer it to your PC. Probably you don't need it but better safe than sorry.
After you will flash March firmware, your phone will boot but you will not have signal, it's okay. Thing is, you don't lose the IMEI, it's still there, but somehow you lose the signal. Boot TWRP again, create a backup of your boot and EFS, you will see TWRP folder in your phone, go there and you will see a backup. Remove your backup files and replace them with the one from the guide, then you can restore them without issues (you will see a modem error, ignore it). Restart and let it boot a bit, then go to bootloader again, flash March firmware again (don't flash the November one! ignore that from the guide) and the signal will be back. If you do this, I doubt you will lose your IMEI somehow. I never lost mine, it's the same from the box.
Good luck! Make sure you go in developer settings after and disable automatic updates or you will be back to Pie. I rooted my phone so it can't update.
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Nafis-ul-Islam said:
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Click to expand...
Click to collapse
I'm happy to help
but all the credit goes to rizkyxculture for finding this method and ibooth2004 for correcting us to flash March update again instead of the November one.
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Marcos OC said:
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Click to expand...
Click to collapse
I agree the system's performance on pie is horrible and also the mic volume is low which is very annoying.

Categories

Resources