Mi A1 restart bootloop - Xiaomi Mi A1 Questions & Answers

pleease hellp.. my xiaomi mia1 bootloop.. restart everytime.. instaled twrp 3.2.1 mohan cm.. but internal show 0 MB.. cant change current slot.. cant repair or change file system..
flash edl via miflash show success but still bootloop and restarting.. can someone tell me how to fix it.. tks before..

Is your bootloader unlocked?

I faced the same problem during flashing custom Rom. As I have no pc, I tried to solve it with android and Alhamdulillah fixed it. Before sharing My experience, let me clear u that, I was flashing rom with that Twrp by mohan. It failed. I was trying again and again and my phone was bricked. I flashed it with pc and stucked in the bootloop sm like u. So I recommend you to install Orangefox recovery instead of twrp.
Firstly, turn on the fastboot mode. Connect your phone to another Android with otg and install Bugjaeger app from playstore on another phone. Open it and go to command writing page.
View attachment 5284423
Write: 'fastboot devices' to check if it is connected to mi a1.
Then type: fastboot flash boot<space>xyx.img
(after space click on attach file and attatch the img file of Orangefox img. After flashing successfully, type again: 'fastboot boot<space> attach same img file.
then your phone should boot into Orangefox recovery. Then install any official or unofficial ROM.

Related

Help with bricked xiaomi redmi 2 prime

Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Stop experimenting.
Does fastboot work? Do a full flash with miflash(erasing all storage)(firmware should be of your model itself)
If fastboot doesnt work,try putting in the charger with battery in,if there is any vibration,you have a chance of reviving your r2
#fingerscrossed
Ezio95 said:
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Click to expand...
Click to collapse
Yup actually download the latest version of miui fastboot files..paste them in the fastboot folder... Dont bother erasing you phn again(as it does erase at the time of writing new files...)And most importantly flashing only 3 files is more than enough. Flash them in the order boot.img, system.img, recovery.img and thats it. If your problem is actually not booting into fastboot then....press the volume down button and insert your usb while keeping it pressed.
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Ezio95 said:
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Click to expand...
Click to collapse
If you can get the fastboot to work, you can flash recovery on your phone for good or temporarily to flash zips.
How to do it?
1.Get into fastboot on phone
2.Install minimal adb and fastboot in your computer
3.Run adb and install drivers
4.Connect your phone which should be in fastboot to computer
5.Check for devices by using "fastboot devices", if a device is listed, proceed
6.Download a custom recovery, rename the recovery img to something easy than using the full name and copy the img into the folder where minimal adb and fastboot is installed
7.Type in "fastboot flash recovery <name you gave to recovery img>.img" (img for the image format) to flash recovery permanently
OR
7.Type in "fastboot boot <recovery name>.img" to use it temporarily, this method will erase the recovery on reboot so flash whatever you want before rebooting if you're following this method.
8.Flash in your ROM zip, try stock and custom ROMs, see if you can get your phone to work
GOOD LUCK
Same error with my yureka plus (error "remote: failed to write partition"). I'm planning to buy redmi 2 prime.. . Scared if this will happen to redmi 2 prime

Real Me 2 Pro Boot / Recovery Image have been damaged

today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
Hi, how about your phone? is your problem have solved?
i have same problem like you. and i want to know about to solve it
thank you
hi, my problem a bit different with recovery.
i have stock recovery with unlocked bootloader. im with coloros 5.2 and can not install coloros 6 update. stock recovery cant find update file in phone storage, wifi doesnt work and starting update from os, returns update failed after one reboot. and suggestion?
vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
I face the same issue. Flashed twrp. Then flashed boot+magisk+patched img file. Now the phone halts at the fastboot mode and is not booting up. It also unable to be power off. plz help. The model is Realme2 RMX 1805
Dont worry you do have a unlocked device so u need a pc to do that download system.img, vendor.img for your device and just open cmd then type this fastboot flash system system.img then fastboot flash vendor vendor.img and reboot it second method if you dont have an pc not sure that it will work you need a second device with otg support download bugjaeger app from playstore and use the same commands which i mention in pc method

How do i root my Mi 9T Global Version?

Hey Guys,
Today I tried to root my new MI 9T. Since my phone is not the Pro version I had problems to find a guide.
I then found a guide and there as described the boot loader opened and then tried via Fastboot to flash on TWRP.
I get no error message so I thought everything would be successful. I then tried the mobile with "fastboot boot recovery.img" to restart.
From there I was stuck in the bootloop. I was able to successfully save the Mi 9T by editing the complete system with MiFlash.
The phone is back to normal, but the bootloader is still open. Can someone please give me a description of how I can root the phone successfully?
I would like to use Magisk so it would be nice if someone could help me flash recovery and root the phone without flashing the OS again. (Softbrick)
Hello
It's nice if you already opened/unlocked the bootloader of the phone.
You got a bootloop after flashing TWRP, it generally means you flashed an incompatible TWRP for your MIUI version/phone model.
Download "Latest stable" Magisk version => https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip
Copy this "zip" file on the root of your phone.
See this topic to check and download TWRP => https://forum.xda-developers.com/mi-9t/how-to/twrp-versions-xiaomi-mi-9t-t3955946
After flashing a correct TWRP image => "fastboot flash recovery <twrp_file_name>.img", don't do "fastboot boot recovery.img" but instead do:
Keep pressing "Vol+" button on your phone and write "fastboot reboot", wait until TWRP is launched before releasing "Vol+".
Use your PIN/Password code used for unlock your phone to decrypt data => always keep system "read-only" => Install => Flash "Magisk-v19.3.img" => Reboot.
Voilà!

mi 9 t anti roll back to 1 and fastboot loop

Hi, I've been trying to get out of this situation for days.
My mi 9t went into boot loop after having wipe a twrp wipe.
Now if I try to flash a ROM it returns the antiroolback error check because my arb is 1 and the rom I find is 0.
I can't even install the twrp anymore, the installation process with fastboot is successful but it always restarts in fastboot and not in recovery.
Can someone help me?
m.92.grosso said:
Hi, I've been trying to get out of this situation for days.
My mi 9t went into boot loop after having wipe a twrp wipe.
Now if I try to flash a ROM it returns the antiroolback error check because my arb is 1 and the rom I find is 0.
I can't even install the twrp anymore, the installation process with fastboot is successful but it always restarts in fastboot and not in recovery.
Can someone help me?
Click to expand...
Click to collapse
Download this TWRP'S:
1. CHINESE TWRP - https://mega.nz/#!dVYX3SzT!CN2lTDmF3xmMlEw-LbU9xDWcFFmFdjcB_ZR1vnk_Gas
2. RUSSIAN TWRP - https://mega.nz/#!AcAlVITI!p15vuiNoSDxhViGzW1PhZwuAI9hMi3_k9FFzYiiLhoM
After installation one of these two (your choice ) TWRP'S, you can boot to your rom or:
1. FORMAT /data partition (NEVER wipe System or Persist!)
2. Copy ROM to the internal storage,
3. Install ROM,
4. Reboot,
5. Done!!!
Download Fastboot Rom
Extract
Reboot phone to fastboot
Open cmd
Go Inside folder
Type fastboot flash system system.img
Fastboot Flash Recovery recovery.img
Done

Fastboot Failed (data transfer failure(unknown error)

Hello and thanks for inteterest to help. (My phone Redmi 2 Prime)
So to the point, i have my phone installed custom ROM. And today when i try to reset factory, it stuck in the MI Logo (Show and then turned off). So i forgot to flashing the twrp again last time, so i left it without any recovery. The only way is repairing it with Fastboot and installing TWRP. So i start installing all driver and flashing. But, when i want to flash twrp to my phone, it keep showing me this
fastboot flash recovery recovery.img
flashing 'recovery.img'
FAILED (Data Transfer Failure(unknown error)
DONE! 5.8 sec
But it doesnt installing any recovery. I have installing MiFlash driver. Is there any driver that i should install again? Or anything that i can do? Also my PC doesnt read my phone storage at all, it doesnt show in the explorer, but can read "my phone" and my phone model. And I'm using USB 2.0. I also have try USB 3.0 but it doesnt work too.
Any help would be appreciated. Sorry for the long post, eh?
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
dabakale said:
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
Click to expand...
Click to collapse
Thank you for replying
So i've try it, but why its stuck at 'downloading boot.img' for 2 hours?
Can i download the boot.img manually? If yes, what should i download?
Can you share a photo of error.
Or you can try miflash to flash stock rom. Then you try to flash twrp. I suspect there would be something wrong with your recovery partition.(i also had similar problem while flashing different roms.)
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Egalito Rieans said:
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Click to expand...
Click to collapse
Try this method
[No More Errors] [Fastboot Rom Flashing] [Direct Method]
Hi all, Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error ;). I tried many things but no luck. Then i followed direct method and that worked...
forum.xda-developers.com

Categories

Resources