Database Info

Failed to flash ROM, Computer won't detect phone now, need help!

So I tried to flash miui eu and my phone was unable to reboot. It goes straight into recovery.
This step by step what I've done so far:
1) unlocked bootloader with xiaomi unlock
2) installed ADB and TWRP 3.3.1-0
3) attempted to flash miui eu ROM, which resulted in boot loop/enters recovery now
I can go back and forth between bootloader and recovery. I was just going to transfer another ROM to my phone and re-flash.
HOWEVER, I can't access the files on my phone via my computer
The phone is detected but it' listed as an "unspecified" device on my computer. Drivers are up to date per the xiaomi bootloader unlocker app.
Any help is appreciated...

Format data?
And after reboot to recovery and flash rom
You have twrp?

Try following this guide I wrote for someone else, the other day, just substitute the version of Xiaomi.EU you want to use for Evolution (or the Xiaomi.EU rom used in the middle of the guide, that may work).
Bootloops on this phone usually come down to needing to *FORMAT* (not just wipe) data, or needing to have the correct vendor image; the one you can find in this little guide has been working fine for me with everything.
https://forum.xda-developers.com/showpost.php?p=79909955&postcount=142

Had this issue before. Try format data typing "yes" then reboot to recovery.

Aleksanderbjorn said:
Had this issue before. Try format data typing "yes" then reboot to recovery.
Click to expand...
Click to collapse
this worked, thanks!

[Q] [Locked OP6] Bootloop after upgrading to 10.3.0 - how to recover without format

My dad got the OTA update to 10.3.0 on xmas day and installed it. However the phone is now stuck on boot logo. He has a locked phone just as it came out of the box (ie no TWRP, no OEM unlock, no root).
I am quite experienced with installing custom ROMs but with locked phones I am lost. Is there anyway to recover the device without deleting data / factory reset? This is because my dad has quite a lot of pics on the device that are not backed up (yeah I know...).
Things I've tried so far:
- reboot holding power button + volume up
- boot flash twrp from fastboot - no permission due to phone being locked
- in stock recovery I do not get access to device via cable
- installed Tool all in One - it sees phone via fastboot
I always use the Stock Fastboot ROMs for OnePlus 6 myself to recover from soft bricks but this wipes data so no option here. Unless there is a way to install parts of ROM? Any other tips or ideas from the awesome XDA community? :good:
Btw this is the update he installed:
Screenshot of update that was installed

If you boot on twrp, it does not ask for the pin code to access the data?
Maybe try the last twrp for OOS 10.3.0 : ( https://androidfilehost.com/?fid=4349826312261678088 )
Use command : fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img
Try flash a new boot img :
Stock boot 10.3 img
https://drive.google.com/open?id=1w44cUg815g-H1h_6gObUVPLDTc_dtiMX

The phone is not unlocked and therefore has no TWRP recovery. This is my problem, if it was unlocked I would have figured out a way to fix it.
PS it does ask for pincode when accessing stock recovery

I'm not sure if this works on locked bootloaders but try switching boot slots using fastboot.

Couple of weird things:
-you don't need an unlocked bootloader for fastboot to boot back into the system
-the dual partition was designed precisely to prevent things like this from happening. When an update fails, you are supposed to roll back to the old slot you were on previously.
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?

Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try

awaiz said:
Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try
Click to expand...
Click to collapse
When I try to set it to slot A (it's B now) it says device does not support slots which is weird as 'fastboot getvar current-slot' does show it using slot B right now.
When I try to set it to B (ie current slot) it says: FAILED (remote: 'Slot Change is not allowed in Lock State').

awaiz said:
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?
Click to expand...
Click to collapse
When I reboot to stock recovery it gives two options:
- Wipe Data and Cache
- Advanced
There are two reboot options under Advanced:
1. Reboot to fastboot
2. Reboot to recovery
2nd option just boots it back to this same recovery. Boot to fastboot works as well. So there is no option to reboot the device.
Perhaps I can try to flash the stock ROM (kinda of dirty flash) but again not sure if that works on locked phone.

https://www.androidexplained.com/change-active-partition-slot/

JagDave said:
https://www.androidexplained.com/change-active-partition-slot/
Click to expand...
Click to collapse
This doesn't work unfortunately on a locked device.

I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end

help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..

Alamin4736 said:
help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..
Click to expand...
Click to collapse
Bro..Use the Msm tool to get recover coz you have the locked bootloader

roel1976 said:
I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end
Click to expand...
Click to collapse
I am facing similar problem with my OP5. When I boot in recovery, it asks for pattern to unlock. But does not accept any pattern. In the absence of pin, it gives option to Wipe Data. Will I get similar options like you did ? I am hoping to save my data.

Unlock bootloader, flash twrp, vbeta, flash rom...ok but phone no boot!!!

Guys!!! what the hell!
i did everyting was written in here. Bootloader unlock, everything ok, flashed twrp, flash vbeta.img then flash any rom but the phone never boot! still go always and alwasy again to recovery!!!
What am i missing?

Format data in twrp.then reboot

I've done everything. Format everything ecc but nothing has changed...still no boot and recovery immediately.
I've tried to put the stock recovery again and it boots (i flashed of course via twpr the c.01 RUI ozip file before). I really can't understand.
I've tried to root the phone but again problem. I put the twrp recovery again (on the C.01 stock rom) then flashed magisk 20.1 or the latest. Everything ok, rebooted and....it says the boot img is corrupted, write or go to the service support! So i entered again in fastboot and flashed a new boot.img. No boot but can enter recovery. Put again the twrp, flashed stock rom again, put stock recovery, format data and now eveyrhing ok. Why so hard to even root???

Did you check format data on right bottom of twrp.this is not same as the wiping data

i made all format.
another curious stuff is. I put twrp, vbeta img . Reboot in twrp. ok. I reboot phone, go to RUI then i try to go again in recovery and .....no more twrp! but stock one! twrp has been replaced! why!!!!!?

Correct,Stock rom will replace twrp to stock recovery.but custom rom not changing recovery

I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.

waqar bukhari said:
I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.
Click to expand...
Click to collapse
uhm ok.
So basically - Flash twrp - go to twrp - flash rom (pixel experience for example) - format data - and then reboot to recovery again?? what's the point sorry

oh man i missed up the format stuff.
Thank you very much. I made it. After format data then i insalled the pixel experience rom via adb sideload now it started let's see hows it the modding rom world on this device!

I followed all those steps. My phone boots, stays on Lineage logo for 4-5 minutes and then it reboots back to orange recovery. Any idea? Thanks!

Possibly bricked my poco f2 pro, is there a way to fix this?

Hi all.
Today I unlocked my phone to flash the crDroid rom. First I went into fastboot to flash mauro's twrp and that worked fine. Then I flashed the miui 12.0.3 full stock image from twrp, which might have been a mistake since I flashed the full image instead of an extracted vendor / firmware version. Then I wiped system, cache and data and flashed twrp but when I tried to boot the phone it went into an infinite boot screen. Then I wiped and flashed the whole stock miui image again in the hope that I would at least be able to boot miui but that also failed, since the phone kept booting back to recovery and there was no boot screen at all.
I have also tried flashing the stock image (ver 12.0.6) from fastboot but it fails because of the anti rollback check error. The image I tried to flash has an antirollback version of 0 while my phone has a version of 1, so "current device antirollback version is greater than this package" is what I got. Now my options are very limited because for some reason my laptop can't access the file system of the phone so I can't transfer files to the phone anymore and the ADB sideload feature from twrp is not working, so I only have fastboot (adb also won't recognize my device). What can I do to save my phone? Any help is greatly appreciated.

Flash the MIUI with MiFlash.

Had sort of the same issue...
Try using adbfastboot tool ( it's a java programme ) to swap recoveries.
I got the bootloop after installing the LOS recovery , installed twrp from adbfastboot tool and got it working.
Nice to have working recovery but since adb sideload is broken in twrp i needed LOS recovery.
Tried to reflash the LOS recovery from the tool and this time it worked

Flash with Miflash (the latest version https://xiaomiflashtool.com/ option CLEAN ALL) the rom that was on your phone when you bought it.
For the roms It is better to flash firmwares with Miflash because TWRP is not 100% functional.

grt67DFqyu said:
Flash the MIUI with MiFlash.
Click to expand...
Click to collapse
Man I can't believe such a simple suggestion would work but it did thanks! Initially I did not flash with miflash because it prompted me to install drivers and it crashed when I clicked the install button, turns out all I had to do was create a folder named log in the miflash directory lol. So flashing the stock image works. And it definitely boots correctly to miui with the clean all and lock option.
But now when I try to flash crdroid or pixel experience I still end up with an infinite boot screen even when using exactly the specified firmware :/ Like you see crdroid and pixelexp boot animations correctly but it lasts forever. I must be doing something wrong with the firmware still because that's the only reason I can think of why it won't boot. After I flash the firmware in miflash I don't have to boot miui up first right? I'm using the 'save user data' option in miflash if that matters.

In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?

NOSS8 said:
In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?
Click to expand...
Click to collapse
I'm now trying to flash crdroid. After flashing V12.0.3.0.QJKMIXM in miflash with flash_all, I formatted data in twrp (the one where you have to type yes) but also with a decrypt & normal factory reset I still get the same result. After the format, I flashed crdroid without magisk and gapps, and it'll just hang on the crdroid boot screen :/. The weird thing is, before I flash the crdroid rom it can boot in MIUI just fine and it'll show that it's indeed the correct 12.0.3.0 in the settings so I have no idea if it's just the crdroid ROM at this point.

Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).

NOSS8 said:
Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).
Click to expand...
Click to collapse
This ended up working perfectly Crdroid is now running like a charm with gapps and magisk. Thank you guys a lot for helping me out with this!

TWRP shows internal storage folders named as random letters.

I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help

does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)

User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password

#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.

the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.

User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though

Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse

Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully

Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD

#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!

#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?

you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.

I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine