yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] pack:
when i mount -a in my shell i get an error

mount: cannot read /etc/fstab: no such file or directory

is it necessary to mount this folder?
[myTouch 3G, Magic Android Development] BurnOmatic:
this happened to me because i had the phone plugged into the power, pc usb, etc... what i did is i unplugged it then the phone recognized the file because it says setting up sdcard etc.. that's probly your problem.
[myTouch 3G, Magic Android Development] hikki2000:
Amon_RA, suggest you change the wording 'wipe data partition' back to 'wipe data/factory reset', wipe data partition is a bit confusing to noob...?
[myTouch 3G, Magic Android Development] djungelmums:
Fstab is a file, not a folder. This file has the info of what is going to be mounted and where.

Probably the same problem as Burnomatic describes.

The sdcard cant be reached by the phone if its mounted by the computer.
[myTouch 3G, Magic Android Development] pack:
I understand that but my problem is that when I run the "mount -a" I get back this error:

mount: cannot read /etc/fstab: no such file or director

just to clarify my phone is not pluged into usb/power/anything and I did switch user to root...

also the rom is Hero_Over's vMT3G.2 "Slick Willy"

....any other suggestions?
[myTouch 3G, Magic Android Development] shohid1234:
I was having trouble flashing roms so I used a vodafone uk nandroid image and now I have lost root access.

Checking on my fastboot, it has changed from:

PVT 32B ship s-on G

to:

PVT 32B eng s-off H

Presumably because I have flashed crios eng spl.

So my question is, "s-off H" is found on 32A HTC branded devices, and my phone is a 32B Google branded. So what amon ra recovery should I use?

im assuming because its a 32B board i should use G and not H.

Am I correct.
[myTouch 3G, Magic Android Development] pack:
Well if you look here at amon's instructions to root the mt3g...

he has you switch your phone from "G" to "H" and when you do that he has you load his "H" recovery even though the mt3g is "G"

then he has you go back to "G" and after you do that he has you using his "G" version

Thats just what I got from it heres the original so you can check it out

http://xdaforums.com/showthread.php?t=547133
[myTouch 3G, Magic Android Development] shohid1234:
cheers pack, just checked out the thread you suggested and boy its alot of work espically for a noob :eek:

Unless theres an easier way i.e use flashrec then flash amon ra's new recovery image I think im going to allow flashing roms for the time being.

Hey amon can you confirm that upgrading downgrading, goldcard here, downgrade there blah blah ect is my only option??????????
[myTouch 3G, Magic Android Development] jokeyrhyme:
If you are stuck with an SPL that prevents flashboot from working, you should try seeing if flashrec works for you. Alot of the official ROM updates are still vulnerable to the Bluetooth bug it exploits to flash the phone. Try to flash the earliest official ROM update you can find.
[myTouch 3G, Magic Android Development] Kevvy1066:
repartition?

with the new interactive partioning, can i re-partition an sd card?

e.g. the card that i have with fat32 500mb ext3 and 32 mb linux

can i change the partitions with this image, or do i have to manually remove them with ubuntu or something before i can partition the way i want?
[myTouch 3G, Magic Android Development] shohid1234:
In that thread both radio and spl are changed from a 32B to 32A, while my phone it is only the spl which appears to be a 32A version.

is there any danger of bricking my phone if I try flashrec and then either of amon ra's new recovery images?
[myTouch 3G, Magic Android Development] Amon_RA:
The H or G in the SPL doesn't matter, it's not that an SPL from a 32A is always with an H or so. You can safely ignore the H or G in the SPL, they have absolutely no influence whatsoever as far as I know.
[myTouch 3G, Magic Android Development] midtoad:
I had trouble flashing the latest recovery image. I kept getting "out of memory" errors. Then I checked the space in /system using df, and discovered I only had 400 kb free! Given that I had an earlier version of the recovery image previously installed, I don't understand how this could have occurred. Could it be that the installation of the latest MyHero ROM with SenseUI took up so much room that the recovery image got punted after installation?

Anyway after some investigation I found some language files I could move to the SD card (e.g. WP_0414RUS.db) and that eventually freed up 4 MB. The installation still failed (for some reason I can't use fastboot to flash the recovery image as it fails with a copy-not-allowed error), but... I found a wiki that described that if you put recovery.img in /system, on each boot it will be flashed into the recovery partition in /dev/mtd1. So I mounted my device and copied the latest recovery.img into /system, and then just rebooted.

Presto! Thanks Amon_RA for making this image!
[myTouch 3G, Magic Android Development] Malza:
I seem to have a slight problem with this recovery.

It seems when I am in recovery mode (as in holding home+power) and I come to my nice recovery screen I want to use adb but I always get errors and problems. For example I'll try to do adb remount and it'll say error. Also I can't push/pull either.

I found a solution(or work around), well a fix really but it's tedious and I don't really understand what the problem is, but the only way to ensure my adb commands work is to:

adb shell
mount -a

Wait till it fails, it will hang for a minute before it responds. Then type in:

exit
adb remount

Now I can use adb without errors or problems, I really don't know why. Any ideas?
[myTouch 3G, Magic Android Development] Amon_RA:
Give the recovery some time to fully boot before using "adb shell".
[myTouch 3G, Magic Android Development] sleepymatt:
Amon_Ra (or anyone else),

Will the following method work for unlocking 1.33.0010? After reading through the comments, the guy who wrote the article replys to some questions stating that it will indeed work. Whats your take?

http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/

Thanks
[myTouch 3G, Magic Android Development] Amon_RA:
It depends on which ROM you are running.

In newer ROM versions the the security exploit that flashrec uses will not work anymore.
[myTouch 3G, Magic Android Development] sleepymatt:
I am running Cupcake. So it should work then ... that's very exciting.

Also wanted to say thanks for your time and effort!
[myTouch 3G, Magic Android Development] crecsky:
Hello Amon_Ra, (or anyone else who can do it :])

I was wondering if it would be possible for you to edit my boot.img for me to get root like you did for that gentleman on page 5 of this thread. I've tried to follow a tutorial on how to do it, but was unsuccessful.

I enjoy the simplicity of the rom that's on it now and would like to get SuperUser access in order to get rid of some applications.

I am using a 32A HTC Branded Rogers Magic, and my Nandroid backup can be found at:

http://rapidshare.com/files/309851666/32AHTCBrandedRogersMagic.rar.html

MD5: 8ED6788912CCDFB95B771B91C6F624D1

Thanks alot.
[myTouch 3G, Magic Android Development] nerdybobby:
Wrong Recovery Image?

Okay, so I am pretty new to all of this. But I have successfully flashed dozens of custom ROMs. No bricked phone or anything of that nature. I have the mt3g. So it's a 32B board of course. I have RA-dream-v1.2.3 recovery image. I guess I wasn't paying attention when I flashed it on the first time. It has worked so far. I have tried many times, through adb to put this new recovery image on. I follow all the steps, get no error messages. But when I reboot into recovery it still has the old recovery image. Could this be because I have a dream recovery image? If so, is there a way to correct this? Or could there be some other reason why the image won't apply? Any help is appreciated.
[myTouch 3G, Magic Android Development] Amon_RA:
The fact that you have a dream recovery doesn't matter.

-Which rom do you have?

-Could it be that your current rom flashes a recovery.img located in system every time you boot?

-Did you restore any old nandroid backups (which might include an old recovery image)?

1. Make sure that there's no recovery.img in /system or /data

2. fastboot erase recovery (so you are sure that the old one is gone)

3. fastboot flash recovery recovery-RA-magic-v1.3.2G.img

4. boot into recovery
[myTouch 3G, Magic Android Development] nerdybobby:
Thanks for your quick response. It's really appreciated. I am using CM4.2.4. Tried the fastboot erase recovery. Returned with "erasing 'recovery' ... FAILED (remote: not allowed). Any other suggestions?
[myTouch 3G, Magic Android Development] nerdybobby:
Also, is it possible to just use flashrec to boot this recovery image in place?
[myTouch 3G, Magic Android Development] kie777:
hi

my htc magic is in myhero rom 1.1 i tried this step :

opy recovery-RA-magic-v1.3.2H.img to the root of your sdcard

start the terminal app

$su (not required if you have root already)

#mount -a

#flash_image recovery /sdcard/recovery-RA-magic-v1.3.2H.img

to make a recovery file,but it won't work

after i type mount -a screen always shows :

mount : cannot read /etc/fstab : no such file or directory

can anyone help explain what's wrong?

ps. my magic is already rooted and i use better terminal pro to the action above
[myTouch 3G, Magic Android Development] jokeyrhyme:
flashrec works by exploiting a Bluetooth-related vulnerability. I think it's safe to say that none of the custom ROMs found here are vulnerable, so flashrec won't work with them.

However, if you currently have an old official ROM from HTC installed on your phone, then there's a good chance it'll work. Most official update ROMs from your carrier or manufacturer released before August 2009 can allow flashrec to work.

While it's incredibly convenient for this one specific case, it's really disappointing that the community can fix and patch in moments what is still probably broken on lots of factory and official update ROMs out there.
[myTouch 3G, Magic Android Development] Amon_RA:
Copy paste of the first post of this thread :

Install

There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).

Use the H/G version if your Magic is HTC branded (PVT 32A board)/Google branded (PVT 32B board).

Just ignore the errors you get with the "mount -a" command, those are normal.
[myTouch 3G, Magic Android Development] kie777:
thanks a lot amon_ra,your tutorial really works,i've done it ,now im making my first nandroid backup,it's been 30 minutes though,the screen still shows the htc logo and some dots running,is this normal? how long it's supposed to be?
[myTouch 3G, Magic Android Development] Amon_RA:
4 minutes max...

Try running it via adb to see what's wrong.

Boot without usb cable, wait for a min and try again.
[myTouch 3G, Magic Android Development] kie777:
that's the problem,to use adb you need a windows pc,i dont have one here,i tried to search how to perform adb via mac os,and it's killing me to find the right method,as for the backup i am doing right now,still running dots,i decided to pull the battery off and retry,still on the process now,and wow,it works now it says backup complete.Thanks for your kind attention and help
[myTouch 3G, Magic Android Development] :
It says me on PC : error: device not found

and when i boot my handy with power + home and when i see the ! than i push power and home again, stand the following :

E:Can´t open /cache/recovery/command

what can i make now?
[myTouch 3G, Magic Android Development] tempix:
I have just received an HTC Magic (from Vodafone). And I have been playing with it for few days. I Have noticed the following problem after gaining root access.

When I power on the phone everything works perfectly. But when the screen goes into power saving mode and I reactivate it the screen is blurred. It looks like some pixels are being displaced.

I have not been able to figure out this happens and it only happens when I am the root user.

I substituted

SAPDHIRE PVT 32B ship S-on G

HBOOT-1.33.0006 (SAPP10000)

CPLD-10

RADIO-2.22.19.26I

May 27 2009,,19:06:41

for

SAPDHIRE PVT 32B ship S-off G

HBOOT 1.33.2005

using flashrec-20090815.apk

Does anybody know what the issue might be?

Thanks in advance
[myTouch 3G, Magic Android Development] auvi:
This method worked here on the US T-Mobile 1.5 cupcake ROM. I used flashrec to upgrade RA recovery v1.2.3 to v1.3.2.
[myTouch 3G, Magic Android Development] sim-value:
Somehow ADB cant acces the sdcard with this recovery ?!
[myTouch 3G, Magic Android Development] magicdroid:
So.. I flashed this recovery img to my stock Proximus HTC Magic.

If I have a nandroid dump of this stock rom, could someone enable root access on it?
[myTouch 3G, Magic Android Development] crzyruski:
on v1.2.3 I was able to mount it manually.
[myTouch 3G, Magic Android Development] bo01:
Hi, I recently bought a Magic HTC and I' m trying to update to hero ROM. I have stuck in the backup part where I am running nandroid (2.2) and the procedure just prints dots for over 30 minutes (maybe 40). I tried twice.

Any suggestions? I am a newbie in the mobile community, so please be patient.

I tried with older recovery version as well.

Thnx in advance!
[myTouch 3G, Magic Android Development] nmesisca:
i assume you have root on it.. and you're not just fastbooting boot the recovery?
[myTouch 3G, Magic Android Development] chris-torb:
Hey..

When i'm trying to flash the V1.3.2 om my HTC branded magic 32A, it results in a lot of out of memory errors, as it tryes to flash...

I'm using the "terminal" method, and i have no problem flashing the V1.2.3

Can anyone tell me, what i am doing wrong?? i hate to "brick" the phone :confused:

chris-torb
[myTouch 3G, Magic Android Development] tuzz:
I have memory errors too flashing trough fastboot.

I flashed trough adb and I had only one memory error...

I tryed again and no errors..

now it works...

I dunno why this happened..
[myTouch 3G, Magic Android Development] eug89:
Hi amon, i've just tryed to compile eclair and now i have a system.img a boot.img and userdata.img, since i have the stock spl i'm not able of flashing this images with fastboot can I flash them through recovery?

e.g. : #mount -a

#flash_image system /sdcard/system.img
[myTouch 3G, Magic Android Development] sandis84:
Hey!

This seems to be exactly what Im looking for. But since it would really hurt to loose my phone, Im just gonna be paranoid and ask a few questions:

This SPL should suffice for the install via fastboot, right?

http://www.gotontheinter.net/content/new-engineering-bootloader

Also, will this recovery image work for all android phones? Or are there any limitations to it?

Cheers,
[myTouch 3G, Magic Android Development] Amon_RA:
Yes you can use flash_image.

You can also create a "fake" nandroid backup with the images you've compiled.
[myTouch 3G, Magic Android Development] Amon_RA:
Any engineerings bootloader will work, just be really carefull when flashing a new one, make sure you are flashing the right one for your phone! So don't flash a dream spl to a magic etc... that will brick your phone.

This recovery image only works for the HTC magic, both the 32A and 32B version (so check which one you have). It will NOT work on other Android phones. I've created some specific recoveries for other phones (check hero, heroc, dream section of xda for those).
[myTouch 3G, Magic Android Development] tazz9690:
so I know on nandroid you can now choose whichever backkup you want to restore, but is there anyway to do it with bart? It just seems to restore the latest one that i backed up.
[myTouch 3G, Magic Android Development] JAWheat411:
Amon_Ra said on twitter that he was waiting on Dream users to report bugs. He said there were a few. I haven't had a MyTouch for long, but did he used to release them Sapphire ones first? Not complaining just knew I didn't know about it on the Dream forum for a long time.
[myTouch 3G, Magic Android Development] sipvn:
Amon Ra 1.3.2. not loading

Hi all,

first thanks for all the infos, soft and tutorial out on this site.

And despite all of them I encounter a pb I did not manage to solve :p

Got a Magic SFR (France) unlocked, working in Vietnam on Vinaphone.

Got it root through fast boot and sdk using this img http://wiki.smartphonefrance.info/GetFile.aspx?File=root-htcmagic/boot-magic-donut-root.zip

to get throught cmd to set up su access.

Looks like my phone is rooted, as I can get su related info through cmd and terminal.

Pbs starts now. Wanted to flash Amon Ra 1.3.2. via terminal, but every time I got the following: "flash_recovery not found"

And yes I did type in the right command and the right image name.

Eventually I decided to flash via fast boot. I first booted on amon ra image via fast boot usb to flash an engineering spl (1.33... 2005). Worked like a charm.

I then used fast boot again to falsh Amon Ra recovery (1.3.2. magic, google branded. the same I used to flash the spl). Worked like a charm. At least my computer said so.

Unfortunately I can not restart the phone on recovery mode, he got stuck on the <!> screen. I reflashed it, still the same.

Any idea?

SAPPHIRE PVT 32B SHIP S-OFF H

HBOOT-1.33.2005 (SAPP10000)

CPLD-10

RADIO-2.22.19.261

Donut 1.6 rooted

2.6.29-00479-g3c7df37 android-build@apa26 #19

****** I reflashed the engineering spl, then erase the recovery, then reflash amon ra recovery and still not work ********

this is driving me nutz
[myTouch 3G, Magic Android Development] Amon_RA:
The name of the binary is flash_image, not flash_recovery... so enter :

flash_image recovery /sdcard/recovery-RA-magic-v1.3.2G.img

First try to fastboot boot the recovery and see if that works :

fastboot boot recovery-RA-magic-v1.3.2G.img

If you can boot the recovery you can permanently flash it :

fastboot erase recovery

fastboot erase cache

fastboot flash recovery recovery-RA-magic-v1.3.2G.img

Ps : Make sure that your current rom isn't flashing a recovery.img at boot. Check your /system if there isn't a recovery.img in it.
[myTouch 3G, Magic Android Development] sipvn:
Tks for the prompt answer.

I can fastboot boot the recovery img. Thats actually how I flashed the spl.

I then flashed it by:

fastboot erase recovery

fastboot flash recovery recovery-RA-magic-v1.3.2G.img

And I got stuck on the <!> when starting my phone with off+home

i just did it again, including erase cache as you suggest. Same result.

I do have a file named "recovery-from-boot" in my system. Should i delete it?

Cheers, much appreciated
[myTouch 3G, Magic Android Development] Amon_RA:
Can you do :

adb shell

# cat init.rc | grep flash_image

What does that give as output?
[myTouch 3G, Magic Android Development] sipvn:
I first had to type in

su

to get # and not $, otherwise I got permission denied.

then after entering su,

adb shell

# cat init.rc | grep flash_image

gives me

grep: not found

write: broken pipe

I have to say that we're reaching the outer limit of my noobness...
[myTouch 3G, Magic Android Development] sipvn:
Ok found this in another thread:

http://xdaforums.com/showthread.php?t=568171

Quote:

ah ... i think the problem is that the recovery is replaced with each reboot.

first do:

adb root

adb remount

adb shell

cat /system/etc/install-recovery.sh > /system/etc/install-recovery.sh.disabled

rm /system/etc/install-recovery.sh

cat /system/recovery-from-boot.p > /system/recovery-from-boot.p.disabled

rm /system/recovery-from-boot.p

Flash a recovery-image like before ...

Does that seem to apply to my case too?
[myTouch 3G, Magic Android Development] Amon_RA:
@sipvn :

grep is not working because you didn't install busybox..

Do a cat of you init.rc and check if any install-recovery script or flash_image recovery is loaded at boot.
[myTouch 3G, Magic Android Development] darkstar38:
Hey Amon RA just wanted to say great work! I have a problem, I am currently running your 1.2.3g recovery on my mt3g 32b. I am trying to upgrade to 1.3.2g via terminal. I follow your commands exactly and the recovery image does not show up after I reboot into the recovery. I have tried this 20 times and cant get it to work. Please help!

Thanks
[myTouch 3G, Magic Android Development] sipvn:
Amon Ra 1.3.2. not loading

@ amon ra

(im a big noob) couldnt figure how to install the busybox properly, so I flashed cyanogenmod 4.2.5 via fast boot loading your recovery.

still have the same pb (sutcked on the <!> windows) but this time busybox is installed and when I do a cat of the init.rc I get:

service_flash recovery /system/bin/flash_image -d recovery /data/recovery.img

Guess that the script you were spking of, right?

thx
[myTouch 3G, Magic Android Development] Amon_RA:
Yes, this means that your rom will try to flash a recovery.img located at /data when it boots.

Just rename my recovery to recovery.img, copy it to /data and reboot your phone. If the flash was successful the recovery.img file should be gone from /data (that's what the -d parameter is for) and you should be able to boot into recovery.

If you still get the <!> window you should try to re-download the recovery image, maybe the image got currupted while downloading (check md5sum to be sure).
[myTouch 3G, Magic Android Development] Amon_RA:
Was the flash successful? What is the output of each command?
[myTouch 3G, Magic Android Development] ronni.rasmussen:
Just installed recovery-RA-magic-v1.3.2H.img and damn that was a sweaty experience!

1st attempt doing this using the terminal method (better terminal) something went wrong and i couldn't get into recovery mode :eek:

Took out the battery to see if i could load the OS but no problems getting android running :)

Then i couldn't get adb to list my device to try that method :eek:

Went to fastboot to see if i could get that method to work even though i don't have engineerings SPL and no luck connecting fastboot :eek:

Booted back into android and tried to use flashrec but backup failed :eek:

And finally i decided to give the terminal another go and got through with plenty of errors and though damn the same thing happens again :(

But powered down the phone to see if it worked and booted into RA-magic-v1.3.2 recover :cool:

Enough playing around with my mobile this evening :D

Thanks once again for sharing!
[myTouch 3G, Magic Android Development] Atlas24:
did you get those read and write errors from the terminal emulator?

mine ended with saying no space left on device?

just checked, my recovery was stuck at the rogers screen, mulligan on this one

well i just kept doing it through the emulator- i did something right because it now works

THANKS AMON RA

works on

SAPPHIRE PVT 32A SHIPS S-ON H

HBOOT-1.33.00.10 (SAPP50000)

CPLD-12

RADIO-3.22.20.17

Jun 2 2009,17:20:20
[myTouch 3G, Magic Android Development] elite_is3:
I am having an ISSUE clearing my Dalvik-cache, it tells me to Wipe in Adb shell. doesnt work

my rom is now unstable... help
[myTouch 3G, Magic Android Development] jessevsm:
seem to be having a slight problem here. When I type in

flash_image recovery /sdcard/recovery-RA-magic-v1.3.2G.img

It tells me 'error reading..."

can someone tell me what I'm doing wrong?
[myTouch 3G, Magic Android Development] Amon_RA:
Did you try doing what it tells you to do?

Run wipe from adb shell... :p
[myTouch 3G, Magic Android Development] MontAlbert:
this happened to me last time and it has bloody happened to me again- buggered if i remember what i did to fix it last time but it sure as hell isnt working so far.....

so atm i am stuck with no recovery..... should have just waited and done it via adb....

****edit*** finally it worked- did it from the terminal inside SUFBS- i used this app to mount the system and data as read/write before hand and then it threw up one read write error but then nothing... rebooted into recovery ok...

phew....
[myTouch 3G, Magic Android Development] NguyenHuu:
i get that error too. but i just went ahead and flash it again, and even though it had errors, the recovery flashed fine. so flash at least 2 times, ignore the errors haha. or do what MontAlbert suggested, trying mounting it first then flashing.