okay, yesterday i got the jt super clean rom and stupidfast 1.54 kernel and it's been great. no problems at all...well i just plugged it up to my computer and it froze...i pulled the battery and rebooted it's just frozen and stays that way...i've rebooted multiple times and it's still happening. i can move around for maybe a minute or two, then its frozen again...i've reflashed a lower kernel and the kernel that came with superclean and still the same thing...what's going on? can someone help? thanks
Related
i have eb01 on my phone with super clean rom 2.3. ive tried all the other eb01 roms and they keep randomly turning off when the phone is fully charged but wont shut off when its hooked to the charger.. i dont know..any help
I haven't noticed this on Superclean 2.0 or 2.2. And please post questions in general. This is not development related. The devs do, in fact, check general.
Have you tried stock EB01? Try flashing the Odin EB01 file and do a complete wipe
I had the same problem also. I could never get it to come back on either unless I pulled the battery.
Tried clearing your dalvik cache and flashing a theme overtop and it should fix the issue.
I was instructed to do the same and its been working fine for a couple days now.
I too had the same issues. Both on DL30 and EB01. I was using Superclean with the midnight theme flashed. Being very frustrated, I updated to the newest Superclean NV and switched themes. I noticed last night Midnight was updated, flashed it and still no problems. I didn't wipe or clear the dalvik cache.
Maybe a problem with your theme?
Send from my FASCINATING Froyo'd DROID
Mine did the same thing when I updated to the 2.3 but when I went to the 2.4 it stopped.
Sent from my eb01 super fast fascinate
Anyone else getting random reboots? The weird thing is it looks like its rebooting, but it wont actually ever reboot. I have to pull the battery. Seems to have started after moving to the newest Bionix.
Could you provide a bit more information such as have you overclocked your device or tweaked any system settings that could have caused it? Also what specifically is your device?
Running Samsung Vibrant. Bionix-V 1.3.1 Gingerbread Edition. No other tweaks or anything.
Have you tried doing a restore to a backup from before you installed the Bionix software? If it only started after returning to what you had before should fix it. Can you get into your recovery menu to restore a backup?
Something similar is happening to me too, except its not reboots but shutting down completely. It happens a few times a day. I've reflashed, odined back to stock and flashed it fresh to no avail.
Sent from my SGH-T959 using XDA App
Problem: Phone wont turn on, at all. Completely unresponsive
Now for the lengthy story.
My original x had liberty aosp running nicely with an OC set on boot at 1200. A nice clump of pixels died randomly one day, so I called verizon for a replacement. I got my replacment refurbished X in the mail, and sbf'd to froyo, for rooted gingerbread upgrade.
I nandroid backed up my old X. I then installed liberty aosp to my new X, and then immediately restored the nandroid from the old X.
My new phone was running great for about a day, then I went and added some changes from the UOT Kitchen, and installed the app that makes the logcat the boot animation.
Again, the phone worked fine for a day or so, then while I was running google maps, it rebooted randomly.
It went through the boot logo, to recovery, so I just hit reboot. It went all through the boot animation, then back to the boot logo, then back through the boot animation.
I made it back to the home screen, then left it alone. After a while it rebooted again on its own. Sometimes the screen would black out, and be completely unresponsive. I pulled the battery, then put it back in, and it wouldn't turn on.
Sometimes, it would take the battery being out for 5 minutes for the phone to accept it, and turn on.
Now, just repeat the two previous paragraphs a few times, and you will get what happened to me.
After a while, I just restored my old working nandroid from the old X. It too had the same problem. I figured it might be my OC, so I set the settings back to stock. Same thing still..
I was then going to wipe data, and install liberty aosp again. The phone was in the recovery menu, so I went to mount usb storage, plugged it in to the computer, and nothing happened.
So, I unmounted usb storage, and hit reboot. The phone booted to the bootloader menu. I unplugged the computer, then tried to power off the phone, but the power button didn't work. So I pulled the battery......
Now the phone wont turn on at all. The battery was at a 70 percent charge at the final time it worked.
Once, I got the phone to boot to the bootloader menu, but once I got my sbf ready to go, the bootloader menu had frozen. Phone was unresponsive to inserting usb, and the sbf program didn't read my phone as being connected.
Again, im now back to a for real bricked phone, that when I hold the power button, it wont turn on. I did leave the phone plugged in, and later today, im going to try using a friends battery...
My dilemma, is now I can't send the phone back for another replacement, for fear it will work at the shop, and they will see my rootedness, then charge me for a new phone, even though im 99% percent sure nothing I did caused this crap.
Anybody have any ideas?
Sent from my DROID2 using Tapatalk
Sent from my DROID2 using Tapatalk
Refurbs not rootable??
I am having similar problems with a refurb X. I have SBF'd several times. The latest was using the Linux mehtod. Then I do the data and cache wiping and install CM7 Nightly 42 and Gapps.
Most of the time when the screen times out and goes to sleep it doesn't come back. When it does, it is by rebooting itself.
Other times it will just randomly reboot.
A few times I have had to remove the battery.
I am going to try a different ROM today and see if that changes things.
Use the linux too found here, has worked on many bricked phones, will work if you can get phone into bootloader mode for sure
www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
DROID X running liberty GB V.8
STAYFROSTY777 said:
Use the linux too found here, has worked on many bricked phones, will work if you can get phone into bootloader mode for sure
www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
DROID X running liberty GB V.8
Click to expand...
Click to collapse
That is exactly what I used to SBF. It works to SBF but when I load CM7 the device starts the random reboot and freezing stuff.
Does it only reboot with CM or does it do it when you sbf as well? If it does it when after you sbf, that is a legit problem. I would suggest if it does it in sbf, leave it unrooted and return it, they wont be able to tell it was rooted because sbf takes you back to stock froyo.
Sent from my NookColor using XDA Premium App
Mine continued to reboot after I SBF'd back to 2.2.1. I went ahead and did the upgrade that was pushed over the Verizon network and now it doesn't reboot.
Could it be something with the newer released Droid X devices and the kernel used in the OTA upgrade by Verizon?
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
so i just flashed the extreme syndicate rom and it seemed like everything went fine, but when it gets to the setup screen it keeps rebooting over and over again, ive waited for like 45 minute to see if it would stop rebooting but to no avail. any idea why its doing this? and im using the us996 variant by the way