Greetings, my lenovo a526 is stuck at lenovo logo.
I already tried wiping cache in stock recovery, but in wipe data/factory reset it says default data flag fail something like that.
Reboot, im still stuck
Then i tried flashing stock rom using spft it was successful yet still stuck at logo.
So I thought i should flash twrp or cwm recovery to install custom rom in sd card
I used adb fastboot. To flash those recovery because my stock recovery doesn't have "install zip in sdcard"
In fastboot,
My device is detected when i execute
Fastboot devices
"mt6582_phone --- device"
I cannot flash cwm or twrp directly because when i do it says remote partition does not support flash.
I believe i need to unlock bootloader first.
So i execute
Fastboot oem unlock
The result is 3 dots loading like forever
Now im in a dead end, i know i have to confirm it in my device but it has no display only logo.
Please, i need help. Is there any way to execute fastboot oem unlock without confirming in my device?
C'mon someone here had experience using fastboot. Any ideas guys?
Hello everybody!
The last day my phone got stuck on bootloader screen. It just wouldn't boot the OS.
So I tried to fix that by flashing other rom. I have unlocked it trough MiUnlock.
Flashed in fastboot TWRP(rosy) recovery. It could boot TWRP but after a reboot, would launch MiRecovery.
After that the Android didnt start no more. After a new flash of TWRP I was able to enter recovery. I tried to flash a custom rom. After that the VOLUME UP + POWER wouldnt launch recovery no more (Also VOLUME DOWN+UP+POWER buttons, wont boot the Recovery)
Now i found an EDL mode to flash rom through XiaoMiFlash. Did it, Made the steps from tutorials. That, has changed the device to COM10 in MiFlash which let me try different official roms, and i always get the same error message: cannot receive hello packet, MiFlash is trying to reset status!
Also tried too flash a recovery img.
Tried everything i found on that, nothing worked to get those packets...
My only hope was to fastboot flash recovery TWRP or MiRecovery. And then flash new rom to fix my phone.
Tried many version of Twrp, but no success to actually flash.
I have tried removing recovery via adb and flashing another. Logs shows success but no effect on phone.
Still can't acces recovery mode on my phone.
Bootloop stuck. Shows MI logo and that its Unlocked.
Doesnt work flashing via fastboot - TWRP or MiRecovery images.
My phone is bricked for a week now. Please share a solution if you got one.
SOLVED
Good news. finally flashed chinese version through miflash tool.
had to rename some files from rom.
Flashed through BOOTLOADER.
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
Hello.
I flashed a custom rom (LineageOS) and Magisk on my Redmi 7 and rebooted to system, but I forgot to flash gapps. Then I got back to recovery mode and TWRP won't go to main menu, any tips? It is safe to fastboot flash TWRP again?
Hi all,
Please help me, I cant boot into TWRP
Before that, I upgraded (xiaomi.eu) from MIUI 12 to MIUI 14 via fastboot (windows_fastboot_first_install_with_data_format)
Everything is fine, but when I try to boot into TWRP recovery, it keeps flashing TWRP logo
I tried to flash multiple versions of TWRP via fastboot also still the same
Thank you
here are some ways:
1 - try installing default recovery and boot into it then install twrp again.
2 - try installing twrp as boot and recovery both then reboot to boot
may work but take backups 1st