yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] NYLimited:
What I am not seeing here is details which may pinpoint the problem.

You need to pick one rom which works for a fair number of us and detail *exactly* what you are doing.

The radio, once flashed, remains. My signature should point you to a radio known to work in the US.

Beyond that, how are you partitioning you device; what kind of sd card and how is it formatted and setup; how are you flashing the rom; which recovery are you using; are you making any changes to the rom zip file... We could go on but hopefully you understand that, according to Murphy, the 1 piece of information you forget to mention out of the 100+ is the one that would have made one of us go "aha!"

---

Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wcstick:
Okay. I will start completely over and document my actions. I'm switching to cLK since I seem to get more consistent results.

Device: HTC HD2 T8585 1100

SDcard: SanDisk 32GB MicroSDHC formatted to FAT32

Program: HD2 Toolkit 4.3.1

ROM: http://xdaforums.com/showthread.php?t=2046327

Procedure:

1. Wipe with Task29 loaded from HD2 Toolkit 4.3.1

2. Make cLK Partition of 280 MB and 5 MB cache.

- Final message on phone screen: "fastboot: processing commands"

3. Install cLK Recovery in fastboot option

- Final message on phone screen: "rebooting the device"

4. Device never reboots.
[HD2 Android Q&A, Help & Troubleshooting and Genera] NYLimited:
I will be only a little help with CLK since I don't know it but..

If this is your first Android install perhaps you should try a stable rom, not an alpha one. Anyway, you don't seem to get to the rom install at all.

Is this a US or EU device? The latter has less space..

Are you SURE CLK requires 280 MB? If this us not a typo how much space is given to system and data?

---

Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wcstick:
It seems to be an EU device since it doesn't have any of the indications that it's the tmous device. But it will be used in the US.

I don't think cLK itself requires 280 MB, I set it to a higher value than what was mentioned in the ROM thread. I'm probably wrong in assuming that, when the thread says "System partition size 275," it means the cLK partition. I apologize for selecting an unstable ROM, I just picked one that I'm vaguely familiar with (i.e. CM). Should I lower the cLK partition?
[HD2 Android Q&A, Help & Troubleshooting and Genera] NYLimited:
Look at it this way: once you get one rom to boot the rest will be much easier to try. :)

Okay, let's backup a little and get on common ground. It may not seem so but we're making progress.

Please keep in mind I have never installed cLK so am not sure about it. However, cLK, like Magldr, is a bootloader. As such I suspect it. Does not use a traditional partition.

I am guessing that the 280 is intended for system. The EU Leo has 512 MB if NAND space. The US (tmobile) version has 1 gb. They have, essentially the same RAM.

Your NAND memory needs to be devided into partitions: boot, system, data and, possibly cache and misc. How these are created is likely specific to your bootloader (cLK or Magldr). The file systems often are dictated by those as well - Magldr uses different formatting for the boot partition than cLK.

Anyway, you will need someone cLK knowledgeable to help if you cannot spot the problem. BTW, which version of cLK are you using? I *think* v1.5.x black is one of the preferred versions.

Once you are able to load the bootloader you can start dealing with the rom. If your device is a 512 MB EU model start with a smaller rom or one that offers DataOnEXT installation.

I will check back to see what progress you will make but first a few hours of sleep (it is 3 am here).

---

Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wcstick:
Thanks for the help. I'll look into it tomorrow as I need to sleep as well. I've been thinking of trying Magdlr again since you're familiar with it. I know how to flash ROMs on Android devices (CWM) so yes, once I get any rom flashed, the rest should be fairly straightforward. It's just not going to that critical step...
[HD2 Android Q&A, Help & Troubleshooting and Genera] jvzijp:
I can really recommend you to try flashing the ROM through MAGLDR instead. I have CLK issues myself, repartitioning CLK on my HD2 also leads to hanging phone. Try repartition MAGLDR instead and then flash the ROM by using AD Recovery from MAGLDR menu.

Also, repartitioning with too large system size gives hanging problems on my phone. I think due to bad memory blocks and lack of space for the rest of the programs. Try different partitioning sizes.

Try THIS rom, it is in my opinion the most stable: http://xdaforums.com/showthread.php?t=1434860

Go for DataOnExt. The rom then needs 175MB, so go for 180MB system partition size when repartitioning MAGLDR.

Please create a FAT32 primary partition with 32KB cluster size, then an EXT4 primary partition with default cluster size on your SD card.

The EXT4 should be about 1GB - 2GB.

So:

1) Task29 (from phone bootmenu)

2) Install Magldr (from phone bootmenu)

3) Repartition Magldr 180 MB (from MAGLDR USB Flasher)

4) Format SD card with 2 partitions (MiniTool Partition Wizard Home Edition)

5) Place the ROM ZIP on the FAT32 partition

6) Insert SD card in phone

7) install ZIP from SD card (from MAGLDR AD Recovery)

8) Choose ROM ZIP

9) choose DataOnExt (in Aroma installer)

10) Choose Davik Cache Wipe (in Aroma installer)

11) Reboot when done

12) Have fun with Android ;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] mengfei:
make sure the HD2 is not fake, there was one here before & he showed a photo of it & it really looked like the real thing, also use the HD2 Toolkit to make it easier for you.

& since it's a T-mobile there are certain Radios that can brick that model if it is such (1g version) so better do a little more reading & there are lot of reference here in XDA.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wcstick:
Thanks for the help. I will try it when I get home later and report back.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wcstick:
I think I've bricked the phone...I tried flashing Magdlr again but got only the header when it booted. So I task29'd it again and attempted reflashing. It got stuck at 96% for a super long time so I did a battery pull. Then I tried booting it into recovery and it does nothing but vibrate...recovery, hard reset, nothing works...looks like the end of the road for this phone.
[HD2 Android Q&A, Help & Troubleshooting and Genera] NYLimited:
If you truly bricked it the phone would not do anything - would not go to 96% or anything. :)

If Magldr did not finish you certainly would not have a recovery installed yet.

Task29 is over-rated and, in most cases, simply unnecessary. You are wearing out your NAND memory if you keep doing it.

OK, so having said all that.. Did you try a different USB cable, a different USB port, re-installing the Windows side of the software (ActiveSync?)

Look for MSKIP's guide to flashing the HD2 - it should get you past the MAGLDR install.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wcstick:
Er, I meant to say I think I've bricked it after I tried reflashing Magdlr. It does nothing but vibrate when I attempt to turn it on now.
[HD2 Android Q&A, Help & Troubleshooting and Genera] NYLimited:
You cannot even get to the tri-color bootloader??

You didn't overwrite HSPL somehow, did you?

Before you try anything else make sure your battery has a decent charge (at least 50%).

The last thing you want is to die in the middle of these steps.

If HSPL is (or should be) OK, disconnect the device from any external power source. Remove the battery and place it back after a short while. Remove the HD2's back cover and press (and hold) the volume_down key. Press in the red reset button under the back cover to the bottom left of the SIM (you will need a sharp object for this) and release the soft reset button but continue to hold the volume down key in until you are presented with the tri colour bootloader screen.

If you get to the boot loader, make sure you have HSPL in tact. You can use this mode, with the tri-color screen, to flash Magldr later.

If you made it this far try the following steps.

Make sure you are using the correct radio - this can create serious problems! YOU NEED A RADIO WHICH SUPPORTS 576 RAM (2.08.50 or later should be fine but the Radio NEEDS to be 2.**.50.**). I recommend the 2.15.50.14 radio

The Original MAGLDR thread by Cotulla is

here

if you need it. MAGLDR doesn't replace OSPL/HSPL. It runs in the chain after. So it's safe to install and remove it Once you are in the tri-color bootloader mode:

Synch Phone with PC in Windows Mobile!!! It has to be connected to activesync or WMDC via USB cable. As an alternative method to activesync you can restart your phone in Bootloader Mode, then connect the usb cable and wait until 'usb' appears in the bottom half of your phones screen

Browse to the folder you extracted your Magldr Package files to on your pc, right click on ROMUpdateUtility.exe and select Run as Administrator (Win7 or later)

Tick the box to confirm you are aware of the risks and select 'Next'

Tick the box to confirm you have followed the preperation steps and select 'Next'. The program will check the usb connection.

Select 'Update'

Verify the image you will flash (it should say 2.00.000.0) and Select 'Next'

Read the process list and Select 'Next'

Your phone will enter BootLoader Mode and the progress will (hopefully) goto 100%

Your phone will Reboot. You should now have MGLDR installed.

To Enter MAGLDR Menu Screen after installation, Long Hold the Power Button when resetting the phone and the menu will appear

If you make it this far I suggest you now run DAF.EX to repartition and update your recovery software. We can talk about this step next - let's ee if you can make it this far!
[HD2 Android Q&A, Help & Troubleshooting and Genera] warpedspeed:
Frustrated with the whole process...What process?

I have spent WAY too many hours this weekend reading through threads here and elsewhere, with the goal of converting my T-Mobile WMo HD2 to Ice Cream Sandwich.

I have seen three for four different message thread that seem to contradict each other on what the process is.

Here is what I have done.

Changed to 2.08.HSPL. It was 2.10.000 .

Flased MAGLDR and it is working.

So I currently have a useless phone, although not bricked.

I had to use an old WinXP Laptop, since my Win8-64 Laptop would not see the phone.

Downloaded a ROM, NexusHD2-ICS-CM9-HWA_v2.9a .

Apparently there should be an Installer or a Daf included, but there is not.

I tried running Daf from the directory on the PC where the MAGLDR installer and other utilities are, like others have. Now I know that that will not work.

The current NAND Toolkit will not work on 32 bit windows. This is according to bzdemes here http://xdaforums.com/showpost.php?p=19931919&postcount=501 . It certainly does not work on my Windows XP, "hd2toolkit.exe is not a valid win32 application" .

If my Windows 8 Laptop would see the phone, then I suppose that I could try it there, but once again, that does not work. I do not have access to any more Windows 7 PCs.

I have since seen messages indicating that I should have done Task29 before flashing MAGLDR. I have seen other messages indicating that it is not necessary. Of course, no usable toolkit, so here we go back into the loop of failure again...

I have wasted an entire weekend on this and have nothing to show for it, other than a non-usable phone.

I know that you guys put a lot of effort into playing with this stuff, but I really hope that someone here can provide a clear concise process for those of us who do not have play time.

FWIW, I am a noob at converting phones to Android, but I am very technical otherwise, with nearly thirty years in IT and Telcom / Data. Clearly this is not rocket science, but for those of us who do not have this specific experience, and generally have all of our time consumed by our non-Android jobs, this is a challenge.

Thanks

Dean
[HD2 Android Q&A, Help & Troubleshooting and Genera] warpedspeed:
Yesterday I had a chance at work to try another Windows XP PC that is pretty much just used for testing. It has a fairly fresh image on it. I had the same Win32 error on it with the NAND toolkit.

I also was able to get my hands on a Win7 32 bit PC, with the same result.

Then I was able to “commandeer” a PC that was going to be re-imaged anyway. I put a Win 7 64 image on it, and sure enough the toolkit worked.

So it appears that the NAND Toolkit works on Win 7 64, and possibly Win 8 64, but support for 32 bit Windows appears is over, unless the program gets fixed.

The problems that I was having with synching the phone on my Win 8 64 PC may have been due to using a USB3 port. Last night I was able to see the phone on that PC with a USB2 port. I should have tried that this last weekend.

So I ended up using the Toolkit yesterday, before I saw your reply. I did look through the partitioning guide that you referenced. I opted not to go with the Data on EXT option. It is a 1Gb T-Mobile HD2, so I am in good shape there. I did not want the operation of the phone to be dependent on a relatively slow SD card. I will just keep optional data there, such as music, pictures, and documents. I will keep anything important, such as programs and notes that I use for reference in the main memory. I do not have all that many extra programs or data.

So I am up with the ICS-CM9-HWA_v2.9a build and it is pretty good. So far I like it. Previously I was doing a dual boot, using Haret and a Gingerbread build, basically as a test, and while I was waiting for some Android apps to mature, that initially were not a good replacement for some specialized WinMo apps that I had. I finally have all of the functionality that I need on the Android platform.

For me, the biggest challenge in this was the variety of documented procedures that are out of synch, and mostly out of date. For instance Mr Skip’s guide is well written, but out of date to the point that it sent me down the wrong road. I am not picking on Mr Skip, in fact his guide was the best written of the bunch, so that is why I mention it.

If I am the last guy on this particular planet to make the switch on an HD2, then it is probably is not worth updating the docs out there. However there might still be a few holdouts in the wings yet.

If I can get my wife to stop using my T-mobile upgrade credits, then maybe I can get a newer hardware platform someday! Although I am very impressed with the longevity and durability of the HD2. That is a rare thing anymore.

Thanks for the help.
[HD2 Android Q&A, Help & Troubleshooting and Genera] NYLimited:
Glad you got it to work. I only have a couple of brief comments to add.

Going with option 1 is fine. You may or may not encounter limitations and you can always change later if need be. However, it should be noted that the HD2 NAND operates at roughly the same speed as a Class 4 card, hence you could not slow it much by using a card. :)

Mark's guides are indeed excellent and as you noted, somewhat dated since they were written early in the HD2 / Android days. A number of things have changed and I think Mark has moved on to Samsung or Nexus devices since that time. For good or evil his guides survived the test of time. :)

---

Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Marvlesz:
Don't say thanks, hit his thanks button ;)

Also, you said the device doesn't boot after you pulled the battery during a 96% flash.

MAGLDR is not supposed to brick your device, even if stopped midway. It is probably the battery pull that killed your device. Check the battery pins on the back of the device. Make sure they are straight and they make well contact with the battery, then try again.
[Samsung Galaxy Nexus] sykomaniac:
​

Description

Exactly the same as RootBox :)

So why the ROM?

A few people have been complaining of lag so I thought I would try and fix this. As I'm the Maguro maintainer I feel I need to at least try and resolve this issue.

What's different then?

This ROM is built using Linaro 4.7 tool chain, -03 arm cflag & strict aliasing all over the place :) It should feel silky smooth.

Will this be added back into Rootbox?

I hope so! I'm looking for real user feedback to see if my changes actually make a difference. If they do I will contact Bajee to see if I can get them merged in.

OK last question - why another thread?

Several reasons. The main two being:

1) Do not want to muddy the official RootBox thread - PLEASE DO NOT POST ABOUT THIS ROM IN THE OFFICIAL THREAD

2) To make people aware of this ROM.

Where can I get it?

Download it here: http://d-h.st/KSb

Use the Goo.im GAPPS: http://goo.im/gapps/gapps-jb-20130301-signed.zip

Installation Steps

1. Wipe Data

2. Wipe System

3. Wipe Caches

4. Flash RootBox zip

5. Flash JB GAPPS

6. Reboot
[Samsung Galaxy Nexus] sykomaniac:
Changelog

Changelog

Build 05/04

- Xposed removed

- Custom toggles for quick settings

- Other bits of cleanup e.g. removing navbar height from ROM Control

Known issues from my quick testing (sure these will be resolved soon):

- Cant activate the bottom 4/5 options in the new AOKP lock screen settings

- PA preferences is missing the pre-set configs (probably can get them from the PA ROM)

- Per app colour settings not really working as expected (specifically signal icons and nav bar colour - think this is due to AOKP settings)

- Disabling per app colour in hybrid settings -> interface causes a SysUI FC loop
[Samsung Galaxy Nexus] androidbaba:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

It is fluidy smooth and butterly touch

Battery looks OK too

go for it people..
[Samsung Galaxy Nexus] boki2911:
thanks for your great effort, reporting results
[Samsung Galaxy Nexus] chickentuna:
rootbox was great, and now with Linaro? This is pure awesomeness! Downloading now
[Samsung Galaxy Nexus] llevo3:
I'll try as soon as I get home
[Samsung Galaxy Nexus] boki2911:
rom is super fast and smooth so far no complaints

edit

settings sounds FC
[Samsung Galaxy Nexus] sergini:
Its awesome guys. Fast and smooth as rihana's ass!

And with RootBox features, what else can you ask?
[Samsung Galaxy Nexus] sykomaniac:
Works fine here did you do a clean wipe?
[Samsung Galaxy Nexus] boki2911:
I changed the kernel, perhaps to the fact
[Samsung Galaxy Nexus] sykomaniac:
Which kernel and I will test and what exactly did you do?
[Samsung Galaxy Nexus] sergini:
NO FC's here. Changed Kernel from stock to ak.

I even flashed BeatsMod and everything works great.
[Samsung Galaxy Nexus] boki2911:
AK

I'll try it again so I'll let you know
[Samsung Galaxy Nexus] slimdizzy:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

Love the go faster stripes. Can the next release have speed holes pleeeeeeease!
[Samsung Galaxy Nexus] boki2911:
SYKO

somewhere was my mistake, apologies, everything works great

it was a mistake due to return some data

AK work great
[Samsung Galaxy Nexus] sykomaniac:
No problem :)

Just remember test the ROM for a day or two and then start posting comments about speed etc :)
[Samsung Galaxy Nexus] boki2911:
Ok sorry boss:p:laugh::good:
[Samsung Galaxy Nexus] galapagos:
It's been rock stable and I threw a kitchen sink at it running all kinds of apps and different settings.

Awesome build with the highest quality.

Addicted to rootbox.
[Samsung Galaxy Nexus] androidbaba:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

Syco do you take requests:D

Can you do dual line date in notification bar also if you can make small cLock available on lock screen that will be awesome..
[Samsung Galaxy Nexus] kompressorgpl:
Hello! Where can I download RootBox
[Samsung Galaxy Nexus] crea78:
Found a bug when trying to install an apk from anywhere but the Play Store. It will let you try to install the app, bit when you click on Install nothing happens. All the other buttons are available to press like Cancel. This happens on the latest update.
[Samsung Galaxy Nexus] sykomaniac:
Are you using something like glovebox? I had this and its an app issue.
[Samsung Galaxy Nexus] crea78:
Yes I am using glove box. Is there another app that does the same thing as glove box?

Uninstalling glove box fixed the problem... thanks :)
[Samsung Galaxy Nexus] beababe:
Um, setting for navbar height is removed from latest build? only setting for width :/ why?
[Samsung Galaxy Nexus] Pelide:
mmm...First post?

rom http://d-h.st/L55

gapps http://goo.im/gapps/gapps-jb-20130301-signed.zip
[Samsung Galaxy Nexus] kompressorgpl:
Yeah! Sorry for my noobish!
[Samsung Galaxy Nexus] noviz69:
If i install trinity kernel i always linaro optimizations ?
[Samsung Galaxy Nexus] chickentuna:
Of course! Let's all enjoy the linaro smoothness and rootbox features
[Samsung Galaxy Nexus] ferozfero:
i think what he meant was..if he intalls trinity kernel will he lose linaro optimizations..?i kinda have the same question ,only for anarkias AK kernel..
[Samsung Galaxy Nexus] sergini:
No, you wont loose anything. Linaro are ROM optimizations, not kernel.
[Samsung Galaxy Nexus] noviz69:
Yes. Sorry for my english

Ok thanks :)
[Samsung Galaxy Nexus] chickentuna:
damn syko, this rom is smooth as hell. Believe me, I've tried different linaro optimized roms like Carbon, Atom, AK-47 you name it but this one is the most feature rich yet smooth that I've tried so far. My hunt for the best rom is over. Now I'm just restoring my apps(60+) and we'll see how far this baby will take me :D

EDIT: Restored 70 apps in total via TB, and guess what? That's right, it's still fast and smooth. After 2hrs+ of use no bugs, lags and slow downs so far. This rom is in full speed! Definitely a daily driver material
[Samsung Galaxy Nexus] macijeep:
WOW, I finally found the rom that i was looking for a long time, there is everything i was looking for :laugh:

Great work:good:
[Samsung Galaxy Nexus] fress:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

Syko.......GREAT work! Thank you

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] dialmformostyn:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

Tried a few Linaro ROMs between RootBox builds and was excited when Syko mentioned merging the two - I'm pleased it's lived up to my hopes! Truly excellent work, old chap.
[Samsung Galaxy Nexus] marantzpm55:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

Excellent work! One small thing for the future "hopefully" button for 'kill all' in 'recent apps'. No ofence Sir...:thumbup:
[Samsung Galaxy Nexus] npalmy:
Re: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

Kill all in general UI settings.

---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------

Clean install with AK kernel and everything running well. Will report back after a few days running. Thanks
[Samsung Galaxy Nexus] tomixdev:
AW: [26/03][ROM] Chocolate Sprinkles RootBox - Now with go faster stripes

im gonna re-virginize my phone (delete everything), and start away with this promising rom! i'm sure this will make me and my phone happy for a month or two (or at least till the storage is full again). thank you! :thumbup::thumbup:

53nT fr0m my g4Laxy neXu5
[Samsung Galaxy Nexus] Dosentod:
Is Linaro really notably better?

I am on SlimBean for now, but this Linaro thing sounds very interesting :good:
[Samsung Galaxy Nexus] kompressorgpl:
Hello! Download now!!!!
[Samsung Galaxy Nexus] Doomhamma:
I read somewhere that a couple of developers tried to find out the difference, and they came to the conclusion that ROM's get 30 - 100 % speed increase ( it varies ) when using Linaro toolchains .. So, I guess it is!