yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] sickleman:
It could be that- lack of the boot patcher. I don't remember if I flashed it after flashing the kernell while I flashed the ROM.

I'm really disapointed. I thought, that I've found something interesting, what can actually help you in your work, or help the others with this solution... Now I'm feeling like a fool.

To small amount of sleep I think... Thanks and sorry for waisting your time.
[G1 Android Development] Asswipe44:
Firerat, the Froyo by Laszlo rom ive been running for the past week has been great minus the fact that i have less than 20megs of space left.

I tried superwiping, applying your 1.5.6 recovery, then flashed the rom, flashed ezterry's kernel, and then 1.5.6 boot with mtdpartmap set at "65 2" and nothing changed. In other words, I've followed all listed instructions and the total data space remains 91.8 in sdcard & phone storage..

Attempting to make this work on a G1. Can you please help me out? I know I'm probly noobing something up.

I attempted to use 1.5.7b as well since I like new and shiny things, but failed utterly again. Next stop, 1.5.8 beta.
[G1 Android Development] tman7510:
trying to use your cm6.1-magpie

Firerat I am having some problems running your cm-6.1-magpie rom. I have a G1 and use radio 2708, using your mtd script set 90 2 but can't get the a2sd to work even though I give the rom permission to move apps and have the install location set to automatic. I know this issue is independent of the radio and mtd partitions but I just wanted to give you some information about how my phone is setup.

I also had some trouble trying to run your aio script...I may have set it up wrong but I entered the aio commands below my mtd config in ty mtdpart.txt file on the root dir of my sdcard and folloed the usual mtd install instructions. Wipe data,cache,system ,sd-ext, flash mtd-recovery.zip then flash rom and any extras the flash mtd-boot.zip but it just hangs??

Can you tell me where I messed up?
[G1 Android Development] Sleeepy2:
did you reboot after you flashed mtd-recovery.zip? then flash rom.

I just did it literary 5 minutes ago and it worked fine I used the 1.5.6 versions.
[G1 Android Development] tman7510:
Yes I did..I can get it to work without aio options in my mtdpart.txt but still have to move apps to sd manualy
[G1 Android Development] Sleeepy2:
OK I messed my Magic up something good.

Short story I had a Custom MTD Partitions and I wanted to remove it.

Steps are

use the remove zip.

then format syste,cache and data

either with

clockwork partition formats ( recommended )

Superwipe zip - search ( you may need to remove assert checks if you don't have

a dream/magic, its recommended if you use RA )

fastboot erase system -w ( not all that convenient, as you need to boot to

fastboot mode, above two are preferred )

Well I didn't have clockwork or superwipe and wasn't at my pc.

So I used rom manager to flash clockwork, reboot to recover, ran the zip, wiped with clockwork and went to restore a nadroid. I then get

Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:/nandroid/

Sd card is fine in pc, formated it on pc and from recovery still the same.

Also when I do df -h (adb shell on pc) I only get two lines

tmpfs 95.9M 0 92.9M 0% /dev

/dev/block/mtdblock4 80.0M 1.1M 78.9M 1% /cache

Fastboot sees the sdcard fine so I tried to re-root and used a sappimg.zip but the next steps are to flash some stuff from recovery and it doesn't see my sdcard.

Helllllp
[G1 Android Development] tman7510:
I would fastboot erase system -w

then do a fresh flash of your recovery.img either RA or what ever you want to use...I think that will solve your problem. I'm not having any problems with my G1...just wish I didn't have to move apps 2 sd manualy with Firerats cm6.1-magpie
[G1 Android Development] Sleeepy2:
thanks for the idea but that is part of the problem, that I should have mentioned.

I don't have an engenering spl I have 1.33.0009 so I get signature verify fails trying to fastboot flash recovery and hboot.

I am following the guide from theunlockr.com and I am supposed to fastboot boot recovery and then flash the update.zip which is the spl. and boom now you see where I am stuck. can't see the damn sdcard.
[G1 Android Development] tman7510:
try this link http://xdaforums.com/showthread.php?t=529019
[G1 Android Development] Sleeepy2:
yeah that is exactly what I am trying to do. The part where it says

"Choose Apply sdcard:choose zip and select the required SPL update "

is the part that isn't working. can't mount sd card

>:(
[G1 Android Development] tman7510:
Flash RA recovery...in recovery mode drop to console...at prompt type mount -a then type recovery then you should be able to flash what ever you want from your sdcard
[G1 Android Development] Sleeepy2:
fastboot flash recovery gives signature verify fail.

can't drop to console as I am using a magic.

tried booting to recovery.

ran adb shell

mount - a

mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory

mount: mounting /dev/block/mmcblk0p2 on /sdcard failed: No such file or directory

I am going to bed now so if you have any other idea's just throw them up here and I will try again tomorrow.

Thanks for helping.
[G1 Android Development] tman7510:
I found your problem :(

the reason you are getting the signature error is because :

Flashing Recovery via fastboot * Requires engineerings SPL!

you need danger spl!!!
[G1 Android Development] Sleeepy2:
Exactly. And how do I get an engenering recovery without access to my sd card.

FUUUUU
[G1 Android Development] johnson8cyl:
Can u boot into the os to flash amon_RA from the terminal?
[G1 Android Development] Sleeepy2:
Nope. Bootloop.

Can I do that with adb shell on the pc?
[G1 Android Development] tman7510:
Hey ma your the one who Fu$%ed up your phone some how so don't get pissed off at me for pointing out that you need a custom spl to flash recovery from fastboot. I won't waste my time trying to help u out anymore :cool:
[G1 Android Development] johnson8cyl:
Not without a custom recovery already installed. Follow the instructions under if u get stuck without a recovery in ezterry's radio/spl thread in the op
[G1 Android Development] Sleeepy2:
I tried that

Failed (remote: model id check fail)
[G1 Android Development] AndDiSa:
Did you really try to flash the orange-1.58.73.2.nbh res. SAPPIMG.nbh file? Otherwise I would suggest you to read the OP of that thread again and give it a try.
[G1 Android Development] Sleeepy2:
Nope I have a magic so I tried SAPPIMG.nbh.

Current HBOOT 1.33.0009 Radio 3.22.20.17

My phone thinks it is a Vodafone
[G1 Android Development] Cherokee007:
Hi I would like to ask how I know that my custom MTD works. Try it

the instructions to launch in the first article and I'm not sure that it running correctly. Thanks
[G1 Android Development] AndDiSa:
Go to the console and enter:

df -h

If your mtd-settings correspond to the partition layout you see now on your screen, it' working ;)

Responding seriously: what values did you configure? What is the output of the command above?
[G1 Android Development] Cherokee007:
In the text file on my sdcard is echo "MTD 98 2 ", text file is called

mtdpartmap.txt. I do not know what the statement does not need me to write by hand. Please advice because they still do not know if my custom function MTD.
[G1 Android Development] wjsturgis3:
Does the file on your SDcard contain the entire phrase echo "MTD 98 2", If so it is in error, it should only contain "MTD 98 2" with out the quotes. This would result in a system partition of 98MB and cache 0f 2MB. In terminal the command: df -h will display the partition sizes. This will verify if your MTD worked. The command: adb shell df -h will provide the same info.
[G1 Android Development] i@jim:
Need to run boot patch after remove?

Hi All:

Sorry to bother you. I tried installing firerat's custom MTD partitions without success. Then I flashed the "remove" zip, and all seems back to normal. Now I'm going to reflash my ROM (aospCmod 2.3.3) and gapps as usual, then reboot.

My question is: do I need to run firerat's boot patch?

And if so, then my second question is: (sorry if this sounds stupid!) which of the files in the OP is the "boot-patch.zip"?

Thanks in advance.
[G1 Android Development] Sleeepy2:
No you don't need the boot patch if you removed the custom MTD
[G1 Android Development] picklerick:
Do I have to wipe and reinstall everything if I update or change my recovery image?
[G1 Android Development] :
Technically, if I did "mtd 200 2", I would have 54 mb of data and 2 mb of cache?
[G1 Android Development] AndDiSa:
Yes, but do a nandroid/bart backup before. After you've patched the new recovery you can restore it and you are done.

But why do you want to change your recovery?
[G1 Android Development] akashkotak:
How to revert back to Orignal MTD for desire ?

Hi I woukd like to know How to revert back to Orignal MTD for desire ?

I just patched FR-recovery-v1.5.6-CustomMTD_S and FR-boot-rpp-v1.5.6-CustomMTD_S

Thanks
[G1 Android Development] Freeport36:
Thank you...

I use your MTD on my Hero and wanted to thank you for some time now... Your account is now a bit larger!!!
[G1 Android Development] punshkin:
this question may be stupid but:

i have the 2825 radio and 1.33.0013d hboot kombo to get the extra RAM

if i apply the custom MTD patch. will i loose the extra RAM?
[G1 Android Development] AndDiSa:
Please don't mix up RAM and internal memory. These are two completely different things.

To answer your question: there is no problem to use 2708 combo with CustomMTD. As you see in my signature, I am running the same combo at the moment. In my signature you can find, too, all appropriate links to set up everything.
[G1 Android Development] punshkin:
thanks

yeah i know ram and internal memory is something different. i wasnt sure if the MTD flash includes a radio or hboot.:confused: but yah... thank you :)
[G1 Android Development] leader288:
On the mediafire folder there are different versions: 1.5.6, 1.5.7, 1.5.8. WHich one can I use to flash my Desire? Or do I need to use the script here: http://xdaforums.com/showthread.php?t=806321&highlight=custom+mtd
[G1 Android Development] bonesy:
im just curious if i can resize my /data to increase my /system partition??

/ # df -a -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.4M 0 95.4M 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
/dev/block/mtdblock4 3.0M 1.1M 1.9M 38% /cache
/dev/block/mtdblock3 197.0M 1.1M 195.9M 1% /system
/dev/block/mtdblock5 265.8M 1.1M 264.6M 0% /data

if my mtdpartmap.txt was say

mtd 250 3
mtd 5 4
mtd 210 5

Would this work?

Oh and 1.5.8 works on Hero GSM
[G1 Android Development] Sleeepy2:
yes you can make system bigger which would then decrease data.

your mtdpartmap.txt only needs the mtd 210 5 line.

not sure why you have more than 1 line and I am not really sure what effect that will have but yes increasing the system makes data smaller.

Remember the first number is the size that you want your system partition so 210 and then the next is your cache 5 then everything that is left becomes data.
[G1 Android Development] fldash:
Has anyone modified the source for this to allow you to resize boot partitions? I have bad nand blocks on my EVO keeping me from being able to flash certain boot.imgs. It seems I could modify the source to do this, but I'm a little apprehensive as I'm not a great coder. Thought maybe someone may have already done it.
[G1 Android Development] fldash:
I spend all morning working on this. I modified the source to resize boot partition. I did a few testruns and the commandline seems to be correct for my EVO. Resizing from 2.5M boot partition to a 3M boot partition, 350M - 400M system, and 160M - 110M Cache

mtdparts=msm_nand:12288K@0x00003F360000(wimax),640K@0x00003FF60000(misc),5120K@0x000004240000(recovery),3072k@0x000004740000(boot),409600k@4A40000(system),112640k@0x1DA40000(cache),437376k@0x24840000(userdata)

Here was my original dmesg:

wimax 0x00003F360000 0x00003FF60000
misc 0x00003FF60000 0x000040000000
recovery 0x000004240000 0x000004740000
boot 0x000004740000 0x0000049C0000
system 0x0000049C0000 0x00001A7C0000
cache 0x00001A7C0000 0x0000247C0000
userdata 0x0000247C0000 0x00003F360000

Unfortunately, it doesn't work. Upon rebooting into recovery (which is what I'm trying to apply the commandline to first, I can't even pull dmesg fast enough to see the MTD mounts... First lines in my dmesg are:

[ 9.256042] msm_nand_block_isbad: unsupported block address, 0xba00004

[ 9.256256] msm_nand_block_isbad: unsupported block address, 0xba20004

[ 9.256408] msm_nand_block_isbad: unsupported block address, 0xba40004

Quite a few of them...

I check /proc/mtd and this is what I get:

mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00500000 00020000 "recovery"
mtd3: 00500000 00020000 "boot"
mtd4: 15b80000 00020000 "Partition_004"

So looks like it bombs trying to mount the system partition for some reason...

I did try a normal resize (resizing system/cache using the default script) and it worked fine and I got no errors. Must be something with resizing the boot partition that the kernel doesn't like or MTD doesn't understand.

Anyone have any thoughts?
[G1 Android Development] ldrifta:
[Q]

just curious what ecactly is the fr_remove file for? i couldnt find any description or refference.. but what does it "remove" exactly?
[G1 Android Development] AndDiSa:
It removes the mtd configuration settings from the kernel parameter list.
[G1 Android Development] ldrifta:
so basically it returns it back to how device was before using fr recovery and fr boot??
[G1 Android Development] AndDiSa:
... before flashing fr-recovery, because the boot patch is to be applied to the rom kerne separately. Principally it's the following:

fr_recovery is patching / modifying the kernel parameters for the recovery kernel

fr_boot is patching / modifying the kernel parameters for the rom kernel

Both (recovery kernel and rom kernel) must be synchronized, i.e. if you remove the fr_patch from recovery you need to install a kernel *without* mtd patch, if you patch the recovery using custom mtd you need to patch the rom kernel, too.
[G1 Android Development] ldrifta:
ok so if i flash fr_remove than i will be able to flash roms as i normally did? what is the proper way to flash remove?
[G1 Android Development] AndDiSa:
yes, you are.

fr_remove can be flashed normally using recovery mode, but then you should reboot to bootloader and do a

fastboot erase system -w

to cleanup the system.
[G1 Android Development] sickleman:
Ok, I'm stuck. Again.

I have 1.33.0013d hboot, 2.22.28.25 radio and RA-dream-v1.7.0 recovery and I can't flash any custom mtd patch without loosing possibility of using bash scripts and commands.

When I type in terminal emulator for example: "ls" I get "ls: permission denied" or "ls: not found" (if I typed before "su"). Su requests are executing without su rights (root explorer is requesting su at start, but nothing happens after it)

I'm sure that I flash custom mtd patch in the proper way (I'm sorry if it's not).

("fastboot erase system -w",flash Recovery Patcher, reboot, check the /system/ size with terminal in RAdream recovery, flash ROM and flash Boot Patcher)

I was trying 1.5.8 and 1.5.6... Rom is booting with all scripts, without custom mtd everything is ok.

I've got some rooting issues before. I flashed clockwork recovery v3 and I loosed root... Then I rerooted it.

Before all this everything was ok. Could it be the source of my problems? How can I repair it?

I'm also trying to rewrite installer scripts for some ROMs. It seems that if I make a mistake with some permissions it could induce similar issues. (I attached updater-script with *.txt extension and janitor.sh) Can someone look at this to make sure that everything with system permissions is ok? All of these is based on scripts found in this forum. (in most on FroyobyLaszlo5.2, but also COS, BeatMod, cyanogenmod maybe and of course boot-v1.5.8-CustomMTD_S.zip/FR-boot-rpp-v1.5.6-CustomMTD_S.zip)
[G1 Android Development] ldrifta:
aftre you flash the recovery i believe your supposed to wipe again.. im pretty sure.. maybe try to re flash you mtd... wipe data, cache, system... flash recovery than power off... wipe data, cache, system again.. than flash rom and fr_boot and reboot.. try this hope it helps...

has anyone done the fr_remove yet? how exactly do i do it? are there steps..? do i just flash remove via recovery than wipe data, cache, system..? is that all i need to do?
[G1 Android Development] AndDiSa:
- flash fr_remove-xxx.zip

- reboot to bootloader

- fastboot erase system -w

and you are done.
[G1 Android Development] sickleman:
With wipeing all is the same...

I figured out, that busybox hardlinks/symlinks are missing... Every bin what is phisycally on the filesystem is working good...

Is there any way to relink this to /system/sbin/

like this (for example):

ln /system/sbin/'busybox cp' /system/sbin/cp

? I was thinking about "alias" too, but It's not working... Any help please!

Why all this happens?
[G1 Android Development] elfasito:
I have a problem, I removed the customMTD with FR-remove. to install a new recovery, well done flash the new recovery. I start to flash again customMTD,

* flash-recovery FR

* flash rom

* FR-boot flash

good turn on the terminal, I'm going to see the memory, to verify that the correct flash customMTD. and did not appear but the internal 117mb, I only appear 67MB. apparently not detected customMTD

PS: I have tried to flash again customMTD
[G1 Android Development] lbcoder:
Fastboot works much lower on the phone's software stack than adb... so just because something messes up with adb doesn't mean that anything will be wrong with fastboot.

Second, have you tried a proper operating system? I.e. FEDORA (not windoze)... there are a whole bunch of barriers working against you in windoze. From just about any Linux, things should *just work*.

Are you able to even mount the phone's filesystem on a computer to transfer files to/from the sdcard? If the answer there is YES, then the phone is definitely fine.
[G1 Android Development] kalpa11:
I need a little bit of help here please. I used your mtd partition patcher so I could use the Cyanogen mod 6 nightly rom after a while I wanted to go back to my previous cynogen mod 4 that i had nand backed up. when I restored though all my user data had been gone. I am guessing this is because my nand is still partitioned. Is there a way I can go unpartition (if that's the word) so all my userdata will be back when I restore again.

Oh and by the way i have a mytouch 32B model
[G1 Android Development] rsxtypes72:
I may be wrong but I will say no.

You have to do a "fasboot erase system -w". If you do any changes, and I mean ANY changes you have to do an erase system.

Also - LBcoder you are refering to me but I do have the lastest version of Ubuntu installed. I have a dual boot on my laptop. Windoze and Ubuntu.
[G1 Android Development] FatBoyExtraordinaire:
That's the thing, I am not able to (I use an SD Card reader) which leads me to believe that indeed my usb port may be dead and may have just coincided with me rooting my phone.
[G1 Android Development] jon6206:
Firerat,

Implemented this with Defcons latest CM6 nightly test 12 and its great I got 82.61MB Available. Thank you for this!
[G1 Android Development] ttabbal:
You could set it to whatever it was when you had that ROM, that's basically the same as "unpartitioning". Or you could just flash the boot patcher after restoring the nandroid backup. That would get the old ROM working fine and is easier than remembering what your partition map looked like for every backup. :D
[G1 Android Development] FatBoyExtraordinaire:
By the way, although it seems I may have to sit out the latest batch of froyo based roms due to my issue, I want to again thank you Firerat and lbcoder for taking the time out to listen to my problem and trying to help me find a solution.
[G1 Android Development] alritewhadeva:
Quick Question; can you *SHOULD YOU* apply this patch if you have the danger SPL? and if you do what are the advantages/disavantages
[G1 Android Development] Firerat:
a larger data partition

you can get at least another 28mb on data

not looked at cm6 rc1 yet, but if it has the same footprint as the 'last' nightly, the you could get an exrta 33mb,, stick with a 90 2 to be safe ;)

Edit: fresh install of CM6.0.0 RC1 ( as seen in recovery )

Filesystem Size Used Available Use% Mounted on
tmpfs 47.8M 0 47.8M 0% /dev
/dev/block/mtdblock4 2.0M 1.2M 852.0K 58% /cache
/dev/block/mmcblk0p1 7.0G 6.4G 651.2M 91% /sdcard
/dev/block/mtdblock3 90.0M 88.3M 1.8M 98% /system
[B]/dev/block/mtdblock5 117.8M 1.2M 116.6M 1% /data[/B]
[G1 Android Development] albatorcobra:
Hi,

I cannot boot on defcon-cm-6.0.0-DS-RC1-full.

My recovery is patched with FR-MTD-PartHack-recovery-v1-3_S.

I tried:

- AutoMTD_partitionPatcher_v1-1 from my linux box

- FR-MTD-PartHack-boot-v1-2_S_S from recovery

Same result with both method, my G1 cannot boot, it is stuck on G1 boot screen with no adb.

I had the same issue with previous patch on CM508.

My file /sdcard/mtdpartmap.txt is:

mtd 90 2
spl 1.33.2005

My spl is HardSPL and I did fastboot erase system -w.

It seems that the boot pacher doesn't work on my G1. My CM508 works only with a custom boot img.
[G1 Android Development] Firerat:
we have seen that the newer kernels are not working on 0.95.3000, I guess we can add 10.95.3000 and no doubt 0.95.0000

1.33.2003 , is a full engineering SPL. but with the same partition layout as the above ( i.e. its not the same as danger )

the safest way to switch to 1.33.20033000 is

fastboot erase system -w ( especially if you have a custom layout now )

fastboot erase recovery ( important )

fastboot boot recovery.img ( a stock recovery )

flash spl_1_33_2003.zip

fastboot boot recovery.img ( reboot would have prompted you with fastboot mode )

spl flash completes

you can then confirm HBOOT 1.33.20033000

and flash your recovery back

fastboot flash recovery recovery.img
[G1 Android Development] albatorcobra:
Ok, thank you. If this is kernel relative, I think I will try to build a custom kernel.
[G1 Android Development] Firerat:
yes, I belive it is

when I was on 0.95.3000, I could only get cm5.0.8 booting with a custom kernel

( only real difference was I compiled bluetooth as modules )

as a diagnostic, you could try fastbooting CM6's kernel

e.g.

fastboot boot boot.img

where boot.img is the one extracted from cm6's zip

the CM5.0.8 kernel would boot like this, but not when flashed

currently I'm compiling a kernel from github, with same config as cm6 rc1, but without support for sapphire, this may reduce the kernel size enought for it to be bootable when flashed

Edit ,. only 12k smaller, will look closer at it
[G1 Android Development] Firerat:
I have uploaded a custom kernel for CM6rc1 kernel, with bluetooth as modules

you can find it in post 2 of this thread

NB, this is only needed if you are having problems with CM6rc1 not booting

i.e. if you have 0.95.0000*, 0.95.3000 , 10.95.3000

* 0.95.0000 is not recommended if you are resizing your MTD partitions, simply because you can not use fastboot erase to get out of trouble if you end up with have un-deletable files in system, cache or data, or render them un-mountable **

** however , if you have clockwork and can use adb, then clockworks erase_image binary will get you out of trouble

adb shell
for i in system cache userdata;do erase_image $i;done
[G1 Android Development] albatorcobra:
I did fastboot boot boot.img with the boot.img extracted from CM6 but nothing happened, I was stck on fastboot image. Afer a while it rebooted into recovery.
[G1 Android Development] albatorcobra:
Ok I have just flashed your boot image on my G1 with 10.95.3000 SPL. It is worksing fine whith CM6RC1. Thank you very much.

But I don't understand why it is not working with stock kernel.
[G1 Android Development] bigdbag:
Can someone put a mirror to that rapidshare link of the CM6RC1 patch? I can't load rapidshare at the moment apparently.