Having some serious trouble. I rebooted my phone and it asked for my password once it was done as always but this time it said it was wrong. I'm certain I used the correct password but even tried my other alternatives to be sure and still a no go. This isn't the decryption option password you get when booting but my lockscreen password. I booted into recovery and it asks me for an encryption password that I never set but I know this is a common issue with twrp. Tried to go back into android but wouldn't let me because of the "wrong" password so I used the failsafe and went into recoveries file manager and deleted my lockscreen settings to remove my lockscreen passcode (tried and proven method, done it dozen times before). Got past my lockscreen this time but now it was saying starting android forever. Figured it was something with the passcode being deleted so I just decidd to factory reset from the recovery and take that loss. NOW the problem is upon booting the rom in trying to start the setup, I'm stuck on the "just a sec..." screen that comes up after you click start. What do I do from here? I cant access anything in recovery because the encryption passcode issue so I'm kind of stuck. Also I'm a work right now and we cant connect our phones (or any USB for that matter) to the computers and laptops because theyre government property and on a secured line. Any help PLEASE, Ill be home later and can try more then.
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
loeffler23 said:
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
Click to expand...
Click to collapse
Hey, I got my phone back working after that and rooted again and flashed same rom. NOW another problem, I rebooted my phone and its not accepting my PIN anymore, nor my fingerprint, and I cant reset through TWRP because of encryption. WTF is the issue, how do I fix this or do I have to flash-all again?
Okay so my device aint a redmi 7 but its a y3 so its basically the same and everything made for the 7 works on it just fine, but this odd encryption issue is very frustrating, my device keeps on getting encrypted during boot and I can't unlock it at all, even if there was no security set on device it wants a password, I can't seem to fix this at all, the first boot is fine on any custom rom but on the 2nd or 3rd it automatically gets encrypted, even on backups, if I restore a previous backup it wants encryption code if that doesn't appear and the phone boots up fine but when the lock screen appears, the previous screen lock password doesn't seem to work. What am I doing wrong here? Even in case of backing up using twrp? This encryption thing is really frustrating!
Thank you!
try different locking methods when setting up the ROM for the first time
a safe haven said:
Okay so my device aint a redmi 7 but its a y3 so its basically the same and everything made for the 7 works on it just fine, but this odd encryption issue is very frustrating, my device keeps on getting encrypted during boot and I can't unlock it at all, even if there was no security set on device it wants a password, I can't seem to fix this at all, the first boot is fine on any custom rom but on the 2nd or 3rd it automatically gets encrypted, even on backups, if I restore a previous backup it wants encryption code if that doesn't appear and the phone boots up fine but when the lock screen appears, the previous screen lock password doesn't seem to work. What am I doing wrong here? Even in case of backing up using twrp? This encryption thing is really frustrating!
Thank you!
Click to expand...
Click to collapse
If you can unlock the device try goin to settings and turn on developer options and head towards last option in developer options i.e Encrypt data using screen lock open it and turn off it
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
After installing beta 1, and factory resetting, phone hung in loop in setup. Wants me to enter my old pin code, and after i enter it, it takes me back to restoring backup screen. Anyone have any ideas?
Thanks
same problem here
Todesdoktor said:
same problem here
Click to expand...
Click to collapse
i'm find solution and it works for me so u can try to
https://www.reddit.com/r/android_beta/comments/nfsvxj
read my instruction post also undre my post u can see links for ota images for p[hone models u must download ota for your phone and then flsah by my instructions
Same issue here. Running Android 12 Beta and was fine. Then a couple weeks in the phone start crashing/rebooting on some apps. I thought I'd factory reset to clear any erroneous data and try again. Now it boots into Android setup, asks and accepts pin, but won't let me enter gmail and password. Keeps asking to restore data from old phone via cable, then back to enter pin again. Over and over. I can boot into recovery, but don't currently have a Windows machine to troubleshoot; only a macbook air and a chromebook. Haven't figured that side out yet.
I found this promising looking info. It's SUPER simple too! Unfortunately it has not worked for me yet, but I'm optimistic maybe later today I can get it going!
https://www.reddit.com/r/android_beta/comments/nrwzxm
Hi guys,
I was having problems with 11.0.20, so I flashed 11.0.17 on my Mi A2 Lite (stock version from Xiaomi).
Now the phone is asking for a password on boot, I can only type in a password and select emergency call.
The problem is: I have never set any password on this device. Screen lock PIN does not work (and I have removed screen lock before flashing).
I tried flashing it twice once again, same result. I always tried flash_all_except_storage .
Is there some kind of master password that does work, if no password has been set? (I tried default_password , but this didn't work for me)
How can I get past this?
I flashed image 11.0.21 again, still the same result.
Now I tried flash_all.sh (including storage), and now the phone is hard reset.
I have flashed this phone multiple times, never did I do a downgrade though. I wonder why this is the first time I have been asked for a password.
WaveAbuser said:
Hi guys,
I was having problems with 11.0.20, so I flashed 11.0.17 on my Mi A2 Lite (stock version from Xiaomi).
Now the phone is asking for a password on boot, I can only type in a password and select emergency call.
The problem is: I have never set any password on this device. Screen lock PIN does not work (and I have removed screen lock before flashing).
I tried flashing it twice once again, same result. I always tried flash_all_except_storage .
Is there some kind of master password that does work, if no password has been set? (I tried default_password , but this didn't work for me)
How can I get past this?
I flashed image 11.0.21 again, still the same result.
Now I tried flash_all.sh (including storage), and now the phone is hard reset.
I have flashed this phone multiple times, never did I do a downgrade though. I wonder why this is the first time I have been asked for a password.
Click to expand...
Click to collapse
Use this tool for reset your phone:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
if u unlocked, boot on twrp 3.3.1.dees_troy (no need to install it) and wipe data, then reboot