Database Users

what gives?

So i've rooted my phone using the unrevoked method... every time I reboot the phone I get a message about "operation failed, check super user something or other" yet when i look in super user permissions, unrevoked, and overclock widget are there... (these are the only apps i can think of that i've granted, or need super user permission) Is there any way to see which program/widget or whatever is throwing that error?
Pardon me if this is a newb question...
Thanks in advance for any help.

i only played with unrevoked briefly, but i believe that you have to open unrevoked and run it again each time you reboot. thats probably why you're getting the error. those apps can't get superuser permissions.
good luck!

SilverStone641 said:
i only played with unrevoked briefly, but i believe that you have to open unrevoked and run it again each time you reboot. thats probably why you're getting the error. those apps can't get superuser permissions.
good luck!
Click to expand...
Click to collapse
I used toast's rooting method first, then unrevoked and have no issues. Others have no issues with unrevoked without toast's method.

why would you use toasts AND unrevoked??? they both essentially do the same thing

hmmm. I seem to remember reading somewhere that they made the root stick on reboot. Maybe They were talking about the next version. Thanks for the tip.

SilverStone641 said:
why would you use toasts AND unrevoked??? they both essentially do the same thing
Click to expand...
Click to collapse
Well no actually they don't..You can't flash custom roms etc with unrevoked for example.

toast's and unrevoked DO NOT do the same thing. toast's gives you write permissions to /system while in recovery. unrevoked allows you to write a few things to /data while in android, but is otherwise useless. nothing currently writes to /system while in android. so, your problem is the overclock bit, because that probably messes with /system, to which nothing can write while in android. remove it, i bet you don't have the problem. unrevoked works well for installing things like wireless tether, not so much for other things.
and, unrevoked has been modified to reboot everytime you start the phone. you don't have to reapply it.

Basically, unrEVOked is useless if you already actually rooted with toast's method.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.

timothydonohue said:
and, unrevoked has been modified to reboot everytime you start the phone. you don't have to reapply it.
Click to expand...
Click to collapse
so then is there any way i can figure out why I'm getting an error when i reboot about "operation failed, check super user"

[Q] Market problems.

I'm having a problem with my market app. The issue is when I download an app, it will download to 100% then start installing the app. But that's as far as I get, it never installs.
I've also noticed that when I go to the manage apps section, it just says computing & never finishes computing.
I'm perm rooted S-off originally had iced glacier then updated to if 1.1.1, currently I'm on cm6 nightly. Any ideas what's up???

Biggizzel said:
I'm having a problem with my market app. The issue is when I download an app, it will download to 100% then start installing the app. But that's as far as I get, it never installs.
I've also noticed that when I go to the manage apps section, it just says computing & never finishes computing.
I'm perm rooted S-off originally had iced glacier then updated to if 1.1.1, currently I'm on cm6 nightly. Any ideas what's up???
Click to expand...
Click to collapse
Yeah. Sounds like you jumped into rooting and ROM flashing before you really knew what you were doing.
Not trying to be insulting but you have to expect some issues if you are flashing different ROMs and what not.
JMHO of course.
Maybe you should reflash the stock ROM and start over.

[Q] n00b bricks glacier with Rom Manager

So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?

lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899

Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App

Also, you need to flash CW at least twice for it to take.

CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.

lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
First thing's first. Pull the battery for about a minute. Reinstall it then plug in the phone but don't try to boot. If the orange light comes on that's good. If not you might be in trouble but all hope is not lost yet.
krohnjw said:
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Click to expand...
Click to collapse
This is your best bet. Re-image it completely and start over, this time READ THE ENTIRE TUTORIAL BEFORE TOUCHING IT!!
jjjackson56 said:
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ADB probably won't be much help since he's not perm-rooted; it won't let him do anything. Just re-image the sucker.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
In order to perform a nandroid backup you need:
1. Perm root, NOT temp root, PERM ROOT.
2. S-OFF so you can successfully flash clockwork recovery.
Not trying to be harsh just want to be perfectly clear.
TeeJay3800 said:
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
Click to expand...
Click to collapse
Yup.

Possible Brick I Dunno what I did

So I'm fairly new to rooting but I have had android since the day it came out and I am good with the system. I have a g2 running a root of Visionary. I wanted to install a custom rom, so i was in Rom manager and i flashed in Clockwork Recovery, that went fine, and then i clicked back up current rom. I changed the name to original Rom, then the phone went blank then it had a g2 with a red triangle with an exclamation point in it. Does that mean the phone was bricked or what mode was that in? I pulled the battery and powered the phone on while holding the volume down. I think clicked the recovery option and the phone produced the same black screen with a G2 with a red triangle with an exclamation point in it. I then pulled the battery again, powered it up with the volume down button and did a factory reset and now my phone is back to how it was out the box running regular software.
Any idea what I did wrong? Or what went wrong? I would like to throw visionary back on and do a temp root and throw in a custom rom. My end goal is to do it once and have the phone run flawlessly and fast and never mess with any settings again. Help please!

Just for your information use the root method in wiki thats on this forum its easy. I think the visionary is outdated.
Sent from my HTC Vision using XDA App.

jjp023 said:
red triangle with an exclamation point in it.
Click to expand...
Click to collapse
The red triangle is the pre-screen to the stock recovery. At that screen if you press Vol + and Power (IIRC), it will take you to the recovery. I am not sure why you got this screen if you flashed clockwork recovery from ROM manager.
If the phone is not properly rooted, it probably cannot flash a custom recovery. Make sure you follow the instructions for rooting via Gfree in the wiki.

you are just soft rooted you will need to go through the root through adb

jjp023 said:
So I'm fairly new to rooting but I have had android since the day it came out and I am good with the system. I have a g2 running a root of Visionary. I wanted to install a custom rom, so i was in Rom manager and i flashed in Clockwork Recovery, that went fine, and then i clicked back up current rom. I changed the name to original Rom, then the phone went blank then it had a g2 with a red triangle with an exclamation point in it. Does that mean the phone was bricked or what mode was that in? I pulled the battery and powered the phone on while holding the volume down. I think clicked the recovery option and the phone produced the same black screen with a G2 with a red triangle with an exclamation point in it. I then pulled the battery again, powered it up with the volume down button and did a factory reset and now my phone is back to how it was out the box running regular software.
Any idea what I did wrong? Or what went wrong? I would like to throw visionary back on and do a temp root and throw in a custom rom. My end goal is to do it once and have the phone run flawlessly and fast and never mess with any settings again. Help please!
Click to expand...
Click to collapse
You can't load a custom recovery with only temp root (I'm guessing that's all you had). What you saw was the stock recovery (so your phone was actually fine and you didn't have to factory reset). If you want to load a custom ROM, you will need to follow one of the permanent root guides first (use the wiki or I just wrote another guide if you can't get ADB working). If you did have permanent root (check for S-OFF in the bootloader), try flashing the ClockworkMod recovery again (sometimes it doesn't take the first time).

ianmcquinn said:
You can't load a custom recovery with only temp root (I'm guessing that's all you had). What you saw was the stock recovery (so your phone was actually fine and you didn't have to factory reset). If you want to load a custom ROM, you will need to follow one of the permanent root guides first (use the wiki or I just wrote another guide if you can't get ADB working). If you did have permanent root (check for S-OFF in the bootloader), try flashing the ClockworkMod recovery again (sometimes it doesn't take the first time).
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Thanks for the help, I appreciate the quick responses. I hade visionary. I temp rooted it and then perm rooted by jus clicking the perm root on visionary. Not sure if that would do the same. I dnt think I have the confidence yet to perm room through terminal and writing scripts. what way would u suggest to perm room and What roms would u suggest that are relativly novice leve and provide signifcant improvement

jjp023 said:
Sent from my T-Mobile G2 using XDA App
Thanks for the help, I appreciate the quick responses. I hade visionary. I temp rooted it and then perm rooted by jus clicking the perm root on visionary. Not sure if that would do the same. I dnt think I have the confidence yet to perm room through terminal and writing scripts. what way would u suggest to perm room and What roms would u suggest that are relativly novice leve and provide signifcant improvement
Click to expand...
Click to collapse
Not positive how Visionary attempts to permroot, but you should check to see if you have it. Hold the volume down while powering on to enter the bootloader. The first line will say S-OFF if you have root and S-ON if you don't. If you have S-OFF, go ahead and try to flash the ClockworkMod recovery again (it just may not have worked that first time). If you have S-ON, or still have problems flashing the recovery, you can use either of the guides I linked to in the earlier post (you don't have to write scripts, but will need to use terminal---just follow the instructions carefully and watch for typos).
As far as ROMs, once rooted, you can try any of them really easily to see what you like best (be sure to make a backup first and you can always revert back). They are all pretty friendly to use right out of the box.

My phone is back to stock so I can't check lol. The link you posted titled guide seems pretty user friendly. I will attempt that root tnite... I will not do the h boot bc I dnt want more risk of a brick. Once I root I will flash clockworkrecovery. So in rom manager i should flash clockworkrecovery then scroll down to the bottom of it and backup current rom.how can I confirm its backed up? And once it is backed up I am clear to install new roms correct
Sent from my T-Mobile G2 using XDA App

If you were already S-OFF, doing the factory reset shouldn't return you to S-ON, so you could still check if you wanted to.
As far as backing up goes, once you choose backup in ROM Manager, your phone will boot into the custom recovery and you'll actually see all of the files getting backed up (there's also a progress bar). The backups are stored on your SD card in the clockworkmod directory (if you want to check to make sure it's there). After you have the backup, you're free to start testing new ROMs.

ianmcquinn said:
If you were already S-OFF, doing the factory reset shouldn't return you to S-ON, so you could still check if you wanted to.
As far as backing up goes, once you choose backup in ROM Manager, your phone will boot into the custom recovery and you'll actually see all of the files getting backed up (there's also a progress bar). The backups are stored on your SD card in the clockworkmod directory (if you want to check to make sure it's there). After you have the backup, you're free to start testing new ROMs.
Click to expand...
Click to collapse
So jus confirmed s on... so I will root using the guide u provided tnite.. few more questions jus to be safe I dnt wanna be a annoying but I appreciate the help...
1. Once rooted and in rom manager I should first flash clockworkrecovery then click back up current rom?
2.if I get back to the g2 with red triangle screen I should clikc power and volume down and which option should I choose at that screen?
Sent from my T-Mobile G2 using XDA App

jjp023 said:
1. Once rooted and in rom manager I should first flash clockworkrecovery then click back up current rom?
Click to expand...
Click to collapse
Yup.
jjp023 said:
2.if I get back to the g2 with red triangle screen I should clikc power and volume down and which option should I choose at that screen?
Click to expand...
Click to collapse
This just means the ClockworkMod recovery did not flash properly (and you are seeing the stock recovery). Just boot the phone normally and try flashing the recovery again in ROM Manager. If that doesn't work, there are other options we can try, but it should work fine once you are actually permrooted.

Sounds good. I'm trying to prepare myself to do this root later tnite.
I want to make sure I get the command right in terminal.
After the money sign and number signs there are spaces correct?
So my keystrokes shoule be (I dnt press $ or #)
$(space)su(enter)
#(space)cp(space)/sdcard/root_files/perm_root/data/local/perm_root(enter)
#(space)chmod(space)777(space)/data/local/*(enter)
#(space)/data/local/perm_root(enter)
Sent from my T-Mobile G2 using XDA App

You don't need to type the space at the start of the commands (they will already be there). Also you are missing a space in the second line:
cp(space)/sdcard/root_files/perm_root(space)/data/local/perm_root(enter)
Otherwise, looks good.

I know exactly what you're talking about with the triangle and red exclamation mark. Happened to me when i first flashed clockwork mod (CWM). What fixed it for me was to flash it TWICE when using Rom Manager. The first time you try to flash it, it doesn't always work, so you just reboot as normal (not into recovery) and flash CWM again and it should fix it.
Sent from my HTC Vision using XDA App

S-off, Superuser denying root like crazy

Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.

Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2

I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<

I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up

Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium

You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.

Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.

I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated

Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.

If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on

No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.

Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser

If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.

Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up

The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium

Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium

MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.

Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks

Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.

estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later