yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Firerat:
well, yeah, kind of

the browser doesn't work

others got the browser working by replacing the the MT Slide /framework/ with the /framework from some other, older , espresso rom

I keep saying to myself I'll go back and have ago at a proper fix ( which shouldn't be too difficult since the mt slide is out now )
[G1 Android Development] Flaming Cow:
I don't use the brower that much so it shouldn't really matter, but if it fits and works fine than I'm going to try it.:)
[G1 Android Development] robuser007:
I cant get it to work with .2003 spl with the latest cm's builds.
[G1 Android Development] Firerat:
but your spl is 1.33.2005 ?

your sig

does your /sdcard/mtdpartmap.txt look like this

mtd 90 2
spl 1.33.2005

?

edit:

here is the relavent code

recoverymode ()
{
mapfile=/sdcard/mtdpartmap.txt
mount /sdcard
# new mtdpartmap config
if [ -e $mapfile ];
then
busybox dos2unix $mapfile
if [ "`egrep -q \"mtd|spl\" $mapfile;echo $?`" != "0" ];
then
SystemMB=`awk '{print $1}' $mapfile`
CacheMB=`awk '{print $2}' $mapfile`
if [ "$CacheMB" -lt "2" ];
then
# need at least 2mb cache for recovery to not complain
CacheMB=2
fi
else
SystemMB=`awk '/mtd/ {print $2}' $mapfile`
CacheMB=`awk '/mtd/ {print $3}' $mapfile`
FakeSPL=`awk '/spl/ {print $2}' $mapfile`

if [ "$SystemMB" = "" ];
then
SystemMB=90
fi

if [ "$CacheMB" = "" ];
then
CacheMB=2
fi
fi
else
SystemMB=90
CacheMB=2
FakeSPL=""
fi

if [ "$FakeSPL" = "" ];
then
CLInit="$CLInit"
else
CLInit="androidboot.bootloader=$FakeSPL $CLInit"
fi
return
}

you must patch recovery with the new style config for it to work
[G1 Android Development] robuser007:
I'm not sure how to do this.
[G1 Android Development] Firerat:
put this on your sdcard

flash recovery

reboot
[G1 Android Development] sisterchick:
New patch issue?

Is something amiss with the newest patcher? I'm running a G1 with Amon-RA 1.7 and 1.33.2005 Danger SPL. I re-flashed Amon-RA 1.7.0 recovery along with new recovery patch and installed 08072010 CM6 nightly. I've not got my 30MB extra space.
[G1 Android Development] Sik-1:
bump, no matter how i rewrite the mtdpart.txt, its not reading it and linking anything, going back to the old patches for now
[G1 Android Development] robuser007:
That didn't work, tried a few times, back on dangerspl (my signial problems seems gone now since I flashed android RC7).
[G1 Android Development] izzy001:
I had the same problem a while back, all I did was reformat my SD card and put the patches and rom back on there and it worked.
[G1 Android Development] Firerat:
it should work.

I was using 0806 nightly for testing, I'll try 0807 now

Edit:

just flashed 0807, and all seems fine

is your recovery showing 30mb cache?
[G1 Android Development] Sik-1:
mine was showing the same 30mb on cache until i went back to the old scripts and everything back to being hacked lol, so far the only thing i can think of is the mtdpartmap.txt....

i tried it both ways posted in the op and nothing worked and wen going back to the old script it works just fine
[G1 Android Development] Firerat:
OK , I'll have a proper look at it tomorrow

but I've just tried with and without mtdpartmap.txt, and both worked fine

I've even d/l from the OP just to make sure
[G1 Android Development] kwrose14:
AutoMTD_partionPatcher_v1-5-1.zip

Am I correct in thinking this is flashable in system recovery ? I have created the md5sum file for it and it continualy give me a response of no signature, verification failed when I attempt to do so.

Am I thinking about this all wrong ?

Thanks
[G1 Android Development] Firerat:
I'm guessing you are using clockwork rec ( 2.5)

For some reason the sig fails, but you can toggle it off
[G1 Android Development] kwrose14:
Actually I am using RA-dream-1.7 recovery.

Any other suggestions? I have recreated it several times and am at a loss for a solution myself.
[G1 Android Development] Firerat:
well in that case I haven't an effing clue what your on about

What are you recreating, how and why?
[G1 Android Development] kwrose14:
Actually I am using Ramon 1.7 and am at a loss for a solution myself.
[G1 Android Development] kwrose14:
I have recreated the checksum file several times in order to try to resolve the error and get it to perform.
[G1 Android Development] Firerat:
you have failed again

what is the answer to the question

how?

I will get bored trying to drag information out of you
[G1 Android Development] kwrose14:
My appologies. I used the numbers provided next to the download and saved it as a md5sum file like I have always performed in the past for any other file necessary.
[G1 Android Development] billquinn1:
I have a guess... Maybe he is renaming the zip on his computer so he is doing the old ".zip.zip" thing windows users sometimes do.

Just a guess.
[G1 Android Development] Firerat:
nah, they have already demonstrated that they have a lack of understanding and can not answer simple questions, which means they cannot ask themselves, and answer, simple questions.

conclusion:- user error

errm, why?

it seems you have been wasting a lot of effort and time

I provide the md5sum so you can dbl check the file is 'good'

the sig check is within the zip file, if its failing it might be a bad download, but I have noted that clockwork 2.5 ( 2.5.0.1 ) fails, idkw it works fine in ra_1.7.0, but you can turn the check off.

the way my flashable zips work is like this:

I zip the files

I sign with this very simple script

java -jar ~/bin/signapk.jar ~/bin/testkey.x509.pem ~/bin/testkey.pk8 $1 FR-`basename $1 .zip`_S.zip

where $1 is the full path to the zip file, the FR-`basename $1 .zip`_S.zip bit is the output file.

I'm not going to do anything silly like rename a none-signed zip to that, the _S on the end tells me I signed it
[G1 Android Development] kwrose14:
so from what your saying if I understand correctly, I can delete the md5sum file for that and it will execute just fine.

Thanks for your patience and understanding.
[G1 Android Development] kwrose14:
Just tried again without the md5sum file and it told me it Failed, No Signature.

Now what's a man to do ?
[G1 Android Development] fredptc:
is anybody get a stay at 1st animation of "TMO G1"? when applying 1.5.1?

I think it was ROM issue before, but now i'm confused...
[G1 Android Development] Firerat:
I promise its all fixed now in v1.5.2
[G1 Android Development] kwrose14:
I tried to flash the updated file and still not working for me.

Install from SD Card

Finding Update Package

Opening Update Package

Verifying Update Package

E: No Signature (1 files)

E: Verification Failed

Installation Aborted

Am I going about this all wrong? - shrugs -
[G1 Android Development] Firerat:
I really do hope you are not trying to flash the AutoMTD file

which would mean you didn't read and understand the OP

( its the only zip that contains just 1 file )
[G1 Android Development] sunzoje:
worked like a charm with 1.5.2 version on amon_ra 1.7 recovery and cm6 nightly 8/9. but had problem with clockwork recovery 2.5.0.1 .. thnx firerat ...
[G1 Android Development] Firerat:
was it a signing problem?

because yeah, I've been having that as well, so I toggled the sign check off

no idea why its not working, as the sig works fine in RA1.7.0.

its not just files I sign that are broken either cm_nightly failed the sig check, but at least the toggle works :)
[G1 Android Development] sunzoje:
it was not signing problem. just the patch didn't work. also whenever i do sdcard format in clockwork, it borked the card.
[G1 Android Development] fredptc:
i download chromatci 4.3, rom is 61Mb. i set mtdpartmap as 65 2;

i use 1.5.2 for recovery&boot.

now after flashed all steps, i can't boot into system, just reboot autmatically to recovery 1.7.0...looks lite it;s indicating something?? lol
[G1 Android Development] usrbrv8:
Great work

Firerat,

Great work, your instructions where easy to follow.

/dev/block/mtdblock3 92160 88520 3640 96% /system

/dev/block/mtdblock5 120576 69996 50580 58% /data

/dev/block/loop0 4096 4096 0 100% /system/xbin

/dev/block/mtdblock5 120576 69996 50580 58% /cache

/dev/block/mtdblock4 2048 776 1272 38% /dev/cache

One question, as I understand it the next time I want to flash a ROM CM6 nightly or R3/Final (when it comes out). I do as follows?

nandroid

flash new rom

flash FR-boot-v1-5-MTD-PartHack_S.zip

reboot

Is that correct?

Thanks
[G1 Android Development] kwrose14:
thanks Firerat

Have this working and its awesome, big help for the builds.

Thanks once again for assisting and providing us G1 owners with something great.
[G1 Android Development] raven_raven:
As long as you don't change partition layout via mtdpartmap.txt or flash new recovery the order is good, expect one thing. You should wipe data, cache and system before flashing a ROM. Just saying.
[G1 Android Development] Firerat:
Well, you only *need* to wipe if you resize, no real need to wipe if for instance you are flashing a new nightly.
[G1 Android Development] Abolfazl:
/dev/block/mtdblock3 90.0M 83.9M 6.1M 93% /system
/dev/block/mtdblock5 117.8M 14.8M 102.9M 13% /data
/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 446.9M 56.1M 367.0M 13% /sd-ext
/dev/block/mmcblk0p2 446.9M 56.1M 367.0M 13% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
/dev/block/mmcblk0p2 446.9M 56.1M 367.0M 13% /data/dalvik-cache
/dev/block/vold/179:1 6.7G 1.4G 5.3G 20% /mnt/sdcard

Works great!

So when I want to update a new nightly I just make a backup (nandroid), flash new .zip? Or do I also have to apply the FR-boot after
[G1 Android Development] Firerat:
you will need to flash the boot patcher ( after you flash your nightly )
[G1 Android Development] foxtrickle:
If I restore from a Nandroid that had the boot patcher flashed on it, I won't have to flash again, will I?
[G1 Android Development] Foo_Blyat:
jesus christ how many times can multiple people ask the same damn question over and over when its already been answered.

ANYTIME YOU FLASH A ROM

OR A KERNAL

OR A NANDROID

YOU MUST REFLASH THE BOOT.

so if i flash a nightly, i flash the boot.

if im on a rom and decide to try a new kernal, i flash the kernal, flash the boot, reboot...

come on people, you arent that simple are you.....?
[G1 Android Development] Foo_Blyat:
Heres a question i dont think you've gotten yet firerat,

i just rooted my buddies Sprint Hero CDMA and flashed him with CM6. You have written

"Applicable to..

Probably any device that uses the same kind of nand as the G1 MT3G ( msm_nand )

The intial scripts are geared towards G1 / MT3G. however I have 'rewritten' much of the script for v1.5 , it now reads the partition table in dmesg, so it _should_ be universal **"

His phones internal memory is a piss poor excuse of ideal storage so i want to help him out and flash your MTD hack on it.

Will it be just as safe and efficient as when i flashed it onto my MT3G?
[G1 Android Development] foxtrickle:
A simple "yes" would have sufficed, but clearly, you need to vent and call me "simple".

Sorry, I read the entire thread and didn't see nandroid in particular being addressed. Maybe I missed it, but either way, it didn't seem like my question was too illogical.
[G1 Android Development] billquinn1:
It's a long thread.
[G1 Android Development] Firerat:
nah.. only 10 pages

besides, the answer is in the OP and post 3 (FAQ)

and it has been asked, idk four or five times, it does get 'old'
[G1 Android Development] foxtrickle:
Sorry to bother. Thanks for all your work.
[G1 Android Development] arefin:
may be I have missed it, but this is a good question no doubt :-)

also a good candidate for the FAQ section on the second post.

the question: how cab I revert back to original/stock partition layout?

simply flashing clock work or amon should do it or we need to do something more?

thanks for your patience in advance :)
[G1 Android Development] Sik-1:
simply flashing another recovery should revert u back to stock, enjoy
[G1 Android Development] arefin:
many thanks, just thinking of exploiting the firerat's a2sd script.

cheers
[G1 Android Development] Firerat:
well, the a2sd is now in the 'All in one' ( v1.3.8b )

which is independent of CustomMTD

However, I'm going to include support in CustomMTD

basically the boot patcher will check your config, look for the latest fr-patch138+ on sdcard, and then run it with the options you want ;)

I may actually have an option to write the config for you if your using the fr-patch in interactive mode

( then I might get round to learning this java stuff )
[G1 Android Development] Foo_Blyat:
I stopped by my buddies house to put all the files onto his sdcard for flashing but his phone was at 19% so i didnt get to proceed with it.

i did get to pull this before leaving

C:\Users\*****>cd C:\android-sdk-windows\tools

C:\android-sdk-windows\tools>adb shell
/ # dmesg|awk '/0x.+: "/{ print }'
dmesg|awk '/0x.+: "/{ print }'
[ 4.835540] 0x1ff60000-0x20000000 : "misc"
[ 4.837188] 0x02c60000-0x03160000 : "recovery"
[ 4.838470] 0x03160000-0x033e0000 : "boot"
[ 4.839965] 0x033e0000-0x0dde0000 : "system"
[ 4.841552] 0x0dde0000-0x15fe0000 : "cache"
[ 4.842987] 0x15fe0000-0x1ff60000 : "userdata"
/ #

I didnt get to run that code to save a sprintcdma.txt to my sdcard but im just going to flash it next time hes got a full charge anyway.
[G1 Android Development] Firerat:
post your recover log
[G1 Android Development] Firerat:
looks ok, but I noticed it has less 00s

I actually strip them in the script, but it would fail with these, so ...

I have reverted that 00 strip ( not really needed anyway )

have to test it a bit more
[G1 Android Development] Firerat:
I've re-jigged the script in 1.5.3 a little bit ( see OP ) , you should use that version
[G1 Android Development] Foo_Blyat:
roger that, ill download them onto my laptop and get them onto my buddies phone when i see him next
[G1 Android Development] Foo_Blyat:
Well everything went smoothly, worked very well on the CDMA Hero, had massive gains to the internal memory and the phone is blazing fast.

i think it went from somewhere like 179mb to 350.

awesome work firerat!!
[G1 Android Development] Foo_Blyat:
i linked this thread over to the guys over in the Hero CDMA android development forum, gotta share the wealth ya know.

im still very proud to say i was the first person in the world to try your mod on a hero cdma and without breaking, messing up, or bricking anything. your patches and mods are as smooth as silk brotha!!
[G1 Android Development] xPreSiDenT:
Works great man!!! Thanks for the help, and thanks for the awesome tool. My G1 seems to learn a new trick every other day :D
[G1 Android Development] elfasito:
a question, sorry

can be applied to: recovery 1.6.2g ? 1.7.0 or is it necessary?
[G1 Android Development] Firerat:
good question,

I think it should be ok with 1.6.2

let me know what you find out
[G1 Android Development] elfasito:
thanks, I echo these steps

1. download FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip

2. * Configure Optinally

3. reboot to recovery

4. nandbackup

5. cache + data wipe

6. FR flash-recovery-v1.5.3-CustomMTD_S.zip

7. reboot to recovery (reboot and hold Home)

8. Nandrestore

9. FR-boot-flash-CustomMTD_S.zip v1.5.3

10. reboot

the previous rom that had this working, but now I want to apply a Froy, I have to do? I do all the steps back to apply another rom?.

otherwise, as I can I know that path was applied correctly?

and one last thing. did not understand step 2. I have not configured anything!
[G1 Android Development] Firerat:
you have quoted a section of the OP, but it seems that you did not read it all

also read post 2 the FAQ it answers your question about doing all the steps.

you will also find the same question crops up in the thread a few times, it gets very boring.

ref configuration, read about it in the OP.

type less, read more
[G1 Android Development] elfasito:
as you said I started to read. While this is what I understood:

* When trying to flash for example CM6-rc3

be used FR-CM6RC3-bootimg4NoneD-AutoMTD.zip

FR because with flash-recovery-v1.5.3-CustomMTD_S.zip, generates conflicts with the kernel.

While this means I have to use FR-CM6RC3-bootimg4NoneD-AutoMTD.zip in step 6.

* Answering the next question was hise, is required for all steps again before a new rom?

not only apply the boot path, then flash the rom, unless it generates a conflict with the kernel again.

good I hope correct me if I'm right.

I am using a translator because I speak Castilian
[G1 Android Development] Firerat:
What SPL do you have?

FR-CM6RC3-bootimg4NoneD-AutoMTD.zip is for

0.95.0000

0.95.3000

10.95.3000

what conflict?

flash recovery patcher

reboot

flash rom + extra

flash boot patcher

if you flash new ROM, Kernel or restore nandroid

flash boot patcher

if you flash new recovery

Flash recovery Patcher

if you want new MTD Size

Flash Recovery patcher

nandbackup

format system,data,cache ( with clockwork or faastboot erase system -w )

reboot to recovery

nandrestore

flash boot patcher
[G1 Android Development] elfasito:
I was totally wrong.

my spl is: 1.33.2003

this means that I need not apply this path: FR-CM6RC3-bootimg4NoneD-AutoMTD.zip!

then I do not see the problem.

* Flash recovery patcher (FR-recovery-v1.5.3-CustomMTD_S)

* Reboot

* Here's where I come, because when you try to flash a new rom (Froyo), the installation is aborted.

succeeds in making the whole process using the Nandroid the first time, namely:

* Wipe all

* Flash recovery patcher (FR-recovery-v1.5.3-CustomMTD_S)

* Reboot (recovery mode)

* Nandrestore

* FR-boot-flash-CustomMTD_S v1.5.3

may be a failure of the flash Froyo not do: erase fastboot system-w?
[G1 Android Development] Firerat:
you need to 'fake' your SPL, as CM6 refuses to believe you can install on an SPL with a partition size 67.5 ( which is true , but we have CustomMTD )

No point in pestering CM to add 1.33.2003, as people who don't have CustomMTD will have a very bad experience

flash recovery patcher after adding

spl 1.33.2005

to /sdcard/mtdpartmap.txt

e.g

mtd 90 2
spl 1.33.2005

basically it adds

androidboot.bootloader=1.33.2005

to the kernel's cmdline, and recovery thinks you have 1.33.2005 SPL ;)
[G1 Android Development] elfasito:
finally everything is correct flash SuperFroyo achieved.

thanks for your great patience and great work on the custom partitions :)
[G1 Android Development] izzy001:
Hey Firerat, is it just me or is anyone else getting a "(Status 6)" error when trying to flash the new RC3 kernel?
[G1 Android Development] Firerat:
:(

mybad

I messed up the Updater-script, had a , instead of ;

try this one

87F160F08FCD2233DDD40FBFC50D3711 FR-CM6RC3-bootimg4NoneD-AutoMTD.zip
[G1 Android Development] albatorcobra:
Hi,

I have downloaded your last kernel. The patching process is ok but my G1 doesn't boot. I am stuck on the G1 boot screen like I am with stock CM kernel.

Thank you for your great work.
[G1 Android Development] Firerat:
I'll have to downgrade my spl from 1.33.2003 and check
[G1 Android Development] izzy001:
Disregard this
[G1 Android Development] foxtrickle:
I've used it with 1.6.2 and SuperD with no problems.
[G1 Android Development] izzy001:
The scripts will run with Amon RA's recovery... but clockwork gave me a huge malfunction when patched. I recommend using Amon RA's recovery 1.7.0
[G1 Android Development] Firerat:
personally I recommend Clockwork , as this is what I use.

But ra 1.6 + will work, but remeber, if you resize you need to go to fastboot mode and

fastboot erase system -w

with clockwork you don't need that step, instead use clockwork's format partitions feature ( its more convenient )
[G1 Android Development] izzy001:
Well last night when I was trying Clockwork, I installed the patches but that's when everything messed up for me, I when to fastboot and installed a recovery but it would just show the version of the recovery on the bottom and that's it no other text, if it wasn't for a nandroid I backed up and flashed in fastboot I would have still been stuck
[G1 Android Development] lbcoder:
You forgot to wipe in fastboot.

Without wiping in fastboot, all your main partitions start at weird places (relative to where recovery expects them to be) and confuse the crap out of recovery. In fact, when recovery tries to mount partitions that are screwed up like that, it starts at the BEGINNING of where it THINKS the partitions are mounted, and SCROLLS ALL THE WAY THROUGH IT until it finds a yaffs2 filesystem header to mount. System will be fine, it'll locate and mount that immediately. Cache will take some scanning to find, and it'll scroll ALL THE WAY THROUGH userdata before crashing when it doesn't exist.
[G1 Android Development] izzy001:
Thanks I know now... maybe I will try Clockwork again some time, just one question, if I do a nandroid and erase everything in fastboot flash Clockwork and then flash the nandroid will everything be ok,as in the custom partions will stay with the nandroid?
[G1 Android Development] lbcoder:
Fastboot does NOT respect the custom partitions.

What you can do is use fastboot to flash back the custom BOOT and RECOVERY partitions (since they live at the same offsets as fastboot knows), but then you need to use recovery to restore the rest of the partitions.
[G1 Android Development] bigboidomo:
I used this universal mod on my htc hero cdma and it worked nicely except when I go to nandroid it didn't work I use clockwork recovery can that bethe problem?

Did I catch you having fun? *slaps*
[G1 Android Development] haunter1982:
Ok.. on my G1 it's working perfectly. But may i ask if it could be done on my second mobile a T-Mobile Pulse? In your first post you said its "universal"

dmesg|awk '/0x.+: "/{ print }' gives the following output:

[1, swapper] [ 0.882645] 0x000002600000-0x000002880000 : "boot"

[1, swapper] [ 0.885423] 0x000002880000-0x000009680000 : "system"

[1, swapper] [ 0.887505] 0x000009680000-0x00000e6c0000 : "userdat

[1, swapper] [ 0.889610] 0x00000e6c0000-0x00000fac0000 : "cache"

[1, swapper] [ 0.892143] 0x00000fac0000-0x00000ff80000 : "recover

[1, swapper] [ 0.894253] 0x00000ff80000-0x000010000000 : "misc"

Recovery on the Pulse is Clockwork 2.5.0.4

The order of the Partitions isnt equal to the G1, does this mean it wouldn't work?
[G1 Android Development] izzy001:
So this is what I do:

fastboot erase boot

fastboot erase recovery

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash userdata data.img

fastboot flash recovery recovery-clockwork-2.5.0.1-dream.img

fastboot reboot

From there I just boot into recovery and patch?
[G1 Android Development] AndDiSa:
No, as lbcoder stated only recovery and boot partitions are ok.

You need to flash recovery,

then reboot to recovery,

flash fr-recovery-MTDxxx.zip,

reboot into recovery

and then your partitions are known, but only from within recovery, not fastboot! The same is valid for the boot image, but if you restore a boot image with the same partition table, you do not need to flash it again.