hiya everyone, im new on here and really need some help.
im trying to downgrade my android software so im able to root it. only problem being ive never used command prompt lol!!
the guide im using says:
Launch a Command Prompt window and browse to the location of the files extracted in Step 1.
Enter the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
You should now get the # prompt, indicating temporary root.
Enter these commands:
cd /data/local/tmp
./misc_version -s 1.31.405.6
but how do i browse for the files if ive stored them in my documents and in a folder called downgrade android.
many thanks
What device are you trying to downgrade and what version of Android are you currently on? If it's Gingerbread there is a oneclick root called gingerbreak that works for a lot of people.
More info needed really.
Related
hiya everyone, im new on here and really need some help.
im trying to downgrade my android software so im able to root it. only problem being ive never used command prompt lol!!
the guide im using says:
Launch a Command Prompt window and browse to the location of the files extracted in Step 1.
Enter the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
You should now get the # prompt, indicating temporary root.
Enter these commands:
cd /data/local/tmp
./misc_version -s 1.31.405.6
but how do i browse for the files if ive stored them in my documents and in a folder called downgrade android.
many thanks
keeps saying not a batch file :s
Moving them into the SDK tools folder temporarily would make things easier and would mean only the file name needs to be typed rather than the specific location, try it out, I hope I remembered correctly
dannysissons said:
hiya everyone, im new on here and really need some help.
im trying to downgrade my android software so im able to root it. only problem being ive never used command prompt lol!!
the guide im using says:
Launch a Command Prompt window and browse to the location of the files extracted in Step 1.
Enter the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
You should now get the # prompt, indicating temporary root.
Enter these commands:
cd /data/local/tmp
./misc_version -s 1.31.405.6
but how do i browse for the files if ive stored them in my documents and in a folder called downgrade android.
many thanks
Click to expand...
Click to collapse
you can either modify the command like this:
adb push C:\users\[YOURUSERNAME]\My documents\downgrade\psneuter /data/local/tmp
or setup a locale path variable to the dir, where adb is stored as mentioned in THIS thread. (step 4)
Then you can simply cd to the dir, where your files are stored, and run adb from there (actually you can run adb from any dir then)
I hope somebody can help me with this little anomaly.
Been trying to downgrade htc panache with gingerbread 2.3.3.
I was able to successfully execute the commands listed on the guide (http://forum.xda-developers.com/showthread.php?t=1178912) however, when i try to downgrade the misc_version, I get the "PERMISSION DENIED"
Here is how it goes:
> adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/*
> adb shell
> cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0: PERMISSION DENIED
According to the guide I should have seen something like this (--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...)
Please help
I've been following (or trying to) the same guide. I ran into the same error. From another member here, "aDeQ666", I found the following:
To be entered in adb
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Fixed my problem, but the next step, "./flashgc" , give the permission denied error. Still looking for answers ....
Type in
Code:
su
to gain superuser permissions before attempting those commands
They're most likely working in temp-root shell, where there is no su, and they don't need to call it explicitly.
The first case is solved, AFAIK.
The second case has some problems:
1) The first command is wrong. It should be:
cd /data/local/tmp/
2) A command is missing before running ./flashgc:
chmod 777 flashgc
3) You don't need to run ./flashgc in any case. You don't need a goldcard for downgrade, unless you have a Panache - and if you have and follow Panache guide, you'll see that a goldcard is already prepared in another form.
Nicgraner said:
Type in
Code:
su
to gain superuser permissions before attempting those commands
Click to expand...
Click to collapse
ive tried that, and it says su not found
How about actually reading the thread before posting?
Jack_R1 said:
They're most likely working in temp-root shell, where there is no su, and they don't need to call it explicitly.
Click to expand...
Click to collapse
So this is probably the wrong place, but I don't see anywhere more applicable, so please move if necessary.
Bought a LG Viper for the wife today, so had to root it
I found a post elsewhere (can't post URLs yet, but it's on androidcentral) that stated how using SuperOneClick, but personally I'm a CLI kind of guy, so this is for anyone using linux (probably could easily be used on Windows, I think you'd need the "LG Universal Drivers", but )
Getting right to the point, you must have adb installed and working.
Notes: Make sure you've got USB Debugging enabled at this point. Might as well make sure "Unknown Sources" are allowed as well.
Go ahead and plug your phone in to your computer now.
Step 1) Find the device on your computer
In /etc/udev/rules.d/51-android.rules add the following (editing as root):
* Note: I had recently rooted a Kindle Fire and had other config in this file, if you do to you can just prefix the lines with a "#" and it will be ignored. You can find the vendor ID by running 'lsusb'
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="YOUR-USERNAME", GROUP="YOUR-USERNAME"
Reboot at this point (or restart udev and logout/in)
Step 2) Grab a copy of "rageagaintthecage" and do the following
adb push rageagainstthecage /data/local/tmp
Step 3) Shell time
adb shell
Once you're in the prompt:
chmod 755 /data/local/tmp/rageagainstthecage
/data/local/tmp/rageagainstthecage
* Note: You'll be kicked out out the prompt at this point, as expected.
Step 4) You've got temporary root (if that's all you want, stop now), otherwise let's make it permanent
adb kill-server
adb start-server
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p27 /system
adb push su /system/bin
adb shell chmod 755 /system/bin/su
Step 5) Install tools
On your phone, download "Superuser" and "Busybox Installer"
Run Busybox Installer
Step 6) Enjoy
Post up any questions, glad to help if possible
Which version of su did you use to push to the device?
The temp root has worked but when I go to install Superuser and update I get this error:
Getting exe path failed with 13: Permission denied
Any ideas? Thank.
-Shaun
When I run RATC, how long do I leave it running? I see the adb shell prompt ($) come up, but then the console feeds a line, and doesn't respond. I eventually press ^C to get back to the windows cmd prompt, but I don't know if I'm doing that too soon (it hasn't spawned all the proc it needs to yet) or if it just doesn't work.
when I type "su" into the adb shell after restarting the server, I get
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I pushed a copy of su into /data/local/tmp and made it executable, but that doesn't work.
127|[email protected]:/ $ /data/local/tmp/su
/data/local/tmp/su
reloc_library[1285]: 15938 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|[email protected]:/ $
Any suggestions?
Use any 1 of the following methods.
I have personally tried these on 2 of my china android phones.
1. Using linux {Recommended}Install Ubuntu or DebianEither
Install the android-sdk.
dl.google.com/android/adt/adt-bundle-linux-x86-20130717.zip <==x86
dl.google.com/android/adt/adt-bundle-linux-x86_64-20130717.zip <==x86_64
or
Just get the standalone adb and fastboot executables
texasice-cream-sandwich-mirror.googlecode.com/files/adb_fastboot.zipInstall ia32-libsRun this in a terminal
Code:
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
Now download the files required for root and put it in the same folder as adbmir.cr/GDEPZT4VAfter you finish installing the files,
Connect your device with debugging mode enabled
Run
Code:
cd path/to/adb
where "path/to/adb" is the directory of your adb file
Now run
Code:
sudo chmod a+x adb
sudo chmod a+x fastboot
>>Root
Code:
./adb devices
./adb push psneuter /data/local/tmp/
./adb push busybox /data/local/tmp/
./adb push su /data/local/tmp/
./adb push Superuser.apk /data/local/tmp/
./adb shell
Chmod and run the exploit under adb shell
Code:
cd /data/local/tmp/
chmod 755 psneuter
./psneuter
Now re-engage an adb shell to check if the exploit worked.
Code:
./adb kill-server
./adb devices
./adb shell
If you see a # sign, the exploit was was successful. Otherwise repeat from >>Root
Now run these on the same adb shell
Code:
cd /data/local/tmp
./busybox ash
mount -o remount,rw /dev/block/mtdblock0 /system
cp /data/local/tmp/su /system/xbin/su
chmod 6755 /system/xbin/su
chown 0.0 /system/xbin/su
cp /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 777 /system/app/Superuser.apk
cp /data/local/tmp/busybox /system/xbin/busybox
chmod 6755 /system/xbin/busybox
Now reboot your device and open up SuperSU. Let it update the binary.
Your device should be rooted. 2. Use Windows + MoboroboMethod 1 {Recommended but hard}
Download Moborobo from
Code:
moborobo.com
This software can Install drivers for many china phones and other branded phones.
After installing Moborobo download the files required for root
Code:
mir.cr/GDEPZT4V
Extract the files to the installation directory of Moborobo.
Code:
C:\Program Files (x86)\Moborobo
Run a CMD window under that directory and type
Code:
xcopy AndroidInterface.exe adb.exe
Connect your device in debugging mode & Open up Moborobo, It will install the drivers.
Keep Moborobo open & Follow the instructions mentioned in >>Root
P.S- the linux commands begin with a "./" remove this in windows or else it won't work. Note: Wherever I mentioned a terminal, the windows equivalent to this would be cmdMethod 2 {Easier}
Download and Install Moborobo just like above and run this under a cmd on that folder
Code:
xcopy AndroidInterface.exe adb.exe
Also download UnlockRoot or SuperOneClick
To make sure the adb files are of the same version, Copy over
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
to UnlockRoot's tools directory or SOC's ADB directory
Connect your device in debugging mode and open up moborobo.
Now keep Moborobo open and Run UnlockRoot or SOC. Good Luck :good:
---Smo0thK, team BL4CKF1R3---
Click thanks if I helped you.
[/COLOR]
Hi there!
under method 2 in the end...I could not locate ROOT nowhere.....
>>Root
arena1 said:
Hi there!
under method 2 in the end...I could not locate ROOT nowhere.....
Click to expand...
Click to collapse
I said follow the instructions mentioned in ">>Root".
I named a step in Method one as ">>Root". So I meant you should repeat those steps.
Now download the files required for root and put it in the same folder as adb
mir.cr/GDEPZT4V
Click to expand...
Click to collapse
What files?
EDIT: managed to do all the steps using method 1 in windows but got this message with executing ./psneuter :
mnmap() failed. Invalid argument
I used windows to root
failed at adb shell psneuter command...
/system/bin/sh: psneuter: not found
how to proceed ?
Hi all:
I am using the guide 1 HTC Desire Z: Firmware Downgrade (Gingerbread) .
i have managed to get the golden card.
on step 6,
at the last line, CHMOD 755 /DATA/LOCAL/TMP, i get the msg:
unable to chmod, /data/local/tmp/fixsu.sh: operation not permitted
On the computer, open terminal and run the following commands:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
whathould i do?
Did you followed the instructions like in this thread: http://forum.xda-developers.com/showthread.php?t=1947934 ?