So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
EDIT: AFTER SEEING SOME POSTS HERE ON XDA I MANAGED TO USE XIAOMI MI FLASH TOOL WITH SUCCESS!, I NEEDED A USB HUB AND CONNECT THE PHONE IN FASTBOOT AND THEN APPLY THE STOCK IMAGES!, ANYONE WHO NEEDS HELP THIS SOLUTION CAN WORK ( ALL MY 3 USB PORTS DIDN'T WORK, WITH HUB IT WORKED )
ClaudioG123 said:
So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
Click to expand...
Click to collapse
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
tsongming said:
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
ClaudioG123 said:
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
Click to expand...
Click to collapse
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
ClaudioG123 said:
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
Click to expand...
Click to collapse
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
Will try soon as im home, if i get waiting for device should i wait?
Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
I can try to see if he works with xiaomitoolv2, and will try what you said and post here
tsongming said:
you do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also it seems that you missed some of the steps outlined in the install instructions for the pixel rom ( i assume the pixel 3 q rom?)
you must install magisk on that rom, you must use recommended twrp,
i haven't used ubuntu for flashing roms recently so i can't provide solid recent steps on ubuntu.
so i would suggest using a pc , ( surely you know someone with a pc) enter fastboot, then you can verify that the phone actually can enter fastboot by checking device manager, or by verifying that the phone is seen by adb
if you are unable to access fastboot, you will need to go into edl mode. Once in edl
download fastboot dipper images rom, and use flashall.bat method to restore the phone.
download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 but it has to be a fastboot rom and not a recovery rom
unpack the rom twice on your desktop
you will be left with a folder and inside you will see batch files and a image folder.
doubleclick flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in recovery mode, fastboot or edl
flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
you should then setup rom
afterwards install twrp and root then create a full twrp backup and save to your pc.
this way you will have a quick solution if you ever need it again in the future.
enjoy a working phone
rom link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
any images fastboot rom will work, you can use the one i listed above or you can use the recent 10.3.5 stable images rom, just find the link via google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
i used this solution but i go i connected the phone in a usb hub!
ClaudioG123 said:
i used this solution but i go i connected the phone in a usb hub!
Click to expand...
Click to collapse
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
Your solution worked with the phone in fastboot, but i had to try a usb hub, that's all, has for roms, experienced both of pixelrom3 and havoc and didn't conviced me enough, i find miui 11 of xiaomi.eu more good looking and doesn't have bugs, and thank you, you are a lifesafer, if it wasn't for that i would have never flashed stock rom back
tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
ClaudioG123 said:
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
Click to expand...
Click to collapse
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
tsongming said:
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
Click to expand...
Click to collapse
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
ClaudioG123 said:
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
Click to expand...
Click to collapse
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
tsongming said:
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
Click to expand...
Click to collapse
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had the issue back with miui 10 stock
Liked the fact that they boosted sound
ClaudioG123 said:
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had+ the issue back with miui 10 stock
Liked the fact that they boosted sound
Click to expand...
Click to collapse
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
tsongming said:
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
Click to expand...
Click to collapse
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
harnkalkn said:
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
Click to expand...
Click to collapse
I am using the weekly Xiaomi.Eu beta rom, averaging 7 hours and 15 minutes SOT and no real issues.
mi 8 bricked
i bricked mi 8 when i try to re-lock bootloader. now i only received a main menu and red massage "this miui version can't be installed on this device". anyone can help me?
Related
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.
Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.
I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode
How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )
No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
buczek0711 said:
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
Click to expand...
Click to collapse
After to flash TWRP you have to flash the vbmeta.img and then boot to TWRP not through commands but manually with hardware buttons, don't allow device to boot to system before to boot to custom recovery otherwise this will be overwritten again.
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
buczek0711 said:
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Click to expand...
Click to collapse
No, this is not the method to boot to recovery from what I pointed out, you don't have to firstly power off device but from fastboot commands you can type either fastboot or fastbootd reboot and inmediately press the volume up till the TWRP logo appears, the fastboot/d command will act same as it be the power button.
The thread explains how to install unsigned drivers in Windows, not to set it on your Redmi but is for your PC. If you succesfully get the drivers installed then you have to reboot your PC entering again in safe mode (not normal mode) and from there the commands through fastbootd are generally the same than those for fastboot.
buczek0711 said:
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
Click to expand...
Click to collapse
Just to be sure you are doing fine and not missing something the adb commands work while device is on and fastboot/d commands work only in fastboot mode.
Can you attach some SS to see what you are typing and the error that brings the cmd?
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
buczek0711 said:
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
Click to expand...
Click to collapse
Yes, fastboot works normally while in cmd, this is intended for that, no problem to enter firstly toi Power Shell but you can switch to cmd from PS just typing cmd and all the commands from here will be for cmd, doesn´t matter at all how many old is, cmd can work inside PS keeping the same aspect.
buczek0711 said:
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
Click to expand...
Click to collapse
You don't need to reinstall nothing, just from the downloaded SDK platform do all that you want to avoid misspelling path and folder directories, I mean place the files you need to use in the same directory and open terminal prompt (PS) in the same folder where adb/fastboot binaries are, pressing right mouse button and shift at same time.
I feel you are missing something simply here, not so hard to do.
The misc.img partition that you mentioned is just to restore something that went wrong in the process.
But if you are happy with this Miui ROM then great. No hurry to answer that, give your time to rest.
I also feel, that there is something simply to overcome, Only the fastbootd is new Stuff to me. However, any time I was doing something with Snap, i was long after finish by the current time (almost a month with It and 3rd day with fastbootd issue).
I don't get it. Now when I've tried to enter fastboot mode...phone entered it (fastboot, not fastbootD). Then I've installed pitch black recovery and sucessfully booted into it by restarting phone and then pressing vol up. Now I'm trying with magisk and another entry to pbrp.
Second try gave me stock recovery again. What is wrong with it XD?
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
buczek0711 said:
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
Click to expand...
Click to collapse
I think you are not following the right direction, if you want consider what I pointed out; you don't have to power off device prior to boot to recovery for first time but you have to type from fastboot (no matter fastbootd) and inmediately from there boot to the custom recovery, when you succesfully booted to custom recovery then flash the recovery zip if there is one (PBR and OFR have one) and if not a zip then flash the image again to the recovery partition, also check if there is some installer apart from the image that can fix it in the ramdisk partition, at this point your issue is solved, next step is to reboot device to system normally, if you don't have any issue on that then OK but if you can´t there some steps more that you should do, but let this for last.
Ok, let's group it.
I do not think that particular matter of how do I restart phone matters here (at least, I do not believe it, that it does anything).
Option to restart to recovery from adb still not working.
Trying to find magisk.zip in main directory of internal storage still fails under pitch black recovery project.
From new stuff - I now got an error message, while opening pbrp, most likely with the issues about system being read-only (not sure though, since I do not remember it now, might look into it once more). I have the options to mount partitions, available from main menu, but since I do not used it at all before, I do not know, how to deal with it.
Also - my system boots normally, it must have overwritten recovery (or at least header of it) sometime during boot, since custom recovery is unavailable to access after first full reboot.
I'll try now to install newer version of twrp from yt that I've posted days back. I would also try with orange fox (however, i cannot find img for it, just source code, don't get it).
Is there someone, who can and will to help me?
Situation looks this - on this 12.0.4 MIUI with android 10 I'm unable to install ANY recovery (either phone do not restart to recovery after proper command from cmd or it boots into it, but after visiting system and then to recovery again it shows stock (even without any operations or updates from ota).
I cannot force to work either twrp 3.4.2b, twrp 3.5.2, pitch black recovery 3.0.0 beta.
After trying to install magisk 21.4 zip from twrp 3.4.2b phone entered bootloop, because f**k you, user, I cannot even get it to fastboot mode now (btw, fastboot now works, fastbootD is luckily a long-gone crap).
All cmd's have been run with admin rights. There are NO SUCH THING, as misspelling (cmd and adb would not execute command ,if it is misspelled, either command or filename). I've installed drivers once again and used cmd from dedicated folder with adb fastboot portable version (runned as admin, of course).
Now I'm downloading older version of rom for fastboot (miui 11.0.9) with android 10. Something has to finally work on this piece of junk.
Writting each time is success (cmd says "OKAY" nad displays time, it took to do so), downloading recovery image to start from it also works, there aren't any errors in cmd, yet phone still isn't working.
Where's the issue with it? Apart from being mediatek, which seems to somehow enormously hardened any flashing? I did not encounter anything like this with qualcomm, yet mediatek still manages to pisses me off with their really weird implementations and working (???) of their stuff.
another update from battlefield. Managed to finally get mediatek verify bypass in smart phone flashing tool, however it ended with forcing me to format anything in the phone (if not, program would not let me install anything).
Second problem is forcing me to disable verify, yet command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img put in fastboot mode (yes, it works now) does not work, because adb says, that "--disable-verity" is not a recognised command.
SPFT cannot properly download images from phone and welcomes me with error about download exception, happening either in recovery part or in boot part. SInce I do have access to fastboot now, I can overcome it (I think).
Old miflash tool to install roms via fastboot says it cannot flash rom in locked stage (I might have lost unlocked status, but I'm not sure about it). Do you know ways to overcome it?
It is me again (inb4 use edit). Had to unlock phone again by using miphone unlocker (it went ok). Still cannot flash using SPFT, miflash started showing idiotic errors like "no file in directory" or "cannot access to directory" (it could before, I did not changed name of it). Will continue reporting of progress (or the so-called "progress").
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Do you believe this could help with the ram dump issue?
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Blumi511 said:
Do you believe this could help with the ram dump issue?
Click to expand...
Click to collapse
I have no idea, but I think it can't get worse by trying it.
Flashing the firmware (so called "RAW"-firmware) that allows one to turn back to A11 on the A12 beta page, should get back every device back to a working condition if the problem isn't hardware or extremely messed up in the few partitions that the raw doesn't flash.
I tried using this method to get back to stock from OmniROM, but after several reboots, the phone is stuck in fastboot mode. I tried booting normally and recovery mode, and it immediately goes back to fastboot mode. Any ideas?
/Edit: Got it to boot by flashing Lineage recovery, rebooting into it, and doing a factory reset from there.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...KS-30.11.51.115-MR0-user_20210826-release.zip
Turn of your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
# Thanks to NisseGurra for the link to the latest RAW image.
Click to expand...
Click to collapse
Thank you very much! This safed my phone! I stupidly flashed the boot image from a different build and wasn't able to boot. Only your flash.cmd worked! I hat to comment out the hardwareid check though, because mine was 0 somehow.
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This could also be just an issue with the fastboot drivers. Try reinstalling them, also clearing up orphaned devices in device manager could help.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This is a known issue with Windows 10 computers. They have some sort of signature check where even if you install the correct drivers, they don't really get "installed" because of this check. There is a workaround for this though, I'm not sure how.
However, if you have a Win 7, Vista / 8 PC, adb and fastboot will both work flawlessly with no hassles (experienced personally).
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Where do you get latest RAW links from?
I could not find them via Asus site.
HyperCriSiS said:
Where do you get latest RAW links from?
I could not find them via Asus site.
Click to expand...
Click to collapse
A12 beta page. The firmware that allows you to go back to A11
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Yippee38 said:
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Click to expand...
Click to collapse
Works for me.
is there a newer image out?
it would be good if there is a full raw android 12 image posted...since android 12 is released now.
Hi there,
Installed LineageOS 18.1 yesterday because my phone was having awkward moments, I want to go back to RAW stock, but I can't finalize the install.
I followed OP's instructions, but I never could find the flashall_AFT.cmd from the extracted archive.
Anyway, i managed to use LineageOS Recovery, but it requires signature at 47% , and when I press Yes, it says :
E:error: 21
Installing update...
E: Package is for product ASUS_I006D but expected sake.
Installation version
Installation tried : UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip.
When I tried WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, it required signature after 0.2 seconds, with following message :
E:footer is wrong
update package verificationtook 0.2 s (result 1).E:Signature verification failed
E:error: 21
Installing update...
E:Open failed: /metadata/ota: No such file or directory
E:Couldn't mount Metadata.
E:Failed to find update binary META-INF/com/google/android/update-binary.
I resetted before launching above operations, everytime.
What can I do to go back to Asus RAW Rom ?
Forward thanks and best regards.
EDIT : OK, found it, I just had to extract the .zip file. I thought I had to flash it like any image.
My bad.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thank you so much! You saved my phone! The only thing is that I couldn't find the flashall_AFT.cmd file in the new image, I had to use the WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, and it worked perfectly. After I flashed the boot.img trying to get root on android 12 several times, my phone was in a ram dump state.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thanks! This helped me after I got into a ramdump situation. I flashed a rom and a boot image through the bootloader instead of fastboot and got things corrupted.
On my Asus Zenfone 8, I upgraded from Lineage OS 18.1 to 19.1.
When I wanted to flash gapps and did a reboot into recovery, since then the device no longer works.
I can't get into recovery and I can't get into fastboot mode.
When I turn off the device and turn it on again, the following appears on the screen.
Waiting for flashing full ramdump...
PLS help me
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse
mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.