Hello to everyone. I have problem with Mi Max 2, what i gave my mom last year. Device was bootloader unlocked and flashed with custom rom HAVOC , idk right version, some build of 2019. It worked for year without problem, but last night my mom was playing some games on phone, and it freeze. She didnt know what to do, so she left phone frozen untill battery drains and shut down. Then this morning she come to me with bootlop on phone, it comes to the havoc logo and just stay there. So i thought it isnt big deal, but when i try to boot in recovery mode, twrp does same thing. It freeze on startup logo and just stays there. TWRP is 3.2.3-0 version.
There comes more issues. I connect phone to PC, it doesnt see him. Nor in bootlop, fastboot, only in frozen recovery, and sees him only like universal USB in Device Manager, still dont shows anything in My PC.
I downloaded a lot of usb drivers for mi max 2, even installed them manually but there is no changes. In cmd, it recongnizes phone only when it is in bootlop in recovery mode, and only in that situation it shows on command /adb devices - the phone, when i try to to type command /adb reboot fastboot, cmd freezes and do nothing, phone isnt booting in fastboot. When i go in fastboot manually, power + vol down, it doesnt recongnises the phone, on command /adb devices now there is nothing, and even over that if i try to /adb flash recovery, it just says waiting for any device.
So theres my problem - i cant boot in system, i cant boot in twrp recovery, pc and platform tool doesnt sees my phone when it is in fastboot so i cant flash other twrp image. Is there any solution? can anyone tell me what to do, i rooted phones since like S2 in 2012 and flashed so many roms, but this situation i never had. I can understand that OS crashed down, but why TWRP trolls and cant be booted in...
Any solutions are welcome, phone is unusable like this.
P.S. phone didnt have any hardware damages, ever.
I don't have a solution and I only wish the best for you and your mom. How cool to have a mom running Havoc! I sure don't know everything so I could be wrong, but sometimes, rarely, phones break. I hope that's not the case here and don't give up yet, but I've been doing this a long time too (since S5) and what you've got there sounds bad. Your mom sounds badass and if her phone is broken, please get her something nice. A Moto G Stylus might be perfect. We've got havoc, and a flawless RR Q. She certainly deserves something nice and, if you're in America, Metro is giving them away free if you bring your number and switch. Best phone I ever had. Even better than oneplus 5. Good luck, Sir.
Press power off + volume down mean go to fastboot.
download orange fox recovery.zip and extract .img file
now connect your phone to pc and use command
fastboot boot extract_boot_image_name.img.
wait to boot
now flashed orange fox recovery.zip from recovery.
Okay done.
Download any rom for mi max 2 in xda rom section android 9 and android 10 based and
simply install rom...
Related
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
Hi there.
I've had a Mi A2 for a few month (January) and really like it. It's been great up til yesterday, when I tried to get it out my pocket and was greeted with a recovery-mode looking menu, telling me it couldn't boot and that files might be corrupt, etc. I had the option to either factory reset or try to reboot (shown with Try Again). I kept trying the Try Again option, and it eventually politely told me to f*ck off, and decided to just boot to the Android One splash screen. I'm able to get into Fastboot, but when I open cmd on my PC and try to use Fastboot, it'll say permission denied for most things other than a reboot, and ADB just won't recognise the phone - USB Debugging was never enabled. I've tried the volume up and power button, and it just reboots the phone again and again.
Help!
Thanks in advance.
- Taylor
tjpbrewer said:
Hi there.
I've had a Mi A2 for a few month (January) and really like it. It's been great up til yesterday, when I tried to get it out my pocket and was greeted with a recovery-mode looking menu, telling me it couldn't boot and that files might be corrupt, etc. I had the option to either factory reset or try to reboot (shown with Try Again). I kept trying the Try Again option, and it eventually politely told me to f*ck off, and decided to just boot to the Android One splash screen. I'm able to get into Fastboot, but when I open cmd on my PC and try to use Fastboot, it'll say permission denied for most things other than a reboot, and ADB just won't recognise the phone - USB Debugging was never enabled. I've tried the volume up and power button, and it just reboots the phone again and again.
Help!
Thanks in advance.
- Taylor
Click to expand...
Click to collapse
Mi A2,TWRP gone,Fastboot doesn't detect device
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the...
forum.xda-developers.com
Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.
I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode
How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )
No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom
Yesterday I unlocked my phone with the official Xiaomi unlock tool, Then it wiped everything, after setting my phone up, I flashed TWRP (not for my device but for redmi k20, I thought 9T and K20 is the same) and now I'm stuck on fastboot, I tried power button + volume buttons but still stuck on fastboot, I tried adb but still stuck, I tried Reiboot for Android but still stuck. So I used XiaoMiTool V2 (unofficial) and selected 'my device is bricked' then it asked me to select what device am I using, I selected k20 bc I thought it's the same with redmi power, after downloading a rom for an hour, it tries to install but fails because it detects that it's not k20, so I closed it and rebooted my device, now my device only shows the charging battery icon, can't boot into fastboot, can't boot into anything, PC can't detect my phone including adb. Please help me (for free), I really need your help. Thanks!
Your mistake was booting a wrong twrp and then a wrong fastboot rom. You could have saved your device when it was in fastboot mod by flashing an official fastboot rom for your device. But now your device seems hopeless. I think you have no option but to send it to a service center.
In this Case, buy only from Trusted Places! Or Learn how to Flash properly.
If the bootloader is unlocked...
Flash vbmeta.img
Then flash the suitable recovery for 9 power... It might boot to recovery then
Hey, dear community,
First of all: I'm using Linux. The Version of Fastboot is 33.0.3p1-android-tools. The device I thought I'm experienced enough to install Lineage OS on is the Asus Zenfone 8. Yes, I asked google - for hours. And I think I am really ****ed now.
Cause the Smartphone (Asus Zenfone 8) was not cheap. And it does not boot anymore. I don't get in Recovery mode anymore. And I'm not able to connect via Fastboot anymore.
But let's start at the beginning.
I was pissed, cause my smartphone forced me to use google. Even if I skipped the Google-Part in the setup, it forced me to agree to send Google information. And I read it. They (quote: may) send Google **a lot** of data. Data I don't want to share - and I don't need to share IMHO! I didn't like to use such a intransparent Device anyway - but this convinced me to try this thing named LineageOS.
I thought about myself I am not a bloody beginner. I mean, I use Linux as my daily driver - for years. And my phone (Asus Zenfone 8) was in the list of supported devices - so I had to try it. I thought if I just install these tools, adb and fastboot, and do these things in the wiki carefully, step by step, what could happen?
And it worked. It worked to unlock device, to connect via adb, to connect via fastboot. It worked to flash the vendor_boot image, It worked to flash the recovery image. But then, just before I wanted to start with the "Installing LineageOS"-part, and therefore boot into recovery mode - it didn't work. I was stuck in the bootloader. I am. still.
There are the options "START", "Restart bootloader", "Recovery mode" and "Power off". No matter what I try to enter, the device restarts (at least it looks like) - It shows "Powered by android", and then the bootmenu again. And again. And again.
When fastboot was still connected, I tried to flash the images again. I even tried to boot directly into the recovery image using `fastboot boot image.img`. But it did not work. And then, the device even stopped showing up when I ran `fastboot devices` - it disconnected.
"Power off" is the only option, wich still appears to work (when not plugged in).
What should I do? Is it even still possible to do something? Please help me.
PS: It would be nice if you tell me, wether the tools or guides you recommend to me work on Linux, in a Windows VM or only Windows Bare Metal. I will do everything to bring my phone back, but it safes a lot of time, not to try using a tool in Windows VM if it only works bare metal anyway.
May be this thread could help you
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Schaukelstuhl said:
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Click to expand...
Click to collapse
I had the same problem. Only bootloader with no device showing with "fastboot devices".
Luckily I tried another cable. An Apple USB C cable behind a hub (screen) got fastboot working. Then I flashed android 13 beta.
And I am sure the other cable worked before with ADB and fastboot.
Try other cables and USB ports... Good luck!