|
This post has been thanked 1 times. |
|
||||
Re: VOGUE 3.35.04 radio ported from Titan
Quote:
![]() ![]()
__________________
|
|
||||
Re: VOGUE 3.35.04 radio ported from Titan
Quote:
|
|
||||
Re: VOGUE 3.35.04 radio ported from Titan
Unfortunately, not everybody here is "smart" (i.e. experienced)!
However, I will generally agree that anyone who comes to forums like this one is taking a risk; and it's their responsibilty. But, not everyone understands the inherent risks. |
|
||||
Re: VOGUE 3.35.04 radio ported from Titan
Quote:
I am not blaming you for posting this radio for others to try nor am I saying that it is ok for others to do so. What I am saying is that it is foolish to think that everyone(expecially noobies) can and does understand the inherant risk when you do something like this. No hard feelings, Dan. |
|
||||
Re: VOGUE 3.35.04 radio ported from Titan
how do parts of roms decide where they will sit in memory? is it possible that due to the memory size difference between the titan and vogue that their different parts reside at different memory adresses, and when flashed to different device overwrite other parts??? example, say titan radio resides a little lower in memory, could it be overwriting part of the bootloader and therefore bricking the device???
The reason I ask, is because I would not have though flashing anything but a bootloader could brick a device, guess I will have to be a little more carefull with my thinking. I guess the short question would be, what desides where the rom gets written, the rom itself, or the bootloader that is loading it? |
![]() |
|
|
|