[ROM] Mi 6 stuck in fastboot - General Questions and Answers

Please help me I screwed up! I tried flashing from Global Beta Back to Stable beta (ROM V10.4.1.0.PCAMIXM), I got bootloader unlocked and after a restart, I forgot to turn on USB Debugging, and when I flashed it I've got an error at the end (failed to check sparse crc). The thing is i thing I've chosen flash and lock and my bootloader might be locked again because every time I try to flash again I get echo Missmatching image and device and it's flashing forever. I tried to unlock it again but i get a fail verifying the device at 50%. So now I am stuck in fastboot, I can't get the phone to recovery mode. Is there any fix? Please help me I am not that not tech-savvy.

I guess bootloader is not locked!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s

try
Code:
fastboot boot "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.3.1-2-sagit.img"
and install Universal DM-Verity, ForceEncrypt, Disk Quota Disablers

Related

[Completed] [Q] Fastboot hangs and does nothing

My phone is a Vodafone Smart 4 Turbo which a rebranded Coolpad 8865U.
I am trying to root it using the ro.secure=0 methods as all the other rooting exploits failed.
Fastboot seems to detect my phone well enough. I can run this command for example:
Code:
fastboot oem device-info -i 0x1ebf
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
However if I try to flash recovery it hangs at
Code:
writing 'recovery'...
and if I try to boot from both and original or modified boot.img it hangs at
Code:
booting...
And if I try to erase something it hangs aswell.
Any ideas of what it is going on? I cannot even figure out how to put fastboot in verbose mode to see if there are any errors or anything.
BTW: All troughout this fastboot crap the phone remained perfect functional. The only change was the personal info that got deleted when I unlocked fastboot.
Also these don't work either
Code:
fastboot -i 0x1ebf oem disable-console
fastboot -i 0x1ebf oem enable-console
fastboot -i 0x1ebf oem dmesg
but these do
Code:
fastboot -i 0x1ebf oem disable-charger-screen
fastboot -i 0x1ebf oem enable-charger-screen
And getvar
Code:
fastboot -i 0x1ebf getvar all
all:
finished. total time: 0.002s
returns empty.
This thread looks similar and a method is mentioned briefly http://forum.xda-developers.com/general/help/vodafone-smart-4-turbo-qs-t2852827
However your question may have better luck in this thread http://forum.xda-developers.com/showthread.php?t=2257421
Unfortunately there's next to no support for this device so these methods your trying may not even be legit
Good luck to you
I looked into those thread. The problem I have is not with fastboot not recognizing my phone. It does. It just hangs when it tries to boot/flash/erase.

MI4c unlocking hell!

Applied for unlocking at http://en.miui.com/unlock/ and got this:
Apply for unlocking permissions
Sorry, your application has been rejected.
The more active your Mi Account is, the more likely your application will get approved.
Reapply​>>
So no way to get unlock code!
Then tried: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
And it seemed to work, could flash TWRP and CM 13.1
Had problems with radio, tried flashing radio, now I'm stuck in fastboot, can't boot to recovery or anything else, loops back to fastboot.
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.063s​
Any attempt to flash I get: "Partition flashing is not allowed"
Any ideas or should I just enter the "How far can you toss your Xiaomi MI4c contest"?
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Ydraulikos said:
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
Thank you friend Ydraulikos, I have tried flashing boot and recovery before, but I have not tried your version.
Unfortunately this was the result:
C:\adb\images>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (469 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.083s​
SOLVED!
Things looked pretty hopeless, two days without a phone, but managed to return to MIUI 7.1.6.7 and can proceed from here. I'm not saying this is the righ method, it worked for me and perhaps can help others in a similar situation. Have read a lot of posts in the last two days so please forgive me if I can not give credit to all the people whose advice helped, so thank you xda!
Installed QDLoader HS-USB Driver_64bit_Setup recommended in one of the posts and rechecked my drivers in general.
One command that seemed to be promising was "fastboot oem edl"
However, when my phone went to edl mode it was no longer accessible for fastboot <waiting for device>
On advice of another post I downloaded MiFlash2015.10.28.0 and libra_images_6.1.7_20151221.0000.11_5.1.*.tar.gz
From the command line typed "fastboot oem edl" and with MiFlash flashed MIUI 6.1.7, had to choose the "Flash all except data and storage" option as other options gave me a memory error message. Flashing went okay!
So my phone is back in business now!

How do I solve Fingerprint Enrollment error

Fingerprint lost, I backed up persist in advance, so I restore it by
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
not worked,prompted for "Flashing is not allowed for Critical Partitions"
then I tried
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
I checked /mnt/vendor/persist,files were successfully extracted.
However,the problem still occurred.
Appreciate for any helps.
ChuyanFang said:
Fingerprint lost, I backed up persist in advance, so I restore it by
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
not worked,prompted for "Flashing is not allowed for Critical Partitions"
then I tried
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
I checked /mnt/vendor/persist,files were successfully extracted.
However,the problem still occurred.
Appreciate for any helps.
Click to expand...
Click to collapse
Enter this command first: fastboot flashing unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
jwarrior319 said:
Enter this command first: fastboot flashing unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
Thanks for ur reply.
It still doesn't work.
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.005s
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.003s
I checked the unlocked status then:
C:\Program Files (x86)\OnePlus Mobile>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.007s
*never mind*
ChuyanFang said:
Thanks for ur reply.
It still doesn't work.
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.005s
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.003s
I checked the unlocked status then:
C:\Program Files (x86)\OnePlus Mobile>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.007s
Click to expand...
Click to collapse
Hmm, it wont allow you to unlock critical. Idk how to fix that.
You could try fastboot oem flashing unlock_critical or fastboot oem unlock_critical
Sent from my OnePlus KB2007 using XDA Labs

Is bootloader unlocked or not?

Hello, gentlemens!
I rollback RM 5 Pro from 12 to Android 11 (Realme UI 2.0). I didn't sure is bootloader unlocked or not. Last two results (false) confusing me. Here is results:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
Btw, I can't install TWRP again. So, I need little help about bootloader, is unlocked or not? Thank you.
Anybody know?

Redmi Note 8T and Bootloader

Hello everybody,
I need help to get my phone inbricked. Last year I installed LineageOS on my device and everything worked fine. Since I needed for some reason to relock my phone. I did via fastboot:
Bash:
fastboot oem lock
Since then my phone prints out: "The System has been destroyed ..."
I cannot flash anymore...
Code:
$ fastboot oem device-info
< waiting for any device >
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
finished. total time: 0.000s
What can I do to unlock the bootloader?

Categories

Resources