I managed to get my phone running Freex10, went to install a custom theme and reinstalled xrecovery, but i FORGOT to install busybox again.
Now the phone will not launch xrecovery. When I get to the lock screen all looks good until i try and unlock the phone. Then it comes up with infinite notifications telling me that every process has stopped unexpectedly. The phone will also sit at the lock screen for a minute or so, then it looks like its trying to relaunch the OS. It will do that in an infinte loop. Also, it shows no network connectivity when its in the lock screen state.
The only thing I can do it pull the battery and start all over.
I would be very appreciative if someone could help me recover my phone as I dont know how to fix it without getting usbdebugging going.
don´t worry just restore the last firmware with flashtool if you don´t know how this is the post what you need
http://forum.xda-developers.com/showthread.php?t=920746
Related
I have just rooted my phone and installed xcyanogen v3.4 for the x10mini pro.
Everything worked fine, I have even managed to go into xRecovery after the installation and reinstalled xcyanogen three times.
This morning, I updated my Busybox from busybox installer from Market. Installed V1.19 busybox, I guess the previous one installed with cynogenmod6 was v1.15 then
The phone reboots suddenly, and hence after
*I only have an Unlock screen that works, displaying clock, charging stats, Sound off etc with NO SIGNALS
*If i unlock the screen, it will have a 'DSOmanager stopped Unexpectly force close' window followed by unlimited 'LauncherPro stopped Unexpectly force close' windows
*I am UNABLE to go into xRecovery to reinstall the system, unalbe to do anything now.
and the Phone reboots all the time automatically, but still get back to this unlock screen.
I am a newbie, any pros would help me pls? Thanks so much!
rccr said:
I have just rooted my phone and installed xcyanogen v3.4 for the x10mini pro.
Everything worked fine, I have even managed to go into xRecovery after the installation and reinstalled xcyanogen three times.
This morning, I updated my Busybox from busybox installer from Market. Installed V1.19 busybox, I guess the previous one installed with cynogenmod6 was v1.15 then
The phone reboots suddenly, and hence after
*I only have an Unlock screen that works, displaying clock, charging stats, Sound off etc with NO SIGNALS
*If i unlock the screen, it will have a 'DSOmanager stopped Unexpectly force close' window followed by unlimited 'LauncherPro stopped Unexpectly force close' windows
*I am UNABLE to go into xRecovery to reinstall the system, unalbe to do anything now.
and the Phone reboots all the time automatically, but still get back to this unlock screen.
I am a newbie, any pros would help me pls? Thanks so much!
Click to expand...
Click to collapse
Newbie too, and had the same problem, phone would boot into a low resolution mode (everything looked huge), followed by most applications and widgets crashing, I was lucky enough for the phone to forget the association with ADW Launcher and it allowed me to use the default home screen when launching it.
Now I'm in the process of repairing it using SEUS, need to charge up the phone before, is there's a way to fix this without having to lose everything? (Can't use the backup service)
rccr, try accessing safe mode, hold the menu key while it's booting.
Thanks!
Thanks! I have got to a post from xcyanogen forum, ways of recovering a 'killed device'. I was managed to flash back Sony Ericsson 2.1 using SEUS. Have installed back CyanogenMod6-v3.6, now everything working as before.
Help!!!!
Rccr can you please tell me the exact link?
You should never replace busybox on a custom rom or if ypy have xrec installed because they depend on their specific bysybox version!
Sent from my X10mini running on MiniCM 2.2.1 RC2 / aZuZu ZiG ZaG Alpha 0
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?
Okey, my problem is this.
I have installed the phone locator beta from their website. Like the name says it's an app to see where your phone is if it gets stolen, wipe it through sms and do some other stuff. I did not manage to finish the application setup cause I got a phone call during the process. After that I'm locked out of the phone and the phone screen keeps shutting down. It instantly shuts back down after I turn it on. It stays on for like half a sec sometimes, sometimes less. I have managed to uninstall the application through adb to no avail. I have made a backup through recovery also hoping I will be able to restore it without getting the same problem.
But it appears that if I restore the data I get the same thing happening.
Other things I have tried:
Reflashing ROM. It's the stock one from Vodafone.
Reflashing CF-Root Kernel.
Trying to figure out which process I have to kill through adb. But I'm not experienced enough with this to do it.
Trying to remove everything about the app I find out. Still did not work.
Anyone has another idea. I really had a lot of data I don't want to lose.
Thank you.
Update: Solved in post 3.
justrome0 said:
Okey, my problem is this.
I have installed the phone locator beta from their website. Like the name says it's an app to see where your phone is if it gets stolen, wipe it through sms and do some other stuff. I did not manage to finish the application setup cause I got a phone call during the process. After that I'm locked out of the phone and the phone screen keeps shutting down. It instantly shuts back down after I turn it on. It stays on for like half a sec sometimes, sometimes less. I have managed to uninstall the application through adb to no avail. I have made a backup through recovery also hoping I will be able to restore it without getting the same problem.
But it appears that if I restore the data I get the same thing happening.
Other things I have tried:
Reflashing ROM. It's the stock one from Vodafone.
Reflashing CF-Root Kernel.
Trying to figure out which process I have to kill through adb. But I'm not experienced enough with this to do it.
Trying to remove everything about the app I find out. Still did not work.
Anyone has another idea. I really had a lot of data I don't want to lose.
Thank you.
Click to expand...
Click to collapse
What I would do is enter recovery mode. From there mount usb storage and transfer everything that's important to PC. Then wipe everything, format system, format sd card and reflash a ROM through CWM. Obviously mount again usb storage to push the ROM from PC to sd card. Maybe it's a little drastic but I can't think of anything else since I'm not a pro user or anything. Well, just an idea.
Hey thomas. Thanks a lot.
I think that's a great idea. At least it's something I did not try and might work well.
I just found out that you can enter usb storage from recovery, right now it seems I can only see the /mnt/sdcard partition. I will play with it a little to see if I can mount the other partitions before mounting USB. I think the application data is in /data/data am I right?
Okey I have managed to fixed it in the most stupid way possible.
I have noticed that if I leave the screen off for like 15 seconds then I get like 2 seconds window before the screen turns off again. I have managed to go to the screen timeout settings and it seems like the application changed that to a very low value as none of the defaults value were ticked. I have ticked the 1 minute value and now the screen stays on.
I have uninstalled the app and I'm really afraid to test it again I should probably make another backup in this state
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 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?