Bootloop? - Xperia SP Q&A, Help & Troubleshooting

Hi, i've got a problem after flashing the newest tangerine kernel (11.3). I had previously BlissPop ROM v3.5 with tangerine kernel installed. I tried to flash the new kernel (but i forgot to wipe the cache and stuff before :facepalm. So my phone vibrates, bootes (no SONY logo, just a black screen not even backlight). I first thought i was because my battery was empty, but after charging the battery directly with a external charging electronic was my phone still in the same state :crying:. My question is : What am i supposed to do to get it working again? I already tryed to do a fast boot but the blue led didnt turn on.

Related

[Q] Stuck on Samsung logo + previous flickering problem

Hello.
About one month ago I rooted my Galaxy Note and flashed Phliz kernel, but kept the original ROM.
A couple days ago my phone started to have some screen flickering and battery drain issues. The screen started flickering and the battery drained till 15%, when the phone completely shuts down. This happened a couple of times. I always put the phone to charge after this, and was able to power it on.
But today this happened and when I tried to power the phone on, it stucked on the Samsung logo screen. And stays there forever. I tried to restart and even do a factory reset (I dont care about my data since its everything on the cloud). The problem persists.
When I put the phone to charge the battery charging icon appears and apparently it charges normally.
I am able to enter the Recovery mode (CWM Touch) and the Download too.
What should I do? Can the problem be the battery? Maybe I should unroot it? Flash a stock kernel?
allanpoppe said:
Hello.
About one month ago I rooted my Galaxy Note and flashed Phliz kernel, but kept the original ROM.
A couple days ago my phone started to have some screen flickering and battery drain issues. The screen started flickering and the battery drained till 15%, when the phone completely shuts down. This happened a couple of times. I always put the phone to charge after this, and was able to power it on.
But today this happened and when I tried to power the phone on, it stucked on the Samsung logo screen. And stays there forever. I tried to restart and even do a factory reset (I dont care about my data since its everything on the cloud). The problem persists.
When I put the phone to charge the battery charging icon appears and apparently it charges normally.
I am able to enter the Recovery mode (CWM Touch) and the Download too.
What should I do? Can the problem be the battery? Maybe I should unroot it? Flash a stock kernel?
Click to expand...
Click to collapse
flashing the latest stock rom shuld do the work.. stay on stock kernel with 4.1.2 may be u wanna try 4.2.2..watch my video for that link is in siganture
Mayank Chandwani said:
flashing the latest stock rom shuld do the work.. stay on stock kernel with 4.1.2 may be u wanna try 4.2.2..watch my video for that link is in siganture
Click to expand...
Click to collapse
Can I follow your video step-by-step even having a custom kernel (Philz) and CWM?
Mayank Chandwani said:
flashing the latest stock rom shuld do the work.. stay on stock kernel with 4.1.2 may be u wanna try 4.2.2..watch my video for that link is in siganture
Click to expand...
Click to collapse
I did it. I followed your step-by-step video. Everything seen to be ok. Unfortunately the same error is happening, the only difference is that it's stuck on the Nexus welcome screen (the X), not the old Samsung screen.
It kept this screen till the screen started flickering again and the phone shut down, as before.
So, I changed the recovery to the normal 6, the kernel to the CM and the ROM to the Nexus 4. None of these solve my problem. What to do now?
So... I tried to flash a stock ROM (JB XXLSZ) through Odin. I did everything according to this video ?v=nmLm2pTdxk0 from youtube.
I also changed my battery to another (non-original) that I arranged. Now the flickering stopped.
Now I'm on a bootloop (like he was at the first try), but I tried the second time and it continues on a bootloop. Also, when I go to the stock recovery, it says:
"e: Failed to mount /efs (Invalide argument)"
It appears I bricked my phone? I do not have an efs backup.
Can anyone help me?
No one? Common guys, I don't know what to do...

[Solved]Phone not booting or charging or going into recovery

Recenty I flashed latest nightly Avatar and NX kernel
And I was texting and the battery died. Screen went blank like its supposed to on battery drain but I could hear a low sound (notification) for a few secs then it died. Now phone won't boot . It passes the samsung logo then goes blank. So I flashed safe kernel to get stable rom but can't boot into recovery mode. DOWNLOAD mode is working.
Also it won't charge. The charging icon is just stuck on loading symbol but not showing green bar progress.
I don't understand what happened
How do I fix this?
help! :crying:
Solved
....
titus1 said:
....
Click to expand...
Click to collapse
What?
How did you solve this? I'm running NXT kernel and Rootbox. My phone went flat ,tried charging but just shows empty battery logo. Just wont boot or go into recovery

Note 3 Battery died, now wont boot.

So I was at work and my phone had 5% battery left approximately so i shut it down to be able to use it right after my shift ends. So when my shift ended, i tried to boot my phone back up and it makes it to the ATT splash screen but will not go any farther. I rebooted into recovery mode and my phone showed battery at 1%. I placed my phone on the stock usb 3.0 charger and it showed that it was charging. i tried booting again after a while but it wont get past that splash screen. During the time that its stuck on the splash screen, the blue LED pulses.
Its been charging for an hour and the battery logo is showing at least 50% now but it still wont boot past that screen
Im on 4.4.2 and its rooted (i have the safestrap recovery). this has happened before but i didnt have the patience and reflashed the stock kitkat firmware through odin and re-rooted. I lost all my data and would like to avoid doing that again. any help would be greatly appreciated.
ant6893 said:
So I was at work and my phone had 5% battery left approximately so i shut it down to be able to use it right after my shift ends. So when my shift ended, i tried to boot my phone back up and it makes it to the ATT splash screen but will not go any farther. I rebooted into recovery mode and my phone showed battery at 1%. I placed my phone on the stock usb 3.0 charger and it showed that it was charging. i tried booting again after a while but it wont get past that splash screen. During the time that its stuck on the splash screen, the blue LED pulses.
Its been charging for an hour and the battery logo is showing at least 50% now but it still wont boot past that screen
Im on 4.4.2 and its rooted (i have the safestrap recovery). this has happened before but i didnt have the patience and reflashed the stock kitkat firmware through odin and re-rooted. I lost all my data and would like to avoid doing that again. any help would be greatly appreciated.
Click to expand...
Click to collapse
have you tried booting with it connected to the charger?
ant6893 said:
So I was at work and my phone had 5% battery left approximately so i shut it down to be able to use it right after my shift ends. So when my shift ended, i tried to boot my phone back up and it makes it to the ATT splash screen but will not go any farther. I rebooted into recovery mode and my phone showed battery at 1%. I placed my phone on the stock usb 3.0 charger and it showed that it was charging. i tried booting again after a while but it wont get past that splash screen. During the time that its stuck on the splash screen, the blue LED pulses.
Its been charging for an hour and the battery logo is showing at least 50% now but it still wont boot past that screen
Im on 4.4.2 and its rooted (i have the safestrap recovery). this has happened before but i didnt have the patience and reflashed the stock kitkat firmware through odin and re-rooted. I lost all my data and would like to avoid doing that again. any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you get into Safestrap atleast or not?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras
xXPINCARXx said:
Can you get into Safestrap atleast or not?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras
Click to expand...
Click to collapse
I tried everything with no luck. Ended up just reflashing my firmware again. I'd like to know what that issue was however, in case it happens again.
Alright, did you install any xposed modules or anything of that sort?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras
xXPINCARXx said:
Alright, did you install any xposed modules or anything of that sort?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras
Click to expand...
Click to collapse
i did not, it was 100% stock 4.4.2 firmware, rooted with towel root and safestrap 3.75
System tuner is an app i use, and i changed some build.prop info such as dalvik vm heap growth limit, start size, and wifi scan interval. but thats about it
Sorry for the late reply but these changes could simply be your problem. Though I am unsure of this it's really the only thing that would make sense besides a hardware issue
DK 4.1, GPE Orange, Xposed, xgel, and other great extras

Stuck with three blink lights

HI! My D5833 was with cyanogenmod but I want the stock rom, so flashed with flashtool and everything went fine but the phone now is stuck in a loop with three red light blinks (dead battery, but I flash with 100% battery) any ideas how can I use the phone again??
When that happens flashing stock with flashtool usually fixes the problem. Considered your are writing in the wrong forum, are you sure you flashed the correct firmware? Also if you have a backup check wipe userdata in flashtool when flashing

Xperia Z3+ E6553 - strange issues, i wanna help

If you dont want to see all my story, go down 2 see the base of my problem and second question.
Hello, i recently bought this phone in last week, used, for fifty euros and it had 32.3.A.2.33 firmware, and please remember WHITE boot screen.
It havent bootloader unlocked.
For some hours of using, it runs fine, except display, seems to be changed by amateur person, sometimes bad touch sensitivity, but i turned on glove mode and no problem. No lags, camera working, every thing - no problem so far.
And then problem began - after restart for sim change, phone boot animation was very slow, and some display flickering. When it booted, system was very slow, display had very slow reactions, i thinked it was GPU or software problem. After some minutes it itself rebooted, 2 red blinks and then booted very fast.
I tried some restarts, 2 of 5 was this problem.
I tried unlock bootloader, and install TWRP, because i think this isnt GPU problem, if 3 times booted and works flawlessly for HOURS !
Okay, bootloader unlocked, twrp installed, i searching for some roms, but phone have very bad community on XDA, i downloaded 3 roms:
AOSCP 3.5.1 - works flawlessly, no display flickering or something, some bugs like camera with bad quality photos, but after restarts, no display flickering or lag and this is important. But no boot screen (pure black boot screen)
Ressurection Remix 5.8.5 - Android 7.1 - after restart it HAD flickering and lag, something similar like first stock rom, 2 of 5 boots... Not very bad but yes. Very good rom.
LineageOS 14.1 - EVERY BOOT HAD THIS PROBLEM. LAGS, DISPLAY FLICKERING, RESTART AND 2 RED BLINKS.
So i installed again AOSCP 3.5.1 and no problem, only camera.
My not intelligent head was a plan - i prove a downgrade. To 28.0.A.4.8 - stock android 5.0.2. Phone gets black boot screen, and EVERY boot had this problem. Lags, scuttering, flickering... But it booted. I try restart, but no difference. 5 of 5 boots had this problem.
I have installed again nougat rom but not like first, but 32.4.A.1.54. After start flashing with flashtool - report an error with boot_delivery.xml - so i checked exclude bootbundle - no problem with flash. Restarted.
Phone had a BLACK BOOT SCREEN - i looking, because nougat sony roms has a white boot screen.
First boot without Sim card - no lags anytime. It has restarted itself, because i wanted to add sim card.
After reboot, every reboot had this problem.
I tried flash with fastboot twrp like first - https://forum.xda-developers.com/xperia-z4/development/twrp-twrp-3-1-1-z3-z4-t3862684
After fastboot reboot - phone has 2 red blinks and not turning on. I put cable out and i trying to turn on it, but it only vibrates 3 times and nothing. Boot or something, i thinked it is dead, but FOR TODAY im able to get into flash mode and bootloader.
I skip some 5 days with trying with flashtool LP, MM and NOUGAT roms, FLASHING TWRP, Sony companion is unusable, because i unlocked bootloader... My phone (or fifty euros) is in holy phucking s+++ in 2 days of using.
Okay, only twrp what i can boot normally is 2.8.7.0 recovery by old 5.0.2 android Z-ROM https://forum.xda-developers.com/xperia-z4/development/zrom-custom-rom-z3-e6553-28-0-8-251-t3206005
For questions, i tried both this stock firmware and custom rom, rare thing is boot normally, but after restart, no difference.
I tried flash again first stock rom 32.3.A.2.33, no difference, but BLACK BOOT SCREEN aside of white.
One but only one different 3.0.0.0 twrp what im able to flash, only into FOTAKernel or RECOVERY not boot partition, because RED blinks and nothing, but this twrp is from sumire (z5):
https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050.
I founded this argument by flashing and aoscp rom and error: This is for (ivy), your device is sumire.
I think i can change update_script - there i changed every ivy to sumire.
Installed with this twrp flawlessly, flashed magisk, reboot.
Again Red blinks...
Now what im able FUNCTIONAL only - flash 2.8.7.0 (too with display flickering and , but this twrp is ONLY for install Z-ROM, other roms like aoscp and RR i cant install because error E1004: cannot install system boot image.
And other twrps i can flash only to boot (kernel) partition, but red blinks or boot again into this 2.8.7.0 recovery.
I am making with Sony, and i had in the hands SO MANY phones , so many from them for repair, from different brands for 7 years, no problem with flashing so far (i thinked i am unstoppable :victory: ), and this is my 2nd phuckedup phone for whole 7 years (first was LG G6) and i wanna help, because i have working flash and bootloader, but i havent an idea what next, because some (80 percent) threads havent functional download links for NO SUPPORT or something, but this is absurd. Like my issue, but this is real. For example: i have Xperia SP for 6 years, with stable recently updated (30.9) LOS 15.1 and Xperia S (recent nAOSP 8.1) for 7 years, flashed anything, anything, anything... Downgraded, upgraded... And no problem for today. Reliable phones as... SP is my primary phone (for 6 years) and S for testing. I wanted something from sony but more performance - functional for 2 days. And karma is here - in xda.
Recently i put it into wall charger, it booted into that 2.8.7.0 recovery and it had 94° and it still breaths ! And really it was very hot ! Normally it had less than 60°.
If i flash through fastboot mentioned newer twrp 3.1.1, 3.0.2, 3.2.3 or other mentioned, what non-functioning there, after that red led blinks, it will go to (green) flash mode.
The main problem is: I am able to go into flashmode and fastboot, i can boot system, but (now) i am able to flash only one old recovery, where i CANT install and boot for example aoscp rom or other rom without problems (black screen, then red blinks, then green flash mode). Original software - lags, display scuttering, graphic artifacts but rare thing is going flawlessly, so i think isnt gpu problem. I need real help. I need this phone and i think it can be recovered. I can send anything from this phone (logs or videos), what would be helpful.
After factory reset + system format, in that old recovery, i have in internal storage (sdcard) folder with name 0. Everything cleaned, but this folder remains.
So there is second question, someone experienced with this issue ?
Problem with aoscp fixed. Very luckely, but no problem now !
I had an version of flashtool, 0.9.18.6, maybe i havent problems, because i had older phones from sony (my fault) and newer versions i have experience, cant found .ftf with older firmware.
An error, what i had in older flashtool when i trying to flash both nougat and marshmallow roms - entry (0000084F)parsing error boot_delivery, which means an program for boot.
I doing an very bad thing - check exclude bootbundle and flash was without errors, but this is reason, why i havent an white screen in nougat and marshmallow and amount of recoveries i cant flash so i cant flash an rom.
What i do is install an 0.9.23.1 version of flashtool (because i have an x86 notebook and today versions dont support x86, only x64)
Downloaded orange PL 32.2.a.5.11 (marshmallow official stock rom) from XperiFirm and it flashed bootbundle without problems !
I restarted it - WHITE BOOT SCREEN and HOORAY ! But lags, display scuttering and things, what i writed here, was here, also after itself restart - 3 red blinks. So after 3rd reboot i take cable, plugged in with volume +, fastboot flash boot 3.1.1.0 recovery and it worked.
Flashed AOSCP, magisk and booted without problems, no lags, no display scuttering and etc.
I am very glad i fix my problem, but an question still, why in official firmware or some custom roms (except AOSCP) i had this problems with lags, graphic artifacts, scuttering and reboot in random time with 3 red blinks ? On EVERY official firmware
Hint for you
If you have problem like me, every custom rom making problems, use boot image from aoscp https://androidfilehost.com/?w=files&flid=143620
I am not maintainer of this rom, i want only help others, if your device lags or graphic issues.
Maybe you get bootloop, but with this boot image i havent experienced after every reboot any problem with mentioned lags or again flashing twrp.
Still question for E6553
I tried almost all roms for this device and every other roms have problem with mentioned.
After flash and restart, every boot have problem with display flickering, lags and very, very slow reactions.
Even with every official firmware.
AOSCP is ONLY FUNCTIONAL SYSTEM FOR MY DEVICE ! But it have some bugs, like automatic brightness, bluetooth turning off, nfc not working, accelerometer or little bit heat and idle battery drain (it is fixed by GlassCanon LXT magisk mod) or screen does not turn off when i call, but never this boot problem.
One thing what i see, aoscp havent boot logo from sony and when i get out boot.img from this rom and put it into other custom roms (like LineageOS 14.1, crDroid or RR) and reboot it, no lags, no display flickering, pretty fast boot animation, but bootloop, so this boot.img is proprietary.
I tried from androidfilehost download aosp ota, but error 7 in twrp and when i change this in updater-script, then error 6.
Next what i tried from aosp - fastboot flash system.img - and i cant install it, because this file is big - around 1.2gb.
I am in corner with this phone and i wanna help, what more i should do for stable system or fix bugs in this rom.
Thanks

Categories

Resources