I can get the unlock code by entering bootloader, typing dualser and then AT%UREG?3FE00C,4.
Can I get the same info using the mh commands in hte default startup of bootloader?
vpreHoose said:
Can I get the same info using the mh commands in hte default startup of bootloader?
Click to expand...
Click to collapse
No, these commands deal with organizer memory, the AT command reads from phone memory. 4MB of flash and 256 kB RAM, completely separate from the organizer, which has 32/64 MB RAM and 32 MB flash.
Thanks
So the Bootloader only gives access to the 32Mb, which obviously contains the Bootloader "mh 18A0" and CE ROM at around mh 41000.
Is there any way to get at the radio memory, other than via AT commands?
Thanks
Many people seem to be of the opinnion that you cannot. I believe there should be a way. After all it is flashed via software. Unless of course the flashing is done via the same RS232 stream. ???
martinlong1978 said:
Unless of course the flashing is done via the same RS232 stream. ???
Click to expand...
Click to collapse
It is.
Hi,
I used
Code:
free - m
with no luck. I tried to use
Code:
dmesg | grep ^Memory
but got no output.
When I use
Code:
free
in terminal I get-
Total memory - 196584
used memory - 193916
free memory - 2668
I am looking for RAM again and again because when my phone starts, the "System Tray monitor" software shows free RAM 98MB initially. Then after couple of minutes it shows free RAM 72MB (without running any program). If I know exactly that the phone has 192MB RAM instead of 288 MB then I can change it.
My doubts is- How much memory does the OS take? (my phone's OS is sapphire 1.6, REL, brand:HiAPK.com).
Do you know any possible way to get exact RAM and ROM of the system?
Thanks in advance.
192 mb is the usable RAM on the 32A, the rest is reserved.
The ammount of RAM depends on the model so if you want to know for sure which one you have you can boot into fastboot and check if it says 32A or 32B.
Hi,
Thanks a lot. Finally I found it. It is 32A.
Thank you very much
Hello all,
I seem to have only 256MB RAM on my nexus one.
How I checked the RAM:
Command Prompt -> adb shell
-> cat /proc/meminfo
Gives me a total of 212.
Very strange.
Do a search.
I agree do a search.
Short answer is they held back some Ram on the stock Kernel.
Cyanogen put out a "high-mem" kernel which increased us up to abour 400, but it requires root to flash it.
My mistake, should have done a search first. But looking at 212MB RAM was rather shocking
@seanowns
Thank you.
I followed directions as posted on:
http://winmo.techparaiso.com/mtty-heaven-for-flash-junkies-on-windows-mobile-phone-devices/
on the CMD I typed set 14 0
Then typed task 29
Then task 8
Then disconnected and held the vol down and end, came back to the tri color screen,
Connected the USB, ran Kwbr_Topix_1.5.7 ROM (ROMUpdateUtility.exe)
It went fine, the phone rebooted, and all I get is
Stick together logo
R 2.08.50 08~2
G 15.34.50.07u
D 1.72.82124
Waited for 30 min and still no progress on booting,
I even did a hard reset, and still the same above issue.
PLEASE HELP !!!
richsark said:
I followed directions as posted on:
http://winmo.techparaiso.com/mtty-heaven-for-flash-junkies-on-windows-mobile-phone-devices/
on the CMD I typed set 14 0
Then typed task 29
Then task 8
Then disconnected and held the vol down and end, came back to the tri color screen,
Connected the USB, ran Kwbr_Topix_1.5.7 ROM (ROMUpdateUtility.exe)
It went fine, the phone rebooted, and all I get is
Stick together logo
R 2.08.50 08~2
G 15.34.50.07u
D 1.72.82124
Waited for 30 min and still no progress on booting,
I even did a hard reset, and still the same above issue.
PLEASE HELP !!!
Click to expand...
Click to collapse
you have the wrong radio. flash either 2.07.51.22 or 2.09.51.03_2 and you will be fine.
Try and flash also the radio again! When you used mtty you also formated the radio and now you need it! The phone is fine, but try to read carefully the How to flash.....here http://forum.xda-developers.com/showthread.php?t=609477 .
Even if you think you know everythin....learn before you flash!
Thanks guys... I am back up now .... heehhhhh I soiled my pants
viperd said:
When you used mtty you also formated the radio and now you need it!
Click to expand...
Click to collapse
not true, mtty doesn't touch the radio.
samsamuel said:
not true, mtty doesn't touch the radio.
Click to expand...
Click to collapse
task 29 formats the drive partition of the device where the ROM (.nbh) file resides
jigners said:
task 29 formats the drive partition of the device where the ROM (.nbh) file resides
Click to expand...
Click to collapse
correct. just the system partition and not the radio partition.
____
I got this when running task 29 and Mitty
Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=7662
erase_page - error bad status: 0xB791E960
ERASE block 460 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
Did I miss an important step? I think I may have not moved a necessary file??
yea that looks correct for task 29 output.nothing wrong there.
just type task 8 next and the phone will reboot.if you hold vol down straight awayit will return to boot loader ready to flash your rom.
samsamuel said:
yea that looks correct for task 29 output.nothing wrong there.
just type task 8 next and the phone will reboot.if you hold vol down straight awayit will return to boot loader ready to flash your rom.
Click to expand...
Click to collapse
ok, so the errors are ok??
BTW.. I did type task 8, but did not show that.. my bad.
richsark said:
ok, so the errors are ok??
BTW.. I did type task 8, but did not show that.. my bad.
Click to expand...
Click to collapse
Yep. These errors are normal and show up every time. The process is correct.
pablo11 said:
Yep. These errors are normal and show up every time. The process is correct.
Click to expand...
Click to collapse
Ok then !
Issue closed. Thanks a Mill !
To the OP,
If you need further help please post directly in the MTTY thread.
WB
There are plenty of advantages of using NAND version (in development) but there is huge risk - the new loader and waranty violation.
After darkstone released so called "RAM version" I started to think about the new direction of development of Android builds.
The advantage RAM versions over NAND is limited risk. It can be started on Stock HD2 ROM without waranty violation.
We need
- 100 MB for WinMo barebone (it is in ROM already)
- 100 MB for Android readonly system files (clean froyo, as darkstone SuperRAM Froy v1) or 150 MB for Sense RAM version
- 256 MB (or more) for some type of data.img.
Our HD2 has (I know there are different versions): 512 MB ROM and 448 MB RAM.
So we have a plenty of memory capabilities, and if WinMo barebone resides in ROM and Andoroid system files goes to RAM or even ROM (but not in NAND way - in "SuperRAM" way). I believe this is really good direction. Maybe it is a good way of next generation Android builds, but not NAND ones.
What do you think (developers) ?
(I do respect NAND developers hard work, it is hard to start new thread without thank you guys)
Edit
Please, do not take it as another "thanks to SuperRAM thread" (this is not the point)
WOW
This SuperRAM from darkstone just leave me wow that is really smoking rom
without one NAND but i respect the hard work from the developer of NAND
install android without use WM 6.5 just like one real android phone of have option to go back to wm install wm 7 and say ok i want go to wm 6.5 again jjuts like that
some person say but u could buy an android phone if you dont want to see wm mobile in hd2 ok i understand but some person just want to install and reinstall and try sothing all day
Im one of those. i dont know you ...
I wonder if over utilization of the ram can lead to hardware problems.
Thoughts?
First we need to know how the RAM version work? I thought ba a normal SD Build data is also going into RAM. What is so special about thius RAM version?
ronalgps said:
some person say but u could buy an android phone if you dont want to see wm mobile in hd2
Click to expand...
Click to collapse
What about ppls who cannot afford cash to buy a new Android phone for like $600-$900.
I have received my HD2 as a gift so.. people be kind when speaking about buying something new if we don't like what we already have/own.
If everyone was thinking like "if you don't want WM, buy an android phone" we would never have Android on our HD2s, neither WP7 nor ubuntu!
lemar123 said:
(I do respect NAND developers hard work, it is hard to start new thread without thank you gays)
Click to expand...
Click to collapse
Developers is not "gays". It is guys.
DerBozZ said:
(...) What is so special about thius RAM version?
Click to expand...
Click to collapse
RAM (way) is haret based version, so you do not have to put hardspl to you phone (or you can now restore stock rom cleaning hardspl). Most of latest stock firmwares are android friendly (radio is good enough). You can use WinMo (30s to boot) and then load Android (another 30s) without any risk of bricking your phone. I assume RAM resident version will be good enough (why not ?) like almost perfect microsd card version.
NAND versions will require new loader (magldr) - so there is always a risk of bricking your phone and, using hardspl you could clean it by a stock rom, there is no info about cleaning it same way.
Can anybody confirm that removing magldr is as easy as removing hardspl (in case of warranty service repair) ? Even it is easy cleanable - RAM version requires neither hardspl nor magldr - so it is pretty safe for me.
So, I have a hope devs/cooks will find the way to put all necessery "haret based" android filesystem files into ROM/RAM but leaving stock WinMo rom alone.
lemar123 said:
RAM (way) is haret based version, so you do not have to put hardspl to you phone (or you can now restore stock rom cleaning hardspl). Most of latest stock firmwares are android friendly (radio is good enough). You can use WinMo (30s to boot) and then load Android (another 30s) without any risk of bricking your phone. I assume RAM resident version will be good enough (why not ?) like almost perfect microsd card version.
NAND versions will require new loader (magldr) - so there is always a risk of bricking your phone and, using hardspl you could clean it by a stock rom, there is no info about cleaning it same way.
Can anybody confirm that removing magldr is as easy as removing hardspl (in case of warranty service repair) ? Even it is easy cleanable - RAM version requires neither hardspl nor magldr - so it is pretty safe for me.
So, I have a hope devs/cooks will find the way to put all necessery "haret based" android filesystem files into ROM/RAM but leaving stock WinMo rom alone.
Click to expand...
Click to collapse
Cotulla has stated that magldr is flashed over HSPL, to clean it all you have to do is flash a winmo stock ROM and it's gone back to normal.
orangekid said:
Cotulla has stated that magldr is flashed over HSPL, to clean it all you have to do is flash a winmo stock ROM and it's gone back to normal.
Click to expand...
Click to collapse
Hmm, mods closed this thread ...
Maybe because of rumors it is creating or maybe it was true.
That is why I prefer RAM version .
RAM introduces data corruption. Everything is loaded into the RAM and then synced with the SD card, but if your phone turns off (battery died or dropped phone) or you have a random hard reboot, you risk not being able to boot back into Android.
So I have one question, for those (like me) who have a RAM limitation (due to hspl) with 3.14 official rom, we have 50mb free ram in winmo.
Can we use this type of build or must we change for a custom winmo rom (with 200 + free ram) before ?
Igoran said:
Developers is not "gays". It is guys.
Click to expand...
Click to collapse
oupsss ...
Sorry, for that ... ;-)
@TonyCubed
I believe, it is not synced at all.
Changes are applied by /Android/root folder - http://forum.xda-developers.com/showpost.php?p=9767735&postcount=16
So no need to to sync. It is safe.
radiance26 said:
So I have one question, for those (like me) who have a RAM limitation (due to hspl) with 3.14 official rom, we have 50mb free ram in winmo.
Can we use this type of build or must we change for a custom winmo rom (with 200 + free ram) before ?
Click to expand...
Click to collapse
As I understand it, when Android is running winmo is completely shut down, so it isn't using any ram or cpu time.
That's why you can't just "quit" android and drop back into winmo, you have to reboot the phone.
Feel free to correct me if someone knows better.
tarwedge said:
As I understand it, when Android is running winmo is completely shut down, so it isn't using any ram or cpu time.
That's why you can't just "quit" android and drop back into winmo, you have to reboot the phone.
Feel free to correct me if someone knows better.
Click to expand...
Click to collapse
if my understanding is correct, winmo kernel should remain in the ram and works as "drivers", and helps communication between hardware and android
vista1984 said:
if my understanding is correct, winmo kernel should remain in the ram and works as "drivers", and helps communication between hardware and android
Click to expand...
Click to collapse
No, it doesn't remain in ram. When you start haret.exe it kills the windows kernel. It does not, however, erase what's currenty in ram at the time. haret uses some of those memory locations to map things.
So it's not good for me to have a limitation ?
mstrk242 said:
No, it doesn't remain in ram. When you start haret.exe it kills the windows kernel. It does not, however, erase what's currenty in ram at the time. haret uses some of those memory locations to map things.
Click to expand...
Click to collapse
thanks for the clarify,
but i was puzzled that why people suggest update quick gps in winmo to improve gps locating speed in android?
are there any booklets of Haret's mechanism for noob like me?
I don't think any of us know the pros and cons of Darkstone's SuperRam vs DFTeams NAND, seeing as how one of those isn't released yet...
mstrk242 said:
No, it doesn't remain in ram. When you start haret.exe it kills the windows kernel. It does not, however, erase what's currenty in ram at the time. haret uses some of those memory locations to map things.
Click to expand...
Click to collapse
Based on this I have a question then: If what your saying is for the most part accurate, Then in thought the kernel is killed but the rest remain, so from a clean boot into WinMO then a boot into android we arent utilizing the full capacity of the HD2 Ram? I understand haret uses some of the memory locations to map things, but meaning to map drivers or hardware information to the android OS?
This peaks my curiosity only cause if Android is using limited memory, then would a NanD Boot (Which I assume is a straight boot) be more benficial to run clean and possibly smoother?
I'm sorry if the question sounds dumb, but it really peaked my interest.
HaRET shutdowns winmo and maps certain portions of linux into certain memory addresses. No part of winmo remains once HaRET boots the linux kernel. To check how much ram you have available out of the total amount you can run "free" from terminal emulator or adb shell. if you get "free: command not found" then run "busybox free", if that fails install busybox and try again.
If any of you have ever checked dmesg's log you'll notice how it recognizes 448mb of ram.