Database Develop

[Q] Easy Root app

Does this app work for milestone?
wwwdroid-lifecom/2010/08/06/android-2-2-on-droid-rooted-with-easy-root/
need to add in the "." as can post links..

It lists milestone so I'm sure it would.
Needs to be >2.1 i believe

i try it .. its really wonderful ..
just seconds then reboot and your phone root ..
i have milestone 2.1

great~!! finally .. the easiest wat to root...!

So this does work then?
Sent from my Milestone using XDA App

yap.. go the homepage and look for the one for milestone..
note: this is only for root only.. nothing more nothing less

got it running. root apps now function.
but root with adb shell doesn't. if I try to remove stock apps like motonav i get permission denied. or if I try to remount with rw option is tells me "remount failed: operation not permitted"
can anyone help?

t.Lancer said:
got it running. worked root apps now function.
but root with adb shell doesn. if I try to remove stock apps like motonav i get permission denied. or if I try to remout with rw option is tells me "remount failed: operation not permitted"
can anyone help?
Click to expand...
Click to collapse
Did you type "su" first?

I love this app it's great. Works great Angevin can now overclock
Sent from my Milestone using XDA App

I did. I googled around and tried to change folder permissions, remount system, data and all that, put none of it works. all shell su commands are denied.
can anyone confirm this, or is it really just me?

t.Lancer said:
I did. I googled around and tried to change folder permissions, remount system, data and all that, put none of it works. all shell su commands are denied.
can anyone confirm this, or is it really just me?
Click to expand...
Click to collapse
Yeah, same for me. The interesting thing is that I was able to delete some system apks step by step, so somehow I had rw at /system but that was only for like 2 mins, then it stopped working. After some reboots, trying to unroot and root again it worked again for some time...too crazy...in the end I messed it up and had to flash the stock sbf, because the market didnt work anymore. Dunno what happened there, but was my first try at rooting anyway
Furthermore shell and /system were denied, remounting to rw didn't work either!

Help me revert Moboot after installing ClassicNerd v4.04.4

I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--

First of all glad your using my theme
If you want to remove the classicnerd option from the menu then do :
Open terminal and type : rm /boot/uImage.ClassicNerd
Or if you have root browser go to /boot/ mount as R/W and delete the uimage.ClassicNerd

I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.

jowyboy said:
I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.
Click to expand...
Click to collapse
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet

jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--
Click to expand...
Click to collapse
I like your post.
Just sayin.
Sent from my SPH-D700 using XDA

TedSamaha said:
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet
Click to expand...
Click to collapse
Meh. It's not a big deal; it would just be nice to order it however I please. My CyanogenMod Nightly installation is now set as default, so meh.
gregory15 said:
I like your post.
Just sayin.
Click to expand...
Click to collapse
Thanks, dude!

Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?

bassrebel said:
Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?
Click to expand...
Click to collapse
You tried updating binaries?
Sent from my cm_tenderloin using Tapatalk 2

if by updating binaries u mean updating SU then I tried but it didn't let me because it says I need root... WTF? I tried checking under options -> developers options and put it to root abd+apps and still nothing is happening... :/

Open the SuperUser app itself, and check your settings there. Something might be changed.
Me, I use the Prompt option, and every once in a while I have to remove an app from the accepted list and let it load itself up and prompt me again. Maybe that'll help you (I hope).

THANK YOU!
jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups...
--[Solved]--
Click to expand...
Click to collapse
Wow. Dude. Where do I start?! Thank you!!! This has plagued my kids tablet for months. Finally, this evening, I thought I would try and do something about it. This boot loader has been causing this tablet to force close after boot for months if it was left to boot up on the 'default' Classic Nerd ROM option (after I flashed another ROM).
Finally fixed.

Fix camera permissions in the market

So the Nexus 7 does not have a primary camera, so a ton of apps in the market that use a camera show up as Not Compatible. You can sideload them and they may or may not work. However, there's a fix.
I'm on rooted stock, but if your custom ROM is also having this issue in the market you can tell your ROM Chef what file to add.
Caveat: This IS working for me as of right now, but it did not immediately, so there might be some delay or something else needed to do to make it work immediately. I'll update this post based on feedback if it's working immediately for folks or there's some other way to speed things up.
Caveat: Just because you can install an app won't make it work. If an app crashes, you've been warned. All apps might not work, but at least some apps that can use camera and don't need the camera function can be installed (Grocery King works fine, barcode scanning crashes), some will work fine (Camera Zoom FX).
And just to be clear, you are modifying /system. If you do this wrong, you could cause yourself problems. You have been warned.
Pre-reqs
Rooted
Root file explorer app to copy a file into /system (I use Ghost Commander, use your favorite app)
--OR THE FOLLOWING--
ADB working
Busybox (does not need to be installed, but needs to be available for cp, or you can use cat if you know how to do that method instead)
Busybox might be needed to remount /system as read-write, or you can use some other method to do this
Pick the method you want to use, adb, or a file explorer that can mount /system and write files there. Pick one method or the other, I've hidden the content on both by default so fewer people think you need to do everything..
android.hardware.camera.autofocus.xml is a file inside of the zip attached to this post, all references to copying that file imply you open the zip file and extract or copy it directly over. NOT the zip file itself. And no, this is not "cwm flashable". If this is working for folks and someone wants to make a CWM Flashable ZIP file to use, I'll be happy to add it to the post and update instructions.
Instructions for using your favorite root explorer kind of app
Download the file attached to this post to your device
Launch your favorite root explorer type app and remount /system as read/write
Copy android.hardware.camera.autofocus.xml to /system/etc/permissions/
Remount /system as read-only
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Instructions for using ADB/Manually copying it
Download the file attached to this post
Connect to your device over adb (I use wifi adb personally)
Do the following commands to launch adb and inside of adb respectively
adb push android.hardware.camera.autofocus.xml /sdcard
adb shell
su
mount -o rw,remount /system
cp android.hardware.camera.autofocus.xml /system/etc/permissions/
mount -o ro,remount /system
Click to expand...
Click to collapse
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Thanks to bonks in #nexus7 for confirming for me that he cannot access a few Camera apps and validating some permissions files for me to verify my changes had worked on my end.
Works for 4.3 as well, but the same caveat... It took three days to show apps as compatible, so not sure what needs to "clear" for the permissions to be updated, but give it a few days and it'll be fine.

Reserving for any followup info, particularly around if the market permission doesn't clear "immediately".

A partial list of apps that work/don't work, but all will install now and previously would not. If anyone tries another app or has more input I'll update this post.
I've also started a list of apps I know of that have altered their permissions in the market so that they should show up natively on the N7 without the fix.
Work Perfectly (maybe mirrored)
Paper Camera - Mirrored
Google Translate - Mirrored, maybe upside down.. Wonky, but does work.
Work With Caveats
Grocery King - Barcode scanning crashes, otherwise completely usable
Don't Work at All
Google Goggles - Blank image, although you can load images you took with other cameras
Retro Camera - Can't find camera
Fixed market permissions
Camera FX Zoom - Use landscape, or things are mirrored and flippped

This worked great for me...thanks a bunch!
Sent from my Nexus 7 using xda premium

Ima give this a go when I get home, thanks

Nexus 7 camera permissions
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David

DavidTheBourne said:
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David
Click to expand...
Click to collapse
http://stackoverflow.com/questions/...ort-for-android-application-manifest-assembly

Just wanted to bump this thread and let everyone know this still works for 4.3. However, I'm not sure what one would need to do to make it work faster.
I installed the XML file on my N7 about three days ago, cleared Market data, rebooted etc, specific apps still showed as not compatible.
Finally today I look, and compatible! Perhaps it's on Google's side, it only updates every so often.. I dunno.
Anyway, so it works, but it might take a few days for it to propagate

Phone shuts down immediately when I use Root Explorer

I got a weird situation. My phone just shuts down when I use Root Explorer, randomly. It has happened while I made a zip of a system file, mounted R/W, deleting a system file. It appears to be completely random. Tried clearing root permissions for it and reaenabled it but it still happens. A reinstall of Root Explorer didn't help either. Any idea what's the problem?
On KA03 ROM, locked bootloader and rooted.

sacredsoul said:
I got a weird situation. My phone just shuts down when I use Root Explorer, randomly. It has happened while I made a zip of a system file, mounted R/W, deleting a system file. It appears to be completely random. Tried clearing root permissions for it and reaenabled it but it still happens. A reinstall of Root Explorer didn't help either. Any idea what's the problem?
On KA03 ROM, locked bootloader and rooted.
Click to expand...
Click to collapse
you probably have not stopped ric, on these devices there is a service called ric which resets the device when system is mounted r/w

lilstevie said:
you probably have not stopped ric, on these devices there is a service called ric which resets the device when system is mounted r/w
Click to expand...
Click to collapse
How do I stop ric?

sacredsoul said:
How do I stop ric?
Click to expand...
Click to collapse
adb stop ric, do you use supersu or superuser?

sacredsoul said:
I got a weird situation. My phone just shuts down when I use Root Explorer, randomly. It has happened while I made a zip of a system file, mounted R/W, deleting a system file. It appears to be completely random. Tried clearing root permissions for it and reaenabled it but it still happens. A reinstall of Root Explorer didn't help either. Any idea what's the problem?
On KA03 ROM, locked bootloader and rooted.
Click to expand...
Click to collapse
That happened to me a few days back, its shows as if you have root but in reality you don't. I tried re-rooting but it would no let me do it again because the superuser.apk already existed. I deleted it and lost root completely but still it would not let me re-root. In the end I just flashed a different rom again as the one one I had flashed was pre-rooted.
So my advice would be to flash and unrooted ROM and then root instead of a pre-rooted ROM (maybe this wasn't your case but it is very similar to what happened to me!!)

lilstevie said:
adb stop ric, do you use supersu or superuser?
Click to expand...
Click to collapse
Followed this post and all is well so far. No more random shut offs! Thanks for pointing me in the right direction. :good:
http://forum.xda-developers.com/showpost.php?p=39514293&postcount=2124

lilstevie said:
adb stop ric, do you use supersu or superuser?
Click to expand...
Click to collapse
sacredsoul said:
Followed this post and all is well so far. No more random shut offs! Thanks for pointing me in the right direction. :good:
http://forum.xda-developers.com/showpost.php?p=39514293&postcount=2124
Click to expand...
Click to collapse
lilstevie pointed you in the right direction, superSU causes these. Superuser or the new, Koush's Superuser app don't do this.

mount -o remount,rw /system mount: Read-only file system

Im on Android M preview 2 with Desparis 3.3 kernel, rooted.
I would like to update build.prop and change user -> userdebug.
Before on Lollipop all I had to do is remount /system in rw and change the file.
Android M doesn't allow me to remount /system in rw.
adb push fails to overwrite the file.
Any solutions please ?

jodvova said:
Im on Android M preview 2 with Desparis 3.3 kernel, rooted.
I would like to update build.prop and change user -> userdebug.
Before on Lollipop all I had to do is remount /system in rw and change the file.
Android M doesn't allow me to remount /system in rw.
adb push fails to overwrite the file.
Any solutions please ?
Click to expand...
Click to collapse
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.

Thanks! At least it's one possible solution !

david279 said:
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Click to expand...
Click to collapse
Actually, can you elaborate how do you do it ?
I've just tried booting into TWRP, then connected the phone to PC, did adb push of changed build.prop into /system, reboot the phone and realized that the phone still has the old build.prop.

jodvova said:
Actually, can you elaborate how do you do it ?
I've just tried booting into TWRP, then connected the phone to PC, did adb push of changed build.prop into /system, reboot the phone and realized that the phone still has the old build.prop.
Click to expand...
Click to collapse
First in twrp make sure you mount system in the mount menu then you should be able to push and pull. You probably pushed the file nowhere even though I think you should've got a error message. I pulled the build.prop straight from twrp edited it then pushed it right back. Did it for the tethering hack. ? ?

david279 said:
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Click to expand...
Click to collapse
sure you can. all i use is root explorer. i change what i need, save it, then reboot for it to take affect. works every time.

simms22 said:
sure you can. all i use is root explorer. i change what i need, save it, then reboot for it to take affect. works every time.
Click to expand...
Click to collapse
I didn't think write to system was working in the M builds. Must be something wrong with his root method.

david279 said:
I didn't think write to system was working in the M builds. Must be something wrong with his root method.
Click to expand...
Click to collapse
maybe. im using despair and sometimes elementalx kernels. does everything else root work for you? all is working here.
edit.. i should ask him, not you

simms22 said:
maybe. im using despair and sometimes elementalx kernels. does everything else root work for you? all is working here.
edit.. i should ask him, not you
Click to expand...
Click to collapse
Root works great in all apps.
The only problem I have is with RO system. Before M I would use ES explorer to modify and save build.prop and Android Terminal to remount system as RW. But it doesn't work like that anymore in M.
Ive never tried root explorer.

jodvova said:
Root works great in all apps.
The only problem I have is with RO system. Before M I would use ES explorer to modify and save build.prop and Android Terminal to remount system as RW. But it doesn't work like that anymore in M.
Ive never tried root explorer.
Click to expand...
Click to collapse
it works exactly like it did before over here. and ive manuslly changed my build.orop several times already.

I'm on Preview 2, rooted, Despair kernel 3.3.
Still confused as to how to enable mounting /system r/w from within Android and not TWRP. Trying FX file explorer as well as Terminal Emulator with no success. I have Busybox installed and under Applet Manager it shows the "Mount" applet as installed and symlinked to /system/bin/toolbox.

KnifeSkills said:
I'm on Preview 2, rooted, Despair kernel 3.3.
Still confused as to how to enable mounting /system r/w from within Android and not TWRP. Trying FX file explorer as well as Terminal Emulator with no success. I have Busybox installed and under Applet Manager it shows the "Mount" applet as installed and symlinked to /system/bin/toolbox.
Click to expand...
Click to collapse
Haven't tried M as it buggy but have used Root Explorer the grand father of file explorers on everything since TBolt.

prdog1 said:
Haven't tried M as it buggy but have used Root Explorer the grand father of file explorers on everything since TBolt.
Click to expand...
Click to collapse
root explorer since 2009 here

simms22 said:
root explorer since 2009 here
Click to expand...
Click to collapse
Root Explorer FTW. Always works and same file system as shows on PC.

Well Root Explorer wasn't the answer, surprisingly enough haha...
Needed insecure boot.img obtained here flashed with help from this thread, with further reading here for better understanding or doing it yourself.
Also I apparently forgot that adbd insecure by chainfire exists until just now, which could have potentially been another solution.