Related
Hi all,
Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error . I tried many things but no luck. Then i followed direct method and that worked. Following is the procedure.
Note:
1. This will erase all your data and internal storage so better you backup them first.
2. I'm not responsible if anything goes wrong with your device.
Requirement:
1. Minimal ADB and Fastboot
2. Fastboot rom
3. Mi Pc Suite (for drivers, you can skip if already installed drivers)
Preparing:
1. Install Mi Pc Suite.
2. Install Minimal ADB and Fastboot.
3. Extract fastboot rom anywhere.
4. Copy all the files from images folder to the directory where Minimal ADB And fastboot is installed.
for example C:\Program Files (x86)\Minimal ADB and Fastboot
Procedure:
1. Connect your phone to pc in fastboot mode,
your Pc will install some drivers automatically.
2. Go to Minimal ADB and Fastboot directory .
3. Hold shift and right click.
4. Click open command window here.
5. Enter fastboot devices command.
If you see your device name in list of devices attached in command window then your good to go.
6. Now enter the following commands given below one by one in sequence.
fastboot flash partition gpt_both0.bin
fastboot flash tz tz.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash tzbak tz.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hypbak hyp.mbn
fastboot erase boot
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot reboot
Or
Simply put Flash All.bat (Attached Bellow) in Minimal ADB and Fastboot directory and double click on it (No need to enter those commands). Your Devices will reboot automatically when flashing done.
congrats
Hit thanks
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
did you place all the files in minimal adb and fastboot folder?
gabika1941 said:
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
Click to expand...
Click to collapse
did you place all the files in minimal adb and fastboot folder? And what you mean by using several different rom package? This method is only for fastboot rom made for redmi 2 only. Make sure your phone is detected by PC in fastboot mode with command fastboot devices.
I have tested this method three times without any errors. You are surely doing something wrong.
screenshot
gabika1941 said:
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
Click to expand...
Click to collapse
Can you attach a screenshot of your minimal adb and fastboot folder here. Also attach screenshot of your cmd window when you face error.
rkmadotra said:
Can you attach a screenshot of your minimal adb and fastboot folder here. Also attach screenshot of your cmd window when you face error.
Click to expand...
Click to collapse
i have a similar problem :
C:\Xiaomi\wt86047_pro_images_6.3.25_20160307.0000.16_5.1_cn_ee14351bfb\images>fastboot.exe flash partition gpt_backup0.bin
target reported max download size of 268435456 bytes
sending 'partition' (16 KB)...
OKAY [ 0.005s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.018s
C:\Xiaomi\wt86047_pro_images_6.3.25_20160307.0000.16_5.1_cn_ee14351bfb\images>
Click to expand...
Click to collapse
I have a 2014813 , was using a moded 2014811 rom on it. Kept crashing wanted to reflash , and installed TWRP on it , that said can't mount partitions and now i can't flash neider the 811 or the 813 roms to it . Just keeps saying error writing to partition . I can attach a screenshot of the Miflash tool if it helps. And above is the Command prompt error.
Pushing just 5 img files didn't worked for me and was stuck on MI logo, but pushing all files was reviving my phone!
Thank you very much for this method!
sir, my Redmi 2 is bricked
when I am trying to flash this the error messages is coming like
cannot load " gpt_both0.bin".
like these and so on. when I am using flash all.bat same messages is coming and then after erasing boot the phone reboots with black screen .
sir please help me
your help will be highly appriciated.
[email protected]
My phone stucks on Mi logo what will do
yeah!!!!!!!!!!!! after trying many other methods like recovery through adb ,command prompt,mi flash tool,mi pc suit...... i downloaded atleast 4-5 roms to just confirm that whether flash tool has some problem or the ROMs..........but if something worked after constantly trying many things in past three days it is this method.......seriously...
FYI this is the way i used it and u should probably use the same way
-> download MI flash tool (google it)
->install(in C
->download any compatible ROM for ur phone
->open :- C:\Program Files\Xiaomi\MiPhone\Google\Android
->paste all the contents of image folder from the ROM into this android folder
->then download this Flash All.bat from here and extract it...
->put your phone in fastboot mode ->connect it via usb
->then double click your Flash all.bat file-> give it some time->once finished ur device will start automatically
->after 10 mins or so disconnect ur phone from pc ... give it 4-5 mins , ur phone will be out of bootloop and u will be awarded with a new MIUI
Yes! It worked for me as well.
Thanks for your steps.
(FYI this is the way i used it and u should probably use the same way
-> download MI flash tool (google it)
->install(in C
->download any compatible ROM for ur phone
->open :- C:\Program Files\Xiaomi\MiPhone\Google\Android
->paste all the contents of image folder from the ROM into this android folder
->then download this Flash All.bat from here and extract it...
->put your phone in fastboot mode ->connect it via usb
->then double click your Flash all.bat file-> give it some time->once finished ur device will start automatically
->after 10 mins or so disconnect ur phone from pc ... give it 4-5 mins , ur phone will be out of bootloop and u will be awarded with a new MIUI )
and it worked good.
My Mi Account was locked and could not connect to internet at all.
I had tried using Flash tools, PC suite - Flash methods and nothing worked. I had spend more time to fix my mobile in all these ways.
But this method is awesome. Only took around 15 minutes to completely flash my mobile.
After flashing the mobile, I am able to connect to internet and I have also created a new Mi-Account and linked my G-Mail account to it.
Am super happy now.
Thanks a lot.
However I would wish to add another details to the above setps:
The Flashall.BAT too needs to be extracted and copied into the same folder where the contents from ROM's Image folder were copied.
awesome bro thankyou very much.it's working absolutely well:good::good:
Tried a similar method and got my redmi2 prime hard bricked. Can someone tell me the test points in the device 2014818?
Thanx This works for me. successfull to flash my redme 2
Simply put Flash All.bat (Attached Bellow) in Minimal ADB and Fastboot directory and double click on it (No need to enter those commands). Your Devices will reboot automatically when flashing done.
congrats
Hit thanks[/QUOTE]
Will this work for Redmi note 3 Snapdragon??
Hello
I am stick in bootloop with my Redmi 3 (after trying Flashify).
Tried the above method with high hopes, as I have been trying everything else also with no luck.
I have downloaded a ROM for my device of course.
It all seems to go well until I launch the Flash_All.bat
Then the DOS commands are executed in 5 to 10 secs, and my devices reboot, but in a bootloop again
I got a breif view at the DOS commands, and it basically, at several lines says somthing, like: "failed to write, device is locked"
see attached sreen shot
does this mean my problem has no solution and I can simply throw away my device?
Thanks
rkmadotra said:
Hi all,
Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error . I tried many things but no luck. Then i followed direct method and that worked. Following is the procedure...
Click to expand...
Click to collapse
You solved my problem :good:
Thank you buddy..... This method works
Fastbooting method did not bring back my stock model number that is hm2014818. It changed to 2014817 when i flashed miui 8 64bit rom for redmi 2. Now i am not able to go back to my original model number even by fastboot method. Any help please??
will the flash all.bat support on other mi device's??
stuck at erasing user data
flashing stuck at flashing userdata
When i try to boot into fastboot mode using power key and volume - key, it shows me a blank screen :crying::crying: . there is no bunny with fastboot logo. only black screen.anyone help me please.
Note: I am on pie with march update.
feroz mahmud said:
...there is no bunny with fastboot logo. only black screen....Note: I am on pie with march update.
Click to expand...
Click to collapse
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.
Aerobatic said:
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.
Click to expand...
Click to collapse
Will you please tell me the process of flashing splash? And where do i get this file?
feroz mahmud said:
Will you please tell me the process of flashing splash? And where do i get this file?
Click to expand...
Click to collapse
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
So, you will need:
1. Mi A2 with unlocked bootloader and critical partitions (search this forum on how to unlock) in bootloader mode, connected to USB 2.0 port in PC;
2. Working drivers and / ADB / fastboot installation.
3. "splash.img" copied into directory of working ADB / fastboot installation.
To check that requirement (1) and (2) are fulfilled, run CMD shell in directory of working ADB / fastboot installation and type
Code:
fastboot devices
If output list contains the only 1 string with ID of device (same as shown by "ADB devices -l" command in normal MTP file transfer mode), you are ready to type in commands:
Code:
fastboot flash splash .\splash.img
fastboot reboot bootloader
You are supposed to see the 'bunny' after phone reboots to bootloader mode once again. To reboot back to system just use "fastboot reboot"
If above is not helpful, bring phone to service
Aerobatic said:
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
Click to expand...
Click to collapse
thanks for you information. my device is locked. when i try to peform fastboot devices , it shows me a error saying application was unable to start correctly.
1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.
Aerobatic said:
1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.
Click to expand...
Click to collapse
thanks for your information.
My devices is locked(bootloader). and fastboot isn't showing up. now tell me how do i flash spalsh file?
1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
Following is what you could have already found in guides I was suggesting to find and study
2. Prepare everything for unlocking in phone:
2.1. Get "developer rights"
2.2 Allow "USB debugging" and "OEM unlocking" in developer options
3. Have you get acquainted with ADB drivers installation and ADB commands and fastboot commands?
Can you see result of "adb devices -l" command in CMD shell when phone is attached to USB-2.0 port with MTP file transfer enabled?
If no, just bring it to service or somebody who knows what to do.
4. Can you see result of "fastboot devices -l" command in CMD shell when phone is attached to USB-2.0 port in what is supposed to be bootloader mode with black screen?
If no, just bring it to service or somebody who knows what to do.
5.. If yes, and device ID is the same as in result of "adb devices -l" command
6. Unlock bootloader and critical (see guides here in Mi A2 threads), it takes 2 commands and 2 reboots
7. Reflash splash.img as stated above in my 1st message
Nobody here can repair your phone, - only you or service. So I won't write more here.
Aerobatic said:
1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
.
Click to expand...
Click to collapse
Can you help me with this? my phone is ok, when i run fastboot command it shows me "??????????? fastboot"
Restart pc or update adb and drivers.
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/images and flash manually it's work with me
Sent from my BASIC using Tapatalk
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
TENN3R said:
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
Click to expand...
Click to collapse
Just to add to this, make sure you left the image-coral-[buildnumber].[builddate].zip ZIPPED. Your folder should look something like this one, although you might also have your platform-tools in that same directory, which is perfectly fine, but not necessary if you have them added to your path.
Just try redoing the flash-all.bat again. This time, though, do it from powershell. Here's what to do. Right click in the folder, not on any item, just in the folder, and you should see "open powershell" (or command prompt, if this is the case, then just type powershell into the cmd window), click that. Then, type or copy and paste into the powershell prompt while in that directory:
.\flash-all.bat | Tee xda-flash-attempt.log
and if it still doesn't work and you're stuck in fastboot, just upload that .log file, so we can see what happened. If you're curious, what Tee does is it simultaneously takes standard input (i.e. what you see on the screen, the output of programs) and shows it to you, as well as sends it to a file, in this case, the xda-flash-attempt.log If you really don't want to use powershell, you can accomplish what's needed by typing flash-all.bat > xda-flash-attempt.log, but you will not see any of the output, as it will all be piped into that file. The | key is the one directly below backspace, which is the same key as \, but with shift held down.
Also, if it's not working, it might be worth checking that the checksum of the zip file you downloaded is correct, possibly redownloading it, and also checking what the flash-all.bat contents are. There are two files named flash-all in the folder, one a .sh for *nix systems, and a .bat for windows. While it should automatically assume you meant the .bat, it's best to be explicit. The .sh really wouldn't do anything different, if it worked, so it's a minor issue that really wouldn't make a difference, but still.
Edit: when you do type flash-all, the cmd prompt was in the directory with the flash-all.bat file as well as all of the other necessary files, yes? Seems obvious, perhaps, but just based on the "cd\pp\p" command you ran, which doesn't do anything, you should be changing directory to the directory that holds the flash-all.bat as well as the firmware.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today ...
Click to expand...
Click to collapse
Like others have said, you need to extract the Google image which has a nested zip file (which you leave alone unless you need something in there). Since you apparently are stuck and cannot boot, I suggest you extract the boot.img from that nested zip file into your tools folder and fastboot flash the boot.img to be able to boot the phone to system. You may need to do the vol-down button press to enter fastboot mode. Once you have your phone back and running, boot into fastboot mode and run the flash-all again. If you extracted the Google image completely, now the script can finish. Not sure if you want to wipe the phone while doing this, so you can also "dirty flash" . If you would like to retain all your apps and app data, edit the flash-all script with notepad and remove the wipe flag (-w) from the script and SAVE it before running. Best of luck. :good:
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Put the unzipped factory image files (should be 6 of them) in your platform tools folder and then open up the command prompt in the platform tools folder and execute the flash-all command. Make sure all remnants of previous factory images, etc. are removed from the platform tools folder beforehand as well so you just have the platform tools default files in there as well as the 6 files from the factory image.
The latest version of platform tools is 30.0.4 I believe so make sure you have that version.
I just switched from a Pixel 2 xl and ran into the exact same problem with the no valid slot to boot error yesterday. It turned out I was not using the latest platform tools when flashing the factory image. I upgraded my platform tools to 30.04 and everything flashed and booted as expected.
Make sure you're using an A to C and not the C to C that comes with the phone when flashing. Yes, it matters.
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
blackbomb1991 said:
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
Click to expand...
Click to collapse
Woohoo! This worked perfectly. Thanks for following up with the instructions.
miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!
Hello,
I unlocked my Mi8 and successfully installed Lineage on it.
After trying to install Magisk, my phone only boots into fastboot (and mi recovery, but that's not very helpful).
fastboot boot twrp.img results in error :
FAILED (remote: Failed to load/authenticate boot image: 00000050)
I tried MIFLASH by
1) downloading, dezipping and starting newest miflash (2020.3.14.0)
2) installing drivers
3) downloading and dezipping MIUI-fastboot-ROM
4) entering path* into miflash, refresh and flash (already tried all options "clean all" to "clean all and lock")
*) path to the folder that includes among others flash_all.bat
all this results in error:
not catch checkpoint (\$fastboot -s .*lock), flash not done
Nothing changed with the phone, still the same error.
While wanting to review the logs, I clicked in miflash on log/flash log. The log did not say anything helpful, but the error code of fastboot boot twrp.img changed to command write failed (Unknown error). Nothing else changed.
UPDATE: changed back to previous error (remote: Failed to load/authenticate boot image: 00000050)
If you have any idea or need any more information, please tell me!
I need that phone and cannot afford to terminally brink it!!
I did not find much online, did no one else had this problem??
THANK YOU!
PS: Using lenovo-laptop with quite vanilla win10 (and not so vanilla kubuntu dualboot, but miflash only supports windows)
MIFLASH-log says:
Code:
[14:37:14]:lsusb path:"C:\Users\<>\Downloads\MiFlash20200314\MiFlash20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:GetScriptDevices
[14:37:15]:FlashingDevice.flashDeviceList.Remove ab6ee6a0
[14:37:15]:add device ab6ee6a0 index 1
[14:37:15]:Thread start,thread id 5,thread name ab6ee6a0
[14:37:15]:start process id 2524 name cmd
[14:37:15]:Thread stopped, thread id 5, thread name ab6ee6a0
UPDATE:
what would the world be without mysteries. Though I cannot really accept them in the IT sector, I cannot really explain, why "everything" works now.
The error of miflash still exists, but fastboot works.
I tried booting and flashing the lineage boot.img instead of twrp.img as well as miflash about every five minutes. I do not think it was the latter, though.
I am still curious on that matter, but having everything working is more important.
Thank you anyway.
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub.
There is no need to use miflash to flash the fastboot miui rom - you can do it from command line in both windows and linux. Once you decompress the fastboot tar.gz, you have .bat and .sh files in the folder - miflash runs those exact files. Just install adb and fastboot on kubuntu and run your choice of script (flash_all, flash_all_lock, etc.) this has the added benefit of not needing odd drivers in windows (last time i used miflash it complained about some .net stuff that i had to manually install).
Since normally you would install twrp i have to wonder if by any chance mi-recovery is not checking the boot image before flashing it ... not sure, or maybe it had something to do with the FBE of lineage since there was no recovery in place to decrypt the partitions, if i remember correctly, the boot image needs to be signed with the verity key. The log snippet you provided doesn't tell anything as it has no error messages or anything.
Either way, not sure how what you brutforced to get it working but glad it solved itself, however, if you still have mi-recovery instead of a custom one, i would suggest you backup the device, flash MIUI without locking the bootloader, installing twrp (not just booting it) and reinstalling lineage from there. (all this can be done from your kubuntu install so you avoid driver and other windows shenanigans)
to install adb and fastboot it's just a question of sudo apt install adb fastboot
either tar -xvzf the archive of the fastboot image or just extract it from the file manager
open a terminal in the extracted folder (where the bat and sh files are)
put the phone in fastboot mode, connect via usb and do a "fastboot devices" just to make sure the device shows up
./flash_all.sh (this does the exact same thing as the clean option in miflash - just open the script and take a look through it)
Once the flash is done and the phone reboots, skip through all the setup steps just so miui loads up then reboot to fastboot
get twrp from their website, open terminal where it is downloaded and "fastboot flash recovery <name_of_file>.img"
once the command finishes do a "fastboot boot <name_of_file>.img" and once you are in twrp, go yo wipe, do a factory reset, back, advanced wipe and select the caches, back, format data, type yes, back to the main menu of twrp and reboot recovery, this should boot you back into twrp but this time the one that is flashed on the device.
from here on install rom of choice and magisk as usual (use the install option in twrp tho, don't unpack the zip)
Had the phone for 2 years and i flashed different roms on it almost weekly since the wait time to unlock the bootloader expired and never had an issue with this workflow and it saves you from having to use windows. Even for unlocking the bootloader, in case you ever lock it back up, you can use https://xiaomitool.com/V2/download (worked like a charm on linux)
sorfat said:
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub....
Click to expand...
Click to collapse
Thank you for your detailed reply!
Of cause, in order to install lineage, I used TWRP. But I somehow did not install it, but used fastboot boot twrp.img in order to manually temporary boot twrp every time I need it. It was not intentionally at first (did do
"fastboot flash recovery <name_of_file>.img"
Click to expand...
Click to collapse
) but I learned to like the mi recovery for it's wiping and being able to use with the keys (not touch, since I managed to disable touch once before that). Mi recovery does not allow flashing at all, so no worries there^^
I have read the ryzen thread before posting, that's why I included my hardware. Not sure, if Lenovo has ryzen, mine does not.
Why I did not think of just running the script in kubuntu instead of hassling with windows, I do not know. Guess it does have something to do with the wood in front of all the trees.
I have the phone for about one and a half week and flashed it at least once a day :laugh:
But I hope to neither lock it again (twice is sweaty enough) nor have to flash it every week.
Thank you very much, if I ever lock myself out again or get another phone to set up, I will defintely reread this post!
btw: is there no way in xda to close a thread?
A Mi8 dipper does boot until the mi sign with 3 dots, then reboots.
It does boot into fastboot. When booting fastboot mode, PC fastboot can see it.
It boots into Mi-Recovery 3.0. ten, PC adb can see it
The bootloader is locked.
When using 'MIAssistant', Mi Flash Pro can see it.
Mi Flash Pro can read IMEIs, can wipe user data.
It does read a Device Versions 9.6.27. When using miui_MI8Global_9.6.27_7e6ce8a462_9.0.zip to re-flash, it gets verified successfully, the flash runs successfully through but the device does not boot -stays in the same status
Using MiFlash 2020 3 14
F:\miui_rom\MI_8_Global\V12.0.1.0.QEAMIXM\dipper_global_images_V12.0.1.0.QEAMIXM_20201021.0000.00_10.0_global
flashes forever (stopped after 3000 seconds) with status
$fastboot -s exxxxxxx getvar product 2>&1 | findstr /r /c:^product: "dipper" || echo mismatching image and device
(no change on the screen of the phone)
Best guess: someone did flash the device with a wrong image.
Is there a adb script based way to get back to stock rom?
(Yes I did search for quite a while).
Thanks for any advise.
Hey!
First, make sure you have the correct fastboot ROM for your phone. (https://bigota.d.miui.com/V12.0.2.0...M_20201113.0000.00_10.0_global_b450e91e17.tgz). By the way, you must unlock your bootloader first. Download Mi Unlock, make an account and wait around 7 days. DO NOT TRY TO UNLOCK YOUR BOOTLOADER AT LESS THAN 7 DAYS, IT WILL RESET THE TIMER. I waited 8 days, just to be sure. Make a folder on Desktop named MI8, or something, but cannot contain spaces, and extract the images folder from that link i wrote up in that desktop folder. Next, download Minimal ADB and Fastboot (https://androiddatahost.com/wp-content/uploads/Minimal_ADB_Fastboot_v1.4.3.zip), and install it in that "images" folder. Put your phone in fastboot, go into that "images" folder, where you installed Minimal ADB and Fastboot, keep Left Shift holded and right click, it should appear Open PowerShell window here. Click on that, type "fastboot devices" and see if it appears. In some instances, you must write like this "./fastboot devices". I will continue this in the next message, because i need to upload something for you.
easyupload.io
easyupload.io
easyupload.io
Here are the commands that should make your phone work again. I had the same problem for my Redmi 8, and this worked. You must run one at a time, and DO NOT GET OUT OF FASTBOOT UNTIL YOU EXECUTED ALL THE COMMANDS, IT WILL PROBABLY HARD BRICK YOU PHONE (stuck in EDL). If they do not work, or they do not show anything in PowerShell or CMD, just delete the point and the slash at the beginning of every command. If you have any questions, you can ask me.