So here is my problem:
My OnePlus 5T is stuck in a bootloop. The device was stock when it started, and is now back to the latest stock ROM.
In between I tried serval custom ROM's and a custom kernel to solve my bootloop issue. Flashing other ROM's, kernels or recovery's didn't do it. The device still is in a bootloop. It goes as far as the boot logo, then freezes and then reboots. Sometimes I can acces the operating system, but that only lasts for a few seconds before it also freezes and reboots.
Is there anyone who can possibly help me with this issue?
Thanks in advance.
u may have to wipe system, data, and both caches also u may have to format data (will wipe internal storage, so make backup to PC or OTG) and install a clean official Oxygen OS from their site, do u have TWRP?
also if you have overlays from substratum can cause issues if u have not wiped system and data.
Bradl79 said:
u may have to wipe system, data, and both caches also u may have to format data (will wipe internal storage, so make backup to PC or OTG) and install a clean official Oxygen OS from their site, do u have TWRP?
also if you have overlays from substratum can cause issues if u have not wiped system and data.
Click to expand...
Click to collapse
Thanks for the reply.
I have wiped system, data and both caches and formatted data. I clean installed the lastes build of oxygen(5.1.2).
Unfortunatly this still gives the same result. The phone crashes on boot. For now I have tried these OS:
Oxygen OS: Gets stuck on boot logo
TheOne5TOS: Gets stuck on boot logo and goes back in TWRP.
Android Open Source Project Extended: Loads OS. crashes after a while. Gives me a black screen with a purple notification light.
For TWRP I use Blu Spark for the 5T
Added: I don't use substratum
Try the unbrick tool. Its my last resort and always works if u can get it into dl mode.
Woodrow256 said:
Try the unbrick tool. Its my last resort and always works if u can get it into dl mode.
Click to expand...
Click to collapse
I tried the unbrick tool. Connected the phone and downloaded the stock firmware. But this gets the same result as previously. It loops.
It's a hardware issue, u need to contact oneplus, someone else had that issue too, not sure the outcome though
Related
I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
LegatoExia said:
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
Click to expand...
Click to collapse
You flashed the TWRP in wrong way. You need to flash it by this method.
Mirhawk said:
You flashed the TWRP in wrong way. You need to flash it by this method.
Click to expand...
Click to collapse
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method (including your tutorial in your signature, which I'm trying as I write this) solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Edit : finished following your tutorials, everything seems to work for the moment, hope it will stay stable this time... thanks for your help )
LegatoExia said:
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Click to expand...
Click to collapse
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Mirhawk said:
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Click to expand...
Click to collapse
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the Lollipop Pure AOSP rom, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. After installing the ROM, I followed your recovery tutorial using "openrecovery-twrp-2.8.5.0-LT26i.img", hope I did the right thing this time, hahah. Thank you again for your help !
LegatoExia said:
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the rom AND the recovery, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. Thank you again for your help !
Click to expand...
Click to collapse
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Mirhawk said:
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Click to expand...
Click to collapse
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
LegatoExia said:
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
Click to expand...
Click to collapse
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Frostymoon said:
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Click to expand...
Click to collapse
I guess You are on stock firmware and flashed the "stock-6.1.A.0.452-twrp-2.4.0.0.elf" or the twrp.img file via fastboot directly. Flash the DoomKernel from here via flashtool as kernel and it will work with stock and have recovery too. Use the blue coloured "Download Now" button and the extension of file is .elf.
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
Hi,
I just got my OP3 today.
I unlocked and flashed TWRP. so far so good.
Then sideloaded OOS, and also sideloaded blue_spark kernel - switched to f2fs on cache and data partitions. The phone booted successfully.
Then I transferred the FreedomOS rom to the internal memory and flashed it, and used elemental's kernel.
The phone loaded up for a couple of minutes, didn't complete the boot, then bootloop.
I wanted to flash it again, but I noticed that my internal data was erased, and I don't remember doing that...
I thought maybe it had something to do with the changed filesystems, so I tried to restore the cache and data partitions back to default.
The cache successfully restored. the data partition procedure did nothing for about 15 minutes, and then I rebooted.
Tried flashing again FreedomOS using sideload - bootloop again.
Tried flashing OOS again, using sideload - The phone just freezes at the boot animation (the boot animation is still the FreedomOS's animation, for some reason), then the screen turns black, the LED remains lit, and nothing happens....
What the hell is going on?? For years I've been flashing ROMs, and it never happened to me.
Can someone please advise??
Thanks
Have you tried to change the file system with TWRP ?
Dushaine said:
Have you tried to change the file system with TWRP ?
Click to expand...
Click to collapse
Yes, did it for the cache and data partitions - the ones I changed for the blue spark kernel.
These are now ext4
I think I'll try flashing stock OOS 3.1.2....
I'm lost here...
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
geokilla said:
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
Click to expand...
Click to collapse
wipe dalvik art cache, cache and system
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
geokilla said:
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
Click to expand...
Click to collapse
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
OhioYJ said:
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
Click to expand...
Click to collapse
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
geokilla said:
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
Click to expand...
Click to collapse
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
OhioYJ said:
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
Click to expand...
Click to collapse
I've asked in the Havoc OS thread but the instructions to clean and dirty flash are the same as when I first played with custom ROMs back in the Samsung Galaxy S days. Wipe system, wipe data, wipe the two caches, etc etc.
If you're using a Substratum theme, make sure to disable all overlays before flashing.
Sorry for digging this post, but with android 10 there is no way to decrypt the data partition.
So how do you dirty flash android 10 "properly" ?