S-off, Superuser denying root like crazy - myTouch 4G Q&A, Help & Troubleshooting

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

Related

Can't root, did before though

Ok so I've done a bit of searching and asking on androidforums but nobody can figure out my an answer to my problem. Alright, first off originally the phone had android 1.5 but when sprint released the 2.1 update I did it. From there, I used regaws tutorial on rooting the official 2.1 release which worked great. Basically I was on a mission at this point, a mission to try out all the 2.1 based custom rims. I had been using the rom manager app for its ability to wipe and flash new roms without even rebooting to recovery. As you are probably aware, to do anything with rom manager, you have to have their clockwork mod recovery flashed, which is simple to do with this app. So one day I wiped and flashed a new rom, aloysius I think, and after it was trying to boot the new rom it gave me some error message and the installation failed. I think at this point I tried to restore my nandroid, which also didn't work, I'm guessing that you have to be using the same recovery you were using when you created the nandroid? No matter what I did from recovery I could not restore my nandroid, as a last ditch effort I did a factory wipe and then rebooted. I didn't think it would reboot at all, honestly I was way scared and thought that I had bricked the phone but after about 5 minutes it finished booting up. Now I don't understand why or how, but when it came to it was quite obvious, I was back at stock 2.1. I immediately look in the app tray for the superuser app and obviously it isn't there, I've been dealing with the phone as is for about a month. A couple of weeks ago I decided to get back to work, sat down at the computer and tried to root it again using the same exact method. After like 5 attempts I get the same problem, I get to the step where command prompt spells out "UNREVOKED" really big but I notice that instead of having a "$" like it shows in the picture I have a "#". At this point the guide instructs you to open the Superuser app on the app tray on the phone, sure enough, I don't have one. I have tried this probably like 7 times all with the same result. I've even tried to install that .6 update to patch whatever remnant of root access I have and go from there as I'm sure the fact I was rooted once and lost it has something to do with my failure. I've tried running RUU's many times as well and always wind up getting an error 171 USB connection error. I havent heard of anyone else having an issue like this. I'm not sure whether I posted this thread in the right place to really get help either so if this needs to be moved to development or whatever don't hesitate. I'd really appreciate anyone trying to figure this out as I am tired of running the slow stock rom but have exhausted virtually every option that I am aware of, PLEASE HELP ME!
I know everyone is probably still reading that book I posted, but once you get to the end lol please gimme some advice, i've tried everything and don't wanna live with the phone as is for the next year....
It's a little hard to read your original post, but I'll do my best to help. From the sound of it you may still have root.
I haven't had to root on stock 2.1 install, so I'm not familiar with the new method. If you get to a bash shell or terminal prompt that is a '#' rather than a '$', you still have root.
You said that you did a factory wipe on the phone. Did you RUU or did you simply wipe through recovery? Are you still able to get to the clockwork recovery?
If you can get back to your modded recovery, you're golden. I would STRONGLY recommend you flash the newest Amon_RA. http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
If you can get that far, you should just be able to wipe and flash a new ROM.
have you tried to update your sync/drivers on your computer lately?
Sent from my Hero CDMA using XDA App
Oh well I finally got it all figured out, had to rum the ruu twice back to back whole the phone was still frozen at the bootloader. From there I finally was able to re root it.

[Q] HELP on getting "Permanent Root"

Anyone know how to get permanent root?What i mean by permanent is when i reboot the phone i still have it.
I usually update to D107 then root phone using one click root method,install magic aosp rom,go to SuperUser(which i placed in /system/app folder) it ask me to update to newest version,i click ok and it works,i get root access in Estrong File Manager and other root apps,i can delete and modify /system folder from Estrong file manager.
After reboot i go to Estrong file manager and it doesnt work any more,SuperUser looses its update and any root app i install after reeboot dont get SuperUser prompt for root access anymore.And if i try to update SuperUser it says that update was successful but at the bottom i don't see new version.I still get root if i adb shell su,but on android i don't get asked for su anymore and i dont think i have root on the phone.Can anyone post step by step instruction for getting "permanent root",Thanx in advance.
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
jokarak said:
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
Click to expand...
Click to collapse
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
lviv73 said:
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
Click to expand...
Click to collapse
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
mykenyc said:
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
Click to expand...
Click to collapse
Thanx man,that fixed my root,you saved me alot of trouble,i guess it was the kernel.Oh and the fluff kernel is probably the smoothest kernel i used so far,now my root is there all the time,thanx again.

R2D2 root??

So, I've tried following the directions for the "nearly" one-step root, and the process completes, but I get no response when I run the Super app, just a blank screen. Is that normal?
Also, from what I've been able to find, it appears there are no released SBF's for the R2D2, so if I brick my phone, I'm SOL. I don't want to end up with a non-warranted paper-weight, so for now I unrooted it....however...did I do something wrong, and if so can someone fill me in?
Thanks!
which one step? I used the Z4root and had zero issues. Rooted within a minute.
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
osufans said:
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
Click to expand...
Click to collapse
Super user app is blank until root apps are used.
For now I wouldn't use a ROM manager you need Koush's Bootstrap to be able to do a backup. It's on the market. To use it just tap the Bootstrap button then wait for the success toast (box) and then tap Reboot Recovery and your phone will boot into Clockwork mod. Backup will take an img of the phone as it is at the point where you backed up. To restore if you mess something on a later install but if you can't get into clockwork for some reason you might be out of luck. Because there is no SBF specifically available for the R2D2 D2 but I've heard that the 2.3.20 might unbrick bricked R2D2's but you won' have the same verizon version you have now it'll be a step back.
OK. I do have bootstrap recovery installed and was able to perform a backup.
Also found a link to some of the bloatware you can "safely" remove. I'm still tweaking it....but that being said, what else can you do (i.e. - overclock, etc.)?
You can overclock, install libs and bins that access hardware features locked out by vzw, change roms and themes....yada, yada.....the 2.3.20 sbf is not a step back. The radio update and kernel tweaks for battery life are not in the 2.4.5 system. They had the rom version because some files are different between the two.
Sent from my DROID2 using XDA App

Is it a brick? Or can I fix it?

My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
xs11e said:
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
Click to expand...
Click to collapse
What google apps are you looking for, 99% of them can be found online and installed. Have you tried the online Android market (it can send downloads directly to your device) https://market.android.com/
You might be able use visionary to temp root the device, that will get you started
Bupahs said:
What google apps are you looking for, 99% of them can be found online and installed. Have you tried the online Android market (it can send downloads directly to your device) https://market.android.com/
You might be able use visionary to temp root the device, that will get you started
Click to expand...
Click to collapse
Online market won't install because I've flashed my HD2 to Android so it keeps saying that everything is already installed.
Visionary won't temp root, nothing will, don't know why? Do you know just how many rooting proceedures there are on the WWW? I've tried each that I've found 3 or more times with no luck.
I'm going to try to see if the online market will allow me to install Root Explorer, that may help me some....
It won't. There seems no way to change phones???
xs11e said:
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
Click to expand...
Click to collapse
When you tried to restore, did you flash the recovery back to version 2.x? You need a 2.x recovery (use 2.5.1.2) to flash CM6, stock, and other Froyo roms. This should let you restore back to stock. Supposedly clockworkmod 3.0.0.6 can flash back and forth between Froyo and Gingerbread roms, but I haven't tried it yet.
Thanks but whatever version of Clockworkmod I have is what I have since the critter won't allow anything to be changed???
I can't get into Clockworkmod so I think changing versions won't help but I can't change so it's sort of moot at this point. The phone will do either one of these things:
1. Boot normally into the partial CM7 build which isn't usable as explained elsewhere.
2. It'll do the hold Vol Dn and hit power boot but then it won't do anything, the only option that works is normal boot and then I'm right back into CM7.
3. I can select "restore" or boot normally and select ROM Manager and hit boot into recovery and it'll reboot to the error screen, red triangle with ! sign on it.
That is the stock Recovery (which doesn't do anything but display the lovely triangle).
If Rom Manager is running in your broken CM7 system, you could re-flash Clockwork Recovery.
You can also flash a Clockwork Recovery image using adb or Fastboot.
xs11e said:
Thanks but whatever version of Clockworkmod I have is what I have since the critter won't allow anything to be changed???
I can't get into Clockworkmod so I think changing versions won't help but I can't change so it's sort of moot at this point. The phone will do either one of these things:
1. Boot normally into the partial CM7 build which isn't usable as explained elsewhere.
2. It'll do the hold Vol Dn and hit power boot but then it won't do anything, the only option that works is normal boot and then I'm right back into CM7.
3. I can select "restore" or boot normally and select ROM Manager and hit boot into recovery and it'll reboot to the error screen, red triangle with ! sign on it.
Click to expand...
Click to collapse
As mentioned the red triangle is the stock recovery. Not sure how you flashed CM7 with the stock recovery but for some reason it sounds like that is all you have on your phone. FYI...If you hold the vol up and power button at the red triangle screen it should boot you into the stock recovery.
A couple of things that caught my eye. You say that your phone now says s=on. did it used to say s=off? When you say you went back to CM7 after trying to flash your backup, what steps did you take to try and go back? Was your backup made thru Rom Manager? Did you try to use Rom Manager to restore your backup?
First thing I would try is a full wipe and factory reset from the stock recovery if you can get there. You need to try and get CM7 to load correctly. If you can do that then you should be able to flash a new recovery. You dont need s=off to flash roms but you do need root.
Do you still have root acces? Ie: can you use SuperUser? Try a few root apps and see if they as for su permission.
jggimi said:
That is the stock Recovery (which doesn't do anything but display the lovely triangle).
If Rom Manager is running in your broken CM7 system, you could re-flash Clockwork Recovery.
You can also flash a Clockwork Recovery image using adb or Fastboot.
Click to expand...
Click to collapse
Thanks, ROM manager is running but re-flashing Clockwork Recovery doesn't help anything, it completes successfully but any attempt to do anything with it gets me to the red triangle.
I wish I could flash a recovery image using ADB or Fastboot, neither will function.
TrueBlue_Drew said:
As mentioned the red triangle is the stock recovery. Not sure how you flashed CM7 with the stock recovery but for some reason it sounds like that is all you have on your phone. FYI...If you hold the vol up and power button at the red triangle screen it should boot you into the stock recovery.
Click to expand...
Click to collapse
Correct, that's all that's there or at least all I can access so far. Vol up + pwr does boot me into stock recovery but that doesn't help.... <sigh>
A couple of things that caught my eye. You say that your phone now says s=on. did it used to say s=off? When you say you went back to CM7 after trying to flash your backup, what steps did you take to try and go back? Was your backup made thru Rom Manager? Did you try to use Rom Manager to restore your backup?
Click to expand...
Click to collapse
Yes, I did have S=off to flash. Steps trying to go back were none, really, after the restore failed the phone wouldn't do anything as detailed in my posts. The backup was made through Rom Manager and that's what I used to try the restore.
First thing I would try is a full wipe and factory reset from the stock recovery if you can get there. You need to try and get CM7 to load correctly. If you can do that then you should be able to flash a new recovery. You dont need s=off to flash roms but you do need root.
Do you still have root acces? Ie: can you use SuperUser? Try a few root apps and see if they as for su permission.
Click to expand...
Click to collapse
Wiped and factory reset several times with no change in the problem. I'd love to get CM7 to load correctly but since I didn't originally load the GAPPS it's pretty useless, no gmail, no contacts or calendar, no Android market (which means all that's on the phone is all I can get, the online market won't work as mentioned in a previous post.) I cannot flash a new recovery, that's what I've been trying to do for several days now.
I do have root access, I can use SuperUser but it doesn't seem to do anything. Attempts to re-root have failed.
i feel ya bro, the reason I am asking these questions is to try and figure out what you have tried and not tried. CM7 isnt useless if you can get it to load. Just because you dont have the gapps installed, that shouldnt do anything but make you not have the market and google apps. Do you have adb set up and will it recognize your device? The biggest question is why would it have turned s=on and why wouldnt rom manager be able to flash a new recovery. Rom manager has a problem making/flashing backups using 3.0.0.X recoveries so that is where this problem started I think. Thats why I am trying to get you a clean working CM7. Does it give you a error when trying to install recovery through rom manager? Have you tried going to applications/manage applications/all/Rom Manager and clearing the data?
If you have su access you might also be able to flash a new recovery via terminal emulator.
Thanks, I appreciate the help and sympathy! I've fixed it in a very unorthodox way, it involved going to T-Mobile's website, changing phone to Blackberry 9700, moving SIM to 9700 and switching data plan to Blackberry.
Dang, that's a little screen....
The reason I'm maybe not giving you all the information you need is that I have very bad arthritis in my hands and I try to type as little as possible, I'm sorry if I'm not being clear but don't hesitate to ask if you need more info.
Not having the gmail means no sync, can't import contacts or calendar, no apps means what I have on the phone is ALL I HAVE, I can't get anything else. That's why I say it's unusable.
ADB does not recognize the device.
Installing recovery through Rom manager results in red triangle.
I did clear Rom manager data as you suggested but it didn't help.
How could I flash recover through terminal emulator, I do have that and can access it and typing SU does give me the # prompt so that's helpful maybe? I'd need step by step directions because I'm very unfamiliar with using terminal emulator, I've only used it to follow directions given in the rooting instructions.
xs11e said:
Thanks, I appreciate the help and sympathy! I've fixed it in a very unorthodox way, it involved going to T-Mobile's website, changing phone to Blackberry 9700, moving SIM to 9700 and switching data plan to Blackberry.
Dang, that's a little screen....
The reason I'm maybe not giving you all the information you need is that I have very bad arthritis in my hands and I try to type as little as possible, I'm sorry if I'm not being clear but don't hesitate to ask if you need more info.
Not having the gmail means no sync, can't import contacts or calendar, no apps means what I have on the phone is ALL I HAVE, I can't get anything else. That's why I say it's unusable.
ADB does not recognize the device.
Installing recovery through Rom manager results in red triangle.
I did clear Rom manager data as you suggested but it didn't help.
How could I flash recover through terminal emulator, I do have that and can access it and typing SU does give me the # prompt so that's helpful maybe? I'd need step by step directions because I'm very unfamiliar with using terminal emulator, I've only used it to follow directions given in the rooting instructions.
Click to expand...
Click to collapse
to flash a recovery image via terminal emulator if you are on cm7 is:
Type "su" and then enter the code below after putting the recovery on your sd card. Make sure you name it recovery.img
Code:
flash_image recovery /sdcard/[COLOR=black]recovery.img[/COLOR]
LMK if that works.
Thanks, I'm not sure what I expected but what happened is exactly nothing:
Put Recovery.img on card, booted up phone, started Terminal Emulator got:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/recovery.img
#
And that's it, nothing happened at all, just went back to the # prompt.
xs11e said:
Thanks, I'm not sure what I expected but what happened is exactly nothing:
Put Recovery.img on card, booted up phone, started Terminal Emulator got:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/recovery.img
#
And that's it, nothing happened at all, just went back to the # prompt.
Click to expand...
Click to collapse
As long as you named it recovery.img and not Recovery.img it should have worked. Try to boot into recovery by powering off your phone and then holding the vol but and power button at the same time. Then chose recovery. Or if you on CM7 just hold power button for a sec and then reboot and recovery.
LMK if that works.
I checked the name several times, booting into recovery just takes me to the red triangle, I've tried that many times before, nothing's changed.
I suspect it's a brick?
xs11e said:
I checked the name several times, booting into recovery just takes me to the red triangle, I've tried that many times before, nothing's changed.
I suspect it's a brick?
Click to expand...
Click to collapse
ok, I still dont believe its a brick. Are you running a rom at all? I mean does it boot into CM7 even though you dont have Gapps? Or is it totaly stuck on bootloop all the time. I am going to send you a PM with my Gtalk. Add me if you want and maybe it will make it a little easier to communicate and help.
TrueBlue_Drew said:
ok, I still dont believe its a brick. Are you running a rom at all? I mean does it boot into CM7 even though you dont have Gapps? Or is it totaly stuck on bootloop all the time.
Click to expand...
Click to collapse
It boots right up in CM7, if I'd added the Gapps at the beginning I'd just be running it happily I think? I'd be able to sync and get needed apps from the market, etc. etc.
I am going to send you a PM with my Gtalk. Add me if you want and maybe it will make it a little easier to communicate and help.
Click to expand...
Click to collapse
Thanks, I'd really prefer to do it this way. Why? Because I'm really sick of messing with it and I hate to spend much time working on it now, I've resigned myself to having a very costly paperweight! Using the thread here allows me to check in once or twice a day when the urge strikes, besides, I really don't IM, never have, never could figure it out. I don't text either, it's blocked at T-Mo's website and on my phones as well. I'm not really a technophobe but I'm 99.2 % one.....
That's fine. I was just trying to maybe make it a little easier in ya.
If you can install a .apk I can send you the market and a few things. We can try to get a few things going that way if you want. If we can get the market going you can get gmail and every thing else from there. will attach the market and tell you how to install if you want
Sent from my HTC Glacier
If he's still s=on, he's not going to be able to flash recovery. You need to get s=off.
Grab the .apk for Visionary. Grab gfree. Grab an apk for a terminal emulator if you don't have one. Put them all on your sdcard, boot into CM7, and follow the instructions for the gfree method here:
http://forum.xda-developers.com/showthread.php?t=858996
If you don't have a file manager to get to them, you could try SMS'ing the download links to the phone and installing through the browser for the .apk's.
TrueBlue_Drew said:
That's fine. I was just trying to maybe make it a little easier in ya.
If you can install a .apk I can send you the market and a few things. We can try to get a few things going that way if you want. If we can get the market going you can get gmail and every thing else from there. will attach the market and tell you how to install if you want
Sent from my HTC Glacier
Click to expand...
Click to collapse
I can't install an APK. I got all the Google apps and put them on the SD card, if I click on one I get "couldn't parse the file" what ever that means?
Actuall, it did install the Market apk but it won't open.....

[HOW TO] Root and Install CWM without USB, Odin, or Computer: 2013 Version

Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod on a stock Epic 4G (SPH-D700) running Gingerbread FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
IMPORTANT NOTE: Be sure to follow the exact procedure below.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- Backup your stock kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
12/08/2013: (Major Addition) Added important note. Added backing up stock kernel.
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Appreciate the effort and updated info.
Mr_You said:
Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod (CWM) on a stock Epic 4G (SPH-D700) running FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- You may backup your kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Click to expand...
Click to collapse
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
TheKillah512 said:
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
Click to expand...
Click to collapse
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Yes, im sorry that i have to make u go through all this trouble because maybe im doing this wrong..
What i was trying to say is that the kernel also has 'su' in /sbin (im not sure if this is the problem but in my galaxy s3 the 'su' is only located in /system/bin and /system/xbin)
I also read this article where it said that the 'su binary' isnt supposed to be in /sbin because in this case (what i think its saying is) that everytime it boots up the /sbin is part of the booting process. Here is the website link: htt p://a ndro idsu.co m (cant post links yet damn)
" People with the su binary located in /sbin have a much tougher time. I’ve found that these are mostly Samsung users (with the notable exception of the Nexus S). I don’t know why it’s done this way, and if anybody does know, please let me know, but for some reason kernel and ROM devs for these devices put su in /sbin. /sbin is part of the boot.img, and therefore any modifications to that directory will be erased on boot."
What i first did is installed Framaroot nd rooted the phone, then got excited because i had been trying to root it for like 2 years now with no success, so since i thought i knew what i was doing, i trailed off nd tried to install CWMR through Rom Manager then went into recovery nd for some weird reason it just put me in the stock android recovery so i knew something went wrong... Then i got scared nd tried to go back to your method nd installed the kernel flasher so i flashed the kernel, rebooted, nd then went into the superuser app. It said the SU binary needed to be updated (got surprised because it didnt say that before i flashed the kernel) i put continue nd it showed me an option to install it through TWRC/CWMR or install normally,so i chose through CWM nd it actually booted me up into CWM but then it said something about a command not working [it was some couple days ago so i cant remember what it said exactly] so i messed around with CWM and tried to installed CyanogenMod which i had downloaded previously, did the signature verification toggle off, but it still said installation aborted because of the command or something... Then i rebooted the phone nd then the problems started, in the superSU app i tried to install normally but it said installation failed... Got the root checker nd said su found in /sbin /system/bin and /system/xbin but i had no root access so i panicked nd tried to root it again with Framaroot, it said success nd i rebboted but it didnt work. I ran the root checker again nd it was the same. I tried to go back to a backup i did when i only had root without the kernel but(which by the way by the end of the backup it said couldnt make md5 sums)but idk why but it took me to the stock android recovery so i couldnt make a restore. I felt trapped cs i couldnt go back to before i had the kernel. With no root access i couldnt also do the restore to the stock kernel(SGS Kernel Flasher app) because i made a backup of it in case something went wrong.. Unfortunately it did so now with no root access i cant really do nothing anymore... I was thinking of using odin to go back to its original state, but then i remembered that it was impossible because odin never recognized my phone while in download mode... Im short in options on what to do please help, im still a noob
Can you try to do a factory reset from the stock recovery and start over?
Mr_You said:
Can you try to do a factory reset from the stock recovery and start over?
Click to expand...
Click to collapse
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
TheKillah512 said:
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
Click to expand...
Click to collapse
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Mr_You said:
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Click to expand...
Click to collapse
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
TheKillah512 said:
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
Click to expand...
Click to collapse
I assume you've already tried uninstalling any SU-type packages?
Mr_You said:
I assume you've already tried uninstalling any SU-type packages?
Click to expand...
Click to collapse
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
TheKillah512 said:
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
Click to expand...
Click to collapse
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Mr_You said:
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Click to expand...
Click to collapse
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
TheKillah512 said:
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
Click to expand...
Click to collapse
Yes that is normal.
I see you say you tried reinstalling Framaroot, but try reinstalling again. But don't reboot. Afterwards go straight into ROM Manager and select "Boot into Recovery" and if rooting was successful I believe it should boot into CleanGBs CWM v3 recovery.
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Sent from my SPH-L710 using XDA Premium 4 mobile app
TheKillah512 said:
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Click to expand...
Click to collapse
For some reason all the forums posts images are broken for me. It seems to be a 404 error.
Ok lets try this:
Make sure you are rooted (install Framaroot again if you need to, don't reboot) and start SGS Kernel Flasher and flash your backup backed up stock kernel and reboot. Then try following the procedure again from the top as described to try to install CWM. Rebooting your stock kernel may or may not fix these issues. If it doesn't then it may require finding a way to fix it via a Terminal app or other method.
I seem to be rooted in some ways but not in others
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
cdupree said:
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
I would try reinstalling Framaroot (and don't reboot) then: Start ROM Manager->Reboot into Recovery
cdupree said:
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
Thats exactly what is happening to me too, friend...
Sent from my SPH-L710 using XDA Premium 4 mobile app
TheKillah512 said:
Thats exactly what is happening to me too, friend...
Click to expand...
Click to collapse
Sorry you're mistaken. You just posted a pic of CWM v3. So your "Reboot into Recovery" from ROM Manager worked.
Did you try what I suggested here to fix your errors?

Categories

Resources