[Q] some questions - HTC Sensation

I hope you can help me with those questions please
I'm getting familiar with the Terminal commands, and had some questions
- Where could I get flash_image binary file?
- When I get into recovery and use adb shell, I can't use any commands such as the ones when booted. It seems that the emulator isn't pointing to the bin directory (it is pointing to the sbin). I tried using cd /system/bin/ doesn't work either. What am I missing?
- What is the use of mount system,data,cache and so on in the recovery? Are those alternatives to "mount" in terminal? I can't understand how to use it either. xD
Thank You

Great xD
Sent from my HTC Sensation Z710e using XDA App

Related

command to install apk

Is there a command that can be used in a terminal emulator on the hero to install an apk from the sdcard? If not can it be done using adb commands? I am trying one of the froyo roms and before I start installing anything through the market, I would like to install a file manager. I have AndExplorer in an apk on the sdcard but I can only access it through adb or a terminal emulator.
Just adb push it to systen/app or you could install appinstaller from the market.
Sent from my HERO200 using XDA App
Open terminal.apk and issue these commands hitting enter after each line.
su
cd /sdcard
cp "app.apk" /data/app
This should do the trick. I don't think it will work with a2sd but I could be wrong. I tested it out just a few minutes ago and it worked great.
Sent from my Heroic using XDA App
mbobino said:
Open terminal.apk and issue these commands hitting enter after each line.
su
cd /sdcard
cp "app.apk" /data/app
This should do the trick. I don't think it will work with a2sd but I could be wrong. I tested it out just a few minutes ago and it worked great.
Sent from my Heroic using XDA App
Click to expand...
Click to collapse
Worked great, thank you for the tip

[Q]Custom Recovery Help

I need help installing a custom recovery. I believe my stock recovery is corrupt or somehow deleted. I have tried looking in multiple forums, but they had no help but using adb or fresh kitchen. Neither of those work, Fresh Kitchen comes up with an error and adb shows this
Code:
C:/android-sdk-windows/tools>adb shell
$ su
su
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
flash_image: not found
Can someone please tell me how to fix this, I want 2.2 badly.
MobileSWord said:
I need help installing a custom recovery. I believe my stock recovery is corrupt or somehow deleted. I have tried looking in multiple forums, but they had no help but using adb or fresh kitchen. Neither of those work, Fresh Kitchen comes up with an error and adb shows this
Code:
C:/android-sdk-windows/tools>adb shell
$ su
su
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
flash_image: not found
Can someone please tell me how to fix this, I want 2.2 badly.
Click to expand...
Click to collapse
well first off i would post this in the right section. Seeing as you actually made the CHECK to say this thread is a question shows you knew it was a question. Look at the sticky that at the toop of this page. POST QUESTIONS IN THERE RIGHT SECTION...Q&A!
my suggestion would to try and do unrevoked or the 1 click apk for hero(or universal androot). those should install a recovery for ya.
i have attached 2 of them but you can go to unrevoked.com and do it there.
My personal favourite way to do it is using the one click root, then flashing a recovery with rom manager (clockwork)
Sent from my HERO200 using XDA App

[DEV][WIP][TOOL] One-click root

I have no idea why there's no tool for that yet, so I decided to make one myself, but I need your feedback to make it good for everyone. So, my current goals are:
1) As simple as possible, all required files should be packaged with the app or downloaded dynamically
2) Cross-platform compatibility (Windows, Linux, Mac)
3) Minimal user interaction, as automated as possible
I see two solutions:
* X11-less console Linux LiveCD image to be booted in VirtualBox or on real hardware.
Pros: completely controlled environment, no drivers required, bash scripting, all libs and binaries bundled.
Cons: large image size, sometimes difficult to use, no GUI so less user friendly
* GUI Qt app
Pros: flexible language (C++), nice GUI, simple to use, allows for small size and on-the-fly downloads
Cons: have to compile and test separately on 3 platforms, different libs/binaries, Linux dependency hell, probably no Mac support because I don't have one.
So, what do you guys say? I'm open for ideas now and won't start coding until Monday.
I only joined the android world a little while ago when the moto olympus/atrix came out but isn't getting root on this as easy as
a)make sure you have a microSd card inserted
b)make sure unknown sources is enabled
c)install the gingerbreak apk, openeng the app and clicking on "root device"?
I'm no developer and haven't a clue what it takes but this would be epic.
Windows GUI
Sent from my HTC Vision using XDA Premium App
Vigneshd said:
I only joined the android world a little while ago when the moto olympus/atrix came out but isn't getting root on this as easy as
a)make sure you have a microSd card inserted
b)make sure unknown sources is enabled
c)install the gingerbreak apk, openeng the app and clicking on "root device"?
Click to expand...
Click to collapse
Okay, I meant root+blob+CWM
Sent from my HTC Desire using XDA Premium App
smellmyfingers said:
I'm no developer and haven't a clue what it takes but this would be epic.
Windows GUI
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Still think a livecd could be the best way... A GUI app can only come if you guys help me with the testing.
Sent from my HTC Desire using XDA Premium App
K900 said:
Still think a livecd could be the best way... A GUI app can only come if you guys help me with the testing.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
I don't even know what these "blob" things are yet.But if you need testers, thats what the rest of us here are for. Count me in.
Hmm... I wonder how a plugin system could work... So, a core library that handles adb, device identification and plugin loading, plugins dynamically linked to the library (needs a stable API though) and a manifest that lists compatible devices and plugins to be used for them... Could be something like that (YAML inspired);
device:
info:
vendor: 'ASUS'
model: 'Eee Pad Transformer'
pciid:
uses:
- gingerbreak
- tf101
And libgingerbreak.so to push and run gingerbreak (a generic one) and then a device specific libtf101.so to take care of blob flashing action.
P.S. It's night here and I'm tired as hell. Sorry if I wrote some nonsense... If anyone is interested in making it big, PM me here or on github.
Sent from my HTC Desire using XDA Premium App
K900 said:
Still think a livecd could be the best way... A GUI app can only come if you guys help me with the testing.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
ttav said:
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
Click to expand...
Click to collapse
Yeah, that's just the thing. What's good about a livecd is that you are 100% sure it works everywhere, cause nothing changes. But if you make it native, you need drivers on Windows, udev rules or root privileges on Linux and a Mac to make it run on a Mac...
Sent from my HTC Desire using XDA Premium App
K900 said:
Yeah, that's just the thing. What's good about a livecd is that you are 100% sure it works everywhere, cause nothing changes. But if you make it native, you need drivers on Windows, udev rules or root privileges on Linux and a Mac to make it run on a Mac...
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
To make it simple isn`t going to be easy I`ll say it again best of luck.
ttav said:
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
Click to expand...
Click to collapse
Yup essentially like one-click rooting app for the Galaxy phones.
It is ***UHHH... get the software and d/l on the computer.....ummm.... click to open
Click the flashing neon sign that SAYS: "click here dummy !!" ...........you are rooted...........
Anything you coud put together would be an absolute god send. I managed to root my X10 okay, and my other half's Vega..... but the guides for the transforemer may as well be in mandarin for all I understand them. I really need a click here, install this, type that, press this, turn round three times and throw salt over your shoulder sort of guide..... or any of your lovely proposed one click solutions
The best I have is a pair of batch files that go through the pre and post root process that I've modded with directions. This assumes you have ADB setup from the Android SDK install and have the ADB drivers installed and working. You need to have USB Debugging enabled via Settings > Applications > Development. If you do not, get the Android SDK and read up on how to setup ADB. There's tons of posts on XDA about how to do just that.
Download tf101-root.zip here
md5: 57f22712625fe75f685499b60b189aa8
Firstly, run root-prep.bat from where ever you extracted tf1010-root.zip (preferably in your platform tools folder for your Android SDK install).
This is the batch file content of the root-prep.bat:
Code:
adb push gingerbreakBB /data/local/
adb shell chmod 777 /data/local/gingerbreakBB
adb push CWM_BLOB_V5 /data/local/
@echo off
echo Now do "adb shell" from another command window. In the shell, do "/data/local/gingerbreakBB" without quotes. DO NOT CLOSE THAT COMMAND WINDOW, EXIT THE SHELL, OR REBOOT AFTER GINGERBREAK IS DONE! THE ROOTING PROCESS MAY WIPE YOUR SD CARD SO BACK IT UP BEFOREHAND!
pause
Go to your Android SDK folder in explorer and (if you're on Vista/7) shift+right-click the platform tools folder and click "open command window here" for a new command window already set to that folder. XP users will have to do it manually or download the PowerToy from this page. Download the "Open Command Window Here" tool and it works exactly the same as on Vista/7. GINGERBREAK MAY OR MAY NOT WIPE YOUR SD CARD SO BACK IT UP BEFORE DOING IT JUST IN CASE!
Rooting process:
Code:
C:\aSDK\platform-tools>adb shell
$/data/local/gingerbreakBB
<you'll see all the gingerbreak stuff here>
#
DO NOT CLOSE THIS COMMAND WINDOW AND DO NOT EXIT THE SHELL WHEN IT'S DONE! If you don't get the # symbol in the shell after running gingerbreak, you'll have to run the root-fail-fix.bat then do the above again after the reboot.
This is the batch file content of the root-fail-fix.bat:
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb reboot
If you get the # symbol after gingerbreak is done, run post-root.bat from the same command window as you did root-prep.bat or a new command window. After the reboot you should be fully rooted!
This is the batch file content of the post-root.bat:
Code:
adb remount
adb shell dd if=/data/local/CWM_BLOB_V5 of=/dev/block/mmcblk0p4
adb push su /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/su
adb shell chmod 6755 /system/xbin/busybox
adb push Superuser.apk /system/app/
adb reboot
You can do the commands manually just to make sure everything works properly (encouraged) or just run the batch files from a command window if you're lazy.
ttav said:
A livecd would probably be too complicated for people who can`t follow the rooting guide.What you need is a program to download on to computer.....in large red letters...connect Transformer to pc.....click obvious button.....rooted
Click to expand...
Click to collapse
That would be a godsend
I can appreciate how many would look at the rooting guide and say "WTF?" Think about it, unless you are command line savvy, the process can be daunting. Not including the linux users we have a generation (or two) who never had the "pleasure" of running DOS so they have not had the experience of a flashing cursor just waiting for the human to tell it EXACTLY what you want in PRECISE commands.
Ahhh...the good old days. (kidding....really...or so says my pet rock...with the mood ring)
Guess I'll hack together windows batch and linux shell scripts tomorrow and start working on the app later, cause I have no free time now.
Sent from my HTC Desire using XDA Premium App
have talked to the guy in Xoom section that created the various 1-Click Root proggies. Check them out here . Maybe he can give you a hand or some suggestions
Here are the threads
http://forum.xda-developers.com/showthread.php?t=1093126
http://forum.xda-developers.com/showthread.php?t=1011196
I am for whatever, even livecd is easier for you to make.
I think it is less work and with simple instruction it allways works.
Sent from my HTC Desire using XDA Premium App
I think with the key now out and the ability to modify any Asus TF ROM it might be wise to wait and make something that works with NVFlash? But I don't know a lot about this stuff so ignore me if you think I am an idiot
I vote for a GUI QT App. The point of One Click Root is to make rooting as painless as possible. A live CD doesn't seem to follow that...

[Q] adb command fails

I have successfully rooted my HTC Wildfire S but now I am trying to reinstall HTC Mail after deleting it in error!
I am using the adb command to copy files from my sd card to the system folder on the ROM e.g. adb push/sdcard/Mail.* /system/app. However, when I press the enter key I just get a list of the adb commands and switches and it doesn't copy the files across.
Any ideas as to why this may be happening? My Android Debug version is 1.0.26
If I could just download the HTC Mail app and install as usual that would of course be preferable but I think it's only available as a factory install. I've tried the K9 mail app but I have a feeling there is a connection timeout bug that means it doesn't disconnect from the POP mail server for ages after it's 'pulled' messages. I've had many senders complain they have message failed errors when they try to send to me but they haven't had them since I uninstalled K9 and started using HTC Mail. And in case you're wondering, I started using K9 because the old version of HTC mail would not save my SMTP settings but the new version is OK.
Thanks for any help.
Marnhullman said:
Any ideas as to why this may be happening?
Click to expand...
Click to collapse
Looks like you've used the wrong command.
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
Obviously swap framework-res for your apps name.
adb command fails
Thanks XperienceD. Will try your syntax later.
adb command fails
XperienceD
The syntax you suggest is not compatible with the adb I'm running i.e. dd is not a vaild switch. I'm trying to use adb to reinstall an app to an HTC Wildfire S.
From what I've read elsewhere the syntax I used should work but doesn't...
Marnhullman said:
XperienceD
The syntax you suggest is not compatible with the adb I'm running i.e. dd is not a vaild switch. I'm trying to use adb to reinstall an app to an HTC Wildfire S.
From what I've read elsewhere the syntax I used should work but doesn't...
Click to expand...
Click to collapse
Did you start by mounting the system - adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system ?

[Q] MMS Fix for KitKatDS 1.3. Help a Noob Plz

Hi. As title says I need a fix for KitKatDS rom. I tried to post in that thread but it won't let me. I saw this fix in the thread but I don't know where you do this or if it works:
FYI - found a fix. If anyone is having issues sending/receiving MMS, do this:
(load up adb shell)
su
mount -o rw,remount /system
rm /system/bin/ip
ln -s /system/xbin/ip /system/bin/ip
IP on /bin errors out so the device is unable to route a connection to the MMS servers. the IP in /xbin works just fine
Can someone give a noob a walkthrough of how to do this? Thanks
Set up adb on PC and turn debugging on on phone, if you aren't sure how to do this a quick Google search will give you many guides.
Once this is working open a terminal/cmd and type
adb devices
If you a see a serial number than you are good, if not see the guide on setting up adb or ask question here if still stuck
Once all is working type
adb shell
Then type the exact commands you linked from above
Now for safe measure type
exit
adb reboot
You should be good (granted I'm not using this ROM currently and have not needed to attempt this fix, but looking at it, it makes sense and could work. Having said that always make a backup of current ROM in recovery before trying new things you don't fully understand)
Best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
As I mentioned in the KK thread itself, I was able to run the fix without having to PC attach and adb shell. Just used the included terminal program with SU permissions, and the fix has held since day 1. I've sent & received plenty of MMS messages.

Categories

Resources