My OP6T is stuck in a boot loop after I restarted it. It is rooted with the blue spark kernel in place. I have tried formatting it but still won't start. What are my options?
I am guessing update 9.0.5 got applied automatically.
https://forum.xda-developers.com/oneplus-6t/help/stuck-bootloop-magisk-module-disable-t3866357
take a look some people ( like me ) are blocked like you xD
Related
Last night after a good night of working with my tablet out on the job I came home and noticed it was running a little sluggish so I rebooted it. It then proceeded to hang on the bootloader screen. I tried flashing into recovery and wiping and reinstalling but it still stays hung up on the bootloader screen. Getting into the recovery boot loader it says the secondary kerlel akb has an issue or something. Is there a way to Odin this thing back to stock? It's not totally bricked I can still get into recovery just can't get it to boot into the second kernel or whatever it means. I can get the exact terminology if someone needs it but I have been bricked worse than this before its just weird it won't fix itself after I re install a new ROM.
Sent from my A100 using Tapatalk
I am on the Skillraz V8 boot loader to be exact, and thats the first screen it gets stuck on..
I just tried flashing a stock un rooted ics zip but it still hangs on the first screen after rebooting after the install, which seemed to take ok... and it doesnt change my recovery or anything back to stock.
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
I have Cyanogenmod 11 installed in my device, and I tried encrypting it. Everything was ok, it went til 100 % and passed the Samsung Galaxy S3 Neo startup screen, but now it's stuck in bootloop, with the Cyanogenmod blue arrow going in circles. It's been like that for more than 20 minutes, so I know it exceeded it's time of booting. I encrypted my phone 2 times already, the first time with the settings in Cyanogenmod, and it got stuck in bootloop, so I took out the battery and put it back on booting my phone in recovery mode (I use TWRP), and formatting the data on my phone. All the data was wiped. the second time I encrypted the phone using terminal emulator, and the same thing happened: it's stuck in bootloop. Now, I'm not asking how to unbrick my device, because that I know, I'm asking how can I encrypt it without it getting stuck in bootloop.
Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.
I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.
Recenty i got a phone that was stuck in a boot loop. when you boot up the phone in the top right is said [ this binary is old , update to latest binary]. After getting issue resolved trying to flash the phone with multiple different firmwares for Samsung galaxy s7 AT&T, G930AUCUACSF1 was the one that i was able to flash but whe the phone was booting up it got stuck on the startup android screen, as in it was frozen. the boot animation wasnt even working. And yes i wipe the cache and did a factory wipe and still nothing.