Develop Bugs

SMT700 - Custom Rom /Installation/Backup

Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:

androidnoob222 said:
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
Click to expand...
Click to collapse
1. There is bootloops but hardbricks are rare. You can enter recovery and download mode(flash stock rom on broke os) in a bootloop. Just hold power, home or vol up for recovery and home +power +vol down for download mode.
2. Yes you can go back to any version of stock os unlike apple you have to be on the latest. The files are online for your device at sammobile. (google it) and also samsung updates.
3. All you need to perform a custom rom flash is a custom recovery called twrp and your device. Theres an app on google play for installation of it. (search on youtube on how to do so). But thats just flashing zip based roms(which most custom roms are). For stock rom installation, you will need a pc and a application called odin 309 to flash a stock md5 file rom in which you will need to be in download mode (like installing new update from itunes).
You will need to backup your whole rom with twrp before flashing a custom rom. You may need a micro sd if your short on space. You will also need to be rooted to install custom roms. Please go to the cfautoroot thread of your device to root your device in which you will viod warrenty.
4. Cm rom as of now still has bugs but is still useable for games and such. There should be a list of bugs on the thread and might have some missing features such as ir blaster and finger print scanner. Battery life may vary. So there are downsides.
5. I can go into more depth of custom stuff and flashing if you wish. Right now my fingers hurts xD. Hope this helps!

1) it is very, very unlikely even if you try intentionally to do so
2) yes, no problem. google for Samsung Firwares, it's all online
3) windows PC, Odin Software, and an USB cable, that's all. You can do it with Linux if you prefer. Some Roms are installed via zip file from the device itself, then you need to flash a new Recovery partition first, that is able to do so
4) ?

Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:

androidnoob222 said:
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
Click to expand...
Click to collapse
1. Sometimes odin and kies will fail for you. Twrp backups is to be really safe if you get bootlooped and odin fails for you. Its much easyer to restore a twrp backup and easy to make one. Its just if odin or kies fails which twrpnwould be your only hope. Just in case
2. Cfautoroot only flashes supersu and root. It keeps your apps and everything. So when you flash cfautoroot, it will say andriod is upgrading becuase its installing root and restoring back your apps.
3. After a full proper reset, it will not have root and revert back to stock. Thats where you flash cfautoroot to gain root again!
Hope this helps!

So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?

androidnoob222 said:
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
Click to expand...
Click to collapse
Most custom roms are to be flashed with twrp. Meanwhile stock roms/md5 is to be flashed with odin(firmware from website).

Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?

androidnoob222 said:
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
Click to expand...
Click to collapse
2.8 is the latest version of twrp. I dont think your device is klimwifixx. It should be klimwifi. What the wipe and and factory reset in twrp does is that it clears all your apps and wipe cache. It does not wipe any folders and it justs wipes your apps. So internal should not be affected unless you formatted it... You just need to swipe the factory reset on it when installing roms. For google play store you have to flash a file name gapps. There should be a link to it on the thread. To get into recovery, turn off your device, then hold power, home, vol up buttons at the same time to enter recovery. To exit recover just touch the reboot rectangle and hit reboot system. Hope this helps!

Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things

androidnoob222 said:
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
Click to expand...
Click to collapse
No no! Twrp replaces stock recovery. Download mode cannot be replaced. You enter it by holding power, vol down, home button when the device is off. Download mode is when you flash things. Recovery mode is when you clear cache or other stuffs. I have no idea with the linux stuff you explained but custom zip roms just adds some modifications and other stuff to the device. You would need to clear cache and factory reset so you wont have problems installing it. You can easyly go back to stock rooted by restoreing a backup you made in twrp. It has to do something with img and replacing those if thats what your talking about idk. No need to format as the rom add things to it. Just need to factory reset and cleae caches.

But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..

androidnoob222 said:
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
Click to expand...
Click to collapse
It shouldnt be as twrp only replaces recovery. Img did you try doing home, power, vol down?

Hi
I have a quick question I have the Galaxy tab S 10.5 wifi and was wondering can I install TWRP without the tablet being rooted?
Also there are some builds where it states that its rooted, debloated and de-knocked. Does this mean that they can be flashed without rooting the tablet and tripping knox.
Thanks for your replies, still trying to get my head around this.

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
​So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
​I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.

You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.

Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.

If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?

mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.

tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?

mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.

TWRP for X2 / X2 Pro - what's needed?

I know there is currently no TWRP for the X2 / X2 Pro devices.
But I wonder why / if it is so difficult to generate one?!
What do the TWRP developer need to create one?
A dump of the recovery partition? Should be possible with root - or not?
(BTW, which of the devices _is_ the recovery partition?)
What else is needed?

Bodenseematze said:
I know there is currently no TWRP for the X2 / X2 Pro devices.
But I wonder why / if it is so difficult to generate one?!
What do the TWRP developer need to create one?
A dump of the recovery partition? Should be possible with root - or not?
(BTW, which of the devices _is_ the recovery partition?)
What else is needed?
Click to expand...
Click to collapse
I would start here: https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Or if you speak Spain go to:
https://www.htcmania.com/showthread.php?t=1312725
Maybe member @nuv can help you as well.

AndroidenKalle said:
I would start here: https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Or if you speak Spain go to:
https://www.htcmania.com/showthread.php?t=1312725
Maybe member @nuv can help you as well.
Click to expand...
Click to collapse
Hi @Bodenseematze,
uh, well; unfortunately I got no X2 and do not know anything about the partition structure.
I didn't compile TWRP myself (e.g. for my X Pro ), so I can't give you hints about that either :crying:
The first link from @AndroidenKalle looks promising, I would start reading there.
If BQ doesn't change the way their phones handle the firmware, the bootloader locking and so on, maybe I can help in the later steps after building TWRP (?)...
edit: if you don't need TWRP but only Magisk, maybe take a look here: https://forum.xda-developers.com/aquaris-x-pro/how-to/root-magisk-bq-aquaris-x2-pro-custom-t3841795

Thanks for your answers.
I'm not sure if compiling TWRP from sources is the right direction for me :silly:
And the guide is really old - I'm not sure if it's still valid (especially because the X2 Pro is such a "a/b"-Device.
I thought about trying this:
[GUIDE]Porting TWRP without source
But I'm not sure about which partition I should use - or if the correct (recovery) partition is included in an official update.
I only see the boot.img - but as opposed to the above source porting guide our device has also two (_a/_b) of them...
And I'm also not sure which existing twrp binary I should use as base (arm64 and 1080x2160 screen resolution and maybe _a/_b support?)...
@AndroidenKalle: unfortunately I'm not able to speak Spanish...
And yes, of course I already have rooted my device with Magisk - but I really want to have TWRP possibilities (easily create flashable backup image, restore image without losing my data, easy flashing, easy access to all partitions, ....)

Apparently, there is a TWRP from aquaris-dev, downloadable from their Slack:
https://join.slack.com/t/aquaris-de...QyMWIwZTk4ZjllYjMxZWJhYzM0YzNhZWZkYTEwMzQ5ZDQ

Yes, that one seems to work at my X2 Pro device (tried with fastboot).
Soon after start it asks for a password when trying to mount the partitions.
In principal that's to decrypt the encrypted stock partitions - but that functionality is currently not available - so to install lineageos this TWRP is fine - for everything else (e.g. to make a backup of your stock image) not...

FAILED (remote: sparse image size span overflow.) error

Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
I recently wanted to give some GSI images a try and tried to flash AOSP. I tried to flash the system image using fastboot and also SP Flash Tool (of MTK). Both gave me the same error:
FAILED (remote: sparse image size span overflow.)
After getting this error, i reset my phone and my default system is still there, so nothing is being written to the system partition. I thought maybe treble AOSP images are larger than my phone's system partition but when i checked, the default system img of my phone is actually larger than the GSI images (I have also tried a "go" version of a gsi image with the same outcome).
What is my problem here please?
PS: My bootloader is unlocked.

What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.

Chaos Storm said:
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Click to expand...
Click to collapse
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?

twilightened said:
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
Click to expand...
Click to collapse
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.

Chaos Storm said:
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?

twilightened said:
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
Click to expand...
Click to collapse
No, you are doing it correctly. I think they compress them to save bandwidth.

just need to resize that partition

twilightened said:
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
Click to expand...
Click to collapse
Which device? Please tell.
I have also Blackview A20 (go).
Flash stock with spflash. Only for stock
Let it reboot. reset. Allow it to reboot once again. Check everything GPS/wifi/bt. Enable ON
Do not connect to Google accounts. not needed.
Enable adb
Charge at least 90% - some devices will NOT flash and silently ignore.
fastboot erase system
fastboot flash system gsi.img
fastboot reboot
If it asks you a password, just type anything. Then it will ask you reset phone. Say OK.
all done
Note always check the sha1sum or md5sum of GSI. Despite having

kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
Excuse me, I'm new to this, would you have a tutorial? I have several phones that would help

kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
how can i resize the partition pls?

Question Mi 11x (aliothin) not booting after updating xiaomi.eu rom through twrp

I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.

Try going into BOOTLOADER to use fastboot instead of fastboot(d), if at all possible.

force reboot to twrp
then wipe cache, select reboot then select system

Raunaksaha2008 said:
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Click to expand...
Click to collapse
I'm glad you posted this, I did the exact same thing yesterday and had the exact same problem. I'm Normally extremely experienced with this stuff I've even made custom roms. This one caught me off guard because I've only had the phone 2 weeks and this was the 2nd custom rom I flashed. Long story short nothing worked and I had to flash miflash stock firmware. Than I tried it again and it did it again. So I flashed the zip before I was already on and everything worked. I don't understand backups with this phone sometimes they backup but I don't believe they will work to restore.
I have never had to say this, there is nothing you can do. You have to flash stock and go back it sucks and I hate it but it is what it is.

hroen_al said:
force reboot to twrp
then wipe cache, select reboot then select system
Click to expand...
Click to collapse
Tried, didn't work

Raunaksaha2008 said:
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Click to expand...
Click to collapse
now its not booting into recovery. only fastboot. run twrp bat command file is not working with it anymore.

Raunaksaha2008 said:
now its not booting into recovery. only fastboot. run twrp bat command file is not working with it anymore.
Click to expand...
Click to collapse
could boot into recovery. backed up whatever i could. flashed fastboot xiaomi.eu rom without data wipe (upgrade mode). System was showing issues - permissions stopped working, couldnt find refresh rate settings, apps were misbehaving, general lag. Now trying to flash again with data wipe. If nothing else works, have to go back to original stock rom with mi flash.

Raunaksaha2008 said:
could boot into recovery. backed up whatever i could. flashed fastboot xiaomi.eu rom without data wipe (upgrade mode). System was showing issues - permissions stopped working, couldnt find refresh rate settings, apps were misbehaving, general lag. Now trying to flash again with data wipe. If nothing else works, have to go back to original stock rom with mi flash.
Click to expand...
Click to collapse
Well did it work or did you have to go back to stock? I told you nothing works and I'm not lying I'm extremely experienced with this stuff. I root every device I can get my hands on. This phone is beyond difficult to flash roms with. The problem is you really need to go back to stock everytime you flash a custom rom to make sure it works.
I know when I said my first comment your hoping to god that you don't have to start from scratch but I tried a bunch of stuff to I just didn't feel like explaining it all. I flashed both twrps and tried I reflshed the rom and I did format data and still didn't work. It screws up the system partition layout and nothing reads right.

Went back to stock. Android 12 on xiaomi.eu rom doesn't have refresh rate settings and we are stuck on 60Hz. And also backing up, restoring everytime is a pain and waste of time. Will stick to stock for now.

Raunaksaha2008 said:
Went back to stock. Android 12 on xiaomi.eu rom doesn't have refresh rate settings and we are stuck on 60Hz. And also backing up, restoring everytime is a pain and waste of time. Will stick to stock for now.
Click to expand...
Click to collapse
I told you, I will say it again this phone for custom roms kinda sucks. It can be done but it's always you have to start from scratch Everytime and roll the dice and hope it works. Good luck I would still root stock though

The way everything breaks made me worried that the phone would hard brick if I kept trying stuff. Either that or some how wipe out fastboot and than it would be like a hard brick because nothing would work to fix it. It's a scary phone to mess with. The problem comes from the A/B partitions because XDA developers aren't really developers their just people who read online instructions on putting source code together and don't actually know how to code or fix anything. They get way to much credit. Topjohnwu is a real developer and that's why Google bought him

Facing issues again. Netflix app not showing in Play store. Device is not play protect certified even after flashing official Rom via mi flash.

Techguy777 said:
The way everything breaks made me worried that the phone would hard brick if I kept trying stuff. Either that or some how wipe out fastboot and than it would be like a hard brick because nothing would work to fix it. It's a scary phone to mess with. The problem comes from the A/B partitions because XDA developers aren't really developers their just people who read online instructions on putting source code together and don't actually know how to code or fix anything. They get way to much credit. Topjohnwu is a real developer and that's why Google bought him
Click to expand...
Click to collapse
i agree, flashing stock each time and booting once before flashing each custom rom seems the way to go. i know you're experienced - more than i - but in case you don't know... here's a couple of good apps for backing up apps etc that have worked well when moving from rom to rom (just save/copy whole swiftbackup folder with backed up apps to pc/laptop).
after moving rom, i select 'restore' from google backup but deselect apps (that's all done with seperate app below). that restores a fair bit, including some settings depending on the rom before and after flash. then install swift backup on my rooted device, copy swiftbackup folder back onto phone and restore apps with all data etc (+ anything else you have that didn't restore from google backup). swiftbackup can even backup and restore your wallpaper/screensaver, wifi passwords etc. it's so much better than the outdated titanium backup, which i find unreliable these days.
another alternative is alpha backup pro, another paid app but apparently worth it. sometimes it's on offer or free. i got it when it was free but haven't tried it as swift works well for me. alpha backup
note: i am not affiliated with either of these apps, just making you aware of a backup alternative as TWRP data backups, for me and with this phone, are a no go. also note, i don't backup system stuff when moving to a different rom, only installed apps.
like i say, no doubt you are aware of these options but thought i would post just in case.

reg66 said:
i agree, flashing stock each time and booting once before flashing each custom rom seems the way to go. i know you're experienced - more than i - but in case you don't know... here's a couple of good apps for backing up apps etc that have worked well when moving from rom to rom (just save/copy whole swiftbackup folder with backed up apps to pc/laptop).
after moving rom, i select 'restore' from google backup but deselect apps (that's all done with seperate app below). that restores a fair bit, including some settings depending on the rom before and after flash. then install swift backup on my rooted device, copy swiftbackup folder back onto phone and restore apps with all data etc (+ anything else you have that didn't restore from google backup). swiftbackup can even backup and restore your wallpaper/screensaver, wifi passwords etc. it's so much better than the outdated titanium backup, which i find unreliable these days.
another alternative is alpha backup pro, another paid app but apparently worth it. sometimes it's on offer or free. i got it when it was free but haven't tried it as swift works well for me. alpha backup
note: i am not affiliated with either of these apps, just making you aware of a backup alternative as TWRP data backups, for me and with this phone, are a no go. also note, i don't backup system stuff when moving to a different rom, only installed apps.
like i say, no doubt you are aware of these options but thought i would post just in case.
Click to expand...
Click to collapse
I am using swift backup right now actually as I was reading this and yes I do the same thing copy folder to the USB C drive. It's the only app I've bought in a year. Thank you for at least making a comment of some depth. I get burned out at xda because everyone doesn't say anything they just want answers for their problems and don't contribute to xda.
I did not know about the other app so I will be looking into it. Normally I wouldn't say this but buy Swift back and you get cloud storage. I'm like you I restore apps with an app and I will be using Xiaomi cloud now but also Google. Another app is migrate it's the best for flashing roms it restores your apps and data from twrp well not quite once you reboot.
I thanl you again because maybe I didn't know about Swift back it's important people respond.

Is 120Hz working on your mi11x with xiaomi.eu? It doesn't work on mine.

chratoc said:
Is 120Hz working on your mi11x with xiaomi.eu? It doesn't work on mine.
Click to expand...
Click to collapse
Yes it is, on the latest stable but not on the latest Android 12 beta.