Database Users

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Help install OxygenOS

Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.

BooBzi said:
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
Click to expand...
Click to collapse
Push the OOS rom via usb to the phone, command: adb push namerom /scard
Next time check the drivers installation result first.

I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!

chaojimbo said:
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
Click to expand...
Click to collapse
I had problems with ADB drivers, anyway got back to life:
1) booted to TWRP
2) adb push ".zip" /sdcard/.
3) tried installing it at TWRP, no success, so get back stock recovery and flashed the file there.
So my issue is resolved. thanks!

Newb needs help rooting, unlocking Bootloader and getting a Custom ROM for ALE-L21

Hey there,
I need help, hope you have some for me . I want to use the 6.0.1. OpenKirin OmniROM on my phone and struggle even figuring out a way to get there.
I just bought a used ALE-L21 DualSIM phone with the B602 Build and EMUI 4.0.3 installed. The device is not rooted, nor has its bootloader been unlocked. The EMUI update service does not offer me any patches.
Could someone please line out to me which steps I have to take in order to root my ALE-L21 and get this ROM to work?
Disclaimer: No, I'm not just a lazy moron who does not want to read other topics on this forum - I'm a mere user with less-than-average knowledge of Android development or stuff like that. And I just can't make complete sense of the various posts I've found, since English is not my mother tongue and there seems to be a whole bunch of ways to do certain things with a phone. Well, since obviously I don't want to brick my new phone, I'm not too sure how to best puzzle together the pieces this Forum offers me. It would be insanely helpful if I could get a list that reads out something like:
1. Action - Source (for needed files, e.g.) - Result, on to step 2
2. Action - Source (for needed files, e.g.) - Result, on to step 3
3. ... and so on...
Okay, just so you see that I'm not entirely lost, I'm gonna show you the picture which is currently in my mind.
From what I understand so far, there's the following steps to get there (please rectify or rearrange steps as far as needed):
1. Update the device to Vanilla EMUI 4.1, Build B895 or B896 (I am currently downloading the B896 Build from this forum - which one is recommended? My phone is DualSIM)
2. Unlock Bootloader (What's the best way to do it? Huawei CS? Heard it's not even sure you get an answer. DCUnlocker? Wants money... Please help me clarify)
3. get TWRP 3.1.1.0 (I already have the IMG file, how do I get it to run on my phone?)
4. Root the device (I'd like to go with MAGISK, does anyone have a link for a MAGISK build confirmedly working on ALE-L21?)
5. Do some magic with TWRP (Which steps exactly?)
6. Flash the ROM Zip file via TWRP
7. Flash Gapps via TWRP
Is that about it?
As I said, please feel free to add to/adjust my list!
Thanks in advance,
Pako

If you haven't already install minimal adb tools on computer (windows) found here :
http://bit.ly/2jxX4ya
You then need to unlock bootloader using minimal adb tools and the unlock code
Unlock Code:
http://bit.ly/2z9EFhV
Unlock Bootloader Method in this thread here:
http://bit.ly/2oIASBs
After you are done unlocking the bootloader
Install twrp find that here :
http://bit.ly/2ok9BTi
There was a tool that was here somewhere to install twrp but I will link to my copy here
http://bit.ly/2ATBgRP
What you do is put the twrp image file in data folder
then change the name of the twrp file to TWRP_3.1.1-0_ALICE.img or
edit the install.bat file line data\fastboot.exe flash recovery data\TWRP_3.1.1-0_ALICE.img to the name of your twrp file
Once twrp is installed then you can pick which rom you want
The 6.0 roms arent going to be supported anymore so i suggest going for 7.0 ROM
I'm on AOSPA which is the cleanest and has good battery life
To install 7.0 rom you need B895 or B896 found here on the first post:
http://bit.ly/2jypIij
this is installed through twrp (which is accessed when Phone is off by holding volume up + power then let go once it vibrates or connect the phone to the computer and then type adb devices then adb reboot recovery in minimal adb tool)
once in twrp you need to install the B895.zip or B896.zip file then reboot your phone will boot into emui
you need to install twrp again as B895 or B896 wipes it
After installing twrp you can then install any custom rom of your choice
let the rom boot and then go back into twrp and install gapps found here: "http://bit.ly/1JOWjUqi recommend nano or even pico pick am64 7.1
I would also recommend installing Galactic forced deepsleep http://bit.ly/2ANVdbS

Hey there,
thank you very, very much for your comprehensive walkthrough! (Almost*) everything worked to perfection and I am now a happy user of OpenKirin's OmniROM 6.0.3. mod! Yeah, no 7.x... but I'd prefer to wait with that until the "issues" section of AOSPA does not contain any relevant things anymore. OmniROM seems to have no issues anymore, so I'm content with my choice. I will now follow your last advice and flash the Deep Sleep Mod to improve my device's battery life, and then I'm just happy.
* = The only issue I encountered was when having flashed TWRP, the device booted to the crappy EMUI eRecovery instead of TWRP. I solved this issue using this advice from another thread.
So, once again, thank you! All you xdaDevs, keep on developing ways to improve people's lives with their android devices!
Cheers,
Pako

I think I bricked my x722 device? Any help would be appreciated!!

Hi! I'm fairly new to modding with Android, so please bear with me
I wanted to install LineageOS 15.1 on my x722 based Le Pro 3 Elite device, and basically all went well. I however didn't enjoy it fully.. I liked the old EUI better after using Lineage for about an hour. So I looked up a flash file, and attempted to flash it using TWRP. I have recently found out this was a bad idea. Basically when I flashed it, it had installed a chinese version of EUI. (I had purchased my device from Banggood, it didn't come with the chinese stuff). So I looked up a guide on here that would take me down to ver. 001D, and put me back to 020S by using a chinese .bat file after installing the 001D version of EUI. It didn't work, so I kept looking around and installing different things. Basically, where I am now is I am not able to boot into my phone. This was my daily driver, but sadly not anymore.
Whenever I try to access recovery, it will flash the recovery text, but then restart back into its boot loop. I am only able to access the blank screen (Hold down pwr, vol+ and vol-) and the Fastboot menu. Whenever I try to unlock the OEM, it tells me I cannot, and whenever I try to flash a stock recovery or a TWRP recovery, it tells me the device needs to be unlocked, or partition flashing is not allowed.
Is my device gone? or is there a way to get it back through something like FlashOne or somehow getting it back through fastboot or ADB?
Any help would be greatly appreciated, once again sorry if I sound like an idiot haha
Thanks!

First, never flash stock EUI in Recovery, it needs to be flashed from ADB.
You could try using the ALL In One Tool to restore you phone to stock, by flashing the current version of EUI ( the one that came with the phone)
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's has a link to the stock Roms for many devices.
Install the program and setup PC first
After you install it, make sure to check for AIT updates, and ADB updates. Plus give ADB system wide privileges, I would suggest that you disable antivirus and firewall so the program can download drivers and software without issue.
Get it here:*https://toolaio.tk**
Go to theXDA page for Le pro 3 instructions: https://forum.xda-developers.com/le-...1#post71627491
Read how to use it within that thread. However, its fairly intuitive.
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader, if needed
* Remove Encryption, if needed
* Install TWRP, when needed
* Install your Rom, Gapps and Magisk etc., if or when needed
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges
At first I was going to tell you that no Qfil is available for the Elite X722, and your phone is not fixable. However, it sounds like maybe? Hoepfully you are lucky and probably not actually hard bricked? You say that you are able to boot into recovery and fastboot right?
If that is the case you should be able to recover your phone., and reflash the proper EUI.
I do not have a X722 , so you need to search XDA for others that have had this similar issue. Look for recent post, some of the older posts from early 2017 is now outdated or just incorrect, such as you finding the chinese version of EUI.
I would recommend that you go to a X722 thread and look for someone that has had a similar issue with their own X722.
Btw, there are plenty of fantastic roms that are much better than EUI but you need to be more careful about what you flash, and ensure that you know what you are doing first.
Try asking Gabronog in the AOSIP forum, I am pretty sure that he has a X722.

tsongming said:
First, never flash stock EUI in Recovery, it needs to be flashed from ADB.
You could try using the ALL In One Tool to restore you phone to stock, by flashing the current version of EUI ( the one that came with the phone)
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's has a link to the stock Roms for many devices.
Install the program and setup PC first
After you install it, make sure to check for AIT updates, and ADB updates. Plus give ADB system wide privileges, I would suggest that you disable antivirus and firewall so the program can download drivers and software without issue.
Get it here:*https://toolaio.tk**
Go to theXDA page for Le pro 3 instructions: https://forum.xda-developers.com/le-...1#post71627491
Read how to use it within that thread. However, its fairly intuitive.
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader, if needed
* Remove Encryption, if needed
* Install TWRP, when needed
* Install your Rom, Gapps and Magisk etc., if or when needed
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges
At first I was going to tell you that no Qfil is available for the Elite X722, and your phone is not fixable. However, it sounds like maybe? Hoepfully you are lucky and probably not actually hard bricked? You say that you are able to boot into recovery and fastboot right?
If that is the case you should be able to recover your phone., and reflash the proper EUI.
I do not have a X722 , so you need to search XDA for others that have had this similar issue. Look for recent post, some of the older posts from early 2017 is now outdated or just incorrect, such as you finding the chinese version of EUI.
I would recommend that you go to a X722 thread and look for someone that has had a similar issue with their own X722.
Btw, there are plenty of fantastic roms that are much better than EUI but you need to be more careful about what you flash, and ensure that you know what you are doing first.
Try asking Gabronog in the AOSIP forum, I am pretty sure that he has a X722.
Click to expand...
Click to collapse
Thankyou so much for this!
One sad thing though, OEM is locked and I don't have a way of unlocking it. Recovery does attempt to launch and open, but it doesn't want to. I see the recovery screen, the screen you see when you try to load into it, but then it just reboots the phone. OEM is locked, and Recovery does not work.
Thanks!

VoiiDFX said:
Thankyou so much for this!
One sad thing though, OEM is locked and I don't have a way of unlocking it. Recovery does attempt to launch and open, but it doesn't want to. I see the recovery screen, the screen you see when you try to load into it, but then it just reboots the phone. OEM is locked, and Recovery does not work.
Thanks!
Click to expand...
Click to collapse
Does fast boot work?
If it does you can try these files : emmc_appsboot.mbn and xbl.elf using adb. You can get those files by unzipping the X722 firmware and then placing those files in your platform-tools folder.
If you cannot get into fastboot, then I am sorry your phone is hard bricked and unfortunately Leeco never released the Qfil for the X722 to the public..
Hard Bricked Options
Replace the motherboard with the motherboard from the X720 or X727 ( Yes, it will work)
Try to return the phone to Bangood under warranty, " It just stopped working" This has been a working option for some people. Worst case scenario maybe they have a way to fix it, or will send you an exchange replacement for a fee
Good Luck

I'm sorry to tell you that you can not do anything.
The fastboot does not work for you, because you do not have permissions, it can only be fixed with qfil, and it does not exist for X722.
Greetings.

Your device is bricked without a fix. I wish you read the sticky here and in the x722 development forum before doing anything.

How do I install OS in MOTO G4 Plus(Andriod) without using fastboot and TWRP?

I've tried to upgrade the rom in MOTO G4 Plus using TWRP version of 3.2.1.0 and during installation process I wiped out the existing android 7.0.1 without backup(understood the cost of backups now). As I faced error while installing android 9.0.1 with error 255 code because of TWRP some upgrade issue couldn't complete the installation process successfully.
I tried multiple ways to upgrade TWRP which was not successful and even fastboot commands aren't working now. Whenever I try fastboot + combinational command like devices and etc it goes into an infinite loop with an error code iterator not found. After a good amount of search found about ADB and happily can connect to my device using ADB now. Then started trying with multiple options like adb side load after reading multiple forum answers and posts I did pushed a rom to scared/data/media after reading this forum NEED HELP: Accidentally deleted OS in TWRP/Cant install Rom which was successfully pushed but didn't do any thing nor I couldn't understand what to do after pushing it.
Then started search again to install stock rom in any different ways before coming here and stumbled at this question which is similar did read the question and included forum post in it to go start the process when I did download stock rom stock rom download couldn't find any flashall.sh file to start the process
Now I'm stuck and couldn't find better place to find a working solution for this situation. Can somebody help me? What can I do while my phone is in this state?

can someone please help me out from this situation

Do you still have access to TWRP on your device? If so, what ROM did you push to your device? You might like to try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on your TWRP version since it's 32 bit.
The stock ROM download would still require fastboot, so I'm not sure why your fastboot is not working. What fastboot are you using (is it minimal ADB/fastboot or the Google ADB) and have you downloaded/installed the Motorola USB drivers as well? https://support.motorola.com/us/en/drivers
(As you probably found out, error 255 when flashing custom Oreo or Pie ROMs means that your TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP. What 64 bit TWRP are you flashing that are not successful, and how are you flashing the 64 bit TWRP, via fastboot or in TWRP?)

echo92 said:
Do you still have access to TWRP on your device? If so, what ROM did you push to your device? You might like to try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on your TWRP version since it's 32 bit.
The stock ROM download would still require fastboot, so I'm not sure why your fastboot is not working. What fastboot are you using (is it minimal ADB/fastboot or the Google ADB) and have you downloaded/installed the Motorola USB drivers as well? https://support.motorola.com/us/en/drivers
(As you probably found out, error 255 when flashing custom Oreo or Pie ROMs means that your TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP. What 64 bit TWRP are you flashing that are not successful, and how are you flashing the 64 bit TWRP, via fastboot or in TWRP?)
Click to expand...
Click to collapse
HI Echo92,
Thanks a ton and you are really awesome. It worked and I'm really thankful to you again Echo.
For the later questions:
I haven't been using the 64bit TWRP for flashing this Custom Pie ROM which was my mistake. I was using 32bit and doing on TWRP directly. What version of TWRP should I use in order to install the Custom Pie ROM I've mentioned in this reply Echo? Could you please share the link or help me with the version.
Thanks a ton and ahead again Echo.

chintu008 said:
HI Echo92,
Thanks a ton and you are really awesome. It worked and I'm really thankful to you again Echo.
For the later questions:
I haven't been using the 64bit TWRP for flashing this Custom Pie ROM which was my mistake. I was using 32bit and doing on TWRP directly. What version of TWRP should I use in order to install the Custom Pie ROM I've mentioned in this reply Echo? Could you please share the link or help me with the version.
Thanks a ton and ahead again Echo.
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 or https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Both are 64 bit TWRP recoveries. You should be able to download them to your device, then install them via your existing TWRP recovery. Reboot to recovery then flash the 64 bit custom ROM and the relevant 64 bit (arm64) GApps package.

echo92 said:
Try https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 or https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Both are 64 bit TWRP recoveries. You should be able to download them to your device, then install them via your existing TWRP recovery. Reboot to recovery then flash the 64 bit custom ROM and the relevant 64 bit (arm64) GApps package.
Click to expand...
Click to collapse
I Tried to install both TWRP with fastboot but unfortunately my fastboot is not yet working Echo. It is looping infinite times when I tried any commands with fastboot.

chintu008 said:
I Tried to install both TWRP with fastboot but unfortunately my fastboot is not yet working Echo. It is looping infinite times when I tried any commands with fastboot.
Click to expand...
Click to collapse
As I mentioned, did you try to flash the recovery whilst booted into TWRP, instead of using fastboot? You should be able to install the zip then reboot to the recovery, then you should have 64 bit TWRP.
From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to.*
Click to expand...
Click to collapse
Credit to https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206