Related
Hi there, as many of you may know dzo or simple god makes a flashable version of android for our KAISERs.
But vefore here are some rules:
THIS THREAD IS MADE TO KEEP THE FLASHING ANDROID ON KAISER DEV THREAD CLEAN FROM USERQUESTIONS!!!
DON'T ASK USER QUESTIONS IN THE DEV THREAD!!!
This Thread is for experienced Kaiser users who aren't in development but wan't to see android running native from NAND.
THIS IS AT THE CURRENT STATE VERY VERY VERY BETA, THERE MAY BE A HIGH RISC TO BRICK YOUR DEVICE. THIS WILL COMPLETLY WIPE WINDOWS MOBILE. JUST USE IT IF YOU CAN ANSWER YOURSELF THE FOLLOWING QUESTIONS: (without search function)
-What is an .nbh file
-how to flash a kaiser
-What is HardSPL /Security unlock
-How to recover a bad rom flash?
-What to do if your device won't start anymore?
-Do you have basic android skills?
Ok Guys, little cleanup and updates:
INDEX:
-Post one:
Different flashing methods
Things to take care off
-Post two:
How to creat your own nbh files
How to make custom splash screens
-Post three:
Working Systems/rootfs
Bugs
Usefull Links
Thanks
HOW TO START ANDROID FROM NAND
Method one:
1-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
2-Download http://www.mediafire.com/?zldjhfnkzk2
3-Copy the androidinstall.tar from the androidinstall.zip file to the root of your sdcard
4-delete/rename any old android files on your sdcard
5-Unzip the androidinstall.zip and replace the ruu_signed.nbh in it with the one you downloaded in the first link. (must be named ruu_signed.nbh)
-6Run the custom ruu.exe - thats all after reboot you'll have a flashed Cupcake android.
Method two:
1-delete/rename any old android files on your sdcard
2-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
3-Create three empty files on your sdcard wihout any extension:
-datafstonand
-systemfstonand
-rootfstonand
4-Copy your prefered rootfs.img, system(img,ext2,sqsh) and an empty data.img to sdcard root
5-Copy the nbh file you downloaded to the root of your sdcard and rename to kaisimg.nbh
6-Reboot your device using restart button and cam button, then when it tells you, press power key to flash the new nbh.
-Reboot by pulling the battery - Thats it ( First start may take a while and may reboot randomly, just give it some time)
Different Tricks and hints (collected in the forums):
-Change Panel Type:
Run: "echo 1 > /sys/module/board_htckaiser/parameters/panel_type" through adb or init
-Experimental GPS:
For working, gps you need to replace libgps.so with the one from the vogue gps thread.
Experimental openGL Drivers ( Eclair Only)
-Download this one and flash your prefered nbh: http://rapidshare.com/files/345432577/kasiandroid_nbh_with_opengl.zip
-Install the included script sheduler, and replace the afterboot.txt with the one included in the zip file
This will install an app that will run the afterboot.txt after every boot and fix file permissions.
-Or you can open the afterboot.txt and run it in terminal after every boot.
To see if it works install the included gallery3d.apk, iff you see thumbnails, it worked
Not tested by me, yet through no time.. (Thanks to quitlahok and rzk333 for this manual)
THIS IS JUST FOR THOOSE WHO ARE MORE IN DEVELOPMENT AND LINUX
HOW TO CREATE YOUR OWN NBH FILES:
1- Set up your prefered Linux Setup, i use Debian.
2-Build kaiser kernel with wiki manual
3-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/tinboot
4-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv
5-cd bootenv
6-cp buildInitrd buildInitrd-mini
7-nano (or whatever your favorite editor is) buildInitrd-mini
8-change all instances (2 of them) of initrd to initrd-mini
9-sh buildInitrd-mini
10-cd tinboot
11-nano tinboot.S
12-the paths to fix are at the bottom of the file, it's pretty self-explanatory. higher up in the file you'll see the kernel cmdline under an .ifdef kaiser line
13-after that you'll need to download and extract any windows kitchen, and install wine however your linux distro requires and make a note of the path you extract nbhmerge.exe to as you'll need it in your tinboot.S file, along with the path to your kernel zImage and initrd-mini.gz
after that if you've got everything else in place, go ahead and run the compilekaiser script in the tinboot dir and you should have an nbh
if the nbh won't flash (i had this issue) copy the output.nb file, boot into windows, and use nbhutil.exe to convert it to an nbh and flash that one. for some reason yang doesn't work right for me personally
HOW TO CREATE CUSTOM SPLASH SCREENS: (this is a manual by POV)
1. Install HardSPL.
2. Create a BMP file in paint, size must be 240x320, save it as BMP 24bit.
3. Download SplashTool
4. Load your BMP on nb_image_converter (included in SplashTool's zip) and save it as splash.nb
5. Open SplashTool.exe and convert splash.nb to new format.
6. Pack the resulting splash.nb into a NBH file using htc rom tool.
7. Flash your cusotm NBH using CustomRUU.
This will not harm your installed android
WORKING SYSTEMS / ROOTFS'S: ( Collected in the forums)
- http://forum.xda-developers.com/showthread.php?t=587116 ION Donut, reuploaded by 160bpm
- http://forum.xda-developers.com/showthread.php?t=619980 MYNs warm Donut
- http://forum.xda-developers.com/showthread.php?t=619718 Jamezelles Sense Tattoo
- http://forum.xda-developers.com/showthread.php?t=591104 Plemens Donut AOSP
- http://forum.xda-developers.com/showthread.php?t=603028 Jamezelles Sense Hero
- http://forum.xda-developers.com/showthread.php?t=619285 Shidells Android 2.1
rootfs 2010-01-06 works best for me get it here: http://sourceforge.net/projects/androidhtc/files/
Bugs:
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth
(GPS experimental with the files from first post)
Usefull Links:
Android on Sourceforge:
http://sourceforge.net/projects/androidhtc/files/
Android on htc Website:
http://www.androidonhtc.com
dzo's page:
http://it029000.massey.ac.nz/vogue/
Android SDK:
http://developer.android.com/sdk/
Tinboot dev thread:
http://forum.xda-developers.com/showthread.php?t=614275
Thanks:
dzo, plemen, jamezelle, zenulator, enatefox, mssmision, vilord, rzk333, diagdave
SORRY IF I'LL FORGET ANYONE
Here's a couple boot screens I made.
Thanks i'll add this to the first post
Thanks JeckyllHavok, good idea I keep posting over here am not into kernel things anyway
Ok after a few attempts I finally got Android flashed, and running, using my backup kaiser, which has no network connection, so the lack of wifi is a bit of a problem, but seems to be working fine so far, and fast
Just wondering if it would be possible to flash other versions, like eclair or even flan, since polyrhythmic's eclair version seems to be nice and stable, or is this going to fast to soon?
Just tested this with sshidels nexus rom, but itjust ends in bootscreen loops. Maybe other roms work
Looks like in need to learn to read. I found these instructions in the Vouge forum:
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
Click to expand...
Click to collapse
Buried for stupidity. Works great so far.
Flashing now.
1st edit: We have Android .
2nd edit:26 min it just turned itself off ... creepy ... soft reset ....I'll post back results.
3rd:39 min later Actual Phone screen came up No SIM ..Opps rebooted waiting agian.
What is working/not working with this flash.
From what I've read everything except.
Blutooth
wifi
GPS
Still waiting back at ANDROID screen
I have successfully flashed THIS BUILD using the following method:
dzo said:
...create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Click to expand...
Click to collapse
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
loserskater said:
I have successfully flashed THIS BUILD using the following method:
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
Click to expand...
Click to collapse
Hi
Can you please send me the files on the sdcard. I am having an issue with every build.
Thanks
Did wifi work with any builds?
I think no, not now
Tilt
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Jaguarius said:
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Click to expand...
Click to collapse
Are the keys on the slide keyboard working correctly
OK now got two nand flashed kasiers, (both kais130), first using the 'original' flash method, ( dzo nbh, androidinstall.tar), and the other method from the vogue threads, with polyrhythmics Eclair build, which is much slower, ( uses SD card rather than Nand?).
Both seem to be working as well as can be expected at this early stage of Nand flashing.
What I would like to know is how to 'upgrade' our zImage, since some builds have a different zImage version than the one we are currently flashing with, ( I am assuming our zImage is in the NBH flash), since this may help enable wifi/gps which we are presently lacking.
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
vuedesprit said:
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
Congratulations. You win the "most questions asked in a single post" award.
Sent from my Desire HD using XDA App
That is a ridiculous amount of questions, and the thread is in completely the wrong area of the forum. I'm sure you'd find the answer to pretty much all your questions if you looked hard enough, but to answer the one about multi-touch. It is multi touch and all the games I've played from your example 'Gameloft' are multi-touch, so I don't know what you're smoking buddy, but ease off.
1. Inb4 "search".
2. Wrong forum.
3. No really, try searching. At least 30% of that is googleable.
Sent from my Desire HD using XDA App
Ok guys, thank you all for your replies, and yes I knew that a war and flames will go on here, but seriously if you think this is ridiculous or newbie or most dumb questions, do not turn the way of the thread or flame me, my intentions are to make this as a one small guide for most new androids functions, it's not a bad thing to do, in fact I will learn as much as other new users here, no one is asked to answer all those ridiculous questions, just answer what you know about, guys please take it seriously and easy, saying look harder will not help the thread, it may help me personaly, but be sure that I did a lot of search, and it will not hurt to put everything in one place, and as you can see, I answered most of the questions up to what I gathered, you can correct me about my answers, put your thoughts or not answer at all, but please be constructive here, and if you all think that i'm in the wrong forum, or asking too much, or asking ridiculous questions, please moderator feel free to do what you think is better for the forum.
Sorry guys for bothering you. Thank you for your response.
N.B.: just to be more accurate, I tried the prince of persia pre installed on the phone by the dealer, and it was not multi touch, so you cant walk and use any of the right actions at same time.
@vuedesprit: Good thread, and thanks for taking all the criticism from the more experienced users.
@all chimers chiming the "use search, wrong forum" tune: c'mon guys, there's at least 2 of us reading this thread going, it's about time all this information got consolidated into one place! The easier it is to find this information, the easier it would be for more of us to get engaged in the process and thus further development, enhancement and adoption.
While our "friendly" mod is doing his best to keep the forums clean, they're as fragmented as ever and from time-to-time, it becomes necessary to consolidate the information into a single thread. I'm sure most of you started some place too and remember the time not so long ago when it was difficult to find even the most basic info? I think by sharing your knowledge, you will gain a much better following and the platform will gain much better adoption.
My 2 cents worth anyways...I've had my DHD for 3 days now and I too am struggling to perform even the most basic tasks.
We really need a questions and answers sub forum
Fair enough, maybe my first comment was a bit rash, but I didn't mean to appear rude. I shall try to answer some questions here:
GENERAL.
1. From my own experience all games advertised as multitouch are exactly that. I don't know about the version of PoP that you have installed from carrier, but I do find that odd.
2. Hard reset is a little perverse with the new "fastboot" hibernation feature that HTC have implemented. You have to go to MENU>SETTINGS>APPLICATIONS and disable "fastboot" (this is where confusion may arise as this is not the bootloader fastboot that allows images to be flashed)!! Now when you hold down the power button and get the option to power off, you will properly power off the phone. Next if you hold "VOLUME DOWN" and "POWER" buttons you will reboot into HBoot, from here the VOLUME UP/DOWN keys navigate the menu and POWER selects menu options.
3. Not sure about this one.
4. Since the release of FROYO you can go to MENU>SETTINGS>APPLICATIONS>MANAGE APPLICATIONS then select any app and move to either SD or to phone memory.
5. The folders on the SD card are mostly generated by the phone when you first insert it. The user guide and HTC sync software are there to move onto your PC for safe keeping. If you insert a freshly formatted SD card, the phone will make fresh folders such as DCIM for pictures, etc...
SYSTEM INFO.
1. Baseband is radio software.
2. Kernel is the linux kernel that is running below Android, this can be updated separately from the main ROM, radio etc. HOWEVER CAUTION IS ADVISED AS CERTAIN KERNELS WILL NEED NEW MODULES FOR HARDWARE TO FUNCTION CORRECTLY as you will see from the wifi modules bundled with the OC kernels.
3. Build number pertains to HTC's internal software version classification (some are built specific for carriers) they are generally released via RUU (ROM Update Utility aimed at windows) or OTA (Over The Air update received on phone [again sometimes carrier specific]). Release keys pertains to the fact that the firmware has been signed by HTC (I think).
4. Software number, basically as above.
OTA ACE with Radio.
1. As Above.
2. ACE: internal HTC name for Desire HD (also reportedly known as "SPADE")
ROOT DESIRE HD ETC.
Most of what you have written is pretty much correct.
MORE THINGS TO KNOW ABOUT.
1. http://developer.android.com/guide/developing/tools/adb.html
2. http://www.busybox.net/about.html
3. http://android-dls.com/wiki/index.php?title=Fastboot
4. eMMC write basically means that you can write to the internal phone (normally protected) memory such as /SYSTEM, this is what S-OFF allows you to do whenever you want. However, the modules that allow the ENG HBoot image to be flashed are what really accomplish this in the first place so theoretically you could just run that module every time you wanted to write to /SYSTEM but that would become very tedious very quickly. I can't really explain further, as I don't have the knowledge.
5. EXT2 or EXT4 are filesystem structures just like FAT, FAT16, FAT32, NTFS, HFS+ etc, EXT4 is newer and more advanced than EXT2 and therefore is more efficient. (kinda general but you get the idea. NEWER=BETTER)
6. ROM manager, find this in the android market, it is free, you install it on your phone and with the addition of clockworkmod it gives you the ability of flashing ROMs etc. USE WITH CAUTION.
I hope that this answers or clarifies most of what you have asked or said, please feel free to cut and paste any of this info into your first post so that we can actually consolidate this.
P.S. I too am a complete android noob and this is my first android phone, I have picked this info up mainly from this forum so all credit for information goes to XDA-DEVELOPERS.COM and not me.
Cheers,
Dok
berek9999 said:
congratulations. You win the "most questions asked in a single post" award.
Sent from my desire hd using xda app
Click to expand...
Click to collapse
+1111111111^2
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
Click to expand...
Click to collapse
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
2-What are the buttons combinations for the different operations like hard reset & boot loader?
Click to expand...
Click to collapse
boot loader = turn phone off. then, volume down + power on.
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
Click to expand...
Click to collapse
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
Click to expand...
Click to collapse
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
Click to expand...
Click to collapse
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
Click to expand...
Click to collapse
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
How to root Desire HD install h-boot (S-Off) and Clockwork recovery?[/U][/B]
Click to expand...
Click to collapse
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
Click to expand...
Click to collapse
android application. eg, visionary+.
2-Hboot
Click to expand...
Click to collapse
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
Click to expand...
Click to collapse
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
Click to expand...
Click to collapse
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
Click to expand...
Click to collapse
see above.
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
Click to expand...
Click to collapse
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
1-What is adb?
Click to expand...
Click to collapse
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
2-What is busybox?
Click to expand...
Click to collapse
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
2-What is fast boot?
Click to expand...
Click to collapse
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
3-What is eMMC write?
Click to expand...
Click to collapse
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
Click to expand...
Click to collapse
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
This thread is amazing!!
We had a lot threads like this in the HTC Blackstone Board of pocketpc.ch....
Hope to get more threads like this in every device category....
Thumbs up
Perhaps Threadstarter can write the answers in the first post...??
50chickens said:
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
boot loader = turn phone off. then, volume down + power on.
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
android application. eg, visionary+.
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
see above.
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
Click to expand...
Click to collapse
Thank you very much.
Hello guys,
Although we now have one-click programs that root our Evos, I am simply the type of person/geek that needs to know the "In's and Out's" and the "why's and how's" of how something works.
I rooted my Evo back in June of 2010 when it was launched, using the then complicated and long process in adb shell. Although I did not stumble in the process at all, I did not know what was really involved and simply followed directions.
With that said:
One of the many Files (flash_image), (mtd-eng.img), (PC36IMG), (recovery.img), needed to root my Evo was the "mtd-eng.img" file.
Can anyone please explain what this file is and it's purpose.
Evidently nobody is going to answer this. I need to know this now too, that is why I bumped this dust bunny. I can't find much information on the system files and mounting points of the partitions. Specifically, mmcblk0p2. Can anyone explain to me any of this? Including what the mtd-eng img file is and what it does?
TheEvoNoob said:
Evidently nobody is going to answer this. I need to know this now too, that is why I bumped this dust bunny. I can't find much information on the system files and mounting points of the partitions. Specifically, mmcblk0p2. Can anyone explain to me any of this? Including what the mtd-eng img file is and what it does?
Click to expand...
Click to collapse
Some one else might know about the mmcblk0p2 block.
The best way to think of the mtd-eng.img is as follows:
The mtd-eng.img is an image of the phone's misc partition as it was on the Evo's initial pre-engineering software state around the time of it's release.
Everytime you run a RUU or flash anything, the misc partition is updated, in particular with the android.txt file. It updates the RUU number (3.70.651.1, 5.07.651.6, etc.) for the misc partition. This, the misc partition, is one of the places where the phone looks to determine whether the phone will accept or reject you trying to flash a RUU when the phone is S-ON. The phone is designed to reject any RUU number that is below that number that the misc partition is reading. That is why you cannot normally downgrade a S-ON phone, because the Software state that you are on, which is being read by the misc partition is greater than the software number of the RUU which you are attempting to flash (downgrade).
The mtd-eng.img is an image of the misc partition at its earliest state, with the lowest RUU number there is. All other RUU numbers are currently greater than this number and not less than, so this is why you need to flash this file if you are trying to downgrade a S-ON phone's software version. The software number which is being read by the misc partion after flashing the mtd-eng.img file is less than all the RUUs software numbers that exist for the Evo. The effect after flashing the mtd-eng.img file and then running a RUU is that you are actually tricking the phone into thinking that it is upgrading, which it is more than willing to do.
Sent from my SAMSUNG-SGH-I747 using xda premium
shortydoggg said:
Some one else might know about the mmcblk0p2 block.
The best way to think of the mtd-eng.img is as follows:
The mtd-eng.img is an image of the phone's misc partition as it was on the Evo's initial pre-engineering software state around the time of it's release.
Everytime you run a RUU or flash anything, the misc partition is updated, in particular with the android.txt file. It updates the RUU number (3.70.651.1, 5.07.651.6, etc.) for the misc partition. This, the misc partition, is one of the places where the phone looks to determine whether the phone will accept or reject you trying to flash a RUU when the phone is S-ON. The phone is designed to reject any RUU number that is below that number that the misc partition is reading. That is why you cannot normally downgrade a S-ON phone, because the Software state that you are on, which is being read by the misc partition is greater than the software number of the RUU which you are attempting to flash (downgrade).
The mtd-eng.img is an image of the misc partition at its earliest state, with the lowest RUU number there is. All other RUU numbers are currently greater than this number and not less than, so this is why you need to flash this file if you are trying to downgrade a S-ON phone's software version. The software number which is being read by the misc partion after flashing the mtd-eng.img file is less than all the RUUs software numbers that exist for the Evo. The effect after flashing the mtd-eng.img file and then running a RUU is that you are actually tricking the phone into thinking that it is upgrading, which it is more than willing to do.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I had Hboot 2.18 with the latest update, 5.07.651.6. When I first rooted it was hard to even find info for the newest system update. I tried every PC36IMG that I could find. All were rejected. Now I know why. Man, this was pretty awesome info. Thank you for taking the time. You're awesome bro.
Hi everyone!
What we need:
A kernel hacker!
Why?
Because of this:
no.human.being said:
Yep this is great. This routine will definitely play a key part for our further investigation. The plan I have is the following ...
I'd like to dump the device's Flash memory (physically, via JTAG), disassemble its contents (e. g. with objdump, as I'm not familiar with IDA and it actually looks quite "advanced") and find where the ARM starts execution. This is probably a fixed address, might find it in the processor's datasheets. There are no datasheets available for the MSM7227, however, it is a replica of the ARM1136EJS for which there are no datasheets either, but there are extensive datasheets for the ARM1136JS, which is probably similar. Just search for the document "ARM DDI 0211K" on your favourite search engine. It's very extensive, so there's really not much that should be "undocumented" about this processor.
Once we know where execution starts, we should try to analyze the "initialization routine" of the processor's firmware, which initializes the uC, loads the vendor specific firmware (Radio, HBOOT) into memory and starts execution. This routine will load the firmware from persistent (Flash) into volatile (RAM) memory and it will probably "pull together" the RAM contents from different parts of the Flash. (Might it already set up some page tables for the MMU at this point?) This is probably why you don't see the "jump table" in the HBOOT image. It's probably not part of HBOOT at all, but from a section that just gets "loaded near HBOOT" into volatile memory during the controller's initialization. (Might it be part of the Radio?)
When we trace the code further through the "jump table" (I'd love to do this on the actual physical device so I really hope that the processor supports single-stepping), we'll hopefully find the actual physical address of the secu_flag. As soon as we have it, the most obvious thing to do is just flick it via JTAG and check whether the device is S-OFF afterwards.
Finally, when we know where the secu_flag resides on the WFS (which means we know its physical address), we can try to find a way to access it from within Android. There's almost certainly some more protection in place, possibly protection via MMU, so we might have to modify Android to set up different page tables during boot process, but once we got that far, this should not be what stops us.
If you have any questions/suggestions, just feel free to ask/propose them.
At least the...
Code:
fastboot -c "mtdparts=msm_nand:0x..." boot recovery.img
... works and it does not require S-OFF! However, the ...
Code:
fastboot oem listpartition
... fails ...
Code:
... INFO[ERR] Command error !!! OKAY [ 0.000s] finished. total time: 0.000s
So yes, we can change the mapping of memory to mtd devices, but we cannot find out how the partitions are laid out on the device (at least not via fastboot, can't we ask the operating system somehow?).
...
Now stop a moment and take a deep breath!
...
Wait! What have we just found out? We can load an arbitrary OS image (kernel + initrd) via fastboot into the device's RAM and execute it! This sounds like the key to total awesomeness, doesn't it? Can't we build an OS image that has just one purpose which is S-OFFing the device (either by asking the Radio to do it, remember it is OUR custom kernel we're executing here so WE can talk to the Radio, or by mapping the memory the way we need it, then doing it directly)?
This may turn out to be easier than we expected it to be. Any kernel hackers here that could aid us in building a kernel that maps the entire memory of the device (this will include the Radio where secu_flag resides) and sticking an initrd to it that does the S-OFF? Of course we'll still need to find the flag in memory, but at least we now have a concrete plan how we can map the memory in. This will also enable us to build a very "user friendly" utility for S-OFF. No more zergRush, no more privilege escalation. The S-OFF utility is a self-contained OS image. You boot it, it does all the work and reboots the phone when done. How cool is that?
Click to expand...
Click to collapse
You probably still remember me for my famous "S-OFF without XTC-Clip conclusions" thread. We all know that now, HTC has given us the privilege of unlocking our Bootloaders using HTC-Dev. This allows us to Root and flash Custom ROMS, and all that; so we're all happy with that. But there are others out there, like me, who want to take even more advantage of this, and still get S-OFF, just like before. Now, we have a deeper understanding of our WFSs, so S-OFF is now much, much easier. If we get S-OFF, then we will have many more privileges on our phones.
With S-OFF, we can get:
Our warranties back
The ability to resize our system partitions.
The ability to flash different HBOOTs.
And many other things!
Be sure to visit *se-nsei.'s campaign, click here!
no.human.being posts his latest findings there.
My thoughts on this is:
from another thread, I've seen that when the HTC-Dev RUU was flashing HBOOT, it froze, but it still managed to flash rom_01.zip. This means, that when flashing HBOOT, the phone needs to be made S-OFF, then, when rom_02.zip is flashed, it finishes flashing HBOOT, and finally changes the security flag on, again.
So, I did some experimenting of my own. I flashed rom_01.zip using many methods, but all my attempts miserably fail. Why? Because the file is not signed properly. This got me thinking, if it's an HTC ROM, then why won't it flash?!?! Probably, because HTC made it in such a way, that the phone rejects it, or it won't work properly without the other files, that maybe reside in the RUU.
Maybe, someone can look into it, and find the function that S-OFFs the phone.
Perhaps, it might flash if it's on a Goldcard, so we'll have to do some more experimenting.
There is a possibility though, that using no.human.being's C code that he made earlier, we could S-OFF the phone, as it will be able to access more "sections" of the phone. We'll just have to compile/convert it and run/flash it.
Like before, if you have any suggestions, please tell me (by posting in this thread, please only PM if you think it's a very close solution, or if it's very important)
Good Luck everyone!
Isn't anyone going to post here!
no.human.being, eoghan2t7, are you there!?!
I think you might want to try extracting the img file and use fastboot flash radio radio.img.
yjwong said:
I think you might want to try extracting the img file and use fastboot flash radio radio.img.
Click to expand...
Click to collapse
Thanks, I have tried this though, but I didn't rename it to radio.img. Perhaps I'll ry this if I got some time (I'm still in High School, and they give me way to much homework. They are so annoying!)
Ideas! Anyone!
Is there a similar way to boot into ENG-HBOOT(unsecured)
like fastboot -c "mtdparts=msm_nand:0x..." boot unsecuredhboot.img ?
Then if unsecuredhboot.img wil be on sdcard we have possibility to flash s-offed hboot.
Somebody help this guy....... This is not my level. I'm a bit lower. I doubt it will work though.
Sent from my HTC Wildfire S A510e using XDA
slavislavi said:
Is there a similar way to boot into ENG-HBOOT(unsecured)
like fastboot -c "mtdparts=msm_nand:0x..." boot unsecuredhboot.img ?
Then if unsecuredhboot.img wil be on sdcard we have possibility to flash s-offed hboot.
Click to expand...
Click to collapse
No, that won't work. The "boot" command takes an Android image, which consists of a kernel, an initrd and a special header. The header tells the bootloader of the phone where to load the kernel in memory, etc. It won't be present in an ENG-HBOOT image, so the phone's bootloader won't be able to boot it.
Furthermore, HBOOT expects the controller to be "uninitialized" and will then initialize it. When the kernel is executed via Fastboot, the controller has already been initialized by HBOOT, after all that's the actual purpose of a bootloader. The ENG-HBOOT probably won't behave correctly if it finds the controller already initialized by a "lower level" bootloader.
Last but not least, the "mtdparts=..." is a kernel parameter. Basically it's just a string (character sequence) that is passed to the kernel. What the kernel does with it is principally the kernel's thing. It's just that "mtdparts=..." can be used on an embedded Linux kernel to change the partition mapping. I doubt that HBOOT can take parameters, since it's not designed to be loaded by anything else (apart from possibly an extremely low-level processor-specific firmware that most likely won't have a facility for passing parameters).
MANIFEST:
Hi again dear magldr users. We have a superb multi os bootloader, magldr and its OS flashers, DAF and DWI since 2011. They are important tools for our Leos, as you already know. But espacially DAF has limitations about flashing size. For example; if you use tmous hd2 with 1024mb nand memory, you cant create 600 MB system partition. If you use eu (wwe) with 512mb nand memory, you cant access full of your nand memory and you can only use its 400mb.
So I tried to remove this limitations and I success. As I writed detailed before, I understood magldrs mtty partition structure and said "I will write an android flasher with this info" on that thread. The day came You can see this: http://androidforum.tytung.com/understanding-amagldr-s-partition-structure-via-mtty-t56.html
I used batch, vbs, mortscript scripts and created a tool which communicates with magldr via mtty bridge and can partition nand memory without any limitation.
Click to expand...
Click to collapse
FEATURES:
- You can use your full nand on eu (up to 444mb) and tmous (up to 956mb) with use last 24 mb feature(1mb reserved for misc partition)
- You can create system partitions on eu up to 420mb (for dataonext method) and tmous up to 850mb.
- It calculates data partition size automatically. So you only enter recovery, boot, system and cache size. Tool will show you remained free storage every step.
- You can skip partitions. For example, you can remove cache partition and can create only system,data,boot partitions. If you skip all partitions, it adds all size data partition. (WTF, What should I do rather)
- Its partition table like this; misc, recovery, boot, system, cache, data. And this tool doesnt erase your nand memory. So for example you can resize system partition without losing misc, recovery and boot partitions. (You should wipe system, cache and data partitions and restore them from backup)
- Finally this tool totally opened, you can open it with winrar and modify.
Click to expand...
Click to collapse
TEST STAGE:
I tested it for 18 hour with nearly 100 repartition process on my EU HD2. It didnt make badblocks etc...
Click to expand...
Click to collapse
HOW TO USE:
- Well. You should have "mtty-specific wince drivers" This is hardest stage of this. Please look this thread for it: http://forum.xda-developers.com/showpost.php?p=5456461&postcount=2
- I recommend to use aMagldr 1.13.07 above. Older versions will cause problems. Please look this thread for getting lastest aMagldr: http://androidforum.tytung.com/amagldr-v1-13-07-t183.html
- Run tool and select your Leo model from menu.
- Enter your sizes for each partitions and press Ok button. You can skip partitions with Cancel button.
- After these it will prompt for connecting phone to PC.
- Run aMagldr and select USB Mtty option.
- Connect phone to PC.
- Press Continue button ready and wait. Tool does all things automatically.
- If mtty app stops with error, please try again. It isnt caused by my tool and it wont hurt anything.
Click to expand...
Click to collapse
HOW TO INSTALL ANDROID OR RESTORE BACKUPS
aMagldr's mtty utility hasnt any command to write any type data on nand. So you should use a "SD Recovery" for flashing a nand recovery on nand partition, installing rom and wiping partitions. I recommend to use kokotas extwrp sd version to flash recovery and/or rom and wipe partitions. You can install sd and nand version of this recovery from: http://androidforum.tytung.com/extended-twrp-2-6-0-0-touch-recovery-for-the-hd2-leo-t42.html
-Copy sd recovery's initrd.gz and zimage files to your memory cards root directory.
-Run amagldr and select Boot AD SD option to run recovery
- If it gives "SD kernel open failed" error;
* You should move this 2 files on sdcard/twrp folder (if twrp folder not there, create it manually)
* Run amagldr and select SD directory from Services>Bootsettings>AD SD dir option firstly. (Select twrp from here)
* After that, select Boot AD SD from amagldr's main menu.
Click to expand...
Click to collapse
CHANGELOG:
v1.20
- improved general speed and stability
- added checking phone connection feature
- attempting to fix mtty startup problem
- added use last Partition Table feature
- fixed invalid commands actions
- changed color scheme
- codes cleaned
v1.11
- fixed remained size calculation
- fixed some strings
- fixed userdata flag
v1.10
- added use and dont use last 24mb option
- added changelog menu
- fixed some strings
v1.00
- Initial release
Click to expand...
Click to collapse
SCREENSHOTS:
http://n1311.hizliresim.com/1h/t/uvrl6.png
http://k1311.hizliresim.com/1h/p/urq7u.jpg
http://t1311.hizliresim.com/1h/p/urq87.jpg
Click to expand...
Click to collapse
WHAT WILL BE NEXT VERSIONS?:
Who knows?
Click to expand...
Click to collapse
DOWNLOAD LINK: http://androidforum.tytung.com/amagldr-partiton-wizard-v1-0-t185.html
symbuzzer said:
DOWNLOAD LINK: http://androidforum.tytung.com/amagldr-partiton-wizard-v1-0-t185.html
Click to expand...
Click to collapse
1 st. thanks super work.
2nd thanks
thanks. this is revolution.
thank you very much, super convenient !
Tool updated to v1.10. Changelog and download link on first post.
Tool updated to 1.11. Please look first post for changelog and download links.
Hi symbuzzer,
I just wanted to wake up my good old HD2 with a new ROM. But to install Slimrom I needed a larger Nand Partition. At the moment i have just 120 MB and that is too small.
I tried to use your wizard but I always get a problem with the mtty connection to my PC. The phone seems to freeze and nothing happens. After a while the tool shuts down without doing anything.
Do you have an idea of a solution? I would be very happy to reactivate that good old piece.
Thanks
Frank
frankhell said:
Hi symbuzzer,
I just wanted to wake up my good old HD2 with a new ROM. But to install Slimrom I needed a larger Nand Partition. At the moment i have just 120 MB and that is too small.
I tried to use your wizard but I always get a problem with the mtty connection to my PC. The phone seems to freeze and nothing happens. After a while the tool shuts down without doing anything.
Do you have an idea of a solution? I would be very happy to reactivate that good old piece.
Thanks
Frank
Click to expand...
Click to collapse
Hi, probably you didnt install correctly mtty specific wince drivers. Please look 1st post again for right drivers.
symbuzzer said:
Hi, probably you didnt install correctly mtty specific wince drivers. Please look 1st post again for right drivers.
Click to expand...
Click to collapse
Thanks for your help. I cant get it to work.
I took the good old HD2 Toolkit and it worked fine.
Tool updated to v1.20. Changelog and download link in first post. Probably this is final version.