I have a problem with installing the xiaomi mi 8 twrp with the twrp-3.2.3.1-dipper.img version,
when i try using the adb powershell command , first i renamed the recovery file to twrp.img
then when i inputted the "fastboot flash recovery twrp.img" , nothing happens and the powershell stucked
my bootloader already unlocked , rn using global v 9.5
already tried using USB 2.0 and USB 3.0 but no luck
Why not flash the latest version (3.3.something)? You could also try cmd instead of powershell. And of course check under developer options if USB is correctly configured for ADB access.
Sent from my MI 8 using Tapatalk
altae said:
Why not flash the latest version (3.3.something)? You could also try cmd instead of powershell. And of course check under developer options if USB is correctly configured for ADB access.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
my nation xiaomi 8 community said that 3.3 has some kind of issues , and prefer to use 3.2 for stability.
so i tried flashing with another pc and it worked , but there is another problem which is i cannot boot to the recovery mode using the "fastboot boot twrp.img" , i tried using unofficial TWRP in XDA
after i done this , my phone just stays black
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In that case I doubt that the installation process was successful. Did you test the ADB connection? Can you issue other commands like copying files etc.?
By the way I'm running 3.3 without any issues. But the installation process was a bit tricky. After the installation of TWRP through ADB I was unable to boot into TWRP recovery from the phone, I had to issue the corresponding command through ADB. I fixed this by making the device boot into TWRP through ADB and then flashing the TWRP Zip file once more but this time on the device instead of through ADB. Now the device finally boots into TWRP when I press the volume down and power button.
Sent from my MI 8 using Tapatalk
---------- Post added at 08:02 PM ---------- Previous post was at 07:40 PM ----------
One more thought: Are you 100 % positive that you have got the right version of TWRP? There are different versions for each phone...
Sent from my MI 8 using Tapatalk
Loald said:
my nation xiaomi 8 community said that 3.3 has some kind of issues , and prefer to use 3.2 for stability.
so i tried flashing with another pc and it worked , but there is another problem which is i cannot boot to the recovery mode using the "fastboot boot twrp.img" , i tried using unofficial TWRP in XDA
after i done this , my phone just stays black
Click to expand...
Click to collapse
Use the all in One tool
It has several versions of TWRP built in and I use it every time that I have an issue installing TWRP on any phone. Plus, it also has many other useful functions such as removing encryption. It can perform many additional functions.
Related
I'm trying to unlock bootloader. Checked all options in dev options like USB debugging and enable unlock bootloader.
Installed all the drivers. Booted into bootloader.
But when trying to see "adb devices", it doesn't show any devices.
For sometime, it shows some kedacom usb driver. I tried googling and tried to uninstall it and use google driver also. Even in device manager, it shows Android Device - Android ADB Interface, but still it shows nothing in list of devices attached in adb.
Also tried this thread - https://forums.oneplus.net/threads/solved-adb-is-not-working.347296/, but still doesn't work. Can someone help me out here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have TWRP installed? In that case flashing Super Su or Magisk from within TWRP should get you rooted. If TWRP isn't installed, Check for Funk Wizards thread in the official forum https://forums.oneplus.net/threads/...a-help-thread-ask-your-questions-here.477285/
Also, adb doesn't work from bootloader. It's fastboot in the bootloader. Enter recovery and check then
Seems like your phone is in bootloader/fastboot mode instead of in-rom ADB or TWRP ADB mode. This is the mode you're phone has to be in to be able to flash other recoveries like TWRP which however also requires your phone to be OEM bootloader unlocked (which completely wipes your phone), and from there you enter TWRP recovery using bootloader menu or power plus volume down, and there flash the latest 2.79 SR3 SuperSU to archive root/sudo functionality.
Either that or you actually did activate ADB under development options and accidentally installed the ADB device using the fastboot/bootloader driver instead of the ADB device driver.
When your in fastboot, you need to use fastboot devices as the command and other fastboot commands. You use adb devices command when your using adb, and connected with phone in recovery or booted.
I just installed the drivers that are on the phone when you plug it in in windows and minimal adb and fastboot from xda.
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Akhyll said:
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Click to expand...
Click to collapse
Excellent, enjoy.
Hello there and sorry if this was something asked 100 times. I haven't found quite something up to date.
So I've had my Mi 5 for some time now and I've decided to Root since I do need quite some features. Problem is I'm pretty scared of doing this since I've never done it before and I'd like to ask here if everything that I'm about to do is correct and if it's not I could get some steps into the right drections.
I'm on Global 9.1.1.0 (NAAMEI).
I'll be able to unlock my bootloader in exactly 10 hours since I had to wait for that stupid 72 hours lock so here's what I prepared.
From what I understand I need to flash TWRP Custom Recovery and download the specific one for my device. Their sites lists twrp-3.2.1-0-gemini.img as the latest for Mi 5 so this one I'm guessing is good to go?
I've also installed fastboot adb drivers installed, the TWRP mentioned above and I also renamed it to ''twrp'' to make things easier later on. That's how my curent folder looks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enable USB debugging from developer options, turn off my phone into fastboot my pressing volume down and the power key then connnect it to my PC via USB.
So I'm to shift right click into this very folder, open up cmd and type fastboot devices to see if my device is properly reconized it shoud show up some numbers. After that type fastboot flash recovery twrp.img then it shoud do it's thing and after that type fastboot boot twrp.img to load up TWRP.
I've put into my phone's storge the following to be ready:
- lazyflasher-no-verity-opt-encrypt.zip
- Magisk-15.3.zip
-Magisk uninstaller
After the recovery boots up I am to flash the lazyflasher and Magisk and hope my phone isn't bricked. Is this all that I need to make sure my phone will not bootload or anything like that? Thank you
Zardax said:
Hello there and sorry if this was something asked 100 times. I haven't found quite something up to date.
So I've had my Mi 5 for some time now and I've decided to Root since I do need quite some features. Problem is I'm pretty scared of doing this since I've never done it before and I'd like to ask here if everything that I'm about to do is correct and if it's not I could get some steps into the right drections.
I'm on Global 9.1.1.0 (NAAMEI).
I'll be able to unlock my bootloader in exactly 10 hours since I had to wait for that stupid 72 hours lock so here's what I prepared.
From what I understand I need to flash TWRP Custom Recovery and download the specific one for my device. Their sites lists twrp-3.2.1-0-gemini.img as the latest for Mi 5 so this one I'm guessing is good to go?
I've also installed fastboot adb drivers installed, the TWRP mentioned above and I also renamed it to ''twrp'' to make things easier later on. That's how my curent folder looks.
Enable USB debugging from developer options, turn off my phone into fastboot my pressing volume down and the power key then connnect it to my PC via USB.
So I'm to shift right click into this very folder, open up cmd and type fastboot devices to see if my device is properly reconized it shoud show up some numbers. After that type fastboot flash recovery twrp.img then it shoud do it's thing and after that type fastboot boot twrp.img to load up TWRP.
I've put into my phone's storge the following to be ready:
- lazyflasher-no-verity-opt-encrypt.zip
- Magisk-15.3.zip
-Magisk uninstaller
After the recovery boots up I am to flash the lazyflasher and Magisk and hope my phone isn't bricked. Is this all that I need to make sure my phone will not bootload or anything like that? Thank you
Click to expand...
Click to collapse
You only choose 1, either fastboot flash (replace ur existing recovery) or fastboot boot (just temp boot to twrp)... I suggest the latter...
You don't need lazyflasher with magisk, what's that for?... [emoji6][emoji6][emoji6]
Sent from my MI 5 using Tapatalk
Hi, today i tried to install MIUI 10 following this video: https://www.youtube.com/watch?v=eD5ftq6lTKo
When i could installed it, i tried to re-lock the bootloader with this other video: https://www.youtube.com/watch?v=9C47rmEKkys
But when i reboot the phone, on screen was this message: The system is destroyed, press power button to shutdown.
I tried to unlock again the bootloader to install the system but i receive this message from cmd: FAILED (remote: Token Verify Failed, Reboot the device
)
I don´t know what to do, i tried with test points to flash with miflash, i tried with miflash unlock but i don´t have an account of xiaomi.
when i use this command: fastboot flashing unlock_critical i receive this message: Command not support: the display is not enabled'
Somebody help me :crying:
Flash stock ROM with mi flash
I tried that but miflash show this message: Mismatching image and device. Only have a success message when i flash the wayne rom but ends on 1 second but doesn't install the system.
On htcmania says because the drivers are wrong but i reinstalled from the tutorial ones, google drivers, and miflash drivers and always says the same.
Now i trying with EMMC dongle program(cracked) and it seems like it´s installing the system, but since yesterday, it looks last forever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well that program does not did anything, i discover that when the phone is on fastboot mode and plug off the battery, miflash make a process success but it last 24s and don´t do anything, maybe that could be useful for something.
I don´t know what more to do with my phone.
Click to expand...
Click to collapse
If ur bootloader is unlocked try
Fastboot reboot edl
Now try to flash with mi flash in this mode
Note: your phone will look like it's turned off (black screen) in this mode
---------- Post added at 02:35 AM ---------- Previous post was at 02:29 AM ----------
I noticed that you where trying to flash Wayne images in the photo that u attached? Do u own a mi A2 or a 6x?
If you convert your mi A2 to 6x you cannot relock your bootloader
And make sure to delete system update folder and change some Dev conf file to flash miui on your android one device
That command (Fastboot reboot edl) doesn't work, when i send it i get this error: Device is already locked!
The only way my phone can be on edl mode is by Test points, and the miflash says that my phone have a locked bootloader if i try to flash the system.
What is the output of this command
Fastboot oem unlock
hv2002 said:
What is the output of this command
Fastboot oem unlock
Click to expand...
Click to collapse
Araxielfenix said:
Click to expand...
Click to collapse
https://youtu.be/ypDU78c4w_Y
Hello there
I think i did somethinh wrong while trying to install twrp. Now when it boots it stays stuck on twrp screen, i cant switch it off. If i try, it will boot again on twrp screen. But i can boot it on fastboot mode.
I tryed with adb commnds to reinstall twrp but it does not recocnize dhe device when the phone is in fastboot mode.
If i boot the phone on the stuck twrp screen it is recognized by adb but it does not executes any command.
Eventually i thought trying to clean flash the stock rom will fix everything and i can try again with a fresh start. But the mi flash gives error,; flashing is not allowed for critical partitions.
The bootloader is unlocked.
Your browser is not able to display this video.
Try flashing your original boot.img (that worked with your current ROM version) back to the device from Fastboot.
Andrologic said:
Try flashing your original boot.img (that worked with your current ROM version) back to the device from Fastboot.
Click to expand...
Click to collapse
Thnx for the suggestion. But as i said the phone does not respont to adb commands.
biqe said:
Thnx for the suggestion. But as i said the phone does not respont to adb commands.
Click to expand...
Click to collapse
Not adb. You need to be in bootloader mode with Fastboot access to be able to flash boot back. Power up the device in bootloader mode with the vol+power buttons and confirm that your device has Fastboot access (e.g 'fastboot devices' returns your device id). Flash your boot from there. If Fastboot access is impossible, it's a bigger issue but try that first...
Andrologic said:
Not adb. You need to be in bootloader mode with Fastboot access to be able to flash boot back. Power up the device in bootloader mode with the vol+power buttons and confirm that your device has Fastboot access (e.g 'fastboot devices' returns your device id). Flash your boot from there. If Fastboot access is impossible, it's a bigger issue but try that first...
Click to expand...
Click to collapse
When i try vol+power it boots on twrp and stays like that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update. It loks like using adb was the problem. But using the platform tools i could execute comands and i fixed the issue. The phone is clean and i could flash the stock rom with mi flash.
biqe said:
Update. It loks like using adb was the problem. But using the platform tools i could execute comands and i fixed the issue. The phone is clean and i could flash the stock rom with mi flash.
Click to expand...
Click to collapse
Hello, i have the same problem. Did you use only mi flash to resolve the issue?
Mi A2 does not have /recovery partition, a recovery is a part of the /boot image, and thus TWRP is not to be "flashed" into /boot (or absent /recovery), but can be "patched" into /boot installing appropriate .ZIP file in a temporarily booted TWRP (tip: search Guides).
This "revelation" could be found in many threads / guides in this forum - search could help you.
As well as "revelations" answering your question:
AndroidOne devices do not need any MiFlash (except for testpoint unbricking, tip: search Guides), if bootloader and critical partitions are unlocked, just normal fastboot.exe from latest Android platform-tools (tip: search in Guides).
Hy Guys,
i rly need your helps.
I Installed the Xioami.eu A12 Beta Rom (and used the windows_fastboot_first_install_with_data_format.bat).
The Script runs thorugh the installation process and after that my phone did a reboot.
And now it appears the screen with
"This device is locked,
This device is associated with an existing Mi Account. For security reasons, you need to enter password to verify the device"
but it seems that the touch screen is not working, so i can't select the network or move into the enter password field.
After seome seconds the phone reboots and ends up in the same screen.
1) Bootloader is unlocked
2) Enter Recovery is still possible (and via MiAssistant recognized by windows)
3) Enter Fastboot is possible but not reconized by windows anymore
but i dont know how i can now get my phone back to work ;-(
I hope someone can help my and let me know what i can do.
For the Final Solution i will pay 25€ as a little gift ;-)
//Edit: Ok i can now Enter Fastboot again (via MiAssistent an then "abd reboot fastboot") and its recognized in windows but when i try to reflash the A12 i got a lot of errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After this reflash, phone still stuck on the "This device is locked" and Touch still not working ;-(
//Edit: If i try to flash A11 via MiFlash i get the following error:
You might have fully bricked it, the initial problem you was just about entering you Xiaomi account password cause your device is protected by find me the xiaomi find device APp
try to recover with the venus engineering rom which was posted
1. Enter in fastboot mode.
2, reflash xiaomi eu 12.6 21.22.10 (and use the windows_fastboot_first_install_with_data_format.bat).
3, phone autostartup
4,first screen go to wireless, set
5.Back, enter yours passord an your xiaomi mi user.
Spegeli said:
Hy Guys,
i rly need your helps.
...
Click to expand...
Click to collapse
You can try two others things because apparently you have access to fastboot mode
1/ Flash lastest Stable Xiaomi .eu A11 from TWRP (Boot TWRP, format data, reboot TWRP, flash Xiaomi.eu)
2/ Flash AOSP ROM from LOS Recovery (but you must have a stable base A11 MIUI before)
and you don't have locked device prompt on the AOSP rom
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
Install the modded Xiaomi tool By Francesco Tescari
And Go for the bricked device flash , Voila
The same thing happened to My Mi 10 5G , i managed to unbrick it