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.
Well, it's not so bad.
Yesterday I bought this phone and applied the October update. Then I flashed TWRP by @mohancm (I wasn't sure about that but I did it anyway). And then I flashed Magisk. But because I couldn't get Xposed to work, I tried to remove Magisk (unsuccessfully it seems) and flash SuperSU. I played around by switching from slot B to A. I am not sure exactly what I did.
The end result is that the phone won't boot when I turn it on. (I think I might still have TWRP installed, but I am not sure.) I tried flashing stock boot.img via fastboot, but I get get an error (I think it's something to do with the partition table). I can't flash using MiFlash because it says I don't have the permission. (I've had bad experiences with MiFlash before.)
However, I am able to boot the phone manually. When I boot to bootloader I can just boot stock boot.img (flashing doesn't work like I said), and then the system boots properly and I'm rooted.
Any ideas what I can do now to fix the issue. I just need to try to avoid random reboots and I can use my phone just fine, but is there a way to fix it? Should I just wait for the November update? Any hope of getting a ROM that I can flash using TWRP?
Edit: I'm dumb. Of course you can flash an image via TWRP. I flashed the stock image via TWRP and now the phone boots properly. Problem solved.
I followed the instructions on this page and I got into a bootloop, so I flashed the stock android and it got me out of the bootloop, but i dont want to be on stock i want to be on RR so how can i not get bootlooped after flashing it? apperently im not the only one with this problem but nobody managed to fix it other than flashing the stock rom so I hope maybe somebody here can help me, btw i also flashed gapps after i flashed RR
YayJohn said:
I followed the instructions on this page and I got into a bootloop, so I flashed the stock android and it got me out of the bootloop, but i dont want to be on stock i want to be on RR so how can i not get bootlooped after flashing it? apperently im not the only one with this problem but nobody managed to fix it other than flashing the stock rom so I hope maybe somebody here can help me, btw i also flashed gapps after i flashed RR
Click to expand...
Click to collapse
I had that problem too when flashing the non-treble version. I'm not sure if this was your issue, but I had to boot back into TWRP and change slots in the reboot menu. Then it booted. So next time, you might give that a shot.
There is a step missing in the instructions too. There is no instruction on when to flash the gapps. Flashing them *after* Magisk worked for me.
If audio quality matters to you, I haven't found a custom ROM that sounds as good as stock, so I'm back on the stock ROM, even though I really liked RR.
Omineca said:
I had that problem too when flashing the non-treble version. I'm not sure if this was your issue, but I had to boot back into TWRP and change slots in the reboot menu. Then it booted. So next time, you might give that a shot.
There is a step missing in the instructions too. There is no instruction on when to flash the gapps. Flashing them *after* Magisk worked for me.
If audio quality matters to you, I haven't found a custom ROM that sounds as good as stock, so I'm back on the stock ROM, even though I really liked RR.
Click to expand...
Click to collapse
i already fixed it and it was the way u fixed it
I found solution for this just flash pie any security patch using mi flash tool which will automatically correct partition, it worked for me.
My previous V20 died of a NAND issue and I liked it so much I got another one. I followed the DirtySanta guide, then installed the Alpha Omega Oreo ROM following the directions on the post. After a while, the ROM became very unstable and slow and laggy, so I wanted to go flash the ResurrectionRemix SSDev build that was released recently. I flashed it, only to discover it didn't work. I figured it was because of AO's total flashing of the system, giving it a new bootloader and such. The only way I could think of getting the Nougat aboot back was to flash to stock, do the DirtySanta process again, and install the ROM. I was able to flash the stock image (VS995 12A) and it went fine, until the phone booted. Once it boots, it just says "Settings has stopped" and that message keeps reappearing instantly after dismissing the previous message. I've tried flashing three different VS995 images, and even a US996 image, but they all have this issue. Did I get yet another phone with a NAND issue, or am I just missing something?
It may be necessary to go in to recovery and wipe every thing......no guaranty.
stinka318 said:
It may be necessary to go in to recovery and wipe every thing......no guaranty.
Click to expand...
Click to collapse
For some reason I couldn't enter the recovery on any of the VS995 images, but it worked on the US996 image. I decided to stay with the US996 image, so now my phone is a US996 on VS995 hardware. Oh well, it fixed the obnoxious vibrating on boot. Thanks for the suggestion.
Hello,
i got a second phone for my GF as i was really happy with this phone and had it flashed without any issues before. This second phone is used and was over a year in use from the guy i've bought it from. It was 100% fine and he always used the shipped Android with it.
So i went on, got the latest TWRP for the phone. Flashed it without any issues and tried to install LineageOS from their website. Flashed it and tried to flash TWRP back as LOS replaces it. I wanted to use TWRP install the backups. But that's where it started to go wrong. Lineage seemed to have been gone from that point on. I couldn't get it to work again, even with reflashing and such. I've downloaded CRDroid and Paranoid and tried them but no luck. Non of them where booting up and TWRP stays showing a warning about "No OS installed".
After some more digging, i've found some posts stating that i would need newest firmware and venders. I've downloaded and flashed them but this made it even worse. The phone started to be stuck in fastboot. I got it working again by flashing latest MIUI version with Xiaomi Flash Tool.
Then i've installed TWRP again but somehow any rom i flash does not boot. The phone starts with the MI logo and flashes once and loads TWRP. There is no message about missing OS or any kind or error when flashing any of these roms.
Anyone able to help me?