Related
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
CiT42 said:
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
Click to expand...
Click to collapse
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Choose an username... said:
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Click to expand...
Click to collapse
I flashed DrakenFX's B29 stock rom. Didn't thought it would work with recovery but anyway ! Thank you.
Do you recommend some ROMs, kernels, etc ?
CiT42 said:
Do you recommend some ROMs, kernels, etc ?
Click to expand...
Click to collapse
Nah, they are all mostly bad. The best of the bunch seems to be NucleaRom, it has an okay kernel (Radioactive, not too good battery-wise but I've never seen so little UI lag, like, ever) and okay features (like 1/3 of what ResurrectionRemix has), an awesome maintainer (OrdenKrieger) and boots in like 15 seconds
But the stock ROM is currently the best of them all, not battery wise (you can get some obscenely high SOT numbers on LineageOS with Substratum black themes) but it's fluid and stuff runs well on it. The status bar is hideous though, and MiFavor is white themed, on an AMOLED screen, what the crap ZTE?
Don't try PureNexus, permanent hard brick from the looks of it.
LineageOS works okay but it has some compatibility problems with some apps I use, dunno
I think you could try the dual-boot patcher, that way you can test the roms and keep a working stock rom to use it as your daily driver without losing data. i never used the dual boot patcher though, so good luck if you will use it
I've bad experiences with Dual boot on my old 1+.
Hi, I want to install TWRP on my phone, but it requires flashing vbmeta. I can find all kinds of links on xda, as well as one from Google's official GSI image.
I'm a little paranoid about the security issue on flashing random vbmeta on the machine, so my question is: is the vbmeta from google generic and can be flash to any arm device, or I have to use the one from 9t forum? Thanks!
ccaappton said:
Hi, I want to install TWRP on my phone, but it requires flashing vbmeta. I can find all kinds of links on xda, as well as one from Google's official GSI image.
I'm a little paranoid about the security issue on flashing random vbmeta on the machine, so my question is: is the vbmeta from google generic and can be flash to any arm device, or I have to use the one from 9t forum? Thanks!
Click to expand...
Click to collapse
Install the official TWRP, no wiping, flashing VBMeta or anything needed (QFJEUXM 11.0.4):
https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Every time you boot to TWRP, enter the same pin you are using when you boot to Android or you use there for unlocking the screen
After reading so many guides and going through ROM threads, I've been left confused on how to flash my 6T with different ROMs and the best way of doing it without bricking the device.
Currently I am on rooted OOS 10.3.4 running Cleanslate Kernel. (TWRP 3.4.0)
So can anybody help me with these questions for which I am UNABLE to find any answers.?
1. What Fastboot Rom should I flash on my device if I cant find 10.3.4 fastboot. Can I flash 10.3.3 and proceed? Also, can I flash fastboot roms via TWRP without the need of turning on my PC.
2. A lot of people are suggesting downgrading TWRP to 3.3.x. How do I downgrade it? By merely running the .img file in the fastboot mode and flashing the zip?
3. Does TWRP 3.3.x have that AB partition thing where we have to flash everything TWICE to get the roms on both the slots? Or just a single swipe to install would do?
1. Use the SourceForge Link on the Fastboot Thread, even 10.3.5 is there. If you want though you can use 10.3.3
2. Just run the 3.3.1-32 installer from 3.4.x. I removed 3.4.x from my LOS Guide as it caused so many problems. The installer for -32 works properly and will still install in both slots. No need to do the install "ramdisk method."
3. No matter which version you choose your phone will still have a A/B partitions. You can't (well shouldn't) have OOS and an AOSP rom on each. Both partitions need to have the same type of ROM. It can cause weird problems if they are different. This is why on the initial install you flash the ROM twice. When you update your ROM, you only flash it once.
My Installing Lineage Guide works for many other custom ROMs, you might look through it. There is also a Cliff Notes version in Post 2 if you want something a bit shorter.
So my current phone recently broke. So I decided to dust of my old Axon 7 which was still using Android 6.0.1. A bit old for these days since a lot of apps won't work. The best thing I could think of was to install a different rom. After a lot of work I finally managed to unlock the bootloader and install TWRP. Then I tried to flash a rom but to no avail. I have tried many things and now I can access only TWRP and EDL through ADB. I cannot access the Bootloader menu anymore. Does anyone know what to do next? How can I fix this and try to flash something again?
Edit: Forgot to mention that I currently have the most recent version of TWRP installed. And the flashing error I get is Error 7, Googled that and tried every "fix" but none of them worked. Another strange thing is that my phone used to be A2017G, but now when I connect it to my pc it shows up as A2017U, Is this a driver issue or did I change something unintended?
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
klałn said:
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
Click to expand...
Click to collapse
Thanks for the reply! I was a bit ahead of you and managed to create a vendor partition using the Party v0.5 script, now I can flash ROMs just fine but the system won't boot (blinking red light, black screen)
I am using the most recent TWRP version for Axon 7 (3.5.2_9-0), I am not sure if this is part of the problem
I've found some possible fixes related to my original question for getting into the bootloader menu, but I have no idea on what to change to regain access to it. I do remember that it said the device name was ailsa_ii as you mentioned, and that the bootloader version was not specified (it was just blank)
Edit: never mind the bootloader menu issue, I managed to get back into it. But the system still won't load.
On which bootstack you are right now?
Which rom you want to try?
Custom roms won't work on stock bootstacks.
First, I would recommend to backup persist/efs partition, before futher changes.
Second, I would recommend upgrade stock marshmallow to nougat, then nougat to oreo and after that, flash universal v2 oreo bootstack.
Bootloader/fastboot was locked by zte on most stock roms.
For what for you need fastboot mode? EDL mode isn't enough?
If you really need fastboot, you may try this aboot on oreo bootstack. Didn't try it with universal v2.
I have no idea what bootstack I am on right now to be honest. How can I check this?
I want to install LineageOS 17.1.
The bootloader is unlocked, I am sure of that.
Sorry for my ignorance, I know I am in way over my head but I am dedicated to make this work.
So you probably on stock marshmallow bootstack.
I still recommend to upgrade system step by step. From 6.0.1 to 7.0, then to 8.0 B02 and applying A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip.
Why this way? Most of a7 users did that at beginning and official updates may do some changes to persist partition.
Some people complained about 50% battery bug, which came out of nowhere.
If you want take a risk, you can flash DrakenFX bootstack straight away or flash A2017G_B02_OREO_FULL_EDL in edl mode and then DrakenFX bootstack. At least - please - do efs partition backup using EDL Tool by djkuz, before doing such a jump.
I don't know if this gonna work. If you brick your device, you will have to download full edl packages, which may take even more time, than official way to upgrade.
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
DNYO31 said:
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
Click to expand...
Click to collapse
Have you tried booting phone to edl mode by holding vol-up + vol-down and pressing power button?
ZTE logo might not appear, but you should enter to dfu/edl mode by pressing those buttons.
It's really hard to make a brick of Axon 7.
In 2016-2017, I had to ground test points on the motherboard to leave DFU mode, but it's not necessary anymore.
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Shahaf said:
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Click to expand...
Click to collapse
OMG
You should first of all know your phone model
"Redmi 9T" reads as different name than "Mi 9T", isn't it?
Hence you MUST NEVER flash TWRP for Redmi K20/Mi 9T (guide clearly says it is for that phone, check the big picture in your post) to your Redmi 9T
oh damn, I can fix that somehow?
Shahaf said:
oh damn, I can fix that somehow?
Click to expand...
Click to collapse
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
zgfg said:
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
Click to expand...
Click to collapse
Thank you, I will check with them!
Shahaf said:
Thank you, I will check with them!
Click to expand...
Click to collapse
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
zgfg said:
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
Click to expand...
Click to collapse
It worked!!! now my device is working, now in order to root, which twrp should I use?
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
zgfg said:
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
Click to expand...
Click to collapse
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Flash (not boot) a healthy un-patched stock "boot.img" that is signed with your ROM version to the device and see if that works.
Shahaf said:
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Click to expand...
Click to collapse
fastboot boot xxx.img boots one time to the xxx.img
For flashing (permanently) to boot you need to use:
fastboot flash boot xxx.img
Before flashing the 'stock' or patched boot img, pls double check: compare your firmware name in Settings / My device against the fastbboot/tgz package you downloaded and extracted the boot.img from
Recovery images might be the same for several firmwares, but boot.img is more critical. If extracted from the wrong firmware, it will not be your real stock boot.img and will not boot
You can use this app (now when your phone boots) to download and look for the proper firmware:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
zgfg said:
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
Click to expand...
Click to collapse
it worked! thank you