How do I get Root (read/write) Access in Recovery? I'm running SGS II rooted using Chainfire 's insecure kernel on XWKE7.
I can only access Superuser via Shell...
If this has been discussed before, please direct me to where.
The point to this would be to be able to push/pull stuff to system on a device that won't boot cause I messed with the framework or something else.
+1 How to make read/write full access in recovery mode ?
Thanks
When using CF-Root, in recovery connect via ADB and type:
Code:
rootsh
at the console.
Yes but how to have root without rootsh.
For push directly in /system ?
Ah, I see.
For that you need a kernel that's running adbd as root.
CF-Root kernel runns adbd with normal user priv's and SUs it to root on the shell, so no go there.
Grab one of the kernels from the "insecure kernels for rooting" thread or my one (*points-to-sig*).
The insecure kernels always run adbd as root, my kernel runns adbd as root when in recovery (not on normally booted system).
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
http://forum.xda-developers.com/showpost.php?p=18160002&postcount=26
ptulluri said:
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
Click to expand...
Click to collapse
Also must people are having issues flashing in cwm after using ROM manager. If you try installing from cwm and get verification error you needed to flash again then kernel and don't use ROM manager
Flashed CWM and nothing is happening
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
noobdeeznutz said:
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Click to expand...
Click to collapse
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
Also if not rooted I do not think CWM will work...
Use this by Entropy512 it is flawless.
http://forum.xda-developers.com/showthread.php?t=1286432
SNadler said:
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
That was it... THANKS!!!
Click to expand...
Click to collapse
SNadler said:
Also if not rooted I do not think CWM will work...
Click to expand...
Click to collapse
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Pirateghost said:
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Entropy512 said:
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Click to expand...
Click to collapse
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Entropy512 said:
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
Click to expand...
Click to collapse
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
DoctorQMM said:
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
Click to expand...
Click to collapse
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Entropy512 said:
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Click to expand...
Click to collapse
I understand (I think) that chmod 644 is to set the permission but what is chmod 6755?
SNadler said:
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
Click to expand...
Click to collapse
I have downloaded CWM Manager and I have tried to install it but it has failed. Is there a different type of process to doing this other than opening it through root explorer?
what are you trying to do? just use the 3 button combo or extended power option to boot into recovery and flash away?
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
ducksauce88 said:
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
Click to expand...
Click to collapse
Use the home soft key to select stuff in CWR, not the power button.
Sent from my SGH-I777 using XDA App
i didnt read all of the posts until after i posted. thanks for not slashing me. so it looks like i use the home button to select then the back button still goes back. got it.
On a side not, I do not remember reading about that within the posts for rooting and flashing clockworkz. I tend to skip over things when reading, but I think someone should put that in big fat red letters "USE HOME BUTTON TO SELECT".
On 2.6.29-modFXP-DooMKernel-v05a and Wolf_Xperia_7.0.0d (unlocked BL) I have the option to choose between Xrecovery & cwm recovery during startup.
When do I need Xrecovery and when do I need cwm recovery? What is the difference in use? (They look very similar to me...)
for CM based Roms cwm can be used i suppose .. or when u r tryin some new ROMs in the OP its specified which to use xrec or CWM rec !!
Sorry i know it is kind of off topic. but it is the only topic i find that is relate to Xrecovery the most.
I used the flashtool to install the xrecovery 0.3 - release ( downloaded from DoomLord page, the file call FlashTool_0.2.9.1-GBready_root_xRec)
It say already using "V0.3 GBready.zip" but when i boot in xrecovery. the top still show "xrecovery v0.3 release"
and so i try to do the xrecovery v0.3 GB updated.
but. i failed in the first line when i type "rm -r /sdcard"
it say
" rm: can't remove ' /sdcard' : No such file or directory"
can i ask what is the possible mistake i did made in the whole process.
Thanks alot everyone.
---------- Post added at 07:09 AM ---------- Previous post was at 07:04 AM ----------
sorry...i didnt put any background of the phone.
Xperia x10a
2.3.3 v
base band 2.1.71
rooted by flashtool, installed xrecovery by flash tool
installed busybox from app market.
thanks again
acerulz said:
for CM based Roms cwm can be used i suppose .. or when u r tryin some new ROMs in the OP its specified which to use xrec or CWM rec !!
Click to expand...
Click to collapse
The reason why I ask is; when I do a backup (in Xrec), and then flash a different kernel, is it possible to do a restore if only CWM rec is present...?
Bugsy
MIUI or CM are based on CWM recovery.
For wolfbreak Rom use xrecovery as it is based on stock rom.
No you cant restore a backup of xrecovery from CWM or vice-versa.
Use bootmanager by doomlord to shift between different recoveries.
I have the same problem
¨ # rm -r /sdcard
rm: can't remove ' /sdcard' : No such file or directory (adb shell)
what did you do???
Diego.xD said:
I have the same problem
¨ # rm -r /sdcard
rm: can't remove ' /sdcard' : No such file or directory (adb shell)
what did you do???
Click to expand...
Click to collapse
flash ftf file found here http://forum.xda-developers.com/showthread.php?t=1226826
this should solve all your recovery problems. if u have unlocked bootloader, flash the ftf files found in dooms thread for unlocked bootloader and dont forget to flash wifi modules via recovery after that
New to android.
What is the difference between Insecure and secure Kernel?
edit: found the answer. Please close thread.
What you mean is insecure kernel and stock kernel.
An insecure kernel has a security flag set to 0 to gain superuser rights in adb.
I am trying to get root on an Alcatel A3 using Magisk since no other option is available. I got ADB working, and it's unlocked from the developer options.
However, if I do
Code:
adb shell
and then
Code:
ls /dev
it returns the following
Code:
opendir failed, Permission denied
How can I make a backup of boot.img?
I have looked on Google, but everything is either ("BACKUP WITHOUT ROOT!" but you need a custom recovery or "BACKUP WITHOUT A CUSTOM RECOVERY!" but you need root)
Thanks for any help
Edit: my version is 5046Y but I have found a stock ROM for 5046J which appears to be some kind of Brazilian/South American version.
Will this work?
Did you ever get helped same problem but with Alcatel A7 5090i
Did you get rooted?