The following is what I did to make this ROM flash by romupdate:
I'm at the moment still searching for the right hex address but when I replace the whole header of NBH file then I can flash it.
The only think is that the size of the storage in OS is then small.
Think with me to solve this issue.
I'm not familiar with hexediting file (i can do only if someone tell me how), but i need find way for flash rom < 50 Mb.
I'll try to ask in my gang
Can you tell me exactly what byte you changed and with which byte?
So this actually causes the size of the Storage to shrink? You no longer get the 60mb free that you did from doing it through the sd card?
Yes this is the problem.
The hex address that I change is 0x163 in NBH file.
At the moment our goal is to find a way around this storage limitation.
ivanmmj said:
So this actually causes the size of the Storage to shrink? You no longer get the 60mb free that you did from doing it through the sd card?
Click to expand...
Click to collapse
We could try tom's methode (change pagepool by activesync) but WM6.1 is not realy the OS to do that.
What I mean is:
1. Change the hex value in NBH.
2. Flash it.
3. Use tom's method but change the hex value of 0x163 address
But the issue is WM6.1
NikMel said:
We could try tom's methode (change pagepool by activesync) but WM6.1 is not realy the OS to do that.
What I mean is:
1. Change the hex value in NBH.
2. Flash it.
3. Use tom's method but change the hex value of 0x163 address
But the issue is WM6.1
Click to expand...
Click to collapse
The Pagepool would only touch the Program Memory, not the storage memory.
We have to bypass the flasher's size requirement check.
What I mean by tom's method is that we change the hex value in NBH file then flash it. After that try to change the hex value using tom's method.
tom changes pagepool by activesync and we can change the size of storage by activesync.
NikMel said:
What I mean by tom's method is that we change the hex value in NBH file then flash it. After that try to change the hex value using tom's method.
tom changes pagepool by activesync and we can change the size of storage by activesync.
Click to expand...
Click to collapse
hmm... interesting theory... Sounds promising!
EDIT: Just thought of something. Once it gets flash into the device it's no longer an NBH... it's more like a os.nb then... the hex value wouldn't exit there, then, would it?
We need to dump a ROM that's has not been modified and one that has and look at not only the os.nb but ALL of the files that the phone dumps. If you can flash by sd, you can do that. If not, then we'll have to install a ROM that's just big enough to pass the limit and one that's much bigger.
Actually increased storage isn't everything (though nice).. The less amount of files in the OS image the faster the ROM works. There is lot's of files in ROMs most people don't use. Even things like simply html based help files etc.. If this limit can be breached ROMs can be faster or filled with more stuff without comprimizing storage size.
I myself want to replace my Artemis this year and am tempted for the Kaiser, if only those videodrivers get fixed. Till then there is no capable replacement..
sparcle said:
Actually increased storage isn't everything (though nice).. The less amount of files in the OS image the faster the ROM works. There is lot's of files in ROMs most people don't use. Even things like simply html based help files etc.. If this limit can be breached ROMs can be faster or filled with more stuff without comprimizing storage size.
I myself want to replace my Artemis this year and am tempted for the Kaiser, if only those videodrivers get fixed. Till then there is no capable replacement..
Click to expand...
Click to collapse
I know. That's why I make small clean ROMs only, but I figured that I might as well find a way around the limit since I loose so much empty space in my ROMs.
We have to figure out a way get the RUUupdateUtil to ignore that address... What was it originally and what did you change it to?
Storage Memory Reduced
Hi... I don´t know if this is the correct place to ask next question but I haven't found where to put it, so, I hope you can help me with this matter:
I have a Gigabyte GSmart i350 (256MB rom, 64MB ram, wm6) and storage capacity showed only 142.24MB, do you know if it is normal to be reduced that capacity?... I know 256MB on real store is 244MB, but it seems to be extremely reduced ... by the way, on a different topic, how could I start a Thread on this forum?... Thanks in advance...
Xilsoh said:
Hi... I don´t know if this is the correct place to ask next question but I haven't found where to put it, so, I hope you can help me with this matter:
I have a Gigabyte GSmart i350 (256MB rom, 64MB ram, wm6) and storage capacity showed only 142.24MB, do you know if it is normal to be reduced that capacity?... I know 256MB on real store is 244MB, but it seems to be extremely reduced ... by the way, on a different topic, how could I start a Thread on this forum?... Thanks in advance...
Click to expand...
Click to collapse
That's not an Artemis, in fact I don't even know if it's an HTC phone. But as far as space goes, out of that 244mb, you have all the stuff that the manufacturer puts in there and then there's the OS and other stuff stored in it. Most phones have a shared memory for all storage, both your storage and system files. That DOES seem kind of low, though. You'll have to find a forum dedicated to that particular phone, though. Do you know who manufactures it? (Or does Gigabyte itself make it?)
NikMel said:
...
What I mean is:
1. Change the hex value in NBH.
2. Flash it.
3. Use tom's method but change the hex value of 0x163 address
...
Click to expand...
Click to collapse
It's a good idea, but with a problem...
tom's method rewrite an address in flash, this address is the same in OS.nb, so we can change pagepool size or in os.nb or on-the-fly with tom's method...
changes in nbh files have different results, becouse nbh is a compressed file that could include too much info that are written in flash... In this case, the address 0x163 is only for ruu, but not really written directly in flash...
we must know where is storage this value in flash!!!
cesconoa said:
It's a good idea, but with a problem...
tom's method rewrite an address in flash, this address is the same in OS.nb, so we can change pagepool size or in os.nb or on-the-fly with tom's method...
changes in nbh files have different results, becouse nbh is a compressed file that could include too much info that are written in flash... In this case, the address 0x163 is only for ruu, but not really written directly in flash...
we must know where is storage this value in flash!!!
Click to expand...
Click to collapse
In fact, i've tried another thing:
creating an nbh file with only os, at address 0x162-0x163 correspond values D4 02
creating an nbh file with radio, splash and os, the values D4 02 don't correspond to address 0x162-0x163 but they are in address 0x16A-0x16B
It means this part of nbh informs ruu.exe what (and where) is included in the file, but how ruu.exe processes this info is not clear...
cesconoa said:
In fact, i've tried another thing:
creating an nbh file with only os, at address 0x162-0x163 correspond values D4 02
creating an nbh file with radio, splash and os, the values D4 02 don't correspond to address 0x162-0x163 but they are in address 0x16A-0x16B
It means this part of nbh informs ruu.exe what (and where) is included in the file, but how ruu.exe processes this info is not clear...
Click to expand...
Click to collapse
We have to modify how the RUUUpdateUtility acts after checking that memory address. I've been trying to track the file through a debugger but thus far have had no luck.
Waiting RUU solution, i flashed using Cesconoa method HERE, that solved problem for SD flashing not running with slow SD.
Not the best i could obtain, but it's good result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Without AS and My Mobilier (for shoot) Program memory is 28 Mb
I think easy obtain 70 Mb for storage (i don't cleaned very well)
bigix1,
WM5torage has no effect on flashing by SDcard.
This software changes application layer settings. SDcard flashing is a lower level access then wm5torage.
bigix1 said:
Waiting RUU solution, i flashed using Cesconoa method HERE, that solved problem for SD flashing not running with slow SD.
Not the best i could obtain, but it's good result.
Without AS and My Mobilier (for shoot) Program memory is 28 Mb
I think easy obtain 70 Mb for storage (i don't cleaned very well)
Click to expand...
Click to collapse
I try to be more clear:
with most popular SD card we are not able to flash from SD: they are too great and for this slow to go on (probabily need more energy).
WM5Torage is used to create partition on SD from PC.
With a little partition (i used 1 Gb Sd for make 2 partition 100/900 mb) we are able to flash from SD. With single partition 1 Gb i'm not able to do it.
I have a 2GB sdcard High speed (not a SDHC) 2gb partition and it works.
bigix1 said:
I try to be more clear:
with most popular SD card we are not able to flash from SD: they are too great and for this slow to go on (probabily need more energy).
WM5Torage is used to create partition on SD from PC.
With a little partition (i used 1 Gb Sd for make 2 partition 100/900 mb) we are able to flash from SD. With single partition 1 Gb i'm not able to do it.
Click to expand...
Click to collapse
Related
Edit: New version available! Compatible with Kaiser, Titan, Artemis, Hermes etc.
New version 2.1rc2! This is a major upgrade to version 2.0 (and a bugfix to 2.1rc1). The ImgfsTools now support generating ROMs for Kaiser, Hermes, Titan, Artemis and probably quite some more. All Hermes-specific code was replaced with code working for all devices
The new version is attached to this post.
These are the screenshots of the original version. Have a look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a completely unmodified LVSW edition WM6. It usually has 47 MByte Storage....
What happened? Well, the IMGFS partition (a.k.a. OS.nb) has 8 MByte free space. Until now it was not possible to shrink the IMGFS partiton and enlarge Storage in return, so that space was wasted.
This has changed - now also on the Kaiser!
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size. The result is what you see above.
This is an excerpt from the ReadMe file from the new version 2.1rc2:
ImgFS Tools Version 2
================================================================
(Current version: 2.1rc2)
What it is
==========
These little programs help you with cooking your own ROM. They allow you to unpack an OS.nb file into individual files as you'd find them on your device, and to re-pack them into a new OS.nb which you can flash to your device. Of course, betweem unpacking and re-packing, you'll want to add/modify/remove some of them.
The tools are enhanced versions of mamaich's imgfs_tools - a huge Thank You goes to mamaich for creating them, and also for releasing the source code!
The most significant enhancement is that the IMGFS inside the generated OS.nb is no longer of fixed size, but is as small as possible. This means: the more of the unpacked files you remove before re-packing, the smaller it'll get and consequently the bigger your Storage memory will become. Also, the tools are no longer device-specific and should also work other devices than the Hermes.
*** WARNING: ***
Before you flash a ROM created with these tools, make sure you know how to recover from a non-booting ROM! For Hermes and Kaiser, you should install a HardSPL before you use these tools! I accept no responsibility for bricked devices!
Supported devices
=================
These tools have been tested on HTC devices only, and are known to work on Hermes, Kaiser, Titan and Artemis. Other devices were not tested and may or may not work.
If you want to try, I will gladly support you. However, I cannot accept responsibility for bricked devices!
How it works
============
On a high level, this is the chain of actions needed to unpack OS.nb:
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->
--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory
At that stage, you will want to edit the 'dump' directory. I recommend using bepe's excellent *Package Tool for this.
The reverse process is:
'dump' directory ---(ImgfsFromDump)---> imgfs-new.bin ---(ImgfsToNb)--->
OS-new.nb.payload ---(NBMerge)---> OS-new.nb ---(*NBHGen)--->
RUU-signed-new.nbh
(The tools marked with '*' are not part of the ImgfsTools, but are also available for free from xda-developers.com. There is also one additional tool, NBInfo, in this package.)
Version History
===============
2007-10-17 2.1rc2
ROMs generated by 2.1RC1 would not boot if created with a certain combination of parameters. Fixed.
2007-10-14 2.1RC1
Major overhaul:
- All Hermes-specific assumptions (like the sector size being always 0x200) are now gone.
- "conservative" mode added to ImgfsToNb and NBMerge
- on devices that have only two MSFLSH flash regions, ImgfsToNb overwrote a few bytes in the XIP section, causing unpredictable results. This was fixed.
- Removed "-emu" support from NBSplit and NBMerge, as this didn't work with WM6 emulator images.
2007-03-18 2.0 RC 2
All tools now linked statically to the MS runtime library, no longer needs DLL. No other changes.
2007-03-18 2.0 RC 1
Initial Release. Starting with version 2 to not collide with mamaich's version numbers.
===================
Enjoy!
Cheers
tadzio
Great job tadzio,
Looking forward to this new tool.
tadzio said:
Have a look:
This is a completely unmodified LVSW edition WM6. It usually has 47 MByte Storage....
What happened? Well, the IMGFS partition (a.k.a. OS.nb) has 8 MByte free space. Until now it was not possible to shrink the IMGFS partiton and enlarge Storage in return, so that space was wasted.
This has just changed!
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size. The result is what you see above.
This currently runs on my TyTN with boot loader 1.10 OliPro. I haven't had a chance to test it with other configurations, but I see no reason why it shouldn't work.
I do not plan to offer any cooked ROMs myself, as there are many excellent chefs in this forum already. But I would think a new approach to ROM cooking may emerge: make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage (bepe's excellent Package Tool makes this very simple!). This will give maximum flexibility without wasting any memory.
Give me one more day to write up the documentation, and then I'll upload the new Imgs Tools version.
Cheers
Daniel
Click to expand...
Click to collapse
sounds great man,
once your instructions are posted I will use this technique for Black version 1.2.
Well Done,
Cheers,
Well done man
Waiting for your great work....
tadzio said:
Have a look:
This is a completely unmodified LVSW edition WM6. It usually has 47 MByte Storage....
What happened? Well, the IMGFS partition (a.k.a. OS.nb) has 8 MByte free space. Until now it was not possible to shrink the IMGFS partiton and enlarge Storage in return, so that space was wasted.
This has just changed!
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size. The result is what you see above.
This currently runs on my TyTN with boot loader 1.10 OliPro. I haven't had a chance to test it with other configurations, but I see no reason why it shouldn't work.
I do not plan to offer any cooked ROMs myself, as there are many excellent chefs in this forum already. But I would think a new approach to ROM cooking may emerge: make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage (bepe's excellent Package Tool makes this very simple!). This will give maximum flexibility without wasting any memory.
Give me one more day to write up the documentation, and then I'll upload the new Imgs Tools version.
Cheers
Daniel
Click to expand...
Click to collapse
Brilliant! Truly BRILLIANT!
good job!!!!
That would be great findings for upcoming roms. For curiosity sake, are there any initials for increasing phone storage from extended rom. Cheers.
That's just great... We're all going to run for the smallest ROM possible ! Even maybe strip out Windows Media Player (We all use other players...) and some of the useless aplications (Who uses Solitaire or Bubble Breaker ?)
who uses Solitaire or Bubble Breaker
Hey. Don't knock it till you've tried it!
But I still wouldn't mind if it was in a .cab
Good job buddy... Looking for your good news.
I just added ImgfsTools2.zip to the first post of this thread.
Disclaimer: I only tested this with my Hermes. Please be careful if you use it with other devices. Oh, and it can't hurt to be careful even with a Hermes!
Feedback welcome! If you run into any problems with these tools, please post in this thread!
Enjoy!
Daniel
Am I right that embedding things into the ROM makes them run slightly faster? Some things that everyone will use would be better off kept into the ROM in that case, which would bring in the disagreement of what everyone thinks should be included. It would be very intresting to see if someone can build a completely pure OS though.
Percz said:
Am I right that embedding things into the ROM makes them run slightly faster?
Click to expand...
Click to collapse
Glad you asked.
If by "things" you mean applications, the opposite is true.
As code cannot be executed directly from NAND flash, everything has to be copied to RAM before execution (the term XIP - eXecute In Place - is misleading here. There is no true XIP in a Hermes). Some executables and DLLs are stored as "modules" in ROM, i.e. already prepared to be copied "as is" to RAM. Moving these from ROM modules to normal files in Storage will indeed make them load slower, although once loaded execution will be the same speed.
However, applications are not stored as modules. Even in ROM they are normal files, and speed-wise it makes absolutely no difference if they are loaded from ROM or Storage into RAM.
But there is one more important aspect: the size of the Windows directory. Even Microsoft admits that having 1800 files in one directory slows the device down significantly. And unfortunately, all files in IMGFS are in the Windows directory (with initflashfiles.dat, you can only copy them elsewhere, not move them).
So, if we manage to remove as many files and apps as possible from the ROM (and hence the Windows directory), and package them into .cabs in a way that they get installed into directories other than Windows, I would think we would see some increase in speed, since accessing the Windows directory would be quite a bit faster - and I guess the OS accesses that directory rather often.
At the moment, this is only theory. I haven't tried to prove it yet.
Cheers
Daniel
Great work, i'm looking forward to new roms being cooked with more storage.
sounds like this is what the chefs need
kjs30 said:
Great work, i'm looking forward to new roms being cooked with more storage.
sounds like this is what the chefs need
Click to expand...
Click to collapse
this chef has strapped this carving knife to his waist.
Alcibiade said:
That's just great... We're all going to run for the smallest ROM possible ! Even maybe strip out Windows Media Player (We all use other players...) and some of the useless aplications (Who uses Solitaire or Bubble Breaker ?)
Click to expand...
Click to collapse
Leave few things in there. whats the point of having all that memory with nothing in it. I love bubble breaker.
Also as mentioned it would be great if we can merge ExtRom into main memory.
Nice work!
I'm happy your modified OS.nb boots for everyone
piopawlu said:
I'm happy your modified OS.nb boots for everyone
Click to expand...
Click to collapse
And thanks again for pointing me to the right place (the partition table). Without your help it'd probably have taken me a lot longer!
Cheers
Daniel
rv1nd said:
Leave few things in there. whats the point of having all that memory with nothing in it. I love bubble breaker.
Click to expand...
Click to collapse
The point is that you can decide what you want to put in there without having to cook your own ROM.
Also as mentioned it would be great if we can merge ExtRom into main memory.
Nice work!
Click to expand...
Click to collapse
I'm thinking about that. Should be do-able.
Cheers
Daniel
*********************************
Jerome! has released a beta rom - see below for details - please help to test
*********************************
I noticed that a P750 Kitchen was released at asusmobile.ru, problem is that it is Russian base.
Using the following steps I was able to compile a rom that worked, abliet one I could not understand
1) grab your preferred kitchen from http://asusmobile.ru/board/viewtopic.php?t=14829 ( I used Manila Version)
2) extract
3) Copy your OEM files to the OEM folder
4) Run Build_ROM.cmd from root
5) When BuildOS comes up select your packages, press play, close when done
6) When prompted to select "B" or "X" to backup or delete dump folder
7) When NB0 Kitchen starts enter password: mrtoto
8) Load ROM and select PegasusP.nb0
9) Fill in and Select ROM version ,ROM date , CPU speed or pagepool size you want and click [Pack Image].
10) Select [XPR Compression] or [LZX Compression] and click [Build NB0]
11) Wait until you see the words "ROM.NB0 complete" in the message box, Exit the nb0 Kitchen and wait until you see its done
12) Open PegasusP.nb0 in a hex editor and change the bytes at offset 00001c5c from 00 10 85 05 to 20 00 00 0a, save.
13) Extract the attached ASUS_P525_NB0_Kitchen ENG.rar, open ASUS_P525_NB0_Kitchen.exe, load your nb0 and choose fix crc.
Flash by copying to root of SD card, hold power up, voice record in, joystick down while pressing reset and the bootloader will initiate a flash.
Next step is to convert to english, I have seen a tut at http://forum.xda-developers.com/showthread.php?t=312704 on how to translate, just wondering if there is an easier way that someone here may know of as with my limited knowledge I am likely to have missed something.
I tried dumping a rom from the guys at pdamobiz.com to use as base but packagetool would not work (no RGU?)
So anyway that is where I am at, if anyone wants to help that would be great as I reckon there is a few people out there that could do with an English P750 kitchen - I intend on getting this working at some point although time is limited.
HAt's off to the tool creators and contributors here at xda-devs, pdamobiz.com (feel like releasing a kitchen Undetect?) and asusmobile.ru.
Oh yeah if you decide to do anything I said and break stuff then don't cry to me, I have had a few bad flash's but each has recovered, YMMV.
dmozk said:
I notoced that a P750 Kitchen was released at asusmobile.ru, problem is that it is Russian base.
Using the following steps I was able to compile a rom that worked, abliet one I could not understand
1) grab your preferred kitchen from http://asusmobile.ru/board/viewtopic.php?t=14829 ( I used Manila Version)
2) extract
3) Copy your OEM files to the OEM folder
4) Run Build_ROM.cmd from root
5) When BuildOS comes up select your packages, press play, close wheen done
6) When prompted to select "B" or "X" to backup or delete dump folder
7) When NB0 Kitchen starts enter password: mrtoto
8) Load ROM and select PegasusP.nb0
9) Fill in and Select ROM version ,ROM date , CPU speed or pagepool size you want and click [Pack Image].
10) Select [XPR Compression] or [LZX Compression] and click [Build NB0]
11) Wait until you see the words "ROM.NB0 complete" in the message box, Exit the nb0 Kitchen and wait until you see its done
12) Open PegasusP.nb0 in a hex editor and change the bytes at offset 00001c5c from 00 10 85 05 to 20 00 00 0a, save.
13) Extract the attached ASUS_P525_NB0_Kitchen ENG.rar, open ASUS_P525_NB0_Kitchen.exe, load your nb0 and choose fix crc.
Flash by copying to root of SD card, hold power up, voice record in, joystick down while pressing reset and the bootloader will initiate a flash.
Next step is to convert to english, I have seen a tut at http://forum.xda-developers.com/showthread.php?t=312704 on how to translate, just wondering if there is an easier way that someone here may know of as with my limited knowledge I am likely to have missed something.
I tried dumping a rom from the guys at pdamobiz.com to use as base but packagetool would not work (no RGU?)
So anyway that is where I am at, if anyone wants to help that would be great as I reckon there is a few people out there that could do with an English P750 kitchen - I intend on getting this working at some point although time is limited.
HAt's off to the tool creators and contributors here at xda-devs, pdamobiz.com (feel like releasing a kitchen Undetect?) and asusmobile.ru.
Oh yeah if you decide to do anything I said and break stuff then don't cry to me, I have had a few bad flash's but each has recovered, YMMV.
Click to expand...
Click to collapse
Just want to let you know I'm working on it, expect some beta ROM's here soon So watch this space!
Hi, i wonder... will this work on O2 Xda Zset , it is made by Asus.
Cheers.
Nice one, I have not had a chance to do anything further. Look forward to seeing your work.
great
Hi is great was looking for one
First screenshots of BETA 0.1
Hi there,
I'm proud to present you the following progress status update:
VGA Windows Mobile 6.1 WWE SYS 21109 / XIP 20933 booting
GSM/3G/WIFI working
99% Interface is in English
20 MB of free RAM after boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All credits to
Barin for the original kitchen (Asusmobile.ru )
Sorg for the VGA modification
Calkulin SYS from Diamond
MRtoto/VIVI for the P525 kitchen
More to come soon!
Looks great I have a P750, and i'm looking for a good rom -- can't wait to see what you come up with
Just wondering -- are you planning on implementing Asus`Multihome too?
(http://forum.xda-developers.com/showthread.php?t=481616)
Also since its VGA will you be porting the P522w software over? (Camera, UrTime, etc.??) Just wondering cause Sorg's original one has replacement problems but they weren't as clean as the original
pear-i said:
Looks great I have a P750, and i'm looking for a good rom -- can't wait to see what you come up with
Just wondering -- are you planning on implementing Asus`Multihome too?
(http://forum.xda-developers.com/showthread.php?t=481616)
Also since its VGA will you be porting the P522w software over? (Camera, UrTime, etc.??) Just wondering cause Sorg's original one has replacement problems but they weren't as clean as the original
Click to expand...
Click to collapse
My plan is to make a 'clean' rom soon. All the basics should be working. When this works I'll focus on porting some applications. Feedback and ideas of which it should contain besides the Camera, Urtime, Multihome, let me know.
Again good work, are you planning on releasing your kitchen when stable?
dmozk said:
Again good work, are you planning on releasing your kitchen when stable?
Click to expand...
Click to collapse
Yes, I will, when I finished translating the OEM files, they are still Russian now. Just to make clear, it's not my kitchen, I'm modifying the work of Barin, Vivi etc etc.
Time for a bèta release - testers wanted
To digg out all the bugs I've created a beta release. I will need your help in testing and reporting bugs. Please reply in this thread when you find something odd:
Please note this is a beta release. Not intended for every day use, however, I have been running this build for a week now and it's working well for myself. There might be things that I've broken though.
Also, since this is a bèta release, I will not be held responsible for any problems on your device. Flash at own risk.
How to upgrade:
- Place the PegasusP.nb0 file on a non-sdhc storage card (128 megs or more)
- Plug in power
- Press and hold the following keys when softresetting:
Voice record - Joystick down - Slider button up (e.g. power on button)
Wait until device restarts. Do not interrupt!
File contents:
Asus P750 Rom WWE 6.1 VGA Build 5.2.20933
Download here:
http://www.megaupload.com/?d=EJ0LA3WZ
Used sources (credits to)
Barin's asusmobile.ru kitchen
Mrtoto NB0 Kitchen
BengBeng asuspda.net XIP 20933
Sorg VGA Drivers
Vivi and all the others involved in the P525/p750 stuff
Calkulin's Diamond SYS 20931
Please report any issues you encounter! Except for:
Known issues:
- When clicking on softkey to open a menu e.g. contactsmenu, the size is bigger than normal.
- Core systems settings as Power, Device info, Brightness still in Russian.
- Some ASUS apps still in Russian like Asus switcher, CPU mode, Asus profiles, Wakeupsource
- Sometimes after first boot "unknown usb driver" message appears. Reflash the rom to resolve.
Nice one - testing now.
Jerome - any chance of uploading elsewhere, can't seem to grab anything from megaupload today for some reason..
dmozk said:
Jerome - any chance of uploading elsewhere, can't seem to grab anything from megaupload today for some reason..
Click to expand...
Click to collapse
Here's your RS link:
http://rapidshare.com/files/201120253/PegasusP.nb0
MicMeo said:
Here's your RS link:
http://rapidshare.com/files/201120253/PegasusP.nb0
Click to expand...
Click to collapse
Thankyou kind sir.
Got it flashed, on boot stuck in endless align screen page loop - soft/hard reset no good. Have reverted to previous rom, for what its worth my bootloader reads as below:
2007/12/05 20:06:37
IPL: iplPegP_4H3
dmozk said:
Got it flashed, on boot stuck in endless align screen page loop - soft/hard reset no good. Have reverted to previous rom, for what its worth my bootloader reads as below:
2007/12/05 20:06:37
IPL: iplPegP_4H3
Click to expand...
Click to collapse
Anyone else experienced the same? I've flashed mine more than 50 times and never had this kind of error. There is a lang unlock tool available. Perhaps it has got to do with that?
I've upgraded from an Extreme Ultralite Rom VGA WWE 3.1.0.7. Perhaps you can flash this one too and check if the same error occurs?
The bootloader of my device is exactly the same. This is a radio/bootloader/gps/free ROM update, just the OS.
thanks for the same
it seems great till now
well i just wanted to ask you is there anyway we can have a manila version in vga p750.
just asking .
cause it take a lot of memory installing it with cab.
if it can be done on the Rom itself it will be great.
prioin said:
thanks for the same
it seems great till now
well i just wanted to ask you is there anyway we can have a manila version in vga p750.
just asking .
cause it take a lot of memory installing it with cab.
if it can be done on the Rom itself it will be great.
Click to expand...
Click to collapse
Doing some testing on OEM packages for the Diamond in the P750 kitchen now...
Jerome! said:
Doing some testing on OEM packages for the Diamond in the P750 kitchen now...
Click to expand...
Click to collapse
hi ,
that will be just brilliant,
Keep up the good work
looking forward for the same
see if i am of any help.
Regards
Prio
I'm no longer updating this! All of the new changes have been pushed to the atools version. L1q1d is going to be taking over from here on out so check out his thread HERE.
Here's an editor to select which settings you want for your nbh!
All this does is hex edit different things, including the cmdline info, like you could do with a hex editor. It's just a lot more user friendly.
Disclaimer:
I'm not responsible for ANYTHING that happens to you, your phone, or your computer. I would not release something that intentionally harms a computer or phone, but there's always that chance when using unofficial software.
______________________________________________________________________________________________________________________________________
What everything means:Device:
-Vogue: LINK
-Kaiser: LINK
-Polaris: LINK
Resolution:
-240x320: The native resolution on these devices. Will give the best overall picture quality.
-320x428: The smaller version of the 320x480 that fits our screens better.
-320x480: The native resolution for the G1 and most 1st gen Android devices. Things will fit better as they aren't scaled down, but everything will look blurry/squished.
Version:
-This is the Android version. Be careful not to get it mixed up with a user's release version. Most builds say either Donut, Eclair, or Froyo, but if not then you can install the system and look under Settings>About Phone and look under "Android Version"
-Donut: 1.6
-Eclair: 2.1
-Froyo: 2.2
Panel Type:
-Only Vogues have auto panel detection, so for Kaiser and Polaris users you will just have to pick one. If there's weird pixels, things don't look right, sleeping issues try a different panel.
Keyboard Types:
-Look HERE for more info if you don't know which keyboard type.
More Settings:
-ppp.nostart: If you set this to 1 it should prevent data from starting on boot. Helpful for some people but if you don't have to worry about data then leave it 0.
-CPU Overclock: This uses the same method that myn uses with Rogue Tools. Our CPU's are set to run at 400 MHz, but we can overclock them to over 500 MHz. I would suggest not going over 500 unless you know what you're doing, but some users have reported running at 550 just fine. It could decrease your device's life expectancy if using constantly, but probably won't notice for quite some time.
-System/Data Partitions: You can use this if running system or data off an EXT2 partition to use all of nand. Also helps when using an older Sense build that needed a larger system partition.
-Disable Vibrate on boot: Check THIS POST for more info on that.
-Battery Capacity: Self explanatory.
______________________________________________________________________________________________________________________________________
How to use the Editor:
WINDOWS, MAC, LINUX:
1. Download python (Version 2.7)
2. Download editor from below.
3. Download the nbh for your phone
a. from DZO's SITE
b. Download the latest one using the editor
4. Open the NBH from the editor
5. Change any settings
6. Save new NBH
7. Enjoy your new nbh
Don't want to install python?
1. Download Windows NBH Editor.zip from below
2. Extract to where you'd like
3. Run nbheditor.exe
Last but not least... Thanks! I've said it all before but this wouldn't be possible without the mighty one, DZO. Thanks to DZO, kallt_kaffe, myn and l1q1d for pointers, and all the other devs that are helping get these what should have been extinct devices back to life!
To Do:
Taking suggestions!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Windows NBH Editor.zip
UPDATES
DOWNLOAD!!!(Right Click>Save As...)
loserskater said:
(I spoke with kallt_kaffe and his will probably work soon.)
Click to expand...
Click to collapse
I've posted new a new version that should be compatible but when I change an NBH (Kaiser) to donut the hw3d.version becomes 01 and the "1" overwrites the space what should be after the "0". Setting an NBH to eclair seems to work though. Haven't tried the same with DZO's NBH though but the result should be the same.
kallt_kaffe said:
I've posted new a new version that should be compatible but when I change an NBH (Kaiser) to donut the hw3d.version becomes 01 and the "1" overwrites the space what should be after the "0". Setting an NBH to eclair seems to work though. Haven't tried the same with DZO's NBH though but the result should be the same.
Click to expand...
Click to collapse
Thank you! New zip should have it working now.
loserskater said:
Thank you! New zip should have it working now.
Click to expand...
Click to collapse
Confirmed, seems to work now.
OK, so how easy was THAT?.. Thanks!
New version posted. Now just one program.
You still need to select the NBH for your device.
Excellent work dude, truly the most useful pre-install software, makes setting up everything so easy, intuitive to use too.
Hi Loserskater,
Thanks for your very good job and to help us to use much better our phone with android
Cheers.
loserskater said:
The moment you've all been waiting for... ok, well maybe just a few of you. Here's an editor to select which settings you want for your nbh!
Click to expand...
Click to collapse
Can you also include battery setting (option: experimental) ?
robuser007 said:
Can you also include battery setting (option: experimental) ?
Click to expand...
Click to collapse
That's something DZO will have to do... unfortunately you can't add things to the cmdline of the nbh or else it wont work right. it will have to be added to the source. If I can convince dzo to add it, I will add the option to change that value for other batteries. For now, you can try kallt_kaffe's nbh.
His also work with this editor
loserskater said:
That's something DZO will have to do... unfortunately you can't add things to the cmdline of the nbh or else it wont work right. it will have to be added to the source. If I can convince dzo to add it, I will add the option to change that value for other batteries. For now, you can try kallt_kaffe's nbh.
His also work with this editor
Click to expand...
Click to collapse
Scratch that. New update now includes ability to add default settings (like in kallt_kaffe's) for battery, clock, and ppp.nostart. I just flashed successfully but I haven't had much time to test.
Can now use either kaiser nbh or the vogue nbh.
Hi guys,
Sorry... I might have miss it.
Can someone explain what is the panel different?
I am using HTC Kaiser.
Thanks
Daniel
Re: Loser's NBH Editor v3.0
It just depends what panel you have. The only way to tell is by trying each one. If you get weird pixels then thats the wrong one. I havent found any difference between panel 2 and 3 though...
Apparently there are some differences in the way panel 2 and 3 handle power on, power off, there have been a few reports of white streaks on waking up the lcd by some users on panel 3 using panel 2 settings.
This is not definitive though, since panel3 seems to be pretty rare.
You could set other default settings, like panel2 (most used I guess), I never tried another panel.And eclair for the other default setting (most used nowadays I guess).
Maybe you can add comments (like use 1.7x radio and hardspl 3.34 before flashing and use kernel from...) to make it completly idiot proof (and have less questions here on the forums).
Great work anyway.
Re: Loser's NBH Editor v3.0
You could set other default settings, like panel2 (most used I guess), I never tried another panel.And eclair for the other default setting (most used nowadays I guess).
Maybe you can add comments (like use 1.7x radio and hardspl 3.34 before flashing and use kernel from...) to make it completly idiot proof (and have less questions here on the forums).
Great work anyway.
Click to expand...
Click to collapse
That's a good idea. I'll change those settings to the commonly used ones and maybe save settings on exit so you don't have to do it each time. And add more info in the actual program. Thanks for the input!
Probably will try with Panel 2. I am using the SD boot with Eclair right now.
Re: Loser's NBH Editor v3.1
What would be some things that people would like to see added to this? I was thinking about making it possible to change cpu and gpu OC settings. And maybe battery settings. Can anybody think of any other cmdline settings?
I don't have any suggestions, just wanted to say thanks for the great app. Very convenient.
Hi,
I want to install Android on my HTC Touch Pro and I want to also do that Dual Boot program. Problem is that I can't get android to work.
I downloaded Android, and it is not installing well. After I boot, the top bar of the Android comes, but it seems all grainy, and my mobile restarts :/ I tried changing to a different RAPH startup.txt, but it just crashes in the middle -.-
Pics: (sorry, they are HUGE)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas anybody?!
Don't try changing to a different startup.txt! Make sure you're using the right file for your phone model. You could also try simply redownloading XDANDROID.
Which RAPH do you have?
Perhaps you need to read the FAQ.
Also, 1) don't take huge pics and post them to a thread - resize them and provide links if anything, although the pics seem useless TBH. 2) post in the build thread, don't create a new thread. Thanks.
@Ben_duder
I downloaded so many lol
@arrrgh
Thanks for that FAQ page, I know I have a RAPH100 now
1. Didn't notice how big they were until I posted them
2. Link to thread pls
Thanks for the help till now every1
EDIT: My download doesn't have RAPH100, but RAPH, RAPH500 and RAPH800 -.-
Is RAPH equivilant to RAPH100?
EDIT2: Ok, so i finally got a RAPH100 one, and it was installing. The last message was 'mp_dma : busy'
It kept on going after a bit, until screen calibration, i didn't even have the time to calibrate, as it kept on going.
Only to get 'stuck' on mp_dma : busy...again
Whilst writing this, it started again....only to get 'stuck'.....AGAIN...on mp_dma : busy....AGAIN!!
Is it normally like that? Does this site have live shat or smthn? Or can some1 PM their MSN/Skype so I can have 'live help' lol
Yes, it is "normal". What shouldn't be normal is the fact that you can't find the RAPH100 startup in the full bundle from THIS thread(for FroYo) or THIS thread (for Gingerbread). Keep in mind, FroYo is more complete and Gingerbread is still in alpha stages even though it seems more "stable" than FroYo.
Additionally, if you just want to be able to boot, the magic number we are looking for is 10 minutes. However, if you aren't getting to the XDAndroid boot animation, this might mean you aren't doing something right. Also, you'll need to grab the ts-calibration file for your device from either thread and put it in the same folder as haret
Hmm, I seem to have got it to work. It look me around 10 minutes to complete It seems ok (I downloaded the new XDAndroid from the official Wiki page). All works fine, incl. camera and Wi-Fi.
Now, I want to do the dual Boot thing. I have the exe downloaded, but now its a new set of CAB and EXT files. I'm going to opt for what seemes to be the newer version (v 1.0.6.0) but when i extract that and open a the file, I get 5 new files
Gen.Y DualBOOT QVGA v1.0.6.0 - Storage Card.cab
Gen.Y DualBOOT VGA v1.0.6.0 - Internal Storage.cab
Gen.Y DualBOOT VGA v1.0.6.0 - Storage Card.cab
Gen.Y DualBOOT WQVGA v1.0.6.0 - Storage Card.cab
Gen.Y DualBOOT WVGA v1.0.6.0 - Storage Card.cab
no idea what to do next.
If you have a RAPH100 use Gen.Y DualBOOT VGA v1.0.6.0 - Storage Card.cab. If you have a DIAM100 use Gen.Y DualBOOT VGA v1.0.6.0 - Internal Storage.cab
NOTE/hint
One installs to internal storage/soldered microSD and the other installs to the storage card/microSD
R^7Z said:
If you have a RAPH100 use Gen.Y DualBOOT VGA v1.0.6.0 - Storage Card.cab. If you have a DIAM100 use Gen.Y DualBOOT VGA v1.0.6.0 - Internal Storage.cab
NOTE/hint
One installs to internal storage/soldered microSD and the other installs to the storage card/microSD
Click to expand...
Click to collapse
Yeh i'll do that.
And I understood the Internal Storage and Storage card bit.
Also, I seem to get A LOT of lag when I play a game, is it normal? Probs coz the phone ain't too power full maybe
I did it, and it works well, it just tells me Android missing :S :S
Is haret in anything other than the root of the microSD? If not, it won't pick it up. There is a trick to get it to recognize the build in something other than the root of the microSD but you'll need to check in that thread where you got the dualboot program.
Yea the dualboot program is really a WinMo issue. You need to set the registry entry for it to work correctly.
But since it's not an Android or even an XDAndroid issue, I'd prefer you to post Gen.Y related questions in the correct section of the forum. Thanks.
@R^7Z
Haret is in Storage Card/bootand. And I forgot where I got the dualboot program though lol.
@arrrghhh
First of all, I'll thank you yest, as I'm restricted to 5 per day.
Also, link to where I can find this thread/section.
Thanks for all the help guys
In short if you want to use that program, you will need to visit the thread where you got the dualboot program from OR push everything up a level. In other words, cut and paste everything under the andboot folder to the root of the microSD and it should work like a charm, my friend!
R^7Z said:
In short if you want to use that program, you will need to visit the thread where you got the dualboot program from OR push everything up a level. In other words, cut and paste everything under the andboot folder to the root of the microSD and it should work like a charm, my friend!
Click to expand...
Click to collapse
What was the reason they told us to do an andboot folder then?
Well aside from "organization", not much else
I honestly only run one build because it is my preference to do so. Most who know what they are doing (or at least more than I do), use the rel_path=andboot option. "6 one way, half a dozen the other" is what I say.
R^7Z said:
Well aside from "organization", not much else
I honestly only run one build because it is my preference to do so. Most who know what they are doing (or at least more than I do), use the rel_path=andboot option. "6 one way, half a dozen the other" is what I say.
Click to expand...
Click to collapse
Well, apart from the fact that I understood NOTHING from that previous post, I want to say that it worked like a charm I cut all the files in the andbooot file to the right place, and what do you know, it worked!
I have a tiny thing to ask you guys Its laggy, and I mean VERY laggy. When i play games, like Angry Birds and such, it jumps, makes it tedious and not really fun to use. I do understand that my phone wasn't built for Android, and that Android needs higher system specs then Win Mobile (it also lags a bit on Win Mobile LOL) but maybe there is a fix to that.
When I check phone settings, it says I'm running Android version 2.2.2, which I think is the latest version, so maybe going to a previous version will make it better. I'm ready to take a small downgrade, only if I will still be able to use all my stuff (3G, camera, wi-fi etc.) I'm hoping to make Android my permanent OS, but with it being this laggy, I'd rather not.
Any ideas
ThaiDai Android Loader is a program for Windows Mobile 6.1.
--------------------------------------------------------------
A few words why I stopped development:
I had to stop this project for personal reasons (reason called baby).
And this was easy because nearly nobody (or only a few < 10) used my loader.
But more important for me now: I do not see any improvements on bugs or missing features for Blackstone with Android, there is no real kernel developer community anymore. Sound problems, BT, battery and performance aren't funny if you want to use the device. For playing with Android it was ok and I learned a lot. But not for every day use. So I switched back to WinMo 6.1.
And yesterday I bought a Samsung Galaxy Note. Android rules!
--------------------------------------------------------------
(6.5 builds will not work because there is an error in writing files with Windows Mobile 6.5 which will appear when linux makes a fsck. So no support for 6.5
You can use builds like Damn Small Topix (Rapidshare works) or other 6.1 builds)
If you run into problems and want help, please provide me with the generated log files in folder "thaidaiboot/Logs".
No Logs = No help!
With the loader you can start Android or you can install Android without doing the usual things: no copy, no edit, no changes etc.
The setup (a normal cab-file) prepares the necessary files on your sd card automatically.
With the program you select what you want to do (install, backup, restore, change device, choose Android Build, edit startup.txt and build.prop) and press "Boot". That's it.
Program is installed in autostart folder and will automatically boot into last chosen OS after a number of seconds (default 100 s, you can change of course). Stopping countdown is easy: klick somewhere or change a value).
FRX07.1 build is included as default. More builds to come from tomorrow.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-------------------- v2.3, 2011/09/18 --------------------
Changelog: including 2.0/2.1/2.2 changes, starting with 2.3 ;-)
---- 2.3 ----
Editor for build.prop for each build
Explanations for entries in build.prop (just started to gather them)
additional logging information in window mobile stage of installation
selected builds stay in original folder (so no system.tgz in folder thaidaiboot) and are used in rootfs.img for installing /system
---- 2.2 ----
Timer option for booting into Android automatically after n seconds is working correctly now.
I added the option to select Apps for installation - but I do not change the apps delivered with the specific build. So this part ist only for your own flavour of apps you want to add.
Next big change: Editor for startup.txt. You can easily change the commandline parameters (like display density or OC or ...). The set parameters cannot be changed until now (I didn't see the necessarity).
Resolution changed to 480x800 and using it. So from now concentrating on Blackstone. Other 480x800 devices may work but still no guarantee.
Resolved some stupid error with choosing Kernels (I just found this one today, nobody else did before)
---- 2.0/2.1 ----
Changed format for builds to tgz. Now it is easier for me to prepare cwm based builds
New rootfs.img for installation and updates with tgz files
Added download links for build thunderbolt
In every build I checked I have to make changes to build.prop: double entries, wrong entries, obsolete entries, stupid entries, optimized entries. That's why I started adding a build.prop-editor to my program.
As default I still use NeoFroyo. (without GAPPS).
Added GAPPS as Update-Package (selected on first start, please install)
New setup package and installation file for windows mobile
For all typical devices like Blackstone, Diamond, Raphael, Rhodium, Topaz
New user interface in windows program
autostart into Android after n seconds (changeable)
new UI (Hubs)
switched from comboboxes to lists for selection (better information on first look)
new ts-calibration for Topaz (thanks to Aggy in Neopeeks forum)
changing Hubs color possible (just for fun)
removed Apps from system.ext2 to folder APPS, so the different Builds will be much smaller and I have to install and upload Apps only one time
with apps in folder Apps the selection of Apps in loader program will soon be possible
Downloads:
One big cab file (about 95 MB) including everything.
Setup for ThaiDai Android Loader v2.3 with FRX07.1
Bugfix for Exe, please copy to your program files folder with thaidailoader, will give a complete new cab file next days.
Some more builds:
Setup for Build Froyo Blue
Prepare SD card:
You need 4 primary partitions on sd card (I use MiniTool Partition Wizard Home Edition)
All sizes here are only examples. Start with them, feel free to change.
All partitions have to be "primary" (ignore warning in Windows)
Partition 1: FAT32 (at least put folder "thaidaiboot" from zip here)
Partition 2: EXT2, about 150 MB (used for Android system partition)
Partition 3: EXT2, about 250 MB (or more for Android data partition)
Partition 4: EXT2, about 100 MB (for Android cache partition)
Size of partition 1: [Size of sd card] - [Size of 3 EXT2]
Installation:
Delete folder thaidaiboot on sd card and deinstall Loader program before using this setup (copy cab to sd card and start it).
- copy first big cab to sd card
- execute cab and start setup
- install on sd card (not on internal memory!)
- start "ThaiDai Android Loader" from start menu
- select your options and boot into Android
Adding new builds:
- copy cab for build to sd card
- execute cab and start setup
- install on sd card (not on internal memory!)
- start "ThaiDai Android Loader" from start menu (build will be copied - takes some time)
- select different build and install (Please start program one time before adding builds!)
Warning:
- Do not edit or change files in folder "thaidaiboot" on your own. Use the program.
- I hope it will install now in all language versions of Windows Mobile. I tested it only with an english installation. And maybe some foreign fonts (like Thai ;-)
aren't recognized by haret.exe or linux.
-------------------- ThaiDai Android Loader options: --------------------
Administrative Tasks
backupSystem
backupData
make Clean
installSystem
fixSystem
fixData
restoreSystem
restoreData
When started in Windows Mobile no Task is selected!
After "haret.exe" is started my installation script will go through the selected tasks
Device Selection
Select "startup.txt" and "ts-calibration" from folder "Startups" for possible devices in FRX07 like Blackstone, DIAM, RHOD, RAPH, Topaz
Build Selection
Select the build you want to install
NeoFroyo (default)
XDAndroid FRX07 (the original)
THUNDERBOLT
... (tell me what you want to see here)
Kernel Selection
Select the kernel you want to use
1342
1346 (default)
Typical Tasks:
For a new and clean installation (data is deleted) choose: "backupSystem", "backupData", "makeClean", "installSystem"
For an update of your system (no data changed) choose: "installSystem"
You can always choose to start with backups first and choose: "backupSystem", backupData"
Tasks with "fix..." are only necessary for updates I will post here
Select Device [Blackstone]
When you select another device, the program checks if there is a "startup.txt" in the folder of this device. If not found, nothing is changed. When a "startup.txt" is found it is copied to the folder "thaidaiboot" and you can start your device.
If a "ts-calibration" is found, it is copied. Please be careful: I do not know if all ts-calibration files are ok.
-------------------- OK-not OK: --------------------
Tested only on Blackstone
OK
Wifi works right from the first start
Market ok
Phone ok
Camera and Video
Root access ok
3.5 jack ok
3G (UMTS HSDPA in Germany) ok
Not OK
Audio stuttering
Youtube not really good (HD problems, normal ok)
Bluetooth starting, but no pairing
Audio, not ok: stuttering
BLAC100-kernel-modules-2011-04-11-1302528888.zip
Audio work on my phone
http://forum.xda-developers.com/showthread.php?t=999544
I don't have any problem with your thread, in fact, I'm glad you made it work
This is a communitary effort, and I'm only an average tester, so couldn't be more far from angry for this.
Thank you!
Hi ThaiDai,
Thanks for sharing your work.
Quick questions:
- have you modified the Roofts.img from FRX07 adding CMW? or modified the roofts from Neopeek CMW 1.8?
- What is the size of the cache partition you recomend as it is now? Neopeek CMW 1.8 recommends between 50-100mb.
I'll try as soon as I finish working.
Brgds
Downloaded the last version of rootfs.img from XDAndroid rootfs Build Service and used this as a starting point.
As far as I understand we do not need a cache for the Android build FRX07 anymore. But for CWM (and his logs) we need. So I will try later to flash the next version with a very small cache partition size.
But first I want to try and repair (if necessary) the scripts, so that other devices can be used (tried?) with this build.
Wait and see...
Update to Version 0.99 (Full Install and Update Only)
First post updated with new version 0.99.
Included download links for Full Install (complete npkboot folder) and Update only (zip-file inside npkboot).
And it should be possible to test this build on other devices now. Tried to restore the multi-device-usability. But no garanty.
Tried the previous version and worked nice and fast. (with cache partition of 50 Mb)
I'll download and try the new version now!
Please try if the Update Only works. I have to check myself later. Didn't do this right now. Thanks
ThaiDai said:
First post updated with new version 0.99.
Included download links for Full Install (complete npkboot folder) and Update only (zip-file inside npkboot).
And it should be possible to test this build on other devices now. Tried to restore the multi-device-usability. But no garanty.
Click to expand...
Click to collapse
update only dowload not working can you check it please thanks
its working now thanks
Thanks man, the first Android that works on my Blackstone. I tried several builds CWM and not CWM, but this seems to work w/o probs - so far
phsnake said:
Thanks man, the first Android that works on my Blackstone. I tried several builds CWM and not CWM, but this seems to work w/o probs - so far
Click to expand...
Click to collapse
Please give these credits to the developers of XDAndroid. I didn't do very much here, only made a CWM build from the original ext2 based build.
But I'm happy you can use Android on Blackstone with this one.
BTW, remember to update SU binary fron superuser app, and better if you don't reuse app data from previous builds. It will surely make your wifi fail, probably other things.
I've been using the XDAndroid FRX07 CWM by ThaiDai 0.99 build from last nigth, and so far so good.
Performance is quite good, batery life acceptable, and the problems are the same as XDANDROID FRX07 running on the Sd (BT, audio stuttering and wifi disconnecting intermittent).
questions:
- have you tried to change the behaviour of the red button using spareparts? it didn't worked for me.
- have someone use the old fancy widget (the one HTC weather clock replica)? it does not work.
Sorry if this question sounds stupid. I already tried to read the info in neopeek but still don't fully understand it, so anybody that is willing to explain to me, thanks!
I have been using the FRX07 and the previous version of XDAndroid in the normal build (one folder in the SD Card). What is the benefit and the difference of running it in this CWM way? Is it better performance, better battery life, or better management?
lie_ui said:
Sorry if this question sounds stupid. I already tried to read the info in neopeek but still don't fully understand it, so anybody that is willing to explain to me, thanks!
I have been using the FRX07 and the previous version of XDAndroid in the normal build (one folder in the SD Card). What is the benefit and the difference of running it in this CWM way? Is it better performance, better battery life, or better management?
Click to expand...
Click to collapse
Some have claimed better performance, but in my testing it's actually worse.
I guess one benefit with having a dedicated data partition is USB mass storage (should) work properly. Other than that it's a lot of work for very little reward - perhaps if you jump builds a lot, CWM has a nifty backup/restore feature built-in to it...
Eodun said:
BTW, remember to update SU binary fron superuser app, and better if you don't reuse app data from previous builds. It will surely make your wifi fail, probably other things.
Click to expand...
Click to collapse
I didn't change the apps, only took them from the official FRX07 build
arrrghhh said:
Some have claimed better performance, but in my testing it's actually worse.
I guess one benefit with having a dedicated data partition is USB mass storage (should) work properly. Other than that it's a lot of work for very little reward - perhaps if you jump builds a lot, CWM has a nifty backup/restore feature built-in to it...
Click to expand...
Click to collapse
You should give it another try
ThaiDai said:
I didn't change the apps, only took them from the official FRX07 build
Click to expand...
Click to collapse
I was referring to a problem posted above, sorry. The thing is I got some nasty problems (in fact had to reinstall again) because I tried to restore some data+apps with TB and it ruined wifi.
Hi Eodun, what do you think the benefits of the CWM build of FRX07?
Its really faster, better battery life, etc? Can you give some insight?
lie_ui said:
Hi Eodun, what do you think the benefits of the CWM build of FRX07?
Its really faster, better battery life, etc? Can you give some insight?
Click to expand...
Click to collapse
It could be faster,you'd get usb storage to work,battery life shouldn't change.