Hi guys, I've installed many CFW without problem, until I installed the latest PACMan build. I didn't like it so I reflashed the Hasa v6, that i've been using for a while, and the phone just got kind of "crazy". I tried to wipe/format/wipe delvik, flash another rom via recovery, flash the stock FW with flashtool, still the problem continue.. I'll try t make a short list of the problems:
- Lockscreen usually hangs the phone, screen goes all black and playing with the power, after a while, it goes back sometimes
- Some force-closes (mainly the system process)
- Sometimes I can't boot to CWM, the "back" and "option" touch-buttons keep lit, and that's it, sometimes I can
- Also the battery status doesn't seem to be working properly, I charge it and it never pass the 30% mark, or get stuck on a number beforr it
How can I do a "brute-force" wipe, or something like that to restore my phone to it's normal state? These issues are driving me mad, and I can't see a solution..
Thank you very much!
The device is a Sk17i Mini Pro
Try flashing a kernel like LuPuS v3 or MESA Hybrid v3.7 via Fastboot and then flash the latest ROM that was working flawlessly.
Thanks, I tried with mesa and Lupus and after that, the same issues seem to occur..
Adding problems:
- I started having the "build prop" error, always when I flash CM-based roms, and I never had this issue before these problems (I do the workaround to install them by editing them with notepad++ and removing first lines..)
- The phone, once in a while, stay with the back and menu buttons lit for ages..
- The phone doens't turn off completely (menu and back and the screen stay lit, the screen is black, but it's ON), the only way to truly turn off is removing the battery..
- When I choose "power off" from the bootloader, the same issue occurs, the screen stay lit in black and phone doesn't turn off..
Please help.. I just don't know what is happening and it is so frustrating.
Related
Hi there, about a month ago my X10 Mini started doing weird thing. After reboot the screen is blank (black) and the notification LED is flashing red. There is no response to any keypress, nothing. The only option to turn off the phone is to disconnect the battery (under the rubber cover at the back). Then when I want to turn on the phone, again the same problem - blank screen and red notification LED. The only option to do something is to boot into recovery and flash/reflash ROM. Erasing cache/data wont help, only new ROM. And now, I reflashed the ROM, it started. I needed to reboot (inserted SIM card) and again, blank scree, red notification LED and no response.
The recovery is working fine so maybe the problem is in the kernel? Why? I was using this phone for more than a half year and without problem.
Specs: bootloader unlocked, nAa kernel, CWM recovery, ROM now GingerRobyn V04 (before MiniCM7)
//Just flashed latest nAa kernel - nothing new happened....
///There is something ****ed up in this phone. A few more times I reflashed the kernel and ROM, tryed stock ROM and kernel and its weird. When I restart the phone and do nothing - red LED. But when I restart the phone and Im constantly pushing the back key (as when I want to get into recovery) but stop pushing right when the screen lights up (only backlight), the kernel logo appears and it didnt go into recovery, but normally boots up into ROM. When I push the back button further when the screen lights up, it normally goes into recovery. And in the recovery if I go "reboot" or "turn off", when turning on the phone without pressing the back button until screen flashes up (then stop), it wont start, just red notification LED.
I wanna sell this phone so I need to fix this. Everything is working except this thing...
////Probably its not kernel or ROM based. Tryed nAa 13/14, stock and nAa JB 3 kernel - nothing changedm still b!tch!ng. Tryed stock ROM, MiniCM, GingerSony, Jelly Bean ROM - nothing changed.
Hi,
try plugging in your sdcard and then powering on you phone. Also make sure your battery has got some juice.
Good luck.
Sent from my Galaxy Nexus using xda app-developers app
nobodyAtall said:
Hi,
try plugging in your sdcard and then powering on you phone. Also make sure your battery has got some juice.
Good luck.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks! The MicroSD actually worked. Any idea why? When booting up, kernel/recovery/ROM needs to write something in it?
This is a known kernel bug.
Sent from my Galaxy Nexus using xda app-developers app
Thanks. I had the same problem.
Device: Galaxy Player 5.0 INTL (YP-G70)
ROM: Cyanogenmod 10.1 (7/23/2013)
Kernel: Sultan r5 INTL
Problem: The battery appears to be malfunctioning somehow. After using "Pimp My Rom" and enabling some tweaks, the device began to randomly turn off and loop on and off with a white battery outline onscreen. Now, the battery has sufficient charge. When it finally turns on, it's always over seventy percent. When it does turn on, if it is plugged in on the wall charger, it immediately turns off upon disconnecting this wall charger. Also, it displays "Android is upgrading, starting apps" at every boot. Managing to turn on the device after doing a reboot with the power button many times takes up to 15 minutes. It sucks. ):
Steps attempted:
Reflashing ROM and kernel using exact steps (wiping all data, /system, cache, etc.).
Flashing Cyanogenmod 10.2 (8/05/2013) with Sultan r6.
Deleting battery stats.
Cleaning charger and microUSB port.
Rechanging tweaks to the values I remember in Pimp My Rom. (IDK about all of them, if someone could post the defaults that would be great).
Draining battery (I did to 1%) and then recharging. Should I drain until it turns off?
[EDIT]: Tried flashing to Chip v1.5 with r14 kernel. No luck; it is just a different battery icon.
[EDIT]: Tried flashing to stock with Odin.
Are there any steps that I could possibly take to fix this? Perhaps flash to stock and see if the problem persists?
[WORKAROUND!] I've found a workaround, however annoying it may be. Plug in the YP-G70 and it should bootloop with the battery icon. However, as the icon disappears and the screen is black for about a second, just before it is about to reboot with the icon, pull the charger from the device. This has guaranteed my device to start every time; I can't ensure that it will work for you, but it is worth a try.
Please help!
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Click to expand...
Click to collapse
I have done many factory resets from CWM. Would flashing back to stock do anything that flashing another rom wouldn't?
Also, after scouring xda for answers, I saw iurnait recommended draining the battery until the device turns off. I'm going to try that I suppose.
I'd flash back to stock if that doesn't work
Sent from my YP-G1 using xda app-developers app
Unfortunately, flashing to stock using Odin didn't remove the problem.
I used a guide from androidromupdate
To be honest, I've given up. I'll update the original post with what I've tried and the workaround that I've found for this dreadful issue. If anyone else has this issue, best of luck!
I've got the same "boot loop with battery logo" problem, but without the random shutdowns are "android is upgrading" message on boot.
Some additional details:
I can boot into download mode without any trouble.
It will occasionally complete a boot, but gets stuck in the loop as soon as something causes it to reboot or shutdown.
I can sometimes boot into recovery mode. It will successfully go into recovery mode about 2-3 times before it will go into a normal boot.
Flashing alternate kernels (even going all the way back to stock) just changes the battery logo, but does not stop the bootlooping problem
The stock kernel was far more reliable than the others, often booting all the way after only 3 or 4 tries.
Throughout the boot loop, the battery logo (except in the stock kernel) will show as empty, even after being charged overnight
Upon a successful boot (all the way to android home screen), the battery is shown as fully charged (if it's been charging) or a level that seems probable (e.g. it'll show as 70-80% if it's been in download mode (which keeps screen on at full brightness) for a while or left to bootloop for close to an hour.
If it's not plugged into a charger, it only loops once each time you turn it on (i.e. battery logo shows for a few seconds then the device shuts itself off).
An update to Joseph's posted workaround:
I've found the button lights a perfect indicator for the timing. Wait for them to go black and then come back on very dimly then unplug the cable before the screen shows anything or the key lights go full brightness (like they are when device is fully booted and awake).
So my Xperia Ray has the display problem with the backlight lighting up only without the display.
I'm trying to install CyanogenMod based on thie
wiki.cyanogenmod.org/w/Install_CM_for_urushi
But when the device is supposed to enter ClockworkMod Recovery, I cant see a thing!
Now I cant start my phone!
HELP!
You mean the display of your phone never lights up? Or is it working on your rom?
Sent from my Nexus 4 running Android 4.3
mihahn said:
You mean the display of your phone never lights up? Or is it working on your rom?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Normally my phone works, but occasionally only the backlight turns on with the screen blank.
But now I tried installing CM9.1, at the part where Im supposed to install CM from the zip file, i cant because the display wont show (but the backlight is on).
Turning off the phone and turning it on wont work
Rapidknight said:
Normally my phone works, but occasionally only the backlight turns on with the screen blank.
But now I tried installing CM9.1, at the part where Im supposed to install CM from the zip file, i cant because the display wont show (but the backlight is on).
Turning off the phone and turning it on wont work
Click to expand...
Click to collapse
This means you soft bricked your device probably... if you are able to enter into Flasmode then do install the stock ICS .13 ftf file to get your phone working
Aneel said:
This means you soft bricked your device probably... if you are able to enter into Flasmode then do install the stock ICS .13 ftf file to get your phone working
Click to expand...
Click to collapse
I have the same problem. I've flashed almost every ftf and custom kernels with no success. Sometimes the phone will boot normally (screen on), but once it get to sleep mode the screen stays black with backlight on.
At first rebooting the device would solve this but every day goes worst, now it need a day to start normally.
I think this is hardware problem but i am not a technician to solve this.
If someone thinks otherwise please write a solution.
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
ampeme12 said:
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
Click to expand...
Click to collapse
Tried wiping cache and dalvik cache in recovery?
Christiaan91 said:
Tried wiping cache and dalvik cache in recovery?
Click to expand...
Click to collapse
Haven't tried that but I will give it a go mate
Hi guys,
I just flashed Carbon rom on my Z2. When it booted there was no problem, but after the screen went on standby i noticed my touchscreen wasn't working. I played with it for a while and it happens a lot. Sometimes i'm able to unlock the screen 3 times and sometimes the phone immediately disables the touchscreen. The only way i found to fix the touchscreen is to softreset by holding the red button. Is there any solution for this?
Also i'm unable to scan for wifi networks. I'm only allowed to go into the advanced settings but nothing more. When i slide the ON button for wifi, it gets stuck and i'm not able to slide it to off again.
I used the CARBON-KK-NIGHTLY-20141103-1906-sirius rom to flash my device. I'm sure i'll encounter much more problems.. but i can't play with it until i figure out how to enable to touchscreen hehe.
Thanks!
Edit: Also i'm unable to setup my mobile network, it gives an error when i click the search network button. When i enter all my APN information and press save it doesn't save and boots me back into the empty APN menu.
Edit2: So i decided to open up NDR Utils, gave me an error and now i'm unable to boot in recovery mode... It does vibrate and turn on a green led when holding the volume button.. but just boots into carbon. I was able to get into recovery mode using the carbon restart option.
Edit 3: If everything fails, am i able to just reflash the 314 stock rom with flashtool and use a different custom rom after?
Edit 4: I just wiped everything and installed a stable CM11 rom. I'm still not able to setup any wifi connection... did i break it?
Edit 5: It was the CM rom. I installed exitenz and everything works properly. I don't know what i did wrong, i followed a guide every time i installed both carbon and CM11, but no luck. If you install on Z2, keep in mind this might happen. Recovery was quite easy tho, even for a noob like me.
This topic can be closed.