Related
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.
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+.
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
MoistPicklez said:
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
Click to expand...
Click to collapse
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Does it have to be touch though? Could it be more old school clockworkmod recovery where you use the buttons or really like default recovery. I don't know enough about it but just a thought. You definitely get use to just downloading and flashing in twrp and it would be cool to find that with the PH-1.
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Been waiting for someone to share this for 6 months.. thanks lol
aer0zer0 said:
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Edit: I wonder if since TWRP worked with the touch driver from the Nougat kernel, if it could work with the P kernel? Maybe whatever was changed in Oreo that prevented it from working has been fixed?
starcms said:
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Click to expand...
Click to collapse
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
aer0zer0 said:
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
Click to expand...
Click to collapse
Not possible to use the driver in userspace after TWRP decrypts the device (userspace) using the default password (after any patterns or pins are removed from the lockscreen)?
Edit: And what the heck is the driver doing in userspace anyway? Shouldn't it be in /vendor? If the driver is in userspace, then how can the touchscreen work after a factory reset?
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
It doesn't after you lets say flash magisk and gapps they create a script in /system/addon....and when updatting lineage it runs the scripts in the addon folder which is how gapps and magisk get installed to the new updated system and boot.....first magisk and gapps have to be flashed in twrp....after that u shudnt need it on dirty flashes
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
@aer0zer0
This seems like the easiest solution to getting TWRP working on the Oreo and P boot images and being able to keep it permanently installed in ramdisk. Make TWRP use the volume up/down keys for scrolling and the power key to select. If the touchscreen is soooo difficult to get working, forget it. If someone really wants to use the touchscreen, they can use the existing TWRP version built on the Nougat boot image.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Has anyone looked in the stock P kernel? I was poking around and noticed some twrp residual files. This was straight from the images zip from essential. I didn't touch it.Wth are they in there for? Could they have a better twrp on the back burner for kernel development purposes for Essential? It was in the ramdisk, ill look again tomorrow when I unpack the boot.img. it would make sense to have it in ramdisk, pixel 2 has it like that. Ill post screenshots after work. But, the conversation looks good folks, you are on to something. We could always bust out some phillz recovery, or clockwork mod.
starcms said:
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Click to expand...
Click to collapse
I would say it is more stock-ish as far as recoverys go. It's a stock LOS recovery. You can factory reset, flash or sideload update.zips or signed zips no regular custom ROM zips or magisk. It is meant to run on LOS, it only runs on LOS actually and not made for the flashaholics out there. It's a good start though.
Sorry, out right now and no other phone/camera handy.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
One could also theoretically copy a copy of the twrp boot. Img to the ex kernel manager backup file, and while booted into the system, hit restore kernel and since its in the boot partition it will flash it then reboot into recovery. Then from there flash your normal kernel and boot back to system/android.. i backup all my kernels after rooting them so after flashing otas, i can just flash my prerooted kernel and reboot without having to flash magisk
Edit. This works, i just did it, but u must make it reboot to bootloader to then tell it to reboot recovery. I dont know if flashify is the same
MoistPicklez said:
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
Click to expand...
Click to collapse
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
dirtyreturn said:
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
Click to expand...
Click to collapse
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
MoistPicklez said:
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
Click to expand...
Click to collapse
Hey, Rashr doesn't support this device(phone). I get a reboot to recovery option and if I tap cancel the app just closes. Did the app identify what it needed to?
In Flashify there are 3 options ,Flash - kernel,boot, and zip. What I'm curious about is , when choosing just the zip option - would twrp first need to be flashed to the boot partition?
Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.
Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something
Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .
Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.
I have an LG V20 H910 dirty unlocked, rooted, and currently using LOS 16
I bought this phone 8 months ago for the sake of me tweaking with it, but unfortunately it didn't go well
The first thing i noticed was the screen ghosting, then the phone is very slow on stock ROM (H910PR 10f i think), so i rooted the phone and installed TWRP
I did installed the Stock Oreo ROM but i still decided to clean flash LOS 15.1 then dirty flashed LOS 16, and here i am still my current ROM is LOS 16.
I need to install the latest TWRP for me to theoretically install Gamma kernel (cuz mine just goes stuck to fastboot after, i dunno why)
So i thought maybe my TWRP is outdated, so i want to update it, but i can't, it is stuck on fastboot after, just like the kernel
I'm currently on @Phoenix591 TWRP 3.2.3-1 and this is literally as far as i can go, because anything later than that (like the lastest 3.3.1-1 or even just 3.2.3-4) bricks my phone to fastboot.
Can anyone help me with this, please?
Download the newest version from the TWRP thread, and then in your TWRP, hit "install" and then select to install by .img and not .zip and you should be able to flash that way. Otherwise do it through fastboot which I can help you with if you need to. Let me know.
iTzFeRReTTi said:
Download the newest version from the TWRP thread, and then in your TWRP, hit "install" and then select to install by .img and not .zip and you should be able to flash that way. Otherwise do it through fastboot which I can help you with if you need to. Let me know.
Click to expand...
Click to collapse
Already tried, still nothing, installing through TWRP or adb bricks the phone
MEMO#22 said:
Already tried, still nothing, installing through TWRP or adb bricks the phone
Click to expand...
Click to collapse
just for kicks (it won't hurt anything, but chances arn't great it'll help... but its something), does the us996 variant of twrp do the same thing?
There's basically no difference besides what the device calls itself (and some minor kernel options) for the purposes of checking what roms should be allowed to flash.
Also just to cover our bases, have you double checked the md5sum of the downloaded ATT twrp image and ensured it matched what android file host shows for it? (if the download was corrupted in such a way as to prevent it from booting properly it might end up going into fastboot from THAT)
Phoenix591 said:
just for kicks (it won't hurt anything, but chances arn't great it'll help... but its something), does the us996 variant of twrp do the same thing?
There's basically no difference besides what the device calls itself (and some minor kernel options) for the purposes of checking what roms should be allowed to flash.
Also just to cover our bases, have you double checked the md5sum of the downloaded ATT twrp image and ensured it matched what android file host shows for it? (if the download was corrupted in such a way as to prevent it from booting properly it might end up going into fastboot from THAT)
Click to expand...
Click to collapse
Yeah i did, still no luck
I downloaded both my current version and the latest one twice, md5 also matches but still nothing