After downgrading on A8 that happend... Tried many firmwares using edl port and fastboot. Also tried 8317.
Related
Hello guys,
I am new to xda and i joined xda today. I have a samsung galaxy note 4 (SM-N910G) and it is stuck in boot loop for 4 days and i tried everything from flashing stock rom through odin to using smart switch but bad luck nothing is happening. I also tried flashing the pit file but still its stuck in the boot loop. I don't know what happened to it, i also tried flashing custom recovery but some times it works some times it dosen't and i tried formatting it through twrp but nothing is happening i also tried to format it using adb but still nothing is happening. I have tried almost everything but its still stuck on boot loop. Please help!!!!!
It was running= lineage os
ood morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
It has been almost 15 minutes and my device won't boot up for the first boot. Is it too late yet? I tried to enter Recovery and Fastboot mode, but none of them work.
Help pls
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
Hi,
I have a Samsung J5 Prime (SG570M) that is stuck in download mode. I flashed the stock rom with Odin (both last version) and when the flashing ends, it says 'successful' in Odin, but when the phone reboots it doesn't boot up, the screen remains black. The samsung logo doesn't even appear. Any suggestion what could it be or what should I do? I have done this a few times and followed all steps, and already tried changing PC, USB port and cables. I don't know what else to do or what I'm doing wrong.
Any help would be awesome, thanks in advance!
Are you able to enter recovery mode and wipe the cache?
Thanks again for answering
No, I'm not able to enter recovery neither. Tried every possible button combination :/