Database Develop

I keep bricking my 9t pro, what's wrong ?

Hello,
I am trying to install lineage OS on my 9t pro, but it fails every time.
I managed to unrbick my phone thanks to miflash, but now i'm totally stuck
So, i'm on miui Global 11 QFKEUXM, and i can install twrp-3.3.1-22-raphael-mauronofrio.
Then, if I try to flash a rom with it (i also tried RevengeOS), i'm going to be stuck in a bootloop, until it goes to twrp again.
When it appens, i can't access files from my computer anymore, all folders seems to have random names like "uzehfj405Cuh5635azP5IUHDPuZ".
So i have to use miflash to go back to miui. I don't know what's wrong i've spent hours trying, can someone help me ?
Thanks and have a nice day
EDIT :
Indeed i didn't format data in TWRP. I tried to, and i'm still in that boot loop unfortunatly.
But this time, file system seems to be ok because i can access internal storage from my computer
EDIT2 :
I think the problem come from GAPPS. If i format then flash lineage without GAPPS, I can boot it
But if then i try to flash them, it won't boot anymore.
I am using the "nano" package here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Is this incorrect ?

hi,
have already format data in TWRP?

BuckyBucks said:
Hello,
I am trying to install lineage OS on my 9t pro, but it fails every time.
I managed to unrbick my phone thanks to miflash, but now i'm totally stuck
So, i'm on miui Global 11 QFKEUXM, and i can install twrp-3.3.1-22-raphael-mauronofrio.
Then, if I try to flash a rom with it (i also tried RevengeOS), i'm going to be stuck in a bootloop, until it goes to twrp again.
When it appens, i can't access files from my computer anymore, all folders seems to have random names like "uzehfj405Cuh5635azP5IUHDPuZ".
So i have to use miflash to go back to miui. I don't know what's wrong i've spent hours trying, can someone help me ?
Thanks and have a nice day
Click to expand...
Click to collapse
See bro When we buy the android the the storage is
Encrypted , when you unlock the bootloader and install TWRP it doesn't decrypt the internal storage that's why only the stick rom i.e. Miui can access the storage , here is what you need to do ..
Install TWRP then go to wipe then click on format data and type yes this will decrypt the internal storage and so that any custom rom you install can access the data ..
Make sure that you format data then reboot trwp and then connect the phone to of transfer the files and install the rom and gappa it will boot just fine
Although for some reason when i install the LOS my storage gets decrypt again I say you try the EvoX rom which doesn't require gappa just flash the rom and the firmware
Also there is some force decrypt zip file that lets you decrypt the internal storage because sometime install the firmware may encrypt your storage again so flash that DFE file you will find that in telegram grp ..
Basically you can't boot into rom and see files on computer cause your storage is encrypted and only Miui can decrypt it unless decrypted ...
Hope it help

Every time when you want to flash aosp or other custom rom you need to format data ( wiping isnt enough because of encryption) when coming from stock miui or miui eu rom.
Best way is to read instruction of rom you want to install.
My steps are when coming from stock miui:
Install twrp
Boot to twrp
Format data with yes
Reboot to twrp
Copy rom you want to install to internal storage, usually you need also rom+vendor file of latest stable miui.
Flash vendor+rom of stable miui
Wipe dalvick+ cache
Flash custom rom (los, evolutionx...)
Wipe dalvick+ cache
Flash gapps if needed
Wipe dalvick + cache
Reboot to system, set your system to your liking
Then reboot to twrp to flash magisk ( if you like to be rooted, otherwise continue to use rom as is)
Best is to read install instructions of rom you want to install

ranjan_shivam said:
See bro When we buy the android the the storage is
Encrypted , when you unlock the bootloader and install TWRP it doesn't decrypt the internal storage that's why only the stick rom i.e. Miui can access the storage , here is what you need to do ..
Install TWRP then go to wipe then click on format data and type yes this will decrypt the internal storage and so that any custom rom you install can access the data ..
Make sure that you format data then reboot trwp and then connect the phone to of transfer the files and install the rom and gappa it will boot just fine
Although for some reason when i install the LOS my storage gets decrypt again I say you try the EvoX rom which doesn't require gappa just flash the rom and the firmware
Also there is some force decrypt zip file that lets you decrypt the internal storage because sometime install the firmware may encrypt your storage again so flash that DFE file you will find that in telegram grp ..
Basically you can't boot into rom and see files on computer cause your storage is encrypted and only Miui can decrypt it unless decrypted ...
Hope it help
Click to expand...
Click to collapse
Hello, thanks for taking the time to help me. I tried again formating the data, it seems a bit better (i can acces file system from my computer), but i'm still in that boot loop :/

BuckyBucks said:
Hello, thanks for taking the time to help me. I tried again formating the data, it seems a bit better (i can acces file system from my computer), but i'm still in that boot loop :/
Click to expand...
Click to collapse
Maybe it's the vendor. What device do you have (china, global, etc.)?

ef1x said:
Every time when you want to flash aosp or other custom rom you need to format data ( wiping isnt enough because of encryption) when coming from stock miui or miui eu rom.
Best way is to read instruction of rom you want to install.
My steps are when coming from stock miui:
Install twrp
Boot to twrp
Format data with yes
Reboot to twrp
Copy rom you want to install to internal storage, usually you need also rom+vendor file of latest stable miui.
Flash vendor+rom of stable miui
Wipe dalvick+ cache
Flash custom rom (los, evolutionx...)
Wipe dalvick+ cache
Flash gapps if needed
Wipe dalvick + cache
Reboot to system, set your system to your liking
Then reboot to twrp to flash magisk ( if you like to be rooted, otherwise continue to use rom as is)
Best is to read install instructions of rom you want to install
Click to expand...
Click to collapse
djoni wallauer said:
hi,
have already format data in TWRP?
Click to expand...
Click to collapse
Thanks to both of you for helping me. As i sayed, I tried to to so and now i can see the filesystem from my computer, but i'm still stuck in the bootloop

Isley_ said:
Maybe it's the vendor. What device do you have (china, global, etc.)?
Click to expand...
Click to collapse
I think it's a global one, but now i have doubts... Is there a way to be sure ?
In the MIUI i managed to flash with miflash, it's sayed MIUI GLOBAL

vladsendrix said:
if it s a mi9t pro its probbably the global version, to make sure try downloading the firmware and vendor from here https://downloads.akhilnarang.me/MIUI/raphael/ . try downloading the global and indian version and try both since you dont know whihch model you have. also dont forget to format before trying anything. hope i helped
Click to expand...
Click to collapse
I'm a bit affraid to flash indian version, it's says to not cross flash ^^

I’d flash MIUI.eu before lineage, let it boot and then do the whole process to install lineage. Yo don’t have nothing to lose.

vladsendrix said:
well i d rrecommen you put your device in fastboot, go to aXiaomiADBFastbootTools and it ll show you your model number or use TOOLSALLINONE. Search ythese on xda and youll find the links and that will definetly show you your model number
Click to expand...
Click to collapse
What fastboot commands should I use to get the model number ? I tried fastboot oem get-psid but it didnt work
When I boot MIUI, in the settings its "MIUI GLOBAL QFKEUXM". So it's correct isn't it ?

vladsendrix said:
well i d rrecommen you put your device in fastboot, go to aXiaomiADBFastbootTools and it ll show you your model number or use TOOLSALLINONE. Search ythese on xda and youll find the links and that will definetly show you your model number
Click to expand...
Click to collapse
I think the problem come from GAPPS. If i format then flash lineage without GAPPS, I can boot it
But if then i try to flash them, it won't boot anymore.
I am using the "nano" package here https://sourceforge.net/projects/ope...beta/20191114/
Is this incorrect ?

How to Revert back to Pie custom ROM from 10 custom ROM?

I've tried a couple of 10 ROM but, as far as i see, there're still too many bugs that makes very unpractical for me to use android 10 as a daily driver.
I'm planning to revert back to a pie custom ROM but I'm worried that I might overlook something.
I know that I have to backup some partiotins (persist? EFS? something else? in 10 in order to restore them in Pie, but I'm not sure wich partiotions and how to restore them (before flasing the new ROM, after flashing the new ROM, should I change the active slot?)
Can someone please give me some advices?
Thank you in advance

Don't do anything you Use mi flash tool for android 10 to move android 9 i do tow time and it working for me know am using android 9 pie.

Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you

Malobestino said:
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Click to expand...
Click to collapse
to start backup everything and put on pc with usb cable ..
better just flash a recovery.zip of miu pie or oreo or even custom
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
custom pie and stock pie are pretty stable ..
remember if going for miu get recovery flashable zip and flash twrp image again after flashing rom..boot straight into recovery ...flash magisk ..use stock

Thank you for your detailed answer
Just a couple of more questions
KevMetal said:
better just flash a recovery.zip of miu pie or oreo or even custom
Click to expand...
Click to collapse
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
Click to expand...
Click to collapse
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
Click to expand...
Click to collapse
Can I just restore my persist backup from within TWRP?
Thank you again for your patience

.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries

KevMetal said:
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
Click to expand...
Click to collapse
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help

Malobestino said:
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Click to expand...
Click to collapse
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .

KevMetal said:
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
Click to expand...
Click to collapse
Im' also quite convinced that is something related to the ROM or the kernel. Fro the time being isn't that big of an issue. I will look into it in the next days
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
Click to expand...
Click to collapse
Apparently this issue resolved during nightime by itself.
My theory is that the autobackup during last night realigned automagically the app (which doesn't make a lot of sense, but I don't really know how whatsapp's backup works, what it writes or read to the gdrive backup).
Anyway I really appreciated your help, thank you again

Question Bootloop at MIUI logo after twrp restore attempt

Hi all and thanks in advance for the possible help. I tried to to move from EU stable to EU weekly formatting data, using TWRP...but I forgot to make some backups so I tried to restore from a TWRP backup of the stable and from then bootloop on the miui logo (I can go to fastboot and recovery). The problem is that I tried a lot of things and also asked help to the russian guy paying money for nothing. I can flash with fastboot, miflash, twrp...different roms, no way...after 3-4 minutes from reboot bootloop at the miui logo (not mi logo)...please help. I can pay obsiously for the job...I forgot to say that I hav a China 512gb

lukemo said:
Hi all and thanks in advance for the possible help. I tried to to move from EU stable to EU weekly formatting data, using TWRP...but I forgot to make some backups so I tried to restore from a TWRP backup of the stable and from then bootloop on the miui logo (I can go to fastboot and recovery). The problem is that I tried a lot of things and also asked help to the russian guy paying money for nothing. I can flash with fastboot, miflash, twrp...different roms, no way...after 3-4 minutes from reboot bootloop at the miui logo (not mi logo)...please help. I can pay obsiously for the job...I forgot to say that I hav a China 512gb
Click to expand...
Click to collapse
so you want to running eu weekly with data backup on eu stable ? that's what u wanna try to say right ?

howdeedodat said:
so you want to running eu weekly with data backup on eu stable ? that's what u wanna try to say right ?l
Click to expand...
Click to collapse
I wanted to...at the moment every ROM is good for me...but I was able to move, the problem came after I tried to restore the stable with twrp...error during efs2 restore...

deleted

lukemo said:
I wanted to...at the moment every ROM is good for me...but I was able to move, the problem came after I tried to restore the stable with twrp...error during efs2 restore
Click to expand...
Click to collapse
I think EU stable data partition file system is different than on the EU weekly, that's why developers of EU ROM advice to format data when you are moving from stable to weekly. Not sure for 100% but before data format was mandatory when switching EU branch. And TWRP when you make backup (its save's data + partition file type?).
Can you do a test ? Just flash EU weekly and then boot up phone, if everything is ok, go to TWRP and restore backup from stable.
If you end in bootloop, go to TWRP and FORMAT data only, if phone boots up, that's mean data backup is problem (different file system type?)

veimus said:
I think EU stable data partition file system is different than on the EU weekly, that's why developers of EU ROM advice to format data when you are moving from stable to weekly. Not sure for 100% but before data format was mandatory when switching EU branch. And TWRP when you make backup (its save's data + partition file type?).
Can you do a test ? Just flash EU weekly and then boot up phone, if everything is ok, go to TWRP and restore backup from stable.
If you end in bootloop, go to TWRP and FORMAT data only, if phone boots up, that's mean data backup is problem (different file system type?)
Click to expand...
Click to collapse
Dear veimus, I thank you so much for the suggestion, but no way trying to flash back the last weekly for twrp...the only thing I didn't try was a fastboot weekly version...but I tried adb flash, twrp, miflash pro with fastboot china and global and no way....

TWRP Bootloop

When I try to install a ROM, no problem installing TWRP and flashing a ROM.
But when I restart, whatever the ROM it systematically restarts on TWRP.
Everything is back to normal when I reinstall the MiUi ROM.
I installed vbmeta, TWRP is kept even with the MiUi ROM.
I tried to install a ROM on MiUi but nothing happened, TWRP is launched systematically after restarting.
I tried with several versions of TWRP but nothing worked.
Also with LOLz kernel with and without; and Magisk too.

Sleep on it !
you have to format DATA and not Wipe !

Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.

1999romelx said:
Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.
Click to expand...
Click to collapse
wrong subforum, heres the poco x2 subf
Xiaomi Poco X2
The Xiaomi Poco X2 is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm SDM730 Snapdragon 730G chipset is paired with 6/8GB of RAM and 64/128/256GB of storage. The main camera is 64+8MP and the selfie camera is 20+2MP. The battery has a 4500mAh capacity.
forum.xda-developers.com
sounds like your data got wiped, thats why theres only a twrp folder in internal. you should prolly full flash a fastboot rom since you mightve missed a few important steps

Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?

johndaog said:
Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?
Click to expand...
Click to collapse
sorry for the super late response
its supposedly for bypassing android verfied boot (avb). it blocks unauthorized roms from booting. if you search for 'what is vbmeta', we literally get no info at all and mainly speculations (no official docs etc). imho it does seem true

Question [CLOSED] Need Nvdata & Nvram backup from TWRP of Redmi Note 10S (Rosemary)

Can anyone help me with the backup of "Nvdata" & "Nvram" taken from TWRP recovery so can restore it at my end..?
I accidentally screwed IMEI & somehow managed to restore it but now getting "nv data corrupted" error with a bootloop of MIUI logo & figured out that with this method of restoring Nvdata & Nvram via TWRP can help me in fixing this issue of same model..
Thanks a lot in advance..
PS : I'm on Global Stock ROM V13.0.8.0.SKLMIXM on Indian Version of Redmi Note 10S (Rosemary).

why make another post for the same issue as before?

Thread closed since the topic already exists here.
-Regards: Badger50