This was split off from another thread that was getting off track a bit.
http://forum.xda-developers.com/showthread.php?t=1305077
slycog said:
It's not on a partition that is accessible through nvflash, the radio module itself has it's own internal flash (1GB) and it can only be accessed via the baseband itself... in fastboot there is a serial interface that becomes available that allows you to talk directly to the baseband.
The code that i've written is a basic framework to allow communicating directly with the baseband... right now the only thing it does is issue the basic AT and SWV commands. You would need to implement a FBOOT handler to facilitate a baseband flash.
There isn't really a compelling reason to get it working, those people having issues with the KDZ tool will have the same issues with the tool I've written... the KDZ tool barfs on itself because it's not able to find/mount the serial interface. (in the examples that I've seen the LG drivers simply don't function properly preventing the pc from ever making the interface available)
Aside from all of that, usb serial adapters are buggy in general... you get all kinds of weird timing issues... you can attribute most of the failed updates to this. I myself had a bad flash my first go-round with the LG Updater.
As for the firmware with imei, if it's not available via B2C (which i'm pretty sure it is) then it can be obtained through B2B (this is the commercial tool used internally by the carriers). B2B is how the service manuals leak for LG... it's not uncommon for people to sell access to B2B... example here: http://b2b-lg.blogspot.com/
Click to expand...
Click to collapse
If you are talking to the baseband directly then why was Paul's Smartflash able to flash an O2X baseband to a G2X? They are different chips, and so it would seem, that they have different protocols for flashing. Maybe these people haven't actually flashed the baseband but screwed up the RIL layer that talks to the baseband? I don't see how a program that is targeting an Infineon baseband chips was able to flash and screw up a Qualcomm baseband chip. That just doesn't make sense to me. Maybe you can illuminate us on how this happened?
jboxer said:
This was split off from another thread that was getting off track a bit.
http://forum.xda-developers.com/showthread.php?t=1305077
If you are talking to the baseband directly then why was Paul's Smartflash able to flash an O2X baseband to a G2X? They are different chips, and so it would seem, that they have different protocols for flashing. Maybe these people haven't actually flashed the baseband but screwed up the RIL layer that talks to the baseband? I don't see how a program that is targeting an Infineon baseband chips was able to flash and screw up a Qualcomm baseband chip. That just doesn't make sense to me. Maybe you can illuminate us on how this happened?
Click to expand...
Click to collapse
It's highly unlikely that this scenario happened at all, it's more likely someone tried to flash the o2x rom and jacked up their partitions causing a soft brick.
If you look at the P990.dll or what has been renamed model.dll for the smartflash release, check the function at 100048D0... you can trace through and look at the commands it's sending to the baseband, 90% of them simply don't exist in the qualcomm based g2x baseband.
Even if you've never used a disassembler before there is a free copy of IDA or even Ollydbg that you can use to look at the model.dll to confirm.
For clarity, when the program gets unexpected results from commands it's issuing it will fail through and return without doing anything... in this specific example the command "AT%CHIPSET" is issued first to which the g2x simply returns "ERROR"... at this point it doesn't go any further.
Let's say for example that it somehow gets beyond the first command, the commands that are shared between devices that get issued in the o2x update process are very generic... such as "AT%IMEI" which does nothing more then return the device IMEI.
I have a few questions in regard to Baseband updates and if we can take advantage of this.
My Question has been covered throughout this forum, with short answers, here and there. However, I have yet to find a sufficient answer to Baseband, Modems, and Radios.
The reason for these questions, are because my signals are horrible and I know it has nothing to do with the roms, I have used all roms offered by our devs. My fiancées mytouch 4g smokes my lg g2x ( sad sad day)
I have ran “GetRil” on every rom and it shows V21e Matching. I have also tried the recommended kernels for each rom.
I have found, depending on the Phone and the thread the terminology changes. For example, HTC threads speak of Radios and Samsung threads talk about Modems. In this thread I have seen Baseband used quite often. Regardless of the terminology, this is the item that effects the signal connection (and much more).
Currently I am running:
Baseband version
M6600A-SCAUTNZ-2.0.9720T [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel version
2.6.32.9
BUILD
Custom
Software Version
LG-P999-V21e
Can we extract the baseband from leaks (if leaks exist)?
Is a different baseband a potential benefit for signal issues?
Any information or advise is greatly appreciated
j3.cole said:
I have a few questions in regard to Baseband updates and if we can take advantage of this.
My Question has been covered throughout this forum, with short answers, here and there. However, I have yet to find a sufficient answer to Baseband, Modems, and Radios.
The reason for these questions, are because my signals are horrible and I know it has nothing to do with the roms, I have used all roms offered by our devs. My fiancées mytouch 4g smokes my lg g2x ( sad sad day)
I have ran “GetRil” on every rom and it shows V21e Matching. I have also tried the recommended kernels for each rom.
I have found, depending on the Phone and the thread the terminology changes. For example, HTC threads speak of Radios and Samsung threads talk about Modems. In this thread I have seen Baseband used quite often. Regardless of the terminology, this is the item that effects the signal connection (and much more).
Currently I am running:
Baseband version
M6600A-SCAUTNZ-2.0.9720T [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel version
2.6.32.9
BUILD
Custom
Software Version
LG-P999-V21e
Can we extract the baseband from leaks (if leaks exist)?
Is a different baseband a potential benefit for signal issues?
Any information or advise is greatly appreciated
Click to expand...
Click to collapse
P999 - No. There are only three known basebands (2 TMO and 1 Wind) and nobody has come up with a way to flash them. We have the .bin file for the baseband that came with the GB update, but no way to flash it. P990 has many basebands because many world versions and due to the baseband chip being different hardware they have a way to flash them.
guys i have a question. its the basebands sames as Radios?
i was just wondering because there are roms for the sensation ported to the sensation 4g and they have a thread were you see all the radios and you just pick the one u need as example we picked the one for tmous and works fine with others roms
gypsy214 said:
guys i have a question. its the basebands sames as Radios?
Click to expand...
Click to collapse
Yes, conceptually anyway. What works on one phone may not work on another.
I have the same July 15 baseband. I updated from the June 15 (Windmobile baseband)
LIke the new one better because my GPS now locks on GB ROM.
With the June 15 baseband, it does not lock on the GPS when using GB ROM.
SL said:
I have the same July 15 baseband. I updated from the June 15 (Windmobile baseband)
LIke the new one better because my GPS now locks on GB ROM.
With the June 15 baseband, it does not lock on the GPS when using GB ROM.
Click to expand...
Click to collapse
That's one of the improvements of the July 15th baseband. It fixed GPS locking problems and it improves WiFi connectivity also. The new baseband chips to everything; radio, wifi, gps, bluetooth, etc. so the baseband code being solid is very important.
SL said:
I have the same July 15 baseband. I updated from the June 15 (Windmobile baseband)
LIke the new one better because my GPS now locks on GB ROM.
With the June 15 baseband, it does not lock on the GPS when using GB ROM.
Click to expand...
Click to collapse
How did you update your WIND baseband? Would you please post your method.
Core Memory said:
How did you update your WIND baseband? Would you please post your method.
Click to expand...
Click to collapse
Most likely he used the KDZ method to force the installation of the Gingerbread udpate. That would also flash the new baseband. You also get the TMO splash screens and bloatware as bonuses.
jboxer said:
Most likely he used the KDZ method to force the installation of the Gingerbread udpate. That would also flash the new baseband.
Click to expand...
Click to collapse
I tried the KDZ method but, although the update started, it got stuck and wouldn't continue. The USB connection was ok and the kdz installer worked. I explained what I did in another thread http://forum.xda-developers.com/showthread.php?p=18844956&posted=1#post18844956
Should I retry with all the steps implemented or is there another method as I ask about.
Core Memory said:
I tried the KDZ method but, although the update started, it got stuck and wouldn't continue. The USB connection was ok and the kdz installer worked. I explained what I did in another thread http://forum.xda-developers.com/showthread.php?p=18844956&posted=1#post18844956
Should I retry with all the steps implemented or is there another method as I ask about.
Click to expand...
Click to collapse
It's been stated numerous times that using virtual PC is extremely buggy... more importantly the tool is inherently buggy anyways for a number of reasons.
The baseband itself gives you a software based vector for updating (you talk to an initialized baseband)... in addition there is an emergency based diagnostic interface for when you fubar a flash... very similar to nvflash for our system nand.
Your concerns in regards to the recovery are also silly as nvflash provides unrestricted low level access to the system nand memory.
Find a Windows XP PC and report back.
same hardware lastest baseband lg-l95g
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I seen this other thread
Where can find lg l95g 's baseband
How to update only baseband
Its really compatible g2x, some tryed flash this baseband to g2x?
sukhochir said:
I seen this other thread
Where can find lg l95g 's baseband
How to update only baseband
Click to expand...
Click to collapse
You've asked and you've been given an answer already. You CANNOT update only the baseband on this phone at this time. Nobody has come up with a way to do it.
More specifically, before you can even think about updating to the prototype baseband you must dump it from the device itself.
Now, because we have extracted the g2x baseband updates from the official kdz files, it is absolutely possible for this guy to force an update to our baseband... which would in theory allow him to use his device on tmobile.
slycog said:
More specifically, before you can even think about updating to the prototype baseband you must dump it from the device itself.
Now, because we have extracted the g2x baseband updates from the official kdz files, it is absolutely possible for this guy to force an update to our baseband... which would in theory allow him to use his device on tmobile.
Click to expand...
Click to collapse
Not sure about that. There is a hidden partition that controls sim lock, etc. That would have to be flashed also to remove the lock. You need special tools to do that.
Deleted - posted in wrong thread.
,When i updated baseband need unlock? , my phone is factory unlocked
sukhochir said:
,When i updated baseband need unlock? , my phone is factory unlocked
Click to expand...
Click to collapse
There are no factory unlocked P999s sold. Only the P990 can be bought factory unlocked. If you bought it unlocked someone unlocked it with a code or special software. The unlock state is kept in a secret hidden partition that you cannot access. Flashing the baseband, which we cannot do, should not change your locked/unlocked state.
A little offtopic but one of the best reasons i loved my old mt4g was how easy it was to flash the radios/baseband thru the bootloader, LG and their godawful drivers/support for this phone just makes me sick. Wish HTC would have made the G2x but kept the tegra chip intact, it's still a nice chip despite having no support from nvidia, played some very nice games with it that put other qualcom/powervr games look ****ty next to it lol
Related
Thanks to help from Dave778 and crazythunder I successfully flashed my WIND LG P999 to the T-Mobile July firmware by using the LG 2.2 driver and uncorrupted V21_00.kdz file. It now has the July baseband. This took 2 weeks of constant failure because the Star_Model.DLL file was corrupt after decompressed from the kdz file. Even though the upgrade worked, it got stuck at the LG screen and the update software didn't indicate that the process had completed. I detached the phone and rebooted but it wouldn't get past the LG logo screen. I flashed it with a ROM after which it completely booted. It totally works and battery life is much better.
Baseband
How does new baseband help? I have Wind too but I dont know how to check which baseband I have. I rooted my phone and flashed EB 2.7 on it.
Core Memory said:
Thanks to help from Dave778 and crazythunder I successfully flashed my WIND LG P999 to the T-Mobile July firmware by using the LG 2.2 driver and uncorrupted V21_00.kdz file. It now has the July baseband. This took 2 weeks of constant failure because the Star_Model.DLL file was corrupt after decompressed from the kdz file. Even though the upgrade worked, it got stuck at the LG screen and the update software didn't indicate that the process had completed. I detached the phone and rebooted but it wouldn't get past the LG logo screen. I flashed it with a ROM after which it completely booted. It totally works and battery life is much better.
Click to expand...
Click to collapse
can you provide the kdz files as they are no longer on tmobiles website? as well as the instructions to flash our wind g2x to gingerbread?
I flashed my phone and also changed my phone info to wcdma only so I don't roam on Rogers I found this setup improved my reception dramatically. I get quicker phone signal recepition than when I was on June baseband. If this does not make any sense sorry on percocet right now from my war wounds but all you half to know is that if your on wind do this upgrade and set your phone not to roam and you will be happy you did
Sent from my LG-P999 using Tapatalk
hixatchi said:
can you provide the kdz files as they are no longer on tmobiles website? as well as the instructions to flash our wind g2x to gingerbread?
Click to expand...
Click to collapse
Look at crazythunder's posts:
http://forum.xda-developers.com/search.php?searchid=99597550
He has provided information and hyperlinks to the files needed.
Because the V21E_00.kdz file I got from someone's post on xdadevelopers had a corrupt file in it, I went through 2 weeks of hell until I got the V21E_00.kdz file he provides which worked. You won't regret upgrading your WIND Optimus 2X to the T-Mobile G2X firmware because it makes the phone operate much better than the Android 2.2 and baseband in the WIND phone.
Core Memory said:
Look at crazythunder's posts:
http://forum.xda-developers.com/search.php?searchid=99597550
He has provided information and hyperlinks to the files needed.
Because the V21E_00.kdz file I got from someone's post on xdadevelopers had a corrupt file in it, I went through 2 weeks of hell until I got the V21E_00.kdz file he provides which worked. You won't regret upgrading your WIND Optimus 2X to the T-Mobile G2X firmware because it makes the phone operate much better than the Android 2.2 and baseband in the WIND phone.
Click to expand...
Click to collapse
That link is broken, can you please post another?
epicsquare said:
That link is broken, can you please post another?
Click to expand...
Click to collapse
Here's the link to crazythunder's profile: http://forum.xda-developers.com/member.php?u=455152
After you access his profile, click on "Statistics" then click on "find all posts by crazythunder"
Here's another option. The files are both good and linked on this thread. Updated my baseband recently.
http://forum.xda-developers.com/showthread.php?t=1332350
http://forum.xda-developers.com/showthread.php?t=1332350
followed instructions on this link and updated baseband to jul 15th!!! and also gingerbread (although its tmobiles bloatware version) but at least no more sleep issue i think
Is there a way to backup out current baseband ? I want to test out this on Videotrons network.. but if it doesnt work good i want to be able to revert...
Core Memory said:
...I flashed it with a ROM after which it completely booted. It totally works and battery life is much better.
Click to expand...
Click to collapse
I noticed the same thing, when I updated to V21e my battery life became much better.
Wind Mobile Baseband
Thanks everyone! Updated baseband with no problems at all. Wind Mobile user
Wind Mobile Baseband
So I have flashed the July 15 baseband and now my data speeds are terrible. I was averaging 4mbps before this update and now i am getting 340kbps. I am on WIND is anyone else had problems like this? Or know how to fix this issue? Also is there any way to go back to the WIND baseband JUNE 5th?
Updated my baseband as well and am having the same crappy data speeds as canuckthejason. Any ideas? Any more info I can provide to help troubleshoot?
---------- Post added at 03:22 PM ---------- Previous post was at 02:42 PM ----------
Just a quick update:
After doing the baseband update, I flashed a backup of CM7 I had taken a few weeks ago (latest stable for g2x) and using speedtest.net, was getting D:32Kb/s U:31Kb/s P:3131ms.
Just updated to the last CM7 nightly (201) and now am getting D:1529Kb/s U:90Kb/s P:272ms so it's a bit better ... still not great, but a vast improvement over the initial test
At 5:25 PM today my phone tested on 3G data service in Toronto at:
Ping = 235ms
Download = 4342kbps (4.342Mbps)
Upload = 386kbps (0.386Mbps)
EEngineer said:
I noticed the same thing, when I updated to V21e my battery life became much better.
Click to expand...
Click to collapse
Was your baseband working when you flashed over to the july baseband?
Kolcrok78 said:
Was your baseband working when you flashed over to the july baseband?
Click to expand...
Click to collapse
Although I'm not Kolcrok, yes but I went through hell to successfully flash my phone with the T-Mobile Android 2.3.3 (Gingerbread) and July 15 baseband update. I have been running the July 15 baseband on WIND without any problems. My phone's battery life, connectivity, and GPS lock also improved.
Core Memory said:
Thanks to help from Dave778 and crazythunder I successfully flashed my WIND LG P999 to the T-Mobile July firmware by using the LG 2.2 driver and uncorrupted V21_00.kdz file. It now has the July baseband. This took 2 weeks of constant failure because the Star_Model.DLL file was corrupt after decompressed from the kdz file. Even though the upgrade worked, it got stuck at the LG screen and the update software didn't indicate that the process had completed. I detached the phone and rebooted but it wouldn't get past the LG logo screen. I flashed it with a ROM after which it completely booted. It totally works and battery life is much better.
Click to expand...
Click to collapse
Hi CM
I wonder if you could lend a hand to a Windie thats been beating his head against the wall all night on this.
I've followed about MANY different tutorials and guides and tips on this process, and it never works properly.
My problems are: LG tool detects my phone as V11H and says, no upgrade needed.
KDZ tool ("Launch software update" from FIRST page) crashes after unpacking the KDZ archive and calling the update.
KDZ tool ("Read phone info, start upgrade, change country to 'different country' ... ) Not possible. Im not prompted for another country, but if I go to the menu and try and select it, there IS no 'different country' entry as shown in some screenshots.
The current state of the phone is, stock GB 2.3.3 from the 'recovery rom' nvflash, plus stock recovery.
Any help you can offer would be much appreciated!
bluenote73 said:
Hi CM
I wonder if you could lend a hand to a Windie thats been beating his head against the wall all night on this.
I've followed about MANY different tutorials and guides and tips on this process, and it never works properly.
My problems are: LG tool detects my phone as V11H and says, no upgrade needed.
KDZ tool ("Launch software update" from FIRST page) crashes after unpacking the KDZ archive and calling the update.
KDZ tool ("Read phone info, start upgrade, change country to 'different country' ... ) Not possible. Im not prompted for another country, but if I go to the menu and try and select it, there IS no 'different country' entry as shown in some screenshots.
The current state of the phone is, stock GB 2.3.3 from the 'recovery rom' nvflash, plus stock recovery.
Any help you can offer would be much appreciated!
Click to expand...
Click to collapse
Did you do it while running Windows XP?
This is what you do
bluenote73 said:
Hi CM
I wonder if you could lend a hand to a Windie thats been beating his head against the wall all night on this.
I've followed about MANY different tutorials and guides and tips on this process, and it never works properly.
My problems are: LG tool detects my phone as V11H and says, no upgrade needed.
KDZ tool ("Launch software update" from FIRST page) crashes after unpacking the KDZ archive and calling the update.
KDZ tool ("Read phone info, start upgrade, change country to 'different country' ... ) Not possible. Im not prompted for another country, but if I go to the menu and try and select it, there IS no 'different country' entry as shown in some screenshots.
The current state of the phone is, stock GB 2.3.3 from the 'recovery rom' nvflash, plus stock recovery.
Any help you can offer would be much appreciated!
Click to expand...
Click to collapse
This is what you need to do to update using KDZ tools. Unfortunately LG changed the way their updater works and now it always need to check with LG before you update. They dont want you to be able to update your phone anymore if they dont agree with what you are doing . So you need to trick it. Follow this tutorial. It worked for me: http://forum.xda-developers.com/showthread.php?t=1473781. Then you can use the KDZ tool and you will get the different country option. Let me know how it goes for you.
Hey ppl! I've been having issues with my baseband after I flashed to stock from Eaglesblood 2.5. This has been going on for 3 days and I haven't found a solution that works. I'm trying to think outside the box here to see if I can resurrect my phone. Are there any roms that I could flash that have the baseband? Since I can't flash over to the stock Gingerbread anymore cause of issues I'm having with the software and/or drivers, maybe I was thinking I could use some other rom that perhaps has the baseband I need.
According to GetRIL the baseband I need is this:
M6600A-SCAUNTZ-2.0.9720T [Jul 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
If there are any roms out there that have this baseband, please let me know and post a link so I can download. Thanks in advance. Any help you guys can give me to ease my suffering a bit is greatly appreciated.
Kolcrok78 said:
Hey ppl! I've been having issues with my baseband after I flashed to stock from Eaglesblood 2.5. This has been going on for 3 days and I haven't found a solution that works. I'm trying to think outside the box here to see if I can resurrect my phone. Are there any roms that I could flash that have the baseband? Since I can't flash over to the stock Gingerbread anymore cause of issues I'm having with the software and/or drivers, maybe I was thinking I could use some other rom that perhaps has the baseband I need.
According to GetRIL the baseband I need is this:
M6600A-SCAUNTZ-2.0.9720T [Jul 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
If there are any roms out there that have this baseband, please let me know and post a link so I can download. Thanks in advance. Any help you guys can give me to ease my suffering a bit is greatly appreciated.
Click to expand...
Click to collapse
Easy answer is, no there isn't a rom or anyway to flash the baseband... you will need to update through the lg updater.
Sent from my LG-P999 using xda premium
The lg updater doesnt work at all. It stalls at 4% and does nothing. I've used the kdz flash but the pc won't recognize my phone anymore when I'm in S/W Update Mode. I've tried using smartflashtool and that doesn't work either cause the phone needs to be in S/W Update Mode. So that being said, what other option do I have?
Send it in to LG, it's sad to see another user going thru what i had to as both lg updater and kdz are such shyt programs even with the correct drivers they buggy as hell. I love my G2x but hate the crap software LG and nvidia put out to try and fix these softbricks/unknown baseband problems. I wish Paul o Brian would have followed thru with his comment about creating a smartflash tool for our P-999's similar to the one he created for the P-990.
Yeah, I was reading about that. Even if he did I don't think it would work.
I used this debug tool here made by slycog:
http://forum.xda-developers.com/showthread.php?t=1248644&page=9
Paul gave up cause it would take him forever to get the smartflash for the baseband to work. First off, he would have to go and rewrite all the drivers so that they work properly. The guy in the thread above like me, had the drivers installed as you can see from one of the screen shots he posted. I tried 3 different sets of drivers all on my desktop and laptop. None of them work when I put my phone into S/W Update mode and connect the usb cable to the phone. As slycog discovered which I'm pretty sure he did but never said it that the driver for the modem just is buggy. Paul's first stop would be to rewrite this driver and get it to work properly. Then Paul would have to create the smartflash and actually get the smartflash to flash the CP bin file. The current smartflash for the P990 has issues flashing the CP bin file. It's alot of freaking work for a phone thats soon to be obsolete in a year or so. Makes no sense for someone like Paul to invest so much time into a project like this that the manufacturer (LG) should have done and foreseen. I'll tell you this much, this WILL be the last time I touch anything from LG period. I'll use my replacement for a month and then I'm off to Samsung. Hopefully by then the Galaxy Nexus will be on T-Mobile. If not, I'll get a GS2. In the meantime, I'll keep searching for solutions. I'm sure there is one out there or someone that can actually find a way to bypass the modem interface and use a different method of flashing per say thru APX that still seems to work for me. I wish nvflash was able to flash the baseband and I wish there were other roms that would have the baseband as I was informed none of the roms do.
Original Post
I started up the LGMobile Support Tool and selected supported model. When I scrolled down, it shows new firmware, V21y, for the LGP999DW, LGP999DWDU, LGP999DWP but still shows V21e for the LGP999WA.
Update 4/20/2012
The V21Y_00 update (LG T-Mobile branded Android 2.3.4) is not available anymore through the LGMobile Support Tool and LG has removed the direct download link to the V21Y_00.kdz file. Instead, thanks to another member, overground, it is now available from http://www.mediafire.com/?obr7717n1ebj2qa
Get it while you can in case LG files a DMCA complaint against Mediafire.
overground
Today, 12:48 PM
# 315
Yeah, seems LG has removed the update from their servers.
I've uploaded V21y here = http://www.mediafire.com/?obr7717n1ebj2qa
@CoreMemory: Feel free to put the link in the OP.
IMPORTANT!
A lot of peeps have had trouble installing the V21Y_00.kdz file. There are many variables which can cause installation failure which are due to "operator error" and/or computer idiosyncracies. This thread and others have information about various methods used to overcome update problems so, if at first you don't succeed, read the thread(s) and keep trying.
As well, this update will install a new baseband and an LG and T-Mobile branded Android 2.3.4 ROM. LG has made some serious changes to the baseband which prevents other ROMs, except for a modded version of the same Android 2.3.4 ROM or the newest versions of CM7 and some other ROMs (which you can find by searching for compatibility with V21Y/March baseband), from working with in-call audio which is the audio for using the phone as a phone - to make and receive phone calls and for the people on each side of the connection to hear each other. So, if you want to install modded ROMs, other than the a modded version of the V21Y Android 2.3.4 ROM installed by this update or one such as CM7 which is compatible (Weapon isn't), don't update. If you do install it you can revert back to V21e by downloading it and using whatever method you used to successfully install the V21y update.
Before you update to V21Y, save a CWM backup of your existing ROM which you can use to revert back to the installation you now have after you reinstall V21E (including the V21E baseband). You can't use CWM to reinstall V21E, you must use the KDZ updater with the V21E kdz file then use CWM to restore your previously installed V21E modded ROM and Kernel. Good Luck!
If you want to revert to V21E Android 2.3.3 and the compatible baseband, get the V21E kdz update file here: http://www.2shared.com/file/WVH0y09f/V21E_00.html
INSTRUCTIONS
There's usually no need to revert your phone back to a stock ROM. If you use the following method, you can install any G2X/P999 .kdz update file (V10f, V21e, V21y, etc.) over almost any ROM, including modded ones. If you want to eliminate a potential update problem, revert to a stock ROM first. If the update didn't work, and you bricked your phone, you need to revert back to a stock ROM which you can do by following the instructions here: http://forum.xda-developers.com/showthread.php?t=1248644&highlight=unbrick+phone
I successfully used Windows Virtual PC in XP Mode to install the .kdz file but you may be able to install it in Windows XP and Windows 7 (32 and 64 bit), as others have successfully done, by using LG_KDZ_FW-Update_OfflineFix as follows:
First,
From the OP by adixtra at http://forum.xda-developers.com/showthread.php?t=1287236
1. download: LG_KDZ_FW-Update_OfflineFix (OFFLINE INSTALLER DOWNLOAD)
2. download: KDZ_FW_UPD_EN (DOWNLOAD FLASHING PROGRAMS)
3. download: ROOT USING SuperOneClick
DO NOT DOWNLOAD ANY OF THE OTHER FILES THERE!
Alternative to downloading the #1 and #2 files listed above,
here's a link to instructions and files, by spyrosk, which includes almost everything (except for SuperOneClick and the .kdz update file) which installs and runs by using an included VB Script: http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
You will still need the .kdz file of your choice to use with it.
Second,
Download the V21Y_00.kdz upgrade/update file which, although LG has removed the V21Y_00.kdz file from their server, thanks to another member, overground, it is now available from http://www.mediafire.com/?obr7717n1ebj2qa
Third,
From the OP by Kairi_zeroblade at http://forum.xda-developers.com/showthread.php?t=1566681
download CWM-Based Recovery 5.0.2.8
Fourth,
Carry out the steps in adixtra's OP at http://forum.xda-developers.com/showthread.php?t=1287236 with the V21y_00.kdz file you downloaded by selecting it from wherever you downloaded it to.
It takes about 10 minutes to complete.
Fifth,
Afterwards, you will have to root it with SuperOneClick and install CWM if you want to use it for backing up, restoring, etc. (saving your butt) otherwise if you restore it will be the stock v21y installation.
XP MODE Instructions
If you don't succeed with Windows 7 or Windows XP (which it should have), it may work with XP Mode in Virtual PC. The LG Modem drivers have to be installed in Windows 7 first then, after you get XP Mode operating, carry out the steps again. After you connect the phone to the computer, you will have to attach the phone's USB port in XP Mode from the XP Mode USB menu. During the update process, the phone's USB port will detach, you'll hear an alert sound, and you must reattach the USB port again from the XP Mode USB menu. That will happen a few times until the process completes. Here's instructions from Microsoft about how to install and use Windows XP mode in Windows 7 http://windows.microsoft.com/en-US/windows7/install-and-use-windows-xp-mode-in-windows-7.
Also,
Have a look at Enyah's thread for information about how others have successfully updated to V21Y_00.kdz http://forum.xda-developers.com/showthread.php?t=1610597
Have a look at Rafase282's post too, it repeats some content from my thread and others' but has some additional content http://forum.xda-developers.com/showpost.php?p=26935107&postcount=3
We're on 21E, right? Weird. Wonder what it is.
Sent from my LG-P999 using xda premium
SefEXE said:
We're on 21E, right? Weird. Wonder what it is.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yes, weird but I have confirmed that it is available. I added a direct link to it in the first post of this thread.
we need a new baseband that sucks less power, and one that does not lose APN when going in to airplane mode... D:
ICS!!!!
.
.
.
.
.
.
SIKEEE x) idk, but I'm restoring back to stock to find out...
missaellpzchvz said:
ICS!!!!
.
.
.
.
.
.
SIKEEE x) idk, but I'm restoring back to stock to find out...
Click to expand...
Click to collapse
I wish
Sent from my Handheld Portal Device
update
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it DID unroot my phone after updating.....sorry i made a mistake before
No LG Camera
illipower said:
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it didn't unroot my phone after updating
Click to expand...
Click to collapse
Ohooooo
Sent from my LG-P999 using xda premium
illipower said:
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it didn't unroot my phone after updating
Click to expand...
Click to collapse
Can you check if it has the LG Camera?
Sent from my LG-P999 using XDA
illipower said:
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it DID unroot my phone after updating.....sorry i made a mistake before
No LG Camera
Click to expand...
Click to collapse
Is it rootable?
It is probably to placate us for a bit about not getting an update to ICS - yet?
Man, even though not ics, it's something. At least we get a new baseband. I'm gonna go fire up the updater and give it a chance, hopefully the baseband is better and that will be used with whatever we flash.
Sent from my LG-P999 using xda premium
mustangtim49 said:
Man, even though not ics, it's something. At least we get a new baseband. I'm gonna go fire up the updater and give it a chance, hopefully the baseband is better and that will be used with whatever we flash.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Same here, haha. I'm in the process of restoring my G2x to stock firmware so I can update it. Takes so long -__-
FatalityBoyZahy said:
Same here, haha. I'm in the process of restoring my G2x to stock firmware so I can update it. Takes so long -__-
Click to expand...
Click to collapse
All I did was restore the stock recovery and I was able to update...then NVFlash CWM back...and restore my ROM I backed up before I updated...
Sent from my LG-P999 using Tapatalk 2
Could somebody please post the OneClickRecovery Flasher? I've gone past my download limit for DepositFiles
lol, I we got 2.3.4 after a almost a year...i guess we are gonna wait for ICS another year ;o
I just updated. Here's some info:
Version: 2.3.4
Baseband: MAR 11 2012
Kernel: 2.6.32.9
Version: GRJ22
Software Version: LG-P999-V21y
So I believe it's running the same kernel as the 2.3.3 update. I'm not sure what differences the new baseband brings.
Why in the f**k would they release another gb version yeah new baseband could be useful however all that manpower and developing could have gone towards some slightly more worthwhile like oh I dunno... ics?
Or maybe LG is soooooo bass ackwards they think 2.3.4 is ics? lmao
Pin it to Win it.
Definitely more stable than 2.3.3, new kernel boot animation seen on leaked build from a few months ago & more options for video encoding (recording). I'm probably going to run it for a while since I do miss the great battery life that LG stock has.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-P999 using Tapatalk 2
I confirm I have the updated baseband. I went through the process to go back to stock and it updated. Then I just restored my backup.
whats the difference btw the two GBs? I know it changes the basebands but anything else that people are noticing?
Here's a flashable zip of the newest modem for Moto x pure xt1575. I recommend to backup efs before flashing...figured id share for those interested
Flash at your own risk:
...remember to make a efs backup first...
https://www.androidfilehost.com/?fid=24438995911969212
Thanks to @Spasticdroid for images
And whoever made the flashable zip for the intial MM update
Google~Android said:
Here's a flashable zip of the newest modem for Moto x pure xt1575. I recommend to backup efs before flashing...figured id share for those interested
Flash at your own risk:
https://www.androidfilehost.com/?fid=24438995911969212
Thanks to @Spasticdroid for images
And whoever made the flashable zip for the intial MM update
Click to expand...
Click to collapse
Flashed with TWRP 3.0.0 and got no service/signal of any kind. Only wifi. Flashed an old modem zip I had and still did not fix the problem. Restoring the EFS backup I made prior to the initial flash returned everything to normal. Anything I did wrong or didn't understand?
Running 2-26 AOKP build
crowmallet said:
Flashed with TWRP 3.0.0 and got no service/signal of any kind. Only wifi. Flashed an old modem zip I had and still did not fix the problem. Restoring the EFS backup I made prior to the initial flash returned everything to normal. Anything I did wrong or didn't understand?
Running 2-26 AOKP build
Click to expand...
Click to collapse
Same issue here.
crowmallet said:
Flashed with TWRP 3.0.0 and got no service/signal of any kind. Only wifi. Flashed an old modem zip I had and still did not fix the problem. Restoring the EFS backup I made prior to the initial flash returned everything to normal. Anything I did wrong or didn't understand?
Running 2-26 AOKP build
Click to expand...
Click to collapse
defvayne said:
Same issue here.
Click to expand...
Click to collapse
Idk... Maybethe rpm images r needed... I flashed it right before i uploaded it... It took about 20 seconds to find my imei and network and then since then all go.... I even proir had an issue wit my fone randomly showong i had. No sim inserted and since i flashed the new update and then flashed aosp roms i habe on the problem twice... So idk what it is.. Oh well that why the first thing a fone should do after twrp is a safely Kept efs backup
Edit... Just flashed another rom along wit the modem just to test and everything worked great...
Google~Android said:
Here's a flashable zip of the newest modem for Moto x pure xt1575. I recommend to backup efs before flashing...figured id share for those interested
Flash at your own risk:
...remember to make a efs backup first...
https://www.androidfilehost.com/?fid=24438995911969212
Thanks to @Spasticdroid for images
And whoever made the flashable zip for the intial MM update
Click to expand...
Click to collapse
Something is not right here.
File sizes are completely different compared to the recovery images from motorola. See pics below:
OP's file contents:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contents from the motorola update:
Difference in unpacked image size. My guess is the OP's images are of the entire partition while the motorola ones are of just the file contents. Still, some folks having identical issues warrants further research.
gpz1100 said:
Something is not right here.
File sizes are completely different compared to the recovery images from motorola. See pics below:
OP's file contents:
Contents from the motorola update:
Difference in unpacked image size. My guess is the OP's images are of the entire partition while the motorola ones are of just the file contents. Still, some folks having identical issues warrants further research.
Click to expand...
Click to collapse
I can promise u there were pulled from the zip in the general section of the February update....extracted the previous modem band 12 fix zip and replace the 2 files... That all i did
gpz1100 said:
Something is not right here.
File sizes are completely different compared to the recovery images from motorola. See pics below:
OP's file contents:
Contents from the motorola update:
Difference in unpacked image size. My guess is the OP's images are of the entire partition while the motorola ones are of just the file contents. Still, some folks having identical issues warrants further research.
Click to expand...
Click to collapse
Could you share link to where you got the stock February firmware
Guys, PLEASE STOP THE UNNECESSARY QUOTING!!! Surely it's possible to reply without automatically quoting or edit the quote out.
I got the firmware by requesting it through motorola. I believe there's a thread on here that's mirroring it but don't have the link. Look in the general or Q&A subsections. Should be on the first or second page.
Following
Sent from my XT1575 using Tapatalk
gpz1100 said:
I got the firmware by requesting it through motorola. I believe there's a thread on here that's mirroring it but don't have the link. Look in the general or Q&A subsections. Should be on the first or second page.
Click to expand...
Click to collapse
That is odd, because i requested the link from Motorola as well and my folder sent from them does not Say Feb 2016 in the title anywhere.
The contents are also diff file sizes as well.
I looked at all the linked mirrors and they all point to the one i have.
look at this pic, yours is on the left, mine on the right.
^^I added the feb 2016 to the name to better distinguish between all the firmware files. After a while it gets hard to figure out which one is what.
Yours looks nearly identical. The difference is you're looking at explorer which shows file size in terms of KB, mine shows actual byte size. Do a properties on each file and you'll see the actual size too. Windows 101.
gpz1100 said:
^^I added the feb 2016 to the name to better distinguish between all the firmware files. After a while it gets hard to figure out which one is what.
Yours looks nearly identical. The difference is you're looking at explorer which shows file size in terms of KB, mine shows actual byte size. Do a properties on each file and you'll see the actual size too. Windows 101.
Click to expand...
Click to collapse
Thanks for the window's 101, did not know that..
But it looks like that's your answer too.. The build that you have is identical to mine. Meaning that we are on the November 1 2015 security patch. OP uploaded the differences from the new February 1 2016 update.
cangri87 said:
Thanks for the window's 101, did not know that..
But it looks like that's your answer too.. The build that you have is identical to mine. Meaning that we are on the November 1 2015 security patch. OP uploaded the differences from the new February 1 2016 update.
Click to expand...
Click to collapse
That's the weird part, files within the archive are dated 2/1/2016. Even so, baseband files do not grow that much in size, especially when they still return the same version number.
Stranger yet (I mentioned it in the feb update thread) is if you flash the current motorola firmware (MPH24.49-18_18), the phone refuses to take the ota to the newest firmware. OTOH, if you flash the original nov firmware 24.49-18, then the phone updates to the feb build without any issues. I've tested all these different firmwares to arrive at the conclusions above.
A binary compare between the original MM baseband (from the november firmware) and the current one (firmware on the motorola site) reveals many differences. There must be some undocumented changes.
My suggested upgrade path is real simple;
1) Flash the original 24.49-18 firmware (not the one that's on motorola now). This is available in the general or developer's thread. filename: CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip
2) Let it boot then perform the system update - this will bring you to the feb build of everything including the baseband
3) Flash whatever rom you want. Don't touch the baseband
Unless there are worthwhile changes, I generally don't touch the baseband. Usually don't touch the firmware either.
non developer build
Hi, if I bought the xt1575 from best buy and flashed the latest marshmallow would it brick my radios and wifi? And if not, where can I find the latest firmware, I tried one from motorola, and lost my radio, comming from 5.1
gpz1100 said:
That's the weird part, files within the archive are dated 2/1/2016. Even so, baseband files do not grow that much in size, especially when they still return the same version number.
Stranger yet (I mentioned it in the feb update thread) is if you flash the current motorola firmware (MPH24.49-18_18), the phone refuses to take the ota to the newest firmware. OTOH, if you flash the original nov firmware 24.49-18, then the phone updates to the feb build without any issues. I've tested all these different firmwares to arrive at the conclusions above.
A binary compare between the original MM baseband (from the november firmware) and the current one (firmware on the motorola site) reveals many differences. There must be some undocumented changes.
My suggested upgrade path is real simple;
1) Flash the original 24.49-18 firmware (not the one that's on motorola now). This is available in the general or developer's thread. filename: CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip
2) Let it boot then perform the system update - this will bring you to the feb build of everything including the baseband
3) Flash whatever rom you want. Don't touch the baseband
Unless there are worthwhile changes, I generally don't touch the baseband. Usually don't touch the firmware either.
Click to expand...
Click to collapse
gigawatt said:
Hi, if I bought the xt1575 from best buy and flashed the latest marshmallow would it brick my radios and wifi? And if not, where can I find the latest firmware, I tried one from motorola, and lost my radio, comming from 5.1
Click to expand...
Click to collapse
If you read everything (including filenames) carefully and were using the correct firmware, (in this case, NOT 1572 which is the Style and not Pure), you wouldn't be losing any radio, unless you were downgrading, in which you'd just have to manually flash the radios again via fastboot after downgrading. Use search for that info.
Anything else you did besides flashing the correct firmware, and not explaining in your posts more on what you did (such as rooting) is on you. Put more details into your post.
There's a sticky thread under Android Development with a collection of firmware for both Pure and Style.
BTW, I saw your other thread. I'm not sure what you were reading, but there is no "developer edition" of this phone, nor firmware.
Has anyone measured any improvement with the newer modem file? I like to use the latest modem when possible.
gigawatt said:
Hi, if I bought the xt1575 from best buy and flashed the latest marshmallow would it brick my radios and wifi? And if not, where can I find the latest firmware, I tried one from motorola, and lost my radio, comming from 5.1
Click to expand...
Click to collapse
You can't "brick" your radios by flashing anything posted here. You can disable them however which is easily fixed by flashing modem or kernel or su depending on the situation.
Anyone been able to solve the problem on this flashable modem file? When I try to flash it, it fails. Currently I was stuck on "roaming indicator on" while on MM and upgraded my custom rom to Nougat (Dirty Unicorn) thinking it would fix it, but it didn't. I tried flashing the MM modem zip, roaming indicator is gone, but I seem to have lost my radio.
modem
Holymsophy said:
Anyone been able to solve the problem on this flashable modem file? When I try to flash it, it fails. Currently I was stuck on "roaming indicator on" while on MM and upgraded my custom rom to Nougat (Dirty Unicorn) thinking it would fix it, but it didn't. I tried flashing the MM modem zip, roaming indicator is gone, but I seem to have lost my radio.
Click to expand...
Click to collapse
how do i tell if my modem is still nougat modem if im back to marshmallow what is nougat radio number or version?
Sherrillface said:
how do i tell if my modem is still nougat modem if im back to marshmallow what is nougat radio number or version?
Click to expand...
Click to collapse
Here is a screenshot from my phone that is running stock Nougat. It shows the Baseband version which is the radio number.
As said in the title... my insurance company has given me several different devices after they keep dying during charge.. I have had several different G1841's and they all seem to die during charge a few days after from applying the DRM fixes and do not turn back on again at all... Has anyone else experienced this issue yet??
I applied all the OTA updates through Sony's official software update then I unlocked the bootloader so I do not believe I am doing anything wrong.. It's just that the devices keep dying every time I obtain root access!! Not sure what to do as this is the 4th time it has happened (happened just today after receiving another device only a few days ago, my insurance company will start to think something is up now...)
Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?
saved-j said:
Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?
Click to expand...
Click to collapse
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?
avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?
YasuHamed said:
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?
Click to expand...
Click to collapse
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Didgesteve said:
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?
Click to expand...
Click to collapse
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
avi312singh said:
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
Click to expand...
Click to collapse
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.
sToRm// said:
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.
Click to expand...
Click to collapse
I believe I used the zips from your 2.0 software.. I sent you a donation through PayPal when you released this, do I get the software or some sort of discount? Student life has hit me hard this year
Well I am getting a completely different device tommorow and will hopefully be able to use your 3.0 fix on it... With regards to the charger, I will use a new wall charger - hopefully can order a new official one from amazon when it arrives and not charge it till then
Before unlocking the bootloader and applying the DRM fixes I experienced no problems such as dead devices.. Let's hope the sixth device is ok!
Update: the culprit of this was the battery charge limit application which requires root privileges and is found on the Google Play store.
I'm not going to link in here but there seems to be a conflict with either the device., rom I don't know - but yeah just making people aware of this