Database Info

[Q] Shell on transformer

Hello everybody,
I'm stuck with a big problem. I downloaded and installed bash on my transformer and mv /system/bin/sh to sh0 and linked sh > bash as described in a thread on this website.Then I changed the bash file with an other bash version and that didn't work. Well, that's not a problem because my transformer was rooted at the time. Next day I got the automatic update to the newest version and my transformer was not rooted anymore. No I can't change any system files anymore to fix the shell. This also means I can't root anymore with adb because it gives an error that it can find 'sh', because it's linked. Is there a way to change the system files without rooting? Or do I have to flash to stock? I tried factory reset but that didn't change nothing.
The error I get when doing "./adb shell" is "- exec '/system/bin/sh' failed: No such file or directory (2) -"
Thanx for any help.
Dave

You really need to root your Transformer first. If it were possible to change system files without root then there would be no point to the root privilege.
I think it should still be possible to root your Transformer again, depending on the serial number. I have a B70 and I managed to regain root in short order after accidentally pushing the button for the OTA upgrade to .21 two weeks ago.
One other thing... My Transformer is rooted, but I seem to have lost bash after the 8.6.5.21 update. I use the shell a lot and have gotten used to bash after years on GNU/Linux. How does one get it back?

stormwyrm said:
You really need to root your Transformer first. If it were possible to change system files without root then there would be no point to the root privilege.
I think it should still be possible to root your Transformer again, depending on the serial number. I have a B70 and I managed to regain root in short order after accidentally pushing the button for the OTA upgrade to .21 two weeks ago.
One other thing... My Transformer is rooted, but I seem to have lost bash after the 8.6.5.21 update. I use the shell a lot and have gotten used to bash after years on GNU/Linux. How does one get it back?
Click to expand...
Click to collapse
But rooting is gonna be a problem when I can't use 'adb' commands.
I tried rooting allready and everytime it gives an error about not being able to find the shell. This is offcourse normal because the rooting script can't acces the shell since I linked it to a bash version that is not working...;-)
I use bash also on linux, since that's the only system I have on all my desktops/laptop.From my linux experience since 1996 I know that you can't change systemfiles when you're not root but I was hoping that the Transformer or android had some trick/secret.
That leaves me then with flashing to the stock rom?
Because the factory reset also didn't do the trick...
This thread is about installing bash on android: http://forum.xda-developers.com/showthread.php?t=537827
thanx

Could also just buy BTEP, as far as getting bash is concerned and you shoukd generally not screw with the systems she, as opposed to installing bash as bash.
If you had CWM you could make anbuodate file to flash, I'm sure.
When ICS comes, it should be root able unless the method used currently gets fixed, rooting the Prime in 4.0.3 is a snap (but does requirebadb).
If you can use nvflash, there is always a way out.
Sent from my Transformer Prime TF201 using Tapatalk

^This.
I've been using Better Terminal Emulator Pro (BTEP) since I got my OG Droid 2 years ago, I love it. It sounds like you need to nvflash to flash a clean rom and then re-root.

In Terminal Emulator you can specify the shell command. Can you not change this to /system/bin/sh0 en try to start the original sh ?

Any update to this? I have the exact same issue. Where can I get the original TF201 rom?

NEW 2.3.4 MT4G Downgrade Instructions...

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

[Q] Can't root after complete reset yestrday

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

Is there another way to root ICS 9.2.2.3 ?

Is there already a method on the root 9.2.2.3 ?

aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
Perhaps downgrade your ROM to an earlier version. Someone has done it with HC.
http://forum.xda-developers.com/showthread.php?t=1400532
[Edit] Ignore me. Apparently you cannot go back to a lower version number.

Bump
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse

aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470

TNS201 said:
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
Click to expand...
Click to collapse
It has been patched up with this update

wolf849 said:
It has been patched up with this update
Click to expand...
Click to collapse
confirmed

if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302

chadster214 said:
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
Click to expand...
Click to collapse
Problem is that 9.2.2.3 update came for tf101g and that means SBK3 device, therefore root by nvflash will not make the trick...
P.S. As far as we are talking about 3g devices

Is it possible to flash recovery.img on device via adb ? (Fastboot) Then boot into CWM and flash a rooted rom ?
Sent from my GT-I9100 using XDA

Nick502 said:
Is it possible to flash recovery.img on device via adb ? (Fastboot)
Click to expand...
Click to collapse
The bootloader does support the fastboot protocol (and some obscure methods of booting a kernel via JTAG), but it's locked down to the point that you can't even get fastboot to recognize the device.
So no luck there

ViperMod is your answer I believe
I've not had to root since any version of ICS, but many are have success with ViperMod: http://forum.xda-developers.com/showthread.php?p=21009605
You might have to drop back to a 9.2.2.17 or 19 but there are lots of roms out there that are still on that version. I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.

chadcspencer said:
I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
Click to expand...
Click to collapse
It doesn't work

I tried with my TFT101G build 9.2.2.3 but didn't work!

OK, so to sum it up:
1. SUID /proc/<pid>/mem write has been patched in this release (aka 9.2.2.3) therefore mempodroid exploit and basing on it viperMod is useless
2. qEmu vulnerability in /data/local.prop is also patched up so TPsparkyroot will also fail.
3. The location of backed up files and temp storage have been shifted out from data therefore all rooting tools connected with ASUS backup app will not do the trick.
4. Jumping back to previous software is unachievable without root.
So I ask you to post ONLY methods that are not listed above.
(However I think that we have to wait for next linux Local Privilage Escalation bug to be discovered in order to get rooted)
Cheers
P.S. Sorry for any mistakes English is not my native.

ICS 9.9.23G
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?

thunderman98 said:
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
Click to expand...
Click to collapse
OTA is only for TF101G. You can install firmware pack from ASUS website through custom recovery, but I do not see any point of doing that.

Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance

hearts king101 said:
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
Click to expand...
Click to collapse
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.

wolf849 said:
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
Click to expand...
Click to collapse
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits

sbiriguda said:
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
Click to expand...
Click to collapse
Unfortunately I've tried that and than I came to a conclusion that 'ro.kernel.qemu=' has been shifted... Try read build.prop on /system and you will find it there, so /data write does nothing for now
EDIT:
Nonetheless, I have rw access to /cache where dlpkgfile is held, so maybe it is possible to do a downgrade of firmware through that hole.
EDIT2:
BTW, I did it by flashing TW 9.2.2.3 firmware on to WW 9.2.2.3 through EP101_SDUPDATE (or similar).
Than:
adb mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /cache /data/local/tmp
adb rebbot
After that /data becomes readwrite
EDIT3:
There is also one more question: where is held /tmp partition needed to repack the blob maybe by accessing it and pushing blob we can manually force its update.

[UPDATE] OTA 9.2.1.21 US - CWM flashable

This applies the 9.2.1.21 US ota update. It will install Superuser and the su and busybox binaries; and set ro.secure=0. It does not modify recovery at all.
As usual, flash at your own risk- I didn't test this.
To flash, you need:
a non-stock recovery
a stock system, rooted is OK
custom kernels, deleted system files, modified build.props or audio files will FAIL.
Good luck!
edit: new url! Find it in the OTA section.
http://www.xdafileserver.nl/geeone/
MD5(gee_one-cwm-9.2.1.21-US.zip)= 30bf3ad60698d41793d992823e942076
I made this with Ubuntu!
Thanks to doaist for paving the way! and thanks to Korumera for the server space!
Edit:
It seems like some people will "lose" root in titanium backup because it looks for the su binary in /system/bin instead of /system/xbin (X!). See post 19 and 20 for how to get it back. I don't use titanium backup very often, so I'm not familiar with it.

I get a status 7 installation aborted error when trying to flash on the stock rom thats rooted no mods.

Thanks
Worked fine on my TF101 US....
Hope it fixes some of the battery issues I've been seeing with .17

Hmmmm.............strange it didnt for me and Im on the stock ICS rom ver .17 currently.

I'm not sure what status 7 is. How much free space do you have? I don't remember the number but the patch does check free space before flashing.
sent while running with scissors

Ive got 20gigs of free space Im using Rogue Recovery............not sure if that makes a difference.......

20 gbs on the sdcard? I think it checks internal memory, or maybe you have a 32gb transformer?
sent while running with scissors

Error Im getting:
Verifying current system....
assert failed: apply_patch_check("/system/lib/modules/battery_rvsd.ko", "66c516b01d95c36310cc3e7ee7771b32ed5cb823",
E: Error in/sdcard/gee_one-cwm-9.2.1.21-US_30bf3ad606.zip
(Status 7)
Installation aborted.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
Ive got a 32gb transformer with a 32gb microsd card.

For whatever reason, your battery kernel module is different? Maybe you changed it while sleeping or maybe the 32gb version uses a different one.
The US firmware is available on the asus site, so you could just download it, extract the offending file, and push it to your transformer. It will be the 92121 version, but the updater will just skip it since it matches the target.
sent while running with scissors

Could it be because Im not using a stock kernel?

y2kardell said:
Could it be because Im not using a stock kernel?
Click to expand...
Click to collapse
Bingo- see the note about FAIL in the first post. You'll want to flash back to a stock kernel to apply the update, or more likely, just flash a full custom rom and a new modded kernel.
sent from my transformer

I no longer have root after I flashed this.
Any suggestions?

kdog78 said:
I no longer have root after I flashed this.
Any suggestions?
Click to expand...
Click to collapse
are you sure you flashed my version and not the other one?
type in "ls -l /system/xbin/su" and "getprop ro.secure" in the terminal and see what pops up.

Ok, I tested this on my TF and it works for me, your experience may differ.
Try updating Superuser and the su binary in superuser. Maybe I have an updated version on /data/app?
sent from my transformer

I flashed this and after I click reboot system now it just gets stuck at CWM.
I'm using CWM v3.2.0.1 by roach2010
Tried clearing cache, it still gets stuck in CWM. Help?

wzseow said:
I flashed this and after I click reboot system now it just gets stuck at CWM.
I'm using CWM v3.2.0.1 by roach2010
Tried clearing cache, it still gets stuck in CWM. Help?
Click to expand...
Click to collapse
That is a recovery issue - there is a trouble shooting thread in the dev section.
sent from my transformer

gee one said:
are you sure you flashed my version and not the other one?
type in "ls -l /system/xbin/su" and "getprop ro.secure" in the terminal and see what pops up.
Click to expand...
Click to collapse
It had a 0.
Sent from my Transformer TF101 using Tapatalk 2

can anyone advice on how to get this to flash on a system with a custom kernel? i can't seem to get it to flash with error 7
Sent from my Transformer TF101 using Tapatalk 2

kdog78 said:
It had a 0.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Sorry to answer your earlier question, yes I used yours. I didn't know there was another. Here are two screen shots.
Sent from my Transformer TF101 using Tapatalk 2

It looks like you have 2 su binaries, and the one ti backup is looking for isn't superuser executable.
Try ls -l /system/*bin/su and this time use the -l flag to check the permissions. The bin/su will be normal, but the xbin one should be rws....
Try this in terminal
/system/xbin/su
mount -o remount,rw /system
chmod 06755 /system/bin/su
mount -o remount,ro /system
Exit...exit...
Then try getting root in tibu. I don't use it, so I'm not terrible familiar. You might also try updating the su binary via superuser apk.
sent while running with scissors