yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] macs18max:
Ok guys. New ROM up and running

Make sure if you r on Nand to increase your system size.

Kernel drain may be worsen

Superuser is not enabled by default instruction so to enable Developers Option > Root access > select "apps" or "app and adb"

But ROM is really smooth. (at least for sometime after installation ;)) ION baby

Enjoy
[HD2 Android NAND Development] hitman1376:
Wow ... Brilliant work ...

Great News man ... I thought you'r work deserves a BIG Thank :good: ... This is revolutionary man :good: ... Great work HD24Ever :good: ... Were waiting for next brilliant releases :good: ... wish all of you success in your whole life :good:

With Best Wishes

Hitman1376​
[HD2 Android NAND Development] macs18max:
Is this comment before downloading and installing ROM or after installing??:confused: LOL
[HD2 Android NAND Development] hitman1376:
Why Confused man ?

Dear friend , I have downloaded your ROM now and it works as expected :laugh: ( Does it matter ? ... The important thing is that now , we have ION almost ... thanks to you great developers :good: ... ) ... why confused ? ION Kernel wasn't reachable without you Devs :good: ... Thanks again
[HD2 Android NAND Development] Robbie P:
I thought i would try magldr dataonext, but it wouldn't boot ("invalid boot image header" message)

tried 11mb and 12mb boot partition

here is flash.cfg

misc ya 1M
recovery rrecov|ro 10M
boot rboot|ro 12M
system ya 390M
cache ya 5M
userdata ya|asize|hr allsize

I did manage to get it to boot by putting zImage and (dataonext)initrd.gz into a folder on sd card and booting from ad sd. Seems fast.

Does it make sense to always boot nand roms from the sdcard? AFAIK ramdisk and kernel are loaded to ram either way, and they can be put in /sdcard/NativeSD just like NSD roms, so can be multibooted from datagr's app.

The only reason i can think of is possibly they were put into /boot in the wrong order by updater script. Not sure.

Edit; Scratch the last, i swapped the order in updater script and still get invalid boot image header. BTW i have no bad blocks.
[HD2 Android NAND Development] macs18max:
Yes, your good idea to boot magldr from sdcard for Nand installation, we will have some additional Nand memory for system for EU's HD2. (Which is 12MB in case of kernel 3.0).

The only disadvantage I can think of is if the user switch sdcard often, he will need to make of zImage and ramdisk on each of sdcard lol:laugh:

Reading my own line on top got me thinking. Are we exceeding our Nand Memory for EU. 1 + 10 + 12 +390 + 5 = 418MB:confused:

Coz I had another user PM me

But he didnt mention his configuration so I cant tell.

I think I should delete Email.apk and Exchange.apk from the installer coz 390MB + 12MB boot magldr may be too much. I dont know. Think i'll do that
[HD2 Android NAND Development] -pixelfreak-:
re

[MENTION=2473151]macs18max[/MENTION] why you work with 3 initrd.gz for clk and 3 for magldr?

pixel
[HD2 Android NAND Development] macs18max:
Coz of the 6MB needs to be added for Magldr.

It can be made simpler using Hypoturtle universal initrd patcher, but I rather use my time on fixing kernel than preparing the script.

I'll just wait for someone to do it.

[MENTION=3629322]Robbie P[/MENTION] Opps I forgot to mention I reverted the battery code so extended battery wont work
[HD2 Android NAND Development] philipped346:
hello , i have installed mac2 on my europe hd2 with magldr and recovery 5.xx . nativesd and i have not wifi working !:crying:
[HD2 Android NAND Development] Robbie P:
try re-flash, wipe dalvic but no full wipe.

I had trouble with wifi not working with nsd.

---------- Post added at 02:18 PM ---------- Previous post was at 01:41 PM ----------

note that recovery can also go on SD using an sd recovery, so eu hd2 magldr users can then have an even bigger system. From my dmesg

[ 2.398834] Creating 6 MTD partitions on "msm_nand":
[ 2.398864] 0x000004320000[COLOR="Red"]67.125mb[/COLOR]-0x000004420000 : "misc"[COLOR="Red"]1mb
[/COLOR]
[ 2.400787] 0x000004420000-0x000004e20000 : "recovery"[COLOR="red"]10mb
[/COLOR]
[ 2.407684] 0x000004e20000-0x000005a20000 : "boot"[COLOR="red"]12mb[/COLOR]
[ 2.415710] 0x000005a20000-0x00001e020000 : "system"[COLOR="red"]390mb[/COLOR]
[ 2.629974] 0x00001e020000-0x00001e520000 : "cache"[COLOR="red"]5mb[/COLOR]
[ 2.634033] 0x00001e520000-0x00001e800000 : "userdata"[COLOR="red"]2.875mb[/COLOR]

we get 67.125mb reserved for video etc call it 68mb

leaving 420.875mb for us, call it 420 so it is more than the 418 above.

less 1mb misc and 5mb cache, leaves 414 for system.

Bad blocks will affect these figures of course.

This can only work for magldr users since cLK must have a boot partition and a recovery partition. To boot recovery from sdcard you must add an sboot partition containing zImage and initrd.gz (in a boot.img) which is essentially what the recovery consists of anyway.
[HD2 Android NAND Development] -pixelfreak-:
my rom test

TmoUS with CLK and DataEXT

cannot read boot image header...

[IMG="Screenshot"]http://s14.directupload.net/images/140930/mnrk8hz5.jpg[/IMG]

you can change the animation scale to min 0.5 with 0.0 the dialer numbers not work

https://github.com/pixelfreak2005/l...mmit/5f7d2a1a6561d5a3f3c5eab462595c06beb6e590

Pixel
[HD2 Android NAND Development] Robbie P:
Just tried cm11-mac2 magldr dataonext install with 13mb and 20mb boot partition (370mb system), still get invalid boot image header.

edit; oops left that quote in. it was 390 because i could choose 390. it probably would work with 365 as in OP, no nand-only users have posted whether it works not.
[HD2 Android NAND Development] macs18max:
Robbie Seems it is because I used Linaro4.7 to compile(Dont have any other expalinations)

I have user on cLK and Magldr both having this issues.

For me I use cLK, NativeSD, extended TWRP, and the kernel boot every time.

I flash the kernel at least 4 times a day to test new changes it commit in the kernel, never had that issue. But may be it causes issue on some HD2.

Mostly I flash using fastboot or TWRP nativesd kernel updater.
[HD2 Android NAND Development] walter79:
For better battery support check marc1706 leo-board from his 3.0.16 kernel. I have no problems with battery with kernel that used marcs source
[HD2 Android NAND Development] fOxunO:
There is no root on mac2 and mac2a ?
[HD2 Android NAND Development] macs18max:
both x-11 and x12(The one in the ROM package) uses marc's code. I only removed unsed/comment codes so that I can read it better. Its the same code.

Think the battery charger give false reading only after when you sleep the device. And since suspend is not working in marc's kernel, it may show correct indication

I mentioned in the first post you need to activate root in developers option
[HD2 Android NAND Development] macs18max:
I didnt understand. Is there a issue in the ROM? dialer numbers not working?
[HD2 Android NAND Development] -pixelfreak-:
no no... You can change to 0.25 for faster animation. with 0.0 the Dialer not work. i have not test this Rom. Kernel header problem...
[HD2 Android NAND Development] macs18max:
You could try this one

http://xdaforums.com/showpost.php?p=55759681&postcount=131

should work
[HD2 Android NAND Development] Robbie P:
i mentioned it before here http://xdaforums.com/showpost.php?p=55599324&postcount=94 "small thing"
[HD2 Android NAND Development] walter79:
For better battery support check this:

https://github.com/walter79/android_kernel_htc_leo/blob/3.0.x-ION/arch/arm/mach-msm/board-htcleo.c

Line 1280 "// Power/Battery"
[HD2 Android NAND Development] macs18max:
Currently I'm out of city (work related) so no hd2 or laptop for a week. walter79 if you could compile the kernel with battery charger fix and publish it here for testing wud be great so that others can test and report.
[HD2 Android NAND Development] Mike_1996:
I just dirty flashed 2a and noticed the absense of accelerometer etc. (seen with the app Phone Tester). Should this be a bug? Version 1 worked fine.
[HD2 Android NAND Development] macs18max:
Can any volunteer reupload this ROM on devhost, but u need to delete the following folder before upload the zip.

Boot

System

Data

Basically I'm out of city and without my workstation. I'm using my mobile which has only 200mb remaining on my data plan. I want to work on the installer script so I need only aroma updater files and files in mod folder.

Also if someone could do the same for my slim 4.2.2 for hd2 , delete the folders

System

Kernel

Data and upload.
[HD2 Android NAND Development] Robbie P:
I didn't DL CM11-mac2a, but have uploaded files from version CM11-mac2 to http://d-h.st/zDq

looking for the slim now

Edit; i found the slim and have uploaded to http://d-h.st/n1V . It has an addon folder with apks in, i deleted this and re-upped to http://d-h.st/142 if you need to save bandwidth. Note i also deleted sdcard folder in all 3 zips

Edit2; [MENTION=2473151]macs18max[/MENTION] i mentioned you in case you did not see my previous edit, not that i am trying to hurry you;):)
[HD2 Android NAND Development] macs18max:
Thanks alot Robbie :)
[HD2 Android NAND Development] walter79:
Got mobile data working with "my" 3.x kernel. (based on marcs kernel)

Fix:

https://github.com/walter79/android_kernel_htc_leo/commit/f9502f4bf549fece17f1ec5224fd6c16b482c068

Can someone help to fix cam with pmem?

Kernel source: https://github.com/walter79/android_kernel_htc_leo

branch: 3.0.x-ION-testing

Display legacy: https://github.com/walter79/android_hardware_qcom_display-legacy

Device tree: https://github.com/walter79/android_device_htc_leo

I am using Evervolv Rom for testing.
[HD2 Android NAND Development] -pixelfreak-:
re

camera is working only the camcorder not

and kernel have deepsleep (in 20 seconds) and after display open (the ring is stuck) i have reboot

pixelfreak
[HD2 Android NAND Development] macs18max:
walter79, pixelfreak. Why don't you guys work on something that's broken(not working) rather than waste time working on something's that's already been fixed.

I feel sharing codes was a big mistake and it won't happen again.
[HD2 Android NAND Development] walter79:
If you don t like to share your code you should look for a new forum maybe . Goal of xda forum is to share his own work and make it possibe that other members can rebuild rom or libs and make a better Android for our phones. Why is the hd 2 the phone with the most "closed" source? Pixelfreak is not a kernel dev. But he is working hard to find a way to build new roms for our hd2. Check my github if you need fix for rmnet and ppp without using 7x30smd or working gps.

This week i working on fixing the camcoder and video/audio encoding. I use the galaxy s 1 way.
[HD2 Android NAND Development] kb0n:
Sharing code is never a mistake ;) See it this way: At least they're not doing *nothing* with it. No harm done, only gain, even if it's just aquiring and/or improving personal knowledge or coding skills, that might benefit all in the future ;)

Keep up the good work, you can be sure it's appreciated, even if not mentioned all the time!
[HD2 Android NAND Development] macs18max:
A. I'm not a kernel developer too. This is my first kernel. I take a lot of time and effort to read and understand what the code does.

B. I don't like to share codes to some people who don't respect others work, use it without credit them and claim it as their own.

I do share codes privately, to some. And two of them have already worked and published their ROMs.

C. Pixel freak is working hard to compile ROM and I appreciate that.

He should know how hard it is for a beginner to compile ROMs.

I worked on my first ROM for 3 months and published it a two weeks later he just changes some pngs, adds a music player, renames the ROM and replublished it which made me stop working on my ROM. I'm glad he too has come to this stage.

I won't discuss about this topic any further. No matter who replies what. End of discussion for me.
[HD2 Android NAND Development] werty100:
With tytung 2.6.32 kernel BlackScreen ?¿

Only changing the zImage maybe i need to change also intrd.gz

Have you compiled with Linaro toolchain ?¿ maybe good for perfomance

---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------

Screen issue with drivers ?¿ so they have been changed
[HD2 Android NAND Development] macs18max:
Tytungs kernel .32 kernel and marcs .35 kernel are pmem based and this ROM and kernel is Ion based. There won't work together so please don't try. I will put this in op when I go home tonight.
[HD2 Android NAND Development] werty100:
ok and now my hd2 is always every rom black screen why?¿
[HD2 Android NAND Development] macs18max:
Can u give me full details please? Can't help you when you say black screen and don't give any details, ROM , recovery, boot loader, installation method.

Another note: my kernel not compatible with any other ROMs ever published for hd2,

My rom not compatible with any other kernel published for hd2
[HD2 Android NAND Development] werty100:
Now i am installing nexus hd2 with was working perfectly and when bootaniamtion need to start i get blackscreen...

I was on WP7 when i flash your rom wipping with TASK29
[HD2 Android NAND Development] Robbie P:
So we can assume you are on magldr? Did you format the sd card https://www.sdcard.org/downloads/formatter_4/

Did you create ext4 partition? How?

What install method?

What recovery?

What HD2? TMOUS or international.

As much info as you can possibly give, we might find out your problem.
[HD2 Android NAND Development] werty100:
yes i have 2 ext partition International hd2 and it was oerfectly booting android and i changed to wp to test it and now i get back with formating phone with task29 and them formating sd...

And always i get blackscreen

4ext recovery
[HD2 Android NAND Development] Robbie P:
nand and sdcard partition sizes?

installation method?

Anything else you did?
[HD2 Android NAND Development] werty100:
340 ext 1024 ext2

340 system nand

by recovery zip

Now i am triying a chinese MIUI 2.3.7 that works before with ext3

Is so strange
[HD2 Android NAND Development] macs18max:
Probably ur first ROM was using direct SD. And then u switched to natives ROMs which installs system and data on same partition. So u will need more around 1gb or more for natives installation. AFAIK nexushd2 don't support directSD (unless I m not updated)
[HD2 Android NAND Development] macs18max:
[MENTION=3629322]Robbie P[/MENTION] , are there any advantages in directsd installation over nativesd installations?
[HD2 Android NAND Development] werty100:
I am 99.99% sure it was nativs SD always now MIUI 2.3.7 works in ext3 but it is booting and working
[HD2 Android NAND Development] macs18max:
But 340mb ext partition is not enough for nativesd installation.

Edit: didn't read that correctly, u got it working I believe.
[HD2 Android NAND Development] Robbie P:
miui 2 3 7 from here http://en.miui.com/download-14.html is only 82mb zipped, so it would be possible for it to boot from nsd in a 340mb sdext

It is the bigger kitkat roms that werty100 is having trouble with.

Seems certain that increasing sdext size will cure it. Delete sdext2 if you are not using directSD;)

---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------

TBH I have not tested fully. chautruongthinh definitely thought dsd was faster than nsd, boxmax too.

Edit; there would be advantages having /system and /data on different partitions if the partitions were formatted differently eg system on ext4, dataon f2fs
[HD2 Android NAND Development] werty100:
This is making my more stupid i have installed Nuxus HD2 and 2gb ext partiton and it doesnt boot go to kernel and reboot all time

---------- Post added at 05:24 PM ---------- Previous post was at 05:20 PM ----------

O **** was the CWM touch that makes 1st partiton ext4 and need to be 1st FAT32 and 2 ext4 i think it is that

it no my day puf...:eek::eek::eek::eek::eek::eek:
[HD2 Android NAND Development] macs18max:
[MENTION=3629322]Robbie P[/MENTION] bro

Time for testing

Could plz test this kernel with extended battery? I have made some changes and enabled debugging.

Try and if it reboot get the last_kmsg

THanks
[HD2 Android NAND Development] walter79:
What are the differents to marc1706 battery implementation in 3.0.x kernel?

Macs if you need help with extended battery pixel and me use this battery too. (original htc)
[HD2 Android NAND Development] macs18max:
Sorry guys. Don't bother to test, the charger still doesnt show correct battery indication...

The kernel I compile above uses marc 3.0.16 charger code.

See here https://github.com/maniacx/android_kernel_htcleo-3.0/commit/181e8cc6edda17a9414ba00655a0c66e07dcba2d (only thing missing are suspend and resume class which were missing, I have added them too and compiled it)

At first impression seems to work well. But suspend it. wait for half hour it will still show the same value as it was before suspend. I had still had 99% after half hour suspend. Took off battery and booted to TWRP showed 94%.:(
[HD2 Android NAND Development] walter79:
On Leo we have only 0,3 - 1 percent per hour battery drain in suspend.

Twrp use 2.6.32 kernel?

+ - 5 percent during boot to recovery seems to be normal.
[HD2 Android NAND Development] macs18max:
Well then you can try and see if it boots with extended battery?

Or if the charger is working correctly?

If it works , i will merge and push the code
[HD2 Android NAND Development] walter79:
Not working. Shutdown after boot.

No last_kmesg.

I will sent you log and dmesg later have to fix adb on my rom with your kernel first.

For testing please upload zimage and kernel modules.
[HD2 Android NAND Development] Robbie P:
Sorry, was out this evening for a change:o

Same here, shutdown after boot with extended battery, I did get a dmesg the second time around, attached.

The battery indicator did show correct amount at startup on normal battery with default x12 kernel as with this kernel as with recovery. I am still using mac2.

couldn't get a log, didn't show up. I think iserial needs to be set in init .d or .rc, can't remember which.

Edit; this morning the battery was flat (after full charge last night), I put it on charger and booted this rom, showed 23%, then booted 4ext sd recovery, showed 23%, then booted tytung's kk 4.7, shows 20%, but the battery is definitely flat. does it need a few charging cycles per rom for it to show correct percentage? I have probably not done this on any rom for years;):)
[HD2 Android NAND Development] macs18max:
OK. question for our existing kernel dev's. [MENTION=3907492]gilbert32[/MENTION] [MENTION=382340]walter79[/MENTION] [MENTION=1660048]Daekin[/MENTION] (sorry if I have missed anyone)

This is defined in our kernel 2.6.xx and 3.0.xx boardhtcleo.h where eb1_bank0 gets mapped

#define MSM_EBI1_BANK0_BASE 0x11800000
#define MSM_EBI1_BANK0_SIZE 0x1E7C0000 /* 488MB - 0x00040000 RAM CONSOLE*/

Now PMEM_ADSP for 2.6.32 get mapped here @ 148f5000 as shown in kmsg from tytung

allocating 35651584 bytes at c30f5000 (148f5000 physical) for adsp pmem arena

also when we playback a media file in 2.6.32 it set buffer at same location as shown in kmsg

<7>[ 56.484924] vdec_setbuffers:359 pmem_id=33 (phys=0x148f5000 len=0x38c000) buftype=0 num_buf=3 islast=1 src_id=17228841 offset=0x00000000 size=0x42cc0

Same goes for 2.6.35

<6>allocating 42991616 bytes at c3122000 (14922000 physical) for adsp pmem arena

playing a video file in 2.6.35

<7>vdec_setbuffers:358 pmem_id=24 (phys=0x14922000 len=0x19e7000) buftype=0 num_buf=5 islast=1 src_id=17228841 offset=0x00000000 size=0x1a5e00

However for 3.0.xx

PMEM_ADSP for 3.0.xx (in Pmem mode, however this stays true for ION too ) get mapped here @ 2dcc0000

<6>[ 0.000000] reserve_memory_for: reserve 35651584 bytes from memory 3 for pmem_adsp.

although physical memory is not shown during initialization of pmem_adsp . small commit can show the physical address but I sure is it mapped there looking at code whilst playing media files in 3.0.16

<7>[ 75.099822] vdec_setbuffers:365 pmem_id=33 (phys=0x2dcc0000 len=0x38c000) buftype=0 num_buf=3 islast=1 src_id=17228841 offset=0x00000000 size=0x42cc0

Dont know if I'm wrong, but seems like the in 2.6.xx physical address for pmem_adsp is mapped inside EB1 bank0 region but for 3.0.xx is mapped outside EB1 bank0

Anyone has the anwser to this question as to why adsp is mapped out?

This may be our solution to low ram and not working hardware encoder/decoder if we figure this out:fingers-crossed:
[HD2 Android NAND Development] macs18max:
I'm on fire today...... :)

Seems partially fixed decoder. Small size media plays using hardware decoder, but 720p files doesn't play. Tried increasing adsp size still no luck. Any ways enough for today.

Here are some codes from kmsg

<6>[ 0.000000] Memory: 180MB 231MB = 411MB total

<7>[ 217.054504] vdec_setbuffers:363 pmem_id=33 (phys=0x1ec00000 len=0x38c000) buftype=0 num_buf=3 islast=1 src_id=17228841 offset=0x00000000 size=0x42cc0

Edit: On earlier post I mentioned that pmem_adsp was mapped outside eb1_bank0 but seems like it is mapped inside

I assumed 11800000 to 1e7c0000 was eb1_bank0 but ebi1_bank0 is actually mapped from 11800000 to 2FFC0000 ( 1180000 + 1e7c0000)
[HD2 Android NAND Development] macs18max:
Anyone using Magldr with this rom, could you post the dmesg here please (kernel log)

Couple of user has help me one this. Do not post any more logs
[HD2 Android NAND Development] Robbie P:
Still with mac2, not 2a sorry bro. dmesg attached

Edit; For magldr users, getting a dmesg is easy. Switch off phone, (if in bootloop or hanging, press tiny red reset button under battery cover) do not pull battery. restart phone, hold end-call button and go to magldr menu 10.services / 2.DMESG to SD, then you will have a file DMESG.TXT on your sdcard, put card in cardreader (or usb file transfer) open a post in this thread and use "manage attachments" to navigate to DMESG.TXT and upload it;)
[Moto X Q&A] Christian Correia:
I updated my Motorbike X XT1058 for 4.4.4 (KXA21.12 VZW_XT1060_4.4.4-KXA21.12-L1.26_1FF) and it wanted to do the DOWNGRADE for 4.4.3 or 4.4.2. Some way for that?
[Moto X Q&A] KidJoe:
The GPT.BIN in 4.4.4 is different from 4.4.3, which is different from 4.4.2, which is different from 4.4.0's.

Motoboot.img is different between 4.4.3 and 4.4.2. 4.4.2's is different from 4.4.0.

These will prevent a complete, successful and safe downgrade of the rom version.

If you've seen all the "don't downgrade or you'll brick" warnings, this is what its talking about.
[Moto X Q&A] Darth:
This ^^^

But a better question is WHY would you want to downgrade?
[Moto X Q&A] Christian Correia:
I did not like because of the modification Verizon
[Moto X Q&A] Darth:
Well, you really can't downgrade without great risk.

So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...

http://xdaforums.com/showthread.php?t=2751177

Otherwise, there isn't much you can do.
[Moto X Q&A] DROID_4_UsEr:
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
[Moto X Q&A] KidJoe:
First this is an old thread...

Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).

For more, see the link in my signature on downgrading..