Hello there!
At first,I would like to say thank you to all users for their supports and their help, thank to your informationI have finally upgraded my Acer Iconia A100 to ICS and I have rooted the device without any problem, and it works like a charm!
But before I made the upgraded to ICS i was using Honey Comb 3.2 which was rooted also and I did manage to install Adhocenabler which worked perfectly with my nokia n97.
So I have upgraded the device to ICS, rooted it, but now I can't get adhocenabler applicatin to work! It always come with "unable to mount system" "are you rooted ?"
All applications have rooted access but it seems that adhocenabler can't have it!
I have tried to Re-root the device, tried to hard reset it, but it still doesn't work...
ANyone is facing the same problem? do you have a solution ?
thank you very much
Hi there, I had a similar problem whilst trying to install chainfire3D.
Try running this (seperate commands) from within terminal emulator (a quick download from the Play Store if you haven't got it installed)
su
mount -o remount, rw /system/
Let me know if this works, did you follow the ZeroNull method?
thank you for your answer!
I've tried your method, but i doesn't work... I'm still stuck with the same error
I have took a screenshot of the application
freefilehosting.net/20120401-145832
freefilehosting.net/20120401-1458361
that sounds weird because it's the only one application that can't get root access
For those who cant get access to adhoc network on ICS,
this method is working perfectly !
download a copy of the wpa_supplicant, here and put it in sdcard/download directory
forum.xda-developers.com/showthread.php?t=1033314
and then open a command shell on windows and type
ADB SHELL
su
mount -o rw,remount /system
cd /system
chmod 775 bin
cd bin
cat wpa_supplicant > wpa_supplicant.old
ls
cat /sdcard/download/wpa_supplicant > /system/bin/wpa_supplicant
ls –a –l
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /system/etc/wifi/wpa_supplicant.conf
mount -o ro,remount /system
press ctrl-c
unplug usb
reboot tablet
restart start phone
Now everything is OK ;=)
Hi everybody,
Sorry for my bad english, i'm italian,
I've a problem with my a100 with stock ics. yesterday i've rooted it and i've installed lcd density modder. now, i've do a mistake and saved the dpi instead of temp apply. after the reboot the home won't start cause it freeze. i can only have access to settings i can't access the lcd density app. i've tried to reset to factory but it's still the same. Can anyone help me ?
thanks
Use adb to pull build.prop from /system use some text editor to open it and find this line ro.sf.lcd_density= and change it to ro.sf.lcd_density=160 then reboot.
The exact commands are :
Code:
adb pull /system/build.prop build.prop
adb push build.prop /system/build.prop
adb shell reboot
thank you so much, resolved
can you explain how to pull it up into the text editor i'm afraid i have the same problem and found this thread i enter the pull command and recieve this in cmd prompt:
C:\Users\Owner>adb pull /system/build.prop build.prop
224 KB/s (1841 bytes in 0.008s)
and now i'm lost.....
ilovemywife269 said:
can you explain how to pull it up into the text editor i'm afraid i have the same problem and found this thread i enter the pull command and recieve this in cmd prompt:
C:\Users\Owner>adb pull /system/build.prop build.prop
224 KB/s (1841 bytes in 0.008s)
and now i'm lost.....
Click to expand...
Click to collapse
Open your editor and then open build.prop in it.
Or name it build.txt then edit it then save as build.prop.
Tapatalked from my Galaxy S II.
pio_masaki said:
Open your editor and then open build.prop in it.
Or name it build.txt then edit it then save as build.prop.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i'm a noob here i need more details on how exactly i should go about getting it opened
ilovemywife269 said:
i'm a noob here i need more details on how exactly i should go about getting it opened
Click to expand...
Click to collapse
Open whatever editor you want, then click on help for how to open documents in that program.
Otherwise, file>open>whereveryousavedit/build.prop
Then file>save.
Edit: for windows I suggest notepad++
Tapatalked from my Galaxy S II.
pio_masaki said:
Open whatever editor you want, then click on help for how to open documents in that program.
Otherwise, file>open>whereveryousavedit/build.prop
Then file>save.
Edit: for windows I suggest notepad++
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ok i didn't save it anywhere how do i save it?
ilovemywife269 said:
ok i didn't save it anywhere how do i save it?
Click to expand...
Click to collapse
C:\Users\owner\build.prop from what you posted before.
Tapatalked from my Galaxy S II.
pio_masaki said:
C:\Users\owner\build.prop from what you posted before.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ok now i get:
C:Users\Owner>adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop' : Read-only file system
what am i doing wrong shouldn't it be in a Read-Write system?
ilovemywife269 said:
what am i doing wrong shouldn't it be in a Read-Write system?
Click to expand...
Click to collapse
adb remount
adb push build.prop /system/build.prop
Edit: if that fails try this:
adb shell mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
mount: permission denied (are you root?)
i was rooted before i factory reset i went through the adb root method which is basicaly how i achieved root to begin with except i used a cmd prompt terminal app and did it all on my tablet and now i'm not sure i never had a "full" root idk how to explain that but it told me i was rooted and could run root apps and such but it still limited me on a few things if this helps i have
"bootloader 0.03.06-ics (unlocked)"
it came stock with gb or honeycomb i had to find a .zip file to get ics
now i've tried to adb root again and failed i'm not sure why...
ilovemywife269 said:
mount: permission denied (are you root?)
i was rooted before i factory reset i went through the adb root method which is basicaly how i achieved root to begin with except i used a cmd prompt terminal app and did it all on my tablet and now i'm not sure i never had a "full" root idk how to explain that but it told me i was rooted and could run root apps and such but it still limited me on a few things if this helps i have
"bootloader 0.03.06-ics (unlocked)"
it came stock with gb or honeycomb i had to find a .zip file to get ics
now i've tried to adb root again and failed i'm not sure why...
Click to expand...
Click to collapse
OK time for info then. What ROM are you on? What recovery? Why did you use a method other then one intended for the a100? Being rooted but limited is probably due to missing or bad busy box installation.
Tapatalked from my A100 - Kuroikaze B3
i used an update zip for what i believed to be a stock ics rom and i rooted with a method that was intended for the a100:
Download the su binary from here.
Hook your device to the computer via USB cable.
Copy the su binary file to /mnt/sdcard/ on your tablet.
Open a command prompt on your Windows computer.
Change directory to where ADB is located. (This is usually the /tools or /platform-tools directory inside the Android SDK installation directory.)
Type in the following commands at the terminal (press Enter after each command):
adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch ‘`cat /mnt/sdcard/su >/system/xbin/su`’
adb shell /system/bin/cmdclient ec_micswitch ‘`chmod 6755 /system/xbin/su`’
Install the Superuser app from the Android Market.
i used this method but i used terminal emulator on my tablet i didn't use adb
here is the update zip i used for ics- this is the error i get trying to attach the zip file:
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.
Use the script as intended. From the PC. If you go running them on the tab itself you may have missed one somewhere.
You can't attach a file that large to a post.
Tapatalked from my Galaxy S II.
when i enter the first shell command it denies me and asks me if i am root......
ilovemywife269 said:
when i enter the first shell command it denies me and asks me if i am root......
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=23285307
Use this method.
Tapatalked from my Galaxy S II.
i tried both ics rooting methods both of which told me they achieved root however i am still denied permission to remount
with my moto phones i've always been able to flash back to stock.....or flash back to life anyways is there a way to flash this tablet?
I have a quick question, I'm wondering which if any kernels support ADB remount to push files to the /system with the phone still on? I always get this error " adb remount says "remount failed: operation not permitted" and adb push [file] /system/apps says "failed to copy '[file]' to '/system/apps/': read-only file system"
I was able to perform this function on the Note 2 with the Chainfire's adbd Insecure app but it does support T-Mobile's Note 3. It is my understanding the the kernel must support this. Right now I'm on Jedi Elite V3 with his kernel but it doesn't look like it's supported. Any Help Guy\Girls?
Happy Thanksgiving By the Way,
Thanks,
D
I had this problem and being heavy adb user I was frustrated just like you. So I did some research and found out that since JB they are using secure adbd daemon in the kernel and adb can't get root access anymore for /system. So I grabbed my favorite kernel, unpacked it with Android Image Kitchen, replaced adbd in ramdisk with the one from Chainfire's adbd Insecure app and just in case changed ro.secure and ro.adb.secure to 0 in default.prop. Repacked the kernel, flashed it and now adb works great on /system. Very simple to make your own adbd insecure kernel.
Hope this helps.
Cool, I will see what I can come up with. Thanks again
Sent from my SM-N900T using Tapatalk
Just made a how to: [MOD][HOW TO]Make your favorite kernel adbd insecure to run ADB as root on /system
Just wanted to say THANKS.....using your guide worked perfect and I was able to have system rewrite access while booted. Thanks.
Hi all
I have read many threads with similar issue, then this my way how to fix it.
Ie: Folder mount app, which make reboot the phone after we mount a folder.
Just add this line to this file : /system/etc/install-recovery-2.sh
If the file is missing, just create it.
Requirement:
on JB 4.3
superSU atleast v200 installed
busybox installed, got it from Playstore, ie: Busybox X,
Code:
#!/system/bin/sh
pkill -f /sbin/ric; mount -o remount,rw /; chmod 644 /sbin/ric
#just to make sure ric is killed
pkill -f /sbin/ric
How to:
You better know than me. but here my way.
if your phone reboot after you touch mount rw in root explorer then adb or terminal emulator is your friend
remount rw system, make the file, then push/copy to target directory, and set correct permission , chmod 755 install-recovery-2.sh
done.
.
This thread lacks a lot of info. You just forgot to cite you must have busybox installed and that this line should be put in install-recovery-2.sh if running Android 4.3 firmware to avoid conflicts with daemonsu...
conclusion:
You didn't search enough
mbc07 said:
This thread lacks a lot of info. You just forgot to cite you must have busybox installed and that this line should be put in install-recovery-2.sh if running Android 4.3 firmware to avoid conflicts with daemonsu...
conclusion:
You didn't search enough
Click to expand...
Click to collapse
Hi mbc07,
i have put the line in that file and of course is work. never get reboot again. i have read the note by superSU in that file too.
but iam forgot to cite the busybox, and i have busybox installed.
but hey thanks, i edited the OP.
How to enable USB debugging on a broken screen using ADB (Permission & Root Issue)
I have a Samsung Note 2 with a Broken screen/digitizer. So no haptic feedback's. Anyway the USB Debugging is already on and I could use the Remote tools like SideSync, Mobizen & other software's on my old machine before the screen broke. But now with new laptop I need to re-enable usb debugging or accept the fingerprint thing that pops up but I can't see what's on my screen. Also I don't know how to force this.
I've tried following several guides on how to enable through build.prop and adding lines - http://forum.xda-developers.com/showthread.php?t=2652564
but when trying to push the file back -
Code:
failed to copy c:\android\build.prop /system/build.prop : permission denied.
I've tried
Code:
adb remount
&
Code:
adb shell
su
mount -o remount, rw /system
and for both I get remount failed : operation not permitted.
I've tried using
Code:
adb usb & adb root
adb root shows error -- adbd cannot run as root in production builds.
adb usb - is just stuck nothing happens.
I've tried googling the above errors but any solutions don't seem to be working.
Reason why I use this phone is because I have kodi installed and everything was working up until now. I had wifi on the device - Do you think I could just enable or rename my wifi name to the same one? Problem would be what password I used. I still have my old router.
Any advice?
Thanks
I believe the devices isn't rooted. I tried using ADB Shell and typed in captials SU but got not found however typing it in lowercase nothing happens. just goes to the next line