New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
Ireas
Old
#1  
Ireas's Avatar
Senior Member - OP
Thanks Meter 17
Posts: 267
Join Date: Oct 2009

 
DONATE TO ME
Default ADB remount - permission denied

OK - small issue here.
It seems that you cant remount the system using the commandshell.
While you can do "su" to get super user permission when you are in the "adb shell" they get lost after closing the session and trying to mount system using the "adb remount" command.

Anyone else with the same problem?
 
FrAsErTaG
Old
(Last edited by FrAsErTaG; 12th May 2011 at 01:16 AM.)
#2  
FrAsErTaG's Avatar
Senior Member
Thanks Meter 1067
Posts: 1,341
Join Date: May 2009
Location: Canberra

 
DONATE TO ME
as Bin4ry said:

Yes it's normal.
The ro.secure is set in default.prop which is part of kernel.img (boot.img) so we need to change the ramdisk for that! I only modded the system.img -> so no unsecure shell.

Edit this has been fixed by Paul@Modaco

GScript Insecure ADB Install:

Link: Click here to download


Instructions:
1) if you already use gscript skip to step 3
2) install gscript from market, create a folder on sdcard called gscript
3) extract files from archive to gscript folder on sdcard
4) load gscript press menu, select add script, then select load script
5) Select "install modaco insecure adb.sh"
6) MAKE SURE SU is ticked, then run script
7) Enjoy adb remount
8) THANK PAUL AT MODACO

WARNING: AS PAUL HAS ADVISED THIS MAY BRICK YOUR DEVICE... Maybe.. Although I would think flashing a system.img from fastboot would repair.

WARNING: RECOMMENDED ONLY FOR UNLOCKED BOOTLOADER
If you found my post helpful please click the thank you or donate button.

The Following User Says Thank You to FrAsErTaG For This Useful Post: [ Click to Expand ]