Stock OS taking too long too boot! Maybe Bootloop - OnePlus 3T Questions & Answers

I was in the middle of changing from Havoc OS 2.0 to Stock OOS 5.0.8 .
I flashed a new twrp version 3.2.3.1 and then flashed OOS zip file, when I booted into system it took too long to start the setup screen and never eventually did.
I suddenly recalled that i read somewhere that twrp 3.2.3.1 is being giving some encryption issues, so I thought that this might be the issue so I forced restarted the booting process (pressing power button for a while),went back into recovery , then to bootloader and changed to twrp 3.2.3.0 and then flashed the rom again.
But this time too had no success and still the boot animation (oneplus's) is going on but 3T not starting.
I had given an ample amount of time ( around 30 mins) and have even repeated the process of flashing about 3 times
(including wiping everything) but still no luck
I am worried because i know my device never took so much time to boot any rom. Please Help
Note: I still can access recovery and everything so might not be the case of bootloop ( i don't know really)
Edit: After Some Fiddling around i decided to try some other rom and surprisingly Havoc OS flashed Perfectly Without Any Problem.

Related

Boot and TWRP issues out of nowhere.

Hello all, this is my first time posting here, and I hope that my problem isn't permanent, but this morning my phone started to act strange. I reverted back to stock yet everything is still the same. Long splash screen time, and very laggy, very unresponsive recovery/UI when the phone is on. At first i thought that I had done something in my pocket on accident, so I clean flashed Chroma, my daily driver, and ElementalX. After rebooting from recovery, the Google splash screen had stayed on for about 20 seconds, compared to the 5 I had been seeing till today.
Now, when the phone actually booted, I was getting random restarts, screen becoming unresponsive along with the buttons. After setting up the phone, every app I tried opening would hang at the splash screen, like Hangouts, and would immediately stop responding, and eventually restart the phone.
TWRP also would freeze and the screen would lock on its own. When trying to swipe to unlock, the slider would freeze and behind it was another lock slide, which wasn't accessible. After reverting to stock, with TWRP once again, the boot and recovery still take 4 times longer than what they used to, and my phone is very sluggish to start. Has anyone else experienced this?
Currently on TWRP 3.0.0.2, stock 6.0.1, MMB30W image.
https://twrp.me/Devices/
Start with updating TWRP.
NLBeev said:
https://twrp.me/Devices/
Start with updating TWRP.
Click to expand...
Click to collapse
Flashed latest TWRP through fastboot, Google screen took 20 seconds again, TWRP started off fine, then froze after locking
Puuuddle said:
Flashed latest TWRP through fastboot, Google screen took 20 seconds again, TWRP started off fine, then froze after locking
Click to expand...
Click to collapse
You reverted back to stock. I assume you used a custom ROM. When you were unencrypted than stock forces encryption. That encryption process may last a very long time and depends on the amount of data.
You could think of wiping and formatting all partitions and do a factory reset.
Will try that soon, thanks ? completely forgot about encryption.

Beta 10 to 4.1.6 Rollback Nightmare. Help!

When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.
I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups
I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.
Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.
I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.

Data Partition always destroyed after turning off phone

Hello there.
I have a Huawei P9 (EVA-L09) with an unlocked bootloader and a custom ROM.
Since a few days I started experiencing something completely weird.
Every time I happen to turn off my phone (often only because the phone had gotten quite warm and I want it to cool down then) I then land in the boot animation and get stuck there. After forcefully rebooting the phone from there (about half of an hour) I held the Volume Up key for three seconds during the warning screen and eRecovery told me about the Data Partition to be badly damaged and it would be recommended to recover it.
There are two ways I can do from here (and also did):
First way is to let it recover using eRecovery, connect to my wireless connection, however the phone always tells me that there was a problem getting the package info for my phone. (Does Huawei stopped supporting the P9 eventually?)
The second way is to run TWRP and reinstall the custom ROM (In my case RROS 5.8.5 for my P9) and to never turn my phone off again. However this isn't always possible to keep it on since it also could happen that I'm not at home and my battery suddenly died.
Installing the stock ROM (or a custom ROM based on a stock ROM) however doesn't work. The stock ROM itself simply won't get installed, neither over the dload method or TWRP or fastboot and a custom ROM based on the stock ROM results in having my phone simply getting a black screen when locking it and then I need to reboot it to use it again.
What can I do? Could it be that my flash memory could be corrupted or something could have happened with one of the partitions of the phone?
Greetings.
EDIT: I managed to install a stock firmware using this link right here.
After the stock firmware was installed, doing a factory reset and wiping the cache every problem I mentioned above this edit vanished.

Can't reboot my phone - Softbrick

I think I have the weirdest soft brick ever. First of all my device works. I can use every feature with no issues till I reboot.
If my device is rooted and I try to reboot, it stucks on bootloader for about 30 seconds and loops on fastboot. There's no single reboot process gone smooth.
I could earlier fix this issue by flashing system, cache and boot all together from my back up. Now it doesn't work, at least it loops on android booting screen.
My device is MI 9T Pro 128 GB Global.
I flashed Xiaomi.eu 11 latest stable rom via the official TWRP and rooted with magisk.
I tried different TWRP's and OrangeFox to flash Magisk or formatting data but no solutions so far.
First time this happened I also tried to flash 'magisk uninstaller' but it didn't help.
I'm really new to this phone and triggered by this annoying issue. It's been 6 set-ups in 10 days. If anyone can help, that'd be highly appriciated.

Phone randomly shows boot animation on custom rom

Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)

Categories

Resources