Database Users

Downgrade from 1.72 issues with cmd

Android SDK installed in programfiles
ADB in this folder : C:\Program Files\Android\android-sdk-windows\platform-tools
written in cmd, with USB debugging activated and charge only.
C:\Users\any\adb devices. my device shows!
Is this the right thing to insert to cmd or the one below
1. Answers!
adb push psneuter /data/local/tmp : A bunch adb commands shows
adb push misc_version /data/local/tmp : A bunch adb commands shows
adb shell chmod 777 /data/local/tmp/psneuter :unable to chmod, no such file
adb shell chmod 777 /data/local/tmp/misc_version :unable to chmod no such file
adb shell /data/local/tmp/psneuter : Not found
adb shell :$
or this
2.
adb push psneuter C:\Program Files\Android\android-sdk-windows\platform-tools
adb push misc_version C:\Program Files\Android\android-sdk-windows\platform-tools
adb shell chmod 777 C:\Program Files\Android\android-sdk-windows\platform-tools/psneuter
adb shell chmod 777 C:\Program Files\Android\android-sdk-windows\platform-toolsmisc_version
adb shell C:\Program Files\Android\android-sdk-windows\platform-toolspsneuter
adb shell :$
Have I installed the Android SDK in the wrong folder or what is thats going wrong?

First is correct, but you have to have psneuter & change_misc files in current directory so adb push could find them.

Whats the current directory?

Probably C:\Program Files\Android\android-sdk-windows\platform-tools.
You can also use it like this: adb push c:\some_directory\psneuter /data/local/tmp
Syntax is: adb push [what you want to push] [where you want it to go]

istopp said:
Whats the current directory?
Click to expand...
Click to collapse
Current directoty is the folder you are in.

Could you resolved the above problem?
because even i am not able to use adb shell chmod 777 command, its shows the same result.
Any help will be appreciated.
Thanks.

Thanks a lot, i just copied the content of the C:\Program Files\Android\android-sdk-windows\platform-tools directory to C:\Users\any\ and tried then, work perfect, finally got the # instead of $
What are the instructions im suppose to follow in the bootloader? fastboot,recovery,factory reset,simlock or image CRC?

istopp said:
Thanks a lot, i just copied the content of the C:\Program Files\Android\android-sdk-windows\platform-tools directory to C:\Users\any\ and tried then, work perfect, finally got the # instead of $
What are the instructions im suppose to follow in the bootloader? fastboot,recovery,factory reset,simlock or image CRC?
Click to expand...
Click to collapse
None of the above. If you've done it correctly, the phone should find PD98IMG.zip on its own. Is your device branded? If so, make sure you have correctly created your Goldcard.

Official update to 1.82.405.1 stock ROM (from 1.72..) and root

Hi there,
I tried if it is possible root on stock ROM 1.82.405.1 on HTC Desire Z. YES, we can!
This is a little "how to" with all previous roots and updates from "1.34.." to actual 1.82.405.1 stock ROM:
Permanent root on HTC ESIRE Z using linux
Software No. 1.34...
Necessary files:
adb (Android SDK)
gfree_02
psneuter
Terminal emulator (Android)
Optional files:
gfree_verify
Settings on Phone:
Menu-Settings-Applications-Development-USB debugging [yop]
USB connected to PC – only charge (card not mounted to PC)
Procedure on PC:
Check your device is properly conneted:
$ ./adb devices
It has to be like this : SH0BFRT00451 device
Than continue:
$ ./adb push su /sdcard/su
$ ./adb push Superuser.apk /sdcard/Superuser.apk
$ ./adb push rage /data/local/tmp/rage
$ ./adb push busybox /data/local/tmp/busybox
$ ./adb push root /data/local/tmp/root
$ ./adb shell chmod 0755 /data/local/tmp/*
On Android:
Launch Terminal Emulator
$ /data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Procedure on PC:
$ ./adb push gfree /data/local
On Android:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
# /data/local/tmp/root
# sync
there can be some errors with directory create – it is ok.
update to 1.72 via system and do following again:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
update from 1.72 to 1.82 via system and again root:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
Superusere error is patchable by this:
http://forum.xda-developers.com/showthread.php?t=886999
check /sys/devices/system/cpu/cpu0/cpufreq/current_scaling_freq​

But do we need to be already on 1.82++ or do we need to downgrade to 1.34++ because I don't really understand what we have to do!
PS: really really thank you!!!!! (all other root methods failed for me, so fingers crossed that this one will work!)

You need to have S-OFF; if you don't you need to go to 1.34 to get it, then upgrade back up the chain...

oh, thanks... I guess I'll have to downgrade then, wouldn't I

I guess so, but should only have to do it once...
Sent from my HTC Vision using XDA App

I rooted my 1.72 device a while ago with this tut: http://forum.xda-developers.com/showthread.php?t=905261
Should I be fine by just executing the latest part off this tut?
Code:
update from 1.72 to 1.82 via system and again root:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....

I got error:
E:signature verification failed
I'm using clockwork recovery 2.5.1.3. I think that's the reason, anyone got a fix for this?

hi, I have desire Z with bootloader 1.82.405.1 , from which stage should I start the rooting process?

Quick Question for Rooting

I have a MT4G and I'm using the Cyanogenmod rooting technique. I'm at the part where i'm pushing certain files to the /data/local path.
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
When i get to "root_psn", I get the error that I cannot push due to being read only...I dont understand because this is the same path as the rest of the files, and I have no problem with them.
I don't want to go any further until I know what's going on.

Are you sure your not just running out of space on your data partition?

Gene Poole said:
Are you sure your not just running out of space on your data partition?
Click to expand...
Click to collapse
It was actually a mistake on my part. I was typing only /data/tmp for some reason...
Anyway, I moved on from there, having trouble here:
adb push su /sdcard/
failed to copy 'su' to /sdcard//su': permission denied
Same error goes for Superuser.apk, and once i get into the adb shell I get permission errors for /data/local/tmp/psneuter.
I didnt go any further than this. My phone is still fine, I also do NOT have visionary installed. I also got rid of the superuser app that was already on my phone.
Kind of stuck.

ugh, wtf. More trouble.
Moved passed the previous error, now i have a new one:
./gfree -f -b hboot-eng.img -y recovery.img
"Error opening backup file"
I tried the next step, then get the error saying how Superuser.spk and SU cannot be found. I placed them directly on the SD card via usb cable since I got the error of write protected SD card.

Trouble rooting 3.2 wifi xoom

Hi guys I can't post in the xoom root thread yet so I had to start a new thread. I am following this guide to root my xoom http://forum.xda-developers.com/showthread.php?t=1170760. I had no trouble up until this point
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
I remounted the xoom but then when I type "adb push su /system/bin" it says "cannot stat "su' no such file or directory" and nothing works after that. Does anyone have a solution?
Update: SOLVED! To anyone else having this problem I figured it out. Make sure the su and superuser apk files are OUTSIDE of the original folder and in the platform tools folder.

Rooting LG V20 H990DS?

Been reading this guide here --» https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
despite much of a mess that it is and poorly written in some regards. I can make perfectly good sense of it all, but the commands issued most of them are pretty useless, or don't work as they're instructed to do.
Let me point out some stuff here, cuz I'm trying to work my way through the tutorial to root my LG V20 H990DS (International) btw;
ok so the first part here it explains the following;
6. Using dirtysanta's steps: Run "RUNMEFIRST.bat" <-- Do not close.
7. Run "step1.bat" <-- Wait until you can type something again.
Click to expand...
Click to collapse
in my case here I'm using Linux, not Windows to do this, so things are simpler, the RUNMEFIRST.sh executable literally does nothing, when I can see it clearly is suppose to do something, let's take a look at what that files trying to run;
Code:
#!/bin/sh
# runmefirst.sh
#
#
# Created by me2151 on 12/13/16.
#
adb logcat | grep -a dirtysanta
OK, so it's using logcat to see what the phone is doing while piping to grep to watch out for dirtysanta being written to the phone while you have step1.sh running in another terminal instance, when that command completes you're left in ADB Shell of your device. Meanwhile the first shell script doesn't report anything going on, OK that's fine, doesn't matter since it wrote the contents of the required files to the phone, so it's there, as it should and as it's described in the shell script;
Code:
#!/bin/sh
# Step1.sh
#
#
# Created by me2151 on 12/11/16.
#
adb push dirtysanta /storage/emulated/0
adb push aboot.img /storage/emulated/0
adb push dirtycow /data/local/tmp
adb push my-run-as /data/local/tmp
adb shell chmod 0777 /data/local/tmp/*
adb shell /data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/my-run-as
adb shell /data/local/tmp/dirtycow /system/bin/applypatch /data/local/tmp/dirtycow
adb shell
Now this next part, doesn't work at all, because in the tutorial guide, they said to do chmod 777 permissions on "/storage/emulated/0/*" this doesn't work because operation is not permitted by the file owner and group root, there is no write permission to change permissions of that directory structure.
Code:
chmod: chmod '/storage/emulated/0/Android' to 40777: Operation not permitted
and yes /storage/emulated/0/ is suppose to be your storage userspace of where you save your files and stuff. Your "virtualized" SD Card space, you have normal read-write access there anyways. The next part of that tutorial says to check the id output from the Terminal Emulator app on Android, and check for the response "untrusted_app", that I do get, if you're doing it through ADB Shell you'll get "context=u:r:shell:s0" instead.
Part 12 of the tutorial has misuse or incorrect command line usage for applypatch, it will not simply execute because the command line usage is incorrect like so;
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
it'll just simply return the following;
Code:
usage: applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Filenames may be of the form
MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...
to specify reading from or writing to an MTD partition.
obviously the step2 shell script can't do anything because there is nothing to backup, since it's calling to backup the boot images off the device.
So far I haven't been able to find any comprehensive or updated rooting guide for LG V20 H990DS in particular, nothing new worked on seems to popup anywhere as of yet.

bump this

No help for this at all? Just gonna be another one of those dead-end topics with no answers?