Related
This tool has been superseded by: http://forum.xda-developers.com/viewtopic.php?t=24779
Go there for support of the newer models! (thanks to Itsme)
Update June 3 2004: With an improvement of the repairing process it is now also possible to unlock the Orange SPV M1000. The latest version is v2.2
Update April 6 2004: After testing it was determined this tool works for all Radio ROM versions except for 1.05.12. If you have this version either use the older method or upgrade your phone with an upgrade by your vendor.
To provide a continued quality user experience, we are happy to announce an update to the XDA 2 network lock repair tool!
Supported Radio versions: 1.05.12A, 1.05.14, 1.06.00, 1.06.01, 1.08.00, 1.10.00.
Please report differences or additions to this list.
This tool does NOT support the XDA IIs, XDA IIi or XDA III.
As this tool is fundamentally different from the previous version it pays to read this closely:
The new tool is a PocketPC application. As such it no longer runs on the desktop itself. The good thing is it needs *no hard reset* anymore. The application communicates on the device with the GSM phone directly. The program xda2unlock.exe now needs to be copied on to your XDA 2. To do this there are two options (choices):
1. Use the packaged installer xda2unlock-setup.exe, which will install the program on your PocketPC for you. (so this does run on your desktop but does not unlock anything yet)
or
2. Copy the binary xda2unlock.exe onto your device manually.
Next is to run the application on your XDA 2. The following is taken from the readme.txt in the installer:
Code:
Welcome to the Himalaya network lock repair tool!
xda2unlock.exe v2.2
This tool installs a program on your Pocket PC called xda2unlock.
It is installed in the \Program Files\XDA2Unlock directory.
But you can also find it in under Programs in the Start menu.
You need to tap on xda2unlock to execute it. A screen will appear
informing you of the progress and any errors that might occor.
When you are done you can remove the program under:
Start -> Settings -> System -> Remove Programs
This tool is free and you can find more tools and information at:
http://forum.xda-developers.com
Running the tool on the XDA should provide you with information if it was successful or not. This tool should specifically provide support for newer radio versions such as 1.10.x.
If you have problems, it does not work or you see other strange behaviour please post it in this thread. Supply as much information about your software as you can find and about the circumstances.
Version 2.1 adds some more error reporting to assist with 1.05.12 problems.
Version 2.2 adds repairing of all locks instead of just the network lock.
Enjoy.[/b]
The original tool required a hard rest to enable the code to be obtained (as it went in to boot loader). I am reluctant to do a hard reset (unless I am forced to) as I have a working system and don't want to have to reinstall everything.
My question is - Does this updated tool now mean a hard reset is not required?
Use a backup program
Sprite backup can restore from bare metal(hard reset) in a few minutes. I have to use it several times a month and it works well.
Sim Unlock
I have been semi successful in unlocking my XDA II: :?
For some reason I was unable to unlock my phone using the latest method.
After 3 attempts I reverted to the Bootloader/hard reset method which was succesful in giving me an unlocking code.
I then entered the code and it was accepted.
These are my results:
Vodaphone sim - Phone signal ok but no GPRS?
Orange - No phone signal or GPRS
O2 (original sim) - Phone signal ok and GPRS ok.
Has anyone had similar results or any suggestions as to how I can rectify the above problems?
Any help would be much appreciated.
PS I must say this is a fantastic website and will be donating the money that O2 wanted to unlock my XDA II to the upkeep of this site.
Keep up the good work chaps.
feedback
Hi
I'm very much interested in feedback as the tool was only tested in a very limited way. What did it say when you ran it?
Did you run it with the blocked SIM in it or without SIM?
As you might have noticed the tool does not require a hard reset now.
magic failed
Hi,
I tried this potentially very useful tool a few times from my XDA II from THE LINK with O2 200 tariff.
It failed everytime with the following message (part)
Start of repair process...
Preparing modem ...
Performing magic ...
Failed to do magic
I have a vodafone sim card with £25 top up left that I would like to use up in the XDa II.
Any ideas please?
me too,with exactly the same problems,i got 3 XDA II from the Link with O2 but it doesnt work.It displays failed magic like Matts...So plz help me.
there is my situation:
I install the progamme to my laptop,then copy the file to my XDA II,after suscess install i run the file in my XDA II,it failed .Do i need to connect to internet ??? or sthing else?
success at last
The new xda2unlock failed for me as reported earlier so I tried using the earlier file direct on the PC after going into the bootloader as per instructions. This worked first time and extracted the unlock code.
Using this code I can now use my vodafone sim which has a lot of top up time prepaid.
NOTE:-
1, I did a full active sync backup to PC before starting. The backup file was approx 38MB.
2, I did a soft reset after removing XDA II from the cradle. It then behaved exactly like a hard reset installing from scratch from the extended rom.
3, I then restored the active sync backup using guest mode (I did not want to remove my old settings)
4, When prompted I replaced the XDA II contents with the PC contents.
5, Finally I did a fresh active sync.
My XDA II is now almost exactly as it was before I started.
The big difference is it is now UNLOCKED!!!!
MANY THANKS to the experts in this forum.
I now feel brave enough to tackle the extended rom with customization in mind.
@W4XY
Worked well.
Unlocked brand new dutch T-Mobile device.
Version: 1.60.00WWE
12/0/03
1.06.01
1337.16
1.60.16
MS 4.20.0 (build 13252)
Removed simm did a soft reset and then used the unlock file
So I had no Simm in it, during unlock
After unlocking it behaved like a HARD-reset
But unlock worked. Tested it with a KPN Simm and all is working well.
Tuurtje
but what is your info?
Ok,
I see a few reports of failure here, but still no idea what you guys are running. Please at least supply the info found in Start -> Settings -> System -> Device information
If you're interested in a fix that is.
I experienced exactly the same screen messages as Matt & Sid.
As I mentioned in my previuos post though I did manage to get an unlock code using the old method and it was accepted.
The strange thing is I get varied levels of signal & GPRS depending on which networks sim I use.
Question for W4XY: If I have generated an unlocking code and my XDAII accepted it, should my XDAII now be sim unlocked for all networks or is it possible that its only unlocked for some?
:?
Failed unlock
Tried both with sim in and sim out, same failure both times.
Performing magic
magic failed
Rom: 1.03.00 USA
Date: 09/24/03
Radio: 1.05.12
Proto: 1337.12
Microsoft: 4.20.1080 (Build 13100)
suitstusir said:
The strange thing is I get varied levels of signal & GPRS depending on which networks sim I use.
Click to expand...
Click to collapse
Well this does not sound so strange. I have different performance with different networks too. Depends on their quality, antenna placement etc etc
Question for W4XY: If I have generated an unlocking code and my XDAII accepted it, should my XDAII now be sim unlocked for all networks or is it possible that its only unlocked for some?
:?
Click to expand...
Click to collapse
It should be unlocked for all. A phone can be locked to multiple networks, but once it is unlocked for a network that was previously locked, it should be unlocked for all.
Please at least give your radio version from Start -> Settings -> System -> Device information so we can figure out what works and what doesn't. It could be the older 1.05.x radios behave differently.
Although I am a happy bunny now, as the bootloader method worked for me, for completeness here is the info from my O2 XDA II. The new method failed on this device reporting magic failed.
ROM version: 1.03.00 USA
ROM date: 09/24/03
Radio version: 1.05.12
Protocol version: 1337.12
This device was purchased on 11/mar/2004
Surely this is not an old radio.
Regards
xda2unlock
failed to do magic
what can i do now, i tried the bootloader way, and direct from pc.
xdaII4mick said:
what can i do now, i tried the bootloader way, and direct from pc.
Click to expand...
Click to collapse
The bootloader way should work. It should give you a unlock code. Unless you have Radio version 1.10.x.
PS:
From now on I won't respond to problem reports anymore that do not contain the radio version in their message.
It should be unlocked for all. A phone can be locked to multiple networks, but once it is unlocked for a network that was previously locked, it should be unlocked for all.
Please at least give your radio version from Start -> Settings -> System -> Device information so we can figure out what works and what doesn't. It could be the older 1.05.x radios behave differently.
Click to expand...
Click to collapse
Sorry I keep forgetting to post radio version etc.
I thought it was appearing automatically because I entered the information in my profile. Ooops!
ROM Version: 1.03.00 USA
ROM Date: 09/24/03
Radio version: 1.05.12
Protocol version: 1337.12
Q. What differences would a user notice between the different radio versions? are some better than others?
Q. What differences would a user notice between the different radio versions? are some better than others?
Click to expand...
Click to collapse
To be honest, I'm not sure on what the differences are precisely. I think the 1.10.x is definetly an update to improve as it also specifically blocks the extraction of the unlock code.
I uploaded a new version of xda2unlock above. Version 2.1 should provide some more error information. Please report what it sais.
i just try the new version n here is my report with the new verson that W4XY just posted:
Magic failed
Err 11 ....
and here is my details
My Rom version is 1.03.00 USA
Rom date 09/24/03
Radio version 1.05.12
Protocol version 1337.12
Plz check it out with Error 11...
sid said:
Magic failed
Err 11 ....
Click to expand...
Click to collapse
Please try and be precise as possible. I suppose it read something like:
Read: 11, Error
I know it can contain weird characters, but at least try. Never assume details don't matter.
I dumped this to a 128mb SD card, is there a way this can be analyzed to see what changes there are?
Changes are already known. HTC have changed the stack addresses used by BL, so that the stack is not overwritten after ROM updates.
Previously in some cases you had to do a soft reset to boot a device after flashing, and sometimes you had problems entering bootloader.
That's all. Nothing important.
And differences between 1.x and 2.x are also known. 1.xx (and 0.xx) work with M-systems G3 chip, 2.xx - with G4. You'll get a brick if you'd flash a wrong version.
mamaich said:
Changes are already known. HTC have changed the stack addresses used by BL, so that the stack is not overwritten after ROM updates.
Previously in some cases you had to do a soft reset to boot a device after flashing, and sometimes you had problems entering bootloader.
That's all. Nothing important.
And differences between 1.x and 2.x are also known. 1.xx (and 0.xx) work with M-systems G3 chip, 2.xx - with G4. You'll get a brick if you'd flash a wrong version.
Click to expand...
Click to collapse
ah ok, i asked around and no-one seemed to know , i must have a g4 version then, any major differences then? i know for wizard and prophet etc it has a big impact, forgive me if these questions are silly, ive not had a universal long, hence the new version.
mamaich said:
Changes are already known. HTC have changed the stack addresses used by BL, so that the stack is not overwritten after ROM updates.
Previously in some cases you had to do a soft reset to boot a device after flashing, and sometimes you had problems entering bootloader.
That's all. Nothing important.
And differences between 1.x and 2.x are also known. 1.xx (and 0.xx) work with M-systems G3 chip, 2.xx - with G4. You'll get a brick if you'd flash a wrong version.
Click to expand...
Click to collapse
Hello Mamaich,
Is it mean that, I've to be sure (about chip) before updating to the 2.x version or it should destroy my PPC and I suppose there is no way to make it live once it's bricked!!!
mamaich said:
And differences between 1.x and 2.x are also known. 1.xx (and 0.xx) work with M-systems G3 chip, 2.xx - with G4. You'll get a brick if you'd flash a wrong version.
Click to expand...
Click to collapse
How to find out, which chip that you have in your UNI ?
Thanks
JDD
if you have bootloader 0.xx or 1.xx atm then you have g3, if it is 2.xx then g4. they cant be interchanged.
Midget_1990 said:
if you have bootloader 0.xx or 1.xx atm then you have g3, if it is 2.xx then g4. they cant be interchanged.
Click to expand...
Click to collapse
Mine is v1.01.....Is it safe if I upgrade it to v2.XX ?
I mean, whaf if chip inside my UNI is not compatible with v2.XX ?
Thanks
H
NO, if you currently have a bootloader begining with 1 then you can only use versions beginning with 1.
Midget_1990 said:
if you have bootloader 0.xx or 1.xx atm then you have g3, if it is 2.xx then g4. they cant be interchanged.
Click to expand...
Click to collapse
I dont understand could you elbaorate? Are you talking about the ROM version?
bootloader is the equivalent to the BIOS in an x86-architecture PC.
rom is the equivalent of the operating system (windows xp for example)
you have a bootloader starting with 1 so the highest you can safely go at the moment is 1.01 - if you go 2 then your device will never work again.
r3bel said:
bootloader is the equivalent to the BIOS in an x86-architecture PC.
rom is the equivalent of the operating system (windows xp for example)
you have a bootloader starting with 1 so the highest you can safely go at the moment is 1.01 - if you go 2 then your device will never work again.
Click to expand...
Click to collapse
actualy it's 1.2 but nvm
Midget_1990 said:
if you have bootloader 0.xx or 1.xx atm then you have g3, if it is 2.xx then g4. they cant be interchanged.
Click to expand...
Click to collapse
I have bootloader 2.01 and chs WM5 on my Xda Exec which was bought last month in China. I tried triple to upgade the ROM using O2 Exec ROM version 1.13.82 WWE found on this site, but failed.
Other versions of ROM are fine. I wonder it is because of the bootloader 2.01 on my Universal.
No, it will not be causing the problem, 2.01 is compatible with all ROM atm.
Is your device CID unlocked?
Hi All,
I've got a legit version of TomTom for my Artemis, and I'm running Meschle's excellent 3.1 ROM. However, when he comes out with 4.1 it's going on my phone - but I suspect it'll change the device ID, which'll break TomTom, and which is going to be hard to explain to the TomTom support people - I think they allow 2 changes and that's it.
Is there a way around this? Can I manually set and retain the device ID so my install of TomTom works?
Ric
Which Device ID are you talking about? I would suspect that the TomTom Software is locked to a device ID thats either the IMEI Number or a hardware generated Number, depending on the Components built in this device. I think changing the OS will not change this Device Number, but maybe you can just contact the TomTom Support, i'm sure they can help.
I've flashed my artemis several times and have been able to re-install TomTom on each occasion with no problem
tajw said:
I've flashed my artemis several times and have been able to re-install TomTom on each occasion with no problem
Click to expand...
Click to collapse
Same here.. Just flash and install!
good to know, ta
prodinho said:
Same here.. Just flash and install!
Click to expand...
Click to collapse
anxiously awaiting 4.01...
PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.
I've tried many unofficial ROMs, but still getting the same message!!!
And when I tried to use the official ROM, the upgrade stopped on 11%!!??
To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.
FirasKB said:
PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.
I've tried many unofficial ROMs, but still getting the same message!!!
And when I tried to use the official ROM, the upgrade stopped on 11%!!??
To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.
Click to expand...
Click to collapse
What "official" ROM? You've given absolutely NO info regarding anything friend...
Myself, I'd click the green link in my signature... but that's me
My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!
Kindly, advice if you have any solution or ask for a specific info.
FirasKB said:
My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!
Kindly, advice if you have any solution or ask for a specific info.
Click to expand...
Click to collapse
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..
Dr Puttingham said:
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..
Click to expand...
Click to collapse
Fine,,,
Device: at&t 8525
ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).
The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.
So, the device still having no GSM.
Thank You....
FirasKB,
Most roms on her DO NOT come with a radio included. Usually only the manufacturer roms do.
There are 2 things you need to do:
- Consult the MrVanx guides which will help you understand what you are doing (google search for this).
- go to the wiki in this forum and search for a radio rom to upload.
In summary, reflash, say, Scahps rom then flash a radio rom from the wiki (I suggest radio 1.47, which is pretty reliable).
Hope this helps.
WB
FirasKB said:
Fine,,,
Device: at&t 8525
ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).
The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.
So, the device still having no GSM.
Thank You....
Click to expand...
Click to collapse
Ahhh, a little info.
First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.
Reboot the pc with the PDA disconnected.
(Oh, make sure that you have ActiveSync 4.5 insttalled of course)
Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)
Connect the PDA to the USB cable and run the RUU_Inside.exe file.
wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.
I can't guarantee that this will work but it IS your best shot friend.
Good luck!
Dr Puttingham said:
Ahhh, a little info.
First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.
Reboot the pc with the PDA disconnected.
(Oh, make sure that you have ActiveSync 4.5 insttalled of course)
Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)
Connect the PDA to the USB cable and run the RUU_Inside.exe file.
wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.
I can't guarantee that this will work but it IS your best shot friend.
Good luck!
Click to expand...
Click to collapse
Thanks to your support friends,,
I've done as you mentioned, but the upgrade process stopped on 11% again and couldn't complete!!?? (the message ERROR [262]: UPDATE ERROR appeared on my P.C)!!??
Kindly, advice...
I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)
Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.
WB
Stuck.... completely stuck
My fiances phone is stuck in the tri color bootloader screen. I am in the US and i have tried everything from flashing the original RUU to a hard reset and everthing, but nothing seems to work. the IPL is 4. 10. 0002 and the SPL is 4. 10. 0000. Can someone please help me. I know there has to be a way to fix this.
I had the same problem. After trying to fix it myself for about a week I gave up and sent it to AT&T Repair center. Got it back functional.
I haven't tried the Himalaya ROM method, though.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=372895
Good luck!
wacky.banana said:
I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)
Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.
WB
Click to expand...
Click to collapse
Thanks again to your support,
The problem happened when I tried to unlock the device to upgrade it (it was fine befor), I don't know whether it was already locked or not, but usualy when I buy any Pocket P.C I'm preparing to unlock it first (I've done that many times on HERMES before, but this is the first time I'm facing such problem!!). So, while unlocking the device it's stucked on the tri color screen.
I've done many things after that to solve the problem (updating the hard SPL to v2.10 successfully, flashing many ROMs -not including Radio- successfully).
So, I can flash any ROM now but it must be without Radio, otherwise the flashing process will stuck on 11%.
try reading the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.
FirasKB,
What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.
WB
FirasKB said:
More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.
Click to expand...
Click to collapse
Schap´s Rom has NO Radio. Flash this one BUT u must have HardSPL
http://forum.xda-developers.com/showthread.php?t=348435&highlight=Radio
wacky.banana said:
FirasKB,
What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.
WB
Click to expand...
Click to collapse
wacky.banana,
As I wrote above, my problem still not solved and my device still running with (No GSM).
I've done the following:
- Updating the ROM (O.S only as the device not accepting any Radio ROM)
- Updating the SPL to Version 7.
- Trying to update the radio (separately) but I didn't success??!!
It seems there is no solution to fix this problem???!!!
Abo Forat said:
Schap´s Rom has NO Radio. Flash this one BUT u must have HardSPL
http://forum.xda-developers.com/showthread.php?t=348435&highlight=Radio
Click to expand...
Click to collapse
No way, I tried it but my device can't accept any Radio version.
FirasKB said:
wacky.banana,
As I wrote above, my problem still not solved and my device still running with (No GSM).
I've done the following:
- Updating the ROM (O.S only as the device not accepting any Radio ROM)
- Updating the SPL to Version 7.
- Trying to update the radio (separately) but I didn't success??!!
It seems there is no solution to fix this problem???!!!
Click to expand...
Click to collapse
Frisk,
Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://forum.xda-developers.com/archive/index.php/t-298516.html
Cheers
WB
wacky.banana said:
Frisk,
Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://forum.xda-developers.com/archive/index.php/t-298516.html
Cheers
WB
Click to expand...
Click to collapse
Unfortunately, but that's also didn't help, because the main problem now is how to install the Radio on the device??!!
The device is not accepting the Radio installation at all, NO WAY....
Hey guys,
Ive got a question. I cant find an answer as to how these differences in baseband version would affect my day to day phone usage. The reason is because i really want to go back to using AllianceRom 1.0 which has a XXDMA6 baseband and hasnt been updated since. Whats the big difference between DMA6 and DMB6 anyways?
Baseband? That's just the base rom. Well xxdmb6 seems to have fixed the battery issues for many users.
this is XXXDDDAAA
Isn't the baseband just a firmware controlling the radios. I mean that's my understanding. But that's not my question. I just want to know if these updates are region specific or what exactly has been changed to improve this battery life? I mean I honestly didn't notice much of a difference since I was using DMA6 and the latest DMB6
Sent from my GT-N7100 using xda premium
Baseband and the firmware itself are different. Baseband is a part of modem. It is just related to sending the signal to boot up the phone and calls.
Also dmb6 had a new change list. So I think there could be some more under the hood.
this is XXXDDDAAA
UtkarshGupta said:
Baseband and the firmware itself are different. Baseband is a part of modem. It is just related to sending the signal to boot up the phone and calls.
Also dmb6 had a new change list. So I think there could be some more under the hood.
this is XXXDDDAAA
Click to expand...
Click to collapse
Technically speaking a baseband contains the radio firmware that controls basic low level functions such as gps, network and wifi..and that is what I meant when I said it's just a firmware. But it doesn't make sense when you say it sends signal to boot the phone, how is that?
Sent from my GT-N7100 using xda premium
bushako said:
Technically speaking a baseband contains the radio firmware that controls basic low level functions such as gps, network and wifi..and that is what I meant when I said it's just a firmware. But it doesn't make sense when you say it sends signal to boot the phone, how is that?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Well the radio or baseband or modem sends the signal to boot when you press power button.
Atleast that was what I read at XDA university.
this is XXXDDDAAA
UtkarshGupta said:
Well the radio or baseband or modem sends the signal to boot when you press power button.
Atleast that was what I read at XDA university.
this is XXXDDDAAA
Click to expand...
Click to collapse
Baseband is part of SW that controls radios of device like phone and network, wifi, bluetooth etc
When you press power button, the bootloader send signal to boot device. and once device boots, kernel takes control.
the bootloader is code that is executed before any Operating System starts to run. Bootloaders basically package the instructions to boot operating system kernel. So pressing power button, bootloader gets activate and direct the device to load OS.
You can start device even absence of baseband, as many cases we can see unknown baseband though they have normal booting device but without network. So baseband have no role in booting device.
dr.ketan said:
Baseband is part of SW that controls radios of device like phone and network, wifi, bluetooth etc
When you press power button, the bootloader send signal to boot device. and once device boots, kernel takes control.
the bootloader is code that is executed before any Operating System starts to run. Bootloaders basically package the instructions to boot operating system kernel. So pressing power button, bootloader gets activate and direct the device to load OS.
You can start device even absence of baseband, as many cases we can see unknown baseband though they have normal booting device but without network. So baseband have no role in booting device.
Click to expand...
Click to collapse
I would assume he meant when he mentioned it boots the device he meant to say the baseband wakes the device whenever someone calls or a message is received. That would make sense.
So its safe to assume that the bootloader is like a BIOS, firmware is like the OS, and the Baseband is just the drivers between the OS and the Radio related hardware such as the wifi and bluetooth.
bushako said:
I would assume he meant
Click to expand...
Click to collapse
May be, but pressing power have nothing to do with baseband thats i want to say.
bushako said:
So its safe to assume that the bootloader is like a BIOS, firmware is like the OS, and the Baseband is just the drivers between the OS and the Radio related hardware such as the wifi and bluetooth.
Click to expand...
Click to collapse
Just difference is in Android firmware itself contains bootloader sometimes.
While on PC it's on MoBo isn't? b'coz without even HDD we can bootup to BIOS.
But yes it is same what you said.
Okay forget to answer original question
I believe baseband is best which comes packed with your ROM unless you are having any network related issue.
In such case i recommend to flash baseband one from latest for your region/carrier. b'coz baseband contains drivers for network and radio and may be they have best one for your network.