Hi!
After receiving my OP 3T, I unlocked it and went to a Nougat firmware and rom. Failing to get VoLTE, VoWifi and SMSC settings on that rom, I tried further roms, one with the recommendation to do a full wipe. At the very end, I downgraded to OOS 3.5.4, but forgot to deactivate the password before starting the OS. That forced me to format userdata via TWRP and that way decrypt the phone the hard way.
With OOS 3.5.4, VoLTE, VoWifi and SMSC settings did work again fine and I would stay with that OS.
So I tried to reencrypt the rooted phone.
Starting that process from settings, the 3T bootet and stucked in the OS splash animation screen (the two white bubbles circling around the red bubble). After 1+ hour I bootet the phone which suceeded. Obviously nothing was happened, the phone remained unencrypted.
Does anyone has a hint how I can get the phone reencrypted?
akxak said:
Hi!
After receiving my OP 3T, I unlocked it and went to a Nougat firmware and rom. Failing to get VoLTE, VoWifi and SMSC settings on that rom, I tried further roms, one with the recommendation to do a full wipe. At the very end, I downgraded to OOS 3.5.4, but forgot to deactivate the password before starting the OS. That forced me to format userdata via TWRP and that way decrypt the phone the hard way.
With OOS 3.5.4, VoLTE, VoWifi and SMSC settings did work again fine and I would stay with that OS.
So I tried to reencrypt the phone.
Starting that process from settings, the 3T bootet and stucked in the OS splash animation screen (the two white bubbles circling around the red bubble). After 1+ hour I bootet the phone which suceeded. Obviously nothing was happened, the phone remained unencrypted.
Does anyone has a hint how I can get the phone reencrypted?
Click to expand...
Click to collapse
I recently did this with the most recent version of twrp, the official one from the twrp website, however a quick fix i believe is to flash stock recovery, reboot, encrypt and then flash twrp. Both methods worked for me
manor7777 said:
I recently did this with the most recent version of twrp, the official one from the twrp website, however a quick fix i believe is to flash stock recovery, reboot, encrypt and then flash twrp. Both methods worked for me
Click to expand...
Click to collapse
Hi!
Thanks for your reply.
With both latest TWRP 3.1.0-1 and the official recovery, I see the green android robot and then the phone shows the screen with the two white rotating bubbles around the red bubble... but no progress indicator or anything else.
Booting the phone out of that screen shows that nothing happened....
akxak said:
Hi!
Thanks for your reply.
With both latest TWRP 3.1.0-1 and the official recovery, I see the green android robot and then the phone shows the screen with the two white rotating bubbles around the red bubble... but no progress indicator or anything else.
Booting the phone out of that screen shows that nothing happened....
Click to expand...
Click to collapse
Hmm I'm not sure then. I'm using the latest FreedomOS so it could have something go do with that. Also rooted with magisk but no other system mods
I think I found the reason...
After I unrooted the phone, it did not stuck in the boot animation (or for whatever that animation was used, it is the same as when booting but the phone did not boot) but continued into the encrytpion progress screen.
I remember having had such an effect with a Samsung some time ago where encryption also failed as long as a process was running related to a rooted phone.
Related
I got my moto x today, updated it right away to lollipop, then went to work unlocking the bootloader, rooting, and installing TWRP.
All worked great, and then i went into TWRP to do a factory reset so that I could have the setup wizard when i turned my phone back on to set it up.
well after I did a factory wipe in TWRP (now i am thinking maybe i also checked to wipe system as well, but im not positive).
after the factory reset my device boots to the boot screen, and stops on the blue m logo at the end.
So i flashed the stock kitkat images using mfastboot, and it boots to the boot screen and then shuts off, doesnt even hang at the end anymore.
What are my options/ what the hell did i do?
Have just a quick question regarding 64gb Nexus 6. On first boot after doing a factory reset, the boot animation actually shows up twice, so it goes from the spinning dots, then the android logo, back to the spinning dots, shows the android logo again, and boots into the phone. This only happens after factory reset. Has been happening since 5.1 ota. Just flashed the 5.1.1 stock ROM yesterday and it still happens. Also phone is completely stock and not rooted. Just wanted to know if anyone else has seen this. Thanks.
techgirl0814 said:
Have just a quick question regarding 64gb Nexus 6. On first boot after doing a factory reset, the boot animation actually shows up twice, so it goes from the spinning dots, then the android logo, back to the spinning dots, shows the android logo again, and boots into the phone. This only happens after factory reset. Has been happening since 5.1 ota. Just flashed the 5.1.1 stock ROM yesterday and it still happens. Also phone is completely stock and not rooted. Just wanted to know if anyone else has seen this. Thanks.
Click to expand...
Click to collapse
Likely the encryption, flashed mine this last weekend and it did that the first time after a reset
I have a security PIN set and it'll run the boot animation, then ask for the PIN code, then start the boot animation again. I would guess that without a security PIN/Password/Pattern set it might behave as you've said.
Hi, I was running cm13 on my XT1058 and today I decided to revert back to stock.
the last firmware I flashed was stock 5.1 "xt1058_ghost_retbr_5.1_lpa23.12-15_cid12_cfc", but since I had updated the phone (did some OTAS before flashing cm13), I didn't know which version my bootloader was (I know you can see it on bootloader screen, but I didnt remember that at the time). So I googled the latest firmware for my 1058 and found the "XT1058_GHOST_RETBR_5.1_LPA23.12-21.7_cid12_CFC" and decided to flash it
After flashing the phone booted and optmized my apps as usual. When it finished wallpaper, status bar and nav bar appeared for a couple of seconds and then came a black screen and after another couple of seconds it showed the "preparing the device" pop up and then it goes back to the bootanimation and starts optimizing my apps again.
so far I tried to reflash the firmware, select the factory option on bootloader screen and boot using the BP Tools option but none of it helps.
what should I do?
thanks
EDIT: bootloader version is 30.BE right now
-----------------------------------------------------------------------------------
FIXED, I flashed the rom again and factory reset a second time and this time it booted normally, I don't know what exactly make it go this second time, but its FIXED.
Hi everyone.
I've android 6 stock (xt1068), and today i woke up and it doesn't work
I try to install the twrp and then to flash rom, ecc, but after that i install the twrp succesfully, when i go in the recovery i see that there is no twrp but the main stock recovery. This thing basically appens with everything that i install/wipe, infact the bootloader tells me that my action worked, but it didn't.
Another thing is that if i let my phone boot up, after the boot animation it tells me 'Starting Android', then this text go out, and for a second the boot animation appears again, after that all the screen goes black. (The phone is not closed, but it is showing black in the screen, i think you got it)
Thank you
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10