I feel like this is going to be a long thread but I'll make it short as much as possible with as much details
I have a SONY Xperia SP C5303 stuck in a boot loop, it was given to me by a friend.
The phone was on stock firmware, android 4.3, unrooted, bootloader locked.
As he was using the phone while charging, he activated WiFi, after a while he activated Bluetooth (WiFi and Bluetooth at the same time) and then it just turned off, rebooted and stuck in the "SONY logo => Xperia logo=> Orange logo" boot loop and then it just fades away and blacks out and reboots.
After many attempts, he wasn't able to fix it and he gave it to me .
Now the first thing I did was flashing it using FlashTool with the firmware "C5303_12.1.A.1.207_AU" but still stuck on boot loop, the only thing that happened is that the Orange logo changed into the colorful waves animation.
I flashed it a couple of times more, the same method, but still, the same results.
Next thing I did, I updated it using SONY PC Companion, after the update finished, it was still in boot loop (ALTHOUGH, the lock screen DID appear but I was not able to do anything, and the screen faded away again)
So, I sent it to a repairer, here's what he have done :
_ He did something (?) and gave it back to me with 0 charge, so I charged it at home and when I turned it on, still boot loop, so I returned it to him.
_ This time, it ACTUALLY worked ! The phone came back to life, everything was working just fine, until I activated WiFi and I noticed that it's not working, then I activated Bluetooth as well (AT THE SAME TIME, remember what I said at first ?) then the screen just faded away and back to boot loop, I sent it back to the repairer and told him that he hasn't changed anything and that the real issue is that WiFi and Bluetooth do not work/cause boot loop when working at the same time
_ He revived the phone once again but the WiFi/Bluetooth issue was not fixed and he told me that there's nothing he can do anymore, and he refunded me.
I can't complain though cause all I wanted was the phone working !! I didn't care less about WiFi nor Bluetooth.
This morning, as I wanted to root the device, I tried the DoomLord Easy Rooting Toolkit, after flashing the first kernel using FlashTool (Yes, I followed the steps VERY carefully) and after the flash of the kernel finished, the phone is once again in boot loop, this time boot looping on the SONY logo only
So the conclusion is that the phone can actually be revived. How ? That's what I'd kill to know !! (Jk)
I tried flashing again the "C5303_12.1.A.1.207_AU" (4.3) but nothing, then I tried the previous firmware (4.1) but still nothing.
Sometimes, after the flashing, when the phone boots for the first time, the lock screen appears but fades away again (unable to touch anything)
SO PLEAAAAAAASE !! If there's anything I can do, please tell me, all I want is for the phone to work, hell to the data or anything else, also don't mind the warranty at all. And I'm not from the US, so there are no SONY service points here
There's a video in the rar file attached down there, it shows how the boot loop happens.
zedex39zeo said:
I feel like this is going to be a long thread but I'll make it short as much as possible with as much details
I have a SONY Xperia SP C5303 stuck in a boot loop, it was given to me by a friend.
The phone was on stock firmware, android 4.3, unrooted, bootloader locked.
As he was using the phone while charging, he activated WiFi, after a while he activated Bluetooth (WiFi and Bluetooth at the same time) and then it just turned off, rebooted and stuck in the "SONY logo => Xperia logo=> Orange logo" boot loop and then it just fades away and blacks out and reboots.
After many attempts, he wasn't able to fix it and he gave it to me .
Now the first thing I did was flashing it using FlashTool with the firmware "C5303_12.1.A.1.207_AU" but still stuck on boot loop, the only thing that happened is that the Orange logo changed into the colorful waves animation.
I flashed it a couple of times more, the same method, but still, the same results.
Next thing I did, I updated it using SONY PC Companion, after the update finished, it was still in boot loop (ALTHOUGH, the lock screen DID appear but I was not able to do anything, and the screen faded away again)
So, I sent it to a repairer, here's what he have done :
_ He did something (?) and gave it back to me with 0 charge, so I charged it at home and when I turned it on, still boot loop, so I returned it to him.
_ This time, it ACTUALLY worked ! The phone came back to life, everything was working just fine, until I activated WiFi and I noticed that it's not working, then I activated Bluetooth as well (AT THE SAME TIME, remember what I said at first ?) then the screen just faded away and back to boot loop, I sent it back to the repairer and told him that he hasn't changed anything and that the real issue is that WiFi and Bluetooth do not work/cause boot loop when working at the same time
_ He revived the phone once again but the WiFi/Bluetooth issue was not fixed and he told me that there's nothing he can do anymore, and he refunded me.
I can't complain though cause all I wanted was the phone working !! I didn't care less about WiFi nor Bluetooth.
This morning, as I wanted to root the device, I tried the DoomLord Easy Rooting Toolkit, after flashing the first kernel using FlashTool (Yes, I followed the steps VERY carefully) and after the flash of the kernel finished, the phone is once again in boot loop, this time boot looping on the SONY logo only
So the conclusion is that the phone can actually be revived. How ? That's what I'd kill to know !! (Jk)
I tried flashing again the "C5303_12.1.A.1.207_AU" (4.3) but nothing, then I tried the previous firmware (4.1) but still nothing.
Sometimes, after the flashing, when the phone boots for the first time, the lock screen appears but fades away again (unable to touch anything)
SO PLEAAAAAAASE !! If there's anything I can do, please tell me, all I want is for the phone to work, hell to the data or anything else, also don't mind the warranty at all. And I'm not from the US, so there are no SONY service points here
There's a video in the rar file attached down there, it shows how the boot loop happens.
Click to expand...
Click to collapse
I assume you've got no recovery installed? flash the william's kernel elf in flashtool. This will give you a kernel which has recovery so what you have to do is download and flash Omni-X, Nexus Prime's omni (my personal favorite) or Paranoid Android. These are all LBL Roms so you don't have to worry about anything at all. Also flash the Super Su binary. I'll provide the links to all these if you want.
Indeed, no recovery installed and PLEASE DO GIVE ME THE LINKS !! I'll try again and again until it's fixed, although I highly doubt that it will.
If all fails, I will just send it to the repairer once again to bring it back to life once again
Indeed, no recovery installed and PLEASE DO GIVE ME THE LINKS !! I'll try again and again until it's fixed, although I highly doubt that it will.
If all fails, I will just send it to the repairer once again to bring it back to life once again
zedex39zeo said:
Indeed, no recovery installed and PLEASE DO GIVE ME THE LINKS !! I'll try again and again until it's fixed, although I highly doubt that it will.
If all fails, I will just send it to the repairer once again to bring it back to life once again
Click to expand...
Click to collapse
you can't flash that ...you are locked bl right ?
NotAbdShahid said:
I assume you've got no recovery installed? flash the william's kernel elf in flashtool. This will give you a kernel which has recovery so what you have to do is download and flash Omni-X, Nexus Prime's omni (my personal favorite) or Paranoid Android. These are all LBL Roms so you don't have to worry about anything at all. Also flash the Super Su binary. I'll provide the links to all these if you want.
Click to expand...
Click to collapse
flash- said:
you can't flash that ...you are locked bl right ?
Click to expand...
Click to collapse
Yup, the BL isn't unlocked
flash- said:
you can't flash that ...you are locked bl right ?
Click to expand...
Click to collapse
I know he can't flash the kernel since he's on a locked bootloader. But if he flashes the rom as soon as booting into the recovery, then he will be using the stock .207 kernel and the Rom will boot
NotAbdShahid said:
I know he can't flash the kernel since he's on a locked bootloader. But if he flashes the rom as soon as booting into the recovery, then he will be using the stock .207 kernel and the Rom will boot
Click to expand...
Click to collapse
maybe the phone will get bricked and not boot ...idk
As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.
Hi guys,
I have been trying to unbrick my Turbo to get my pics back but not having any luck... hoping someone can help.
Background:
Bought this phone refurbished about 1 1/2 yrs ago and used Sunshine to unlock bootloader, installed TWRP, rooted, all was fine until last weekend. Battery was totally dead (battery icon wouldn't even show up with power button press). Plugged it in to charge and when I came back to it it was on the bootloader screen (robot lying down with his hatch opened). I can go to the Logs entry and it says 'Failed to validate boot image'. Any other option does nothing (except power off and Barcodes). Cannot boot into recovery. I can see phone info on bootloader screen along with "Device is UNLOCKED. Status Code: 3" "Software Status: Modified" but flashing has not helped.
Tried reflashing TWRP and stock Recovery and Boot with mfastboot, the phone seems to take them (no errors from mfastboot) but no change. I tried to flash the logo.bin from a stock image and the phone seemed to take it ok but after rebooting, the robot image and menu are gone (the text is still there... 'AP Fastboot Flash Mode (Secure)' with other info). The battery icon is also gone and all I see is 'static' when the low battery icon should be displayed attempting to power up with low battery. Same static seems to have replaced the 'Bootloader Unlocked' warning screen which flashed briefly before stopping on bootloader.
Are there any suggestions of how to get this phone back to life? I am really only concerned with getting the photos off (I already have a replacement; G5+). For some reason ADB does not see the phone. Any help would be appreciated!
Thanks
Hank
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
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.