Ok so, yesterday I hard-bricked my device. But I've unbricked it now, I don't understand why, but whenever my phone boots, it's just blank screen.
I used mtkclient and used the `plstage` command from it, it boots and I completed the miui setup, but I can't run that command EVERY TIME, how do I fix this? I cannot boot without that command.
It's blank screen if I don't use that command.
Might be some corrupted image ?
Try the built-in Xiaomi fastboot rom flasher of this tool in BROM mode:
[Tool] Android Utility Tool Version 106 - Auth Bypass MTK, Unlocking, Factory Reset and much more!
[Tool CREDITS]: Developer Mofadal El-Tayeb Android Utility Tool Version V106 Disbale Auth Dump Preloader Crash Preloader to Brom.... Extract Samsung ROM (MTK Devices Only) Extract Huawei Update (MTK) and so on Patch Xiaomi Qualcomm...
forum.xda-developers.com
Use latest version v109 => Password: mfdl
Code:
Main - [LIB]: ←[31mError: Couldn't detect partition: system_a
Available partitions:←[0m
Main - misc
Main - para
Main - countrycode
Main - expdb
Main - frp
Main - nvcfg
Main - nvdata
Main - vbmeta_a
Main - vbmeta_system_a
Main - vbmeta_vendor_a
Main - vbmeta_b
Main - vbmeta_system_b
Main - vbmeta_vendor_b
Main - metadata
Main - persist
Main - persistbak
Main - protect1
Main - protect2
Main - seccfg
Main - otp
Main - md1img_a
Main - spmfw_a
Main - pi_img_a
Main - dpm_a
Main - scp_a
Main - sspm_a
Main - mcupm_a
Main - gz_a
Main - lk_a
Main - boot_a
Main - vendor_boot_a
Main - dtbo_a
Main - tee_a
Main - sec1
Main - proinfo
Main - efuse
Main - nvram
Main - boot_para
Main - logo
Main - md1img_b
Main - spmfw_b
Main - pi_img_b
Main - dpm_b
Main - scp_b
Main - sspm_b
Main - mcupm_b
Main - gz_b
Main - lk_b
Main - boot_b
Main - vendor_boot_b
Main - dtbo_b
Main - tee_b
Main - devinfo
Main - gsort
Main - ffu
Main - rescue
Main - cust
Main - super
Main - userdata
Main - flashinfo
I can't boot anymore. this is what mtkclient shows when trying to flash system.img
I flashed Pixel Experience Boot Image, and now i'm in recovery, and now can access fastboot
this is what it shows when trying to erase preloader or system:
Code:
C:\Users\woozy\Documents\mtkclient-1.52>fastboot erase preloader
erasing 'preloader'...
FAILED (remote: Partition doesn't exist)
finished. total time: 0.012s
C:\Users\woozy\Documents\mtkclient-1.52>fastboot erase system
erasing 'system'...
FAILED (remote: Partition doesn't exist)
finished. total time: 0.012s
actually, tried erasing system_a and worked
Everything works, except the booting part, I must use python mtk plstage (mtkclient) command to boot it. I don't understand why, preloader and system partitions are fine.
Related
Hi friends,
The app recommended by BQ "MTK Tool Flash" (SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip) just didn't work for me on my Debian PC. There were always some excuses. So I tried some black command-line magic with fastboot and now I'm with a bricked device.
See ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 link I cannot post...
The good news is, I have installed the TWRP (twrp-3.1.1-0-freezerfhd.img) before I shot myself in the toe. So power + volume up gives me the comforting bluish screen of TWRP.
Question is, how can I bring the lovely device back to life? I wanted to flash official Android on it (which failed - 2.3.0_20170405-1553_bq_aquaris_m10_FHD_-FW.zip) and I'd like to complete that, but if it's a no go, I can go back to Ubuntu.
I have tried installing the image zip from twrp, but it said the image has invalid zip file format!
Thanks a lot for your help
Rob
failures
I've been struggling with this one. So I can switch to the bootloader mode and run fastboot commands. However, when I try to flash the system image I get some funny error:
Code:
sudo fastboot flash system ./system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
With the flash tool (after fixing all it's complaints) I'm stuck with a timeout on detecting the USB port (while fastboot works just fine)
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
And with TWRP as mentioned earlier:
Code:
Invalid zip file format
I read the stock rom can be adjusted somehow to allow TWRP to flash it but I'm quite like what...? Android kitchen doesn't list my device as supported.
progress
Aha! This got us further:
Code:
sudo fastboot flash system -u -S 1G ./system.img
Which means do not erase the partition upfront, and sparse the file at max 1 GB.
Code:
sudo fastboot flash userdata -u -S 1G ./userdata.img
sudo fastboot flash boot -u -S 1G ./boot.img
sudo fastboot reboot
Now device is "powered by ubuntu" and stuck there... not sure what's happening
S now I tried flashing some more exotic partitions and the device is completely dead. I hope BQ can help...
undead
Wow, so BQ contacted me right away with a hard reset procedure. The key bit of information I must have overlooked somewhere is that for the flash tool to detect the device, the device must be plugged in while it's off and while the tool is waiting. We're now "powered by android" and system is ready to use. Oh my... thanks BQ
I have XT1900-2 with unlocked bootloader and Havoc-OS 13022019 build installed. No root. Never flashed 'copy-partition.zip".
Initially when I flashed it, everything was alright, I can boot twrp (never flashed it) and switch the slot.
Now I want to flash newer build. 'fastboot devices' runs fine with the serial number output.
But I can't boot twrp,
Code:
$ fastboot boot twrp.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
fastboot log,
Code:
cmd: getvar:slot-count
cmd:
I can't switch the slot,
Code:
sudo fastboot --set-active='b'
(bootloader) slot-suffi: not found
error: Device does not support slots.
Bootloader shows "Baseband: <not found>".
But the baseband shows up on Settings; the OS runs fine, I have data, call and wifi.
Edit: partition list
Code:
$ ls /dev/block/platform/soc/c0c4000.sdhci/by-name
abl_a bluetooth_b cid cmnlib_b devinfo dto_a fsg_a hyp_b logfs misc modemst2 persist prov_b ssd system_b utags vendor_a
abl_b boot_a cmnlib64_a ddr dpo dto_b fsg_b keymaster_a logo_a modem_a msadp pmic_a rpm_a storsec_a tz_a utagsBackup vendor_b
apdp boot_b cmnlib64_b devcfg_a dsp_a frp hw keymaster_b logo_b modem_b oem_a pmic_b rpm_b storsec_b tz_b vbmeta_a xbl_a
bluetooth_a carrier cmnlib_a devcfg_b dsp_b fsc hyp_a kpan metadata modemst1 oem_b prov_a sp system_a userdata vbmeta_b xbl_b
I can't even restore to stock (using this guide) since all the fastboot commands fail. blankflash is not applicable since fastboot still can recognize the phone.
I ran all the commands (each command is repeated at least five times), remarkably none of the command is executed and everything is still intact.
Edit: Managed to restore to stock using Windows (I'm using Linux), except for oem which failed to flash due to exceeding partition size. The baseband is still "<not found>".
As stated in other threads, I have yet to break my phone to test this.
I still think starting from the blankflash and then flashing stock from the motorola program would be your best bet to restoring your phone.
Thanks. blankflash didn't work for me because I didn't specify the port number (default is 9008, judging from other threads). I managed to restock using Windows 7 and the latest fastboot (r28.0.1). It didn't work for the first reboot, so I flashed the Copy Partition . The baseband somehow came back on bootloader after a few reboots.
Anyhow, I think the issue could be due to corrupted /system. Yalp Store's ota.zip currently doesn't support /system/system, so I modified the script. I also wrote a script to install microG (without using NanoDroid). I probably messed up the scripts...
There was a script once made for my current device that didn't work.
Doing everything manually, step-by-step, worked though so that's the route I go when I can.
I just got a brand new phone straight out of the box and am having the same issue. Did you ever figure it out?
Edit: I got it to work using an older computer with USB 2.0... which is strange because I tried the 2.0 ports on my desktop also...
It would seem that for me Flashing the TWRP Recovery (or any other, tried Orangefox too) doesn't work. I would really appreciate some input on this.
Here's some info:
- Redmi 4
- MIUI 10.2 | Stable // 10.2.2.0(MBECNXM)
- Android version 6.0.1
- Android Security Patch level 2018-04-01
- Unlocked the Phone (Successfully)
- Booted into fastboot
- used "fastboot flash recovery <filename>.img" to flash the twrp image (also tried older versions of the twrp image; also tried the orange fox recovery image)
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot flash recovery twrp.img
Sending 'recovery' (36040 KB) OKAY [ 1.002s]
Writing 'recovery' OKAY [ 0.977s]
Finished. Total time: 2.046s
- I proceed to use "fastboot boot twrp.img"
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot boot twrp.img
Sending 'boot.img' (36040 KB) OKAY [ 1.001s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Now unto the errors / things I've tried:
- If I try to just use "fastboot reboot" -> it proceeds to eternally get stuck on the "mi.com" loading screen
- If I try to use the "standard" power off > Power + Vol Up -> The phone boots into the Chinese interface which is not TWRP (yellow big buttons, bottom button is blue) -> I change the language to english, hit "Recovery" and it yet again either stays stuck or boots into Mi 3.0 Recovery
I have tried all TWRP Santoni versions currently officially available on the official TWRP site.
All give me the same error if I try to boot the recovery direclty through fastboot as seen above: "(remote: dtb not found)"
can anyone please help me with this?
Flash latest stock ROM with fastboot first without re locking bootloader, boot into it, and then flash twrp 3.2.3-1 official from fastboot again, and then disconnect the phone and reboot into recovery with vol up + down + power button and ensure that you have downloaded lazyflasher into your phone storage, and after booting twrp, flash lazyflasher, clear cache and reboot system. Done!
Sorry, my English very bad. I have Mi A2 with bootloop. Bootloader locked. I tried to flash three different firmwares using MiFlash, but was getting one error. it 1st image.
Later it seems I changed my MiFlash version and got another error, this is the second image. What do these errors mean?
Me_gusta_98 said:
Sorry, my English very bad. I have Mi A2 with bootloop. Bootloader locked. I tried to flash three different firmwares using MiFlash, but was getting one error. it 1st image.
Later it seems I changed my MiFlash version and got another error, this is the second image. What do these errors mean?
Click to expand...
Click to collapse
Don't know what that means but 'ack' should refer to "android common kernels".
I found a few videos searching for "Android Ack count don't match". Maybe you could try their solutions / methods.
User699 said:
Don't know what that means but 'ack' should refer to "android common kernels".
I found a few videos searching for "Android Ack count don't match". Maybe you could try their solutions / methods.
Click to expand...
Click to collapse
I saw it, there Indians install the beta version of MiFlash and everything is fine. But the beta version does not work for me, it does not see the file "flash_all.bat"
Me_gusta_98 said:
I saw it, there Indians install the beta version of MiFlash and everything is fine. But the beta version does not work for me, it does not see the file "flash_all.bat"
Click to expand...
Click to collapse
Maybe try an older (beta) version. It could be a problem in the current release which didn't occur in prior releases.
I have the same problem with a brand new Mi A2
Stuck at the androidone bootlogo.
Entering fastboot works without problems.
Flashing results in this error: FAILED (remote: 'Error flashing partition : Write Protected')
No matter which slot is used.
Unlocking via fastboot tells me that everything is already unlocked.
Booting the twrp image from fastboot gets stuck at the twrp logo.
This also happens with the patched twrp_4pda version.
This [GUIDE] Flashing ROMs with TWRP black screen post seemed helpful and adb shell works.
But sending commands like twrp wipe cache results in:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Code:
fastboot --set-active=b
fastboot flash boot_b twrp.img
fastboot --set-active=a
fastboot flash boot_a twrp.img
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
fastboot boot twrp.img
adb shell
twrp wipe cache
Entering EDL mode via fastboot works without problems.
I installed the qualcomm 9008 drivers (windows 10 driver signature verification had to be disabled) and the phone in edl mode appears.
Downloaded the Mi A2 global fastboot rom
I tried all miflash versions (2015 to 2018 and beta) ... they had various bugs
XiaoMiFlash.Config --> rename to XiaoMiFlash.exe.Config
generate "Log" folder
place rom files inside miflash folder ... avoid any long/special path names
In the end they all start flashing and fail with "no Binary dump" or "ACK count don't match".
I also tried a different PC, different USB cable and fastboot on linux.
Is there anything else that could be done or is time to consider a hardware failure (broken emmc ...?) ?
#### update ###
fastboot format userdata
.... works and writes something without error
fastboot format cache / fastboot erase cache
... FAILED (remote: 'Error flashing partition : Write Protected')
I was able to get into stock recovery (hold VolUp+Power --> "no command" --> hold again).
wipe data / factory reset --> getting stuck forever on "wiping data..." screen
Apply Update from ADB --> adb sideload miui.zip also gets stuck forever
calling fastboot -w results in:
Spoiler: error code
Erasing 'userdata' OKAY [ 0.081s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4652023 4k blocks and 1163264 inodes
Filesystem UUID: 969bf7be-a1e1-11ec-9ff1-f15f995f2a7c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (180 KB) OKAY [ 0.011s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'cache' OKAY [ 0.002s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 96ab61ae-a1e1-11ec-aed9-d92ea3a1e9cc
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed
Hi, I found a tool that makes flashing payload.bin/full OTA zips on root/ unlocked devices easier on dynamic partition devices.
Github: Fastboot Enhance
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Credits: https://github.com/libxzr, https://forum.xda-developers.com/m/xzr467706992.7594064/
rockstar1997 said:
Hi, I found a tool that makes flashing payload.bin/full OTA zips on root/ unlocked devices easier on dynamic partition devices.
Github: Fastboot Enhance
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Credits: https://github.com/libxzr, https://forum.xda-developers.com/m/xzr467706992.7594064/
Click to expand...
Click to collapse
"..on dynamic partition devices." = all versions (Global, EEA, India) of OnePlus Nord CE 5G (and more..)