yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] lolmensch:
@Angeldeath

I dont know why you did implement your gps.conf (even though it was a lot of work for you) as tytung clearly said that his (which he had written by himself which means he knows about his own code) and everyone else's gps lib is not going to fetch any data of the gps.conf

so why even putting it in there? (or was it just because it can't hurt to put it in there?)
[HD2 Android NAND Development] TheGeorgiaSwagger:
Will try this in the morning angel, your the man. Enjoy the rest of your night brodie.
[HD2 Android NAND Development] the_scotsman:
Download link is dead....?

EDIT: Actualy mirror link is dead, first one works ok, even though it's incredibly slow.

EDIT 2: EU 1.3 Update link is dead.
[HD2 Android NAND Development] AngelDeath:
Mirror very much alive, just checked it as soon as I read your reply.
[HD2 Android NAND Development] the_scotsman:
Both the mirror and the original are down for me now...no idea why...oh well.

EDIT again: It's kicked in again, but still slow...I'll let it keep going.

Looks like I can only download one file at a time maybe?
[HD2 Android NAND Development] AngelDeath:
My Site (Dont know about the mirror) yes only one connection per IP. Being I only have a 5mb upstream, and the amount of people DLing I have to set a limit.
[HD2 Android NAND Development] Southerncrosser:
Thanks for a new part of your hard Work, and now with an update Package,it is perfect. I am stil on your 3.7 because it is not bad.

One question about Memory. Is the Problem only because the Rom is so big? or is something wrong, because the have an ext 3 Partition so the System should use it. I have 4 Gb EExt3 and i run out of memory. is the tool that enable the ext3 usefull and compatible with your rom?

I Love your work

Edit:

Wow, it is the first Rom, who install my old Apps automatic from Google. amazing

I run now on AngelDeath 1.3 on an EU HD2 512
[HD2 Android NAND Development] AngelDeath:
The low memory issue the way I see it comes because of sense, (Wish I knew how to make a shortcut in android) if you were to not run sense its GB obviously underneath, you would see that from boot to main screen, you would have a total of 170-190mb of space, adding sense to the mix takes up alot of the room.

All the ext partitions arent going to help, all that helps is space on your "drive" to add apps, your cache etc.

If you went to settings then applications and then running services you would see what is using up your memory, one thing I dont know why is Maps uses nearly 11mb of memory and you cant kill the service, if you do it comes back, regardless if your running it or not. The best way to conserve memory is utilize what you really want from sense. For example this would kill your memory just about:

Weather Lockscreen, Live Weather Wallpaper, Any large widgets (Friends Stream, Calender, Music, Twitter, Mail.

The Live weather wallpaper is an absolute hog for resources, as neat as it looks, its the one thing I dont use cause it also slows the response time of the phone down to acrawl.

I normally hover at around 90mb of free ram, sometimes I'll use Task killer, and get up to 130mb, but thats pretty much the limit of what you can achieve. Its all on how you setup your phone.
[HD2 Android NAND Development] ftd01:
Dear Angeldeath i am stil waiting :(
[HD2 Android NAND Development] AngelDeath:
the gogogo screen doesnt have anything to do with the rom.

Are you using mag version or did you convert to clk using the command in the faq? If you are using it as a magdlr, then My suggestion as I have said:

Go into CWR, then mount & storage, Format Boot, Cache, Data, System, then go to advanced, and wipe dalvik cache, then install the rom (1.2) before rebooting, or flashing the update pack, go to advanced, then error report, it will copy the error report to your sdcard, then mount your sdcard in CWR, and copy the report located in clockwork folder called recovery.log out of your sdcard, then flash the update pack, then repeat the step to copy the error report to the sdcard, and then copy the recovery.log to your computer, making SURE to RENAME the first recovery.log to recovery1.log so it doesnt get replaced, then reboot and see if it boots, if it doesnt, attach both recovery logs here so i can read them and I will tell you whats wrong, if anything with the rom.
[HD2 Android NAND Development] Kameirus:
everything works perfectly AD thanks

one question

is there anyway to have the lockscreen on the op match my wallpaper

i like dark wallpapers and just curious if theres a way to do that
[HD2 Android NAND Development] jan-willem3:
Well it can have to do something with the rom. For example when you use a wrong initrd.gz or kernel.;)

But I don't think that is the problem in your rom:D
[HD2 Android NAND Development] AngelDeath:
The only way that's possible is if you have a dark wallpaper on you phone screen then you can choose either the wallpaper lock screen or the clock screen, only those two will use your phone wall paper. And as far as I know the lockscreen can't be different then the wallpaper of the main screen. I think that feature only applies to double shot ROM.
[HD2 Android NAND Development] ognivo:
Has established on EU, installation has passed without problems. All flies.

But there is a question on internal free memory (only 62 mbytes), whether нге is small...???:confused:

Thanks for insertions...;)
[HD2 Android NAND Development] ftd01:
It is not write anything in recovery.log(i see the time is old of this file)

I flash rafpigna1.9gb and it is start install rom (it is working now). Thank's for you and jan-willem3 :)
[HD2 Android NAND Development] Achen_su:
how to download? user name and password
[HD2 Android NAND Development] vitalisvv:
Use Google Crome or Mirrors
[HD2 Android NAND Development] maximus_N_:
Same problem here. I will follow your instructions and report the results.

UPDATE: I installed the 300M system and 8MB cache with the help of the HD2 toolkit.

I also made an EXT3 partition of 1024MB. The FAT32 for the ROM zip files has 551 MB free space. You think this is the issue?

Dump from log file:

minzip: Extracted file "/system/xbin/zip"

minzip: Extracted file "/system/xbin/zipalign"

minzip: Extracted file "/boot/initrd.gz"

minzip: Error writing 28672 bytes from zip file from 0xbec23a6c: No space left on device

minzip: Process function elected to fail (in inflate)

minzip: Can't extract entry to file.

minzip: Error extracting "/boot/zImage"
[HD2 Android NAND Development] Magnumutz:
Have the graphic glitches been fixed?
[HD2 Android NAND Development] phearell:
ext2/3/4

i just dont understand one thing

I know how to make a one ext partition

But when i need for a rom ext2/3/4, does this mean that i have to make 3 partitions (ext2 or 3) ??
[HD2 Android NAND Development] stirkac:
no it just means you can use any of them (ext2, ext3, ext4, whichever you prefer)
[HD2 Android NAND Development] AngelDeath:
minzip: Error writing 28672 bytes from zip file from 0xbec23a6c: No space left on device

That tells you right there, you ran out of room on the phone.

My suggestion based on you saying that you are using the HD2 toolkit, try using the old fashioned Recovery Flash, My feeling is the toolkit is partitioning your phone incorrectly.

If you need me to attach the Recovery Program with the Configuration set, let me know and I'll attach it to Post #4
[HD2 Android NAND Development] AngelDeath:
Not completely, but not as noticeable as before.
[HD2 Android NAND Development] gottley:
to those who said "everything works perfectly wifi hotspot nor wifi tether work on this rom so no everything doesnt work perfectly the rom runns good though;)
[HD2 Android NAND Development] ricky886:
Bug report

tmous v1.3

Can't type Chinese.
[HD2 Android NAND Development] cyphol:
Gallery's not working for me. It shows nothing (blank white page). I've applied a gallery fix by @JHR5474 from Dungphp's Kingdom thread to make it working.

This ROM (v1.3 EU) is fast. Thanks @AngelDeath. :)
[HD2 Android NAND Development] AngelDeath:
Could be the files might not be in the rom, honestly I dont know what I am looking for when it comes to that, but I'll look and see what I can find.
[HD2 Android NAND Development] AngelDeath:
I think its a link in one of the default.xml files, I'll if its what I think and add it in, keep you posted.
[HD2 Android NAND Development] AngelDeath:
Odd, I'll double check the Update pack, but its the same Update pack thats for TMOUS and it works beautifully on mine...
[HD2 Android NAND Development] metaltech:
Is there a tmous blurry mms fix in the rom? Only thing lacking for me in all these sense 3 roms.
[HD2 Android NAND Development] Kameirus:
ok cool it wasnt showing my wallpaper on the lockscreen at first

now it is

Thanks
[HD2 Android NAND Development] dharvey4651:
Strange.. After installing this on my T-Mobile HD2, I get stuck at the MAGLDR "123456 GO GO GO"... Any ideas?

EDIT:: Even tried reworking my partition layout and re-flashing that. I'm using the 445mb partition layout as recommended in the OP and I installed the ROM via CWM like I would any other. Update goes smoothly and finishes successfully. Still a "NO-GO GO GO"

This is the partition layout I'm using:
[HD2 Android NAND Development] Kameirus:
i just switched from ADs eu version to the tmobile version

and this is what im using as cwm

misc ya 1M

recovery rrecov|ro|nospr 5m recovery_3.0.2.5_leo-seadersn.img

boot yboot|ro 8M

system ya 445M

cache ya 44M

userdata ya|asize|hr allsize

and it booted right up

dont use the hd2 tool kit as mentioned in a previous post

and recovery 4.0.0.0 never worked for me so i went back to 3.0.2.5

and havent had a problem flashing the sense 3.0 roms
[HD2 Android NAND Development] sagarjawaress:
+1.

flashed rafpigna 1.9 gb and its booting from magldr now(for eu HD2)
[HD2 Android NAND Development] amitwats2004:
Internal Memory left only 63MB

I am EU HD2 user. Installed your almost "PERFECT" ROM....LOVE IT. But I am facing following problem:

Even after having 1GB EXT partition on my SD card, I have only 63 MB memory left after installation of your ROM. This is limiting installation of new apps from market.

May be I am not the only person facing this problem. Dear AD, please tell me if I am missing something resulting in such low internal memory problem.

Thanks & Regards
[HD2 Android NAND Development] dharvey4651:
Reinstalling the ROM with CWM 3.0.2.5 and your partition layout right now. Wish me luck. Will report my results.
[HD2 Android NAND Development] Kameirus:
good luck it should work

i hope it works
[HD2 Android NAND Development] dharvey4651:
Hah! What do you know.. It worked. :) Thanks a million man.

Installing the 1.3 update now to see what else it fixes.
[HD2 Android NAND Development] Kameirus:
awesome Glad i could help
[HD2 Android NAND Development] gottley:
ok cool that sound good cuz i need it
[HD2 Android NAND Development] dharvey4651:
Noticed that after the 1.3 TMOUS update, the calendar widgets no longer work.. Strange..

EDIT::

And the more I configure the build it seems that it likes to "hot reboot" itself very frequently...
[HD2 Android NAND Development] `SBR`:
you saved me :) ... finally able to boot it..
[HD2 Android NAND Development] Kameirus:
cool glad to help
[HD2 Android NAND Development] Kameirus:
thats weird on the hot reboots

i had the run eu version all night long and nothing like that

will continue testing the tmobile version
[HD2 Android NAND Development] brianb2:
i cant even download the rom
[HD2 Android NAND Development] sso1955:
I am waiting for 18 minutes now in the first boot screen.

Is it normal or something it's wrong?
[HD2 Android NAND Development] sstrunks84:
I got stuck at the GO GO GO screen as well. I even tried different partition cache sizes, and different recovery versions but nothing worked (advice was from Kameirus). I'm using a TMo HD2.
[HD2 Android NAND Development] Kameirus:
sorry it didnt work for you

as it did for others

i have no clue as to why its doing it now
[HD2 Android NAND Development] AngelDeath:
Yes its in there, as well as the MMS size has been changed from the default of 100, 200, 300kb to 300, 600, 1024, with the default setting being 1024.
[HD2 Android NAND Development] AngelDeath:
I just tested this and both calender widgets post to the screen for me, obviously one widget has 3 choices while the other has only one, so all four worked for me, which widget are you having trouble with? Also I have experienced no hot reboots at all, if anything its the most stable build of the 3 I have come out with, if I dare say. If you can re-produce it let me know and I'll try to replicate it.

Also, I can not guarantee the rom booting from any CWR size other then the one I recommend. The cwr size that Kam suggest from what I know runs dangerously close to running over the limit. Im glad it works for people, but there is the possibility of corruption or problems with the rom, please be aware of that. I cannot test every partition size as I wouldnt have enough time in a month to see if it works, so do be careful.

On a Side note, Dharvey, please can you look into my account if its me, or if its just in general why multi-quote doesnt work, I hate having to make several replies when i can do it in just one. Thanks
[HD2 Android NAND Development] AngelDeath:
No it doesnt take that long first boot, should roughly take no more then 3 minutes to the boot screen, and another minute at the boot screen, so in 5 mins you should have the lock screen. if you dont, most likely wrong flash or wrong CWR partitioning.
[HD2 Android NAND Development] AngelDeath:
Again as I said in the FAQ, you can try different partition sizes, but any problems that occur I can not be responsible for. Do understand that we all have a limit of what we can use on our rom.

So seening that so many people are having this stuck at gogogo problem, I have attached here (And will be attaching to my main posts, the CWR zip for EU & TMOUS. The problem is your BOOT Partition layout is wrong. RAF's Kernel works because its designed to work with a 5mb boot layout. (CLK users ignore this as this doesnt pertain to you)

Just to be safe here are the instructions, "Just in Case":

Boot into Magdlr, make sure your phone is not connected by USB, then choose USB Flasher when it says waiting USB, plug your phone in, WAIT for it to say Waiting USB...USB, then flash the CWR I provided, these settings will and do work, when the phone reboots, then choose option 8 to go to recovery, and flash the rom, and right after flash the 1.3 update.

As a habit, you should after the flash of the rom go into the advanced option before rebooting, and choose error report, so that a recovery.log of the boot process is saved to your sdcard, and then you should pull this log into your computer. This log shows you the whole flashing process and can save you endless time and headaches of why your phone is not booting.

98% of the time the failure to boot is due to running out of room on the device because of the wrong partition layout. 1% of the time it is due to a wrong boot layout. 1% of the time its due to bad blocks on the phone that cant be writtten to which reduces your partition size.

I cannot guarantee that HD2 toolkit formats the partition layout correctly, or anything other program, this is what I use and it has not failed me yet, if you choose to use a different way of laying out your partition, then please do not blame the rom.

Thank you.
[HD2 Android NAND Development] AngelDeath:
The 63mb is not memory (Correct me if I'm wrong), that is how much internal Storage you have left on your actual phone AFTER installation. Understand that is two different things, and some people can be confused about that.

Now when you install apps, your applications should be installing on your SDcard or the SD-EXT partition, is it doing that? If so, then the 63mb shouldnt prevent you from installing any apps since it will be going to your sd-ext partition since thats where your framework and apps are being loaded.

Please double check. Hey KAM, since you installed the EU version mind checking this out and giving me a hand? (And dont clap smartass :))
[HD2 Android NAND Development] impy101:
I'm stuck on gogogo. I already did the wipes etc about 3 times now.

This is my error report.

http://www.mediafire.com/?1bzc51bgqsza04g
[HD2 Android NAND Development] jhr5474:
So if you open this up and read on the last line it tells you that you ran out of room and the zimage and init could not be extracted. I would suggest a task 29 with a new flash of magldr and use angel's cwr zips he just posted to partition with and make sure you use the correct layout for the version you are flashing.

ANGELD> THIS ROM IS BAD ASS STABLE MAN!
[HD2 Android NAND Development] AngelDeath:
Impy,

you have several problems on your device, first you have several bad blocks on your phone, and I mean several, second, you have run out of memory while writing to the device during flashing, and third, you ran out of room during your flashing.

Formatting /data...

mtd: not erasing bad block at 0x03400000

mtd: not erasing bad block at 0x03420000

mtd: not erasing bad block at 0x07ca0000

mtd: not erasing bad block at 0x0b400000

mtd: not erasing bad block at 0x0b420000

Done.

Formatting /system...

mtd: not erasing bad block at 0x00000000

mtd: not erasing bad block at 0x00020000

mtd: not erasing bad block at 0x08000000

mtd: not erasing bad block at 0x08020000

mtd: not erasing bad block at 0x080a0000

Thats one problem.

Symlinks and permissions...

symlink: failed to symlink /system/xbin/crontab to busybox: Out of memory

The whole folder is like this thats the second problem.

minzip: Error writing 28672 bytes from zip file from 0xbee8428c: No space left on device

minzip: Process function elected to fail (in inflate)

minzip: Can't extract entry to file.

minzip: Error extracting "/system/xbin/busybox"

minzip: Extracted file "/boot/initrd.gz"

minzip: Error writing 28672 bytes from zip file from 0xbee84a6c: No space left on device

minzip: Process function elected to fail (in inflate)

minzip: Can't extract entry to file.

minzip: Error extracting "/boot/zImage"

And thats your third problem.

You didnt tell me if this was a Eu rom or a tmous rom, but judging by the SD-EXT your using I will say its a EU rom. Here is what i would suggest you do that you can try:

Task29 the phone, then re-flash magdlr 1.3, then download the EU CWR zip I just posted two posts above, or in Post #2, and flash that, and then try again, but again, copy the error report to your computer just in case we have this issue so i can see what its doing.
[HD2 Android NAND Development] Kameirus:
lol dang

yea give me a few minutes i just got home and am cooking dinner

and i have to flash back to EU version was theme testing on the tmobile version

30 minutes and i will let you know
[HD2 Android NAND Development] impy101:
I did exactly as you said.

I used radio, and flashed it. Then I flashed MAGLDR 1.13 and that EUCWL you posted above. Still no luck.

Edit: I installed the wrong one, my bad. It's working now! :D

Edit 2: I'm not sure it's working afterall. It's been stuck at this blue startup screen for a few minutes now. Is this normal?
[HD2 Android NAND Development] Kameirus:
ok just did task 29 and used this cwm

misc ya 1M

recovery rrecov|ro|nospr filesize recovery-raw.img

boot yboot|ro 8M

system ya 300M

cache ya 8M

userdata ya|asize|hr allsize

booted up fine no problems

went to market and downloaded a file manager

then installed root explorer and screen off and lock

went into root explorer to sd-ext and all three of those apps are there under the app folder when i go to system\applications\manage applications and click on the all tab

it shows i have 13mb used and 598mb free internal storage ..when i open up task manager it shows total memory 411mb ....298mb used and 113mb free
[HD2 Android NAND Development] dharvey4651:
It's all of the HTC Calendar Widgets. When I go into the customize menu to add one of them, they just don't appear. Strange I must say..

Also, the hot reboots are totally random. I could be in the middle of replying to a text, browsing the market, installing an app, even making a phone call and it will do it. Not sure how or why.

I'll also contact Svetius about your multi-quote issue.
[HD2 Android NAND Development] impy101:
Can someone please help me? I just did everything that I was told. Use radio 27, flash magldr1.13 again, then the EUCWR that AD posted and now the rom DOES start up, but now it gets stuck at that blue picture. It's been there for the last 15 - 20 minutes.
[HD2 Android NAND Development] Kameirus:
its not just you AD i cant multiquote either
[HD2 Android NAND Development] Kameirus:
i dont have a clue impy as i just flashed the eu rom and reported on it a couple posts back
[HD2 Android NAND Development] impy101:
I'll try that TMOUS rom then.
[HD2 Android NAND Development] impy101:
That tmous CWR doesn't work.. I get this error:

Error Description: Size is too big.

Info: .\RSPL\RSPL.cpp (800)
[HD2 Android NAND Development] Kameirus:
what hd2 do you have a tmobile one or eu one
[HD2 Android NAND Development] impy101:
The phone is purchased in europe and has a Dutch sim card. So.. EU?
[HD2 Android NAND Development] Kameirus:
yea im gonna guess EU

i honestly have no clue why the eu version of this rom wont work

on your phone

the tmobile version isnt gonna work
[HD2 Android NAND Development] metaltech:
AngelDeath..just flashed rom..sent myself a 550kb pic and it came in at 3kb. :(

Doesnt seem like the fix took.
[HD2 Android NAND Development] dharvey4651:
Noticed that after I installed SetCPU and clocked it at 1190mhz it froze immediately. Now this is the 2nd time I tried installing this ROM. Perhaps SetCPU is what caused the random Hot Reboots before..
[HD2 Android NAND Development] impy101:
W00t. Fixed it =)

This is AD EU Kingdom 1.2 (sense 2.1 I believe) But I want that 1.3 with the 3.0

Where can I find the readme for that?
[HD2 Android NAND Development] impy101:
P.S. Is it just me, or does everyone have these weird graphic problems? I sometimes see lines in the screen when pressing (gently)
[HD2 Android NAND Development] Kameirus:
no its 3.0 also

its all in the OP

you were just trying flash the 1.3 update werent you
[HD2 Android NAND Development] impy101:
No, I just forgot to partition my SD card, lol.

But I do have 2 small problems now though.

I get these weird lines on my screen from time to time, they look like dead/misplaced pixels.

And lastly; how do I reboot/shutdown the phone? I keep holding the power button, but nothing shows up.
[HD2 Android NAND Development] metaltech:
The lines are graphic glitches that all GB Sense roms have. You can flash a fix for them but it breaks the camera.

Use the quick boot app thats included in the rom.
[HD2 Android NAND Development] impy101:
My last rom (Core Droid 1.6) didn't have these problems?
[HD2 Android NAND Development] Kameirus:
coredroid is also sense 2.1 not 3.0
[HD2 Android NAND Development] impy101:
So all sense 3.0 roms have these problems? Man, I hope 'they' find some fixes for it soon =)
[HD2 Android NAND Development] AngelDeath:
That could very well be your problem Since I dont overclock my phone I dont test for things like that, I for the most part test as is because 80% of the people on here dont, so that could very well be your issue.

Also just for giggles, would it be too much to ask if you would use the CWR that I posted and re-flash the rom, I want to see if the widget problem might go away, if it doesnt, then I am going to re-flash my test phone and try to replicate your issue with the Calender Widgets.

Hey Kam want to try what DHarvey is having issues with to see if its the rom or him?
[HD2 Android NAND Development] AngelDeath:
That is strange, cause when I recieve pix on mine and I tap on it, I see it in full screen, thats why I find it odd. But I will test this as well when I re-flash my test phone, been working on fixing Doubleshot so i can update that rom as well, but I'll put it as a back burner to check these issues out.
[HD2 Android NAND Development] AngelDeath:
Think I'm going to dub you my spokesperson for my thread LOL.