Related
Hi there
I am following this guide:
http://forum.xda-developers.com/showthread.php?t=905261
In order to root my HTC Desire Z.
I've gotten as far as Step 15.
But when doing the:
'adb push su /sdcard/'
I got a 'permission denied', so I ran psneuter again and now I am getting:
"Failed to copy 'su' to '/sdcard//su': Read-only file system"
Can someone please help me fix this?
Thanks in advance!
For solution. Check the next post!
For the record:
I fixed this by setting the phone to NOT use the SD-card.
I had set it to 'USB-drive mode'. Setting it to 'Charger only' solved this.
Well done for working it out. I've just scanned the guide and i'm surprised to see no mention of not mounting SD when plugging in via USB. Other ADB guides usually state this as it's a common problem, along with forgetting to enable USB Debugging.
Thank you
Yes it is rather surprising, but I fixed it and am now running Cyanogenmod 6.11 on it
Thanks!
eaxexe said:
For the record:
I fixed this by setting the phone to NOT use the SD-card.
I had set it to 'USB-drive mode'. Setting it to 'Charger only' solved this.
Click to expand...
Click to collapse
Thanks a lot for updating the thread with the resolution! I was able to help my friend out.
thanks
eaxexe said:
For the record:
I fixed this by setting the phone to NOT use the SD-card.
I had set it to 'USB-drive mode'. Setting it to 'Charger only' solved this.
Click to expand...
Click to collapse
Thank for this, worked for me on htc glacier, while using the step by step from cyanogenmod.
i am attempting an sdk port with mixed sucsess with defferent methods
i have today (1/5/11) tried the port using the .36 kernel but now get stuck with a black screen no abd or the slightest signs of life :blink:
if i use origional kernel i get adb working before boot loop but if i try and run a log cat to see whats going on i get
Code:
D:\Documents\android-sdk-windows\tools>adb logcat
- waiting for device -
- exec '/system/bin/sh' failed: Exec format error (8) -
18/4/11
Gets stuck on the boot image screen
doesnt make it to boot animation
doesnt reboot
adb works
but i cant run a logcat to find out whats up?
Code:
D:\Documents\android-sdk-windows\tools>adb devices
List of devices attached
1714404540bfb617 device
D:\Documents\android-sdk-windows\tools>adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
any ideas
19/4/11
Ok so i have deleted some unused apps in system such as phone so now the system image is small enough and copies correctly
It now gets stuck in boot loop after boot image and i now have no adb
Any help welcome
20/4/11
my files are here, i dont no what to do next so go on and have a dig around if you wish
19.4-2update.zip----------------get stuck in boot loop no adb
http://www.mediafire.com/?u403ooy0mijoy4y
18.4-3update.zip----------------no boot loop but adb
http://www.mediafire.com/?isdf8wpf7d5n8pt
20/4/11
ok im a little confused not. the updater-script is the thing im least sure about but i have found a problem with it.
however when i change a load if ui_prints and some file locations and re flash it has not changed anything all the ui prints are unchanged and the problem i encountered is still their
any one know whats going on?
Click to expand...
Click to collapse
I got this message today appling a zip file into CWM 3.
Never seen it before
add.thebad said:
when i try and flash my rom in clockwork i get an error status (0) what does this mean?
Click to expand...
Click to collapse
That can mean your using the incorrect or corrupt update binary
bob1369 said:
That can mean your using the incorrect or corrupt update binary
Click to expand...
Click to collapse
Thanks i thaught i may have something to do with the update binary or script. this is my first rom how can i get a cOrrect one
Try taking one from one of the various roms for the vega but don't take the update script
Did it work?
bob1369 said:
Did it work?
Click to expand...
Click to collapse
yeah i did thanks for the help
just now it get stuck at the boot logo
doesnt get to animation or reboot but adb will work
good to here it good luck boot logo's good progress often just a few bugs from there
bob1369 said:
good to here it good luck boot logo's good progress often just a few bugs from there
Click to expand...
Click to collapse
thats good to here, just a shame i dont know where to start. could it be a problem with the update script
possible always wipe data etc trying adb logcat can reveal problems bootloops and freezes can have many causes difficult to suggest a likely fix if you have real problems i'd suggest getting help from an experienced dev
bob1369 said:
possible always wipe data etc trying adb logcat can reveal problems bootloops and freezes can have many causes difficult to suggest a likely fix if you have real problems i'd suggest getting help from an experienced dev
Click to expand...
Click to collapse
i cant get logcat to work see first post so i dont no where to start
I have this problems sometimes.. it's a problem of space in /system. You only have 105Mb in system, so bigger images dont copy all the files. In your case dont copy sh, so no shell, so no logcat or anything
Corvus.
What bootscreen do you mean black or picture
Sent from my HTC Desire using XDA App
What the Corvus said makes a lot of sense
corvus said:
I have this problems sometimes.. it's a problem of space in /system. You only have 105Mb in system, so bigger images dont copy all the files. In your case dont copy sh, so no shell, so no logcat or anything
Corvus.
Click to expand...
Click to collapse
ok thanks, so i should unyaff the system.img and delete /sh
add.thebad said:
ok thanks, so i should unyaff the system.img and delete /sh
Click to expand...
Click to collapse
Yes and no. You need to delete files so all the files fit in the system partition. Usually you can remove a handful of apps without any impact on the system.
bob1369 said:
What bootscreen do you mean black or picture
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
the cyanogen logo beacause i used the cm7 boot.img and never changer the initlogo
HomerSp said:
Yes and no. You need to delete files so all the files fit in the system partition. Usually you can remove a handful of apps without any impact on the system.
Click to expand...
Click to collapse
ok thanks, have have deleted some of the phone and sms apps and have saveed enough space, down to 92mb now
this time round it took longer to flash so i think it is copying correctly
now i get boot loop after boot logo and now i have no adb so dont know whats going on
Ok cool might restart my attempts at a port had issues with freezing sound like a similar problem had a lot in system directory on my rom
Sent from my HTC Desire using XDA App
bob1369 said:
Ok cool might restart my attempts at a port had issues with freezing sound like a similar problem had a lot in system directory on my rom
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That would be good if we can get some more peopple working on it. I just tried because i got fed up witg all the people winging about honeycomb. Ive never made a full rom b4 only tweaked so this is a big learning curve
Hopefully will see some sucsess for all my late nights reading stuff
If any one had any advice on how to fix my boot loop i would b very happy
Hello Everyone,
I have supposedly rooted my new Galaxy Nexus (CDMA) phone. All the apps that request root on the phone are able to get access to it, also if I use "adb shell" and then use the "su" command to switch to root it will grant me access, albeit without ever prompting me on the phone. However when I try to use the "adb root" command from the terminal window it gives me an error of "adbd cannot run as root in production builds".
I need this function to work, but cannot seem to find my way around it. I am not the only one I know who has seen this, but we cannot seem to figure it out. I was hoping to get some suggestions? Any thoughts?
No luck it looks like...will this bumb it?
Why do you need the command "adb root" ?
Mostly for grabbing logs via the logcat command.
Sent from my GNex,
-Originalme8
Why not "adb logcat" ?
Still don't understand why you need the specific "adb root" command.
Does it really matter what my reasons are? Maybe I am worried that there is a problem with my such controller? I just want to know why this command isn't working. If your not going to help, please don't post hand waste my time.
Sent from my GNex,
-Originalme8
you could use adb logcat as mentioned above
http://forum.xda-developers.com/showthread.php?t=833756
forum search, it's magic.
and yes, reasons matter.
Seriously...you two have been no help...
Sent from my GNex,
-Originalme8
So you are saying the link i posted, does not contain the answer to your question, although it states what causes the error message and how it can be fixed?
Originalme8 said:
Seriously...you two have been no help...
Sent from my GNex,
-Originalme8
Click to expand...
Click to collapse
So you have a "recognized developer" trying to help you out and posting a link to the problem and the fix, and that is how you respond? Good luck on XDA buddy.
Oh, and don't worry, I will hit their thanks button for you.
Old Thread and that attitude certainly wasn't the nicest but incase someone else Google Searches this...
First you need to decompile the kernel.
In your Root of decompiled files, find a file called
default.prop
Edit it with Root Explorer or ES File Explorer
Find these lines
ro.secure=1 and change it to ro.secure=0
ro.debuggable=0 and change it to ro.debuggable=1
Save and recompile. If this is already too complicated for you, then you can read about what decompiling and compiling is. Search it.
Your Kernel is likely stock kernel and will not allow this change if you don't have USB Debugging option available within your ROM.
If you have this option, then enable it. It is possible that you have half root - Unlocked boot loader, but Kernel is from a stock ROM. You can still get shell access. You just won't get it while your System is Mounted if you don't have USB Debugging enabled and you plugged into Windows while your System is running. So Reboot into Recovery, and then go into your ADB Directory and type
adb start-server
adb devices (see if it lists the connected device) if yes then type
adb root (It should say adb is already running as root)
then type
adb shell
you can use the ls command to list all the directories.
cd to change into them. like cd /sdcard then ls and so on.
and cd / to go back.
Look up basic linux shell commands.
and then you can do whatever you want. List of ADB Noob Commands
http://forum.xda-developers.com/showthread.php?t=517874
Hope this helps anyone who got in here from a Google search.
Next time try to be nice to others, and be patient. I spent time trying to help you. As did the other guys. Try to give back.
ocd_amp said:
Old Thread and that attitude certainly wasn't the nicest but incase someone else Google Searches this...
First you need to decompile the kernel.
In your Root of decompiled files, find a file called
default.prop
Edit it with Root Explorer or ES File Explorer
Find these lines
ro.secure=1 and change it to ro.secure=0
ro.debuggable=0 and change it to ro.debuggable=1
Save and recompile. If this is already too complicated for you, then you can read about what decompiling and compiling is. Search it.
Click to expand...
Click to collapse
Terribly sorry for bumping a post this old in advance. I would PM but I am also leaving a reply for people Googling this later on.
I have been searching on how to compile a .prop file for 2 hours now. The most relevant thing I could find online was a tutorial on how to compile my own ROM's but that compiles the whole ROM and seems unrelated to what you said (using Es file manager). Also, I just want to make my Stock rooted ROM debuggable.
Could you direct me to a source or simply explain how I would do that?
Hello,
I need quick help, because I got a big Problem.
I accidentaly enabled a virtual screen (xdpi) in Developer Settings and since then my device froze and will freeze at boot.
Can someone please tell me how the vallue in settings.db from /data/com.android.providers.settings/databases is called or where else I can reset that value so my device will boot again?
I already got that settings.db and I am in Recovery now to exchange it.
EDIT: Oh I am on Android 4.2.2 CM10.1
EDIT2: found the little thing named overlay_display_devices in table Global, I just deleted the line and followed that tutorial (setting the right owner and permissions)
Still freezes during boot, will try to fix permisiions automaticaly now via recovery...
EDIT3: Nope, still freezing during boot
what are the normal owner and permissions of settings.db?
I guess they are system.system and 775?
Ok ok, I am just too dumb to handle console commands...
It worked now, let this be a lesson to me how to manipulate settings without the settings app
Hi everyone.
I don't know why i have this "module". Only install the other one and nothing more.
I try to delete it then restart phone but it doesn't go away.
Not a problem, just aesthetic
That's weird....
If you are bothered and you don't mind re-installing/re-flashing all your modules again, you could try the adb command
Code:
adb wait-for-device shell magisk --remove-modules
and that should remove all your modules including that unknown weird one.
Also, if for whatever reason that doesn't work, I read somewhere that Magisk has its data folder outside of the internal storage folder and is more in the root data folder -- so if one wiped their phone, all the Magisk data (deny list i imagine, on top of modules) would still survive -- and you might consider finding and deleting that folder and reinstall/re-flash Magisk. CAUTION: I imagine this has a chance of bringing up some glitches or bugs (incompatibilities) when the app connects-to/works-in-conjuction-with the patched init_boot.
If you are still sure you wish to do that, I believe I found the folder which I put in spoilers below...
Spoiler: Magisk root folder
root: /data/adb
These are just a couple of ideas...hope it helps...
Thx for your help !
The adb command works.
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
I also have the same problem.... ".core" and i cannot delete it...its like a bug or something like that?
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
is this the official version downloaded from an official source? check the magisk forum
febo17 said:
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
Click to expand...
Click to collapse
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
simplepinoi177 said:
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
Click to expand...
Click to collapse
in fact I had already applied that line and it didn't work either in fastboot or in ell recovery. It worked for me, to my surprise, with the phone on. all modules were deleted
What version of Magisk are you using, and where did you download it from?