Related
Guys please dont flame me i am having a pannic attack and cant think strait. i rooted and flashed twrp with moto g5 plus tool kit, then later used ex kernel, then got update ota notioce...i knew it wouldnt work but was suprised it downloaded and propt to restart..so i did thinking it would say no you cant.. instead stuck in twrp like there is no os! please help. I dont know how to reflash the stock os, my backup didnt work when i restored it, and besides that after trying to restore i ended up wipin g and formatu=ing data and looso=ing it now anyway. i am shaking help please
I have just tried to flash lineage zip and it said succesful but when rebooting it goes strait back to twrp, have i lost my boot img ? what can i possiblu do, i am concerned if i download the 1.6 gig stock rom file from g5 plus kits "factory rom kit" it wont be the propper rom for my region "australia" or wont even have a modem..what can i do.. god why dont i stillhave any xanax
when trying to flash stock rom with toolkit the log says bootloader slot suffix not found and bad key
So i finally drank enough scotch to calm down, and realized the "errors" were not actually preventing the stock rom from flashing... and i now have not only a working rom but a baseband..so my reccomendation goes out to anyone panicked to just flash the downloaded stock rom found in the links of the moto g5 plus toolkit
Never,take otas with custom recovery , the solution is flash whole rom
djzero86 said:
Never,take otas with custom recovery , the solution is flash whole rom
Click to expand...
Click to collapse
Yes.. I truly thought there would be a "wah wah wah" notice being rooted.. But it went straight in to it. Just didn't know where any stock rocks were and wasn't prepared.. And ended in a hyperventilating mess. At least I now have the files
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
djzero86 said:
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
Click to expand...
Click to collapse
true! My last phone I felt secure and that it was completely unbrickable all because I had all the necessary rescue files and backups. And I had learned from every previous disaster. Thank you for your kind words friend.
Can't get fastboot to recognize device
So I'm kind of in the same boat as you were. I unlocked the bootlader and rooted the phone before giving it to my wife. During that whole process, fastboot had no problems recognizing the phone (obviously). Then my wife tried to update via the OTA which got her stuck in TWRP. I'd like to reflash the stock ROM, but the problem I have is that TWRP won't just flash the zip file ("invalid zip file format"), and I can't use fastboot to do commands line by line since "fastboot devices" doesn't show my phone anymore. I was able to get her going on a custom ROM for now, but I'd like to put her back on the stock ROM so we won't encounter this problem again. I've reinstalled the Motorola driver several times, but no luck. ADB has no problems recognizing the phone when in TWRP recovery. One thing that happened recently was a big update to Windows 10, but I'm not sure if that is the reason for my fastboot issues.
Any advice would be appreciated.
Just a follow up, I tried uninstalling/reinstalling the Motorola driver and ADB on the original computer, but for some reason it still won't "see" the phone in fastboot. I was able to install ADB/Fastboot and the Motorola driver on a separate computer (also Windows 10) to get fastboot to recognize the phone so I could issue commands to reinstall the stock firmware. I noticed, though, that the following commands FAILED when I entered them:
fastboot erase customize
fastboot erase clogo
I'm not sure what those were for, but the phone seems to be working fine on the stock firmware now.
I downgraded from custom Nougat to stock Marshmallow as I discovered that the incall sound (hearing the caller from the ear speaker) is louder and clearer, so of course I lost TWRP recovery and root in the process which is normal. However, I now can't re-install TWRP as a .img file since although I can boot into Android Recovery I can't go into Fastboot mode (phone just re-starts every time) so of course it's no go whether I try Axon Toolkit or ADB via computer. I also tried the EDL route but same thing.
I have all the required ZTE and Qualcom drivers installed. My phone's model is the 2017G and the bootloader is still unlocked.
Only thing I can try is installing TWRP as a zip file through Android Recovery or directly from 'system update' via the phone's menu. Problem is I can't find a zip version of TWRP for the Axon 7
Any help/suggestions most grateful.
xectis said:
I downgraded from custom Nougat to stock Marshmallow as I discovered that the incall sound (hearing the caller from the ear speaker) is louder and clearer, so of course I lost TWRP recovery and root in the process which is normal. However, I now can't re-install TWRP as a .img file since although I can boot into Android Recovery I can't go into Fastboot mode (phone just re-starts every time) so of course it's no go whether I try Axon Toolkit or ADB via computer. I also tried the EDL route but same thing.
I have all the required ZTE and Qualcom drivers installed. My phone's model is the 2017G and the bootloader is still unlocked.
Only thing I can try is installing TWRP as a zip file through Android Recovery or directly from 'system update' via the phone's menu. Problem is I can't find a zip version of TWRP for the Axon 7
Any help/suggestions most grateful.
Click to expand...
Click to collapse
If you can use miflash there is a thread somewhere that has stock everything with twrp included. I'm on my phone so I can't find it right now. But if you can't find it by the time I get to my computer I'll look through my history to try and find it.
JTruj1ll0923 said:
If you can use miflash there is a thread somewhere that has stock everything with twrp included. I'm on my phone so I can't find it right now. But if you can't find it by the time I get to my computer I'll look through my history to try and find it.
Click to expand...
Click to collapse
Thanks for the response. I looked around for the thread you mentioned but had no luck in finding it yet but I'll keep looking meantime.
Thanks
xectis said:
Thanks for the response. I looked around for the thread you mentioned but had no luck in finding it yet but I'll keep looking meantime.
Thanks
Click to expand...
Click to collapse
So the thread I found was actually not for the g model sadly. But, have you seen this thread?
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547/page10
Down a ways there is a "TWRP flashable bootstack/stock system images" section. I think if you can flash those (maybe with miflash?) You should then have fastboot available to flash twrp again.
When you unlocked surely you learned how to use the tools to flash twrp without fastboot.
You can use miflash, the toolkit, tenfar's tool or tenear's tool.
There's a million and one guides on how to to this plus the actual tool threads.
Even the twrp thread has a guide.
JTruj1ll0923 said:
So the thread I found was actually not for the g model sadly. But, have you seen this thread?
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547/page10
Down a ways there is a "TWRP flashable bootstack/stock system images" section. I think if you can flash those (maybe with miflash?) You should then have fastboot available to flash twrp again.
Click to expand...
Click to collapse
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
xectis said:
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
Click to expand...
Click to collapse
Okay so since I was not paying that much attention (sorry) I just realized that those are bootstacks and stock systems that you can flash in TWRP. My bad. But I have been looking around and on that thread I just had you go to he mentions another thread with step by steps that may help you! Here it is. Good luck!
xectis said:
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
Click to expand...
Click to collapse
JTruj1ll0923 said:
Okay so since I was not paying that much attention (sorry) I just realized that those are bootstacks and stock systems that you can flash in TWRP. My bad. But I have been looking around and on that thread I just had you go to he mentions another thread with step by steps that may help you! Here it is. Good luck!
Click to expand...
Click to collapse
Ignore the fastboot part. Just reinstall twrp with axon7tool, then install raystef66's TWRP flashable B09 bootstack and stocksystem zips (plus magisk if you won't relock), then follow his guide on how to get rid of the 5 seconds screen to get fastboot and, well, get rid of the 5 seconds screen
p.s. I basically just found out that I said the exact same thing on that crappy Q&A thread...
Choose an username... said:
Ignore the fastboot part. Just reinstall twrp with axon7tool, then install raystef66's TWRP flashable B09 bootstack and stocksystem zips (plus magisk if you won't relock), then follow his guide on how to get rid of the 5 seconds screen to get fastboot and, well, get rid of the 5 seconds screen
p.s. I basically just found out that I said the exact same thing on that crappy Q&A thread...
Click to expand...
Click to collapse
The link you provided is titled 'Get TWRP and root after updating to Nougat'. As am on Marshmallow I'll have to first update to Nougat? . So do I go ahead and flash stock Nougat from ZTE's page before following the instructions on that page? Sorry for my confusion.
**Update** I followed instructions of link you provided to install TWRP but I came to a brick wall every time. Short story is no matter what I tried I cannot install anything with either ADB, Miflash or Axon Toolkit. The big problem here is the Fastboot issue which otherwise would make things so much easier. Only thing left for me to do is just to upgrade stock firmwares via the phone's update option and remain bootloader unlocked. The Axon 7 is still a great phone, it's just too much hustle getting things done so I'll just have to sell it. Samsung and HTC phones are much easier to work with when it comes to rooting/installing custom ROMs.
***Update 2*** Success!! I managed to install fastboot/bootloader mode by following the section 'Get Fastboot' from that same link you provided so now I have latest TWRP installed and the 5 second notice has also disappeared. Am back in the running now. Many thanks for your help
xectis said:
The link you provided is titled 'Get TWRP and root after updating to Nougat'. As am on Marshmallow I'll have to first update to Nougat? . So do I go ahead and flash stock Nougat from ZTE's page before following the instructions on that page? Sorry for my confusion.
**Update** I followed instructions of link you provided to install TWRP but I came to a brick wall every time. Short story is no matter what I tried I cannot install anything with either ADB, Miflash or Axon Toolkit. The big problem here is the Fastboot issue which otherwise would make things so much easier. Only thing left for me to do is just to upgrade stock firmwares via the phone's update option and remain bootloader unlocked. The Axon 7 is still a great phone, it's just too much hustle getting things done so I'll just have to sell it. Samsung and HTC phones are much easier to work with when it comes to rooting/installing custom ROMs.
***Update 2*** Success!! I managed to install fastboot/bootloader mode by following the section 'Get Fastboot' from that same link you provided so now I have latest TWRP installed and the 5 second notice has also disappeared. Am back in the running now. Many thanks for your help
Click to expand...
Click to collapse
You could have bricked your device. I specifically told you not to follow that part. Also what has adb, axon7toolkit and miflash got to do with that guide? You have to use axon7tool just like a) it says there and b) i told you on the q&a thread
Choose an username... said:
You could have bricked your device. I specifically told you not to follow that part. Also what has adb, axon7toolkit and miflash got to do with that guide? You have to use axon7tool just like a) it says there and b) i told you on the q&a thread
Click to expand...
Click to collapse
Yes you did warn me about the fastboot part but I was stuck as nothing else worked. By using the Fastboot instructions I managed to install TWRP and root the phone. I used Miflash to install the fastboot package which was successful. Now I can boot to Fastboot and bootloader via TWRP. Remember am on Marshmallow so I guess that helped not to brick the phone? I don't know but it worked.
xectis said:
Yes you did warn me about the fastboot part but I was stuck as nothing else worked. By using the Fastboot instructions I managed to install TWRP and root the phone. I used Miflash to install the fastboot package which was successful. Now I can boot to Fastboot and bootloader via TWRP. Remember am on Marshmallow so I guess that helped not to brick the phone? I don't know but it worked.
Click to expand...
Click to collapse
Well again, if you want to be on Nougat, download raystef66's flashable B09 bootstack and stocksystem, flash them on TWRP with Magisk 15.2, and follow his guide on how to get rid of the 5 seconds screen (all in twrp, don't get out of it).
Just do all of that or you'll lose fastboot. Also that zip that you got from that ancient guide doesn't work on anything else than Marshmallow
Choose an username... said:
Well again, if you want to be on Nougat, download raystef66's flashable B09 bootstack and stocksystem, flash them on TWRP with Magisk 15.2, and follow his guide on how to get rid of the 5 seconds screen (all in twrp, don't get out of it).
Just do all of that or you'll lose fastboot. Also that zip that you got from that ancient guide doesn't work on anything else than Marshmallow
Click to expand...
Click to collapse
Thanks for the advice. If I keep the phone I'll wait for a stable Oreo update. Nougat didn't impress me much.
This is the latest Nougat update that was released on 06/11/2018. It does not flash recovery or laf. If you must have laf, there is an additional zip to flash.
It is still ARB 2, so you can flash back to any version of Nougat.
I have removed the recovery-from-boot.p file from system so that recovery doesn't get overwritten, but that is the only change that was made -- this is not a debloated ROM.
Please let me know if you have any problems.
ROM download: h901_v30d.zip
OK, now for my spiel on laf...
You only need to install the laf zip if you have installed TWRP on laf in addition to recovery, and you would like download mode back.
I *HIGHLY* recommend that you keep TWRP on both recovery and laf. You will never be in a situation where download mode would help you, but TWRP couldn't.
You CAN be in a situation where TWRP could have helped you, but you are just stuck with download mode.
laf download: h901_laf.zip
-- Brian
Thanks for the update. I was very quick! I wanted to report that when flashing it did not show each file flashing like it usually does, it just keeps saying " please wait" , and then it finishes and on to the next zip which was the root file flash, that acted normally. I'm grateful Brian! Thanks
I'll take a look, I am sure I messed up a progress meter.
Thanks,
-- Brian
woohoo!
runningnak3d said:
This is the latest Nougat update that was released on 06/11/2018. It does not flash recovery or laf. If you must have laf, there is an additional zip to flash.
It is still ARB 2, so you can flash back to any version of Nougat.
I have removed the recovery-from-boot.p file from system so that recovery doesn't get overwritten, but that is the only change that was made -- this is not a debloated ROM.
Please let me know if you have any problems.
ROM download: h901_v30d.zip
OK, now for my spiel on laf...
You only need to install the laf zip if you have installed TWRP on laf in addition to recovery, and you would like download mode back.
I *HIGHLY* recommend that you keep TWRP on both recovery and laf. You will never be in a situation where download mode would help you, but TWRP couldn't.
You CAN be in a situation where TWRP could have helped you, but you are just stuck with download mode.
laf download: h901_laf.zip
-- Brian
Click to expand...
Click to collapse
thank you man! it works like a charm. no problem at all. .
:highfive:
Does it matter what version I'm coming from? Receiving a refurbished phone tomorrow that is supposed to be on LP but could be MM or even Nougat. I want to install TWRP like I did on my original phone (MB died) then upgrade to this.
Nope, doesn't matter. Once you get TWRP on your phone, you can flash this and go straight to the latest.
-- Brian
Does anyone have a link to the actual kdz?
I re-locked the phone trying to fix a grayed out "Enable OEM unlock" switch that was turned off in the developers options and in the process of locking the bootloader, it is unable to boot up again but I can still get into fastboot and download modes.
I know how to restore the phone through LGUP, just need the kdz, either 30c or 30d would work, thanks.
For some reason it seems that flashing this relocked the bootloader and bricked the device. Getting the message "Your device is corrupt. It cannot be trusted"
Was on 5.1.1 and it's my wife's phone. Downloaded the zip and Magisk and rebooted into TWRP. Flashed and now just about bricked. Now to try and see if I can unbrick the phone.
NightShade00013 said:
For some reason it seems that flashing this relocked the bootloader and bricked the device. Getting the message "Your device is corrupt. It cannot be trusted"
Was on 5.1.1 and it's my wife's phone. Downloaded the zip and Magisk and rebooted into TWRP. Flashed and now just about bricked. Now to try and see if I can unbrick the phone.
Click to expand...
Click to collapse
Same thing here, had to find a KDZ, found one and flashed it and everything is good now.
KDZ 30d: https://lg-firmwares.com/downloads-file/15906/H90130d_00_0611.kdz
ziphoy said:
thank you man! it works like a charm. no problem at all. .
:highfive:
Click to expand...
Click to collapse
hey guys how do i install this? i am comming from Eliminater74's stock. think its 5.x and i have twrp so not sure if i can just flash it. reason i ask is cuz another user said he had to kdz coming from 5.x so think i might have the same problem.
Tried using this one, Flashed, but only getting a boot back into TWRP what am I missing?
lg H901 30d root needed
hello can someone help me root LG H901-30d android 7 , i need to root this device but no method for this version (TMB)
Any other download link then Gdrive ???
When I try, it just shows a faliue msg after 10%
I have screwed my phone big time. It has been screwed for a while and I've been searching for methods to fix it. So awhile back when I didn't know about the sheer amount of models of this phone there are, I tried to flash TWRP. The image was not for my model and my recovery is screwed. I figured that it was no big deal, the phone worked just fine. Not long afterwards, I was goofing with Xposed modules. One of these broke Asus's ZenUI or something, because the phone boots up and Systemui.apk immediately crashes and won't stop. It's just a black screen with the error message box. There is a repair option that pops up in the dialogue box after a while, but it does nothing. I've tried remote wipe with Google services, but my location services are off and I can't turn them on. I've tried Xposed safe mode, but it won't engage. USB debugging is off and I can't enable it or USB mass storage mode, because there is a prompt that I can't tap. I can't get into recovery, because it just goes right to the boot logo. Fastboot works, but I can't flash a new firmware with it, because the bootloader is locked. Does anyone have any suggestions or even a backup of the original recovery.img for the US model? ASUS provides the system but not recovery.img and their support staff gets angry if you ask for it. The root of the issue is Systemui.apk. Since I can't just replace that, I have to restore, and I don't have a way to restore Android to factory settings.
Unofficial bootloader unlock followed by flashing twrp or stock recovery if you can find it. Twrp will allow you to mount your sdcard if you want to try just replacing systemui.apk, otherwise both recoveries can flash back the stock Rom. You might be able to get away with dirty flashing your current rom if replacing the APK doesn't work.
wang1chung said:
Unofficial bootloader unlock followed by flashing twrp or stock recovery if you can find it. Twrp will allow you to mount your sdcard if you want to try just replacing systemui.apk, otherwise both recoveries can flash back the stock Rom. You might be able to get away with dirty flashing your current rom if replacing the APK doesn't work.
Click to expand...
Click to collapse
That's the thing, though. There is no twrp available. There is no stock recovery available. I can't unlock the bootloader, because ASUS never released a working method to do it. I am screwed.
Have you tried to dirty flash the same firmware version you have via Asus flash tool?
wang1chung said:
Have you tried to dirty flash the same firmware version you have via Asus flash tool?
Click to expand...
Click to collapse
Sorry about the delay, but ASUS flash tool doesn't recognize the phone, either in system or fastboot modes. That tool doesn't seem to work with fastboot. Basically I have to do some trickery with fastboot but there isn't much available to do with it.
Sorry, it's not Asus flash tool, it's sp flash tool.
Check out this guide.
wang1chung said:
Sorry, it's not Asus flash tool, it's sp flash tool.
Check out this guide.
Click to expand...
Click to collapse
Tried this. Have the official firmware but need a scatter file. The one in the firmware zip is deemed invalid because it is missing a lot of the required data I suppose. If only I had made a backup of everything while the phone was still working...
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.