I uninstalled Liberty 1.5 and reverted back to stock ROM due to better battery life, and because I was getting random lockup/reboots when trying to turn the screen back on by pressing the power button or home key.
However, since restoring the nandroid of my rooted, stock ROM, I've noticed that I'm still getting random lockups when powering my screen back on (which I never had issues with before installing Liberty 1.5). Are some of the scripts or settings from Liberty still active? Is there possibly another cause for my lockups? What are my options for fixes? Right now I can only think to completely SBF and start over from scratch. Thanks for your help!
Related
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
I was running CM7 7.02 from emmc with Dalingrin's 4/24/11 OC kernel, and was very happy with it. However, I got distracted by shiney... Rom manager gave me a pop up saying 7.03 was available, which it hadn't done in the past, so I figured, why not give it a shot?
I ran a full backup, installed the update, booted... and all my apps were gone. It was a fresh install instead of an install over my existing 7.02 like I would have gotten if I just booted from my CWM boot SD card and flashed. Well, crappy, but I have my backup, right? Still, might as well try the OC kernel and see how it runs real quick... oh, won't boot after the OC kernel. huh.
So I boot to recovery, and clear cache, and restore my backup.
Everything looks perfect. Back to my customized layouts... wait, where is my Honeycomb style bottom status bar? I'm back to the default look/feel. Ok, I can fix that... wait, why isn't my N button working? I've gone into ADW settings, selected several options for the "home button" functionality, rebooted, nothing works. I've got everything except a working N button. Why?
The only time it has worked is ONCE right after I installed a second home launcher, flashed 7.02 over 7.02, rebooted, and hit the button. It popped up and asked me which of the two launchers I wanted as default. After that, it hasn't responded.
Anyone have any idea what I did or what I can do to fix this? I'm fine if I have to format and start from scratch, I just would rather not since I'm stuck in an airport and waiting on a flight home, so I'd rather be reading/watching movies/playing music instead of tinkering... if it's something simple to fix, ya know?
That post just made me mental!
Sent from my Nexus S using XDA Premium App
I'm glad I could provide some amusement?
I ended up wiping data and system, installing 7.02, gapps, and 4/24/11, clearing cache and dalvik, then booting up and then refreshed my apps and data from Titanium. Everything worked great for a while and then the N button stopped again. No idea what happened. I've been working 16+ hour days for 7 days straight and can't think straight. On the up side, I was able to finish watching my movie on the flight home after my flight was delayed for 4 hours.
I need sleep. I also need to figure out why my button keeps dying. Works perfectly in CWM and to wake the device up, just not for it's intended purpose.
Had a similar problem with the N button not working with the 04/24 kernel. However it got working after a reboot...
One thing you could try is to use the 04/04 kernel instead. Might be a OC related issue.
I was running CM7 n136 with nook tweaks (overclocked to 1300). My NC randomly rebooted (probably because I haven't quite nailed down my undervoltage settings) and when it came back it had me at the android start screen (touch the android to begin). I clicked through it and almost all my apps were gone; it was like I was starting CM7 for the first time. I had a handful of force closes too (they just popped up right away before I could click through the startup). Not a problem, I thought, and I went to recover with ClockworkMod (3.2.0.1). Restoring doesn't work and I end up at the same screen. I've tried restoring two different restore points and neither works.
Any ideas how to get around this?
Thanks for all your help!
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?
My A500 hasn't been acting quite right. Since I upgraded a while back to a FLEXREAPER rom from Taboonay (HC) I've had numerous SOD issues, but even more so worse and worse crashing and hanging.
Things I've done:
Full wipe/install of latest FLEXREAPER, Lightspeed, Taboonay (3.1). My A500 would hang even during initial setup (google account, etc). Eventually I'd get through the setup and it would still crash (screen freezes) or SOD. Oddly enough, I can't seem to format my internal sdcard .. but I have wiped everything else several times, and absolutely before installing any of the ROMs.
It would also, many times, not even boot. The white power light would come on, the vibrator would spin, but nothing would happen on the screen. It would boot about one in five times.
I then tried going back to a reinstall of old HC Taboonay 2.2 .. it worked for quite some time before, but now it's hanging and crashing just as it did with the ICS ROMs.
Up to this point I didn't touch the bootloader, which meant I was on the old HC bootloader. But in doing a lot of reading it seemed that many SOD issues were fixed with the new ICS bootloader (unlocked and patched).. so I used nvflash to flash a the ICS bootloader.
Well, this solved my only-would-boot-one-in-five problem and it boots everytime. But it still crashes. I even had it crash in CWM 1.7 just like everywhere else ... frozen screen. I've never seen that before in any of my Android devices.
I really don't know what's happened at this point. I'd be happy just to go back to a version of HC that works. I'm downloading timmyDean's V4 3.2 package (the depositfiles link is the only one that works .. and it'll be done in ELEVEN hours.) to attempt a shot at going back to full stock. But considering that's 11 hours or more away, without knowing it'll work .. I thought I'd ask.
Is there any way to downgrade from the ICS unlocked/patched bootloader?
Is there another bare-metal restore for HC out there besides the hellishly slow timmyDean V4 on depositfiles? Another location to download it from?
Is there anything else I can do?
Thanks ...
Found EUUs_SBK_Acer_A501_0.017.01_PA_ATT on some russian site.
I was able to reinstall everything back to 3.01 from the EUU loader. However my A500 still has serious problems.
- During loading the EUU, getting it in AXP mode worked every time, but bouncing it to Download mode worked rarely.
- Most of the time when attempting to power on it will turn on the power light and vibrate, but nothing shows on the screen.
- Sometimes if it makes it past the above, it will display "ACER" but go no further.
- Once actually loaded into an OS (doesn't seem to matter which one) it will lock up after a short while with the screen frozen. Only a hard power off (hold power for 5 sec) will shut it off.
- It will simply die if soft powered off .. not right away, but after some time.
So, is my A500's hardware broken? I can't seem to get any part of it stable.
Many reinstalls later, all options expired. Returned to Acer for warranty repair.