Related
Hey Guys.
I "rooted" my HTC Desire by T-Mobile using Unrevoked3.
Then i flashed a Pre-Rooted Froyo:
http://forum.xda-developers.com/showthread.php?t=773997
Now i wanted to use the "Root Explorer" to remove Apps like "FriendStream" and stuff.
I was able to delete them, but the still keep running.
Then i rebooted and they are still there although deleted with Root Explorer and Super-User permit.
Is it possible that unrevoked is just a "*****-root" i can just use to flash Images but not for mounting /system (R/W) and removing Apps?
What can i do now? Hope u can help me
erichbitch said:
Hey Guys.
I "rooted" my HTC Desire by T-Mobile using Unrevoked3.
Then i flashed a Pre-Rooted Froyo:
http://forum.xda-developers.com/showthread.php?t=773997
Now i wanted to use the "Root Explorer" to remove Apps like "FriendStream" and stuff.
I was able to delete them, but the still keep running.
Then i rebooted and they are still there although deleted with Root Explorer and Super-User permit.
Is it possible that unrevoked is just a "*****-root" i can just use to flash Images but not for mounting /system (R/W) and removing Apps?
What can i do now? Hope u can help me
Click to expand...
Click to collapse
the desire dosent have an unlocked spl yet so even a rooted desire dosent have r/w access to /system/ when booted, there are two ways around it, either delete the apps using adb in recovery mode or flash a rom that utilises the new file overlay system that will give you r/w access to /system/
It more or less sounds like you don't understand the meaning of being root. On a system like android, running something with root or superuser permissions will normally allow the app or command to have full access and rights. This is gained by adding a binary called su and the superuser app, which is for controlling which apps gets root access. So actually unrevoked or any other root methods is not about gaining root, but about being able to put these files on the system partition, which it also does.
Now this is not the case on newer HTC handsets, because they have nand protection, which prevent write access to /system even though an app is run with root access. this is controlled by hboot, and in order to allow rw to /system, we will need an s-off hboot. This is not yet available, but the unrevoked team is working on it.
So the socalled "*****" root just shows me that you don't know, what you are talking about
edit: for now if you want to remove apps, you will need to flash a new rom, where you have removed the apk files yourself, or you will have to learn some adb commands, which you can use to edit system partition while in recovery with rw access.
Using adb in Recovery to backup/remove them is very simple (for removal i.e adb shell rm dir/name.apk) however many default apps break other workings and/or cause confusing unexpected errors if removed. I learnt first hand when removing many pre-installed apps. So be careful and always backup.
-----------------------------------
- Sent via my HTC Desire -
AndroHero said:
there are two ways around it, either delete the apps using adb in recovery mode or flash a rom that utilises the new file overlay system that will give you r/w access to /system/
Click to expand...
Click to collapse
How can I tell which roms utilize the new file overlay system? Im also having the same problem especially with programs starting up after I've disabled them.
shaliru said:
How can I tell which roms utilize the new file overlay system? Im also having the same problem especially with programs starting up after I've disabled them.
Click to expand...
Click to collapse
We have s-off now. Look for that, or use adb.
Sent from my HTC Desire using XDA App
Hello,
I just received my Malata ZPad 1002 version which i bought from Merimobiles.com.
So far it working flawless and extremally fast ( never had such a fast tablet ).
But when i try to root it - it just doesnt happends.
I have tried with Z4's , i have tried with Superoneclick's, ADB's - everything which i have found so far, and still nothing.
When i use Z4root - it restarts, but i dont have root permissions after.
When i use Superoneclick - there is a message popuped what i'm having root permissions but actually i have not.
Please help.
Deleted sorry...
I had no issues with installing Z4 on with mine.
From what I have seen of others who have had problems in other parts of the series of steps to full market, is the confusion over sdcard and sdcard1
When instructions say put it in the root of the sdcard they mean the internal fixed one and not the one you insert.
The 4GB internal card with is called "internal" on the zpad's file manager.
Malata T2 ZPad SMB-1002-WIFI rooting anyone got?
Help help help
please someone help me I am desperate
I need root
I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.
Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?
your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse
mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!
I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.
It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?
its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS
Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.
I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app
I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD
Hey guys,
I just went and purchased Root Explorer because I thought it might be a handy App to have. I boot it up and the SuperUser box requests permission, I allow and remember it.
But, Root Explorer wants none of this and just displays this:
Root access could not be obtained because su failed with the following message:
FIX ME! implement ttyname() bionic/libc/bionic/stubs.c:360
Make sure you granted root permission when requested by SuperUser. If you did then try re-rooting your device.
Root Explorer will continue in non-root mode.
Click to expand...
Click to collapse
I am sure my phone is rooted correctly, all my other "root required" Apps work just fine (and that "su" trick in Terminal returns the #), it's just Root Explorer that doesn't like it. I really don't want to have to re-root the phone... Can anyone make something of that error?
Else { what's involved in re-rooting?
No one?
try to clear SU cache+ root explorer cache from app management and then try to re-grant permissions to root explorer. if this does not work, then just remove root explorer and just redownload it. maybe it is a broken download/install.
Morsolo said:
No one?
Click to expand...
Click to collapse
mariosraptor said:
try to clear SU cache+ root explorer cache from app management and then try to re-grant permissions to root explorer. if this does not work, then just remove root explorer and just redownload it. maybe it is a broken download/install.
Click to expand...
Click to collapse
Thanks for the help, but, nope, didn't work...
I tried clearing the cache of both SU and RE, didn't work... Tried clearing the cache, then uninstalling, then re-installing... Still didn't work.
It can't be my root itself, as I've said, everything else works just fine...
EDIT: Could it have something to do with the "NAND Unlock" and "S-OFF" I keep hearing? I never did any of this when I originally rooted my Desire, though I do have an older model that - as far as I know - doesn't come with those extra security blocks. Plus, all other apps work with root just fine...
Its not the nand protection, that dosent stop you getting root access, just prevents you from writing to certain parts of the nand....
Sent from my HTC Desire using Tapatalk
Ok guys, the latest update for Root Explorer seems to have fixed it. Despite the changelog not having anything relevant to my problem... Either way, it works now
Thanks guys
Hi Everyone,
Anyone got a resolution for sdcard issue with 4.4.4 --- I tried all fixes available -- rooted, updated permissions, etc. installed https://play.google.com/store/apps/details?id=nextapp.sdfix and still having same issue --- I can't even move my pictures from internal to external sdcard.
Link2SD, FolderMount, and Root Explorer is 100% broken and not working.
If it can't be remedy anyone got a good guide to safely downgrade my phone without erasing my files?
any help is greatly appreciated
Thanks,
Shizuwi said:
Hi Everyone,
Anyone got a resolution for sdcard issue with 4.4.4 --- I tried all fixes available -- rooted, updated permissions, etc. installed https://play.google.com/store/apps/details?id=nextapp.sdfix and still having same issue --- I can't even move my pictures from internal to external sdcard.
Link2SD, FolderMount, and Root Explorer is 100% broken and not working.
If it can't be remedy anyone got a good guide to safely downgrade my phone without erasing my files?
any help is greatly appreciated
Thanks,
Click to expand...
Click to collapse
Sounds like you may not be properly rooted. I am on 4.4.4 rooted and i installed the same sdfix app you mentioned and my 3rd party apps have write permissions to sd card.
Sent from my D5503
camaro322hp said:
Sounds like you may not be properly rooted. I am on 4.4.4 rooted and i installed the same sdfix app you mentioned and my 3rd party apps have write permissions to sd card.
Sent from my D5503
Click to expand...
Click to collapse
Thanks for the response --- I followed the thread -- http://forum.xda-developers.com/showthread.php?t=2784900 for rooting my phone --- do you have any advise to re-root? or diff. way to root our phone... I checked root checker and it appears normal but you might be correct.
Try this method
http://forum.xda-developers.com/showthread.php?t=2807092
Best solution for rooting but firstly install new rom 4.4.4 unbranded generic and try this method this is one click method from @munjeni my favorite method. After that you will have root and buaybox and recovery. And after this flash again sdfix and try to move sth to exsd
Shizuwi said:
Thanks for the response --- I followed the thread -- http://forum.xda-developers.com/showthread.php?t=2784900 for rooting my phone --- do you have any advise to re-root? or diff. way to root our phone... I checked root checker and it appears normal but you might be correct.
Click to expand...
Click to collapse
You can try what mosespl mentioned, or you can try easy root tool again (that's what I used and it worked the first time). I saw a lot of people in the easy root tool thread were "half" rooted, or things appear to be rooted but SuperSU failed up update binaries because r/w on system was missing (or something like that, I'm a bit new to all this as well).
camaro322hp said:
You can try what mosespl mentioned, or you can try easy root tool again (that's what I used and it worked the first time). I saw a lot of people in the easy root tool thread were "half" rooted, or things appear to be rooted but SuperSU failed up update binaries because r/w on system was missing (or something like that, I'm a bit new to all this as well).
Click to expand...
Click to collapse
Thanks guys -- i just had the time today and unfortunately without success --- I'm stuck with same problem, guess I don't have a choice but to reflash
Shizuwi said:
Thanks guys -- i just had the time today and unfortunately without success --- I'm stuck with same problem, guess I don't have a choice but to reflash
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54272368&postcount=2094
try flash this patch in recovery to disable RIC if your rom support init.d ... if not, you can also use script manager to give it(99diasbleric) ROOT permission and set it to run at boot.
TheEndHK said:
http://forum.xda-developers.com/showpost.php?p=54272368&postcount=2094
try flash this patch in recovery to disable RIC if your rom support init.d ... if not, you can also use script manager to give it(99diasbleric) ROOT permission and set it to run at boot.
Click to expand...
Click to collapse
Thanks for the help everyone --- i just found out my sdcard is faulty ---- kinda too late I already reflash and use EasyRootTool_v11 and bought new sdcard lol, 100% working now
Thanks again guys.
Shizuwi said:
Thanks for the help everyone --- i just found out my sdcard is faulty ---- kinda too late I already reflash and use EasyRootTool_v11 and bought new sdcard lol, 100% working now
Thanks again guys.
Click to expand...
Click to collapse
Test your old sdcard with a card reader on PC to check if the card is real defective.
Yesterday I put a microsd in z1c and it just can't mount but the card just working fine in windows. At last, I used a USB OTG Cable to connect the card reader with the microsd card and z1c asked me to format it this time and the sd card working fine after that.
TheEndHK said:
Test your old sdcard with a card reader on PC to check if the card is real defective.
Yesterday I put a microsd in z1c and it just can't mount but the card just working fine in windows. At last, I used a USB OTG Cable to connect the card reader with the microsd card and z1c asked me to format it this time and the sd card working fine after that.
Click to expand...
Click to collapse
I actually tested it in Windows and Linux OS -- its 100% broken unfortunately, anyways thanks -- hope I can avail the warranty for this sdcard.