Related
How to Fix for WIERD LOCKSCREEN BUG on Android 8 and + custom roms
Many of them are facing this Bug after setting up Lockscreen, after few reboots we face System UI FC when entering Unlock code or pattern. This bug is faced when using Oreo, Pie and 10. And this bug is not present on Nougat.
Warning You will loss your all data including your device internal storage and i will be not responsible for any bricks if it happens on your device
Steps :-
Step 1 :- First of all Download MIUI global stable FASTBOOT ROM from the link http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Step 2 :- download mi flashtool and install on your pc and extract fastboot_rom.tgz to a folder.
Step 3 :- Important to have Official Unlock, if you are Unofficially unlocked try this method :- https://forum.xda-developers.com/re...icially-unlock-bootloader-redmi-note-t4009799
Step 4 :- Now copy userdata.img and persist.img from images folder to minimal adb and fastboot folder.
Step 5 :- Now open command window and write following commands -
fastboot erase persist
fastboot erase userdata
fastboot flash persist persist.img
fastboot flash userdata userdata.img
Step 6 :- Now "clean" flash a custom rom 8 or above it. And check whether this bug is still present of not. If you still face the bug then once flash full MIUI through Mi flash tool and repeat Step 5. Note :- After repeating Step 5 don't boot back into MIUI. After performing Step 5 quickly flash twrp and wipe MIUI and flash Custom rom.
Step 7 :- The bug will be gone.
I have made it easy.
If you guys have any Problem regarding this Pm or contact me on telegram my account @sk_ik_27400
Enjoy Flashing:fingers-crossed:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
arnabbandopadhyay said:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
Click to expand...
Click to collapse
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Ishaan Kaushal said:
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Click to expand...
Click to collapse
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
arnabbandopadhyay said:
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
Click to expand...
Click to collapse
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
It was probably magisk issue
nathanchance said:
also @D-m-x (and everyone else), please try this Magisk build (it can be installed in the modules tab in Magisk Manager)
https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
It includes a commit that should fix all of the weird issues with Magisk like the PIN not being accepted after a reboot or the phone getting stuck at the Google logo with the progress bar. The root cause is services crashing during the boot chain and either causing deadlock or lack of functionality. It's entirely possible that a service crashed during boot and started causing issues.
Click to expand...
Click to collapse
Please refer to this post if you have magisk installed. thanks to @nathanchance
Ishaan Kaushal said:
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
Click to expand...
Click to collapse
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
arnabbandopadhyay said:
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
Click to expand...
Click to collapse
ok :good:
Dims_Camper said:
Please refer to this post if you have magisk installed. thanks to @nathanchance
Click to expand...
Click to collapse
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Ishaan Kaushal said:
ok :good:
Click to expand...
Click to collapse
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
arnabbandopadhyay said:
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
Click to expand...
Click to collapse
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Ishaan Kaushal said:
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Click to expand...
Click to collapse
I use but coudn't start my phone now, I am uploading pic
Ishaan Kaushal said:
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Click to expand...
Click to collapse
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
i am not able to see any screenshots attach again
Dims_Camper said:
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
Click to expand...
Click to collapse
ok:good:
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Ishaan Kaushal said:
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Click to expand...
Click to collapse
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
arnabbandopadhyay said:
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
Click to expand...
Click to collapse
bro its better u contact me on telegram it will better to help Your there
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
Your device is encrypted!!!
Format data through recovery.
nilesh8343 said:
Your device is encrypted!!!
Format data through recovery.
Click to expand...
Click to collapse
doing this only produces lock screen bug
Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.
Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something
Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .
Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.
Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)
I am not expert on that field but from my knowledge try booting twrp and copy all your files to your pc or laptop (the one you need at least for saving some photos or videos ) then flash a fastboot ROM
And as I said from my knowledge not sure there might be other ways
testemailmailx said:
Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)
Click to expand...
Click to collapse
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...
Micdu70 said:
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...
Click to expand...
Click to collapse
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)
testemailmailx said:
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)
Click to expand...
Click to collapse
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo
batman957 said:
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo
Click to expand...
Click to collapse
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?
testemailmailx said:
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?
Click to expand...
Click to collapse
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )
batman957 said:
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )
Click to expand...
Click to collapse
I could make it work easily, but I want keep that step as final step cuz will wipe everything
testemailmailx said:
I could make it work easily, but I want keep that step as final step cuz will wipe everything
Click to expand...
Click to collapse
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) ? then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode
batman957 said:
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode
Click to expand...
Click to collapse
God bless us
I’m not using custom rom at all
BTW is there any way to delete twrp recovery without delete system ?
Did you by any chance flashed with the greek TWRP? I got the same bootloop so I get back to miui 10 official global version (the one I updated from) and it booted alright without wipe needed...
I'll try other TWRP versions as well though but right now I don't think I wanna update :|
Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3
sijav said:
Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3
Click to expand...
Click to collapse
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?
m-Khadem said:
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?
Click to expand...
Click to collapse
Here is patched vbmeta for davinci (K20/Mi 9T) => https://drive.google.com/file/d/1IC78J20ovcZudWYlijgSGdjeP6D3hx2V/view?usp=sharing
hello everybody
I was on the Android version 10 global version 11.0.4 ,I decided to download ExtendedUI OFFICIAL ROM, the bootloader was unlocked, then I Installaled the recovery , so i waiped system ,chash and date
by mistake i restart my phone , when i did that every thing is gone and the only thing that works is fastboot .
i tried everything nothing is worked .
please guys help me what should i do?:crying:
abood.mhd said:
hello everybody
I was on the Android version 10 global version 11.0.4 ,I decided to download ExtendedUI OFFICIAL ROM, the bootloader was unlocked, then I Installaled the recovery , so i waiped system ,chash and date
by mistake i restart my phone , when i did that every thing is gone and the only thing that works is fastboot .
i tried everything nothing is worked .
please guys help me what should i do?:crying:
Click to expand...
Click to collapse
Reflash the official twrp and flash the extended ui ROM. It isn't bricked
This happenned to me too.
If you can't boot or flash twrp via fastboot in this state (It wouldn't work for me), download and flash the fastboot ROM for your device and use the flash_all script (careful NOT to use flash_all_lock!!!!!). It'll go back to stock and keep the bootloader unlocked so you can flash TWRP and start over.
Benfatica said:
Reflash the official twrp and flash the extended ui ROM. It isn't bricked
Click to expand...
Click to collapse
how can i do that?
ShiningScias said:
This happenned to me too.
If you can't boot or flash twrp via fastboot in this state (It wouldn't work for me), download and flash the fastboot ROM for your device and use the flash_all script (careful NOT to use flash_all_lock!!!!!). It'll go back to stock and keep the bootloader unlocked so you can flash TWRP and start over.
Click to expand...
Click to collapse
can you please tell me exactly how to do this ? whech app is that?
thank you guys i did it lol
Is it possible to downgrade from 11 to 10 without twrp? And without wiping my phone?
You will be wiping your phone if you want to downgrade from A11 to A10. No way around it.
Hi , how I can go back to A10 please ?
No. Downgrade will wipe all in youre phone, but it can be done just by flashing downgrade rom with Settings > System updates > Local Upgrade.. No twrp needed.
Can I have link for your method please ?
I really want to go back in A10 , android 11 is **** even if I need to wipe my phone
"Downgrade zips (will wipe your data)"
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Choose the one for the region you live in !
Thanks bro it's working
The MSM tool is a way back. Never done it but should be safe.
dladz, my friend, MSM is the ultimate resort, when you got booboo..
1.Downgrade rom
2.FastBoot rom
3.MSM tool
I am on stable Android 11 , want to downgrade to 10 . Do i need to download the downgrade zip file or the regular os file will work ? Downgrading from Stable 11 to Stable 10.
Thansk
OPOmaniac said:
Is it possible to downgrade from 11 to 10 without twrp? And without wiping my phone?
Click to expand...
Click to collapse
letscheckitout said:
I am on stable Android 11 , want to downgrade to 10 . Do i need to download the downgrade zip file or the regular os file will work ? Downgrading from Stable 11 to Stable 10.
Thansk
Click to expand...
Click to collapse
MsmDownloadTool is the best way I found to downgrade from OOS 11 to 10. I have tested on OP8P. If you use the tool your data will be lost.
null0seven said:
dladz, my friend, MSM is the ultimate resort, when you got booboo..
1.Downgrade rom
2.FastBoot rom
3.MSM tool
Click to expand...
Click to collapse
Ha.
I'll be honest I've never used it pal.
Seems to be the only way without twrp.
The times I've not been able to boot I've just wiped system. Always does the job.
I used a few times Downgrade, FastBoot rom, MSM on my OnePlus phones, since OP3 to OP 8 Pro. All of these are Life Savers.
And i did a clean flash all the time, till the latest 2 phone models.
null0seven said:
I used a few times Downgrade, FastBoot rom, MSM on my OnePlus phones, since OP3 to OP 8 Pro. All of these are Life Savers.
And i did a clean flash all the time, till the latest 2 phone models.
Click to expand...
Click to collapse
Sometimes you will need to use MSM Tool.
It's possible to break only one partition and there is only one way with MSM to fix that. Even fastboot rom or OTA won't fix that. I had that once with my OP7T and also saw some other guys reported that issue.