Hey folks, I just updated to .21 and reran rootkeeper. That restored su to /system/bin. I can adb in and get root just fine. However if I run the superuser app or titanium it always fails getting root.
Code:
[email protected]:/system/bin # ls -l su
ls -l su
-rwsrwsr-x root root 22228 2012-05-06 13:22 su
Anyone have any suggestions as to why this is?
Just to follow up. I tried running vipermod, that failed (both option 1 and 3), and I figured I'd boot into recovery and just wipe, but all I get is the "dead android" picture. From what I read, to restore stock recovery I need cwm. To flash cwm, I need root for recoveryinstaller. I have root through adb, is it possible to flash cwm via adb?
I'm really stuck here. All I want to do is wipe and restore this baby to stock.
Try copying the su from system/bin and paste it to system/xbin
run RecoveryInstaller after that to install CWM
Done that already too. No dice.
shadoslayer said:
Just to follow up. I tried running vipermod, that failed (both option 1 and 3), and I figured I'd boot into recovery and just wipe, but all I get is the "dead android" picture. From what I read, to restore stock recovery I need cwm. To flash cwm, I need root for recoveryinstaller. I have root through adb, is it possible to flash cwm via adb?
I'm really stuck here. All I want to do is wipe and restore this baby to stock.
Click to expand...
Click to collapse
The "dead android" is the stock recovery.
You can try Wolf's method to flash the recovery blob.
http://forum.xda-developers.com/showthread.php?t=1622628
or you can go back to .17, root with ViperMod, use OTA Rootkeeper and OTA back to .21
Really? They must have changed the recovery since the HC roms, because I remember this having some options in recovery back then...
Ok, I'll give flashing the recoveryblob a shot. thanks for the help!
Hey, thanks base. It worked perfectly. I was able to get cwm flashed, flashed su+bb, backed up everything with titanium and we're all good. You've been a great help!
Related
hi all. I already Unlock the Bootloader, I flash the Amon Ra 1.5.3, it works. I made the Nandroid backup, then after reboot it doesn't work. is going to original recovery (see triangle with exclamation mark in the middle). what can I do? I was trying several times but same results. Amon Ra recovery is working only until reboot... What I have done wrong? thanks in advance
You have to flash a ROM after flashing the Recovery for the Recovery to stick, if the same principle from the G1 transfers over to the N1... ie, flash Recovery, boot into it, flash a ROM, you are good to go.
I mean. it will not remain if I will not flash a custom rom?
Are you flashing from sd or fastboot?
from fast boot. i was following the steps from http://androidcommunity.com/forums/...ing-amon-ras-recovery-on-the-nexus-one-30499/.
A nandroid backup does not have the proper permissions/formatting for your system to boot.
You need to nandroid
then fastboot flash boot boot.img, etc
DELETE......
wow way for them to steal my outdated tutorial..... bastards
ovigt71 said:
hi all. I already Unlock the Bootloader, I flash the Amon Ra 1.5.3, it works. I made the Nandroid backup, then after reboot it doesn't work. is going to original recovery (see triangle with exclamation mark in the middle). what can I do? I was trying several times but same results. Amon Ra recovery is working only until reboot... What I have done wrong? thanks in advance
Click to expand...
Click to collapse
Have you already flashed (through OTA or manually) the last update released by google? If yes you need to delete (you must be root for this) the install-recovery.sh you find in /system/etc:
Code:
adb shell
cd system
cd etc
rm install-recovery.sh
By deleting this file I solved this problem of having to reflash the recovery after each rom reboot
ok. so, finally, someone can post one link or a explicit tutorial about how to install this recovery? at least one link would be good enough.. ... thanks
eug89 said:
Have you already flashed (through OTA or manually) the last update released by google? If yes you need to delete (you must be root for this) the install-recovery.sh you find in /system/etc:
Code:
adb shell
cd system
cd etc
rm install-recovery.sh
By deleting this file I solved this problem of having to reflash the recovery after each rom reboot
Click to expand...
Click to collapse
yes. i already install the update.... I was trying to root by MoDaCo way, but after root I was no able to enable the wireless. WIfi was completely out of order. Lucky me 'cose I already done the nandroid backup, otherwise........ so I install again the Amon Ra recovery and I roll back the backup.... please help with one good tutorial regarding root.
http://forum.xda-developers.com/showthread.php?t=612858
easist recovery can be tricky
do u have SDK?
Yes, I have.... usualy I go in recoveryy mode from "ADB reboot booloader recovery"..
Think i should write a recovery flashing tutorial?
So as many of you are now finding out is that clockwork is borked and so is root with the new update. The root method on cyanogenmod wont work. The rootboot.img breaks wifi and you still cannot get into clockwork recovery ... well at least I can't. Anyone else seeing this and possibly have a solution?
zeiroe said:
So as many of you are now finding out is that clockwork is borked and so is root with the new update. The root method on cyanogenmod wont work. The rootboot.img breaks wifi and you still cannot get into clockwork recovery ... well at least I can't. Anyone else seeing this and possibly have a solution?
Click to expand...
Click to collapse
ya the OTA breaks root and CWM,,,thats why in roms the ability to OTA is removed
Reflash koush's clockwork recovery via fastboot.
After the successful flash, you can get into CWM recovery by selecting Recovery while still in fastboot.
Once in CWM, go to mount options menu and mount /system.
Then use adb shell to navigate to /system/bin.
Once in /system/bin type chmod 6775 su
Root functionality should now be restored when you're in normal boot mode.
Getting permanent CWM recovery back is proving more problematic for me. Once you reboot the phone after that first install, selecting Recovery gives you the Android and "!" screen. Battery pull required.
You can however, get back into CWM recovery by either fastboot flashing the image again as above, or from the ROM Manager app where you flash the recovery and then select boot into recovery.
Pain in the butt, but not totally lost.
Just a minor issue that comes from running custom recoveries and roms. Koush already is working on a flashable update that will work with CWR. Just gotta be patient. Chances are that if you have been keeping up with the tweaks and new apk's in the dev forum, this update won't really mean that much anyway. I am a sucker for wanting the latest version number in my "about phone" though
distortedloop said:
Reflash koush's clockwork recovery via fastboot.
After the successful flash, you can get into CWM recovery by selecting Recovery while still in fastboot.
Once in CWM, go to mount options menu and mount /system.
Then use adb shell to navigate to /system/bin.
Once in /system/bin type chmod 6775 su
Root functionality should now be restored when you're in normal boot mode.
Getting permanent CWM recovery back is proving more problematic for me. Once you reboot the phone after that first install, selecting Recovery gives you the Android and "!" screen. Battery pull required.
You can however, get back into CWM recovery by either fastboot flashing the image again as above, or from the ROM Manager app where you flash the recovery and then select boot into recovery.
Pain in the butt, but not totally lost.
Click to expand...
Click to collapse
Bah im a douche up arrow and didnt read the line and I was flashing the stock boot.img over and over lol ... Thanks
zeiroe said:
Bah im a douche up arrow and didnt read the line and I was flashing the stock boot.img over and over lol ... Thanks
Click to expand...
Click to collapse
LOL, don't you hate when that happens.
Glad it worked out for ya in the end!
So I had a stock Evo -> rooted via unrevoked, upgraded via OTA to 3.70, lost root. Re-rooted using unrevoked 3.31, CWM 2.6 installed perfectly fine. So far so good.
Before I foolishly upgraded via OTA, I had psfmod which is based on CWM 2.5.1.8. My question is
1. Can I flash psfmod (even do it's CWM 2.5, not 2.6)
2. I know it will cause problems, if I can flash psfmod, how?
I tried terminal emulator
$su
~# flash_image recovery /sdcard/recovery.img
no success, I've tried to reflash using unrevoked, no success. What to do now?
Yes I have backed up everything;
Thanks in advance!
-ninjila
I wouldn't go that route, but if you want to flash that image as recovery:
Code:
su
remount rw
find -iname "flash_image"
[will display the directory flash image is stored]
Code:
chmod 755 directory path to flash_image
[i found when I tried to flash, mine didn't have proper permissions, so use chmod]
Code:
flash_image recovery sdcard/recovery.img
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
I usually install superuser.zip with TWRP recovery. This time I tried both latest twrp with f2fs support on SD card and TWRP on nand, but looks like all zip files I install with recovery trying to apply to nand and nothing happens. I installed Superuser apk, but that way it tells i need install superuser via recovery and all apps tells me I have no root, but I have root access with adb shell. Fresh install CM12.1 hd2 rom with two ext4 partitions. Note: I tried mounting two sd-ext partitions before installing superuser in recovery. Also I tried to replace su binary under /system/xbin/su in rom archive itself. After installation su file is correct and permissions is right, but Superuser still ask me to install self through recovery, and apps can't get root. I even tried install SuperSu, but still without success.
Looks like its really easier then I thought. I just need enable developer options and activate root under Developer section.
Video: youtube.com/watch?v=Knm1kKVkJd8
Thanks: macs18max