ok
i've been usign whatsapp and suddenly my phone went into bootloop,
tried to enter fastboot, recovery
but he keeps on boot-looping after 2-3 sec of showing the fastboot-recovery icon.
i tried disconnecting the phone-battery-motherboard-etc, but he keeps going boot-loop, showing the first load screen, black screen, and so on and forth
any suggestions? never occured to me before , only after unsuccessful flashing, but like this? this is really weird.
i have a custom rom yes, but with it for a few months already , 0 problems.
p.s my phone fell on the floor few days ago, but had no problem since whatsoever
any clues on how to solve this?
i can't even get to flash via fastboot/recovery because it restarts when im there..
what could be the problem? the only thing pops into my head is that the restart key is pressed all the time, but is it possible?
I had the same problem, crazy thing. I couldn't even enter orange fox, got to the loading screen and got another reboot. I pressed power button fast many times and then worked. The power button seemed to be ok. The only thing that i had recently changed was the EAS version of the predator kernel. It may not make sense but i went back to HMP and now it's fine.
well! it worked lol
what is HMP? a kernel?
A type of kernel, the common one. Now i know that was not the reason!
Hello
I have the same problem as you and if someone has a solution, I will be very grateful !
I can use my phone but if I push to the power Button, it bootloop.
Related
Hi all, i installed the CM11 on my gf's Galaxy s3 (i9300 international version), the problem is that sometimes it randomly reboots and get stuck in an unusual bootloop. It reaches the bootsplash logo and it keeps rebooting, the only solution to get it back to work is to remove the battery for at least 30 seconds and try to turn it on, sometimes it works.
When the bootloop happens i'm not able to enter the recovery mode, because it just turns on and it keeps rebooting, same thing with download mode.
So, i'm new here, but i read about a common issue which is the sudden death syndrome and half-sds, it might be that? I checked and it has the insane chip.
Any advice/idea? It would be better to flash a stock ROM to be safe?
I would backup the whole device, recover initial firmware using kies emergency recovery mode and then start over again.
Had a similar problem but even worse: same bootloop, but no dice on recovery :\
Was unable to reflash or restore old firmware using Odin, Kies was the only thing that worked for me.
Nemed said:
Hi all, i installed the CM11 on my gf's Galaxy s3 (i9300 international version), the problem is that sometimes it randomly reboots and get stuck in an unusual bootloop. It reaches the bootsplash logo and it keeps rebooting, the only solution to get it back to work is to remove the battery for at least 30 seconds and try to turn it on, sometimes it works.
When the bootloop happens i'm not able to enter the recovery mode, because it just turns on and it keeps rebooting, same thing with download mode.
So, i'm new here, but i read about a common issue which is the sudden death syndrome and half-sds, it might be that? I checked and it has the insane chip.
Any advice/idea? It would be better to flash a stock ROM to be safe?
Click to expand...
Click to collapse
Do the reboots occure few seconds after pressing the power button?
I have exactly the same problem and I figured out that my power button is kinda stuck and thus permanently pressed.
This causes the permanent reboot, because holding the power button for a certain amount of time causes a reboot.
Try to push "Vol down"+"Homebutton" instantly after a reboot. If your galaxy enters the download mode (before rebooting again), you have the proof, that it's the fault of the power button due to the fact that pressing the power button would have been necessary.
I hope the fix will be for free under warranty.
At the first moment I also thought it would be the Sudden Death syndrom, but thankfully it's not the case and only the power button has to be fixed.
Togholl said:
Do the reboots occure few seconds after pressing the power button?
Click to expand...
Click to collapse
I don't know, i didn't paid attention to it. Anyway thanks to both of you for the replies, i'll check the power button as soon as possible since i don't have the phone with me right now. If that's not the cause, i think i'll do an emergency recover with kies as suggested by Cy4n1d3.
Now i still have a doubt, CM11 should have the fix for the sudden death syndrome merged into its code right? I'm asking this because if i'm right i could exclude sds as the cause of the problem...
Rebooting is not an SDS symptom, SDS is totally dead -suddenly.
Power button failure is diagnosed by inserting the battery, if it turns on by itself then button contacts are shorted out.
Your problem sounds more like corruption of the cache or dalvik, wipe and reflash your rom or go back to stock to test. Check MD5 of downloads and don't restore anything before you test.
hi...
I'm really desperate, my phone is suddenly dying and I have no idea why, I'll tell you from yesterday what has happened:
- I'm playing a stupid game and suddenly the screen goes black. No led, phone doesn't answer any button, nothing. I hold power button, nothing. Remove battery and put again, nothing. After some attempts phone turns on, but just after starting it reboots or stays frozen.
- I decide to change the rom (I had simpl rom), so I do a full wipe and put CM 12. It seems it works, but when I'm in the settings, at the beggining, I don't even have time to put the wifi, it starts rebooting again and/or not responding.
- Desperated, I install via odin the stock firmware from Sam Mobile. It seems it's gonna work, but when the dialog of "Android is upgrading -- Optimazitating app x of XX" it always gets stucked in a number, randomly. I never get to the 230 apps.
- As a last chance, I try Kies to install factory firmware. The same as before happens, but now it's only 17 the number of apps it tries to optimize.
These last 2 times, of course, I enter recovery from time to time (now the default one) and wipe cache partition.
My phone is agonizing, what the f is happening? Does anybody know what could happen?
Please help...
So i have bought my phone about 3 months ago. All have worked well, but a couple off days ago, it have had some problems.
It sayed 2-3 days trebuchet process have stopped and process.android.process.media has stopped. The only solution when this came i had to restart the device. I tried yesterday a factory reset but it didnt work.
Yesterday evening it did again the process stopps and then i tried to restart my phone. But when it shut down it dosent anymore go on. Now it dosent react to anything, not the normal powerbutton and not even the powerbutton + volume -. I havent rooted the device. So is there anything i could anymore do or should i just send it to warranty repair?
Im very desperate, thanks for all the help. But if you have an solution can you write it step by step, im not so experienced in smartphones.
Now i got the phone to restart but when it start it says over and over again that trebuchet has stopped. What can i do to this problem?
Edit: And now its stucked in the Zuk start screen. Dam im getting frustated...
Enter in recovery mode and do a factory/cache wipe
Have you installed any themes? Because some cm13 compatible themes cause system ui crashing
Hello, havent installed any themes. How do i get to recovery mode?
If the recovery mode is volume up and power button. This neither works, its still dead. Dosent even vibrate when pressing power button long.
Power on the phone , when you hear the vibration and the zuk logo appears , press both volume buttons, this should let you boot in the recovery
What happens if you connect the fone to charger?
But the phone dosent power on. So i cant do that. And no, the battery is not dead.
Ok, if you cant boot it, the last thing is warranty , where have you bought your device?
I could boot it today on the morning 1 time but then it again died and now its totally dead. I bought it thru tomtop, have put a message to the seller already. Lets se what they answer.
Ok, hope the seller will answer you , continue trying to boot it .
Let me know if wou solve it ��
Yeah the seller answered that i get a new device. But then on tuesday i tried a last boot, and it got alive again! I did the factory reset and now the phone has worked perfectly after that [emoji106]
But now the trebuchet keeps stopping and after that all the processes i have open. So now i changed to Nova launcher, i hope it would solve the problem.
Glad to know you solved the problem
Trebuchet problemi shoul be solved with marsmallow update.
maryankomar said:
Glad to know you solved the problem
Trebuchet problemi shoul be solved with marsmallow update.
Click to expand...
Click to collapse
Yeah it was solved like 5 days. Now the apps started to crash again :crying: And now the f***** phone dosent even start. Its just stuck in the Zuk powered by android start screen. Is there something i could do? I dont think the factory reset would help in long term beacause it didnt help the last time. Or should i just send the phone to the seller and request for a new one?
Edit: And now the factory reset dosent even work. When i try to reboot it after Factory reset its stuck on the Cyanogen start screen, so i think my last option is to ship the phone to the seller and hope i get a new device.
Edit2: And now after a second factory reset the phone started to work again. What can cause this type of meltdown? Could it be somekind of hardware problem or is it a software problem?
The Best solution is to change the device if you can, because you're not sure if it will work in the future.
Dear friends of xda,
let me say something first. i'm a possessor of a brand new zuk z1 since a week. from day 1 i've rooted it with kingroot and then switched to SuperSu because i didn't succed installing adb drivers on my laptop.
so i'm stock. no custom recovery no unblocked bootloader, just root permissions.
a week went by with no problem. just a couple of freeze here and there. nothing much.
today i was playing on my bed and suddenly the phone got really really hot. everything is frozen. i can only drag down the status bar. but if i press some icon or button nothing happpen. Ok i'm like well another freeze. i press and hold power button. screen get black. phone vibrate. aaaaaaaand i'm stuck at zuk screen. really?
after searching the web i tried to enter in recovery mode. after many tries i succed. so i tried to do a factory reset. it asked me if i'm sure, as i press yes the screen goes black for a while and then the phone reboot in recovery again. mmm strange. so i tried to wipe cache. it happen the same as before. it did not even asked me if i was sure. so i pressed 'power off' thinking that a real boot would repair the situation but no. my phone decided to self brick. ok. i throw in the towel.
so i decided to plug the charger in and went to do stuff.
when i come back home 3 hours later. i softly press the power button and the phone says it is at 99% . i tried to boot it up. and guess what? it boots normally. like nothing never happened.
so. what do you think is happened? i've some background but i've never seen something like this.
could be a problem of overheating? what should i do now? and what if it happens again?
sorry for the wall of text.
tl;dr: rooted phone get really hot. freeze. and after powering it off went in bootloop. nothing could be done in stock recovery. after some hour it booted up normally. what to do now?
Hi! I got my Essential Phone from someone that had it boot loader unlocked etc. I have experience with flashing and all so it was not a problem for me. Yesterday when I got the phone I went here and flashed AOSIP Rom again since it was the one it had but a wanted to make sure to have a fresh install etc. All working fine by then until about an hour ago the phone turned it self off and now it doesn't do anything. Every time it finally boots it shuts down again. If I try and enter recovery or Bootloader for fastboot, same thing. Sometimes it holds up for about 20 seconds and goes back to Off and be unresponsive for a period of time.
Has anyone had this problem before? If so, is this a Hardware problem?
I can't fix it by computer so I don't know what I am into right now. Its the only phone I have so I'm kind of stressed right now