Xperia ZL C6506, Generic US FTF.
So, an interesting and odd problem here.
After updating to Lollipop, I have intermittent signal loss which requires reboots (many each day) to get the cellular signal to reinitialize.
I downgraded back to 4.4.4 stock, and all works fine.
Both have custom kernel (maybe the issue)
Both were rooted (possible)
It is possible that the IMG available here is the issue. I was using the boot.img posted by shoey63, who made the boot.img for Yuga, but does not own a ZL device. He modded the stock kernel from an FTF.
For now I'll just stick with 4.4.4, maybe test BL locked, unrooted stock 5.1.x rom and see if I have any issues.
Any ideas what might have caused this issue?
Related
Hello everyone,
This is my first post here although I have gotten plenty of helpful information from the site in venturing off into rooting and customizing my ION.
I have the Xperia Ion LT28at, which is rooted. I just had a warranty exchange on the phone due to the microphone completely going out. On my previous ION I rooted it and flashed the lt28i firmware to get rid of the att firmware. I noticed a problem after flashing lt28i firmware that I don't believe I encountered before. If I were to be listening to spotify or pandora with head phones or speakers plugged in, if I got a call during or even hours after of listening to music, I would get this weird underwater, alien sounding voice and I sounded the same way to the person on the other end. Has anyone else experienced this? With the new phone I have I'd like to put the deodexed lt28i firmware so I can do a few mods that require it to be deodexed and of course limited to roms due to the locked bootloader. Any Ideas?
Thanks
It might be, as I could be wrong, that it is caused by the cross flash of basebands. Try flashing every bit of int. fw except for baseband (or flashing the att baseband only)
Thanks. That thought actually crossed my mind today about flashing the att baseband only after installing the other firmware. Now is there a difference between the lt28h and lt28i firmware? I see here it states if you want the lt28h over the lt28i firmware with lte then flash just the baseband after installing the lt28h. I was just curious if there was a difference or advantage of one over the other since there is specific instructions in case someone would want the h over the i.
Not knowing what exactly to search for when I originally asked the question I wasn't sure if there was anything on here related. After browsing around a little I ran across 2 post answering discussing both of my questions, no answers on the baseband issue but I'll continue to follow. Thanks for the help. This could be deleted.
^^i too became aware of this problem yesterday...
Your scratchy garbled thing is a known bug with any LT28i ICS firmware being used on a Lt28at. To my knowledge; no one has been able to completely remove it unless running gingerbread or stock AT&T ICS....or the hybrid thing of Lt28h firmware with att baseband...
the weirder part, though, are these baseband flashing issues. That is the difference between the LT28h and i. The 'h' doesn't support LTE, and its firmware's baseband doesn't utilize it. So guys would run LT28h with an AT&T baseband, and NOT have this garbled thing, yet still have LTE.
So some of us figured running any AT&T baseband with LT28i firmware would remove the bug, right? Flashtool seemingly won't do it...it says the flash of the baseband is successful, but it doesn't change anything on the phone...
either way...I'd say just deal with it for the next week or so...JB will be out, and we'll have plenty of other bugs to figure out too haha.
We did indeed flash the at GB base band for the h ics firmware. I will say that the problem was still there with this setup though not as frequent. The only confirmed rom on at devices to not do it are the stock roms from att. Why we can not flash it now I have no idea. I also wounder if it still works for the h roms now?? I will also add that I did notice the issue more when going in and out of 4g. Now that 4g is on all over town it has not done it. I say that and it will tomorrow haha. All we can do is wait now and with two firmwares being leaked it cant be long before a ftf shows up somewhere.
has anyone tried flashing the ATT GB baseband over an LT28i ICS? I only tried ATT ICS baseband, which didn't change the version number (but i haven't had a garbled call since?)...
Hi guys,
I am new to android coming from apple. I am looking to update my xperia zl 4.1.2 build number 10.1.a.1.395 to android 4.2. I have never flashed the phone before but i do however rooted my phone using i believe doomlords mod. I have also an issue with the in ear peice when calling i notice the volume is extremely low when i am making calls. If someone would let me know the steps to fix this issue and the update that would be great. As far as i know i need flashtools and the 4.2 android update? Just want to know which update i would need. My phone is originally a rogers xperia zl but its been unlocked to use any carrier. The bootloader is also locked on this phone.
Thank!
Update your phone over the air. (settings, about phone, software update) and use doomlords tool to root again.
Sent from my C6506 using Tapatalk 4 Beta
Trying to get the update from OTA wont work in your case since you have never flashed the phone and are probably on the stock Roger's firmware meaning you wont see an update available until Rogers pushes their 4.2.2 update with their own bloatware which may take a while.
Just flash the latest FTF firmware C6506_10.3.A.0.423_Unbranded.ftf (stock Sony firmware) found on here on XDA and flash it with Flashtool. Then use doomlord's method to gain root. Very easy stuff... Dont wait for Rogers to update unless you want to wait forever... Carriers are usually slow to update their stuff.
I have had several issues with the 4.4.2 OTA update on my I747 . The most annoying is the battery drain and "hot phone syndrome" which apparently is a bug related related to the camera daemon. Details can be found here http://tinyurl.com/KK-Batt
My goal is to throw 4.4.2 in the bit bucket and go back to stock 4.3 (when life was perfect), however I am leery of the older ROM's running on the newer NE4 bootloader and modem. I have done much reading on XDA for the past week (scortched eyeballs) but haven't found a 4.3 ROM that gives me any confidence ( they all state specifically to flash the MJB or MJ2 level firmware)
Has anyone sucessfully accomplished running 4.3 on the new NE4 bootloader / modem ?
I read a post from @DocHoliday77 that said this "should" be possible .....but I cannot afford a brick. The phone is my ISP, as I have no cable or DSL available , just a mediocre LTE signal from ATT (for which I am grateful)
I am considering this ROM http://forum.xda-developers.com/showthread.php?t=2504903
Thanks for any info or suggestions that you may have
You can flash any ROM you like as long as the ROM does not attempt to flash a new bootloader or modem.
The reason many ROMs require the 4.3 bootloader and modem is the fact that the ROM requires these two things to function properly.
audit13 said:
You can flash any ROM you like as long as the ROM does not attempt to flash a new bootloader or modem.
The reason many ROMs require the 4.3 bootloader and modem is the fact that the ROM requires these two things to function properly.
Click to expand...
Click to collapse
Thanks for the response audit13 , that all makes perfect sense ..... I was hoping maybe someone out there had suffered the same plight and tried this solution.
I read that the problem won't be corrected until android "L" (they attempted to fix it in 4.4.3 but failed). To me this is like Ebola for Android so I don't understand the lack of urgency by Google to correct it ??? Also, one would think a developer would have suffered this plague and been motivated to fix it.
This is not necessarily a Google problem. Samsung ROMs use Samsung kernels, not stock Google kernels.
Samsung is on 4.4.2 while custom ROMs are at 4.4.4.
audit13 said:
This is not necessarily a Google problem. Samsung ROMs use Samsung kernels, not stock Google kernels.
Samsung is on 4.4.2 while custom ROMs are at 4.4.4.
Click to expand...
Click to collapse
Yes but the problem exists in the Nexus line as well, looks like Sam inherited it in the source code. I have thought about trying a different kernel , but IDK if the problem is with the kernel or the daemon or a combination of both.
@audit13 since I am mostly a NOOB here maybe you can help me. I am about to try a custom ROM but am leery that they may mess with my bootloader and modem (NE4) is that possible or typical when you flash a ROM? or do they always state it if they do?
I was running the latest version of Liquid Smooth 4.4.4 and never experienced excessive battery drain or a hot phone on my Nexus 4. After a few days, I installed a custom kernel and my battery life improved but not by very much. Maybe I have been lucky with my Nexus 4. I tried Android L on my Nexus 4 for a while but didn't like the interface. Again, battery drain did not appear excessive on L.
I Don't have KK on my s3 as it is running 4.3 bootloader and modem with a custom ROM.
It is possible that a custom ROM will attempt to flash a bootloader or modem but I have never seen this happen other than a couple of ROMs for a Nexus 4. To ensure that a new bootloader/modem is not going to be flashed to your phone, make sure you look at the first few posts for instructions and warnings.
audit13 said:
I was running the latest version of Liquid Smooth 4.4.4 and never experienced excessive battery drain or a hot phone on my Nexus 4. After a few days, I installed a custom kernel and my battery life improved but not by very much. Maybe I have been lucky with my Nexus 4. I tried Android L on my Nexus 4 for a while but didn't like the interface. Again, battery drain did not appear excessive on L.
I Don't have KK on my s3 as it is running 4.3 bootloader and modem with a custom ROM.
It is possible that a custom ROM will attempt to flash a bootloader or modem but I have never seen this happen other than a couple of ROMs for a Nexus 4. To ensure that a new bootloader/modem is not going to be flashed to your phone, make sure you look at the first few posts for instructions and warnings.
Click to expand...
Click to collapse
Thanks for the feedback @audit13 much appreciated ...... I feel better now. I think I will try upgrading first since there has been no specific feedback on downgrading and my gut tells me it may not be the best idea SlimKat 4.4.4 looks interesting.
Hopefully you will not see a post from me in the future that starts with HELP !!!
I also have never seen a rom that flashes the bootloader or modem. Doing so would be a HUGE mistake!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
I also have never seen a rom that flashes the bootloader or modem. Doing so would be a HUGE mistake!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
@DocHoliday77 ....... Thanks Doc
So I've just about had it with the leaky 5.0.2 lollipop firmware we got stuck with. Bootloader is hopelessly locked for no good reason meaning only Sony signed firmwares/kernels are flashable. A kind gentleman in one of the other subforums gave me instructions to install nuts recovery and that worked (I had rooted previously using kingroot).
He also packages up a flahable zip from a preroted c6903 5.1.1 official firmware (minus the modem files so my american tmo modem stayed in tact. I was trying to do a clean flash). Theoretically this should work right? Nope. Left my phone soft bricked over several attempts. I ended up getting the 4.4.4 ftf and flashing that back and honestly I'm happy with it.
But then I find out that my new vehicle in getting, which will support Android auto in a march update, requires lollipop or better. Son of biscuit eating bulldog!! I dont want to go back to the broken 5.0.2 firmware Sony and Tmo left us with. It was terrible.
Surely there has to be a way to trick the system into thinking we are flashing a stock 5.1.1 firmware to circumvent the locked bootloader right??? I was flashing customized ROMs back when my little brother had a Motorola Defy with a locked bootloader that all we needed to do was install recovery and "restore" a backup of said customized ROM and voila.
Any ideas?
Oh, another thought popped into my head. As far as I was aware, Xposed didnt work on our devices (well, the Z1s c6916 specifically). Can anyone confirm whether xposed works on the Z1s or not on 5.0.2? There is a module for xposed that claims to fix the memory leak issue so that could be another work around.
http://forum.xda-developers.com/showthread.php?t=3034811
Follow the instructions to install xposed.
Hi guys,
I have a problem I need some advice for. A year ago, I purchased my Amami for the purpose of GPS-navigation on my bicycle. It always worked fine and I was able to charge it with my dynohub without any issues. The charging is giving me a headache now though, and all troubleshooting points at the phone being the problem.
Now, a couple months ago I decided to ditch 4.4 and go for a custom ROM (I've tried Oreo and Pie) which worked fine, but the phone doesn't charge as well as it used to on my bike. I'd like to go back to stock to see if that's what is causing the issue and used the Xperia Flashtool to revert to a stock image, but the ones that used to work on the phone now give me bootloops after I've flashed TWRP and ResurrectionRemix and Lineage OS.
Is there anything I need to know before I flash a stock firmware with the tool? Any input would be appreciated.
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
jho55 said:
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
Click to expand...
Click to collapse
My bootloader is unlocked, I have TWRP installed and am currently running Lineage OS (Android 8). It doesn't matter if I flash Sony's original Kitkat or Lollipop; both will have bootloops. No offense, but I'm not sure you understood my original post: I'd like to go back to an old stock ROM, because 4.4 is the one that I'm sure have me no trouble with charging on my bike.
Proper BL relock:
https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907
If you use twrp in fotakernel partition maybe necassary to write back original fotakernel.sin (inside stock.ftf) before relock with flashtool. Remember! After relock with flastool the new BL unlock key here: DEVICESERIAL \ unlock.txt