I used SP Flash Tool to update the ROM of my Umi Iron (deselected preloader, as advised), it stopped at 18%, gave an error and since then, my phone is in a bootloop. Can only get to stock Recovery (the android on its back). After a while in recovery, the phone reboots automatically, showing the Umi symbol for a few seconds, rebooting again back to recovery...
Fastboot and adb don't seem to find the device in this state. Installed the MT65x3 USB VCOM drivers, anything else I need?
Anyway to enter the bootloader or use adb/fastboot in any way? Sure hope I'm not completely screwed...
Related
Hi there guys!
My Xiaomi Hongmi S1 couldn't pass the boot phase after me trying to install Xposed. Then, the software Mi Phone Manager tried to recover the system files with the phone in fastboot (in this phase I still could enter fastboot and recovery) - somewhere along this process I had to leave and, when I came back, I had an error message in the software and the phone was turned off. After this I could not turn the phone on anymore, not even into fastboot or recovery.
MiFlash detects the phone even like this, but is unable to flash things into it.
PLEASE, HELP ME!
Someone?
Go in fastboot to pc
(you probably see anything on your phone)
On PC you can see if you are in fastboot by
Klicking on Refresh button on MiFlash you will see that you are connected
And Flash stock rom
See On thread (1)
(Also See MiFlash Picture from Thread)
Link: forum.xda-developers.com/showthread.php?p=53594673#post53594673
If that fails, your phone is probably broken.
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
So, I have an XT1723, a Moto C Plus. Following @shr!pad's guide, I was able to install TWRP on it, and flash SuperSU with the SYSTEMLESS=true modifier in /data/.supersu...
...however, the phone now will not go past the bootloader; it hangs indefinitely.
So I tried sideloading the LineageOS 14.1 ROM from here over ADB while in TWRP. It goes to the booting screen, the one with the blue arch and the bubbles travelling along it...and it stayed there for 8 hours overnight. Still doing it this morning. I then tried the 15.1 ROM; same result. Flashing via ADB Sideload mode led to the same problem. Magisk didn't help either.
Therefore, I decided to go back to stock rom. I found a stock ROM archive, which had SP Flash Tool and a Scatter file for the entire memory map of the device. This worked when I flashed TWRP...but now, I get BROM (2004) errors, no matter which computer and which USB port I use!
Bhai, did I break my phone forever? How do I fix this?
I flashed a wrong TWRP recovery on my Nokia 1 (a one from a Huawei P10 Lite). After that, i rebooted reinserting the battery, it showed android logo + "orange state", 10secs of blackscreen, and bootloop "forever".
I tried to get into bootloader mode via adb at reset
Code:
fastboot reboot bootloader
, but it doesn't work ("waiting for any devices"). Note that i flashed the wrong recovery successfully via adb, and previously i had a correct recovery flashed with adb too.
Flashing the TA 1056 stock rom via OST didn't work either; OST doesn't detect the phone (probably because i can't get into bootloader mode).
I tried with SP Flash Tool too, flashing the TA 1056 MT6737M firmware, but CHIP TYPE NOT match, scatterChipType 143, targetChipType 160. In the scatter file (i don't know why), i changed "platform: MT6752" to "platform MT6737M" and holding down both volume buttons till the end, i could flash the complete firmware.
Then, i reset reinserting the battery and obtain the ethernal bootloop with a blackscreen; the phone vibrates every 10secs until i remove the battery (no logos show up).
I can't do anymore; i can reflash with SP Flash Tool, but it's the same.
Please, help me
*PD: i flashed via SP Flash Tool with "Format All + Download" option; can it be a problem?
Man... I am right now where you were.
Same error. Did you find any way out?
*sigh*
Hey OP, you still looking to troubleshoot? I might be able to help
Hi, I beg your help. Well what happened is,
I was on CORVUS OS, then I thought of rolling back to stock rom. So after flashing "laurel_sprout_global_images_V12.0.21.0.RFQMIXM_11.0" using Mi Flash tool (clean and unlock), My phone said to me "This device has been destroyed". So I thought I might have flashed a wrong version. So I again flashed "Xiaomi_Mi_A3_V10.3.4.0.PFQMIXM_20190815.0000.00_Global_9.0_XFT" using Mi flash tool. But this time, android one logo showed up and did'nt proceed. Luckily I could access to fastboot mode. But after doing this flashing few more times, My phone blacked out completely. Things I have done so far:
1. Tried flashing again using Mi flash tool. The device manager says that the "QDloader 9008" is connected properly, but the flash tool is saying "cannot receive hello packet" and eventually fails the proccess.
2. Tried volume button and plugin combination. Nothing happened.
3. Download QFIL software. But it's not detecting any device.
4. Tried switching USB port
Please save me. I am going through a disaster. and it's my primary driver T_T
try to disconnect the battery, and plug usb
Try flashing using Paltform-Tools instead of Mi Flash Tool. See https://forum.xda-developers.com/t/slot-a-is-destroyed.4399965/ for links to instructions.
Do not take the back off your phone. Seriously, shell out the ten bucks for the deep flash cable. You need to get to EDL. Here are a couple of methods, depending on what you want:
Repackaged A11 stock here: https://c.mi.com/thread-3527044-1-0.html
CC9e Conversion here: https://forum.xda-developers.com/t/miui-12-port-10-miui-12-for-mi-a3-stable-weekly-rom.4016457/
Note: If you want to use QFIL, make sure you're using the latest version with QPST. Save yourself the time and install it system wide. https://qpsttool.com/qpst-tool-v2-7-104