Hi. I am asking for help because I have tried everything. Most of the times I enjoy solving this kind of problems and I learn a lot of things during the journey but in this case it is becoming very frustrating.
The story begins when I downgrade tissot, using the MiFlash tool and the official firmware 7.8.23_7.1. The system booted, but SIM card was not recognized and after about 15 seconds the system reboots. Always
Then I flashed V9.6.4.0.ODHMIFE_20180712.0000.00_8.0_735823083f. F. Same issue. This one was funny because for some reason the option "allow oem unlock" was reset to 0. So I had to finish the initial configuration, enable developer menu, and allow oem unlock in just 15 seconds
Then I went back to V10.0.24.0.PDHMIXM_9.0_20200810.0000.00_9.0_49f16fd30d, and the system stuck booting at android Logo. What I already tried:
reflash with diferent options, diferent versions of Mi Flash
Locking, unlocking bootloader
Factory reset from recovery menu, from TWRP, fastboot erase data / format userdata
Flash using fastboot oem EDL with broadcom drivers via COM port
Changing USB ports, cables
Powering off the phone at night, putting it into the status when only the battery and charging logo is visible
AIO tools from the forum
Then I tried a different path: installed TWRP and flashed Lineage OS for tissot. Everything OK until it got stuck when loading (Lineage OS animation logo stayed for more than 1 hour)
Then I flashed again stock using the new tool Mi Flash Pro, enabling advanced options for reformating, wiping, everything I could throw to the device. Then I did a factory reset from stock Recovery. And even tried doing it again from slot b. Nothing worked: it still stuck at android one screen, seems it is doing something but I know it is halted at some point
Finally I tried Pixel Experience ROM and ... the system stuck at pixel logo animation when loading
I had the idea that you could recover any android smartphone by just flashing stock with the right drivers in recovery mode. What am I missing? Are there any logs which give me clues about the reason why the system does not finish the start?
Thanks to all the community for your help. I have read almost every guide and I have learned a lot. But seems not enough
Solved. This is how to do it
buy a second hand Pixel 2XL for $80
take your Xiaomi MI A1 to the closest recycle center
The good old Pixel now is unlocked, rooted and patched without any issue. Everything working now
Related
I am having a problem with my OnePlus two device. I used qcom download tool on my device, because my OnePlus two didn't want to reset. So after qcom download tool was done My phone rebooted and stayed in a boot logo. I tried It again and again and so on. After doing that a lot over and over I thought It could fix it, I got the same output over and over. My phone got the OS completely wiped and the recovery. The only thing that works is fastboot mode. I get now is the boot loop. I've tried everything and nothing has helped.
I have tried to fix it the hard way but my OEM is locked so I have no luck.
• (fastboot continue) I've tried it I got nothing out of it.
does anyone have a solution to fix this problem.
fd
Hello,
You bricked your phone. Use this guidr step by step, it works 100%
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Try boot with recovery image (fastboot > boot recovery.img), I got unlocked boot loader even after a reset (using qcom tool).
Hi guys,
some days ago I woke up to my Xiaomi Mi A1 constantly rebooting (e.g. boot screen with the MI logo appears, gets brighter, android one logo appears, then the animation gets stuck and shortly after the device reboots). USB debugging was enabled, otherwise no changes to the system had been made prior to the bootlooping, e.g. no root, bootloader still locked, etc.
What I tried so far:
1. Factory reset via stock recovery -> No change
2. Started fastboot, unlocked the bootloader, booted TWRP and wiped data/cache, rebooted into fastboot and reinstalled latest official stock ROM (tissot_images_V10.0.10.0.PDHMIXM_20190613), which had been running on the device via OTA for about two weeks before the incident -> No change
3. Repeated step 2 with several older Stock ROMs (10.0.9 and 10.0.6) -> No change
4. Tried to flash various stock and custom ROMs via adb sideload and TWRP's install feature -> all fail as soon as the first of system_{a,b} partitions is supposed to be flashed
5. Tried to downgrade from 9.0 to 8.0/8.1 using this guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624 -> No change
6. Ran fsck on Data and System partitions -> No errors found
7. Tried reinstalling current and old stock version anyway -> still no change
So I'm left with a device that's booting again and again and always freezing during the boot animation and I can't think of anything else I could try. Does anyone of you have an idea what I could try?
Thanks!
Same situation here....i was also latest pie,and same thing happened with me.but you are lucky you can unlock bootloader and your stock recovery is still there but mine is gone.
Totally hopeless. Waiting for some dev come like messenger of god and help us out from this ****ty problem.???
Hi all,
I unlocked bootloader and tried several custom ROMs. Then I came back to ColorOs 5 version A.15 by converting ozip to zip and flashing from TWRP (twrp-3.4.0-20200610-RMX1801.img) but then I made a great mistake. Without upgrading the stock ROM, I directly wiped 5 and flashed PixelExperience android 10. Upon reboot after a momentary "Realme" splash screen the phone turned off. It can't boot or bootloop, it can't boot to recovery or even bootloader. The only time the screen ever shows a momentary splash screen of Realme is when I long press and release power, thereafter pressing power+volume up. Otherwise it looks dead. The PC can't detect any adb or fastboot interface, only the interface as in attached picture is detected. I think it is EDL mode. At this pandemic situation it's very difficult to access service center, and even if I can, they'll probably flash Realme UI, thereby making bootloader unlock impossible. The most pathetic situation is that I have the ofp file version A.17 for EDL flashing but no virus-free and authentication-free tool to do so. After searching for hours I am asking for your help, if there is any.
EDIT: Nevermind, problem solved by trying different key combinations.
Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com
Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.