Related
After the OTA update killed my phone, I used Odin to recover and then put Bionix 1.9 on my phone. Everything was good until last night when I tried to put the 1.91 update on. It looks like I have lost root and/or superuser permissions. I ran Clockwork recovery to load the ROM and it booted, let me pick the ROM and then started giving me error messages like:
The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. And force close.
Now Titanium backup and other root apps won't work. I tried unrooting and re-rooting with no luck. What should I do?
In Rom Manager run > Fix Permissions.
If that doesn't work un-install Superuser and reinstall.
I don't seem to be able to uninstall superuser. It's like I lost root and can't get it back. There is no superuser app listed to uninstall.
You're probably just better off ODINing back to stock and flashing straight to Bionix 1.9.1. There's some releases of Bionix 1.9 that had some issues, you may have gotten a bad copy.
I am downloading the stock image to my home computer now. Something is all screwed up with my permissions.
I am new to the Samsung so I have a noob question, why do some roms only let you Odin and others clockwork install? I prefer using Odin on the Samsung but I don't know if I can install the Bionix that way. Almost everything on the MT3G side with Cyanogen was done through the boot loader. Even on the MT3G I have had problems with Clockworks from time to time.
Can I extract the Bionix file and use Odin? Sorry for the stupid questions I am just trying to figure this out!
Good question. I myself prefer Clockwork to flash ROMs, since I think it's a lot faster and more convenient than messing with Download Mode. As far as I know, Bionix is only flashable via ROM Manager / Clockwork.
It's all about the way they package it. Sombionix must prefer clockwork installs so he does it that way. I always go download mode if I can. Much more reliable in my eyes.
zaduma said:
It's all about the way they package it. Sombionix must prefer clockwork installs so he does it that way. I always go download mode if I can. Much more reliable in my eyes.
Click to expand...
Click to collapse
Same here I always flash from Recovery Mode opposed to Rom Manager for flashing new roms.
I went back to the stock rom and now the phone won't come up. It loads the Vibrant screen then the T-Mobile screen finally the Galaxy S and then goes blank. Is it dead? I have tried flashing it back to the stock rom a few times and it looks like it is working. It does give a message that says it can't wipe the data though.
What should I do?
cyberpyr8 said:
I went back to the stock rom and now the phone won't come up. It loads the Vibrant screen then the T-Mobile screen finally the Galaxy S and then goes blank. Is it dead? I have tried flashing it back to the stock rom a few times and it looks like it is working. It does give a message that says it can't wipe the data though.
What should I do?
Click to expand...
Click to collapse
I'm assuming that you've got a decent charge on the phone (>65%) since you haven't been using it. You can get into download mode just fine right? What version of Odin are you running 1.0 or 1.3? Which stock JFD package did you download? This one has worked for me in the past.
~SB
I used the 1.3 Odin. I reinstalled the drivers from the package I found here forum.xda-developers.com/ showthread.php?t=803492
I can still get into download mode. I think the battery is above 65% still. I have had it hooked most of the afternoon.
I had also tried the download you linked to.
I just tried again with the files you posted and the same results. It keeps saying that it can't format the data / do the wipe.
cyberpyr8 said:
I just tried again with the files you posted and the same results. It keeps saying that it can't format the data / do the wipe.
Click to expand...
Click to collapse
Lemme look around the forums and see what I can find. This phone is pretty resistant to bricking. I'm sure there's a fix for this in one of the few million posts here.
Thanks! I can't wait 7 days for a replacement phone.
Try this thread and see if it works for you. Seems like some people were having the same issues.
~SB
I am at the Android System Recovery and it boots with the error like it is supposed to but I can't seem to get the command prompt step. It says to go to a command prompt and run ADB Reboot. Where do I find the A It looks like this DB command at?might work if I can get the phone to reboot.
Edit: I see it is in the SDK.
It's alive!! Thanks SB for all of your help. I have Froyo running. I will leave it there for now.
This site is a better source of help than any other. Thanks again.
cyberpyr8 said:
It's alive!! Thanks SB for all of your help. I have Froyo running. I will leave it there for now.
This site is a better source of help than any other. Thanks again.
Click to expand...
Click to collapse
Glad to help! The answer is always here....somewhere...
~SB
Sent from my SGH-T959 using XDA App
I ran into this as well all u have to do is a factory reset after Odin the ji6 update
Sent from my SGH-T959 using XDA App
I had this same problem.
cyberpyr8 said:
The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. And force close.
Click to expand...
Click to collapse
I corrected it by going to SETTINGS>APPLICATIONS>MANAGE APPLICATIONS>ALL>SUPERUSER PERMISSIONS>CLEAR DATA
Hope it works for you!
I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!
Try reflashing your recovery image.
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/
Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
ok thanks, i'll try it when I get back home
jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.
I have a rooted EVO 4G that I rooted with Unrevoked after I got the OTA update to FroYo. I removed a bunch of apps with Titanium that in hindsight I probably should have just froze, as I can't manually install any updates without getting an error message. I believe this is due to the update trying to install to a missing app. If I reinstall the original ROM, is there any way to save the paid apps I have on the phone? Suggestions?
you could with titanium, just hit the apps then backup.
EyeNoU said:
I have a rooted EVO 4G that I rooted with Unrevoked after I got the OTA update to FroYo. I removed a bunch of apps with Titanium that in hindsight I probably should have just froze, as I can't manually install any updates without getting an error message. I believe this is due to the update trying to install to a missing app. If I reinstall the original ROM, is there any way to save the paid apps I have on the phone? Suggestions?
Click to expand...
Click to collapse
If you want to download the original rom and still remain rooted, download the Stock ODEXED 3.70 rom from the link below and flash it.
http://forum.xda-developers.com/showthread.php?t=874251
Make sure you go into recovery, wipe EVERYTHING in the wipe menu except your SD card and then flash the rom. Afterwards, be patient during the initial boot. When you've booted into your homescreen and signed in with your Google credentials, start the Market app. Your paid apps should be listed under the MY APPS tab.
After you get your device exactly how you want it, reboot into recovery and make a nandroid backup. Get used to doing that each time you make a change to your device. Doing so will allow you to return your device to exactly how it was before the changes were made in case you don't like the changes. All of your apps will be intact as well as your homescreens.
EyeNoU said:
I have a rooted EVO 4G that I rooted with Unrevoked after I got the OTA update to FroYo. I removed a bunch of apps with Titanium that in hindsight I probably should have just froze, as I can't manually install any updates without getting an error message. I believe this is due to the update trying to install to a missing app. If I reinstall the original ROM, is there any way to save the paid apps I have on the phone? Suggestions?
Click to expand...
Click to collapse
your paid apps, if downloaded from the market, will always show in the market, and you can redownload them from any new rom you flash. they are attached to your google account.
you can use any of multiple backup methods if you want (titanium is my fav too), but your paid apps will always show in the market.
ROM won't flash.
Says to switch to edify scripting? What now?
I think that has something to do with the version of recovery u are using.... Try amon ra's beta test version for recovery or if you are more comfortable with clockwork use version 3.0.0. They both work
HTC EVO 4G
EyeNoU said:
Says to switch to edify scripting? What now?
Click to expand...
Click to collapse
Old packages are not compatible with the newest version of Clockwork Mod Recovery (3.0+) so you need to downgrade to a 2.x release, which is simple to do via Rom Manager. Or you can find a newer package to use instead. I would suggest going with the 2.x version of CWM Recovery.
Or... you can just grab the latest PC36IMG.zip and throw that on the root of your SD card, then reboot to bootloader by holding volume down while powering on. That'll set everything back to the way it came. Make sure you grab the right PC36IMG.zip that you need before flashing...
Update
Well, now I really get a chance to show my ignorance. When I got to the point that I was getting error message, I panicked as I needed the phone at work the next day. I went with the "reboot now" option in recovery mode not knowing what else to do. The phone rebooted with FroYo installed and still rooted. All the downloaded apps were gone.
One of the main worries I had was I didn't know if I could get out of recovery mode after the wipe without having flashed a new ROM. It appears I was able to.
Also, is there any way to load files to the SD card if I get hung up like again?
I guess the advice I most needed is to download the older version of CWM into ROM Manager, and make a backup immediately, and also once I get all apps reloaded and have the phone tweaked to my liking?
The first thing you should do is boot into recovery and make a nand backup. If you are just learning probably use rom manager and get the paid version. Once you have a backup you should not have any worries. You should be able to access your SD card from recovery.
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
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
phisher177 said:
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
Click to expand...
Click to collapse
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
xxaddictedxx said:
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
Click to expand...
Click to collapse
CM10's built in SU didn't seem to think the binaries needed updated, installed chainfire's SU and it wanted to update CWM.
it asked me about disabling recovery flash, to which i said yes. Its not the root im having an issue with though, its getting stuck at a black screen.
either way, update didn't work.
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
phisher177 said:
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
Click to expand...
Click to collapse
did you try one of the roms on xda? if MD5 dosent match then thats your problem