Root Help - Eee Pad Transformer Q&A, Help & Troubleshooting

I'm having trouble with step 4 of the rooting guide. The command prompt says:
data/local/gingerbreakBB: not found
Where should I place the files from the zip? Inside the platform-tools folder? Or inside a different folder?
Thanks in advance for helping a noob.

You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk

Jocelyn said:
You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
All the files were in the platform-tools folder originally. Just making sure because it isn't working.

Cory1234 said:
All the files were in the platform-tools folder originally. Just making sure because it isn't working.
Click to expand...
Click to collapse
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk

Jocelyn said:
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
Do you mean like to: C:\program files (x86)\android\android-sdk\platform-tools
??
I'm going to reinstall everything one more time.

Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?

Cory1234 said:
Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?
Click to expand...
Click to collapse
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9

baseballfanz said:
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9
Click to expand...
Click to collapse
Thanks. I got that info earlier by using google . Now I'm stuck on step 9. I am in a new terminal window. The output I receive after entering "md5sum cwm_blob_retransfer" is "md5sum is not recognized as an internal or external command, etc.
I also tried md5sums as another member commented on. Still no go.
This is starting to get frustrating..Jailbreaking was simple compared to this.

Anyone have any ideas?
Edit: Dur, Finally got it. Apparently, some of the files had write protection on them for some reason, which was causing all the problems. Thanks everyone for the help.

Related

[GUIDE] How To Root The Sprint CDMA Hero (Windows)

I have compiled this guide from the other one posted on this forum, the discussion therein, and my own knowledge. If you have any suggestions on making it better or to correct any mistakes I may have made please let me know.
This guide is intended for Windows and includes detailed instructions. It will cover the steps necessary to root, flash the new recovery image, create a full backup. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). If you have updated to 2.1 please following this guide here. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
I have put to together a video on YouTube for you to follow along as well. The version numbers of certain files are now outdated in the video so change file names as necessary.
If you own a non-Sprint Hero, you will need to do some extra steps. Follow the guide in the How to Root Non-Sprint CDMA Hero thread.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The Windows file is called android-sdk_r06-windows.zip. Extract the files to your C: drive so that you now have the folder C:\android-sdk-windows
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to C:\android-sdk-windows\tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g Place this file in C:\android-sdk-windows\tools as well.
Step 4: Make sure USB Debugging is off by going to Settings>Applications>Development. Now connect the phone to your PC via USB cable.
Step 5: Mount your sdcard; Browse to the HTC Sync folder and install HTC Sync on your pc. After it is done installing unmount the sdcard then enable your USB debugging.
Step 6: Open a command prompt by clicking the Start button and typing cmd into the search box and pressing enter or found under All Programs>Accessories.
Step 7: You will now enter a series of commands which I will place inside code boxes to indicate the entire command. You may copy and then paste them into the command prompt window by right clicking. Only enter one command at a time.
1:
Code:
cd C:\android-sdk-windows\tools
2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging AFTER you connect the USB cable. Continue on once you get the proper phone serial output.
3:
Code:
adb push asroot2 /data/local/
4:
Code:
adb shell
5:
Code:
chmod 0755 /data/local/asroot2
6:
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#​Now for a few last commands.
7:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
8:
Code:
cd /system/bin
9:
Code:
cat sh > su
10:
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
11:
Code:
exit
12:
Code:
exit
13:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
15:
Code:
adb shell
16:
Code:
su
17:
Code:
cd /sdcard/
18:
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
19:
Code:
reboot recovery
Step 8: This is the last command; you may now close the cmd prompt. This will cause your phone to boot into recovery mode; it should take no longer than 30 secs. The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system. Rebooting your phone after installing the new recovery image may take several minutes.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!
wow dude,
instructions worked great on Win7
i was able to download the missing usb_drivers by running SDK Setup in C:\android-sdk-windows, and selecting the usb driver from the available packages. I was unable to download the index for the SDK Setup program until I enabled "force http://" in the settings menu.
had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
izanagi said:
wow dude,
i'm about to follow these instructions. thank's for the precise list!
(btw, about to try it on Win7.. may have to change some folder pathing but we'll see)
okay.. typo on the first command in parentheses, and I'm missing the usb_drivers folder (do you have it / can sent it to me) so am unable to install the device in win7.
Click to expand...
Click to collapse
Heh, thanks for the misspell heads up. I did my rooting from Win7 pc; it automatically installed correct drivers for me. To check go to the Control Panel>View devices and printers. You see one device named "Android Phone". Otherwise as far as Ive heard installing HTC Sync installs proper drivers.​
izanagi said:
*** edit had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
**** edit: all done.. your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
Click to expand...
Click to collapse
Thank you for taking the time help make my guide better. I'm very glad to know there are little to no hiccups.
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
detox702 said:
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
Click to expand...
Click to collapse
This guide is for the CDMA Hero not the Eris!
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no. I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip". This is done from the boot menu. Does the rom load automatically? Did I do something wrong? I got root with no problem. A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Never mind. I held down Home and Power at
the same time instead of Home THEN power! ARRGH! Loading up now as I type. Sorry.
ELIMINATED said:
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no.
I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip".This is done from the boot menu.
Does the rom load automatically? Did I do something wrong? I got root with no problem.
A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Click to expand...
Click to collapse
yuck... break up your sentences, that's alot of crap to throw on someone all at once... and the bold doesn't help it any.
check to see if you have the custom recovery installed....
-turn off phone
-hold vol down + power
-should search for some stuff then give three options
-press "home" to enter recovery image
do you see "!" and a phone.... does it just hang or do you see a green/yellow menu?
At the end of his post he says he figured it out. He wasn't holding down home key
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
awesomeindeed said:
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
Click to expand...
Click to collapse
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
thank you TS. I've been lurking xda for a couple years now when i had the mogul and tp. First time on an android device. Thank you for your time in helping me.
someone buy this man a drink!!!
Invaluable piece of work right here, helped me get it done in no time at all....real clear concise and very helpful....REQUEST THIS BE A STICKY!!!!!
fenske09 said:
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
Click to expand...
Click to collapse
That was the name of the zip file not the extracted folder.
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
newtodroid said:
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
Click to expand...
Click to collapse
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
theresthatguy said:
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
Click to expand...
Click to collapse
also make sure you have the heroc version there's a hero and heroC, i messed that up once and had similar results
new ROM
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
kristaps said:
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
Click to expand...
Click to collapse
you converted your sd card to fat32,ext2,swap and now the apps are looking for the program on your sd card,
turn off your phone
take out sd card
turn on phone
uninstall app
turn off phone
put in sd card
turn on phone
reinstall app
this should fix you

Need help

I rooted my cool with one click method and tried to flashed the latest tiamat kernel for SD card capabilities got as far as the and remount step and got to the step where you adb push the kernels system files and it didn't work it said file location doesn't exist now my WiFi doesn't work I'm sorry this is just one big sentence but I need help.
Sent from my PC36100 using XDA Premium App
Do you mean it can't find the files on your computer? Easiest fix is to copy all files in every subdirectory of the ZIP archive into one folder and run the adb commands from there.
My cmd is c:/users/(nam
Sent from my PC36100 using XDA Premium App
E)/ and I put the kernels system files there and adb pushed the file name and location and it still didn't work
Sent from my PC36100 using XDA Premium App
does your cmd window look anything like the attached file?
put single qoutes around your C:\ path like this 'C:\path\to\kernel\file'
When starting to type out a file name in the command prompt, pressing the TAB key will try to fill in the title. It ensures that you've got quotes around everything too if needed.
Like if I wanted to list the C:\Program Files folder, I'd type "dir C:\progr" and hit tab after going that far. It'll fill in what it can. Just keep typing to help it along as you press tab.
I copied and pasted what the instructions said about the kernel my CMD directory isn't c temp its c users (computer name)
Sent from my PC36100 using XDA Premium App
blackroseimmortal09 said:
I copied and pasted what the instructions said about the kernel my CMD directory isn't c temp its c users (computer name)
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
OK, let's try it this way. I packed you all the files of the Tiamat 1.3.1 into an archive that does not create subdirectories. Please follow the steps below:
connect the Xoom
create a directory on C: called "temp"
extract all files from the archive found here to c:\temp\
Start cmd (command prompt)
Simply copy and paste the next steps, line by line:
Code:
cd C:\temp\
adb shell
mkdir /data/media/sdcard2
exit
adb reboot bootloader
(wait until Motorola logo shows)
Code:
fastboot flash boot boot.img
fastboot reboot
(wait for reboot)
Code:
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
Please let me know if that works for ya!
Never mind root my xoom got updated with the latest tiamat kernel with SD card support thanks anyways
Sent from my PC36100 using XDA Premium App

HTC One X Root Assistance

Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
check pm
beaups said:
check pm
Click to expand...
Click to collapse
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
smartnphone said:
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
Click to expand...
Click to collapse
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
abhipati said:
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
smartnphone said:
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
Click to expand...
Click to collapse
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.
A cool username said:
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.
Click to expand...
Click to collapse
Thanks. Yeah i've been trying it alld ay but it can't find where my SU is. it's in the same location as the ADB stuff i believe C:\android-sdk-windows. Seem like some of the senior members are willing to go through teamviewer to help the ones who can't do it. I'll try asking them :/
Sorry I couldn't be of any help, but please let me know if/how you get this to work just in case this happens to me when I get my one x.
Sent from my Touch Pro 2 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
I wonder if the one who actually started this thread got his/her phone to work...???
Sent from my Touch Pro 2 using xda app-developers app
Someone think they can help me root the phone? I'm on 1.85 and I believe I finally got adb to recognize my device but after that I don't think I'm doing it right
Sent from my SGH-I777 using XDA Premium App

S-off help - "cannot stat soffbin3"

So I was performing the Facepalm S-off method and ran into this when I got the push soffbin3 step
-------------------------------------------------
adb push soffbin3 /data/local/tmp
"cannot stat 'soffbin3': No such file or directory"
-------------------------------------------------------------------------
Any idea what that means or what to do from here?
Did you put the file in the folder that contains adb (most likely your platform-tools folder) or change directory to that folder?
panda_mode said:
Did you put the file in the folder that contains adb (most likely your platform-tools folder) or change directory to that folder?
Click to expand...
Click to collapse
yep. the soffbin3.zip file is there.
Do I have to extract it?
Yup you have to extract it lol
panda_mode said:
Yup you have to extract it lol
Click to expand...
Click to collapse
haha!
<----noob
no dice though... I'm still S-ON :/
Did you get the 99 error instead of the 92?
panda_mode said:
Did you get the 99 error instead of the 92?
Click to expand...
Click to collapse
First off - got it work. I'm showing S-off now! :arty::
Yep, had the 99 error. So I rebooted into recovery, wiped cache and dalvik cache - then did a hard power off. Powered on into bootloader.
Then repeated all the steps and got the 92 this time.
The reason why it failed the first time was because I forgot to grant adb su access. Second time around I caught it and granted the permissions request but only on third command of "adb shell su -c...etc"
Does the second command "adb shell chmod 744...etc" need su access to perform correctly? What does that command do anyway.
I'm wondering if the second command needed su, I may have messed something up that won't rear its ugly head until I stumble on it.
I checked the log for su requests and adb only popped up once, which means the "adb shell su -c..." is the only one that needed.
I think I'm in the clear!
To be honest I'm not sure what it does either lol. But I do know the command: adb shell su -c "/data/local/tmp/soffbin3" will contact SU and you have to grant access. Glad you got it, though!

adb no such file or directory

I am trying to replace my digitizer firmware so G01 will work in place of the 5185FC I replaced.
I was following a guide which told me to type this in:
$adb push 02-3011-4820.ekt /sdcard/
$adb push 02-3011-4820.ekt /sdcard/
$adb shell
$su
#touch_fw_update command -u /sdcard/02-3011-4820.ekt
Click to expand...
Click to collapse
every time I try to push the new touch firmware I get this
"cannot stat '02-3011-4820.ekt': No such file or directory"
adb detects my device, I havea all the naked drivers, Android studio and JDK 64bit installed.... what else do I need to do?
I'm just wondering what I can do to fix this and get my touchscreen working once and for all!
Thank you so much in advance
And you are in the folder where you have put the file you want to push?
Changed the directory in the command prompt to the correct folder?
edit: ok, if it's linux, not the command prompt, but the shell...
compact_wisdom said:
And you are in the folder where you have put the file you want to push?
Changed the directory in the command prompt to the correct folder?
edit: ok, if it's linux, not the command prompt, but the shell...
Click to expand...
Click to collapse
I put the file on the root if the sdcard. Or should i be putting it in the directory of minimaladb/fastboot?
How do i change the directory in the command prompt?
Im using Windows 7 by the way.
hkp2 said:
I put the file on the root if the sdcard. Or should i be putting it in the directory of minimaladb/fastboot?
How do i change the directory in the command prompt?
Im using Windows 7 by the way.
Click to expand...
Click to collapse
Here is the command you are using to push
Code:
adb push 02-3011-4820.ekt /sdcard/
Maybe try this instead .....
Code:
adb push 02-3011-4820.ekt /sdcard
You can change directory with this
Code:
cd
and you can list files once in adb shell like this
Code:
ls
Thx Josh
I wasn't sure what I should cd to. I also tried ls but wasn't sure what to do from there.
I did look at the tutorial for adb and pushed the file into /sdcard/ from my laptop. It seemed to be successful because this is the message I got
943 KB/s <32868 bytes in 0.034s>
Click to expand...
Click to collapse
I proceed to type in the following
adb shell
su
touch_fw_update command -u /sdcard/02-3011-4820.ekt
Click to expand...
Click to collapse
And that's where I'm stuck with a message
sh: touch_fw_update: not found
Click to expand...
Click to collapse
It seems like I'm at least moving forward a couple steps so that's good.
hkp2 said:
I wasn't sure what I should cd to. I also tried ls but wasn't sure what to do from there.
I did look at the tutorial for adb and pushed the file into /sdcard/ from my laptop. It seemed to be successful because this is the message I got
I proceed to type in the following
And that's where I'm stuck with a message
it seems like I'm at least moving forward a couple steps so that's good.
Click to expand...
Click to collapse
Where is this command coming from, a guide or somewhere like that ?
Code:
touch_fw_update command -u
Thx Josh
This guide
snart[dotcom]/replacing-tf300t-digitizer/
Click to expand...
Click to collapse
I'm getting the adb tutorial from here
http://forum.xda-developers.com/showthread.php?t=2266638
Click to expand...
Click to collapse

Categories

Resources