Related
Hello all: I am having a problem trying to root my Droid Charge. when I type adb shell, I get the $.
Then I type in /data/local/Gingerbreak
it says /data/local/Gingerbreak: not found
Any ideas?
thank you very much,
MrSpohn1 said:
Hello all: I am having a problem trying to root my Droid Charge. when I type adb shell, I get the $.
Then I type in /data/local/Gingerbreak
it says /data/local/Gingerbreak: not found
Any ideas?
thank you very much,
Click to expand...
Click to collapse
right after "adb shell" type "chmod 775 /data/local/Gingerbreak"
Then type: /data/local/Gingerbreak
That should give you premission.
MrSpohn1 said:
Hello all: I am having a problem trying to root my Droid Charge. when I type adb shell, I get the $.
Then I type in /data/local/Gingerbreak
it says /data/local/Gingerbreak: not found
Any ideas?
thank you very much,
Click to expand...
Click to collapse
try /data/local/GingerBreak
Sorry. I misstyped here. I did type GingerBreak on the thing. It isn't denying any permission. It is saying that it can't find it. I think I may have erred on my code insertion in the PATH section. It says it found my device, and when I push something it says all of what different commands mean. Is that correct? I only added the direct path to adb. Is there something else I was supposed to do?
Thanks
MrSpohn1 said:
Sorry. I misstyped here. I did type GingerBreak on the thing. It isn't denying any permission. It is saying that it can't find it. I think I may have erred on my code insertion in the PATH section. It says it found my device, and when I push something it says all of what different commands mean. Is that correct? I only added the direct path to adb. Is there something else I was supposed to do?
Thanks
Click to expand...
Click to collapse
Just use gingersnap
http://forum.androidcentral.com/cha...harge-5-19-11-windows-mac-now-gingersnap.html
Yeah Gingersnap rocks !! I Odin'd back to ED1 and then opened Gingersnap and pressed start and about 5 seconds later I was rooted !!
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?
I had the issue of downgrading the NEW out of box 2.3.4.... I was given this link by neidlinger. I had to edit the ending of it to get it to work but it worked, and is working great. Here is the link, and below it is my edit of them.
P.S. MAKE SURE YOU USE THE LINKS TO DOWNLOAD THE PROGRAMS YOU NEED....IF YOU ALREADY HAVE THEM DOWNLOAD THESE AND REPLACE THEM.(JUST TO BE ON THE SAFE SIDE) It wouldn't work for me until I re-downloaded and replaced them.
http://wiki.cyanogenmod.com/wiki/HTC_Glacier:_Full_Update_Guide
Downgrading to 1.17.531.2
If the HTC Glacier is running a Gingerbread firmware (2.xx.xxx.x) (Settings » About Phone) you need to downgrade the device first in order to root. If the HTC Glacier is already running 1.17.531.2 or lower you can skip to the Rooting the HTC Glacier section.
1. You will need ADB on the computer to proceed thru this process. Follow the Android SDK guide, to get the ADB shell on the computer.
2. Download fre3vo, misc_version 0.2 & the 1.17.531.2 firmware:
o fre3vo: Download
md5: 010e076a4a93be876579711bf8934c70
o misc_version 0.2: Download
md5: 1f40aaf88d1bf15775631a58c4361218
o 1.17.531.2 firmware: Download
md5: 49d07f0ee7de1765a6a84cb12fa53110
3. Unzip the fre3vo & misc_version packages to the same folder as adb (the /platform-tools folder within the Android SDK folder).
4. Make sure the filename of the firmware is PD15IMG.zip exactly or it will not work and copy it to the same folder as adb.
5. Connect the HTC Glacier to the computer via USB.
6. On the computer, open terminal and run the following commands:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on. If you have the "$", then the exploit has failed, refer to xda developers, RootzWiki, or #G2Root for further assistance.
/data/local/tmp/misc_version -s 1.00.000.0
exit
7. Now that misc version has been downgraded, the HTC Glacier is ready to have the firmware downgraded. On the computer, open terminal and run the following commands:
adb reboot bootloader
8. Use Volume up/down keys on the HTC Glacier for navigation and Power key for confirmation. Select Bootloader to flash the 1.17.531.2 firmware.
( IT MAY AUTOMATICALLY START )
Once finished you can Root the device by following the instructions on this link…..
http://forum.xda-developers.com/showthread.php?t=858996
its gotta be an easier way to downgrade.
It's actually very simple... I did it after 2 showers of the "herbal" essence kind. Ha...!
Sent from my HTC Glacier using XDA App
BillyBoy74 said:
It's actually very simple... I did it after 2 showers of the "herbal" essence kind. Ha...!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
i am kinda surprised with all the people on this site that no one has made a one click downgrade yet.
??????
Can anybody help me please?
i followed these steps and i still havent downgraded
bam5bam57 said:
Can anybody help me please?
adb cant read my mytouch 4g device.
Click to expand...
Click to collapse
You installed the usb driver and rebooted your computer?
Sent from my myTouch 4G using xda app-developers app
modbass said:
i am kinda surprised with all the people on this site that no one has made a one click downgrade yet.
Click to expand...
Click to collapse
Why dont you make one then?
Sent from my GT-N7000
thecool14soh said:
its gotta be an easier way to downgrade.
Click to expand...
Click to collapse
Actually used instructions from THeUnlockr.com - very easy to follow and worked like a charm.
http://theunlockr.com/2011/10/25/ho...ire-z-desire-hd-and-mytouch-4g-back-to-froyo/
CAUTION: there's a link to the Froyo ROM that seems to be defective - get the ROM from here:
http://forum.xda-developers.com/showthread.php?t=1476745&highlight=pd15img&page=1
Bass_Man25 said:
Actually used instructions from THeUnlockr.com - very easy to follow and worked like a charm.
http://theunlockr.com/2011/10/25/ho...ire-z-desire-hd-and-mytouch-4g-back-to-froyo/
CAUTION: there's a link to the Froyo ROM that seems to be defective - get the ROM from here:
http://forum.xda-developers.com/showthread.php?t=1476745&highlight=pd15img&page=1
Click to expand...
Click to collapse
I tried following theunockr directions but it didn't work. I wound up having to turn my SD card into a goldcard for it to finally downgrade (what a stupid idea going for the unlocked bootloader was)
This is the RIGHT one.
skygear said:
This is the RIGHT one.
Click to expand...
Click to collapse
This is the Right WHAT?
K-JACKS said:
This is the Right WHAT?
Click to expand...
Click to collapse
Shhh. Pretend it's not there and slowly walk away.
Jerk. This is the right set to downgrade.
Can't believe you were thanked for your stupid response.
Lol... Yes it works like a charm...
Estalling lol looking good so far for that RC title.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Lol... Yes it works like a charm...
Estalling lol looking good so far for that RC title.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Hahaha :thumbup:
Thank You!
Thank you, I have an HTC Glacier MyTouch 4g and I can not root, unlock the bootloader, or downgrade! I just went through the Android Bullet but failed after about 5 tries.
modbass said:
i am kinda surprised with all the people on this site that no one has made a one click downgrade yet.
Click to expand...
Click to collapse
NOOB needs help
Can someone please help me.... trying to down grade and ready to give up. This is my second day on this and just got past (adb shell cat /dev/msm_rotator). Anyone have a new way to downgrade?
I always use the instructions on theunlockr.com actually just did it last week to a vision which is the same process. Make sure u follow directions exactly and don't skip through.
As long as u have adb set up correctly then all is good.
Sent from my HTC myTouch 4g using xda app-developers app
This Device Does Not Support This Exploit
I've tried a few different guides for temp root, but they all rely on fre3v0. The issue I am having is that after running the /data/local/tmp/fre3vo command, or its alternate configurations, the device returns:
Code:
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The expoit has failed.
Does anyone know what causes this issue? Or does anyone have an alternative way for gaining temporary root? I spent the evening looking around but haven't found any strong leads.
Device info: Android 2.3.4, HTC Sense version 2.1, Software number 2.32.531.1, Kernel 2.6.35.10-g4dcb781
PopeOnABomb said:
I've tried a few different guides for temp root, but they all rely on fre3v0. The issue I am having is that after running the /data/local/tmp/fre3vo command, or its alternate configurations, the device returns:
Code:
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The expoit has failed.
Does anyone know what causes this issue? Or does anyone have an alternative way for gaining temporary root? I spent the evening looking around but haven't found any strong leads.
Device info: Android 2.3.4, HTC Sense version 2.1, Software number 2.32.531.1, Kernel 2.6.35.10-g4dcb781
Click to expand...
Click to collapse
the method works trust me print full device info from hboot. just follow the guid on the unlockr.com and if u cant get s-off after they say u should follow the post in the comment or better yet a ton load of proven tuts on this site
3/14. I had to do a complete reset after a botched install of Revolver
I really want to get back to the PRIME ROM I had running before I messed up.
On Sunday, I did a one click root, then installed CWM and then the PRIME ROM ( wished I would have left well enough alone.)
Now I can't even get this Tablet to root ( TF101). ( Razorclaw)
I updated to 4.0.3 yesterday. Could that be the issue? If so, any suggestions on how I get back to the Prime ROM, CWM and root.
Thanks in advance, and please feel free to kick the sh!t out of this noob.
ViperMod will root ICS on both TF101 and Prime.
I just tried vipermod today and it won't work . I'm using Ubuntu and at every line in the script it says " cannot stat no such file or directory
Sent from my Transformer TF101 using xda premium
Sounds like it might be path errors. ViperMod is only a batchfile of ADB commands. You should be able to open up the batchfile and manually type and run the pertinent commands at a prompt if you have to, changing path and filenames where necessary.
You need to
chmod +x adb
Also remember to ensure adb can see your device. Use
adb devices
If your device is not seen, you need to add a udev rule in /etc/udev/rules.d/
Krish.Nagarajan said:
You need to
chmod +x adb
Also remember to ensure adb can see your device. Use
adb devices
If your device is not seen, you need to add a udev rule in /etc/udev/rules.d/
Click to expand...
Click to collapse
I did that and it does see the tf. But once I am in the path where my adb resides then I do sudo sh primetime.sh I still get all those errors.
Do I need to chmod the adb file that's residing in the PrimeTime folder as well?
I did add the rules to the 99-android.rules also
Sent from my SGH-T959 using xda premium
Hey E, I sent you a PM for a possible solution.
Woodrube said:
Hey E, I sent you a PM for a possible solution.
Click to expand...
Click to collapse
Got it man. I'm rooted now. :-D my issue was using wrong command in terminal.
Sent from my Transformer TF101 using xda premium
Uhm, I have a XYBOARD 10.1 inch (WIFI ONLY) And I edited something in Build.PROP. I then restarted at to my surprise it goes completely black after it shows the Motorola DUAL CORE screen. I can get into the recovery. I even Factory Resetted thinking that might help but, Nothing. Is there anything I can do to restore it? Because I'd rather not have an expensive XYBOARD paper weight.
BUMP? I really need help.
if you can get to recovery, you should be able to push stock OS via ADB.. there is a guide in the Xoom development section.
pinoiryder said:
if you can get to recovery, you should be able to push stock OS via ADB.. there is a guide in the Xoom development section.
Click to expand...
Click to collapse
And this is for XYBOARD? Anyway, I can't find the topic...
is there not maybe a way you can pull the build.prop file via adb edit change what you editied, then push it bk via adb???
just outta curiosity, what did you change in the build.prop, also remember, ALWAYS MAKE A BACKUP FIRST!!!! lol
[email protected] said:
is there not maybe a way you can pull the build.prop file via adb edit change what you editied, then push it bk via adb???
just outta curiosity, what did you change in the build.prop, also remember, ALWAYS MAKE A BACKUP FIRST!!!! lol
Click to expand...
Click to collapse
...
How do you make a BackUp on a XYBOARD?
Anyway, Can someone just link me to the needed programs and topic?
ok well since you know, you cant make backups on an XYBOARD then why muck about with it????
[email protected] said:
ok well since you know, you cant make backups on an XYBOARD then why muck about with it????
Click to expand...
Click to collapse
If one doesn't muck around with things, Nothing will ever be discovered.
But I should of waited until someone better at things like this paved the way.
*Beats self with XYBOARD*
SUperFatCatNine said:
If one doesn't muck around with things, Nothing will ever be discovered.
But I should of waited until someone better at things like this paved the way.
*Beats self with XYBOARD*
Click to expand...
Click to collapse
Lol can you not download the original image from motorola and flash it somehow ?? There must be a way surely
Sent from my Xoom using XDA Premium App
Does anyone have the stock build.prop for XYBOARD 10.1 Wifi only?
Also, How do you push it on using ADB?
I think there is no way to solve the problem. Send it to Motorola and will fix it for you.
Sent from my XOOM 2 ME using Tapatalk 2
As the XOOM2/Xyboard has a locked bootloader and no bootstrap for a recovery so your stuck right now until Motorola decides to care about the Android community. Also adb is not possible from what I heard when it can't boot. If you want some help then contact the not many Xyboard devs here "Bricks" as they are always happy to help bricked people.
luke.arran said:
As the XOOM2/Xyboard has a locked bootloader and no bootstrap for a recovery so your stuck right now until Motorola decides to care about the Android community. Also adb is not possible from what I heard when it can't boot. If you want some help then contact the not many Xyboard devs here "Bricks" as they are always happy to help bricked people.
Click to expand...
Click to collapse
It's More of a soft brick. I can get into recovery.
(It's Still Makes a Nice Frisbee or Paper Weight. xD)
SUperFatCatNine said:
It's More of a soft brick. I can get into recovery.
(It's Still Makes a Nice Frisbee or Paper Weight. xD)
Click to expand...
Click to collapse
I'm in the same situation as you as of today (But I have the Verizon Droid Xyboard 10.1). Messed around with the Build.prop and now its not working. I have a copy of the original Build.prop but don't know how I can push it to my tablet.
Adb is not working but fastboot is.
I don't think my original build.prop would be any help to you since I have the 4G version but if you want it let me know and I will send it to you!
Looks like I may have to send it to Motorola :-(
OK guys, no worries... I think I know the solution.
1 - enter in recovery
2 - open cmd on your PC
3 - go to adb and fastboot folder via cmd
4 - type:
Code:
adb devices
adb shell
su
cd /system
rm build.prop
exit
5 - copy original build.prop to this folder (adb one)
6 - type:
Code:
adb push build.prop /system/build.prop
adb reboot
exit
Hope that helps you guys it already helped me (I have the Origina Xoom)
Sent from my MZ601 using XDA Premium HD app
Just one more little thing, I presume you guys have su, as you changed build.prop and recovery (because to install super user recovery is needed!) If you guys don't have them, I'm sorry but don't know a solution...
Sent from my MZ601 using XDA Premium HD app
XxLordxX said:
OK guys, no worries... I think I know the solution.
1 - enter in recovery
2 - open cmd on your PC
3 - go to adb and fastboot folder via cmd
4 - type:
Code:
adb devices
adb shell
su
cd /system
rm build.prop
exit
5 - copy original build.prop to this folder (adb one)
6 - type:
Code:
adb push build.prop /system/build.prop
adb reboot
exit
Hope that helps you guys it already helped me (I have the Origina Xoom)
Sent from my MZ601 using XDA Premium HD app
Click to expand...
Click to collapse
And where might I find CMD?
It's a Windows thing... just search a little on it... try using the menu option to show up everything and search for cmd... Which OS are you using?
Sent from my MZ601 using XDA Premium HD app