[BASEBAND PATCHES] for Baseband -36 and -64 - Xperia Arc Android Development

Hello!
Many users have reported excessive battery drain and/or/due to intermittent loss of signal using the latest basebands.
I have been trying different basebands myself and found that baseband -36 gives the best combination in battery life and signal reception.
However, there are libraries in /system/lib that are related to baseband and, in my trials,
it seems that they made a difference in how the baseband was functioning in a different firmware than .368 (in which it initially shipped).
In other words, I've simply come to the conclusion that each baseband needs its appropriate libraries.
UPDATE for people asking which is the "best" baseband:
Bin4ry said:
@All asking for which baseband fits best:
Please please DON'T start flashing basebands without thinking about now.
Normally ALWAYS use the baseband which comes with the ROM! For example SE always has the corresponding baseband included. This baseband fits the android libs it comes with.
On custom Roms please read what the developer of the customRom telly you. If he/she has developed the Rom for specific baseband libs.
All other things like baseband patches are tested and developed by other developers which know what they are doing. So if you use such a patch ALWAYS read the manual and the requirements. Because it CAN happen that it is NOT possible to use a GB baseband on a ICS rom and vice versa. The is a little more than "just" libs and firmware. Also the java part framework/base/com/java/internal/telephony....
has to fit the baseband (SE is very special here).
So i hope now you all understand. Please please please leave the decision which baseband is best and which is working to the devs who know what they are doing!!!!!! Don't come here and tell "i tried baeband xxxxx now my phone randomly disconnects data/voice/..."
Thanks
Click to expand...
Click to collapse
And now, here are the patches flashable in CMW recovery:
DOWNLOAD THE PATCH for -36
(It will NOT change your baseband!!!
It will only flash baseband's -36 libraries in your system.)
DOWNLOAD THE PATCH for -64
(It will NOT change your baseband!!!
It will only flash baseband's -64 libraries in your system.)
INSTRUCTIONS: Of course you need to be on STOCK SE ROM, on baseband -36 or -64* and on any other firmware other than .368 and .062.
Place the patch zip in your sdcard, boot into CMW, flash it, reboot and enjoy!
Works for Arc and Arc S. Tried it on .042 and .058 ROMs.
Even better instructions, by DooMLoRD:
DooMLoRD said:
step 1:
flash baseband FTF via flashtool
step 2:
boot device and go into recovery
step 3:
while in recovery mount USB storage and connect device to PC
step 4:
copy the patch flashable (update.zip) to sdcard
step 5:
unmount sdcard via PC & also via recovery menu
step 6:
flash this patch (update.zip) via recovery
step 7:
reboot and enjoy!!
u can skip step 3 to 5 if u already have the patch update.zip on sdcard
Click to expand...
Click to collapse
* Here is baseband -36, flashable ftf for FlashTool.
DOWNLOAD baseband -36 (thanks to erwin929)
If this file doesn't work for you, kindly find baseband -36 elsewhere.
* Here is baseband -64, flashable ftf for FlashTool.
DOWNLOAD baseband -64
If this file doesn't work for you, kindly find baseband -64 elsewhere.
NOTE: Test the new libraries for at least 1 day before reporting,
in order to have more thorough proof of the improvement or the lack of it for that matter.
Simply booting after flashing the patch and seeing less signal bars doesn't mean anything by itself.
After running your phone for several hours on battery you can see the battery graph,
in the About Phone section, and check for signal strength, signal loss, etc.
Mirros For Baseband Files:
caqo71 said:
BB 36 http://www.mediafire.com/?kxkrtdtzeyme47w
BB 64 http://www.mediafire.com/?ah93az9kd226cli
BB 70 http://www.mediafire.com/?56nb4bpz5ncfv5l
BB 72 http://www.mediafire.com/?d0qp936etx9cmn7
Click to expand...
Click to collapse
Cheers!

Ftf file doesn't work with flashtool.
I tested to flash the zip file with recovery, i'm still in .58 baseband.

Azev said:
Ftf file doesn't work with flashtool.
Click to expand...
Click to collapse
Works for me!
Make sure you use the latest version of FlashTool.

When I am going to flash the TFT file, will I lose any data? I am on stock rom.42 and on baseband -56.
Sent from my rooted LT15i using XDA App

DeeDeeKay79 said:
When I am going to flash the TFT file, will I lose any data? I am on stock rom.42 and on baseband -56.
Sent from my rooted LT15i using XDA App
Click to expand...
Click to collapse
No, no data loss whatsoever.
Azev said:
Ftf file doesn't work with flashtool.
I tested to flash the zip file with recovery, i'm still in .58 baseband.
Click to expand...
Click to collapse
Yes, of course you are, because you just flashed the patch.
The ftf file is not an either/or situation, you want to change baseband, you flash it.
And if you are on baseband -36, you need to apply the patch.

any chance it will work on th eplay

faisaldante said:
any chance it will work on th eplay
Click to expand...
Click to collapse
Most probably yes, but I have no way to be sure.
You can make a backup and try it!

so we just have to flash the ftf using the link above?
is that all the steps needed?

iridaki said:
Hello!
Many users have reported excessive battery drain and/or/due to intermittent loss of signal using the latest basebands.
I have been trying different basebands myself and found that baseband -36 gives the best combination in battery life and signal reception.
However, there are libraries in /system/lib that are related to baseband and, in my trials,
it seems that they made a difference in how the baseband was functioning in a different firmware than .368 (in which it initially shipped).
In other words, I've simply come to the conclusion that each baseband needs its appropriate libraries.
So, without further ado, here is the patch flashable in CMW recovery:
DOWNLOAD
INSTRUCTIONS: Of course you need to be on baseband -36 *** and on any other firmware other than .368.
Place in your sdcard, boot into CMW, flash it, reboot and enjoy!
Works for Arc and Arc S. Tried it on .042 and .058 ROMs but it should work on any stock ROM.
*** Here is baseband -36, flashable ftf for FlashTool.
DOWNLOAD
PS: I am uploading the ftf for the baseband itself too, but it's going to take a while with my speeds here. Stay tuned!
Cheers!
Click to expand...
Click to collapse
I've been using the baseband -36 on my .42 firmware for at least a month without any issues!! (I just took the .368 firmware and flashed the baseband only using the flashtool which stated to supports that option) So what issues are expected if the libraries are missing?

prathaban said:
I've been using the baseband -36 on my .42 firmware for at least a month without any issues!! (I just took the .368 firmware and flashed the baseband only using the flashtool which stated to supports that option) So what issues are expected if the libraries are missing?
Click to expand...
Click to collapse
Yea I been flashing different basebands since last week with flashtool trying out different combos but mostly with .42 build. Right now I'm on doomkernel with -58 baseband and battery is way better than it was with stock .42 -56 baseband and with no issues at all
Sent from my R800a using XDA App

When i select the .ftf in flashtool, it doesn't do anything, doesn't prepare it for flashing or anything???
Anyone else had this problem?

for a second i thought this was cobrato posting this (when i read the thread title )
great work Iris!

my baseband is 59 will notice the difference in battery if I change it?
Enviado desde mi LT18i usando Tapatalk

Im confused by the tutorial. Basically im on 56 baseband with .42 firmware. So how do I flash this? Cause on the instructions it says I need to have 36 baseband already :S
---------- Post added at 10:40 AM ---------- Previous post was at 10:13 AM ----------
I dont think this works. I tried flashing the tft and all it does is says device connected and tft select then it doesnt say if its flashing it or anything. After waiting it just says device disconnected.

step 1:
flash baseband FTF via flashtool
step 2:
boot device and go into recovery
step 3:
while in recovery mount USB storage and connect device to PC
step 4:
copy the patch flashable (update.zip) to sdcard
step 5:
unmount sdcard via PC & also via recovery menu
step 6:
flash this patch (update.zip) via recovery
step 7:
reboot and enjoy!!
u can skip step 3 to 5 if u already have the patch update.zip on sdcard

same problem for me also, just sits there and does nothing with latest flashtool with this ftf baseband.

Crocodile1973 said:
same problem for me also, just sits there and does nothing with latest flashtool with this ftf baseband.
Click to expand...
Click to collapse
Did you get .ftf file? If you got .zip file like i did, renamed to
.ftf

CMW via flat when I finished and reboot and check the setting but it is still 56, I do not understand what I do wrong, sr my english is not good

Guys, let me make this even more clear to you (I'll at least try):
1. This thread is mainly about the PATCH.
The said patch is a .zip file flashable with CMW recovery.
It will NOT change your baseband.
It will flash baseband's -36 libraries in your system.
2. The ftf I posted is baseband -36.
It will change your baseband to -36 after you flash it with FlashTool.
It works for me.
If it doesn't work for you, find baseband -36 elsewhere.
3. If you feel that running baseband -36 on a different firmware libs gives you stable results, just ignore this thread altogether.
I am only trying to help, but I swear I'm starting to regret it.

Nice work mate.
Sent from my LT18i

Related

[Q] Stock apps/ROM reset

I just got a rooted Optimus 2x. It has the stock ROM. The previous owner had removed many stock apps including Google Talk, music player which I would want to reinstall but I can't reach him now.
It has some backups because of Root Uninstaller, but not every app is there.
I found some links for all Optimus 2x stock apps but they aren't working anyome.
Is there any way I can reinstall these apps? Or do I have to reflash the stock firmware or something?
You should reflash
Sent from my Optimus 2X using XDA
So before I reflash can anyone confirm if this is what I should be doing?
Download my firmware from here: http://forum.xda-developers.com/showthread.php?t=1035041 (Hungarian one)
Download Smartflash and Baseband (0725-V20q-Baseband) from here: http://forum.xda-developers.com/showthread.php?t=1658047 And follow the instructions. But also select the firmware file too.
The problem is the link for my baseband is down and I can't post in the thread.
Also after I flash it, I will have to root it again, right?
After u flash the stock firmware, the baseband will be flashed as well. So unless the stock baseband is not working with ur network u dun have to flash the baseband again,
Yes, u will have to root again
Kupo28 said:
The problem is the link for my baseband is down and I can't post in the thread.
Also after I flash it, I will have to root it again, right?
Click to expand...
Click to collapse
Follow this and ull get the link to download original+latest stock...
Replaces the x's with your IMEI number: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=XXXXXXXXXXXXXXX&model=LGP990
In the text that follows, you'll be given a link to a .kdz file which is the latests version for your phone. you can get completely back to stock.
bliizzz said:
Follow this and ull get the link to download original+latest stock...
Replaces the x's with your IMEI number: link
In the text that follows, you'll be given a link to a .kdz file which is the latests version for your phone. you can get completely back to stock.
Click to expand...
Click to collapse
Thanks, it worked with the kdz file, it's now back with 46 system apps instead of 23.

[Q] More details about flashing

Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
SCC2002 said:
Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
Click to expand...
Click to collapse
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
SCC2002 said:
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
Click to expand...
Click to collapse
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
gregbradley said:
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
Click to expand...
Click to collapse
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
Click to expand...
Click to collapse
Well, I was thinking that these questions are better asked on a separate thread then. Anyway, thx a lot for compiling the All In One thread. It's very useful. More details can be added though. =)
SCC2002 said:
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Click to expand...
Click to collapse
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
gregbradley said:
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
Click to expand...
Click to collapse
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
SCC2002 said:
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Click to expand...
Click to collapse
Hard brick means your phone is properly FUBAR'd
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
Maybe, try it and see. But i think a whole flash of the firmware is needed.
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
gregbradley said:
Hard brick means your phone is properly FUBAR'd
Maybe, try it and see. But i think a whole flash of the firmware is needed.
Click to expand...
Click to collapse
Spectre51 said:
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
Click to expand...
Click to collapse
Happy New Year, guys! Thx for the answer. I've tried just flashing the kernel. Doesn't work. Succeeded rooting after flashing the whole firmware. =)
Anyway, now I'm stuck in the process of upgrading the firmware. I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/showthread.php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/showthread.php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Spectre51 said:
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Click to expand...
Click to collapse
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
SCC2002 said:
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
Click to expand...
Click to collapse
I kept the other file in the original location. Not sure about any Mac address issue. Worked fine for my device. Not sure about the way you use to build the rom. I just use the android kitchen since its pretty quick and easy.
Sent from my Sony Xperia™ TL

[BASEBANDS][TUTORIAL] Freedom! Choose your baseband.

Up until now, this topic has largely remained in the dark. Not anymore however!
I have figured out how to flash different basebands onto our phone. Unfortunately, at the moment, doing so requires a "factory reset" of sorts, and you will have to re-flash the recovery image and restore your nandroid backup afterwards.
I look forward to finding a better way, but this will suffice, I think, if you, like me, have had terrible GPS problems.
The main use for replacing the baseband is bad GPS signal. Best results have been reported using the ICS basebands for people with trouble getting a signal / finding satellites.
!!DISCLAIMER!!
This is probably not for the uninitiated. It will most likely be fine, but I give no guarantees whatsoever. I paid attention when putting this together, but the only baseband I have tested myself is the V10H - EUR, that is currently running on my phone.
If you end up without IMEI, unable to make phone calls, your phone doesn't boot, I am not responsible and might not be able to help you.
I HIGHLY recommend you have your bootloader unlocked before you try this. I don't know if it will work with a locked one, it might, but I wouldn't try it.
However if you pay attention, are careful and follow instructions, you should be fine.
Pre-requesites:
Hex Editor (I use HxD in windows - http://mh-nexus.de/en/hxd/)
LG Flash Tool with working drivers (please see this great tutorial by SnXo about it: http://forum.xda-developers.com/showthread.php?t=2179126)
Model firmware (See below)
Baseband you mean to flash (See below)
Tutorial:
Download and extract the "Model firmware" and the baseband you mean to flash and place them under a folder named Baseband
Open the Hex Editor
With the Hex Editor, open the baseband file.
You will see a bunch of numbers and letters, nevermind them. Just make sure the first four blocks of the file are numbered 30 12 95 78, they should be, if not STOP and use another baseband. Also warn me so I can correct it,
Now that you have all selected, right click, select all and copy.
DO NOT CLOSE THE HEX EDITOR.
Now open the model firmware file (it ends in .dz)
Open the search dialog box. You want to search for "INSERT" and datatype "text string" - should be in a drop box somewhere.
Now you will see on the left a bunch of Fs with INSERT FLS HERE in the middle. Select everything between and INCLUDING the first and last F on the block. (the first and last block should be addressed 2484 and 24D3, respectively).
Right-click and paste
If it warns you the file size will change, say you're okay with it.
Now save the file and call it "Flash.dz"
MAKE SURE YOUR BATTERY IS WELL ABOVE 50% BEFORE PROCEDING!!
Now flash the .dz file you just created with the X3_v0.0.7.4.dll using the LG Flash Tool as per instructions here: http://forum.xda-developers.com/showthread.php?t=2179126
Congratulations! You are now running the baseband of your choice. Let it boot, root it, flash the recovery, restore your nandroid and presto!
Tools:
Model firmware: https://mega.co.nz/#!kQMG1CSB!GFvbEwDi1ByO2_1B_JRdOhX4pwIb8CVU2s_QUrZ8CmY
ICS Basebands:
V10A - EUR (Europe)
V10B - 262-000 (Europe , Portugal)
V10B - 525-01 (Singapore)
V10B - 714 (Panama)
V10B - AMX (Puerto Rico)
V10C - HKG (Hong Kong)
V10D - EUR (Europe)
V10E - ESA (Thailand)
V10E - TMO (Germany\T-Mobile)
V10F - EUR (Europe)
V10H - EUR (Europe)
JB Basebands:
20A-232-01 (Austria)
20C-232-10 (Austria)
20A-262-000 (UK , Portugal)
20A-525-05 (Singapore)
20A-ESA (Thailand)
20A-EUR (Europe)
20B-EUR (Europe)
20B-466-92 (Taiwan)
20B-BUM (China)
20B-CIS (CIS)
20B-HKG (Hong Kong)
20C-AME (Nigeria)
20D-AME (Turkey)
!!ALTERNATE METHOD FOR JB BASEBANDS!!
The tutorial above is the only method available to flash ICS basebands at the moment. To flash JB basebands, however, if you prefer, you can grab the full roms from here (the corresponding countries are between parentesis above):
http://lg-phone-firmware.com/index.php?id_mod=15
and flash the .kdz file with LG PC Suite hacker or KDZ flasher. You can find more information about that here:
http://forum.xda-developers.com/showthread.php?t=2134192
http://forum.xda-developers.com/showthread.php?t=2069723
Then just proceed to root and flash your nandroid backup as usual, The baseband will be kept.
Thanks to Flying_Bear for reminding me to include this method!
Commentary and what to expect:
Using the 10H baseband did wonders for my GPS. It might do for you to if you had great GPS on ICS but not on JB. Different region basebands might make a difference too, I'm not sure how they differ from each other.
I am not a developer, just a user like you who had a problem and decided to tackle it in the ways he knew. If you want to help or have any relevant input, please don't be shy, I will listen and be greatful for it.
You might have noticed there is a short list on the ICS baseband side. That is because there are many more left to add but I didn't want to delay making this guide any longer.
Also, I will try to make an executable to automate this byte replacing process, but make no promisses. My coding skills are limited and so is my time - if you'd like to do it, feel free to do so. I'll put your work here and give you full credit!
If you're an advanced user or developer, wondering about RILs and whatnot, don't change the RIL. I'm not sure it'll work for every single baseband here, but for the 10H - EUR, the 20A - EUR and the 20B - HKG it works fine. Changing the RIL breaks the phone and you have to restore a backup.
The basebands were extracted from .dz file of stock firmwares downloaded from the LG website. The name is that which is in the .dz file after extraction from the .kdz and the basebands listed differ in md5 checksum from each other. How they are different, I have no idea.
I'll put a FAQ up with the most asked questions, if there are any.
Cheers!
Reserved 1
Reserved 2
thanks for this, i have pretty crappy gps on any of 20x variations, so i'll try ICS baseband either tonight or tomorrow. thanks again!
Will flashing a different baseband resolve baseband wakelock which is a big battery drainer on my LG?
also, a tip - you dont need to use lgflashtool to change basebands between 20x versions - you can flash kdz trough lg pc suite hacker or kdz flasher, then restore your nandroid backup. the method described here is useful to get 10x basebands, since you cant just flash kdz to rollback to ics.
brunek said:
Will flashing a different baseband resolve baseband wakelock which is a big battery drainer on my LG?
Click to expand...
Click to collapse
I'm not sure, give it a shot. But I believe that is a different issue that is kernel related.
Flying_Bear said:
also, a tip - you dont need to use lgflashtool to change basebands between 20x versions - you can flash kdz trough lg pc suite hacker or kdz flasher, then restore your nandroid backup. the method described here is useful to get 10x basebands, since you cant just flash kdz to rollback to ics.
Click to expand...
Click to collapse
Thanks for the tip! Actually, I am aware of that. It's just that I really like LGFlashTool better. Also, thought it would be a good idea to systematize the different basebands availible under one flashing method, to be less confusing, and to save the good people downloading some bandwith (5 mbs baseband vs. 500 mb full rom). Also, it's a complex method, but at least it's just one!
Newbleeto said:
Thanks for the tip! Actually, I am aware of that. It's just that I really like LGFlashTool better. Also, thought it would be a good idea to systematize the different basebands availible under one flashing method, to be less confusing, and to save the good people downloading some bandwith (5 mbs baseband vs. 500 mb full rom). Also, it's a complex method, but at least it's just one!
Click to expand...
Click to collapse
^^
for me, lgflashtool seems like a hit and miss, i had some issues gettting it to work right now. flashing the modified .dz with 10h bb atm. i agree it's better to have unified method, the kdz one can stay as an alternative to people who have bunch of kdzs lying around (like me, had 20a & 20b leaks, 20a eu, 20a esa & 20b hk, tried all of their basebands and gps locator was slower than what i remember on ics) or dont feel comfortable working with flashtool, or have issues with it etc.
edit:
flashed modified .dz, no issues as of yet, gonna restore nandroid backup now (first root & recovery setup, /yawn), and we'll see how it goes
Flying_Bear said:
^^
for me, lgflashtool seems like a hit and miss, i had some issues gettting it to work right now. flashing the modified .dz with 10h bb atm. i agree it's better to have unified method, the kdz one can stay as an alternative to people who have bunch of kdzs lying around (like me, had 20a & 20b leaks, 20a eu, 20a esa & 20b hk, tried all of their basebands and gps locator was slower than what i remember on ics) or dont feel comfortable working with flashtool, or have issues with it etc.
edit:
flashed modified .dz, no issues as of yet, gonna restore nandroid backup now (first root & recovery setup, /yawn), and we'll see how it goes
Click to expand...
Click to collapse
Let me know if it works for you! I had some luck with the HK 20A baseband, but the 10H really fixed it for me. Also, added your method to the original post
A proof it works I'll test gps tomorrow to see if i have improvements. Thank you!
edit:
actually, just went to my windows to test it lol, got a signal in under than a minute, while it took over 10 on JB baseband. thank you again
Very nice work! Can see that a lot of research went into this.
Will give it a try later.
Did you try to flash only baseband naming it *.fls? Very nice work! Thanks for figuring this out.
Sent from my LG-P880 using xda app-developers app
Well, so which baseband is the best? Anyone could test?
Why is there no way to flash a new baseband like flashing a kernel with flashing in cwm?
brunek said:
Will flashing a different baseband resolve baseband wakelock which is a big battery drainer on my LG?
Click to expand...
Click to collapse
I wonder this too...
I have seen that not everybody has problem with baseband wakelock. In my country,I know people that dont have baseband problems so I thought it might be a thing with baseband version..That would be easy fix,just flash the different basebad and problem solved!
iodak said:
Did you try to flash only baseband naming it *.fls? Very nice work! Thanks for figuring this out.
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately renaming the file .fls won't work, the process will fail, and I know why. The LG Flash Tool needs a proper header to know where to place these files. Removing the other parts of the .dz file and keeping the header won't work, and I really don't know where to find documentation on this. This process is possible for example on the LG Optimus 2X, because there are effective tools to unpackage the .wdb file (contained in the .kdz) into separate parts with the appropriate headers. For the .dz files our phone uses there is no such tool, and the headers between the files show no resemblance. This needs further research!
chrisch91 said:
Why is there no way to flash a new baseband like flashing a kernel with flashing in cwm?
Click to expand...
Click to collapse
Of course this was my first approach, as you will see if you check my thread on general asking for help. To flash something in CWM you need to know what files you are replacing, where they are and what partition they belong to. This is possible for example on the Nexus 7 3G or the HOX. However, on our phone, I was unable to locate the baseband files, and as far as I can tell they do not belong in any partition CWM can write to. This seems to be the way LG phones are designed, as it is the same for the LG Optimus 2X. I might be wrong though, so figure it out if you can
brunek said:
I have seen that not everybody has problem with baseband wakelock. In my country,I know people that dont have baseband problems so I thought it might be a thing with baseband version..That would be easy fix,just flash the different basebad and problem solved!
Click to expand...
Click to collapse
Give it a try man, it's not that hard or time consuming. It might work.
reas0n said:
Well, so which baseband is the best? Anyone could test?
Click to expand...
Click to collapse
I'm living in Portugal and so far have excellent results with the V10H-EUR baseband, both in terms of GPS and 3G signal. So seems to Flying_Bear. But there are so many, who knows which one is the best? The more we try the more we'll know!
Dumb question.
Would flashing a baseband help with my lost IMEI?
My phone died and after recovering to CyanogenMod, and then back to stock, my IMEI has disappeared. I've tried flashing Cyaonogen nightlies but it hasn't worked.
WeeJockMacFeegle said:
Dumb question.
Would flashing a baseband help with my lost IMEI?
My phone died and after recovering to CyanogenMod, and then back to stock, my IMEI has disappeared. I've tried flashing Cyaonogen nightlies but it hasn't worked.
Click to expand...
Click to collapse
I would need more information, but that would seem the effects of a corrupt baseband. You should flash a fresh .dz or .kdz file and see if it fixes it.
Newbleeto said:
I would need more information, but that would seem the effects of a corrupt baseband. You should flash a fresh .dz or .kdz file and see if it fixes it.
Click to expand...
Click to collapse
Have tried flashing both .dz and .kdz files.
One just fails every time at 23s, the other fails every time at WParam = 2010 Iparam = 207

[Q] How do I flash a rom without overwriting the baseband and RIL?

Question is in the title. Have at it!
Tick exclude baseband on flashtool.
argynly son
gregbradley said:
Tick exclude baseband on flashtool.
Click to expand...
Click to collapse
Flashtool only seems to be able to flash FTF files. It won't flash a zip, or the uncompressed files.
sebzag said:
Flashtool only seems to be able to flash FTF files. It won't flash a zip, or the uncompressed files.
Click to expand...
Click to collapse
Yes...
Just flash the .zip in recovery that you want to and if you want to keep a certain baseband or LTE then flash a stock ftf (with the baseband you want) in flashtool and exclude everything EXCEPT baseband. That will then just change the baseband to the one in the ftf and as long as that ftf has the baseband you want then you will be OK.
Baseband and RIL is part of a ROM.
If you want to preserve baseband and RIL from another ROM, change modem files in /system/etc/firmware and /system/lib/libril-qc-qmi-1.so in the ROM zip.
peetr_ said:
Baseband and RIL is part of a ROM.
If you want to preserve baseband and RIL from another ROM, change modem files in /system/etc/firmware and /system/lib/libril-qc-qmi-1.so in the ROM zip.
Click to expand...
Click to collapse
Can firmware files be switched out just that simple, or do I have to edit some kind of config/list of the files so that they are recognized by the flashing mechanism? Is there a way of finding out which stock firmware is absolutely necessary to stay for the device to work optimally?
Also, can the kernel of a locked bootloader phone be updated if the newer kernel is official and unmodified, which is to say it came by official manufacturer means? In my situation, my phone notified me that 9.1.A.1.140 was officially available for my phone which I could not successfully update because CWM Recovery on my phone was an issue for it. After flashing my phone with SEUS to reset it to factory default, it now claims that the version I already had before, 9.1.A.0.489 is now [somehow] the most recent. The only discrepancy is that it is a Rogers phone, but the only FTF I could find for the exact same model is from a Bell phone. They use the exact same hardware, and most likely same baseband (seems to work just fine), but ofcourse comes with a few different vendor apps.
Yes, you can just change those files (I changed whole firmware folder), flash newer radio and newer kernel with flashtool.
But RIL stays almost unchanged in JB versions (if you compare it in editor), so it is probably not necessary to change it.
gregbradley said:
Yes...
Just flash the .zip in recovery that you want to and if you want to keep a certain baseband or LTE then flash a stock ftf (with the baseband you want) in flashtool and exclude everything EXCEPT baseband. That will then just change the baseband to the one in the ftf and as long as that ftf has the baseband you want then you will be OK.
Click to expand...
Click to collapse
When I try to flash the FTF over the ROM I get an error saying there is a SIN header mismatch.
The exact error:
ERR_SEVERITY="MAJOR";ERR_CODE="0019";ERR_DYNAMIC="SIN header verification failed";
Hello wisemen,
On a very related note, I would like to flash just my baseband in recovery from a zip (I've never used the flashtool). Is there a baseband repository for the Xperia T anywhere (LT30p model)? If there is, it seems to have evaded the search engines.
Background:
I'm doing this to fix the broken speakerphone and call echo in CM10.1.3.
Thanks in advance.
zilboris said:
Hello wisemen,
On a very related note, I would like to flash just my baseband in recovery from a zip (I've never used the flashtool). Is there a baseband repository for the Xperia T anywhere (LT30p model)? If there is, it seems to have evaded the search engines.
Background:
I'm doing this to fix the broken speakerphone and call echo in CM10.1.3.
Thanks in advance.
Click to expand...
Click to collapse
No. But if you download a ftf for your phone then you can exclude everything EXCEPT baseband to have the same effect (Ensure you UNTICK all the wipe options as well.)

c6906 baseband files

GUYS! I think I found a way to get the at&t band working on a c6903 ! read this post that someone wrote and I want to try it. I flashed the baseband of many c6906s onto my c6903 and this explains why it doesn't change and it stays the same even when I flash it.
so ifanyone with a c6906 would be so generous to hand over these baseband files, I would greatly appreciate it.
Baseband is contained in /system/etc/firmware. Flashing baseband partitions won't change anything except maybe resetting your current baseband.
If you want to change baseband, you have to take the files from the rom that contains it: modem.* (mdt, b00, b01...bxx), q6.* (mdt, b00, b01...) , tzapps.* and dsps_fluid.* then copy them into your own rom in /system/etc/firmware.
You'll see that by doing that, your firmware version changes.
Flashing the baseband partitions after copying the files could help having a fresh start.

Categories

Resources