Hi everyone,
I am kind of stuck with getting a custom ROM on my HTC Magic 32B (spl:1.33.0013 radio:2.22.28.25 os:2.2.1ota)
I cant flash custom recovery...or anything else
Here´s what happend so far:
http://forum.xda-developers.com/showthread.php?t=939749
Hope someone can help
There was another person that I was working with having the same problem. For whatever reason we couldn't get the custom recovery to stick no matter what we tried and we ended up stopping with him trying to downgrade to root. I'm not sure where he got. You can try using "flash_image" from terminal, but it probably won't help. Download the attached "Flash_image.zip", unzip the file, and put in on the root of your SD card. Then open up terminal on the phone and type the following hitting enter at the end of each line:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/*name of recovery*.img
reboot recovery
Thanks for your instructions...but it did not work for me.
I kind of gave up on getting my Magic flashed.
Did you check to see if there are any scripts that will override the recovery on closure?
Do this:
Pull out the battery when you execution of the flash_image command has succeeded.
This way you can avoid any scripts being executed on turn-off.
Now try to see if you can get the custom recovery to work!
Related
Going through the steps in this thread to update the lockscreen images, I have a question about messing around with the system files.
Which is the better method?
1) While the phone is up and running, start adb shell and mount the system using this command:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
or
2) Boot into the modified recovery screen, start adb shell and then use these steps:
Code:
mount /system
{copy, move, edit files files... whatever...}
umount /system'
reboot
Would the second method be the more correct (or cleaner) method, or does it not really matter?
You might want to replace the second part with just
Code:
{copy,move,edit,etc}
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
The first step already mounts the partition so the mount in step 2 is kinda redundant. Also, a reboot can be helpful, I've not found it necessary in most cases...the phone adjusts pretty well to change usually (at least it adjusts to removal of programs or even taking rosie out and adding it back in).
can anybody answer my why i keep getting this message
C:\android-sdk-windows\tools>adb push recovery-RA-heroc-v1.5.2.img /sdcard
failed to copy 'recovery-RA-heroc-v1.5.2.img' to '/sdcard/recovery-RA-heroc-v1.5
.2.img': Permission denied
what do I have to do to get permission granted?
thanks in advance
Is your SD card mounted? It cant be mounted to your computer when running adb to it or you will get this error.
limbicsystem said:
can anybody answer my why i keep getting this message
C:\android-sdk-windows\tools>adb push recovery-RA-heroc-v1.5.2.img /sdcard
failed to copy 'recovery-RA-heroc-v1.5.2.img' to '/sdcard/recovery-RA-heroc-v1.5
.2.img': Permission denied
what do I have to do to get permission granted?
thanks in advance
Click to expand...
Click to collapse
I have had that problem before if you have gotten to that step in the guide then you are already rooted you just need to flash the recovery. just mount your card and manually copy the file to the root of your sd card then unmount and use this code
Code:
cd /androidsdk/tools/
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/
flash_image recovery recovery-RA-heroc-1.5.2.img
wait for the # symbol to come back up and then type
Code:
reboot recovery
this is what i get when i try to do it manually
C:\android-sdk-windows\tools>adb shell
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
error opening recovery-RA-heroc-v1.5.2.img: No such file or directory
# flash_image recovery recovery-RA-heroc-1.5.2.img
flash_image recovery recovery-RA-heroc-1.5.2.img
error opening recovery-RA-heroc-1.5.2.img: No such file or directory
i tried to put the v in front of the one because thats how it was listed but it still didn't work. does it help to say that i bought this three days ago?
flash_image recovery recovery-RA-heroc-1.5.2.img
i have the same problem. can anyone help? I download (flash_image recovery recovery-RA-heroc-1.5.2.img) on to pc but it seems that it wont open the file to read. I copy the file on xp and vista. even copy it manually on the sd/card? can anyone help?
Pre-Kitchen.
limbicsystem said:
this is what i get when i try to do it manually
C:\android-sdk-windows\tools>adb shell
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
error opening recovery-RA-heroc-v1.5.2.img: No such file or directory
# flash_image recovery recovery-RA-heroc-1.5.2.img
flash_image recovery recovery-RA-heroc-1.5.2.img
error opening recovery-RA-heroc-1.5.2.img: No such file or directory
i tried to put the v in front of the one because thats how it was listed but it still didn't work. does it help to say that i bought this three days ago?
Click to expand...
Click to collapse
You are getting that error because it can not find the specified file. Try this:
When your phone is plugged into your computer, mount your SD card. Then, using Windows Explorer (On your computer) look at your SD card and see if the Recovery IMG is there. If it is, this should work. If it is not, simply click and drag the 1.5.2 Recovery img onto your SD in the root folder (there isn't a folder called root, it simply implies the main/top level folder. The img should not be in any subfolders). Once the Recovery img is on your SD card, then on your phone unmount the SD card, and try your commands again.
i get an error when try adb push a recovery file to my sdcard and ideas?
Need to give it a file name at the location you're moving it to I believe.
Example: adb push foo.txt /sdcard/foo.txt
ok thanx, how do i delete a file off the phone? when i install a custom recovery and reboot it goes back too stock recovery so i need to delete /system/etc/install-recovery.sh file, but need to know how
corolla90 said:
ok thanx, how do i delete a file off the phone? when i install a custom recovery and reboot it goes back too stock recovery so i need to delete /system/etc/install-recovery.sh file, but need to know how
Click to expand...
Click to collapse
enter this into command prompt or terminal
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now, and now I'm here. What am I doing wrong? Thanks
there
Code:
mount -o remount,rw /dev/mmcblk0p12 /system
back
Code:
mount -o remount,ro /dev/mmcblk0p12 /system
Hmm, well at least I didn't get any errors this time.
I didn't get a confirmation or that it did anything at all. Is that normal?
Run mount with no parameters and look for the line with that device name, should see rw in that line instead of ro.
Sent from my MB860 using XDA App
Thanks guys, but I resorted to busybox chmod command instead lol
I tried this and got no errors, and using cat /proc/mounts/ I see the path as rw. But when I try to copy I still get the read only file system error.
**Lol, I had the phone in usb storage mode and had to switch it to Windows Media Sync**
DISCLAIMER: This tutorial requires root access, so be careful. I'm not taking any responsibility.
This is a quick tutorial on how to enable all system watchfaces on Ticwatch E&S. In order to make this method working it is needed to change the product model. I don't know if ota updates will still work after applied.
Instructions:
1. First of all we need to gain root access. To do this I suggest to follow this thread (thanks to @EpicLPer )
2. Download and unzip the file oem.prop attached to this post. It is a modified version of original file in which I have just modified the product model from "Ticwatch E" (or Ticwatch S") to "Ticwatch E&S"
3. Connect the watch to computer and and send these commands:
Code:
adb push "[I]/directory/to/saved/oem.prop[/I] " /sdcard/download
adb shell
su
mount -o rw,remount /oem
cp /oem/oem.prop /sdcard/download/oem.prop.backup
cp /sdcard/download/oem.prop /oem
mount -o ro,remount /oem
mount -o rw,remount /system
chmod -R 644 /system/app/TicWatchface
mount -o ro,remount /system
reboot
3. Wait for the watch to reboot and don't worry if there is no more any default watchface, it is normal at this point.
4. Connect the watch to computer again and send these commands:
Code:
adb shell
su
mount -o rw,remount /system
chmod -R 755 /system/app/TicWatchface
mount -o ro,remount /system
reboot
5. When the watch is booted there should be all watchfaces on it, both S and E ones.
6. Have fun
elios93 said:
DISCLAIMER: This tutorial requires root access, so be careful. I'm not taking any responsibility.
This is a quick tutorial on how to enable all system watchfaces on Ticwatch E&S.
Instructions:
1. First of all we need to gain root access. To do this I suggest to follow this thread (thanks to @EpicLPer )
2. Connect the watch to computer and and send these commands:
Code:
adb shell
su
mount -o rw,remount /system
chmod -R 644 /system/app/TicWatchface
mount -o ro,remount /system
reboot
3. Wait for the watch to reboot and don't worry if there is no more any default watchface, it is normal at this point.
4. Connect the watch to computer again and send these commands:
Code:
adb shell
su
mount -o rw,remount /system
chmod -R 755 /system/app/TicWatchface
mount -o ro,remount /system
reboot
5. When the watch is booted there should be all watchfaces on it, both S and E ones.
6. Have fun
Click to expand...
Click to collapse
Thanks, I was just working on this and you seem to have found the MUCH easier route than I (editing the APK).
BackCheck said:
Thanks, I was just working on this and you seem to have found the MUCH easier route than I (editing the APK).
Click to expand...
Click to collapse
Well, I was working on your same direction when I found this easier solution!
elios93 said:
Well, I was working on your same direction when I found this easier solution!
Click to expand...
Click to collapse
After reinstalling some apps, I think they reset back to the model defaults. I'm not sure but I think anything that adds or modifies watchfaces causes it to revert.