Related
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock ROM.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
Came back to it after a few weeks and issue has been resolved. Despite error warnings fastboot operated correctly, only manually. Any script etc. that booted device into fastboot would never find the device. Simple as flashing recovery and restoring a backup.
tl;dr: I'm not very bright.
FiniteDGk said:
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock KDZ.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
EDIT: Forgot to include that I see the proper devices in device manager.
EDIT 2: Device is properly configured and can be found in ADB when powered on.
Click to expand...
Click to collapse
where u able to fix it? i currently have no recovery or OS it just stays at the LG screen i can only get into Download mode i tried to flash a kdz but it cant read my phone....it turns on but thats it i cant got past the LG screen and when i connect my phone now i get different device drivers than before like LGE AndroidNet USB Serial Port and USB Modem....idk what to do
Hey!
I unlocked bootloader, installed TWRP, and rooted the phone.
Now I cannot get into recovery, the screen just goes black and white led lights up. I tried to factory reset in phone settings, but it wont do nothing. I try to switch off the phone, press vol+ & plug the usb cable to do the unbrick thing, but its not responding to that either.
Fastboot oem device-info says tampered false & bootloader unlock true.
Ned help!
Assuming you have Windows on your PC, if you try to enter download mode (in order to use unbrick method), can you hear a device plugged in sound and/or see the device in Device Manager? Maybe you don't have the drivers.
If fastboot is working too (because you could type "oem device-info" and get an output), you may want to try flashing a custom kernel/ROM or TWRP once again to get it working.
Are you sure you have flashed correct files and haven't mistaken OP3T with OP3?
AFAIK everythings OP3T specific.
Now I ran msmdltool, sideloaded most up-to-date stock rom, managed to flash TWRP and magisk, everythings going smooth this far. I made backups and tried to flash RR rom, but its saying "...this device ( . ) ERROR 7" whats the deal?
*FIXED*
I read that TWRP merged OP3 & OP3T, found a proper dl link for the newest ver TWRP and manage to flash the rom.
So If someone is having same kind of problems like me and trying to figure what can go wrong when you following step-by-step guides, pay attention to details. In this case first after unbrick I forgot to sideload newest ver stock rom. This error 7 thing was a minor and easy to fix, but still can take couple of hours to figure out(find a proper dl link)
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?
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 everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
Oh well, a phone that turns on in fastboot is not a big problem you'll say, and I thought the same as i previously had a problem and solved it by reflashing the stock rom in fastboot, so I took my nice computer (actually it's a 12 year old pc that runs on carbon, but that does its job), I opened the mi flash tool, connected the phone, selected the fastboot rom, precisely the EEA 12.5.7.0 (like the one natively installed before the damage) and started the installation. 20 minutes later ... error: cannot load bla bla bla, ok ok, i seached various solutions on Google and tried every metods, i changed the directory of the mi flash, of the rom, I updated the version of mi flash, i installed both on C:/ drive, reinstalled the drivers, i edited the batch file to remove the anti rollback but nothing, it arrives at flashing the super image and after some minutes it fails the flashing. Before you ask, YES, the bootloader was unlocked. I also tried to flash the rom in twrp, but ... the phone no longer had the twrp. The only way to start it was via command (fastboot boot twrp.img), the onekey injection did not make it permanent, and connecting the phone to the pc it revealed the device, but not the internal memory, I tried to make a format data but nothing. I managed to make it permanent only once, manually flashing only the vendor_boot and boot images in one of the boot_ * slots, in that case incredibly the pc also detected the internal partition, I copied the flashable rom and ... the twrp said to restart the recovery for I don't remember what, but basically I couldn't install the rom via twrp. At that point I finally gave up and took the phone to an authorized xiaomi service center where they fixed it (bye bye 25€), I don't know how exactly, I would opt through edl mode I think, and now i have my working phone...but heeeeeey, they flashed me the 12.0.1 TW version, not the EEA... Ahhhhh come on. They also re-locked the bootloader, so... agaaaain i re-unlocked the bootloader, this time i downloaded the unofficial tool xiaomi flash tool v2, it installed every needed driver, i clicked on "my phone works and i want to mod it", this time i tried to flash the global rom 12.5.7.9 and when it arrives at flashing the super image IT FAILS (fast boot flash_all failed, exit code:1, output: flash super error), and like a nightmare the phone was stuck in fastboot again, fool once but never fool twice, this time I had previously made a twrp backup of everything except the data partition, I install it and the phone restarts perfectly, I also notice that despite the attempted flash of the rom in fastboot after restoring the twrp backup without the data partition, nothing has been deleted from the data partition. So benevolent gods of xda, how the heck should I change rom region? Thanks for your attention and I hope I haven't stressed you out any more than I already am.
you are probably uploading rom miflashem pro and hence this error - I had the same. Use miflash's built-in pro miflash and it should go - it worked for me
SpYneX_ said:
Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
---
Click to expand...
Click to collapse
1/ OMG, take your time, espace your words, compact your questions...
2/ For old configuration a user have fix adb/drivers/detection problem with an another driver pack, and a old is btter than the lastest for some old configuration (so if your conputeur jhave 12 years, maybe...)
So try to install this drivers here
Change your USB port and verify your cable
3/ If problem occur, change computer (family/friend computer), just for flash, for be sure it's a communication/usb/detection problem
PS : Finally, why trying to overclock a soc already overclock by Snapdragon and always overheat ? It's really want finding problems ^^