HTC Sense Problem - Yesterday my clock widget disappeared mysteriously so I deleted it and went to add it back. When I did this, I got an HTC Sense error that Sense wouldn't load. I searched this forum, the Droid forum and the Verizon Wireless forum and it looked like what I needed to do was to go in settings-applications-HTC Sense and "Clear Data". I did this and it rebooted and went to the home screen but is stuck with this message "Loading.... It may take several minutes to complete, please wait." I waited an hour and all it did was continue with this message, occasionally popping up an HTC Sense error (it pops up and closes too fast to read it.
I've tried going to the boot menu and doing recovery, clear data and factory reset and it just does the same thing.
Weird thing is that the phone is giving me all notifications, etc., and I can go to anything that pops up on Notification bar, I just can't initiate any actions. I can't go to apps, settings or even dial, but I can answer calls.
Any suggestions.
Your HTC Sense apk might be screwed up. Have you been theming? I'd recommend to reflash a rom.
Still same issue
This phone was rooted. Has S-off in Bootloader.
Tried to run Unrevoked again but get an error on phone to force close and Unrevoked says not able to Root.
Tried to flash using RUU but RUU won't even start.
Tried recovery and it goes through process but after it is done it is still in the "loading".
Verizon is sending me a new phone tomorrow but I can't get the S-Off back to S-on so this will be a problem with warranty.
Anyone Have Sense!
After talking with the tech support guys at Verizon, it appears it is just HTC Sense not working properly since all other functions of the phone work. Does anyone know where I can download just Sense as an app?
Waiting
Finally figured out how to get it to Boot into Clockwork Recovery - I had to download an app from Market and then go into "my apps" from the menu - then went to ROM Manager and did Boot from Clockwork. Decided to go with "Wipe Data and reset factory settings".
Waiting on phone to reboot. For the last 5 minutes it has just had the Hat with the Orange Circle Clockwork Logo.
Fingers are crossed.
benjylafond said:
Finally figured out how to get it to Boot into Clockwork Recovery - I had to download an app from Market and then go into "my apps" from the menu - then went to ROM Manager and did Boot from Clockwork. Decided to go with "Wipe Data and reset factory settings".
Waiting on phone to reboot. For the last 5 minutes it has just had the Hat with the Orange Circle Clockwork Logo.
Fingers are crossed.
Click to expand...
Click to collapse
If you are seeing a a hat and Orange logo you hit the wrong button to reboot don't use the power button to select in recovery you use the track pad... tap the power button again and the menu should pop up then use the track pad to select reboot
Sent from my Incredible using XDA App
newtoroot said:
If you are seeing a a hat and Orange logo you hit the wrong button to reboot don't use the power button to select in recovery you use the track pad... tap the power button again and the menu should pop up then use the track pad to select reboot
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Thanks. Used the "wipe data/restore factory settings" line. Now phone keeps giving me 2 errors when it goes through initial setup:
"The application News (processcom.htc.newsreader" has stopped unexpectedly. Please try again."
Then at last step of the HTC Setup is gives me this error:
"Sorry! The application Setup (process com.htc.androd.setupwizard has stopped unexpectedly. Please try again."
benjylafond said:
Thanks. Used the "wipe data/restore factory settings" line. Now phone keeps giving me 2 errors when it goes through initial setup:
"The application News (processcom.htc.newsreader" has stopped unexpectedly. Please try again."
Then at last step of the HTC Setup is gives me this error:
"Sorry! The application Setup (process com.htc.androd.setupwizard has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
You must deleted something you shouldn't have..... wipe everything again and reflash the Rom
Sent from my Incredible using XDA App
If you got ROM manager installed, why not try installing a new ROM? If you like sense, I used virtuous for a while before switching to CM7. Virtuous is pretty much stock sense, just lets you tweak things a lot easier and comes with less bloat enabled by default.
I'd recommend formatting system and doing a factory wipe from recovery prior to installing the rom to make sure you start clean...
Thanks
Got it done last night. Weird though, I had to install CM7 first and then go back to Stock ROM after that because Stock ROM kept giving me errors when it was rebooting.
Thanks for all your help.
I used mskip's method to root my VZW Galaxy Nexus LTE: http://forum.xda-developers.com/showthread.php?t=1392310
Everything was working fine all night, so I don't think it was the root that did it, but I had just downloaded an app to test my LED and the moment I hit 'open' from the market the phone showed the colored spiral booting image which then froze.
At that point no buttons would work, so pulled the battery and attempted to reboot the phone into recovery mode since I had made all the proper backups.
Prior to the hard crash the phone was unlocked, properly rooted, CWM installed and working.
I've tried pulling the battery and SIM but nothing seems to bring it back to life. I was able to get some odd beeps when plugging the USB into my pc while connecting it to the phone but nothing would happen from that point. ADB devices and fastboot devices show nothing.
Any help or the dreaded 'bricked' word would be appreciated for the sake of learning and 'closure'.
Try leaving the battery out for a little bit, and maybe even charging it for a good 15-20 minutes.. strange as that sounds, it could help. I doubt you're bricked if all it did was crash during normal use, but you never know.
I would try leaving the battery out then charging a little.. maybe even reinstall your samsung drivers on your computer to make sure that isn't an issue..
Thanks for the info steps I've performed since leaving the post and reading yours, in order of execution:
*** Last night before making post (adding more detail now that I can think) ***
Prior to the root I had the issue a lot of people had reported in that the phone was somewhat temperamental at which cords it would charge on but 'most' of my micro's worked fine. Other than that I could get to adb and the sdcard without any issues.
The full sequence of events leading up to this is as such:
- Made sure I was fully charged
- Performed the root as mentioned in the OP
- Booted into CWM first thing and made a backup
- Used TiBu to restore some of my market apps (user only, no system apps) from my old rooted Incredible
- Finished setting up the rest of my phone
- Installed ROM Manager to update CWM to the newest version
- Installed the rest of my normal apps, then booted up TiBu and backed up all apps and their settings (user only, no system apps)
- Played with my phone for the next few hours with a reboot here and there if I installed an app and it's widget didn't show up
- About an hour after that I installed "market.android.com/details?id=com.rageconsulting.android.lightflowlite"
- After it had installed I clicked open and phone immediately jumped to the booting graphic and froze with no button response at all
- Pulled battery and rebooted, it showed the google logo (with the lock at the bottom), made it past the boot screen, got to the lock screen and no buttons or swipe action would take me to home screen
- Pulled battery and attempted to get into fastboot/recovery to no avail
- Attempted to get it talking to my pc and outside of the battery out OMAP4440 device manager message gave up for the night
- Uninstalled PDAnet, Samsung drivers, then used USBDeview to ensure I got them all, rebooted, reinstalled the Samsung drivers (Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe), rebooted, attempted to plug in phone and same OMAP4440 message
- Tried pulling the SIM and battery for a few minutes with same results
- Left it on the charger overnight so I could get some rest (same time when I left the OP)
*** Starting this morning at 10AM ***
- Let the phone sit on the charger overnight with the battery in
> No change
- Pulled battery for 10-15min then put battery back in and attempted to fastboot
> No change
- With battery in, tried plugging it back into my pc
> No change or response from Device Manager
- With battery out, tried plugging it back into my pc
> I attempts to installed drivers but always fails, I've attached a picture of the device manager during this situation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And an image from USBDeview:
(The instance ID that is chopped off: USB\VID_0451&PID_D010\6&1f916cd7&0&7)
At this point I'm still dead in the water
Ok, as a freak of nature I got to fastboot! I was doing a combination of trying to get the the OMAP driver to installed using samsung/pdanet drivers. A lot of plugging and unplugging with the battery out. Put the battery in one last time with the usb plugged in and finally got the oh so lovely 'vibrate' and fastboot loaded.
In the process of recovering to the original backup I made before the crash. Will let you know what happens from there.
I can get into the phone and restored my CWM backup from just before root, going to try flashing it back to stock and starting over after I give it time to charge fully.
Edit 11:53: Flashing the stock image back onto the phone and relocking the bootloader to see if the LED is still broken.
Edit 1:26: Phone is now locked and stock, trying to debug the LED since it use to come on while charging or if I was in a call. All it does now is one short blink and then nothing.
Edit 1:40: Looks like things are behaving again so back to root.
And back to the original spot I started at
When I tried to root, it got past unlocking, during the root I completed the steps to let it keep loading but then it went into a boot loop and kept jumping between the animation, vibrate, black google screen. After it did that a few times in went completely black and now back to no load at all (fastboot or recovery).
I've tried the battery pull and wait, but seems I'm back where I started . Ah the joys we put ourselves through out of the quest for knowledge .
Garoun said:
And back to the original spot I started at
When I tried to root, it got past unlocking, during the root I completed the steps to let it keep loading but then it went into a boot loop and kept jumping between the animation, vibrate, black google screen. After it did that a few times in went completely black and now back to no load at all (fastboot or recovery).
I've tried the battery pull and wait, but seems I'm back where I started . Ah the joys we put ourselves through out of the quest for knowledge .
Click to expand...
Click to collapse
Did you use my ToolKit for the second root or another root method?
What model and build are you on?
I dont see how the root method could make your phone not load into fastboot or adb as it only boots (not flashes) an insecure boot image to then push the 2 files needed.
Are you back running again or still nothing? If you get the phone running again then flash back to stock and exchange the phone. Just tell them the phone goes dead now and again.
Mark.
mskip said:
Did you use my ToolKit for the second root or another root method?
What model and build are you on?
I dont see how the root method could make your phone not load into fastboot or adb as it only boots (not flashes) an insecure boot image to then push the 2 files needed.
Are you back running again or still nothing? If you get the phone running again then flash back to stock and exchange the phone. Just tell them the phone goes dead now and again.
Mark.
Click to expand...
Click to collapse
Method: Yep, I used the Toolkit for the second try after using it to return to stock and locked phone. All drivers were working correctly but the main difference between the 1st time and second I did the root before trying to flash the CWM onto the device.
Version: (this is a snapshot from system info before the first root but it was 4.0.2 LTE/CDMA)
I honestly don't think it was the root that did it, since the phone was running stable for hours after the original root(including multiple reboots and charging). It wasn't until my LED Notification light started acting up that things went pear shaped, which started with Trillian then once I ran the led app that put the nail in the coffin. It was also having issues with recognizing most of my USB cables, only really had success with my included cord.
As from prior posts I somehow made it come back to life but could not achieve the same success with the 2nd SOD. Both times had the same case of seeing Device manager pop up the OMAP4440 pop up momentarily if no battery was installed, but not USB response at all by the PC if battery was in. The one time it worked I was in the middle of reinstalling PDAnet and the Device manager repeatedly tryed to reinstall the OMAP driver even though it failed every time but inserting the battery (while still connected) made the phone wake up.
I ended up biting the bullet and taking it back for warranty replacement. At least it was pretty much wiped clean (no titanium backups) at that point since I had just unlocked it. Lady up front said, "you broke it already", I responded with, "Well it was having issues charging on any cable other than what it came with so I didn't bother bring it in since I could get a charge, but after getting the rest of my apps installed I tried to open one and it went to that rainbow colored screen when you turn it on and froze. Tried pulling the battery but still wouldn't work". I simply answered the questions asked. Unfortunately, I'm going to hold off on rooting for now until I know my phone is completely stable since first one was having occasional oddities before I even touched the boot loader.
Considering I was only rooting and not doing any other customizations, only wanted to be able to backup/restore my apps and their data, my research made me think the SOD wasn't normal.
Am I correct in thinking that none of the actions made in ":applyroot" from the runme.bat should cause fastboot and/or ODIN to be unreachable if it fails at any point? Hell I don't even think a corrupt recovery should prevent it from at least making it to ODIN? I hadn't even gotten to the ":deleterecoveryrestore" step.
wow - I'm definitely curious as to what happend here. Could it have been defective hardware?
I'm leaning heavily towards defective hardware. The way my led and usb port started acting seemed like I had a short or something. The fact that it tried to connect to my pc with the battery out has me beyond perplexed.
Had done a lot of reading and researching to try to understand all the possible pitfalls, but this one had me dumbfounded.
I'm curious to see the reply to the questions on my previous post. I'll gladly answer any questions I can if it'll help someone else in the future.
Sent from my Galaxy Nexus using XDA App
Garoun said:
Am I correct in thinking that none of the actions made in ":applyroot" from the runme.bat should cause fastboot and/or ODIN to be unreachable if it fails at any point? Hell I don't even think a corrupt recovery should prevent it from at least making it to ODIN? I hadn't even gotten to the ":deleterecoveryrestore" step.
Click to expand...
Click to collapse
Nothing in the rooting procedure in my ToolKit would harm the system. First it boots (not flashes) an insecure boot image to gain temporary adb root access. 2 files are then pushed to the phone and permissions are set. After a reboot the only thing left on the phone is the 2 files (su and superuser.apk). These files have been used thousands of times to grant root for phones so there is nothing wrong with the way they work.
The Galaxy Nexus is pretty much unbrickable in that it should always be able to boot into fastboot mode as it it is totally outside the operating system and cannot be overwritten by flashing.
Dont be put off by your bad experience as im sure it was a very rare thing to happen
Mark.
my god ....i have the same problem as you ...but now i can't find any omap4400 driver....and i don't what the timing to put battery back to the phone ...
I'm just letting the phone rest for a while to make sure it's fully stable. I'm sure it'll eventually get rooted again (incredible has been ripped for a while now), for three time being I'll just have to use adb to push/pull my important app data.
Ade, I don't believe there is an omap driver we have access to, since my research has turned up that it's essentially the chipset trying to initialize. I am probably wrong, but for now I believe only a provider/manufacturer has that access.
Sent from my Galaxy Nexus using XDA App
Literally the same thing happened to me to.
Phone was rooted 4.0.2 with CWM recovery installed.
Turned off my phone this morning after charging all night.
Came back an hour later and saw the white full battery icon on the screen. Tried to turn it on and would not turn on.
Tried going into fastboot to no avail.
When plugged into PC all I got was the OMAP thing under device manager.
Took the phone to Verizon, they got it to boot up to the boot logo after removing the battery and then putting the battery in while holding the power button. The phone crashed after booting past the boot logo, had it replaced.
Firerouge said:
Literally the same thing happened to me to.
Phone was rooted 4.0.2 with CWM recovery installed.
Turned off my phone this morning after charging all night.
Came back an hour later and saw the white full battery icon on the screen. Tried to turn it on and would not turn on.
Tried going into fastboot to no avail.
When plugged into PC all I got was the OMAP thing under device manager.
Took the phone to Verizon, they got it to boot up to the boot logo after removing the battery and then putting the battery in while holding the power button. The phone crashed after booting past the boot logo, had it replaced.
Click to expand...
Click to collapse
So based on 3 quick accounts of this issue I'm wondering if there is a critical flaw that only pops up after the bootloader is unlocked.
Adesos and Fire, did you two use mskip's toolkit or another method?
In my case, the only common factors between my two roots was unlocking the boot loader and getting through the initial root. On the 2nd root it hardlocked before I had renamed the recovery reset file or installed CWM.
Trying to figure out some common ground.
So mship knows exactly what got completed before the hardlock, these are the parts that got completed from the batch before the bootloop.
fastboot-windows.exe oem unlock
fastboot-windows.exe boot root\boot_LTE_ICL53F_insecure.img
(had an issue with needing to restart the program at this point since I had to reboot into Android and enable usb debugging, did not have this problem the first time)
adb-windows.exe root
adb-windows.exe remount
adb-windows.exe push root\su /system/bin
adb-windows.exe push root\Superuser.apk /system/app
adb-windows.exe shell chmod 06755 /system/bin/su
adb-windows.exe shell chmod 06755 /system/app/Superuser.apk
echo Completed. Now booting back to FastBoot Mode:
echo.
pause
(The moment I hit Enter after this to kick off the reboot is when I got stuck in a boot loop, and it finally hard locked after about 6 reboots since I didn't want to battery pull unless it never stopped)
adb-windows.exe reboot bootloader
Again, the first root worked fine until I tried to test the LED notification light that had started acting up.
Hunh, now I wish I had a backup battery so I could see if something got screwed up with the battery since the phone acted like it was shorted or something when the battery was installed. (fact that device manager popped up the omap only when battery pulled)
I did indeed use the toolkit.
The first time I did it I unlocked bootloader. Phone rebooted tweaked it a bit.
About an hour later launched the tool before rebooting the phone into fastboot, tried to run the root exploit, all steps failed though since the phone hadn't been in fastboot first. So I rebooted into fastboot and then ran the tool again successfully.
Root was applied, then deleted the recovery restore file, then put CWM recovery on it.
I never once booted to CWM recovery. The next day the phone stopped working.
hi, did you get any idea to restore the dead phone???
13 days past away, and i'm only waiting to jtag flash a bootloader to my phone.....
1: i unlocked my bootlloader
2: i rooted my phone
3: fastboot flash recovery
and i'm very likely to know, how to get in the fastboot mode?
(1,with the battery in or out?
2, should i press any button when i plug the usb cable to phone?
3,or what esle i should do?)
thank you.....plz give me some answers....i hate to wait jtag info to flash my phone....it will be 1 month later or more....
adesos said:
hi, did you get any idea to restore the dead phone???
13 days past away, and i'm only waiting to jtag flash a bootloader to my phone.....
1: i unlocked my bootlloader
2: i rooted my phone
3: fastboot flash recovery
and i'm very likely to know, how to get in the fastboot mode?
(1,with the battery in or out?
2, should i press any button when i plug the usb cable to phone?
3,or what esle i should do?)
thank you.....plz give me some answers....i hate to wait jtag info to flash my phone....it will be 1 month later or more....
Click to expand...
Click to collapse
If the normal tests and attempts to get the phone at least booting, there had been mixed results of holding the power button only while putting the battery in, but the issue is honestly a toss up since I haven't heard of any other people with this problem.
I've been so busy at work I haven't bothered trying to root my phone again or track down more people with the same problem.
Your best bet may honestly be sending it in and take your chances.
yeah i'm busy in my work too, so my reply is late........
thanks for your reply
you mean that....
you just put battery in ...... and hold the power button......and plug usb cable to computer so you get in the fastboot mode???
adesos said:
yeah i'm busy in my work too, so my reply is late........
thanks for your reply
you mean that....
you just put battery in ...... and hold the power button......and plug usb cable to computer so you get in the fastboot mode???
Click to expand...
Click to collapse
You need to HOLD the volume up and down buttons then press the power button to get into fastboot mode.
MArk.
HELP!!
I have the exact same problem as stated before, however I don’t think it has anything to do with the rooting process. I unlocked and rooted the old fashion way weeks ago and have been running very stable since. However, yesterday I received my extended battery which has worked well and today I got a couple extra cables. I was charging both of my batteries with my new cable for 4-5 hours this morning at work. I was going to lunch and powered off my phone to switch out the batteries. Now my phone won’t turn on at all, with either battery. I have tried both batteries, with the OEM cable… nothing. If I have the battery out and attempt to plug into my PC I get the “looking for OMAP4400” pop up. I’ve tried every combination listed previously… has anyone got any new light to shed?
Title says it all. When we got this replacement, the power button was finicky, but we kept it for a while. Eventually it became annoying, and we decided to return it. Unfortunately, it won't stay turned on to reflash to stock. When plugged it, it sits on the Kindle screen. When booted to fastboot, it turns off after a couple seconds. Same if it's turned on without being plugged in.
Any advice on what I can do to return it to stock to send it back?
gsu_golfer said:
Title says it all. When we got this replacement, the power button was finicky, but we kept it for a while. Eventually it became annoying, and we decided to return it. Unfortunately, it won't stay turned on to reflash to stock. When plugged it, it sits on the Kindle screen. When booted to fastboot, it turns off after a couple seconds. Same if it's turned on without being plugged in.
Any advice on what I can do to return it to stock to send it back?
Click to expand...
Click to collapse
Two threads already deal with this: this one and this one
I elected to create a new thread (other than the one of mine you listed) because the thread title didn't attract attention to the current issue. The other thread doesn't address my issue. I understand the process to flash back to stock - if they KFHD will stay turned on, but it wont - even in fastboot.
Anyone?
Last ditch effort? Still having the issue and need to get it in the mail on Monday.
Here's the error I get when I try to flash the stock system image. The other two items flashed fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As long as you were able to get the stock boot and recovery back on it that is all I would worry about let Amazon worry about the rest. Try a factory reset of course you will have to race it before it powers off. Very likely the battery is dead that is why it will not stay powered on.
Thepooch said:
As long as you were able to get the stock boot and recovery back on it that is all I would worry about let Amazon worry about the rest. Try a factory reset of course you will have to race it before it powers off. Very likely the battery is dead that is why it will not stay powered on.
Click to expand...
Click to collapse
It wasn't staying powered on because of the faulty power button (the reason we RMA'd it in the first place). Got it to stay on and it actually flashed back to stock without that posted error for once. It actually had about a 90% charge, so I knew that wasn't the issue.
gsu_golfer said:
It wasn't staying powered on because of the faulty power button (the reason we RMA'd it in the first place). Got it to stay on and it actually flashed back to stock without that posted error for once. It actually had about a 90% charge, so I knew that wasn't the issue.
Click to expand...
Click to collapse
Very good glad you were able to get through it.
Got a stock GT-N7100 off a friend, kid was playing games on it and it rebooted, got stuck on GNII splash screen. Booted into recovery mode, reset data and wiped cache. Rebooted and this time it made it to second Sammy screen. So I decided to follow instructions I saw on a thread here basically this "Go to download mode and flashed CWM first. After flashing CWM wipe dalvik, cache partition & then data reset. U will loose downloaded apps or sms & call logs. Later flash a new firmware thru pc odin & the phone will start perfectly. Give a try. Hope it works for u. Its a risk but give a try. "
Did the first part, phone restarted and went to desktop. as follows which I have no idea what to make of (I am very familiar with an Note 1 i717)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I thought I will turn off phone and restart to recovery mode so that if it got rooted then I can flash SuperSU. But it was still stock recovery. Restarted and now it stopped at the first SGNII splash screen. I repeated the process but same result. I d/l latest Odin and philz recovery, odin was stuck at RESET! I let it sit and after a couple of minutes it said pass! I disconnected phone, removed battery and attempted to boot into recovery but it was still stock. When I attempt to restart it stops at SGNII splash or sometime it would go past that to the second flashing Samsung splash screen and just stop there. I don't know what stock ROM it has (EDIT - just confirmed it has 4.4.2) Now I am at the end of my wits and need help guys.
Decided to KIES restore the phone. It's been at 3% progress overnight and not progressing. I don't know if by disconnecting it now that will make it worse, possibly brick. What should I do?
UPDATE:
Disconnected, got the error "Firmware upgrade encountered an issue, Please select recovery mode in kies and try again." A jig got the DL mode on again. KIES went smooth this time. Phone attempted a restart but got stuck at the first splash "SGNote II" screen.
Attempted to enter recovery mode but it won't budge.
Guys I really need help with this thing.
Hello,
I tried to unroot my phone from SuperSU, my phone restarted and started to do smth in the boot screen. Now there's a LG logo on the screen and the blue light is slowly blinking.
It did so for like 2 hours then I gave up and tried to reboot. Power buttons didn't work so I took out the battery for a second and then tried to boot it up, it went back stuck to the LG screen, has been so since.
Now it has been like 4 and a half hours. No idea what to do, can't boot safe mode or anything, always the same boot stage stays.
This is called a Bootloop, if you have a custom Recovery like TWRP, try flashing another ROM (you will lose all your data).
If you don't have a custom recovery, you can Re-install the Stock Rom, take your time and read this Guide, it is simple and explained step by step: http://forum.xda-developers.com/showthread.php?t=2785089