I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
The Magician Type 0 said:
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Has anyone try to format the entire phone, and then fast boot back?
Someone mentioned trying that, but I never heard the results.
Sent from my DROID4 using Tapatalk 2
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
It's almost like Motorola has us all figured out! This and the unrootable Atrix HD... I think we just have to get better. I'm sure there is a root check somewhere in nvram or something
Sent from my Nexus 7 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Whoa. I mean, it probably just writes a value somewhere we can't touch (yet?), but still.
repeated shell auto-granted permissions
fade_to_red said:
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
Click to expand...
Click to collapse
highlandsun said:
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Morlok8k said:
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
Click to expand...
Click to collapse
After doing this, here is what i did in a terminal emulator:
Code:
su
mount -o remount,rw /system
chmod 644 /system/bin/dumpstate
i had to do the "644" instead of "a-x" because i kept getting an error message "Bad mode 10|"
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file??
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file???
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
It's /system/bin/dumpstate not /sys/bin/dumpstate
removing execute permissions does not do anything.
Should I or shouldn't I?
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
supraket said:
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
Click to expand...
Click to collapse
I say.....
You should:
unlock tether, free apps, better phone, harder to replace if something goes wrong (worth it to me)
You shouldn't:
warranty risk, stock performance, easy replacement
je2854 said:
removing execute permissions does not do anything.
Click to expand...
Click to collapse
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
intellitek said:
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
Click to expand...
Click to collapse
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
je2854 said:
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
Click to expand...
Click to collapse
Okay, well, let's say, hypothetically-speaking, somebody was willing to experiment with this.
When exactly does this "rootchecker" run? I guess I'd need to rename/replace it before it runs, but after I've rooted. Or somehow before, although I believe that's currently not possible. I'll try and see if the bin is signed.. not sure how to check if it's actually verifying it on exec, though, without rooting.
EDIT: Nevermind, it looks like it's built into the boot and recovery .img files?
Related
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Faud said:
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
See this post:
http://forum.xda-developers.com/showthread.php?t=664532
Ignore the installation commands, you need to boot in to recovery and push the hosts file to /system/etc/ on the phone.
Adfree works fine. The reason it doesn't work on slide has nothing to do with the app. The hosts file goes in /system/etc/ and since we don't have r/w access to /system, the app can't do what's its supposed to do. It works great I used it the whole time I had a G1, its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Til then you gotta adb push the file thru recovery...
I dunno if you know this, but adfree temporarily d/l's the hosts file to your sdcard, then deletes it when its done. But since it couldn't replace the file on my slide, it left it on the sdcard! All you gotta do is run the app and wait for it to error out, then go get the file and put it on your pc and adb push to /system/etc...
-BMFC
Sent from my ROOTED myTouch3G Slide
bmfc187 said:
its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Click to expand...
Click to collapse
Actually, its rooted just fine (you can run anything you want as uid 0). The SPL security has nothing to do with root.
It is like saying you don't have the proper key to a door just because after you open it there is a guard standing there not letting you in to the next room.
Just being picky...
i think what he meant is that with all the other phones most of us have had we had an SPL to flash once we had done the original tweaks(or before on some phones) so as of right now i agree that the phone is not rooted properly yet as i don't have full control over the phone whenever i want, i want to be able to mv stuff to system partition from android terminal
just being picky...
could anyone please post the actual commands? im new to adb and wold really appreciate the help adfree is the entire reason i even rooted
among others but it was the number one
adb push hosts /system/etc
-BMFC
Sent from my ROOTED myTouch3G Slide
thank you so very much
Other than removing a few of the stock apps, this is one of the things I'm looking forward to rooting for, I loved it on my G1.
With all of the folks having so much trouble rooting this sucker though, I may wait awhile.
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
and if i type su it asks for a password and if i try to run in root it says that production models wont run in root
but i rooted and have the superuser permissions apk installed and has granted me permission to other things
ParkerOviedo said:
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
Click to expand...
Click to collapse
Were you booted in to recovery with /system mounted?
i was able to figure it out
i never tried typing su into the adb shell after i rooted
i got the prompt on my device and accepted it now i have full permissions
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
ParkerOviedo said:
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
Click to expand...
Click to collapse
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
poetik517 said:
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
Click to expand...
Click to collapse
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
jnight666 said:
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
Click to expand...
Click to collapse
You need to have flashed the engineering rom so you have a root shell in recovery.
Does the Hosts file even block ads?
droctii said:
Does the Hosts file even block ads?
Click to expand...
Click to collapse
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
dumfuq said:
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
Click to expand...
Click to collapse
BINGO! Thanks!!!
Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
Hello All,
I have been in and out of every Dev and General forum about installing the CWM on Z8. Unfortunately I have yet to find a solid solution to the below errors when using MTM's ZV8CWMRecovery bat. I would be posting in related thread on the dev site, but I don't have enough posts to post in there. So far I have seen multiple users with this problem:
Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Recovery
5152 KB/s (5345280 bytes in 1.013s)
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
I have only seen a couple answers to this that actually address the error messages. One being to manually copy the local.prop into the data folder. I have tried taking the local.prop file and moving it to /data but when I do I get the error message on my phone saying java.io.filenotfoundexception:/data/local.prop (permission denied).
I feel that this has something to do with Superuser mainly because when I have tried to use other methods like using quick boot or Rom Manager to boot into recovery, I get messages saying that Super User has denied access.
1) Is anyone else having similar Super User problems when they get the CWM installation error above?
2) Can anyone think of a correlation bewtween the super User error and the CWM installation errors?
3) Can anyone give any usefull insight into what these mean?
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
Any support is much appreciated.
im having same problem
williep said:
im having same problem
Click to expand...
Click to collapse
I am going to try the suggestion in this thread right now.
http://forum.xda-developers.com/showthread.php?t=1594369
I will let you know.
OK, I have decided that my main problem right now is that SuperUser is denying access to every program that could help me (Quick boot, Rom Manager, Terminal emulator). Every time I try and run any of those I get a message saying it was blocked by SU. I have set SU to allow all requests, yet it still Denies access?
Anyone with Ideas on how to stop this without starting from scratch?
Plumbert said:
OK, I have decided that my main problem right now is that SuperUser is denying access to every program that could help me (Quick boot, Rom Manager, Terminal emulator). Every time I try and run any of those I get a message saying it was blocked by SU. I have set SU to allow all requests, yet it still Denies access?
Anyone with Ideas on how to stop this without starting from scratch?
Click to expand...
Click to collapse
Sounds like the phone did not root properly. I had that problem before where i had superuser but no root access to anything. My solution was starting over from scratch, im not sure how to do it w/o starting over. If you have everything on the computer already then starting over should only take 15 mins or so. For me thats how long it took after i had all downloads and installs in place
Sent from my VS910 4G using xda premium
jimmyhawk said:
Sounds like the phone did not root properly. I had that problem before where i had superuser but no root access to anything. My solution was starting over from scratch, im not sure how to do it w/o starting over. If you have everything on the computer already then starting over should only take 15 mins or so. For me thats how long it took after i had all downloads and installs in place
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Plumbert said:
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Click to expand...
Click to collapse
Sorry i am unfamiliar with that one
Sent from my VS910 4G using xda premium
Plumbert said:
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Click to expand...
Click to collapse
Give this a shot:
http://forum.xda-developers.com/showthread.php?t=1594369
I was getting the same errors. If you choose option two in the .bat it will reboot you to cwm.
Sent from my VS910 4G using Tapatalk 2
Never had to do anything with the local.prop file
Sent from my VS910 4G using Tapatalk 2
MacK1ll3r said:
Never had to do anything with the local.prop file
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I am having this problem also, but only on my new revo (came with Zv8 my old one that came with Zv4 that is stuck in test mode worked flawlessley with MT's AIO root&Recovery App, The new one worked once i flashed TOT back to zv7 then kept root through to Zv8 but then it wouldnt install CWM or anything for that matter, All of MT's .Bats dont work no matter how many times i flash or hard reset i think something is in new software, be it LG verizon or SuperUser i dont know, but are all you people having trouble having it on Newer Phones?
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
System is protected: you can't modify it while the phone is booted. You'll have to make a zip or whatever to delete it in recovery.
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
fkofilee said:
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
Click to expand...
Click to collapse
It seriously took you all day to root? What went wrong?
Did you try just freezing the app instead?
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
afilopou said:
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So you can no longer go into ES explorer, mount root/system go to system > apps and delete whatever you want ?
Sent from my HTC Incredible S using Tapatalk 2
The recovery flashed but wouldnt boot , managed to get round it when i discovered POB with his superboot Thank god for the desire C
Then i realised that i couldnt flash anything because I manged to install 6.0.2.8 as a boot img, and 6.0.3.0 as a proper recovery.
Then i didnt have any files on the device to flash boohoo so i managed to get ADB sideload working through the AIO One Toolkit... And managed to flash AHRD finally getting a working device,
As you see Im a seasoned vet at these things but the HTC One has been the first device that has stumped me....
----------------------
The apps issue is not unkwown for HTC however they havent done this for a while.... Back with the G2 they did exactly the same thing and yes ive frozen them but there should be away to remove system apps for us through root.... But i cant remember how, Throwing it into ADB Shell and requesting SU along with a Remount works fine but still would like to remove the apps.
Im also looking for someone with a locked phone... (Sim Locked) i have a theory and it worked on the Desire C Anyone wanna help?
fkofilee said:
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
Click to expand...
Click to collapse
Delete the apps with titanium and power off the phone. Don't do a restart.
Already tried that ^_^
You need to flash a custom kernel with a modified ramdisk to disable system protection Without doing that you're like deleting an app on windows with deepfreeze on it
Is that the only solution?
There are so many bloated useless and intrusive (cr)apps on this phone it's unbelievable.
Other solution is boot in recovery and delete it there. Either thru adb while in recovery mode, flashable zip or through file manager(if you're using TWRP). Other than that nope
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
ogdobber said:
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
Click to expand...
Click to collapse
MacHackz said:
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
Click to expand...
Click to collapse
limx said:
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
Click to expand...
Click to collapse
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
issak42 said:
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
Click to expand...
Click to collapse
All Wonderful Ideas folks, however i had a go at this last night, it was a fricking nightmare even mounting ADB through recovery
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app