Develop Bugs

Rooting and Modding questions. Final Check

So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201

You dl'ed android sdk yet or all the fastboot files you need?
Sent from my Galaxy Nexus using xda premium

You have it correct. Use titanium backup to save all your app data. And you have to restore a nand backup if you want to undo a mod you flashed. The mod usually instructs you to backup right before flashing, so you can just revert right back if you want.
I wouldn't worry about ota anymore. Being rooted always leads to you being able to flash the latest ota quicker than if you were stock and waiting for your number to be called. Trust me after years of this that's how it always happens.

corban227 said:
So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.

efrant said:
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.
Click to expand...
Click to collapse
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus

corban227 said:
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you are asking that question, more reading is likely in order before you start flashing things.
But anyway: a stock ROM is the ROM Google puts out. They are found here, and instructions on how to flash are in my signature. All other ROMs are custom ROMs.

Gotcha. Ill look it up tonight
Sent from my Galaxy Nexus

I ended up reading more which lead to me unlocking and installing 4.0.4
Im happy with this now and I dont feel the need to custom mod. I need my phone to be functional all the time with out being too time consuming =D thanks for the help and leading me to my conclusion

I would seriously give aokp a try, I promise its worth it. Its the same as stock there's no extra work needed or anything to worry about or deal with. Its that good.

Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.

biffsmash said:
Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.
Click to expand...
Click to collapse
I wouldn't recommend re-locking your bootloader if you have unlocked it. Actually, I would recommend that, every time you buy a Nexus device, the first thing you should do is unlock the bootloader. Don't forget, having an unlocked bootloader does not mean you are not "stock". An unlocked bootloader doesn't affect anything (aside from what I mentioned below).
Why you ask? Good question:
Advantages of a locked bootloader
If you lose your device, no one can easily access your data, but only if, in addition to your bootloader being locked, you have the stock recovery installed AND you have USB Debugging disabled AND you have a password on your device. However, this "risk" (if you can call it that) can be mitigated by many apps that can remotely wipe your device.
Disadvantages of a locked bootloader
You cannot use fastboot commands, so you cannot flash or boot images, which can save your butt in certain occasions.
You cannot try out new radios (assuming no root).
You cannot backup your data (i.e., make an image of your device's memory (assuming no root).
You cannot root (on 4.0.4 and later).
You cannot manually update to the latest version of Android once Google starts rolling it out. You have to wait until Google decides it's your turn, which could be minutes to months after the update becomes available.

+1 to working without me thinking. I'm leaving the boot loader unlocked to install any updates Verizon doesn't push through but other than that its staying stock. Plus I really like vanilla ICS AS IT IS
Sent from my Transformer Prime TF201 using Tapatalk 2

Please help....How to wipe everything out and start from scratch?

Hi All,
I have been having some issue with one of my box, it is rooted running stock version 51.1.0.1 .
i have completed the following steps of the rooting process.
1) block updates on router
2) rooted (installed towleroot, supersu, busybox)
3) disabled update on AFTV box via adb command
4) Unlock partial bootloader
5) installed latest CWM at this point fire tv restarts but does not boot up in to CWM recovery.
I can get into CWM via Alt + prntscr + i using my keyboard. i did the wipe data/factory reset thru CWM and it clean up everything i rooted again installed CWM and it still wont boot up in CWM so may the firmware is corrupt?
What should i do? Should just flash pre roted rbox ROM and installed Rbox boot menu and see if i can get in CWM or should i wipe everything from AFTV and start again.
How do i wipe everything out using CWM? I read a lot tread on xda forms but didn't see a detail guide, i would appreciate if someone could give me all the baby step in exact order i should perform and if you could use the same terminology that is used in CWM menu that would be great, please.
Please note i have rooted at least 8 box before (updates blocked, rooted, bootloader unlock, install cwm, installed pre-rooted ROM and Rbox manu) so i am familiar with the process but one can always mess up.
Thank you

You're approaching this in a differnt angle than I'm used to--is there a reason you use stock firmware? With custom recovery, I'd venture to say a factory reset will do what you want it to and performing it will give you a clean slate and though updates will try to download they won't install.
I do this but I run rbox firmware...
1. Reboot recovery
2. Factory reset in cwm
3. Confirm it (this will wipe user data)
4. Reboot system
This should get you back to the registration page. You'll lose EVERYTHING except su. First thing I do is pm disable updates again. Once that's done you should be good tonset it all up--install busybox, all your apps.
I just worry because I use custom ROMs and never did this with stock. On your average android device keeping stock firmware wouldn't bother me but aftv is a little different since there's no doubt they don't want you rooted with custom recovery. I'd go to the dev threads and ask questions or flash prerooted ROMs. You might want to update incrementally as some have reported issues when they skip updates, not critical but it might be in your best interest.
And of course when I refer to updates I mean preroot not stock.

KLit75 said:
You're approaching this in a differnt angle than I'm used to--is there a reason you use stock firmware? With custom recovery, I'd venture to say a factory reset will do what you want it to and performing it will give you a clean slate and though updates will try to download they won't install.
I do this but I run rbox firmware...
1. Reboot recovery
2. Factory reset in cwm
3. Confirm it (this will wipe user data)
4. Reboot system
This should get you back to the registration page. You'll lose EVERYTHING except su. First thing I do is pm disable updates again. Once that's done you should be good tonset it all up--install busybox, all your apps.
I just worry because I use custom ROMs and never did this with stock. On your average android device keeping stock firmware wouldn't bother me but aftv is a little different since there's no doubt they don't want you rooted with custom recovery. I'd go to the dev threads and ask questions or flash prerooted ROMs. You might want to update incrementally as some have reported issues when they skip updates, not critical but it might be in your best interest.
And of course when I refer to updates I mean preroot not stock.
Click to expand...
Click to collapse
Hi,
I did the factory reset from CWM i forgot to mentioned this on intial post, sorry about that. It went thru the whole process, i re rooted and everything but again after installing CWM aftv did not boot in CWM so i thought maybe i should wipe everything out and start over instale fresh stock firmware.
Maybe the fireware is corrupted or the partition. I tried to down grade and upgrade to stock version but AFTV wouldn't installed the updates.
For me go get in CWM using ALT+PRINT SYS+I option is really pain full, after trying if for a 3 days and spending at least 2 hours each day i was able to get in so i thought start from scratch would might work.
thank you

ashsha7877 said:
Hi,
I did the factory reset from CWM i forgot to mentioned this on intial post, sorry about that. It went thru the whole process, i re rooted and everything but again after installing CWM aftv did not boot in CWM so i thought maybe i should wipe everything out and start over instale fresh stock firmware.
Maybe the fireware is corrupted or the partition. I tried to down grade and upgrade to stock version but AFTV wouldn't installed the updates.
For me go get in CWM using ALT+PRINT SYS+I option is really pain full, after trying if for a 3 days and spending at least 2 hours each day i was able to get in so i thought start from scratch would might work.
thank you
Click to expand...
Click to collapse
If I'm hearing you correctly I think I know your problem. You can't flash stock firmware with cwm. Rbox has protections in place thatbwont letbthis happen and for good reason--doing so could brick your device. You need the preroot ROMs. Follow aftvnews starters guide because I only had to do this once and I'm not certain I remember exactly. I think there's a certain version you should start with and some users find its better to update incrementally.

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.

Is my phona safe after kingroot?

Hi everyone!
I have rooted my phone. To be honest I don't even remember when
I've used kingroot. Don't remember version or source.
I have newest clean rom.
Didn't have any problems since rooting but I started to wonder if my data is safe. How Can I check it?

I've used KingRoot a few times for other devices, and it always makes me nervous. Use other methods for root if available.
The key to using KingRoot is to ONLY use it to obtain root to flash TWRP. Once you get TWRP recovery flashed, boot immediately into it and do a FULL wipe of everything except the recovery (ie system, data, etc, etc). Then just flash a custom ROM with a normal root like Magisk and that should keep you safe.
KingRoot is exclusively coded by a Chinese group, and it has been verified that the app has sent meta data back to China. So who knows what else it sends back to China. Sometimes on some of my devices it's the only option, so I just follow the steps above to stay safe.
Good luck! :fingers-crossed:

860lacov said:
Hi everyone!
I have rooted my phone. To be honest I don't even remember when
I've used kingroot. Don't remember version or source.
I have newest clean rom.
Didn't have any problems since rooting but I started to wonder if my data is safe. How Can I check it?
Click to expand...
Click to collapse
Your data is safe if you make a full wipe after rooting and flashed another rom.
On the orther side your imei is in their database now.

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.