Related
I have searched the forum but could not find something of relevance.
It might sound stupid and maybe there is an easy explanation, but what I just don't understand is the following:
TyTN specs say 128meg ROM, 64meg RAM.
Looking at Start->Settings->Storage it tells me (translating from German):
File storage total: 56.22 megs
Program storage total: 48.80 megs
Then the usual stuff like 'used' and 'available'.
Of course there is the ExtendedROM which shows a total of 9.57 megs.
Where's the 128 megs gone or what am I missing here??? :roll:
Thanks for your help.
Cheers,
StonyA
the operating system basically. a perfectly intact copy is held in rom so that you can reinstall at any point using hard reset, this image is what you flash when you update your phone (same goes for your radio protocol).
hope this helps
herman3101 said:
the operating system basically. a perfectly intact copy is held in rom so that you can reinstall at any point using hard reset, this image is what you flash when you update your phone (same goes for your radio protocol).
hope this helps
Click to expand...
Click to collapse
Hello herman3101,
Thanks for your reply! Still a bit confused though. I understood the files stored in the "ExtendedROM" to be those who are used for reinstall.... ???
Even though, why doesn't it show Total ROM 128megs and xxx used???
I guess, I am still something missing :?
Cheers,
StonyA
The extended rom contains the customizations and patches that your carrier decides to put on, this is the way that different roms vary between carriers. The extended rom does NOT contain the operating system, this in a seperate hidden region of your rom (note that rom in this case has two variations of a meaning, one refers to the physical memory on your phone, the other refers to the image that is placed into that memory)
Think of that part of your memory as being an image of your windows xp cd rom, for normal day to day running its not needed as all the files it needs recide on your hard disk but when you come to reinstall you need to work of the cd. Same principle applies to that part of the rom. apologies if my analogy only makes sense to me, I have a habit of doing that.
Hey herman3101,
Many thanks for your explanation. Yes it does make a lot of sense what you are saying. Still don't understand why HTC does not openly show that, i.e. 128 megs rom, xxx megs used, xxx megs available.
Cheers & great weekend,
StonyA
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.
Starting this thread again as my previous one was deleted during the board's transformation yesterday...but I think it's important to bring up the subject.
Coming from an older Android terminal (Htc Magic), I still don't understand how so few dev's out there are actually using ClockworkMod Recovery for their ROM. I know, a lot of you come from WM 6.5, where USB-Flash was the only way to go but now things have changed ! If you are fan enough of Android to be willing to flash it completely to the Nand, wiping WinMo6.5, then go with it and start flashing your ROMS the Android way. The CW way !
As a reminder, CW allows to :
- Flash your ROMS from the SD card. Imagine you want to flash a new ROM but have to leave for 2 days without a computer; it's not a problem ! Put it on the SD card and flash it later !
- Easily implement new kernels or updates. Doing so, dev's can propose completely clean build with the option to flash as many add-on's, updates, kernels or fixes you want. Look here : http://forum.xda-developers.com/showthread.php?t=810471. You can't make it easier.
- Partition your SD card with an ext partition the size you want without the need of a software or a linux-based iso. If you are a Windows user, that's a huge time saver !
- Back-up ans restore. That's a HUGE bonus. Want to flash a new ROM ? Back-up all your current ROM (5 minutes), then flash the new one. Don't like after all ? Restore your backup in 5 minutes...
- For me (and here, I'm not my saying it's always the case, just FOR ME), sd data transfer through CW is two times faster than through MAGLDR.
- Many more...
The same goes for EXT. Using data.img is outdated, it's another WinMo days leftover. Ext is actually mounted as an internal memory, allowing Sense Roms. And the apps installed there won't need to be reinstalled every updates...
It's tough for a Android user like myself to find a proper ROM/Zip with data2ext support these days. Pretty much MDJ, thank God for him. It seems that there a lot of ROMS to choose from but actually there isn't. Especially when the DAF to ZIP tool from the board doesn't work with all the DAF's releases (most of the time it's actually the releases that are not made right).
So please, be an Android user and make the step. It's like you found the door but are afraid to come in...
Just go and read the CW tutorial thread if you are unsure. I'll be willing to help also...
Flashing different custom ROMs, some of us, sooner or later, are meeting ONE TERRIBLE PROBLEM - device getting bricked... Unfortunately, might happend...
With new developments of feropont we are getting, finally, updated (in the meaning of ballanced and smooth "relationship" between hardware and software) device. He, certanly, done jobs, Toshiba supposed to do before releasing the device.
... And it is real pain - inability to enjoy using such improved device...
As a members of xda-developers community, we become pretty skillsful resolving different problems - we have huge support over here - this is one of the reasons for opening this thread - to get help, and help others. Again - everyone of us can meet the problem.
I am a hard user of Windows Mobile from early years when Dell Axim just came to public. TG01 - my last device, in which I found full functional Pocket PC and pretty developed cell phone - all in one , and with my accurate attitude in using my "toy" I did not expect to fall victim of software glitch... But it happened!
My particular problem is really unusual – I cannot flash ANY custom made ROM (even earliest – see pere’s ROM table), But I am ABLE to flash any official ROM (!?)
We discussed the problem with feropont, he found it pretty unusual - I am inviting you to open discussion here, in one place, related to most common problems TG01 Users can meet… and hope, I'll find solution for my problem, as well.
Following, I would like to provide with links to previous answers to came across problems – all about TG01. (send me links – you consider helpful – will post them here in a first page).
Two brick variants from mirolg
Short Pins Illustration from kevinpwhite
TG01 Downloader TG01 Driver TGTool contains TG Tool
Smart Quote:
fxdjacentyfxd said:
1) always check .tsw file in prg directory via tgtool.exe software
2) from time to time I execute chkdsk utility to check SD card.
Only after point 1) and 2) I start sdll+ uploader.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
Another try...
Pere's TG01 Cooked ROMS' Table
eskyt said:
My particular problem is really unusual – I cannot flash ANY custom made ROM (even earliest – see pere’s ROM table), But I am ABLE to flash any official ROM (!?)
We discussed the problem with feropont, he found it pretty unusual - I am inviting you to open discussion here, in one place, related to most common problems TG01 Users can meet… and hope, I'll find solution for my problem, as well.
Click to expand...
Click to collapse
Hi.
What method of flashing You used to utlize ?
I can confirm only that using 3-pin metods ( as always I say - absolutely do not use this method if You really do not have to. ) should be involved only for official roms . Someone will say not true. I say I had always problems to flash custom roms utilizing this method so always, I repeat always, flash only any official rom this way. Never have had any problems with official roms but always problems with custom roms including "terrible" messages like "NAND flash error". Maybe flashing custom roms this method cause such big problems in the future ? It seems to be service mode not normal flashing mode so who knows what wrong can wait for us if rom is not official.
Anyway utilizing sdll+ software seems to be ok both for official and custom roms.
I have not had any slightest problem with it.
Sometimes people are gilty themselves. Flash strange custem roms with God knows where custom bootloaders and it is enough. For example, Nokser has bricked His tg01 and only JTAG can help him. Too much experiments with unknown matter and disaster is ready. Many people tried His last rom and who knows whether they are next candidactes to have unresolved problems with their tg01s.
Regards
fxdjacentyfxd
Flashing any device always has a risk attached, whether that be a Toshiba TG01 or a pc motherboard bios, still as long as procedures for flashing are followed correctly nobody should have many problems, but obviously bad things can happen, how many motherboards have died on a bios flash for example?
Flashing TG01 is no more risky than flashing other devices, however what you flash it with is the area where risk becomes involved.
I think what is needed is a tool for HTC devices called 'task 29' basically when we flasg custom ROMs over and over again, some roms are bigger than others etc, so they dont overwrite all system files, therefore, old system files from the previous ROM is left in the new ROM. this corrupts the phone, therefore you expeirience bugs. We need a tool like task 29.
but personally i dont/ havent faced any of these problems... *touch wood*
Thank yo guys!
To fxdjacentyfxd - thank you for sharing thougts.
I am exactly an example of "next candidacte" - I always was extremly carefull and used sdll+ only. I even did not know how to use3 pin method (feropont, many thanks him, instructed me).
I guess, (really just guess), my problem came from corrupted .tsw file - you know, we can see full sized file on memory card, when (factually) copying process was interrupted...
This is the riddle - what "changed" in the boot area, that compel my device to accept officials ROMs only (and only through 3 pin method), when customs (through sdll+) stopping it on Toshiba logo...
To olyloh6696 - yes, feropont had mentioned this future in privet correspondence - would be good to have it!
To (InsertNameHere) - "obviously bad things can happen" - supposed to be motto of this thread
eskyt said:
To fxdjacentyfxd - thank you for sharing thougts.
I am exactly an example of "next candidacte" - I always was extremly carefull and used sdll+ only. I even did not know how to use3 pin method (feropont, many thanks him, instructed me).
I guess, (really just guess), my problem came from corrupted .tsw file - you know, we can see full sized file on memory card, when (factually) copying process was interrupted...
This is the riddle - what "changed" in the boot area, that compel my device to accept officials ROMs only (and only through 3 pin method), when customs (through sdll+) stopping it on Toshiba logo...
Click to expand...
Click to collapse
Accordingly to what You wrote about corrupted .tsw file I forgot to mention that after every copy of new .tsw to prg directory on SD card I :
1) always check .tsw file in prg directory via tgtool.exe software
2) from time to time I execute chkdsk utility to check SD card.
Only after point 1) and 2) I start sdll+ uploader.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
B] always [/B] check .tsw file in prg directory via tgtool.exe software
Click to expand...
Click to collapse
That is smart! Did not know it before. Hope, other users will take it into consideration...
eskyt said:
That is smart! Did not know it before. Hope, other user will take it into consideration...
Click to expand...
Click to collapse
Reading posts about bricked tg01s I got to conclusion that some bricks were really becuase of corrupted .tsw or logical errors on SD card. So I have always thought it is worthy to waste 1 minute to check .tsw in prg directory than irreversibly bricked tg01.
P.S. Your case is really very, very strange. To "damage" bootloader it accepts only official roms.... I can not belive in it. Must be other explanation.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Must be other explanation.
Click to expand...
Click to collapse
... - and I am trying to find solution...
i agree with olyloh6696's opinions
when we flashed roms so many times,maybe our phone's NAND flash appear some bad blocks.it's really like the problems in HTC phones.
Maybe use Tgdownloader flash an Official rom will helpfull with this problem.
Anyway,when we cook roms,tgtool always check if there's any error in our custom rom,and we just make changes in OS partition,didn't change/edit anything with the Bootloader or Radio.So i must say the most possibility that brickes our phone should be the Flashing Progress.
eskyt said:
This is the riddle - what "changed" in the boot area, that compel my device to accept officials ROMs only (and only through 3 pin method), when customs (through sdll+) stopping it on Toshiba logo...
Click to expand...
Click to collapse
It is similar I wrote in my first post. Typically ( I am not going to check more ) I am not able to flash rom via 3-pin method if rom is not official. It seems I have always had this feature. I had maybe free "bricks" since I have tg01 , because of my experiments with drivers and so that to flash any good rom via 3-pin it had to be always official rom ! Fortunately sdl++ works fine for any rom.
Did You flash many custom roms ? Maybe one of them is "this one" and it is worthy to find out which it is.
On the other hand as I remember tgdownloader has feature to upload different areas of the rom separately ( boot area too ).
Maybe someone brave could upload this method boot area ? If it works You could upload Your boot area too.
I know, it is hardcore
Regards
fxdjacentyfxd
ffboy2009 said:
i agree with olyloh6696's opinions
when we flashed roms so many times,maybe our phone's NAND flash appear some bad blocks.it's really like the problems in HTC phones.
Maybe use Tgdownloader flash an Official rom will helpfull with this problem.
Anyway,when we cook roms,tgtool always check if there's any error in our custom rom,and we just make changes in OS partition,didn't change/edit anything with the Bootloader or Radio.So i must say the most possibility that brickes our phone should be the Flashing Progress.
Click to expand...
Click to collapse
yes, as no tool exist, the best method for us is for every ROM flash:
1) Hard Reset Current ROM
2) Flash Stock ROM
3) Hard Reset Stock ROM
4) Flash New ROM
5) Hard Reset
You could even go as far as Reflashing the same ROM over the same ROM again to eliminate further errors.
This is the recommended precedure to follow, however I usaully miss out steps 1,2,3.
My bootloader is dead and i don't have a solution...
Maybe one... bay Riff Box
Nokser said:
My bootloader is dead and i don't have a solution...
Maybe one... bay Riff Box
Click to expand...
Click to collapse
Well, I remember wonderfull times when any bootloaders were in OTP ROM or EPROM. None possibility to "kill" the device. Today is to be cheap, easy, universal and we pay for it.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Today is to be cheap, easy, universal and we pay for it.
Click to expand...
Click to collapse
...So true.
By explanation of feropont official ROM supposed to "zap" like kind of bad blocs in a flash memory (if any exist...), but, as we can see on my example Toshiba is "writing" every thing above of exist information without "cleaning" inside flash like task29 HTC is doing... He also mentioned that problems, mostly, becoming not in a boot area, but later, on the level of (qoute) "kernel initialization, xip..." - I am not prepared enough technically to discuss this llevel, but it is seems for me like I will stay with Malaysian ROM for ever...
eskyt said:
...So true.
By explanation of feropont official ROM supposed to "zap" like kind of bad blocs in a flash memory (if any exist...), but, as we can see on my example Toshiba is "writing" every thing above of exist information without "cleaning" inside flash like task29 HTC is doing... He also mentioned that problems, mostly, becoming not in a boot area, but later, on the level of (qoute) "kernel initialization, xip..." - I am not prepared enough technically to discuss this llevel, but it is seems for me like I will stay with Malaysian ROM for ever...
Click to expand...
Click to collapse
The main trouble is that the TG01 really does not make a general cleaning of flash Task 29 by analogy HTC devices. Judging from the descriptions of problems, bootloader is absolutely not damaged, it allows you to upload the whole flash ROM is not just any official ROM. The problems begin during kernel initialization XIP at the first boot device on any custom ROM. Every chef in the community TG01 anyway does not collect the full XIP, all cut-ins debuggers and encryption (kd.dll hd.dll mencfilt and etc). Unfortunately I have no time but first and foremost I would like to cook a custom ROM with the full original XIP, that would finally remove the issues in which there were bad blocks of flash in the kernel XIP or OS.nb.
Thx
feropont said:
The main trouble is that the TG01 really does not make a general cleaning of flash Task 29 by analogy HTC devices. Judging from the descriptions of problems, bootloader is absolutely not damaged, it allows you to upload the whole flash ROM is not just any official ROM. The problems begin during kernel initialization XIP at the first boot device on any custom ROM. Every chef in the community TG01 anyway does not collect the full XIP, all cut-ins debuggers and encryption (kd.dll hd.dll mencfilt and etc). Unfortunately I have no time but first and foremost I would like to cook a custom ROM with the full original XIP, that would finally remove the issues in which there were bad blocks of flash in the kernel XIP or OS.nb.
Thx
Click to expand...
Click to collapse
Thanks feropont.
Very interesting. You mean that if I cook my rom not removing any .dll from original XIP I will have more "safe" rom. Have any of mentioned dll's like for debug any influence on rom speed ( can be switched on-off after flashing ) ?
Bootloder part seems to be possible be overwritten too in some cases. Example, Noksers works.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Thanks feropont.
Bootloder part seems to be possible be overwritten too in some cases. Example, Noksers works.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
Unfortunately I can disappoint you, this is not an example of a new bootloader, and the result work of a new OEM, in particular, changed the entrance to the bootloader. Bootloader by definition can not be in OS.nb, he placed in the common part of the file .TSW who all mistakenly called RADIO, and if elementary compared Hex, the differences are almost no. Located in the very first sectors and is called MIBIB_BOOT.
Code:
*** MIBIB_BOOT Region Info ***
Region 0: "MIBI " start: 0 size: 80 r-size: 32 Ver: 0x0000 SubVer: 0x0000
Region 1: "SIM_ " start: 80 size: 48 r-size: 0 Ver: 0x0000 SubVer: 0x0000
Region 2: "FSBL " start: 128 size: 32 r-size: 24 Ver: 0x0000 SubVer: 0x0000
Region 3: "OSBL " start: 160 size: 32 r-size: 24 Ver: 0x0000 SubVer: 0x0000
Thx
feropont said:
Unfortunately I can disappoint you, this is not an example of a new bootloader, and the result work of a new OEM, in particular, changed the entrance to the bootloader. Bootloader by definition can not be in OS.nb, he placed in the common part of the file .TSW who all mistakenly called RADIO, and if elementary compared Hex, the differences are almost no. Located in the very first sectors and is called MIBIB_BOOT.
Click to expand...
Click to collapse
I have always thought , this device starts as typical ( known from microprocessors equpipped with boot section ) always from bootloader part but other circumstances decides whether after power up bootloder:
1) boot the system and "jump" to it
2) do other action like flash upload - check 3-pin condition or condition forced by sdll+ software
That is why I do not understand why Nokser can have completely dead device and not damaged bootloader.
Regards
fxdjacentyfxd
Since moving to Android I noticed most roms come with an md5 to check against the downloaded copy before flashing, just in case there is any corruption. Maybe a good idea to take a similar approach with tg01 roms.
I don't own my th anymore but flashed it in excess of 100 times using both sddl+ and 3 pins and never had any problems.
Sent from my Desire HD using XDA App
I am very new to android and tablets as well.
I want to know what is Custom made ROM ?
BadProgrammer said:
I am very new to android and tablets as well.
I want to know what is Custom made ROM ?
Click to expand...
Click to collapse
You get 1 freebie from me....
Please Google and also learn to use the search function of the forum in the future
Android custom ROM explained:
http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/
~~~
UnicornKaz said:
You get 1 freebie from me....
Please Google and also learn to use the search function of the forum in the future
Android custom ROM explained:
http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/
~~~
Click to expand...
Click to collapse
Yes ! I tried searching forums but i din't got the exact meaning for this so far i can understand Cutom made ROM is adding extra features and functionality on your tablet OS.
I also tried searching google which gave me this result
ROM is an acronym for Read-Only Memory. It refers to computer memory chips containing permanent or semi-permanent data.
More Clarification on ROM's will be helpful.
Edit : Thanks for the link
what does the narwhal bacon
Its just a custom made os for the device.
Sent from my GT-P7500 using XDA Premium App
The ROM is your OS, your system. With all the apps and settings, Kernel from Linux usw...
My gut instinct was to start describing a doofy Ferengi who eventually becomes Grand Nagus... wrong ROM!
But yes, the ROM is simply the software from your device or another which has been modified in some way by the community to add new features or fix bugs or whatever. Honestly, and I'm usually the last to say RTFM anywhere, there really is more than enough information around here on the subject... you may want to look around at sections for other devices to get a more generalized idea of what Android hacking is all about.
a ROM is not a place where we sleep???
go to your ROM and don't go out!
ROM is not a software...
Read-only memory (ROM) is a class of storage medium used in computers and other electronic devices. Data stored in ROM cannot be modified, or can be modified only slowly or with difficulty, so it is mainly used to distribute firmware (software that is very closely tied to specific hardware, and unlikely to need frequent updates).
In its strictest sense, ROM refers only to mask ROM (the oldest type of solid state ROM), which is fabricated with the desired data permanently stored in it, and thus can never be modified. Despite the simplicity, speed and economies of scale of mask ROM, field-programmability often make reprogrammable memories more flexible and inexpensive. As of 2007, actual ROM circuitry is therefore mainly used for applications such as microcode, and similar structures, on various kinds of digital processors (i.e. not only CPUs).
Other types of non-volatile memory such as erasable programmable read only memory (EPROM) and electrically erasable programmable read-only memory (EEPROM or Flash ROM) are sometimes referred to, in an abbreviated way, as "read-only memory" (ROM), but this is actually a misnomer because these types of memory can be erased and re-programmed multiple times[1]. When used in this less precise way, "ROM" indicates a non-volatile memory which serves functions typically provided by mask ROM, such as storage of program code and nonvolatile data.
but we call ROM because we put on the ROM