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?
Related
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
jtguf87 said:
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
Click to expand...
Click to collapse
I am having the same problem. Unfortunately, I have not gotten any answer. Sorry I couldn't help, but at least we're not alone.
same here, have had same issue with multiple dailies. do you think this is with twrp or cm12?
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Shakinghead said:
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Click to expand...
Click to collapse
How did you do it? I've tried to encrypt with 27/08/2015 nightly and I couldn't. It said encryption failed and I had to wipe it.
I'm using the 26/08 (UK date format) build - This is the one that broke Chrome. I just encrypted the phone using the settings. I've been trying every couple of weeks for sometime. In the past I get the CM logo and nothing happens. If I remove the battery then the phone boots OK...so clearly the encryption hadn't started. This time I left it and walked away. 30 mins later I went back to the phone and it was prompting for the encryption password after boot....So all good for me....except TWRP cannot decrypt the encrypted partitions...
I am using the D855 model.
I'm having similar issues. I was able to encrypt after installing the Resurrection Remix v5.5.5 but now TWRP shows internal storage as 0mb and throws out a bunch of mount errors. So can't backup or load anything new through TWRP now.
The only way I was able to change ROMs was to flash the stock ROM through the LG flashtool, thereby unrooting the phone and then starting the whole process from scratch. It's a big pain because everytime I do that I need to get admin approval to setup my work email and then need to encrypt again , which locks me into the existing ROM again!
Ughh!! Can't wait for a solution top this problem.
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?
Hi!
I have successfully rooted my Redmi 7, using latest TWRP and Magisk. However, now when I setup either pin, password or lock scree pattern, I cannot log in using them. I.e. I CAN set up a pin(1234), but when I try to enter(1234) it says incorrect. After that I cannot access my phone, and am forced to factory reset it. I tried resetting the phone multiple times, but I still cannot set up pin.
Is there any solution? The only one I thought of would beinstalling ROM, which I really don't want to do.
Thanks!
Same but with Samsung A6. Probably you can try this
kandalto said:
Hi!
I have successfully rooted my Redmi 7, using latest TWRP and Magisk. However, now when I setup either pin, password or lock scree pattern, I cannot log in using them. I.e. I CAN set up a pin(1234), but when I try to enter(1234) it says incorrect. After that I cannot access my phone, and am forced to factory reset it. I tried resetting the phone multiple times, but I still cannot set up pin.
Is there any solution? The only one I thought of would beinstalling ROM, which I really don't want to do.
Thanks!
Click to expand...
Click to collapse
You will need to factory reset your fone if it doesnot solve your problem then flash fastboot rom through mac or windows
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