first of all iv been trying to root my legend for hours and this is geting very furstarting... i am using the guide here http://forum.xda-developers.com/showthread.php?t=845512
i have finaly managed to get adb to work and have made my goldcard after 2 days of intense work and now im trying to downgrade my phone to root it
i am geting the following error in adb
when i type adb remount it says remount failed operation not permitted i have looked all over the net and found no answer
in additon to that when im trying to use adb push i type the following
adb shell
$su
su
#adb push flash_image /data/local/
adb push flash_image /data/local/
i just get the same line repeated how to excute commands from adb? this is very confusing since im noob with rooting also the following lines i don't know how to excute them too
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
chmod 755 /data/local/flash_image
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
/data/local/flash_image misc /data/local/misc1-2.img
please explain to me how to use theese thanks!
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Click to expand...
Click to collapse
Read better, you have to open a new terminal for pushing the files to the phone, you can't use adb push while you are in adb shell.
BTW you should avoid posting questions in development section.
Related
anyone kind enough to make a complete step by step noob guide on rooting, installing the SU and custom boot.img..... cause im lost in installing the SU and the custom boot img....thanks in advance for the guide.....
see here
http://www.androidworld.it/wiki/Root_HTC_Tattoo
can it be in english???
shazarul said:
can it be in english???
Click to expand...
Click to collapse
Hi,
see #237 post of the page 24 of this thread for what you want:
http://forum.xda-developers.com/showthread.php?t=635961
You need to collect the files: m7 at page 1, tattoo-hack.ko at page 23, and su at page 23. Just follow the sequence of #237.
Note that if you haven't pushed "su" to /data/local/bin, you can only execute the
Code:
while do /data/local/bin/m7 ; done
for first rooting, otherwise
Code:
/data/local/bin/su
At the first time to root it, you need to push the files to /data/local/bin, like:
Code:
----------- Your machine ----------------------------
adb push m7 /data/local/bin
adb push tattoo-hack.ko /data/local/bin
----------- Android Shell ----------------------------
adb shell
chmod 755 /data/local/bin/m7
while do /data/local/bin/m7 ; done
(find your first character of shell changing from $ to #, got root already.)
----------- Your machine ----------------------------
adb push su /data/local/bin/su
adb push su /sdcard
----------- Android Shell ----------------------------
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
mount -o rw,remount /dev/block/mtdblock3 /data
chown root.root /data/local/bin/su
chmod 4755 /data/local/bin/su
(and run the #237 procedure from step 7, insmod tattoo-hack.ko ......)
After the first time rooting, you can just type "su" to enter root again. If not, you need to do the #237 procedure from step 1 to last.
thanks guys for the help.....finally root my fone.....
I have Sprint signed 2.0 ruu and I have the phone rooted successfully.
My problem is this, when I try to flash the recovery image it says "file not found"
I've tried flashing from terminal on phone and from CMD on pc.
I have searched and searched with no luck.
please anyone help. Also how to use nand Restore what is the file that is being restored.
Also how to add removed apps from DC 2.0.72 rom step by step please.
Thanks
make sure debugging is turned on in the phone
settings>applications>development>usb debugging
Here is a guide that you can try
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
or try these instructions
http://forum.xda-developers.com/showthread.php?t=583291
Theres some others you can do, but its a males it more difficult after doing the 2.1 RUU
Thanks for the reply
Still showing flash image not found
I tried those websites with no luck!! Does this not work after installing the 2.1 ruu?
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image: not found
# [1] Killed su
# exit
exit
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found
# exit
exit
# adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb: not found
#
joshuadb20 said:
I tried those websites with no luck!! Does this not work after installing the 2.1 ruu?
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image: not found
# [1] Killed su
# exit
exit
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found
# exit
exit
# adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb: not found
#
Click to expand...
Click to collapse
No that will not work. pm me and I will fix it with you on gtalk.
Since you ran the test ruu you do not have flash_image on your phone. You need to push flash_image to /system/bin/flash_image. I will attach it as a .zip below. Put the .zip in your sdk folder then follow these adb instructions to rename and push it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
Be sure to type it as above to correctly rename it..it is not really a .zip but XDA forces the rename to attach..
You have to give flash_image permission now, so type this:
Code:
adb remount
adb shell chmod 0755 /system/bin/flash_image
Now you should be able to flash the custom recovery if you have indeed rooted your phone and gave permissions to flash_image.
Thankyou thankyou thankyou
I love you guys, This fixed my issue, it drove me nutts all night last night.
Thank you very much!!! Your posting solved my all day issue, im happy :-*
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image: not found
# adb remount
adb remount
adb: not found
#
I am having the same issue on my phone except I can't get the the flash_image file to even work. See above for example of my outcome. Am I not rooted fully? I am using universal androot and getting the Superuser icon and everything. Please help if you can. This is driving me crazy.
91nbtsi said:
...
# flash_image recovery recovery-ra-heroc-v1.2.3.img
...
Click to expand...
Click to collapse
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
kjjjjshab said:
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
Click to expand...
Click to collapse
I am pretty new to this, so it is case sensitive? I will try and see.
jeez guys. just plug your phone into your computer and drop the heroc-...img into your sdcard's root folder.
then:...\tools> adb shell
ls (to see what's in your current directory)
cd sdcard (to hop onto your sdcard)
su (if not already root)
flash_recovery recovery-.......3.img
reboot recovery
kjjjjshab said:
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
Click to expand...
Click to collapse
It is the command "flash_image" that is not found - not the img file
I have the same problem - but in posting it I see that everyone is looking at the error as though it relates to9 the img file
91nbtsi said:
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image: not found
# adb remount
adb remount
adb: not found
#
I am having the same issue on my phone except I can't get the the flash_image file to even work. See above for example of my outcome. Am I not rooted fully? I am using universal androot and getting the Superuser icon and everything. Please help if you can. This is driving me crazy.
Click to expand...
Click to collapse
Here is what you need to do
Code:
adb shell
cd sdcard
flash_image recovery xxxxxxxxxxxx.img
reboot recovery
You should not need to remount, but if you need to or for future reference you type in adb remount from the command prompt and not in adb shell
diogenesthesceptic said:
It is the command "flash_image" that is not found - not the img file
I have the same problem - but in posting it I see that everyone is looking at the error as though it relates to9 the img file
Click to expand...
Click to collapse
Read an earlier post, download the file and do what the post instructs. You need the flash_image file on your phone
danknee said:
Since you ran the test ruu you do not have flash_image on your phone. You need to push flash_image to /system/bin/flash_image. I will attach it as a .zip below. Put the .zip in your sdk folder then follow these adb instructions to rename and push it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
Be sure to type it as above to correctly rename it..it is not really a .zip but XDA forces the rename to attach..
You have to give flash_image permission now, so type this:
Code:
adb remount
adb shell chmod 0755 /system/bin/flash_image
Now you should be able to flash the custom recovery if you have indeed rooted your phone and gave permissions to flash_image.
Click to expand...
Click to collapse
Mine says "remount failed: Operation not permitted" when I try to remount.
LARPkitten said:
Mine says "remount failed: Operation not permitted" when I try to remount.
Click to expand...
Click to collapse
If you are in recovery and trying this you do not need to remount. If you are booted into Android try
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
you might also replace /dev/block/mtdblock3 with /dev/mtd/mtd1
and then chmod
I am having this problem as well.
Okay if your having a problem with the ole "flash_image not found" saying do this open up command prompt and type
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then open up another command prompt with the old one still running and type this
Code:
adb push flash_image /bin
adb shell chmod 0755 /system/bin/flash_image
Now you should be good to flash your recovery
Asadullah said:
Okay if your having a problem with the ole "flash_image not found" saying do this open up command prompt and type
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then open up another command prompt with the old one still running and type this
Code:
adb push flash_image /bin
adb shell chmod 0755 /system/bin/flash_image
Now you should be good to flash your recovery
Click to expand...
Click to collapse
I'm getting all the same errors everyone else on here is getting. Is flash_recovery a file that is required? I don't mean the .img file, but is it some kind of command file?
Ladies and Gents:
Please help me out.
I am trying to install a "Japanese IME" that sir JMaurice has kindly provided through one of the forums.
Did everything (I think) required in order to get my N1 connected and recognized by my laptop. Then used SuperOneClickv1.5.5-ShortFuse to gain root. Started on the IME installation and got the following.
>adb devices
List of devices attached
HTxxxPxxxxxx device
>adb kill-server
* server not running *
>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
>adb remount
remount failed: Operation not permitted
So I decided to confirm root.
>adb shell
$ su
su
# exit
exit
$ exit
exit
I couldn't start the "adb push" sequence due to the errors above. What am I doing wrong?
Did you reboot after executing SuperOneClick? Try that.
Jack_R1 said:
Did you reboot after executing SuperOneClick? Try that.
Click to expand...
Click to collapse
Believe I rebooted. Rebooted again just in case. Still gives me the following:
>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
>adb remount
remount failed: Operation not permitted
Weird, but already seen on the forum not a long time ago, I think. I'm not sure what can be done in this situation. "adb remount" can be easily substituted by shell commands, root shell you're still achieving by "su", but how to solve this - I have no idea. Might be permissions thing.
Jack_R1 said:
Weird, but already seen on the forum not a long time ago, I think. I'm not sure what can be done in this situation. "adb remount" can be easily substituted by shell commands, root shell you're still achieving by "su", but how to solve this - I have no idea. Might be permissions thing.
Click to expand...
Click to collapse
Thanks for your replies. Am searching the forums for a similar post; still no luck. Hopefully someone will chime in with an answer.
Thanks again.
You have root, you just don't have an insecure boot.img
Rusty! said:
You have root, you just don't have an insecure boot.img
Click to expand...
Click to collapse
Please clarify. Where possible, detailed explanation/instructions would be most appreciated.
You have root, that's all fine.
To use the command adb remount, you need an insecure bootloader, as you don't have this (due to using the stock boot.img) you have to mount /system as RW in a different way:
su
mount -o remount,rw /dev/mtdblock3 /system
Rusty! said:
You have root, that's all fine.
To use the command adb remount, you need an insecure bootloader, as you don't have this (due to using the stock boot.img) you have to mount /system as RW in a different way:
su
mount -o remount,rw /dev/mtdblock3 /system
Click to expand...
Click to collapse
What I am trying to achieve after adb remount is:
adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
adb push iWnnIME/libnjubase2.so /system/lib/
adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
adb install iWnnIME/iWnnIME.apk
This will actaully be the first time for me to use su. Could you confirm whether the following sequence of commands are correct?
>adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /data
# exit
$ exit
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
>adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Please let me know if I am missing anything.
Wrong. You don't need to remount data, it's always writeable, and the command is erroneous - you're mounting system partition and calling it "data". You need to just push the apps to /data, as shown below:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
> adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Jack_R1 said:
Wrong. You don't need to remount data, it's always writeable, and the command is erroneous - you're mounting system partition and calling it "data". You need to just push the apps to /data, as shown below:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
> adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Click to expand...
Click to collapse
I think I am starting to understand this. I punched in the first adb push sequence and got the following:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
push: iWnnIME/jp.co.omronsoft.iwnnime/dicset/master/njuserphone.a -> /data/data/dicset/master/njuserphone.a
failed to copy 'iWnnIME/jp.co.omronsoft.iwnnime/dicset/master/njuserphone.a' to '/data/data/dicset/master/njuserphone.a': No such file or directory
Checked in tools directory and the appropriate directory/file combination was there. Does this indicate that I have to create the appropriate directory in my phone?
Someone? Anyone?
Or is it possible to execute the same adb sequence in shell as su?
I must admit, I've never pushed more that a single file at a time over, given you appear to be trying to push an entire directory tree, perhaps you might be better off copying it over to the SD card in Windows, and using busybox to get it where you need it.
Exactly as Rusty suggested above me. Otherwise you need to create all the directories manually, through adb shell mkdir <your_directory_that_is_not_on_the_phone> .
I wanted to ask this in the actual thread but 10 post limit...
Anyway,
I can't get any GPS lock on my I9000, Onemsomic's ICS RC3.1, JVU modem.
I tried changing the NetworkLocation.apk by following this post http://forum.xda-developers.com/showthread.php?p=21351809#post21351809
but since I have absolutely no idea how to use ADB I couldn't do the "change mode to 0644" step.
Someone help a noob?
Thanks.
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
AurosGamma said:
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
Click to expand...
Click to collapse
I get a "device not found" error after adb remount. What should I do?
hadar.shamir said:
I get a "device not found" error after adb remount. What should I do?
Click to expand...
Click to collapse
Well I have been looking here and there, and I found that adb doesn't work directly on the phone, you must use adb from your pc. So, this is what you should do from now on:
Install Java SDK
Install Android SDK
Turn on "USB Debugging" in your SGS settings
Connect the Device to the PC
And finally, use the following commands (from the PC):
Code:
// Go to the folder where you put the *.apk
cd C:\users\exampleuser\Documents\ // or /home/exampleuser/Documents/ if you're using linux
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note:
The text after the double-slash ( // ), must not be written in the console, they are just comments
You need to install the SDK's because there it is where the adb tool (and tools needed by adb) is found, so, good luck!
Hi, I'm a newbie to android rooting and have spent the whole day trying to root my Kindle Fire HD v7.2.3.
I've used the bin4ry RunMe.bat and RootQemu.bat. I have no problems with the Qemu part but as for the RunMe.bat part I get permission problems (see picture below)
http://www.freeimagehosting.net/ikz64
The device gets rooted but the super user is no where to be seen. Therefore I can access root files but I can't write as it is read only.
I've already tried this: http://forum.xda-developers.com/showthread.php?t=2086210 (fixing a bug)
I've also tried the basics of rebooting after rooting, run as admin, locate through cmd but nothing has worked for me so far.
Anyone know what the problem is?
I was having a similar permission denied error when rooting 7.2.3. Try this and see if it helps. These commands are pulled from the Qemu script.
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
Wait for the device to reboot then run these.
Code:
adb shell rm /data/local.prop
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
reboot
Now wait for the device to reboot then check if the Qemu root hack worked correctly by connecting to your device with adb shell. You should see a root prompt.
Code:
$ adb shell
[email protected]:/ #
If you see a root prompt then re-run the RunMe.bat script and it should complete without error. The reason for your permission denied error is the script is not running as root.