So about 2 months ago I rooted my phone. I followed the method here:
http://forum.xda-developers.com/showthread.php?t=928160
Everything was ok, until my super user permissions program stopped working. The program opened but its a solid black screen and I cannot give any new program SU permission. At first the programs that already had permission could still have SU permission, but, in an attempt to fix the issue I cleared the program cache and those programs lost their SU permission(like TT and terminal).
Their is a new SU permissions program on the market that I paid for from the same company but I assume because the old one is still installed that it is not showing up for that reason and cannot be opened.
I cannot figure out how to get rid of the original Superuser Permissions program. I have tried every program I could find by surfing forums, I have factory reset the phone... but that SU permissiosn program is still there upon a clean factory reset!
I have the ADB installed on my PC, but when I try to run a remount I get an error that I am not allowed to do that. After my factory reset I tried running back through the walkthrough I listed. Visionary says its temp rooted, but in terminal the SU command says "access denied." I think this all has to do with that bad SU program being in stalled and if I can get that off and install the replacement one I paid for, then the SU could grant access to terminal and I could re-root the phone.
My theory is only speculation. Can anyone tell me how to remove this SU program. Its located in directories that are read only and all the commands I have found to remove it so far have required a rooted terminal command, or ADB remount commands that I cannot use. Please help. Thanks
Couple of things to try. First can you boot into recovery? What Rom are you using if any? Since you already did a factory reset I assume you don't have any data you want to save so I would just reflash a Rom from recovery. I don't remember off the top of my head but I think you hold vol - plus power when booting to get to recovery? Or if your current Rom has the permissions still to boot to recovery from the power menu?
Another thing to try is the "rage" method to gain root. I know there are issues with using visionary after you already have root. So give rage a search and try that. Come to think of it you might just try the rage method first. Let me know how its goin I might be able to help more
Sent from my HTC Vision using XDA App
shortlived said:
First can you boot into recovery?
Click to expand...
Click to collapse
A: Not sure I will try.
shortlived said:
What Rom are you using if any?
Click to expand...
Click to collapse
A: Stock that came on the phone
shortlived said:
I don't remember off the top of my head but I think you hold vol - plus power when booting to get to recovery? Or if your current Rom has the permissions still to boot to recovery from the power menu?
Click to expand...
Click to collapse
A: Again, I will try, but nothing has SU permissions anymore.
shortlived said:
Another thing to try is the "rage" method to gain root.
Click to expand...
Click to collapse
A: I will try this too. I will look on our forum, but since you are familiar with the process maybe you can provide me with a link to make things easier? Would you happen to have a link to the rage method for the G2?
Thanks for the reply!!
Nothing has worked. The original superuser permissions is still installed. I get errors when trying to push files to those read only directories even though ADB.
Any ideas on how I can get everything back to factory settings?
What do you mean "a new SU permissions program that I paid for"?
There's only one SU program that I know of. The only paid one that I know of is just a license file for an upcoming, yet to be released, program. You'll need to be specific in order for this to get resolved but it sounds like you may need to reinstall the SU binaries and the SU program.
To uninstall the current one you just need to go to applications>manage, click on the program and then click uninstall. Then use ROM manager to download and install SU for you.
Thanks for the reply but I am way past that. The OS will not let me uninstall the current SU program. The "paid" SU program is a separate program because it asked me to install the file rather than "update" like the free one says when I open it from the market.
I am very specific in my original post.
Somehow the SU program stopped working. New programs that require SU access were not givign the pop up that allowed me to grant SU access. When I open SU its just a black screen with no options. I cleared the cache to try to fix and this removed SU permissions from all the programs that I had already granted SU permissions to(like terminal). I cannot uninstall the program from the built in manager or any of the several file managers I have tried. I also cannot overwrite the current file by "updating" the existing installed version. I paid the 1$ for the paid version because its a different program all together. My thought process was if android sees it as a separate program, it will install it as a separate program and I can use it independantly of the original non-functioning version. That did not work. It says its installed but the icon is no where to be found and I cannot run it, even from a file manager. The old SU icon(of a ninja) still stays in the program list even after I wiped the phone and dida factory reset.
The point is its going to take some advanced procedure to remove the SU program. Its in adirectory that is read only. It takes SU permissions to make that directory read/write and I cant get SU permissions, even temporarily with visionary or Z7. I have tried ADB and it also says permission denied.
So this is NOT resolved yet.
At this point:
-I have reset the phone several times, each time SUpermissions is still installed when the phone comes back up.
-USB debugging is enabled.
-I have googled possible solutions that all have not worked(using ADB failed, updating the SU program failed, clearing the cahce failed, disabling usb debugging then hooking to cpu and reenabling it and using adb to try and use SU command failed...etc
-using 3rd party apps to uninstall failed
-using other SU apps failed
A rough rundown of my problem is:
Phone is rooted. At some point when I opened a NEW app that would require SU access, the pop up generalted by SUpermissions stopped popping up allowing me to give access. Programs I had already granted SU access to would still work(like terminal and titanium backup). Per someones request I tried to clear the cache. When I did this all the programs that DID have SU access lost SU access and I still could not add new programs to the SU list. I have tried ADB commands, file managers, factor resetting the phone. Nothing works. The SUpermissions program is there when I factory reset the phone as if it is one of the preinstalled apps. Apps tell me that I DO have my phone rooted, but that I still need to allow it SU access. I have not been able to uninstall the SU program and if I could get that program updated/re-installed then I believe that I could get the root access back.
Any real suggestions?(not the "is usb debugging enabled" Tier I troubleshooting steps that I am WAY past)
Thank in advance
Kk do you have s-off and the eng-bootloader? Do you have a custom recovery?
If you have s-off and custome recovery you can back up your rom using nandroid, then do a wipe and install a freshly new rom
Also you can boot into clockwork and try to run fix permissons
If you don't have custome recovery (clock work) you will need to have eng-bootloader to do fastboot commands to flash recovery
Also have for adb make sure debuggin is on and boot into bootloader from there try to do adb commands there
If your able to do so and get access
You can go into adb shell and remount to rw then push a new SU.apk in and reboot and su should work as well
This if you don't remember commands
Adb shell
Su
#mount -o remount,rw /dev/block/mtdblock3 /system
#
Then exit out of shell then do adb push
Adb push (where ever su user location on pc) /system/app
I installed rom manager by clockworkmod, which I believe is the program you were refering too.
I tried to "fix permissions" and it failed there.
How would I reload the stock ROM?
If I backup the current ROM, and reload it, then it will reload it as it is with SUpermissions already installed.
Where can I find a copy of the stock rom that came on the G2?
BTW
I do have S-off, but I did not install the engineering hboot.
Let me know the best way to go about getting a stock rom put back on.
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
You never answered if you could get to recovery. If you really have soff then your fine. So when your phone boots it says s off correct? And what happens with you hold vol down while booting? Even if you dont have clockwork recovery you can still install the original rom which you can find in the forums.
Sent from my HTC Vision using XDA App
when chick the superuser ,it always display "force close"
but other app can be supported to get root permission by superuser.
but ,
when i get the superuser update in the google market,nightmare coming.
well ,i have the same issue like yours.
i try to fix ti anywhere ,but i flash other rom to replace.
do you have the solution?
shortlived said:
You never answered if you could get to recovery. If you really have soff then your fine. So when your phone boots it says s off correct? And what happens with you hold vol down while booting? Even if you dont have clockwork recovery you can still install the original rom which you can find in the forums.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I assume that its s-off. The link that I posted the the root method that I used said that it would root with S-off. The only thing I did not do is install the eng hboot. I assume that the root is done with S-off.
I have not had time to sit and try this yet. I will try soon and get back with my results.
ilostchild said:
Do you have clockwork recovery, not rom manager
Click to expand...
Click to collapse
I know at one point I had it, but as I said I factory reset my phone. I want to make sure that I install the correct app, so who manufacturers clockwork?
If you had the cwm recovery b4 and all you did was a factory reset then you should still have it, only time you lose recovery if you update to official rom or you flashed another recovery, clockwork recovery is made my koush, and rom manager is also made by koush
derricks2 said:
So about 2 months ago I rooted my phone. I followed the method here:
http://forum.xda-developers.com/showthread.php?t=928160
Everything was ok, until my super user permissions program stopped working. The program opened but its a solid black screen and I cannot give any new program SU permission. At first the programs that already had permission could still have SU permission, but, in an attempt to fix the issue I cleared the program cache and those programs lost their SU permission(like TT and terminal).
Their is a new SU permissions program on the market that I paid for from the same company but I assume because the old one is still installed that it is not showing up for that reason and cannot be opened.
I cannot figure out how to get rid of the original Superuser Permissions program. I have tried every program I could find by surfing forums, I have factory reset the phone... but that SU permissiosn program is still there upon a clean factory reset!
I have the ADB installed on my PC, but when I try to run a remount I get an error that I am not allowed to do that. After my factory reset I tried running back through the walkthrough I listed. Visionary says its temp rooted, but in terminal the SU command says "access denied." I think this all has to do with that bad SU program being in stalled and if I can get that off and install the replacement one I paid for, then the SU could grant access to terminal and I could re-root the phone.
My theory is only speculation. Can anyone tell me how to remove this SU program. Its located in directories that are read only and all the commands I have found to remove it so far have required a rooted terminal command, or ADB remount commands that I cannot use. Please help. Thanks
Click to expand...
Click to collapse
Try flashing another ROM or a kernel. this could be an error or corruption in the folder located in the root folder of your phone. Flash a new ROM and try it again but set a backup and see if this error continued to another ROM. Hope I helped
ilostchild said:
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
Click to expand...
Click to collapse
When I hold the vol down button the text is in orange.
I will try this process. I am at work and may not have a lot of time here today. If you can point me to where I might find the stock ROM w/ root that would be wonderful.
I assume that rooted version comes with SU and clockwork etc already installed?
ilostchild said:
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
Click to expand...
Click to collapse
Ok... maybe I was mistaken. When I boot into recovery, it says S-off, and the options I have to choose from are orange, but ALL the text is not orange.
When I go through ROM manager to flash a ROM(which is the stock rom i downloaded that I want to flash) it says I need to have CWR installed and to use the option at the top to install it. When I click that it says its asking for permissions to install, which means I need SU permissions, which is my problem in the first place.
I have the rom loaded on my SD. As I said, the 4 options I have in the initial recovery mode are orange(though the rest of the text is now orange) but I do not know which one to choose. Any advice? Do I have clockwork recovery installed? If not, is their any way to flash a ROM?
derricks2 said:
The only thing I did not do is install the eng hboot.
Click to expand...
Click to collapse
Did someone miss this? I thought you had to have the ENG-Hboot?
But, what do I know, I'm a newb.....
Related
NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others
sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App
If you look at Darkyy's rom he has a script that does this.
Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.
Tested and works with Rogers 2.2 Rom. Thanks
skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks
Works great on Rogers 2.2. Thanks
I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+
I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.
I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.
Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?
Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works
HTC Magic
SAPPHIRE PVT 32B
HBOOT-1-33.006
CPLD-10
RADIO-2.22.19.261
I have problems getting in to the recovery mode (pwr button + home) it just gives me de red vodafone screen and hangs.
I am trying to install a custom rom.
- rooted the device with universal androot. it says my device is rooted succesfully.
- i also installed rom manager and installed the default clockwork recovery.
But i cant reboot into flash recovery.
I also tried another thread with a custem flash recovery recovery-RA-sapphire-v1.7.0G.img. I followed it's instructions.
the instructions tells me on a terminal session or CMD prompt to install this custom ROM.
adb shell
su
(Now look at your device. If the superuser app is asking for permissions, then just push "allow" and make sure that the "remember" option is checked.)
cd /system/bin
ls
But i get no permission. I cant get root user when i type su.
so I must not have a rooted device or my permissions are incorrect on the sd-card.
Does anyone have an idea what i should do?
Did you reboot your phone after running Universal Androot?
Sent from my LG-P500 using Tapatalk
What happens if you switch off the phone and then press and hold home button while pressing the on/of button to switch on the phone.
If you are root and have installed the recovery properly, it should be shown within a few seconds after showing the red vodafon screen. From there you should be able to flash any custom rom. Meanwhile I flashed many recoveries and roms on both my tattoo and my magic 32b. Never had any problem execept those when forgetting to wipe.
And to be honest, I'm far away from beeing an expert!
I installed rom manager first and then universal androot.
also when i use adb from the android sdk i sometimes get the problem that i have no permission.
Could it be that the phone is'nt correctly rooted?
I tried all kinds of tools either on pc or mac. nithing really works
what would be the best way to root the HTC Magic correctly and what recovery image should i use. Also wich order.
I'm quite the noob when it comes to installing custom roms
Try "SuperOneClickv1.6.3-ShortFuse.zip" (available at xda).
This was very easy to use and worked like a charm.
I used it twice on my magic 32b, no problem!
I tried that also.
the rooting works. I tried an app to check if i have root access and it says I have root acces.
but when I use adb commands and su to root it will say no permission.
i think this is why installing the recovery in clockwork fails.
any suggestions?
I'll repeat myself. Have you rebooted the phone after running the root programs? Either one?
yes. I rebooted after each try but still I can't get into recovery mode. it just hangs.
also when i try to install a recovery image file i still get the no permissions errors.
the only recovery mode install that worked was the recovery from clockwork in ROM manager.
If ADB is working, goto shell (adb shell).
What do you see in prompt,
is it '$' or '#'?
If it's '$' try "su".
What is the output of "id"?
If you're root you should see something like "uid=0(root) gid=0(root)"
I See a $ and my id is shell instead of root.
if I type su it will give me a no permission error.
however I did download a terminal tool for android
from there I can su and it will make me root.
is there anyway i can use the terminal to install a recovery image so that if i boot my phone with home+power I will get into the recovery?
Try something like this:
http://forum.xda-developers.com/showpost.php?p=4056530&postcount=6
Replace the recovery image in the post by for example recovery-RA-sapphire-v1.7.0G.img.
I did it almost the same way.
I was also having a recovery problem (Tmobile) after trying to flash_image RA-1.7.0G into recovery in rooted 2.2.1 OTA (obviously not the way to go). I downloaded the Clockwork Rom Manager from the Market and it was able to flash both Clockwork or Amon RA recovery with no problem and then reboot it into recovery.
sickbox said:
I was also having a recovery problem (Tmobile) after trying to flash_image RA-1.7.0G into recovery in rooted 2.2.1 OTA (obviously not the way to go). I downloaded the Clockwork Rom Manager from the Market and it was able to flash both Clockwork or Amon RA recovery with no problem and then reboot it into recovery.
Click to expand...
Click to collapse
When you reboot and go into recovery, does it load amon_RA or clockworkmod?
I had problems with that from the 2.2.1 OTA.
I was rooted for a long time, and then had to try the t-mo 2.2.1 so I unrooted and ran that for a while after their ota update. It was sluggish and I didn't much like it so I thought I would try using z4root and superoneclick to root it and put setcpu and overclock it a bit to see if it improved. Z4root didn 't work and superoneclick appeared to work. If you went into terminal it would give you # and seem to be rooted. I could install and run set cpu and it would work. However no matter what recovery I tried to install, it would disappear and return to stock recovery upon reboot with the 2.2.1 OTA.
You could get rom manager to load, or seemingly so , clockworkmod recovery. You could also have rom manager load into clockworkmod from within rom manager. Buit as soon as you reboot, it goes back to the default stock recovery.
I eventually gave up with that and decided to reroot old school and rooted it manuallyl. I went back to the sappimg.nbh file, installing the old cyanogen 1.4 recovery, the 1.33.2005 SPL. I then put clockwork mod 2.5.0.7 recovery on and then the t-mo 2.22.23.02. I was running cm6.1 for a while and now Yoshi's ginger rom.
And so, after this wandering tale, lol, I am wondering if you had more success that I did with the 2.2.1 and getting a recovery to load.
cyberstoic said:
When you reboot and go into recovery, does it load amon_RA or clockworkmod?
I had problems with that from the 2.2.1 OTA.
I was rooted for a long time, and then had to try the t-mo 2.2.1 so I unrooted and ran that for a while after their ota update. It was sluggish and I didn't much like it so I thought I would try using z4root and superoneclick to root it and put setcpu and overclock it a bit to see if it improved. Z4root didn 't work and superoneclick appeared to work. If you went into terminal it would give you # and seem to be rooted. I could install and run set cpu and it would work. However no matter what recovery I tried to install, it would disappear and return to stock recovery upon reboot with the 2.2.1 OTA.
You could get rom manager to load, or seemingly so , clockworkmod recovery. You could also have rom manager load into clockworkmod from within rom manager. Buit as soon as you reboot, it goes back to the default stock recovery.
I eventually gave up with that and decided to reroot old school and rooted it manuallyl. I went back to the sappimg.nbh file, installing the old cyanogen 1.4 recovery, the 1.33.2005 SPL. I then put clockwork mod 2.5.0.7 recovery on and then the t-mo 2.22.23.02. I was running cm6.1 for a while and now Yoshi's ginger rom.
And so, after this wandering tale, lol, I am wondering if you had more success that I did with the 2.2.1 and getting a recovery to load.
Click to expand...
Click to collapse
You could have just got booted into recovery once, flashed the engineering SPL only (there's a ZIP you can flash from recovery to do this), which would only change the SPL, from recovery, then erase/reflash the recovery from fastboot, and finally change the SPL back.
DonJuan692006 said:
You could have just got booted into recovery once, flashed the engineering SPL only (there's a ZIP you can flash from recovery to do this), which would only change the SPL, from recovery, then erase/reflash the recovery from fastboot, and finally change the SPL back.
Click to expand...
Click to collapse
Thanks; that is very useful , and I didn't even think of that at the time. I think I was so frustrated that the recovery would not stay I just had a "I will make it work moment" and I knew what I was doing would work.
But thanks, I will definitely remember that if I have to do that again
Just here to help ;D
Sent from my LG-P500 using Tapatalk
OK, so I just got my Nexus S4G two days ago, and I'm ready to root. My phone out of the box has 2.3.4 on it.
I follow this tutorial: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ the link to which was provided by a good XDA'er. I get the bootloader unlocked and install CWR (recovery-clockwork-3.0.2.4-crespo.img) and that goes fine.
That's when things stop going fine.
First, I try to create a Nandroid backup, and that process seemingly completes fine until i note that the process says it couldn't mount /data. I don't worry about it.
So, I go to Mounts and Storage to prepare to push SuperUser.zip and I tell CWR to "Mount USB Storage" and I wait as directed, but the USB storage never mounts. I try mounting USB Storage and mounting /sdcard, neither of which work, so I can't push SuperUser.zip.
Figuring I did something wrong, I decide to restore from Nandroid, only to have CWR tell me that the MD5 checksum is incorrect and now I have no clean, base Nandroid to restore to.
Then I do some digging, and discover that there's a new CWR for the NS4G at Koush's site and I download the file (recovery-clockwork-3.1.0.0-crespo4g.img) from there, push it to my phone using fastboot's recovery command and start it up.
It doesn't work.
Clicking any of the options (like mounting partitions, or restarting/powering down the phone) causes the screen to go blank and just display the CWR logo in the middle of the screen. The only solution to get out of those loops is to pull battery and restart.
So, now, I'm wondering what to do.
I go back into fastboot, relock the bootloader and I now wait for a reliable root method to root a 2.3.4 NS4G on a Mac.
My questions are:
Where can I get a stock ROM to completely start over from scratch and even remove the recovery I've installed <-- found a base ROM here: http://forum.xda-developers.com/showthread.php?t=1078213
Is there a fully reliable way to root the NS4G on a Mac, and if so how? (I've looked at this thread: http://forum.xda-developers.com/showthread.php?t=878446 and it looks problematic as well).
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
herbthehammer said:
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
Click to expand...
Click to collapse
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
My first nandroid choked. After root and final recovery install, I cleared all the caches it was *****ing about the first time, went in normally to make sure everything was okay, then went back and nandroid and no errors the second time. I probably will just stay with rooted stock but I would not flash other stuff until the dust settles and many of the bugs are worked out of the roms and kernels before jumping in.
TonyArmstrong said:
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
Click to expand...
Click to collapse
If cwm mount won't work then boot into the phone normally and copy over the file like usual is the only other quick and easy way to do it that I could think of at the moment the snafu happened. Yeah the way I did it might not have been the most efficient way but it got me past the hurdle that cwm made quickly. In the end, the result is the same so no big deal.
I don't know if cwm backs up wimax keys so I did it manually. There's a post on how to do it, I don't know if it's in this section. It might be dev?
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
Sorry, this question was posted in the wrong thread and cant find how to delete it myself, either delete or move. sorry again.
Not sure how this happened, but i lost root access to my 3.2 (was a acerstock+root variant) but still have CWM access. What is the easiest way to get root back?
as long as you still have a copy of the same ROM, you could boot to CWM, wipe only cache + dalvik-cache and flash the ROM again. you won't lose anything and should get root back. Also, first thing you should do after that is open Superuser and update the su binary.
When i go to do a dalvik-cache wipe, it gives me an error
E:unknown volume for path [/sd-ext]
and then when i reflash the ROM i still dont have root.
That's fine with older versions of CWM. It will still wipe fine. Moving on...
1) are you sure the ROM you're flashing is supposed to be rooted?
2) just to be sure, which ROM is it exactly?
3) do you even have the Superuser app?
4) if yes, what happens when you open it? Can you update the su binary?
I'm going to guess, the user installed the factory update or rom to 3,2. Based on the fact he/she didn't really know what they had to begin with....
There use to be an update.zip with su and super user.apk. If you still have cwm I would be looking for that. Last place I saw it was a Motor Droid forum.
I loose root every time I try to update busybox. I just restore a backup to regain root.
Sent from my A500 using xda premium