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.

Problem with TWRP, boot, stock ROM and custom ROM

So, to begin with, yesterday Mi A1 got the Android 9 update. As I always do, I went to uptade it with Magisk (it worked with 8.0 to 8.1 and with every security patch, so I, as a newbie, thought, "why the h3ll not?"). Obviously, it didn't work and I got into a boot loop. So, here are the [lot] of things I have tried to do.
-Downloaded MiFlash and the latest OS version from Xiaomi site (8.1 witch november patch). Tried flashing a lot of times, I always get the boot loop after installing it. Wiped all data with TWRP and still didn't work. Always the same problem. Tried with with march security patch and it actually boots. But if I try to uptade via Settings or flash the newest room, I get stuck again.
-Downloaded latest AOSP ROM for the device, flashed it, wiped cache and data, instaled TWRP (3.2.3-0), but the system never initiates. It freezes in the boot animation and nothing happens.
-I've tried the same thing with Lineage 15.1 as well. Checked with MD5 in both roms. Doesn't work at all. Followed every tutorial I could, step by step, don't know what I'm doing wrong.
Can any one please help me? I don't know what to do anymore. Don't wanna get stuck in 8.0 either.
Also, if someone could .zip the Pie update, I would apreciate that. Could try that

Here's the latest flashable pie for you:
https://drive.google.com/file/d/1q9O_F-TB4l3yWthYjw4jkL2prWfh7ClQ/view
Fastboot boot into twrp and clean flash the above latest rom and everything will be fine

thedemon786 said:
Here's the latest flashable pie for you:
https://drive.google.com/file/d/1q9O_F-TB4l3yWthYjw4jkL2prWfh7ClQ/view
Fastboot boot into twrp and clean flash the above latest rom and everything will be fine
Click to expand...
Click to collapse
It worked and it didn't at the same time. The boot animation doesn't freeze anymore, but it's stuck in an infinite loading screen
EDIT: Nevermind, it worked in a second flash. Thank you again

Daniel.meurer said:
It worked and it didn't at the same time. The boot animation doesn't freeze anymore, but it's stuck in an infinite loading screen
EDIT: Nevermind, it worked in a second flash. Thank you again
Click to expand...
Click to collapse
Just hit thanks if it helped. Merry Christmas

Unable to install custom roms

I have a Tab E 8 (SM-T377P) and I cannot get any version of TWRP new than 2.8.7.0 to flash, Magisk will not flash, and no custom roms will install.
I've tried both lineage 15.1 and 16, both the standard and GO versions.
It's on stock firmware, 5.1
I rooted with cfautoroot with Odin 3.10.7.
Hopefully someone has an idea on what I need to do.
:edit:
I was able to get magisk installed by rerooting with cfautoroot and then doing a full unroot and restoring bootimage with supersu. Still can't install any roms though

So I was able to update to Nougat using the rom posted in this thread. It was the ONLY place I was able to find the stock firmware. I was hoping that installing 7.1.1 would put me on a new bootloader/kernel that might allow me to install an Oreo rom.
Still, the only TWRP that I can get to boot is the one posted in this thread, which is 2.8.7. The dev posted links to 3.0.2-1 that do not work, but I've tried multiple different versions of TWRP, and they all boot loop and I have to reinstall 2.8.7 via Odin.
All roms say that they are intended for SM-T377P and cancel, although my device is exactly that.

So, after doing a total wipe and flash back to stock 7.1.1 using Odin, I was able to boot back into Download mode and install the latest version of the TWRP posted in this thread - https://forum.xda-developers.com/ga...official-lineageos-16-0-galaxy-tab-e-t3847488
Still won't let me install a custom rom though...

Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.

Krunk_Kracker said:
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Click to expand...
Click to collapse
Thank you for documenting your progress.
I am in a similar situation.
I am the original owner of my t377p.
I'm going to try your steps to see if it will work for me.
UPDATE:
Flashing back to Stock and starting the process all over again, as you described above--fixed the problem. I am now running LineageOS16.
Thank you!

I'm glad it worked for you!
That's exactly why I updated the thread, I knew I wouldn't be the last one have this odd issue.

Do you have a copy of twrp the servers are down and I've been trying for week to download it

Samsung Note 3 N9005 + TWRP 3.x = bootloop

Hello!
I try to install the latest version of lineage on my note 3 and followed the tutorial on the lineage website.
However, I got some issues getting the latest version of TWRP on the phone. Beside the method via heimdall I've also tried Odin and update via old TWRP install and sd card. I also installed the stock rom again and retried flashing but nothing worked.
Basically I can flash old TWRP and get into the TWRP recovery mode - twrp-2.8.7.0-hlte-4.4.img works perfectly fine. But when I try twrp-3.4.0-0-hlte or trwp-3x though the flash is confirmed I cannot get into recoverymode and will end up in a bootloop.
I've tried twrp-3.2.2-0-hlte, twrp-3.1.1-0-hlte, twrp-3.4.0-0-hlte all with same result (bootloop). Only version that works is twrp-2.8.7.0-hlte-4.4
Any idea where this issue may come from?
Any other recovery tool I could use to get lineage on my note3?

update:
hmm why would the recovery system care for the os?
fwiw I updated the firmware to the latest official version (android 5.0) and then retried.
same result: with TWRP 2.8.7.0 I can flash and get into recovery mode. TWRP 3.x I can flash and they will bootloop
TWRP 2.8.7.0 I get the message
"Recovery booting...
recovery is not seandroid enforcing
Set warranty bit: recovery"
=> TWRP recovery mode
TWRP 3.x
"Recovery booting...
Set warranty bit: recovery"
=> bootloop

What model ??
Known issue for some re TWRP 3 failing , well posted on here .
Read answers to your other posts .

JJEgan said:
What model ??
Known issue for some re TWRP 3 failing , well posted on here .
Read answers to your other posts .
Click to expand...
Click to collapse
sm n9005
I found a possible reason in the TWRP thread: LCD and Digitizer may have been replaced and hardware change could case this. I am not sure though
[/COLOR]
ashyx said:
If you've got one of those finicky devices which seems to have slightly different hardware then you may find this build works:
https://androidfilehost.com/?fid=6006931924117938350
However be aware it's also likely you will not be able to boot any recent android version on your device if this is the case.
Click to expand...
Click to collapse
this worked for me finally! And it looks like linageOS can be installed too... I will update
-------
lineageOS and google apps could be installed without issues. I was stuck on the bootsequence quite a bit but now I am in the OS

smuffiy said:
sm n9005
I found a possible reason in the TWRP thread: LCD and Digitizer may have been replaced and hardware change could case this. I am not sure though
[/COLOR]
this worked for me finally! And it looks like linageOS can be installed too... I will update
-------
lineageOS and google apps could be installed without issues. I was stuck on the bootsequence quite a bit but now I am in the OS
Click to expand...
Click to collapse
Hi smuffy,
May I know what lineage version are u flashing?
I'm facing same problem also, can you please guide me how to solve this issue?
Thanks

I do not remember exactly but I think the latest by that time.
However I was unable to make lineage detect my SIM card after that. I tried some other workarounds but it never worked and I finally gave up.

smuffiy said:
I do not remember exactly but I think the latest by that time.
However I was unable to make lineage detect my SIM card after that. I tried some other workarounds but it never worked and I finally gave up.
Click to expand...
Click to collapse
My phone cannot flash lineageOS 17.1 version and above.
My phone is new, just rooted, tried custom rom android 9 worked!
LineageOS 16 - ok
LineageOS 18.1 - x (After flash, cannot see any file inside the phone memory)
Havoc 2.9 - ok
Havoc 3.7 - x (After flash, cannot see any file inside the phone memory)
Are you facing same problem also?
*Remarks*
My phone keep in bootloop, cannot initialize...
Thanks.

Which TWRP are you using? I had the custom "twrp 3311 ashyx".
I just checked, 17.1+ also does not work for me. Just as you stuck in bootloop.

With this (ashyx) https://www.alebalweb.com/note3/note3-sm-n9005--twrp--work-on-my-note3.zip los 17 work until 02 jan 2021... Then bootloop...
I can't update after 02 jan 2021 (Galaxy Note 3 SM-N9005)
I can't update after 02 jan 2021 on my Galaxy Note 3 SM-N9005, all work good but when the phone restart... an infinite reboot... I make a video to show what happen If I reinstall the 02 jan 2021 update the phone work perfectly... Ideas?
forum.xda-developers.com

Stuck at bootloader--HELP!

Let's get this out of the way. I don't have much experience flashing ROMs. I've done it on a few phones, but I can't say I really understood what I was doing. I'm just good at following directions. So, I know about enough to get into trouble.
And ...I've gotten into trouble. My goal is to install LineageOS on my brother's Essential Phone. Based on directions I found here, I determined the active slot was b, so I installed TWRP on slot a. TWRP worked in recovery, but without touch. I then flashed twrp-3.2.3-0-mata.img to the non-active slot. Lastly, I sideloaded twrp-installer-mata-3.2.3-0.zip. I then changed the active slot back to b and rebooted. It now boots only to the bootloader and not to the OS. No matter what option I select--Start, Bootloader, Recovery--it reboots to the bootloader.
Any help to get out of this would be greatly appreciated.

Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps

MuddyDog said:
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
Click to expand...
Click to collapse
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.

mcmc08 said:
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
Click to expand...
Click to collapse
Try:
Fastboot flash:raw boot_slot recovery.img

So, I found a solution. In order to overcome the errors I was getting, I had to use the raw command. So it was fastboot flash:raw boot [image file]. Once Lineage recovery was installed, I could boot to recovery and sideload Lineage.

MuddyDog said:
Try:
Fastboot flash:raw boot_slot recovery.img
Click to expand...
Click to collapse
I guess our replies crossed. At any rate, the raw command did the trick. Thanks for your help.

I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)

Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.

rocketrazr1999 said:
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
Click to expand...
Click to collapse
I installed Lineageos directly on the february android stock version. (which is the last one from Essential)
Simply by following the tutorial on the LineageOS website.
Everything worked the first time.
So there is no need to switch back to the January android stock version. The image recovery provided by Lineage works very well.
And for your information LineageOS is updated almost every Monday.
Moreover the developers of the TWRP are not the developers of Essential. Company which closed at the end of February.
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
KJannot said:
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Click to expand...
Click to collapse
Which Rom would you like to install instead of Lineage?

groovebox said:
Which Rom would you like to install instead of Lineage?
Click to expand...
Click to collapse
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?

KJannot said:
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
Click to expand...
Click to collapse
Paranoid Android: What I heard is VoLTE broken, if you enable it, SMS/MMS might not work properly.
Evolution: No update in Android 10 since August, not sure they contine to support Essential phone for Android 11
Pixel Experience: I don't think they Anroid 10 for Essential phone, only official Anroid 9 which is too old
TWRP issue: You need to go back to Jan stock rom before going to any rom if you just flashed LOS
What current stable rom with Nov security update: I'm using crDroid 6.12 (unofficial release but from XDA reliable source)
https://forum.xda-developers.com/essential-phone/development/rom-crdroid-v6-7-t4129739