Trying to install per this thread. But 4ext recovery does not start. It simply restarts the phone.
Help would be appreciated.
What name did you use for the recovery folder, on the root of your sdcard, which you put Haret and the other files into?
Trying to install per this thread. But 4ext recovery does not start. It simply restarts the phone.
Help would be appreciated.
What name did you use for the recovery folder, on the root of your sdcard, which you put Haret and the other files into?
Then you need to edit startup.txt to reflect this name change rel-path="4extrecovery"
Then you need to edit startup.txt to reflect this name change rel-path="4extrecovery"
Edit; or change the folder name back to exactly what it was originally (ie Whatever_it_was if rel_path="Whatever_it_was")
Edit; Actually, i just read the bit about installing recovery (post#3 of this thread) and the recovery mentioned (4ext_recovery2.2.7sd), is no longer on Xylograph's goo repository, and the above about editing startup.txt is not mentioned.
I will edit post#3 when i have a moment, but am not on wm ATM so can't test the ones that are there.
You have to expect broken and out of date links and guides to a certain extent, this is an old phone, Devs and users move on, hosting sites (and accounts) are closed down, hard disc drives get corrupted, etc, and it would be a huge amount of work to get everything up to date for the benefit of a diminishing number of new users.I wound up using "recovery_cwr_5.5.0.4_leo" because, as you said, the Xylograph file is no longer there.
This is an example of the issues I'm having - broken and out-of-date links. Isn't there SOMEPLACE where everything is up-to-date?
Thanks, with more thanks to come.
You are right in that all of the nand is used by windows phone. That is why there are edited recoveries for NativeSD, exactly like the one Poyensa mirrored in the post above yours. Have you tried it too? It should work for both wm and wp7.I have a problem with hd2 native-sd
My phone
EU HD2 Windows Phone 7.8 nand
bootloader magldr
32 GB class 10 sdcard ==> 10gb fat / 5gb Ext / 16gb wp
Native-SD android 4 versions
Some native-sd roms and even some recoveries
in fact anything that mount the cache partition
it stops at green htc logo then restarts
they boot when formatting nand for android
I think it is Because all of the nand is Windows Phone formatted
I will need a tutorial on how to fix the issue without removing the windows phone
I think this issue is on Windows mobile 6.5 too
And also a tutorial on how to change a rom's name before flashing
For native-sd , data on Ext , direct-sd
You are right in that all of the nand is used by windows phone. That is why there are edited recoveries for NativeSD, exactly like the one Poyensa mirrored in the post above yours. Have you tried it too? It should work for both wm and wp7.
Changing the rom name depends on which rom is being installed. tytung's roms involve editing ROM_NAME.prop in the boot folder of the rom.zip and init.rc in initrd.gz using linux. With some other roms updater script needs editing along with init.rc.
Why do you want to change rom name?
The ramdisk you posted seems to mount the cache first then move it to /data1st the problem is the roms that mount the cache partition such as sense 4 and 5 roms ... is there a way to edit them to work too
I already have a good recovery
I attached one of the kernels I am having this problem with would you edit it to stop mounting the cache partition
2nd about the rom name I am working on a little project of my own may own
and maybe if it works I will share it
The actual coding of this is a bit beyond my meagre skills, and i have no linux on pc at the moment. perhaps @gilbert32 might be able to help.on fs
# mount mtd partitions
exec /bin/busybox sh -c "/bin/e2fsck -p /dev/block/mmcblk0p2 > /fsck.log"
mkdir /NativeSD
mount ext4 /dev/block/mmcblk0p2 /NativeSD wait noatime nodiratime barrier=0
mkdir /NativeSD/primo
mkdir /NativeSD/primo/system
mkdir /NativeSD/primo/data
exec /bin/busybox mount --bind /NativeSD/primo/system /system
exec /bin/busybox mount --bind /NativeSD/primo/data /data
mount yaffs2 mtd@persist /mnt/persist nosuid nodev
mount yaffs2 mtd@cache /mnt/cache nosuid nodev
mount yaffs2 mtd@persist /mnt/persist nosuid nodev
on post-fs
# once everything is setup, no need to modify /
#mount rootfs rootfs / ro remount
# move cache to /data -TYT
mkdir /data/cache 0770 system cache
symlink /data/cache /cache
1st the problem is the roms that mount the cache partition such as sense 4 and 5 roms ... is there a way to edit them to work too
I already have a good recovery
I attached one of the kernels I am having this problem with would you edit it to stop mounting the cache partition
2nd about the rom name I am working on a little project of my own may own
and maybe if it works I will share it
2nd issue: just like Robbie P said.
First issue: you can comment the mount cache line, and i HIGLY RECOMMEND that you checkout ueventd.htcleo.rc. if it has a misc@mtd line, comment or delete it. That's what prevents many roms from booting on wm
on fs
# mount mtd partitions
exec /bin/busybox sh -c "/bin/e2fsck -p /dev/block/mmcblk0p2 > /fsck.log"
mkdir /NativeSD
mount ext4 /dev/block/mmcblk0p2 /NativeSD wait noatime nodiratime barrier=0
mkdir /NativeSD/primo
mkdir /NativeSD/primo/system
mkdir /NativeSD/primo/data
exec /bin/busybox mount --bind /NativeSD/primo/system /system
exec /bin/busybox mount --bind /NativeSD/primo/data /data
mount yaffs2 mtd@persist /mnt/persist nosuid nodev
mount yaffs2 mtd@cache /mnt/cache nosuid nodev
mount yaffs2 mtd@persist /mnt/persist nosuid nodev
on post-fs
# once everything is setup, no need to modify /
#mount rootfs rootfs / ro remount
mkdir /NativeSD/primo/persist
exec /bin/busybox mount --bind /NativeSD/primo/persist /persist
should be ok. I think some users had some problems with 3.03 on some roms.if i have the stock rom 3.14 and 3.03 hspl will i be able to flash android in sd card and have both of them? is the steps from page 1 the same or i have to do something else?
thanks