[Q] my phone is continuously rebooting since I tried factory reset - Sony Xperia ZL

yesterday my phone was having difficulties when I tried answering a call. Today since morning, it was going off when the display got dim. So, I switched it off. This evening, when I switched it on again, it was having the same problem. So, I decided to factory reset. When I tried factory reset, the android icon was on display and after sometime the phone was on a reboot loop. Its trying to reboot automatically till now and failing again and again. what do I do now?

revolutionibus said:
yesterday my phone was having difficulties when I tried answering a call. Today since morning, it was going off when the display got dim. So, I switched it off. This evening, when I switched it on again, it was having the same problem. So, I decided to factory reset. When I tried factory reset, the android icon was on display and after sometime the phone was on a reboot loop. Its trying to reboot automatically till now and failing again and again. what do I do now?
Click to expand...
Click to collapse
Was your phone running a custom ROM, was it rooted or completely stock...Did you install or do anything to it previous to these weird occurences.
Try flashing your phone with a stock FTF or use Sony PC Companion to repair your phone (it will wipe completely and flash back the latest firmware for your device).
Good luck!

revolutionibus said:
yesterday my phone was having difficulties when I tried answering a call. Today since morning, it was going off when the display got dim. So, I switched it off. This evening, when I switched it on again, it was having the same problem. So, I decided to factory reset. When I tried factory reset, the android icon was on display and after sometime the phone was on a reboot loop. Its trying to reboot automatically till now and failing again and again. what do I do now?
Click to expand...
Click to collapse
There's nothing else you can do except flash it....

signal lost an continuous rebooting
Hello guys, I realy need your help here.
Some days ago, out of nowhere my fone lost it's signal and started to reboot. The only way of stoping it is waiting while it drain 10% of my battery or more, or forcing shutdown by the OFF back button.
Does any one know what is happening?
I saw lots of posts about this trouble with xperia ZL and xperia Z, but I got no solution from this.
Thank you!

Related

[Q] IceColdSandwich does Reboot instead of Shutdown

Hello,
today I flashed IceColdSandwich 7.0 on my DHD and when I want to shut my phone down it always does a restart. Anyone knows a fix for this?
cheers,
z3xi0n
not sure, but you're probably more likely to get an answer on the support thread for that rom. here:
http://forum.xda-developers.com/showthread.php?p=24364406
Sounds like a clock problem. Strange, I know.
Deselect the time auto-update, and change the time and date to something random.
Turn off, pull the battery before it restarts and leave for a few mins.
Battery back in and restart, reselect time auto update and you should be good to go.
Sent from The App that Time Forgot.
Tried your advice twice, phone reboots again and again ^^ Any other solutions? ^^
cheers ;D
I've been having the same issue since installing 7.x on my device. It got so frustrating that I restored a 6.x image via recovery, but unfortunately the problem still exists. The phone never restarted on shutdown previously, so I'm a bit confused as to what is causing the problem.
I did flash Touch Recovery recently, so might go back to ClockWorkMod Recovery to see if that helps.

[Q] Waking up to TWRP on phone?

A little back ground. Many months ago I rooted my phone and was planning on installing a custom rom. I never got around to doing it and the other day I got a notice saying that my phone was ready to update. I remember reading that if you were rooted you were not to install any factory updates because it could brick the phone. So I just figured I would leave it and not update it. So last night I plugged my phone in like I always do and went to sleep. I woke up and my phone was showing the TWRP screen. I could not get out of it. I tried a factory reset from the TWRP factory reset button as a last resort, still nothing. Is loading a ROM the only way to get out of this or did I brick the phone?
Thanks in advance.

OP3 rebooting to blank screen (with white notification light)?

Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
AWretchSavedByGrace said:
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
Click to expand...
Click to collapse
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
thelad said:
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
Click to expand...
Click to collapse
So done that and got one black screen and the white light,went to work had 3g/4g on all day didn't get one black screen,got home connected to wifi and I got a black screen,so something to the with wifi seems to cause it for me
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Paradoxxx said:
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Click to expand...
Click to collapse
I think I'll have to its pissing me off now,goes great for hour or two then I'll get this black screen 4 or 5 times in a row
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
nono77240 said:
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
Click to expand...
Click to collapse
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
I don't know how much time after, maybe 6 hours later or so...
I had a freeze yesterday evening and had to reboot my phone.
Everytime it freezes on reboot and I have to wait 3 to 4 tries before the phone really boot.
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
I created a RMA ticket this morning.
My phone will go to repair center
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
My situation
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Breecko said:
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Click to expand...
Click to collapse
Have you tried holding power and volume down for a few seconds without the cable plugged into the phone?
thelad said:
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
Click to expand...
Click to collapse
acmerw said:
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
Click to expand...
Click to collapse
AWretchSavedByGrace said:
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
Click to expand...
Click to collapse
I received a mail yesterday evening saying that they can't take my phone and I have to do a factory reset.
I replied to this mail saying that I did multiple factory resets and even do a remote session with a oneplus tech support.
They sent me a mail an hour after with a number and the process to send my phone.

Samsung Galaxy Tab S stuck in bootloop after flashing official ROM and factory reset.

After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800

LG G3 D855 blackscreen right after booting logo

Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.

Categories

Resources