Related
I have reflashed my phone about 3 times and the last resulting in a fresh start without carrying over any data. My original rooting method was system mode which left me unable to accept OTA updates and was unstable. I am now using systemless magisksu and systemless Xposed with a untouched system partition. And at first I was able to play games like fire emblem heroes and pokemon go without trouble, then after a while I noticed that the same issues were happening again. Fire emblem gives a error code dispite me having hide magisk and automagisk enables for it, same for pokemon go. No matter what I do or how many times I reinstall I always get the errors.
I have read that you cannot hide root if you have a unlocked bootloader which I do. I have a stock ROM but a unlocked bootloader because I have a developer global installed. Do I need to modify my boot.img to not have the flag?
With original developer I think that you can relock the bootloader.... But you have to flash the original recovery too... I think I tried and it stuck so you might consider flashing via fastboot the original developer. I am not sure what happens to root
To lock bootloader you have to go to fastboot mode and type fastboot oem lock
jimger said:
With original developer I think that you can relock the bootloader.... But you have to flash the original recovery too... I think I tried and it stuck so you might consider flashing via fastboot the original developer. I am not sure what happens to root
To lock bootloader you have to go to fastboot mode and type fastboot oem lock
Click to expand...
Click to collapse
1. i have heard that relocking bootloader is actually more dangerous then unlocking and i have permabricked a 3s before and
2. no way will i unhack and relock just so that i can use some apps that to ignorant to leave rooted people alone. i will have to find away to make a custom kernal that removed the saftynet flag. someone was talking about that for another phone.
I don't think it is easy to brick redmi 3s.... Have you tried getting it into edl?
For me even when I had it with black screen I could "do" stuff to it. You can relock it if you use miflash and put developer and/or stable from en.miui.com. It will replace both your system and your recovery but also delete your media to your internal "sd".
I use an xposed module that responds well to safetynet but actually it doesn't really pass. Android pay can't be activated (to me) and I am not sure about pokemon or whatever because I don't use it. But safety net passes. I use an app from play store safetynet helper which in latest version included a basic integrity check. Well my device responds ok to cts profile but fails to basic integrity. Not sure why exactly but even thought I have magisk+ supersu in systemless mode I have touched the /system partition perhaps with adaway or I don't know for sure. I don't know how undroid checks for tampered system partition. I have miui-globe rom which is not official
jimger said:
I don't think it is easy to brick redmi 3s.... Have you tried getting it into edl?
For me even when I had it with black screen I could "do" stuff to it. You can relock it if you use miflash and put developer and/or stable from en.miui.com. It will replace both your system and your recovery but also delete your media to your internal "sd".
I use an xposed module that responds well to safetynet but actually it doesn't really pass. Android pay can't be activated (to me) and I am not sure about pokemon or whatever because I don't use it. But safety net passes. I use an app from play store safetynet helper which in latest version included a basic integrity check. Well my device responds ok to cts profile but fails to basic integrity. Not sure why exactly but even thought I have magisk+ supersu in systemless mode I have touched the /system partition perhaps with adaway or I don't know for sure. I don't know how undroid checks for tampered system partition. I have miui-globe rom which is not official
Click to expand...
Click to collapse
trust me i have tried everything to unbrick that phone it is IMPOSSIBLE no one can fix it, it just sits as spare parts in my storage now as i brought another one
https://forum.xda-developers.com/xiaomi-redmi-3s/help/bricked-redmi-3s-identify-test-force-t3438220
http://en.miui.com/thread-326730-1-1.html
http://en.miui.com/thread-373634-1-1.html
and even when my phone isn't rooted like after a fresh miflash after like 20 minutes the test fails but for that little time before then everything is ok.
Which test?
I saw that you ordered the deep flash cable and still not ok?
Have you tried the modified reboot to edl?
Also have you got x64 windows with test mode enabled?
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
jimger said:
Which test?
I saw that you ordered the deep flash cable and still not ok?
Have you tried the modified reboot to edl?
Also have you got x64 windows with test mode enabled?
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
yes and yes the cable did not do anything
trust me i have tried everything anyone can ever imagine.
xdarkmario said:
yes and yes the cable did not do anything
trust me i have tried everything anyone can ever imagine.
Click to expand...
Click to collapse
Well don't know Then you are one of the very few... I can't tell anything else
If you reflash in fastboot it will be relocked. And there is no problem at all....
I am still having issues with this, i dont have the knowledge for compiling a kernel from source. no matter what i try i just cant bypass this stupid saftynet. if i flash the phone from scratch it will allow me to use saftynet protected app for a little bit but on reboot or something i cant use use it again.
As far as I know, developer ROMs don't pass SafetyNet, only the stable ROMs. And only with locked bootloader and without any modifications (root, xposed, magisk, etc.). For locking bootloader I recommend you to flash a fastboot ROM in fastboot mode and in MiFlash choose flash all and lock option, this way you will not brick your phone. But if it's not working and as I see you can unlock your bootloader, I recommend you xiaomi.eu ROMs. If all is true, the next release (both of beta and stable) will bypass SafetyNet (of course without modifications, but with this ROM don't lock your bootloader). But since it's based on china ROMs, beta releases are suspended until august. From the stable ROMs MIUI 8.2 doesn't pass SafetyNet yet, so you have to wait to MIUI 8.5.
22Dávid22 said:
As far as I know, developer ROMs don't pass SafetyNet, only the stable ROMs. And only with locked bootloader and without any modifications (root, xposed, magisk, etc.). For locking bootloader I recommend you to flash a fastboot ROM in fastboot mode and in MiFlash choose flash all and lock option, this way you will not brick your phone. But if it's not working and as I see you can unlock your bootloader, I recommend you xiaomi.eu ROMs. If all is true, the next release (both of beta and stable) will bypass SafetyNet (of course without modifications, but with this ROM don't lock your bootloader). But since it's based on china ROMs, beta releases are suspended until august. From the stable ROMs MIUI 8.2 doesn't pass SafetyNet yet, so you have to wait to MIUI 8.5.
Click to expand...
Click to collapse
i know how to relock my bootloader, i have done it before and relocked it as well as my xiaomi account is allowed to do so but for what i do i at least a rooted phone at the least. xposed it a heavy want but not mandatory like root is. i also need to be on the global weekly because the stable haven't added EXfat support yet.
Use magisk 13.3 =_=
jimger said:
I don't think it is easy to brick redmi 3s.... Have you tried getting it into edl?
For me even when I had it with black screen I could "do" stuff to it. You can relock it if you use miflash and put developer and/or stable from en.miui.com. It will replace both your system and your recovery but also delete your media to your internal "sd".
I use an xposed module that responds well to safetynet but actually it doesn't really pass. Android pay can't be activated (to me) and I am not sure about pokemon or whatever because I don't use it. But safety net passes. I use an app from play store safetynet helper which in latest version included a basic integrity check. Well my device responds ok to cts profile but fails to basic integrity. Not sure why exactly but even thought I have magisk+ supersu in systemless mode I have touched the /system partition perhaps with adaway or I don't know for sure. I don't know how undroid checks for tampered system partition. I have miui-globe rom which is not official
Click to expand...
Click to collapse
All the neccessary apps ( android pay & Pokemon ) use basic integrity
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
svandasek said:
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
Click to expand...
Click to collapse
Glad it helped you
ah.... if i only knew :crying:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
TWRP Encryption ByPass
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
Agree .... that seems like a gaping security vulnerability. :-/
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
There's no need to be concerned (about this, specifically).
tk8lm6 said:
Agree .... that seems like a gaping security vulnerability. :-/
Click to expand...
Click to collapse
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.
Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.
If that's the way that's meant to work, then that's flawed by design.
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
manchitro said:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
Click to expand...
Click to collapse
Just flash it.
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.
Can someone detail please?
---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------
Actually I just found a way out to get to previous twrp version, and all is back to normal
From your running ROM, you can download the application twrp (root needed oc)
Then you can use it to flash recovery.
I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!
Still not solving the encryption password issue when flashing new recent twrp..
Android 10 Encryption / Security Issue - ADB Encryption Bypass?
rahulrs0029 said:
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Click to expand...
Click to collapse
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
monicaONxda said:
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
Click to expand...
Click to collapse
Anyone with thoughts on this...?
monicaONxda said:
Anyone with thoughts on this...?
Click to expand...
Click to collapse
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.
If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.
So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.
Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
Click to expand...
Click to collapse
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
nvertigo67 said:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
Click to expand...
Click to collapse
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).
For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
Dear members, i don't see the way how to skip 7 days of waiting on oreo on xda (OEM LOCK and RMM STATE: PRENORMAL).
But i found one.
Note: THIS DOES TRIP KNOX.
Download any ROM before December(Nougat) for your device.
Then, using ODIN and download mode flash that ROM. After setting UP device will not have RMM state in Download mode and you will se OEM unlock in Dev settings.
Now you can flash twrp and get custom ROM (Nougat or Oreo)
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
you can press thank's button for them
SmailkO said:
Dear members, i don't see the way how to skip 7 days of waiting on oreo on xda (OEM LOCK and RMM STATE: PRENORMAL).
But i found one.
Note: THIS DOES TRIP KNOX.
Download any ROM before December(Nougat) for your device.
Then, using ODIN and download mode flash that ROM. After setting UP device will not have RMM state in Download mode and you will se OEM unlock in Dev settings.
Now you can flash twrp and get custom ROM (Nougat or Oreo)
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
Click to expand...
Click to collapse
ODIN Does not allow Bootloader downgrade.
JazonX said:
ODIN Does not allow Bootloader downgrade.
Click to expand...
Click to collapse
yes it does. At least this time it does - I have flashed back to Nougat and then back to Oreo several times. If you don't want to be locked out once you have flashed OREO - you can use ODIN to flash a NOUGAT ROM and it will work. I know you can, I have done it.
Work! Thanks ?
JazonX said:
ODIN Does not allow Bootloader downgrade.
Click to expand...
Click to collapse
Who told U that, downgraded BL so many times in Odin.
rajkabul said:
Who told U that, downgraded BL so many times in Odin.
Click to expand...
Click to collapse
Can you explain how you did, So I can try again?
In my Note 7 - It didn't happen. Got a Fail error in ODIN.
JazonX said:
Can you explain how you did, So I can try again?
In my Note 7 - It didn't happen. Got a Fail error in ODIN.
Click to expand...
Click to collapse
Nougat and Oreo firmwares for the S8 are same binary. So you can downgrade.
For The Note Fan Edition, you can't downgrade from binary 2 to binary 1
New way
BlackMesa123 said:
Hello everybody. I got interested about this problem since my friends @Yahia Angelo and @corsicanu got the "Only official released binaries are allowed to be flashed" problem, so we decided to search deeply about this. We found out that this problem isn't related to FRP/OEM Unlock (even if enabled same problem comes), but to a new prop that you can see in Download Mode (RMM State: Prenormal). By searching in system, seems this prop is related to a new "thief" protection Samsung added in latest firmwares. Let's make an example: you get the device, setup Google Account, all good... then someone steals the device and wipes it... ok. After wipe he boots, but he can't pass the setup without internet, and when he connects to internet it asks for your Google account, since your account is saved in FRP partition, so he can't setup. This RMM State is more than that simple FRP, as it doesn't allow him to flash custom binaries to remove FRP. So now let's cut to the chase: who still doesn't have this RMM lock can avoid to get the device locked by following these two simple steps:
1. In build.prop, make sure "ro.security.vaultkeeper.feature" property is set to 0, like this:
Code:
sys.use_fifo_ui=0
ro.wsmd.enable=true
ro.security.vaultkeeper.feature=[COLOR="Blue"]0[/COLOR]
keyguard.no_require_sim=true
ro.carrier=unknown
2. Remove Rlc app. To do this go in "/system/priv-app" folder with a root file manager or with twrp file manager and remove "Rlc" folder.
For those who unfortunately has RMM State set to "Prenormal", as this user reports, seems that by keeping your phone running without shut it off/reboot, at a certain device running time value RMM State prop will set again to "Normal", so you can flash custom binaries again, if it works to you make sure to follow the above steps to not get locked again, I'll keep you guys updated about this when there will be news.
EDIT:
In attachments now you can find a zip that does the job for you. So when RMM State is set back to "Normal", flash a custom recovery and then flash this zip file to avoid lock again
Click to expand...
Click to collapse
UPDATE
rady96 said:
...................Odin flash fails fixed 100% solutions..................Explanation to why odin fails
When your s8/ s8+ is forced rebooted by holding the power and volume down buttons or crash reboots. And when booting into download mode for some reason download mode is locked or corrupted and Odin will fail even if you use official device specific firmware. So follow the steps below to fix
How to fix!
1. Boot into download mode by pressing ( power + volume down + Bixby button) and stop at the screen of continue and reboot.
2. Press volume down to restart phone
3. Quickly boot back into download mode by pressing (power + volume down + Bixby button)
4. Press continue
5. Congratulations fully working now
Click to expand...
Click to collapse
T0nyCr said:
New way
Click to expand...
Click to collapse
of course you have to be Rooted to do it manually and you have to have TWRP installed to flash the fix - so either way - if you can't flash because fo the Official Binaries Only warning - you will have to wait 7 days, 168 hours before you can flash again - or flash the NOUGAT BL as suggested by the OP.
FYI - there is an OREO ROM called Minotaurus (Find it on Telegram) that you can use while on the NOUGAT BL - so you can enjoy the benefits of OREO by first going to back to the last NOUGAT Firmware in ODIN - then flashing MINOTAURUS ROM (V19) - OREO Rom. (It is an excellent rom!)
Obviously this isnt for G955U??
Geekser said:
yes it does. At least this time it does - I have flashed back to Nougat and then back to Oreo several times. If you don't want to be locked out once you have flashed OREO - you can use ODIN to flash a NOUGAT ROM and it will work. I know you can, I have done it.
Click to expand...
Click to collapse
Thats because both nougat(Nov and DEC builds) and oreo are on V2 bootloader at the moment. ODIN DOES NOT allow bootloader downgrade. infact its the phone and not even ODIN controlling that.
It's binary 1, not 2
Envoyé de mon SM-N935F en utilisant Tapatalk
Doesn't work
T0nyCr said:
New way
UPDATE
Click to expand...
Click to collapse
New way (updated) doesn't work, still prenormal rmm state, still can't flash
gastondh91 said:
New way (updated) doesn't work, still prenormal rmm state, still can't flash
Click to expand...
Click to collapse
Just downgrade if you got the S8 or S8+
Envoyé de mon SM-N935F en utilisant Tapatalk
benyou54 said:
Just downgrade if you got the S8 or S8+
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
Yeah sure, i have nougat working with no prenormal rmm state but i want to have oreo with no prenormal and when i flash with odin it gets to prenormal again even if do that power+ vol- + bixbie trick, it doesn't work
gastondh91 said:
Yeah sure, i have nougat working with no prenormal rmm state but i want to have oreo with no prenormal and when i flash with odin it gets to prenormal again even if do that power+ vol- + bixbie trick, it doesn't work
Click to expand...
Click to collapse
The prenormal state goes away after 7 days. You have to wait 7 days with the phone turned on. There is no trick to make the rmm state disappeared from the download. Just wait 7 days then flash twrp, magisk and rmm fix [emoji106]
Envoyé de mon SM-N935F en utilisant Tapatalk
Do I have to flash to pure stock or can I stay on a nougat backup for 7 days?
Smartphones13 said:
Do I have to flash to pure stock or can I stay on a nougat backup for 7 days?
Click to expand...
Click to collapse
I don't know what you mean by nougat backup ? You just have to wait 7 days with your FE turned on, that's all.
Envoyé de mon SM-N935F en utilisant Tapatalk
so once I go back to stock rom I just need to wait 7 days with no reboots right?
Hi. My fp stopped working. I need to reconfigure at every reboot. But it doesn't work. I think this is caused because changed SElinux to permissive. Anyone can give me a solution? Now I'm using Pixel Experience last build. Flashed it yesterday in a very strange way: all the apps and datas remained installed (without using migrate for backup).
Flash latest firmware
coremania said:
Flash latest firmware
Click to expand...
Click to collapse
I already flashed the latest firmware but unfortunately it didn't was successful. I need to configure the fingerprint every time I reboot the phone. But it doesn't work.
tudorscutariu said:
I already flashed the latest firmware but unfortunately it didn't was successful. I need to configure the fingerprint every time I reboot the phone. But it doesn't work.
Click to expand...
Click to collapse
Remove your security settings like pin or pattern.
Boot to twrp, mount system, use the twrpfilemanager
and delete locksettings.db under data/system.
Reboot and try to setup your fingerprint again.
coremania said:
Remove your security settings like pin or pattern.
Boot to twrp, mount system, use the twrpfilemanager
and delete locksettings.db under data/system.
Reboot and try to setup your fingerprint again.
Click to expand...
Click to collapse
You probably meant mount DATA, not SYSTEM, right? Mounting system is unnecessary and will just screw up OTA updates.
Edit: ah, guy is on custom rom. So OTA doesn't matter
Btw. it sounds like he installed custom ROM without a data wipe, this might explain the unusual behavior.
_mysiak_ said:
You probably meant mount DATA, not SYSTEM, right? Mounting system is unnecessary and will just screw up OTA updates.
Edit: ah, guy is on custom rom. So OTA doesn't matter
Btw. it sounds like he installed custom ROM without a data wipe, this might explain the unusual behavior.
Click to expand...
Click to collapse
Sounds like same issue as it happens after twrp restore. Deleting the locksettings.db should fix it. I didn't understand his issue in the first place. If he is cross flashing without data wipe he should clean flash anyway, but maybe he's to lazy for it
Edit: of course, you're right, mount data....
First I want to thank you for your helpfulness. I deleted the file but it doesn't work with selinux permissive enabled. Is there a way to make working both permissive and fingerprint? Because I need permissive to make working aiocammodule for gcam
tudorscutariu said:
First I want to thank you for your helpfulness. I deleted the file but it doesn't work with selinux permissive enabled. Is there a way to make working both permissive and fingerprint? Because I need permissive to make working aiocammodule for gcam
Click to expand...
Click to collapse
Not sure what's the purpose of that module, but I'd try setting selinux to enforcing and play with specific selinux policies. With the early Pie releases it was needed to use this to fix lags caused by selinux issues.
Code:
magiskpolicy --live "allow hal_camera_default surfaceflinger_service service_manager find"
Source: https://forum.xda-developers.com/mi-a1/themes/module-long-camera-start-fix-mi-a1-t3745262
You should go for a clean install of pe. What you have written on your first post with your remained data doesn't sound right. If you flash a new rom do it clean or you will constantly run into issues other don't have. Why you want to use an old selinux permissive fix for the tissot cam. Go for gcam it will make better shots anyway.
Made a clean flash of PE. All Is good now, thank you again.
Bootloader is unlocked. Using xiaomi.eu 12.0.4 .
Just curious, Can i install official rom 12.0.5 to my M3 global version?
Yes you can, you need to flash the fastboot version with MiFlash. Just make shure to keep the bootloader unlocked, because locking the bootloader on an other rom than the one that came on the phone will result in a brick.
In MiFlash in the right bottom corner you have a couple of options, you need to choose 'Clean all'.
You can try to use Mi Flash to install the fastboot ROM, but you need to choose "clean all", do not choose lock, the phone will not boot if the bootloader is locked and detects a ROM of a different region.
If it boots successfully after installing the official EEA ROM, you need to always keep the bootloader unlocked.
Edit: I have installed Taiwan ROM on my M3 that came with global ROM, using Mi Flash Tool, the phone still works after locking bootloader (clean all and lock).
mierlo420 said:
Just make shure to keep the bootloader unlocked, because locking the bootloader on an other rom than the one that came on the phone will result in a brick.
In MiFlash in the right bottom corner you have a couple of options, you need to choose 'Clean all'.
Click to expand...
Click to collapse
I have installed Taiwan ROM on my M3 that came with global ROM, using Mi Flash Tool, the phone still works after locking bootloader, with the clean all and lock option.
So it is only not allowed to install a different region MIUI ROM on China devices, global devices do not have this limitation.
cbw said:
I have installed Taiwan ROM on my M3 that came with global ROM, using Mi Flash Tool, the phone still works after locking bootloader, with the clean all and lock option.
So it is only not allowed to install a different region MIUI ROM on China devices, global devices do not have this limitation.
Click to expand...
Click to collapse
Thank you so much for this info
cbw said:
You can try to use Mi Flash to install the fastboot ROM, but you need to choose "clean all", do not choose lock, the phone will not boot if the bootloader is locked and detects a ROM of a different region.
If it boots successfully after installing the official EEA ROM, you need to always keep the bootloader unlocked.
Edit: I have installed Taiwan ROM on my M3 that came with global ROM, using Mi Flash Tool, the phone still works after locking bootloader (clean all and lock).
Click to expand...
Click to collapse
yes flashing other region rom doesn't brick the device as fas as I know and also I have the experience of this .
cbw said:
You can try to use Mi Flash to install the fastboot ROM, but you need to choose "clean all", do not choose lock, the phone will not boot if the bootloader is locked and detects a ROM of a different region.
If it boots successfully after installing the official EEA ROM, you need to always keep the bootloader unlocked.
Edit: I have installed Taiwan ROM on my M3 that came with global ROM, using Mi Flash Tool, the phone still works after locking bootloader (clean all and lock).
Click to expand...
Click to collapse
can you please check if your playstore is certified or not after installing a rom of other region and locing bootloader ...
pocoX3_karna_user said:
check if your playstore is certified
Click to expand...
Click to collapse
Yes, it is certified after locking bootloader.
Can global flash to China? Flashing global to china is literally forcing myself to hammer a phone due to the GMS ban, but it is just a question out of curiosity.
cbw said:
Yes, it is certified after locking bootloader.
Click to expand...
Click to collapse
okay thanks for the reply
cbw said:
Yes, it is certified after locking bootloader.
Click to expand...
Click to collapse
Hello, so you went from a Global rom (MI) to a Taiwan rom (TW)? I personally have a Redmi Note 10 Pro (in version 12.0.6.0, RKFEUOR), and I would like to change to a version 12.5.4.0 in RKFEUXM.
Logically, I will be in the same region since I am going from an EEA (EU) rom to an EEA rom (also EU), I simply remove the overlay from my Orange operator by switching from RKFEUOR to RKFEUXM. Will it be a problem if I lock my bootloader by doing "Clean All and lock"? I would like to keep the certifications.
Thank you !
Xiaomi17 said:
Will it be a problem if I lock my bootloader by doing "Clean All and lock"? I would like to keep the certifications.
Click to expand...
Click to collapse
The phone should still work without problems after relocking bootloader with that option, and it will still pass the certification.
But to flash the fastboot ROM you will still need to unlock bootloader, you can't update it with the recovery ROM method since they are different versions (OR and XM).
cbw said:
The phone should still work without problems after relocking bootloader with that option, and it will still pass the certification.
But to flash the fastboot ROM you will still need to unlock bootloader, you can't update it with the recovery ROM method since they are different versions (OR and XM).
Click to expand...
Click to collapse
Okay, so to recap: I unlock with Mi Flash Unlock (there is a week left), then I flash my ROM for my Redmi Note 10 Pro "12.5.4.0 RKFEUXM" with Mi Flash while selecting "Clean All and Lock" , and the flash should go smoothly with the bootloader locked again after reboot? In short, the only ones who are affected by this problem are the Chinese who would like to move to another region (MI, or EU, TW ...), or those of Russian origin too, I guess ?
Xiaomi17 said:
I unlock with Mi Flash Unlock (there is a week left), then I flash my ROM for my Redmi Note 10 Pro "12.5.4.0 RKFEUXM" with Mi Flash while selecting "Clean All and Lock" , and the flash should go smoothly with the bootloader locked again after reboot?
Click to expand...
Click to collapse
Yes, that is correct, make sure that the file you download is the fastboot ROM in the tgz format, not the recovery ROM.
Then you need to extract the tgz file into a folder, make sure there is no space in the path of the folder, so it's better to extract it to C:\ or D:\ on the computer, then select that folder in Mi Flash.
To unlock bootloader, you need to use the latest version of Mi Unlock (version 5.5), because there is an older version of it that already does not work.
Xiaomi17 said:
In short, the only ones who are affected by this problem are the Chinese
Click to expand...
Click to collapse
Yes, at least in my own experience, the problem only exists when installing the official global ROM (or another region of MIUI) on a phone (after Redmi Note 5) that came with China ROM pre-installed. The phone will not boot until the bootloader is unlocked again.
I have tried installing the global ROM on the China versions of both Redmi 4X and Redmi 6 Pro, on Redmi 4X, I could lock the bootloader with global ROM installed and it would still boot, but Redmi 6 Pro wouldn't boot with locked bootloader, and it would show "This MIUI version can't be installed on this device".
The global phones I used (POCO M3 and Redmi 9T) do not have this problem, I have installed Taiwan ROM (TWXM) on both phones that came with the global ROM (MIXM) pre-installed, with re-locked bootloader, after more than 6 months, the phones still work well without software problems, they just feel the same as the phones that are from Taiwan.
cbw said:
Yes, at least in my own experience, the problem only exists when installing the official global ROM (or another region of MIUI) on a phone (after Redmi Note 5) that came with China ROM pre-installed. The phone will not boot until the bootloader is unlocked again.
I have tried installing the global ROM on the China versions of both Redmi 4X and Redmi 6 Pro, on Redmi 4X, I could lock the bootloader with global ROM installed and it would still boot, but Redmi 6 Pro wouldn't boot with locked bootloader, and it would show "This MIUI version can't be installed on this device".
The global phones I used (POCO M3 and Redmi 9T) do not have this problem, I have installed Taiwan ROM (TWXM) on both phones that came with the global ROM (MIXM) pre-installed, with re-locked bootloader, after more than 6 months, the phones still work well without software problems, they just feel the same as the phones that are from Taiwan.
Click to expand...
Click to collapse
Oh okay. So if I am able to switch from one EEA version to another EEA version without a mobile operator in order to have the updates in advance, I can also switch if I want from an EEA to a rom Taiwan, for example, or from EEA to an MI (global) ?
And another question, I had heard that as the phone was reset beforehand by unlocking the bootloader, then doing a flash clean and lock, some were blocked because for they asked for a Mi account, on restart, except that like the phone was reset (thanks to bootloader unlock), well the person was stuck because the phone no longer had the account registered. But I guess it's a minority, or it's a specific problem. Normally it doesn't ask to reconnect after doing "Clean all and lock" ?
Xiaomi17 said:
I can also switch if I want from an EEA to a rom Taiwan, for example, or from EEA to an MI (global) ?
Click to expand...
Click to collapse
Yes, you can install any other region of MIUI and lock bootloader as long as it's an official ROM for your device, not a custom ROM.
I chose to install the Taiwan version of MIUI because it has the MIUI dialer, while all other regions of MIUI except Taiwan and Indonesia only have the Google dialer which I don't like.
Xiaomi17 said:
some were blocked because for they asked for a Mi account,
Click to expand...
Click to collapse
That is because MIUI's find device is enabled, if the phone had a different account signed in with find device enabled, after a factory reset, it will ask for the password of that account.
I think that usually happens when people buy used phones that the original owners did not remove their Mi accounts before selling.
I think if you are the only person who used the phone, it should be safe as long as you remember the password of your Mi account.
By unlocking bootloader, Mi unlock will erase the data on the phone, also when you flash the fastboot ROM, the data still needs to be wiped again.
So you will always need to type the password when the phone boots for the first time after data is wiped, if you have find device enabled, you will need to have an Internet connection to be able to type the password.
I am not sure what will happen if you disable find device before unlocking bootloader.
But when I tried to unlock bootloader of my phone without enabling find device, I had to wait for 15 days instead of 7 days.
Okay, so the only thing to do is to put the password of the Mi account with which I unlocked the bootloader (if asked at startup)? Anyway, I'm the sole owner, I bought it in June, it's just in case. Another thing, once I unlock the bootloader with Mi Unlock, and my data is erased, and therefore I end up with the phone's first setup screen, can I turn it off right away? I do not need to reconnect to my Mi account: I unlock the bootaloder, then I turn off immediately once it is well started and I flash in fastboot?
Xiaomi17 said:
put the password of the Mi account with which I unlocked the bootloader (if asked at startup)?
Click to expand...
Click to collapse
Yes, the password of your Mi account.
Xiaomi17 said:
I unlock the bootaloder, then I turn off immediately once it is well started and I flash in fastboot?
Click to expand...
Click to collapse
After unlocking bootloader, data will be erased and the phone will reboot, but you can just reboot the phone to bootloader (fastboot mode) by long pressing the power button and the volume down button, then flash the fastboot ROM in Mi Flash, and go through the setup after flashing the ROM, since data will be wiped again during flashing.
I received at the moment 12.5.1 (still under Orange operator rom) just before I unlock and flash, as if by chance. But I will still unlock the bootloader and flash, so I will have the latest version and then above all, I will have the updates faster.