Hey there browsing with all those ads is a real pain, therefore i wanted to edit the hosts-file since adaway didn't worked.
Therefore i wanted to use the content of this page and add it to my hosts-file:
http://someonewhocares.org/hosts/
problem is, i can't mount /system with total commander although root is working (flashtool installed busybox fine as the root popup comes up and asking for root).
the bootloader is unlocked and via adb shell in root mount i also get:
Code:
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
is there another way? can i somehow flash the hosts-file trough recovery?
You must not have full root. Install RIC Killer or XZDR to defeat this protection.
i thought only "temp root" existed besides the full root? well NUTS Dual Recovey is also installed... gonna check out the RIC Killer...
:Edit: Ok, neither the "Windows" RIC-Reboot Remount Fix worked, as the ZIP-Version trough Dual Recovery....
what would be the best way to reinstall root (altough it is an system app?)
The command you specified works fine for me. Further, root explorer via ES Explorer.
What root APK do you have installed? SuperSU, for example, has a "complete unroot" command you can use unroot.... but since there's no one-click root for 5.1.1, re-rooting isn't possible without reflashing. I suppose a dirty flash back over top 51.1 isn't as risky as between versions, so you could try that in order to re-root.
How did you root initially? My process for 5.1.1 has been to flash the FTF, SuperSU, and XZDR all in one go, no reboots between. People have had issues getting full root to work especially if the SuperSU and XZDR steps are separated by a reboot.
sorry for the long pause i was at vacation and there i had no chance to try something (since a backup would be needed first in case of fire )
I've been installing a prerooted tft the day 5.1.1 came out. RIC Killer didn't worked and fully unrooting well... doesn't work either
Flashing a zipped SuperSU or something like that won't work? I mean - i can unroot it go to XZDR and flash it again - this should work right?
Related
I have downgraded from JPK to JM8. When recovery runs I get an errormessage about "can not access /system/csc", not exact words but I think I've understood it right. I have checked it with ADB and I have permissions set to "drwxr-xr-x root root csc" and in /system/csc I have "-rw-r--r-- root root" on all files. It seems a little strange that my permissions are set to that in the folder. Are those permissions correct?
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Ok. Will do that. I'm looking for a reason to why I can't flash docs rommod onto my phone. I can't get any further than to the S on black background hearing bootsound but the phone doesn't boot up to a ui. Thought the message could be a clue to that problem
did you do a factory reset in recovery?
When do I have to do that factory reset? I have tried to do it after the slimmod flash. Should I do it before flashing the mod? Now I have oclf installed. Do I have to remove it before trying again?
I have done a clean install of JM8. Installed OCLF, rooted, installed RomManager and clockworkmod recovery. Pushed extreme superslim to internal sdcard. Rebooted into recovery. Did a factory reset and wipe of cache. Installed zip from sdcard. ONLY DIFFERENCE IS THAT MY CLOCK SHOWES TWO HOURS TO EARLY. What am I doing wrong?
Install fresh jm8 push docs update.zip to sdcard and apply it. Then install those rest...
Sent from my GT-I9000 using XDA App
At last! After to more resets and flashes I have Extreme Slim on my device and I really likes it. Big applause to doc. Happy HTC:ing.
mickeko said:
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Click to expand...
Click to collapse
I noticed with this you had to change the permissions for these foders using a program such as root explorer. Tick all boxes. Well, that's the only way I got rid of the error.
Also case sensative..
/system is usually mounted a read-only, you have to remount it like this from terminal emulator (rooted of course)
$ su
$ mount -o remount,rw /system
then run
$ mount
you should see /system mounted as 'rw'
Yes, I'm a noob
so I got my Moto XOOM and rooted it with adb and flashed a new kernel and installed ROM Manager and got a new recovery in it and all that and it was smooth as butter. I'm not a fan of ROMs but the kernel does make a huge difference already. Now, I did that as soon as I took the XOOM outta the box so I had no data to lose when rooting...
I've had my N1 for about a year now, been using 1-click root exploits because I didn't feel like starting over and losing all data even though I can have backups I know... but just putting the settings back, losing high scores in games, etc... is annoying enough.
But I'm starting to think now's the time.
So:
1) Best backup solution to not lose anything? My last titanium backup is from about two month ago when I lost root after the Gingerbread OTA
2) does it still stay rooted now with gingerbread? basically adb --> fastboot oem unlock and that's it?
3) I've read the wiki and it's great but not "omg I'm such a noob" proof... so the steps:
- I backup my stuff
- Reboot in recovery
- from my PC, run the command in adb --> fastboot oem unlock
- yes
- my nexus one is now unlocked, rooted but is back to factory...
after that, get the 2.3.3 update zip file from XDA and flash that. flash a new kernel via kernel manager (which one you guys recommend for speed and stability without all the fuss?)
that's it, finito?
thanks if you respond!
A - there are exploits available for Gingerbread, so you don't need to unlock the bootloader (though don't let that stop you)...
http://forum.xda-developers.com/showpost.php?p=13090966&postcount=67
B - unlocking the bootloader doesn't give you root. You also have to install a custom recovery and flash the su zip to gain root...
C - flashing an update zip will probably cause you to lose root (unless it's a pre-rooted zip, in which case you would need a custom recovery to flash it)...
hmm so I skipped a step, after unlocking bootloader I need to do what exactly? (commands/links if possible!)
it seemed simpler on the xoom.... unless it's the same thing?
adb reboot bootloader
fastboot oem unlock (wait for reboot)
adb reboot bootloader
fastboot flash boot rootboot.img
fastboot reboot (wait for reboot)
adb remount
adb shell push su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
that's it? are the Nexus files different? (got a link?)
as for Gingerbreak, I kinda got sick of always waiting a long time for 1-click roots after each update. I will try to get it working (so far no go, gonna stick a blank sd in my phone and try that) just so I can do a full Titanium backup and maybe a recovery if possible
Gingerbreak worked - stuck a blank micro-sd, rooted, put my 16gb micro-sd back in - all is well
running full Titanium now...
This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.
boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back
did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.
then you should flash firmware and root again
Superuser
maybe update superuser binary?
solved
chmod 777 path name n got busybox 1.12
You lost root access because there is no busybox. Reflash the ROM. Easy way out.
nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
After folowing all the steps on this guide (http://forum.xda-developers.com/showthread.php?p=41997803#post41997803) to finnaly have .253 rooted, it seems I can't write to system. Every time I try to uninstall system app using titanium backup, the phone reboots. The selected app is uninstalled, but I have to do it one by one, cause it reboots always after unistalling. Same when trying to integrate dalvik cache files to the rom with Titanium Backup or to integrate an updated app to the room. When I open the File Manager, the phone instantly reboots too... Any idea about how can I fix it?
Thanks!
Rebooting Fixed!
If someone else is facing the same problem, I fixed rebooting issue while writing to system following this guide, thanks to the user [NUT]:
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
You need to reroot, as that is the issue.
From me to you.
hum...
It means... downgrade to.434, root again,... reflash .253?
.LEONARDO. said:
It means... downgrade to.434, root again,... reflash .253?
Click to expand...
Click to collapse
Whichever way you want, but this is a root related problem.
Xperia Z rebooting while writing to system FIXED
Rebooting Fixed!
If someone else is facing the same problem, I fixed rebooting issue while writing to system following this guide, thanks to the user [NUT]:
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.