Related
(Sorry for not posting actual links - the system won't let me because I'm still a "new user.")
I already rooted my Sprint Hero using this (thread 583291) guide and can successfully tether using the WiFi Tether app. Yay!
Now I want to delete and/or replace the boot up sound (boot.mp3 located in /system/media/bootscreen) When I try to delete it right now (either through adb shell on my computer or from within a file manager app on the phone itself) I get permission denied or "read-only file system."
I see two threads regarding busybox, superuser, and adb remount. Thread 591303 which is dated 11/28/09 and is just for busybox and Thread 593952 which is dated 12/03/09.
I'm not sure which of these two I need to install. If it's the latter which includes ADB remount and superuser as well as busybox, then I'm not sure if I am supposed to unzip them before pushing them to my phone.
Could anyone point me in the right direction based on what I want to do (delete files on my phone - ANY file I want)?
Thanks in advance for any help you can offer.
All you should need to do is:
Code:
adb remount
rm /insert file path/file
So yours would be
Code:
rm /system/media/bootscreen/boot.mp3
Mr. Biggz said:
All you should need to do is:
Code:
adb remount
rm /insert file path/file
So yours would be
Code:
rm /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
will rm work without busybox?
As long as you can shell into the phone it should work. The rm command is to be run inside the shell.
So it actually should be
Code:
adb remount
adb shell
rm /system/media/bootscreen/boot.mp3
You want to install the busybox remount and superuser Rom if you want to run stock.
Or manually install busybox, superuser whitelist and adb remount
Biggz - looks like they are on stock. No adb remount.
gbhil said:
Biggz - looks like they are on stock. No adb remount.
Click to expand...
Click to collapse
Unfortunate, custom is so much better.
If you are on stock, do this:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mv /system/media/bootscreen/boot.mp3 /system/media/bootscreen/boot.mp3.old
exit
[you can also do rm /system/media/bootscreen/boot.mp3 instead]
gbhil said:
You want to install the busybox remount and superuser Rom if you want to run stock.
Or manually install busybox, superuser whitelist and adb remount
Biggz - looks like they are on stock. No adb remount.
Click to expand...
Click to collapse
successfully removed (rm) the boot.mp3 in the shell - Thank you for that. I do want to replace it with a different one (I'll use the same file name since the .xml file still refers to it) so I'll need the cp command and I've noticed that it's missing in shell. I'm assuming I need to install busybox to get this functionality. I'm not really sure I want to install a complete new ROM and I don't mind manually installing busybox, adb remount, etc. What does installing "superuser whitelist" and "adb remount" allow me to do? I'm not sure what their potential uses are?
I installed busybox and have the cp command functionality now (see above post) but now when I try to copy anything to the /system/media/bootscreen folder I get "cp: cannot create '/system/media/bootscreen/boot.mp3': Permission denied"
I type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" after getting into shell and typing "su" and getting the "#" prompt and it takes successfully (this is the only way I was able to actually "rm" the original boot.mp3 file to begin with.
See anything I'm doing wrong?
Nope, that is correct.
/system is normally mounted as read-only, so you can't add or delete anything. The mount command remounts it as read-write, so you can modify it as root.
armyturtle said:
<snip> I'm not really sure I want to install a complete new ROM and I don't mind manually installing busybox, adb remount, etc. What does installing "superuser whitelist" and "adb remount" allow me to do? I'm not sure what their potential uses are?
Click to expand...
Click to collapse
Superuser whitelist is an application that warns you and asks for you to provide permission whenever an app tries to use the su binary to run as another user. You want this, as without it there's no way to know if an application runs as root.
Adb remount is a service that allows you to toggle the +RW bit on the /system/ partition through the shell. IIRC the one one floating around also kills color terminfo so you don't get all the extra chars on a windows PC when using the ls command. Just a matter of convenience.
jonnythan said:
Nope, that is correct.
/system is normally mounted as read-only, so you can't add or delete anything. The mount command remounts it as read-write, so you can modify it as root.
Click to expand...
Click to collapse
I can't create/copy anything after getting into the shell and remounting as read-write. From CMD prompt I type:
adb shell
and get:
$
Then I type:
su
and get:
#
This is where I type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Then trying to copy anything into the /system directory gives me:
Permission denied
It will let me DELETE anything I want from this folder (as confirmed by now deleting boot.gif just to check) but it won't let me cp (copy) anything to this folder. WHY?
What the heck?
try these commands for the boot mp3
Code:
cd/
cd /androidsdk/tools/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push directoryonpcwhereyourbootmp3is /system/media/bootscreen/
make sure that you rename the mp3 to boot.mp3 or it wont work anyways.
the other option (this is what I do) is find a bootscreen that you like (I use this one). open the zip file useing winrar or 7zip, navigate into the files where you see the boot.mp3 and drag in YOUR (now renamed) boot.mp3 close the window, put the zip file onto the root of your sd card, boot into recovery, choose flash from zip, flash the file and your good to go.
wtphoto said:
try these commands for the boot mp3
Code:
cd/
cd /androidsdk/tools/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push directoryonpcwhereyourbootmp3is /system/media/bootscreen/
make sure that you rename the mp3 to boot.mp3 or it wont work anyways.
the other option (this is what I do) is find a bootscreen that you like (I use this one). open the zip file useing winrar or 7zip, navigate into the files where you see the boot.mp3 and drag in YOUR (now renamed) boot.mp3 close the window, put the zip file onto the root of your sd card, boot into recovery, choose flash from zip, flash the file and your good to go.
Click to expand...
Click to collapse
tried this just now and still get "failed to copy 'C:\android-sdk-windows\tools\boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied"
It's the /system folder... I can push to /data/local all day long, but anything in the /system folder is read only. How the hell can I change this?
/system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
if this is the code you are using then that could be your issue
the code line should look like this
Code:
adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/
doing adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/boot.mp3 says that you are trying to push the boot.mp3 to the directory bott.mp3 and there is no boot.mp3 directory the folder where you want the boot.mp3 is bootscreen. try the ubove code and see what happenes.
wtphoto said:
if this is the code you are using then that could be your issue
the code line should look like this
Code:
adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/
doing adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/boot.mp3 says that you are trying to push the boot.mp3 to the directory bott.mp3 and there is no boot.mp3 directory the folder where you want the boot.mp3 is bootscreen. try the ubove code and see what happenes.
Click to expand...
Click to collapse
Nope, was a typo on my part (here in the post, not when issuing the command). Still permission denied. I don't think it's actually mounting the /system folder as writable. Is there a way to check after issuing the remount command?
A quick command of "ls -l" at root prompt gives the following for the /system folder:
drwxr-xr-x root root 2009-09-21 06:30 system
after you run the remount command what does it say? does it say remount succeded?
After typing the remount command it simply repeats my command back at me and returns to the "#" prompt.
honestly at this point what I would try doing is do a back up then flash a custom rom like fresh 1.1 that has all the tools built into it. then go into the cmd prompt and cd to where sdk is then type adb remount and see what it says then adb shell and try to cp the file to that directory.
this is more a test than anything else.
wtphoto said:
honestly at this point what I would try doing is do a back up then flash a custom rom like fresh 1.1 that has all the tools built into it. then go into the cmd prompt and cd to where sdk is then type adb remount and see what it says then adb shell and try to cp the file to that directory.
this is more a test than anything else.
Click to expand...
Click to collapse
I'll try this - so you recommend trying fresh 1.1 then? I know it's just a test, but just in case I like the ROM and decide to stick with it, might as well try a really good one! I'll try this tomorrow - I'm beat! (Thanks again!)
im on to the command prompt thingy and im a little confused......
do i put the whole command in? because when i do it says faild bla bla?
do i type it in just how it shows? cuz i wont work for me, but if i put in
JUST..."abd shell mount" it show alot of writing like it worked but im not putting in the WHOLE command???
can anyone tell me what it is supposed to say after each command??????????
omg i just want it to work. i got a new phone from verizon because i downloaded the leak, when all i wanted was a custom rom for wireless tether
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
you might want to hit up in the irc chat, you can get real time help there. irc.wastate.net i believe or irc.zifnab06.net chat room either erisroothelp or droideris
where is that? those links diddnt work
those werent links, they were the servers for the irc chats. you need a irc chat client to get on there. if you want to use a web based chat client, the direct link to there is chat.andirc.net
whooohoooo!
you dont remember how the command prompt works? im just wondering if you put the whole command in or just the first part....sorry if im coming off a little stupid and pushy
how about posting the error?
ok i get in to my tools directory(this is what i see)
*C:\AndroidSDK\AndroidSDK\tools>
i put in (adb shell mount -o rw,remount /dev/block/mtdblock3 /system)
this is what it says "mount: Operation not permitted"
Why not use this:
http://forum.xda-developers.com/showthread.php?t=661413
what does that do? is it an app to get around the command prompt?
Does your phone have root access? (did you flash the rooted PB00IMG.zip?)
yes i did all the steps leading up to this now im stuck on the command prompt
do i type in all of the command? when i do it says "mount: Operation not permitted" on the first command
*Sigh*
- Open up command prompt (either type in cmd in the windows search bar or dig deep into your computer to find that sexy thang.
- Direct it to the folder of your choosing. In this case, the tools subfolder of android sdk. There are several ways to do this, the easiest would be as follows:
Say you're trying to get to C:\AndroidSDK\tools
Type:
cd C:\AndroidSDK\tools
or
cd C:\
cd AndroidSDK
cd tools
- From here, you shouldn't have a problem with adb. Make sure your device is plugged in and type:
adb devices
and you should see your device. Copy and paste the commands and you should be good to go.
ok so i put in adb devices (wasnt in the walkthrough)
and it showed
"list of devices attached"
HT9CTHG01052 device
im assuming that this is my device! yay.....or so i thought
i copied and pasted the command...and i also tried to type it out
it said the same thing!?
"mount: operation not permitted"
im sure its something im doing wrong...i just need someone to take a couple minutes to help a brutha
i typed in "cmd" in front of each command and it showed
microsoft windows [version bla bla]
copyright bla bla
untill i got to the last command..... it said 'ecovery.img' is not recognized as an internal or external command, operable program or bach file (yes it did say " 'ecovery.img' ") i looked all over a i found no file mis labled as "ecovery.img"
when it says all that stuff about windows does that mean that it took the command?
Why are you typing in "cmd" infront of everything?
IDK im just trying to figure it all out? am i wrong?
thanks for helping btw
i wish someone knew what it is supposed to say after each command....or even a video showing someone doing these commands so you can see them typing them
Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
you type the adb commands in exactly like they are shown. you dont type anything in front of adb.
Someone please tell me what I'm doing wrong:
C:\Users\[my name]> cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools> adb devices
List of devices attached
HT9ADHG05719 device
C:\android-sdk-windows\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/mtdblock3 /system
# adb push recovery-ra-eris.img /sdcard
adb push recovery-ra-eris.img /sdcard
adb: not found
#
I had to enter adb shell and hit enter before inputting the rest of that command just to get past that step. I tried doing the same with the next step and entering adb push separately but I got this:
# adb push
adb push
adb: not found
#
Does anyone know what I'm doing wrong or leaving out? I have the recovery and flash saved to the tools folder of my sdk.
you cant use adb push from inside a shell
That's what the "how to root" instructions are telling me to do.
joshw0000 said:
That's what the "how to root" instructions are telling me to do.
Click to expand...
Click to collapse
looks like you are "separating" steps...
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
(Taken from this thread: http://forum.xda-developers.com/showthread.php?t=647707)
your command is "adb shell" (which is going to shell... in which, anonomouse is correct, you cannot "adb" inside a shell). instead, type 1 command like this:
- adb shell mount -o rw,remount /dev/block/mtdblock3 /system
re-read the thread (link i posted) again... you're close
from your post... you'd have to exit shell... then get back to a DOS prompt... then do the "adb push" command
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Linux or windows
Nevermind.... i reread your post. Sorry.
joshw0000 said:
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Click to expand...
Click to collapse
Make sure your sdcard is not mounted, it should be in charge only mode. Also make sure USB Debugging is on.
My phone was in charge mode and USB debugging was enabled, thanx.
joshw0000 said:
My phone was in charge mode and USB debugging was enabled, thanx.
Click to expand...
Click to collapse
You can use the application in this thread to help ease the process. They automated the commands through scripts to help in these situations. Plus, ECLIPS3 and Jamezelle do great work!
http://forum.xda-developers.com/showthread.php?t=661413
joshw0000 said:
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Click to expand...
Click to collapse
First the solution and then the explanation; note that I have included the command prompts here:
C:\android-sdk-windows\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
C:\android-sdk-windows\tools> adb push recovery-ra-eris.img /sdcard
C:\android-sdk-windows\tools> adb push recovery-ra-eris.img /sdcard
So, here's what is happening.
When you "break up the command", by making the first part the single line
Code:
adb shell
What you are getting is an interactive shell running on the phone. That shell does not terminate immediately; you can type an unlimited number of commands into it, one after another.
When you issue a command (from the PC's command window) which looks like this:
Code:
adb shell programname arg1 arg2 arg3 arg4
something a little different happens than in the first example: the program "programname" is launched on the phone, with the arguments "arg1", "arg2", et cetera - and the "shell" on the phone terminates as soon as "programname" is finished running
Note that the command prompt changed!
C:\android-sdk-windows\tools>
vs
#
So what happened? "adb" is a program on the PC, and NOT ON THE PHONE. When you typed "adb blah blah blah" into the interactive shell on the phone - guess what? you see "command not found".
If you insist on "splitting up the command", then go ahead (although I really don't see any reason why it wouldn't work in it's original format); just bear in mind you are typing commands into an interactive "command prompt" that is running on the phone. When it comes time to run other "adb" commands - you need to be at the PC's command prompt
bftb0
Thanks for the info. You were right. I had just screwed something up when I typed it in the first time. Explaining the steps really helped me to understand what I was doing. I entered the commands as you had them in the tutorial and it worked perfect. So after that I created a backup and attempted to flash a custom rom:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
It turns out I was just having another newbie moment. I did a wipe and reflashed the rom and it worked perfectly.
should i flash it. i dont have root
WOW! i cant believe no one has replied to you.
if you take a look at the first post with the topic
[ROM] Official AOSP 2.2 OTA
but you mentioned you dont have root. so try installing alogcat from the marketplace and capture the whole deal. then you can email directly from the app.
logcat isnt going to do much, it prefetches the files, need to pull the update.zip from adb
ok, so i havnt gotten the notice yet.
but need a bit of help prepping for when i do.
i have the android sdk installed on my desktop, and can create a virtual device etc...
but when i open the cmd prompt and try to run adb devices it says it is populating a list but i see no results or no file created.
so i tried just running adb logcat and it stops at waiting for device.
any pointers. im running win7x64 ultimate
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
sepiid said:
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
Click to expand...
Click to collapse
but how do you know the new radio and spl update name?
you should get that by running su then "cd /cache/ ; ls"
right now i have
download-1.apk
downloadfile.apk
recovery
lost+found
so after it is precached i run that "cd cache/ ; ls" i should have another file or two in there
that would be the file you run adb pull /cache/*.*
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Are you rooted? If not use Universal Androot.
*anticipation*
sepiid said:
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Click to expand...
Click to collapse
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
callmeradical said:
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
Click to expand...
Click to collapse
So the YAFFS2 part of the code I put up there is designating the file system in which we are reading/writing.
YAFFS2 is the most popular and widely used format for flash memory.
please allow me.
yaffs2 is a filesystem type. /cache is of course the directory. -o is for option.
rw: read/write
remount: remount /cache again with new option.
sepiid said:
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
Click to expand...
Click to collapse
Oh yeah and BTW, you can change the permissions back if you want after your done, otherwise I believe you can just reboot the phone and it fixes it, not entirely sure, I was trying to rewrite my default.prop to get adb remount to work with stock 1.6 rooted, but I am getting and access denied issue.
perfect was about to ask what the -o was but i tried mount --help and mount -h both resulted in nothing. then you reply sharpt71
thanks again all.
i am now ready to pull the update and upload once i get the update. hopefully soon!
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
SilverSurfR said:
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
Click to expand...
Click to collapse
You probably could I just know that this is a sure fire way to grab everything in cache directly to the machine, otherwise if you aren't next to a machine you could probably do a copy like you said.
My 2nd update failed, do you guys think the files are still in my cache?
Hi everyone,
A few days ago I got the OTA 2.2.1 on my MT3G and then rooted it using the SuperOneClick tool. I was able to remove all useless apps, pushed others to /system/app with Root Explorer, etc., there is only one to do, and I am clueless: how to replace the stock Android System Recovery <3e> with a custom recovery image, so I can do Nandroid backups, flash .zip files, etc?
I used the ROM Manager app to flash Clockwork, got an "Installation successful" confirmation, but then on reboot into recovery mode my phone got stuck on the MT3G logo. I had to remove the battery, then in second attempt the phone booted into the <3e> image. Restarted again, opened the ROM Manager, according to it Clockwork was installed. Total craziness! Then I tried to flash it using Better Terminal Emulator (su, flash_image recovery /sdcard/Clockwork.img) but I got a "flash_image: not found" message, though I had the image on my sd card.
Any good ideas, folks?
All useful suggestions much appreciated, thanks!
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
It's kinda relative to the topic. I'm stuck on clockworkmod and would like to get back to stock recovery as the new HBOOT doesn't let me flash roms. Is there any way I can do so?
Look in my guide... all the files, steps and binaries are included...
Check out my signature!
Thanks, Asadullah. One more question: Are there different versions of flash_image for different android versions, because I saw in another forum a user complaining he/she didn't use the right binary.
Edit: I've extracted a flash_image binary from CM 6, hope it will work
Edit2: It worked, thanks a lot, man!
I think that flash_image from different devices is different someone correct me if I'm wrong. Glad it worked
Sent from my HERO200 using XDA App
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
lgtsanev said:
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
Click to expand...
Click to collapse
I know it's been a while and you didn't get a reply, and while I found this thread because I too am having enormous trouble rooting this whatever it is cheap chinese android 2.2.1 momo 2 thing covered completely in chinese language apps that I simply cannot use even for the low price it cost me - I thought I'd offer an answer, most likely wrong, but one that may help the next person who may fall into your position.
adb root is an option to start the adb service in root mode, and I can only assume that means for the device.
As I have not been able to get this thing sorted, not knowing what it is really - no phone, no camera, no buttons on the case apart from power/sleep - Home/Esc which do nothing on booting apart from alert the PC to detect a new USB device, no market access, but otherwise exactly what I required - I dont know if it'll help.
But I hate threads left in a question, because I always find them. And this circle of frustration seriously should not be real, it just cannot be this damn hard to do something...
yikes!
help please
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
sky rider said:
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
Click to expand...
Click to collapse
root your phone
install terminal emulator on your phone
type in everything that you quoted except for adb shell
Confused in differences
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Jkhim said:
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Click to expand...
Click to collapse
Honestly it's been so long I forgot ?? I don't think you need too use flash image anymore
rm failed????
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sh: ./flash_image: not found how to fix this sir? im so new about this, sorry about that
---------- Post added at 05:22 AM ---------- Previous post was at 04:43 AM ----------
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sir is this CM.12 cyanogenmod fakelollipop is an example of flash_image even its in a zip file? because i cant get it at all, im stuck at flash_image not found