• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Update crashed my Comando

C

Comandead

Lurker
My rooted comando updated last night, yes I know its not supposed to update when rooted but this morning it said update complete and rebooted. When it came back on it locked up as soon as I slid the icon over to unlock the screen.
Well it doesn't really lock up, it pops up "sorry *** has stopped unexpectedly ..." and the force close button is the only one that will work.
Each time I press the close button another one pops up.

Windows still recognizes the card when I plug in usb and ADB.exe still works. I backed everything up with titanium b4 I rooted. Can I manually copy everything back using ADB, if so, what are the dir paths? I don't see the phone memory in windows.
Please help this is worse than the blue screen of death in windows. [:{

ps; I've tried rebooting and removing battery many times, I've clicked that damn "force close" button hundreds of times, when it goes through all the processes it starts over.
 
Thanks, I tried it but can't get past the 1st line. "the system cannont find the path specified"
I can get it to reboot recovery from adb so I tried pushing recoveryFlash.sh > /data/local/recoveryflash.sh
It said it pushed it but still boots to base recovery - just the triangle and droid...
 
so when it's attached to usb, you can see the phone in adb shell? i would think you'd be able to install the custom recovery.
 
Yes adb sees it, and looks like su loads but then in the last step it says permission denied.
I even rerooted and repeated the steps got same results...

ps
I might have this thread in the wrong place mods, sorry
can you move to all things root so maybe I can get more help?
thanks in advance
 
oh shoot. the update killed your superuser, so you'll have to root again i would think. then you should be able to install the custom recovery.
 
yes, I've tried a few times now. rooted with the .bat file and the superoneclick and gone through the whole process several times.
Get errors at random places, I guess it depends on how many times I click that "force close" button on the home page.
Gonna keep trying different combos and see what happends
 
another guy had this issue too in all things root..

said re rooting fixed his issues.

whats so updated about the phone now btw... lol?
 
You must log in or register to reply here.
Back
Top Bottom