Questions & Troubleshooting
while using this version of SLIM ROM JB
Step A & B - HSPL, Radio
Install HSPL and the latest radio (probably most of you have done this, if not, search in Xda)
(It is recommended to task29 before flashing bootloader, but not necessary)
Step C - Flashing Bootloader
Two type of Bootloader available for cLK or MAGLDR
First lets go to pro's and cons
Benifit MAGLDR over cLK
*Supports RMNET which is very stable data connection
*Support booting of WP7
*Boot a second faster than cLK
*NativeSD boot kernel don't occupy any space in Nand(Phone memory)
Benifit cLK over Magldr
*Support charging when device is OFF
*Behaves more like native android device, supporting fastboot and booting into recovery using ROM
*You can change system size by editing in settings, unlike Magldr we need to flash bootloader again.
Decide which Bootloader you want to flash: cLK or Magldr
Download Bootloader.zip and extract the content to a folder
Press and Hold volume down key and press switch on HD2. You will be booted into HSPL showing serial. Plug in the USB. HSPL will display USB
Run "LeoAdvancedRUU.exe" as administrator
Select "Regualr RUU (Task28) - recommended for flashing NBH with OS section
Select NBH file the bootloader you want (Selecting clk.nbh will flash cLK bootloader or magldr will flash MagLDR bootloader)
Click "Next" (This will flash bootloader, wait for it to finish and let it reboot)
Step D - Flashing recovery and setting system partition
Understang of partitions: The Phones ROM has been partition into the following: Misc, Recovery, boot, system, cache, and data
Misc 1MB, boot 5MB and cache 5MB sizes are the same for most of ROM unless specified.
Recovery partition size depend on the Recovery we flash (For TWRP it is 9MB )
ROM develeper usually specifies the size of ROM, example system=300MB so we need to adjust system partition size accordingly.
The remaining space will be assigned to data automatically.
If you are planning to use data2ext, make system size 380MB as data partition isn't used, we can utilize everything for system.
Step E - Partitioning SD card
Partitioning SD card with ext4 (only required for data2ext and nativesd, this step is not needed for nand type installations)
Once booted in recovery, go to "advance" > "partition SD card" > and choose size for sd-ext partition by moving the slider.
And "swipe to partition" will start creating and formatting partitions
Step F - Installating ROM
TWRP can mount sdcard as USB Mass Storage by choosing Mount>Mount USB Storage.
Copy the installation ROM Zip file to sdcard. Safely remove device in Windows and Unmount from TWRP recovery
In TWRP main menu click install and choose installation zip file and swipe to install.
Step G - NativeSD Boot
When we installed NativeSD, the Bootloader doesn't know how to boot it. On power on it will still boot the Nand ROM. So we need to make the bootloader boot nativesd rom. Heres how
If we have installed a NativeSD ROM, we need create seperate boot partition for storing the NativeSD kernel. in clk we can add 4 more secandary boot partitons. sboot, tboot, vboot and wboot (Offcource this comprimises nand space). To add/remove secandary partition go to clk settings
Now we can flash NativeSD kernel on Sboot. 3ways of doing this. I have already included an option in aroma installer to flash sboot whilst installing rom. However if you are on other rom, you will need to flash sboot2.zip (search in xda) or you can goto twrp recovery>advance>native manager choose your secandary boot and rom.
For Magldr is rather simple. We don't need to add secandary boot partiton for nativesd. Just show the location of the kernel on sdcard.
Goto Magldr main menu. now select Services>BootSettings>AD SD Dir and choose the NativeSD folder on sdcard.
Step H - Default kernel and Mulitboot options
Now that we have STEP G, I will try to explain about Default kernel and Mulitboot options.
When to bootloader boots into ROM we need to tell the bootloader which ROM we need to boot into, this is done by choosing default kernel
When We enable ShowMultiboot the bootloader will ask the user to choose the ROM that need to be booted into. (Clk will wait for 5seconds for user input and then will boot in defualt kernel whereas Magldr will wait forever until user choose the ROM)
User A: I want my HD2 to directly boot into Nand(or Data2ext) ROM when I switchON my hd2
User B: I want my HD2 to directly boot into NativeSD ROM when I switch ON my hd2
User C: I want my HD2 to ask me which ROM should I boot, when I power up my HD2 and I will choose everytime which ROM to boot
User A and B wants to directly boot into their ROM type without asking (so they need to disable ShowMultiboot) but User A need to set Default kernel as NAND and User B has to set default kernel to NativeSD
UserC has to enable show multiboot.. Below are steps how to achieve this
Boot into Clk, Go to settings
You will see set default kernel. If you choose Nand it will boot into Nand(or Data2ext) ROM. (UserA should do this)
If you choose sboot(or on of the secandary) it will boot into NativeSD ROM. (UserB should do this)
If you enable show multiboot it will wait on the clk boot menu for 5 seconds. If you don't choose within 5 secs, it will boot to the default kernel selected (UserC should do this)
Boot in MagLDR main menu.
We can set default kernel by going to Services>BootSettings>BootSource.
Choosing Boot from NAND will automatically boot into Nand or Data2ext everytime we switch on HD2 (UserA should do this)
Choosing Boot from SD will boot into NativeSD automatically, without asking, everytime we switch ON HD2 (UserB should do this)
We can enable show multiboot by going to Services>BootSettings>Always Menu. . Choosing Green-Yes will activate Show Multiboot(UserC should do this)
Is there a reason why should I replace my CWM 184.108.40.206. with 4ext recovery? I mean,is it better, does it have more options, is it more stable...?I'm asking this cause 4ext was recommended here as recovery type.
Will the flashing of 4ext wipe my rom and everything? I never flashed another recovery but cwm,and that was way back when my phone was still running WM.
Sorry for asking this here,but like I said ,only cause 4ext was mentioned here.
Sent from my Htc Hd2 using Tapatalk 2
Hi Lincoln357, I think you should try another recovery, you might then be able to boot a pixeldroid rom, just a thought.
That said, I had trouble with this ROM on nativeSD booting from wm6.5.
I first tried launcher2 from aroma, after booting and at end of setup i had setup not responding (wait/force close) and could not get to launcher (home button pressed). After reboot it hung on slim bootscreen.
Fresh install same sdcard, and it hung on slim bootscreen. (note sdcard was previously formatted with gparted)
Fresh install new sdcard, chose nova, same problem with setup and couldn't get to launcher. (formatted with minitool)
Fresh install, same new sdcard, formatted sdext with recovery (4ext sd version edited by Xylograph, never given me problems before) and finally got it to go to launcher. Phew
So a combination of sdcard and formatting got me there. It is odd how some roms are sensitive to these things
Lastly, I think the same problem with tytung's aroma script with ppp is occurring here. If you leave rmnet as default (booting from wm6.5), there is no data. you must choose ppp to get data despite there being a checksys.sh and lines in updater.script which should force ppp install for haret booting.
Anyway, its great to see Slim ROM back on our hd2, it seems really fast.
Excellent job max18mac and thanks for your continuing support for our hd2
|Thread Tools||Search this Thread|