I installed eclipse for ICS with no problem. I then restored everything using Titanium backup. When I rebooted, however, a prompt eventually come up saying something like problem with Eclipse launcher. After two more reboot attempts with the same results, I went to the startup menu, and changed it to reboot without safestrap. (I honestly can't remember why I did it, but regret immediately followed .) Now, when I reboot, it tries to start the stock ROM and gets stuck on the red electric eye. Every time I reboot now, I get to that same point and it goes no further. I can't even access the startup menu anymore. Can someone please help me?
Related
I have been trying to add a rom to my lg optimus-t for pretty much the whole afternoon. I rooted it fine but when I tried to install AmunRa to make a recovery but that failed that was ok though since the ROM I ended up choosing asked for a different recovery system. The ROM I chose to use ciaox's openoptimus build
So I installed ROM Manager and did a recovery with clockwork mod, everything seemed fine until I loaded the clockworkMod and got E: bad boot message "recovery" I decided to continue anyways and followed the steps and when I finished part one it actually booted up, but I was unable to see any icons. All I was able to see was the lock screen and the network manager bar at the top.
There is a second part so I thought maybe if I went through all of the steps it would fix itself. It was all going great until I got to phase 2 #16 because it just wouldn't do it and the error message I got was "you cannot program the qcsbl header without the partition". in my infinite wisdom (dun dun dun) I decided to re-install everything, went to the recovery file and nothing happened, said it didn't exist. I had the rom so I decided to wipe the phone again and re-install it, now it doesn't even load and I realized I should have stopped to re-install somethings in the beginning.
Thankfully the clockworkMod recovery still boots and I have all functionality there(Well except for the recovery), so is there anyway for me to get 2.2 and install that into my phone to start all over again? A quick answer would be awesome, sorry for the novel, TIA.
Edit: got the rom up and running again, but I am back at the :"The Application settings (process com.android.settings) has stopped unexpectedly. Please try again" stage where I get the full unlock screen and the top bar that work, the emergency dialer still works as well. I tried doing phase2 again and following the instructions, but the phone goes into emergency mode and shuts off. At this point I'm thinking of trying another more simple ROM where I dont have to change the basebands, does that sound like a good idea?
After I restarted my Cell the boot animation keeps on replaying after the slight vibrate, same thing hapens for 10 mins then the mobile starts.
Its not normal
Can anyone help?
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
hirentherock555 said:
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
Click to expand...
Click to collapse
Found a partial solution after formatting the cell twice like a fool
Last night while playing Dangerous chambers 3D or somthing my cell got hanged.
Later it wouldnt restart or anything so had to pull out the battery.
After it started it went into loop mode.
I got worried
Formatted it once.
All ok later then again after some apps it went in loop mode.
Couldnt figure out which app was causing the prob.
Then today morning after some reasearch found out that:
In CM7 settings in settings menu> Tablet tweaks> disable lock screen> Tick
This is what i used to do to use an alternate lock screen.
After removing the check all is fine untill now.
Will update if anything happens next.
I also met this problem when trying to develop a CM7 ROM myself (from HPA CM7 BETA2). My problems are:
1. After building successfully, apps inside the output /system/app folder are bigger (in size, of course) than the original HPA ROM (ADWLauncher in HPA is 731.5K, and mine after building is 1M)
2. After flashing to DV, my phone hangs at the CM7 logo. It's OK to type "sudo adb devices" to see that my device is attached, but then any command other than that will receive "error: closed"
Guys, do you know what's the problem with my build?
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
Hey
So this old i9000 phone came with some Horrible bloatware I wanted to get rid of.
I flashed a stock Rom with Odin, (I've done it many times before on a different i9000)and Wiped Data and Cache afterwards, And 3 different Roms give me this problem:
When the phone finally initializes, Everything keeps Stopping unexpectedly. I've tried to get to enabling ADB to maybe view the logcat but I can't even get to the settings.
I did notice in the recovery mod an error that said something about System/CSC/CEL/system not being accesible (And i'm surprised it's still there after 3 flashes, CEL being the CSC for the bloatware company)
What do I do?
Currently on Stock rom with stock recovery.
Edit:
Okay, I have managed to race through the crashes, Launch the Home app, and enable ADB... so we have that now... "ADB devices" Shows its connected.
Edit2:
They all crash with "java.lang.ClassNotFoundException:" Right now Home screen is working but anything i try to run crashes
Edit3: It's like the old Gmail account is HARD CODED to it, What the hell? 3 rom flashes and countless factory reset, The account is still there, I cannot get rid of it.
So I've been running KitKat via CM11 nightlies for quite a while now and about every other week the I lose signal and have to reflash stock. I Use Razr Utility (http://www.droidrzr.com/index.php/t...-verizon-droid-razr-and-droid-razr-maxx-only/) to flash stock, get signal, reroot, and reinstall SafeStrap. Have done it I think like 80 times or so now.
Today when I did it, when I pressed start at the Setup Wizard it said "Preparing may take a few minutes ... blah blah" then it reboots. I rebooted and tried again, over and over it won't get past the language selection, and if I leave it alone for a few minutes w/o pressing anything it will reboot on its own still; it continually reboots over and over. Also I am no longer getting service back on a fresh stock flash. I have tried 1.8/1.82/newest of RAZR Utility, all received the same result. So I tried House of Moto with 2 different VZW firmwares (2 newest JB) and still same result.
I was able to get root w/o having to mess with Smart Actions and then use ADB w/ su and PM to disable all the setupwizard BS so I could install SS and get back to CM11. (Setup Wizard is locked and no way to bypass, even tried build.prop tweaks to turn it off and nothing) Now on CM11 it is liking to randomly reboot whenever it feels like it too; that is if it even boots back into CM11 after rebooting, sometimes it makes it all the way to CM11, sometimes it doesn't.
Does anyone know WTF is going on with my device and how to fix it. I'm going to try and get a new SIM tomorrow and see my SIM fried or something (though I never received the "No SIM" error). I'm honestly about to chuck this phone through the friggin wall....
Update: Was finally able to get CM11 to stop rebooting, upgraded to newest nightly and wiped Dalvik & Cache, and Fix Permissions. Signal has sort of come back, it goes in and out; very finicky.
Update 2: Service is completely gone and can't get it back now.