[FINAL] OMJ's HTC EVO 2.2 Custom ROM v4.6 | FroYo 3.70.651.1 | *Updated 3/29/11*

[rlmurray]

this is the output.
D:\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# mount -o rw,remount -t yaffs2 /sdcard
mount -o rw,remount -t yaffs2 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
D:\android-sdk-windows\tools>


It had me reformat since it said the card was unreadable. I did and now the camera works after the reboot. Thanks for that!!
I'm guessing all is golden now but I hope that I don't have a bad SD card if the issue crops up again?
Copying my old pics, mp3's and videos back again and will let you know if I can view them.
That was the original problem before. When I copied the old DCIM folder it would not read the old pictures and videos when copied via explorer on windows XP.
Also I can view all the files.
Thanks again.

[iknowsquat]

Originally Posted by rlmurray

this is the output.
D:\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# mount -o rw,remount -t yaffs2 /sdcard
mount -o rw,remount -t yaffs2 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
D:\android-sdk-windows\tools>


It had me reformat since it said the card was unreadable. I did and now the camera works after the reboot. Thanks for that!!
I'm guessing all is golden now but I hope that I don't have a bad SD card if the issue crops up again?
Copying my old pics, mp3's and videos back again and will let you know if I can view them.
That was the original problem before. When I copied the old DCIM folder it would not read the old pictures and videos when copied via explorer on windows XP.

[IMG]file:///D:/downloads/android%20apps/backup/evobackup752010/DCIM/100MEDIA/100_0089.jpg[/IMG]

The old pics/vids could be the issue. I've read that they can become corrupt rendering your card 'read only'.

Sorry about the code ADB n00b here

I left off part of the code. What it should be is something like this:

mount -o remount,rw -t yaffs2 /dev/block//vold/179:1 /sdcard

The part I left off is how it is on my device. Yours MAY differ. To find out in adb shell type
mount (as long as you are at a #)
Look at the code that is generated and look for the /dev/block//vold...
it corresponds to your sdcard. I ASSUME they would be the same for all devices but just in case verify on your device.

Hope that helps.

[Nygel]

I have a question its pertaining to the WIMAX and radio, I have not installed the update but I have the second update (from release date) and fully root (NAND unlock). Now I am seeing the wimax radio for this ROM version, when you complete the toast root does your wimax radio gets changed also? And after flashing the radio for this version should I still install the wimax radio ( for the 2nd update not .47)

[rlmurray]

DOn't have anything regarding an sd card.
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
#

[iknowsquat]

Originally Posted by Nygel

I have a question its pertaining to the WIMAX and radio, I have not installed the update but I have the second update (from release date) and fully root (NAND unlock). Now I am seeing the wimax radio for this ROM version, when you complete the toast root does your wimax radio gets changed also? And after flashing the radio for this version should I still install the wimax radio ( for the 2nd update not .47)

I dont know if the Toast method changed your wimax.
But even if it does it would not be the most up to date one.
And yes, after flashing the latest radio it is advised that you also update your wimax for best performance. You dont HAVE to, it's just advised.

HOWEVER, updating the wimax caused A LOT of headaches, breaking 4G for many.

The SAFEST way to go is to wait for OMJ to work with the latest kernel source which should get you working 4G along with the latest radio and wimax.

If you have an itchy flash finger like me then I'd reccomend the whitslack Start Over. I've linked it numerous times but here it is again
http://forum.xda-developers.com/showthread.php?t=715915

It worked perfectly for me and I'm reaping benefits even though I dont have 4G.
If you go that route, follow his steps, wipe then flash OMJ 1.6 (1.6r is not needed as whitslack includes the radio and wimax) then restore your settings.
As usual no promises but it worked for me and many others.

[iknowsquat]

Originally Posted by rlmurray

DOn't have anything regarding an sd card.
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
#

Weird, we are identical except for that.
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid
1015,fmask=0702,dmask=0702,allow_utime=0020,codepa ge=cp437,iocharset=iso8859-1,
hortname=mixed,utf8,errors=remount-ro 0 0
#

How is your phone connected? Charge only with USB debugging selected?
It appears adb cant see your card which makes me wonder if that could be it?
You already reformatted in FATS32 correct?
If that isnt it PM me and we'll see what else we can hash out.

[rlmurray]

Originally Posted by winmonewbie

Weird, we are identical except for that.
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid
1015,fmask=0702,dmask=0702,allow_utime=0020,codepa ge=cp437,iocharset=iso8859-1,
hortname=mixed,utf8,errors=remount-ro 0 0
#

How is your phone connected? Charge only with USB debugging selected?
It appears adb cant see your card which makes me wonder if that could be it?
You already reformatted in FATS32 correct?
If that isn't it PM me and we'll see what else we can hash out.

I'm dense and a noob. Learning albeit real slowly.
You were right. I did not have it set to charge only.


/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=su
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepa ge=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
#
Well I had to reformat and copy the files a little bit at a time. I found when I copied files larger than 800 meg at a clip I would have to reformat and it would say the card is damaged. It very well could be.
Since I got the card from a reseller on Amazon I'm going to see if I can get another one. Could be a bad batch. Next time I'll be weary of the resellers on Amazon, but that 100$ price tag seemed sweet.
Thx again.

[johntiger]

LOL we don't want to wait for OMJ we need our apps now now I said.......we all sound like my kids when it comes to these phones....... I kind of like breaking my phone just to see if I can fix it again. THe only thing I can't understand is how can they truely be broken. Is there no way to just start over. I see MAC IDs getting messed up but is the Android operating platform so wide open that it allows us to mess with stuff that should be chip specific? Just questions and oh yea my 4G is still broken 3rd phone. I talked to a buddy of mine at Sprint and he say's these phones have a hard time provisioning. Which makes since because I am unable to update my profile my 4G really shouldn't be broken (I flashed 1.6 without the new radio or wimax) so maybe I should flash the new radio and wimax from what I've been reading and maybe it will work?

[jfizz88]

SO what EXACTLy are the problems with 1.6r? just the broken wimax?

[johntiger]

Originally Posted by jfizz88

SO what EXACTLy are the problems with 1.6r? just the broken wimax?

Well I don't know. No one has really figured it out yet. I had 1.6r running fine on my first EVO before I got stuck in the rain storm with it. Ever since then the 2 replacements I've had are having 4G issues. other than that I have found any problems with them. I don't know why I'm so obsessed with 4G anyway since I only get service every now and then. The only real advantage is the ability to talk on the phone and surf the net with my normal 1 - 0 bars of 4G coverage 3G usually runs faster