Database Develop

Porting xperia JB roms from T to TX.

if anybody wants to try to make this work here is a cople of things that need to happen.
If you flash any roms made for LT30p to you LT29i you (I am talking custom roms like from peetr, Tim, Greg, etc) you will ended up with black screen whitin first 30 seconds after boot. To get past this issue you need to replace pre_hw_config.sh script from TX rom into T rom. Also make sure that you replace hw_config.sh file from TX rom to T othervise you will flash new touchscreen firmware to you tx and you will be unable to navigate.
now you rom will boot into android and all functions will be operatinal except touchscreen. Screen will show small circel on display every time you touch the screen and you will see that calibration is way off. You can navigate thru screens as long as you try to follow that cytcle. any apps wou want to open you have to double tap on that app. two fingers on screen at the same time will let you swipe between screns.
I think this issue is releatd to kernel vs display driver mismatch.
Another thing that need's to happen just to be safe is you have to remove touchpanel driver from etc/firmware folader so you don't enad up with dead toucscreen because you didn't copy hw_config.sh .
In case you end up with dead touchscreen you will have to re-flash back to ICS stock to make touchscvreen to work. Flashing JB stock ftf will now resolve this issue.
This issue with screen calibration is in kernel and i remember when i tested doomlords tx kernel V2 this is what happened. I had this cyrcle on my screen just by flashing that V2 kernel to TX rom.

Hi, somehow I managed to flash xperia T rom into TX by following your guide. For cursors, just replace all the content of /system/usr folder from TX to original T rom.
but I have one problem, I cannot turn my wifi on. I don't have wifi mac address in wifi menu. And when I tried to insmod it manually, it gives me error. Could you help me fixing this? I could send you my logcat if you need it. Thanks..

so you got touchscreen to works properly? thats great news.
as far as wifi not working issue is probably releated in updater script with symlinks. doublecheck that please.

Is it possible to port rom for locked BL to TX JB like you did before for ICS?

shad0wbane said:
Hi, somehow I managed to flash xperia T rom into TX by following your guide. For cursors, just replace all the content of /system/usr folder from TX to original T rom.
but I have one problem, I cannot turn my wifi on. I don't have wifi mac address in wifi menu. And when I tried to insmod it manually, it gives me error. Could you help me fixing this? I could send you my logcat if you need it. Thanks..
Click to expand...
Click to collapse
touchscreen is working fine.great find

joonlin said:
Is it possible to port rom for locked BL to TX JB like you did before for ICS?
Click to expand...
Click to collapse
once we know what is neede then it should be ok. patches will not work since some files from original T roms will have to be removed and replaced before flashing to TX

shad0wbane said:
Hi, somehow I managed to flash xperia T rom into TX by following your guide. For cursors, just replace all the content of /system/usr folder from TX to original T rom.
but I have one problem, I cannot turn my wifi on. I don't have wifi mac address in wifi menu. And when I tried to insmod it manually, it gives me error. Could you help me fixing this? I could send you my logcat if you need it. Thanks..
Click to expand...
Click to collapse
got wifi working. driver mismatch again for wifi modules.
only thing left is lights for xperia logo

asterix005 said:
got wifi working. driver mismatch again for wifi modules.
only thing left is lights for xperia logo
Click to expand...
Click to collapse
how did you do that?
I'm still stuck here..

make sure you have this line in your updater scrip under symlinks
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
next replace modules from tx to t rom. modules are under /lib/modules
your camera will be up-side down. replace camera modues from vendor/camera

Weird. I've already done everything as you instructed before
gonna try that again tomorrow.
thanks a lot!

alex you are realy xperia geniuos. i used you patch for about 6 ICS roms.and all worked. after the update to jb started i was not able to update till i installed a stock rom and made my update.i was waiting for the jb patch since the 1st days of xperia jb. please would you mind recomending the list of roms you think that they gone well with your patch.i have xperia tx rooted with the russan stock rom
thank you

bldysurgeon said:
alex you are realy xperia geniuos. i used you patch for about 6 ICS roms.and all worked. after the update to jb started i was not able to update till i installed a stock rom and made my update.i was waiting for the jb patch since the 1st days of xperia jb. please would you mind recomending the list of roms you think that they gone well with your patch.i have xperia tx rooted with the russan stock rom
thank you
Click to expand...
Click to collapse
Thank you. all stock based JB custom roms made for xperia T can be converted to run on TX since they are all based on .489 or .140 base.
I have used recoba's rom to work as a base for conversion. I will test TiMiN8R's rom next and with permision from those devs i can make conversion and upload them.

Xperiment_T_2.5 is working good. Everithing works except xperia logo light - same issue on recoba's rom.

asterix005 said:
make sure you have this line in your updater scrip under symlinks
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
next replace modules from tx to t rom. modules are under /lib/modules
your camera will be up-side down. replace camera modues from vendor/camera
Click to expand...
Click to collapse
Re-Testing again.. and works like charm!
Thanks to you, dude!
But one more thing.. I've gathered all the required things in one folder, including the updater script. but when I tried to install via cwm, it gives me status 6, and failed to install. Can you point me what's wrong?
-----
Edit, almost forgot to tell, I'm using peetr__'s Hybrid rom.. Same problem, xperia logo light is off

Upload your .zip file. It seems you have done something wrong
Sent from my star trek communicator
Sony Flagship device circa 2145

gregbradley said:
Upload your .zip file. It seems you have done something wrong
Sent from my star trek communicator
Sony Flagship device circa 2145
Click to expand...
Click to collapse
Somehow I managed to make it work. Gonna upload the file as soon as i'm back from campus. :thumbup:
Sent from my LT29i using xda app-developers app

asterix005 said:
if anybody wants to try to make this work here is a cople of things that need to happen.
If you flash any roms made for LT30p to you LT29i you (I am talking custom roms like from peetr, Tim, Greg, etc) you will ended up with black screen whitin first 30 seconds after boot. To get past this issue you need to replace pre_hw_config.sh script from TX rom into T rom. Also make sure that you replace hw_config.sh file from TX rom to T othervise you will flash new touchscreen firmware to you tx and you will be unable to navigate.
now you rom will boot into android and all functions will be operatinal except touchscreen. Screen will show small circel on display every time you touch the screen and you will see that calibration is way off. You can navigate thru screens as long as you try to follow that cytcle. any apps wou want to open you have to double tap on that app. two fingers on screen at the same time will let you swipe between screns.
I think this issue is releatd to kernel vs display driver mismatch.
Another thing that need's to happen just to be safe is you have to remove touchpanel driver from etc/firmware folader so you don't enad up with dead toucscreen because you didn't copy hw_config.sh .
In case you end up with dead touchscreen you will have to re-flash back to ICS stock to make touchscvreen to work. Flashing JB stock ftf will now resolve this issue.
This issue with screen calibration is in kernel and i remember when i tested doomlords tx kernel V2 this is what happened. I had this cyrcle on my screen just by flashing that V2 kernel to TX rom.
Click to expand...
Click to collapse
Excuse me..i have flash ExperimenT 2.5 rom and use TX kernel(.411). then use the path http://forum.xda-developers.com/showthread.php?t=2268401
I can successful start into the system, but the screen upside down.
So i used flashtool flash the stock LT29i FTF(.411) back.
the same situation also happened.....why??please help me

It would be great if the MIUI rom from Xperia T can be ported to Xperia TX
Really waiting for it
Sent from my LT29i

lt29 invers display
after flash lt29 has inverted display...i flashed it with setool and didnt help..any idea?

How about porting to XV ?
Sent from my LT25i using xda premium

Stock/Pure Android on Z1? ["Solved"]

Hi!
I was wondering, is it possible in some way to download the latest Android version from Google servers and somehow install the Nexus image on Z1?
I love my Z1, but I really, really, don't need the Sony stuff on it (Yeah, I'm a purist). All i need to function is the camera (and of course the necesseties like WLAN, BT, making a phonecall etc, but I assume these are "standard" drivers that will work?)

Falck said:
Hi!
I was wondering, is it possible in some way to download the latest Android version from Google servers and somehow install the Nexus image on Z1?
I love my Z1, but I really, really, don't need the Sony stuff on it (Yeah, I'm a purist). All i need to function is the camera (and of course the necesseties like WLAN, BT, making a phonecall etc, but I assume these are "standard" drivers that will work?)
Click to expand...
Click to collapse
I don't know where to begin with this,....
No, No and NO

There's no way to cross flash other devices firmware. What you can do is root your phone and just delete the sony stuff you don't need.

Ahki767 said:
What you can do is root your phone and just delete the sony stuff you don't need.
Click to expand...
Click to collapse
Yep, the only way. :good:

You could always flash Cyanogenmod or Omni Rom, they're both very close to stock Android
Sent from my Nexus 7 using Tapatalk

Michealtbh said:
You could always flash Cyanogenmod or Omni Rom, they're both very close to stock Android
Click to expand...
Click to collapse
To do that he have to Unlock Bootloader.

Ok!
Thanks for the replies!

And don't forget to backup your TA it could be usefull if you ever want back to stock rom or sell your device
Sent from my C6903 using XDA Premium 4 mobile app

[Q] Can we make a AOSP-Rom for Locked Bootloader?

Hi,
i have a Xperia Z1 with non-unlockable Bootloader. I just love AOSP-Roms but those Roms are just for UB. But can someone make a AOSP-Rom for LB? I think many Users would love that...

Please post questions in the Q&A section,
Thread moved
And to answer your question. No, it needs an unlocked bootloader as AOSP roms require a different kernel to the stock Sony one.

Just to add to the above answer: no, the kernel is different so therefore since you cannot flash a custom kernel on LB, you won't be able to use AOSP.

I think he means use Sony kernel but try port aosp to sonys firmware

And why it work for xperia sp?

richmaster1o2 said:
And why it work for xperia sp?
Click to expand...
Click to collapse
Give link for this.

The Xperia SP have just 4.3 and on this Kernel work a Custom-Rom wich is at 4.4.4:
http://forum.xda-developers.com/xperia-sp/development/kk-nexus-p-c-t2835662

richmaster1o2 said:
The Xperia SP have just 4.3 and on this Kernel work a Custom-Rom wich is at 4.4.4:
http://forum.xda-developers.com/xperia-sp/development/kk-nexus-p-c-t2835662
Click to expand...
Click to collapse
:facepalm::facepalm:
It's built around that kernel so no surprise...

And why we cant make this for our device?

richmaster1o2 said:
And why we cant make this for our device?
Click to expand...
Click to collapse
well apparently you can flash kernel on LB on xperia SP, not on Z1.
If you think otherwise, show us how it's done

richmaster1o2 said:
And why we cant make this for our device?
Click to expand...
Click to collapse
Well i can see that all of that "features" can be made only with root access and Xposed framework modules, and few mods.
Deep in framework, rom is still close to sony stock rom.
For example, everything you can make with apps or mods, except OTA update (for pac), and CM themes.
Everything else is pretty much on google play, and some mods on XDA.
If you want pure AOSP feel, you need to unlock bootloader, this is, how to say, kang version of PAC.

If you say me how to get the flip settings from AOSP on 4.4.4 i would be happy

There is an xposed mod for it
Sent from my C6903 using XDA Premium 4 mobile app

I used it but it ends in Force Close from System UI

richmaster1o2 said:
I used it but it ends in Force Close from System UI
Click to expand...
Click to collapse
Tell me what did you do
Sent from my C6903 using XDA Free mobile app

I installed the Module Activated it and reboot. But if i look at the quick settings there are the normal sony one and then system ui crashes

richmaster1o2 said:
I installed the Module Activated it and reboot. But if i look at the quick settings there are the normal sony one and then system ui crashes
Click to expand...
Click to collapse
Did you read everything careffully.

I know how to mod Android, im not a noob . I did all right and carefully. And just if you want know, im on iHackers v5.0 Beta

Xperia Flip Xposed Module is outdated it don't work on 4.4

Yeah i know that. I just wait while Kexec is in development

[Root] Xperia E1 - Enable Lockscreen Widgets

Due to the Xperia E1 having only 512MB RAM, Sony added a line inside build.prop that disables some features in Android so that the phone won't be running slow. If we change the value of the line from true to false, it will re-enable the disabled features and lockscreen widgets will come back.
Steps:
1. Download an advanced file manager from Play Store (Root Browser)
2. Go to /system and open build.prop with the text editor.
3. Search for the line
Code:
ro.config.low_ram=true
4. Change the value 'true' to 'false'
Code:
ro.config.low_ram=false
5. Reboot

xezrunner said:
Due to the Xperia E1 having only 512MB RAM, Sony added a line inside build.prop that disables some features in Android so that the phone won't be running slow. If we change the value of the line from true to false, it will re-enable the disabled features and lockscreen widgets will come back.
Steps:
1. Download Root Browser from Play Store (Root Explorer is not gonna work)
Click me
2. Go to /system and open build.prop with the text editor.
3. Search for the line
Code:
ro.config.low_ram=true
4. Change the value 'true' to 'false'
Code:
ro.config.low_ram=false
5. Reboot
Click to expand...
Click to collapse
The swipe lockscreen is software bug, or It can be solved with tinkering with build.prop?

Can't work in my xperia e1 dual
If I Help You Then Say Thanks

Kizoky said:
The swipe lockscreen is software bug, or It can be solved with tinkering with build.prop?
Click to expand...
Click to collapse
I tried to set stuff in build.prop, but it still did not work, so I believe it is some kind of software bug, or Sony added something else ( a security certificate thing or something ) that disable the options.

Vicky7999 said:
Can't work in my xperia e1 dual
If I Help You Then Say Thanks
Click to expand...
Click to collapse
That's very unfortunate to hear. Did you do it with Root Browser, or were you using something else? I myself have tried editing build.prop with Root Explorer but it did not work. Root Browser seems to work correctly, or you can also do it using adb push\pull.

xezrunner said:
That's very unfortunate to hear. Did you do it with Root Browser, or were you using something else? I myself have tried editing build.prop with Root Explorer but it did not work. Root Browser seems to work correctly, or you can also do it using adb push\pull.
Click to expand...
Click to collapse
OK I will try
Sent from my D2105 using XDA Free mobile app

xezrunner said:
I tried to set stuff in build.prop, but it still did not work, so I believe it is some kind of software bug, or Sony added something else ( a security certificate thing or something ) that disable the options.
Click to expand...
Click to collapse
No there is no security certificate or software bug. do you use the the single sim (D2005, D2004) or dual sim (D2105, D2104) variant of the e1?
for me it's working

7Zero3 said:
No there is no security certificate or software bug. do you use the the single sim (D2005, D2004) or dual sim (D2105, D2104) variant of the e1?
for me it's working
Click to expand...
Click to collapse
I have a D2005 with 20.0.A.1.21 right now (reinstalled JB for reasons) but this was working last time on 20.1.A.2.13.

xezrunner said:
I have a D2005 with 20.0.A.1.21 right now (reinstalled JB for reasons) but this was working last time on 20.1.A.2.13.
Click to expand...
Click to collapse
Okay then it can be a bug on jelly bean. I can not test now because I can not make a backup of my KitKat firmware. otherwise I would now switch to the Jelly Bean firmware

7Zero3 said:
Okay then it can be a bug on jelly bean. I can not test now because I can not make a backup of my KitKat firmware. otherwise I would now switch to the Jelly Bean firmware
Click to expand...
Click to collapse
The Lockscreen bug only occurs in KitKat, JB is fine. They rushed KK fast on this phone. I regret that day when I bought this phone.
VPN does not work either. Sony does not release Device tree, nor add AOSP support for this phone, so we can't fix it ourselves.

How many devices are affected by this bug please? My E3 on the new 4.4.4 version does not have this issue for example.

image45 said:
How many devices are affected by this bug please? My E3 on the new 4.4.4 version does not have this issue for example.
Click to expand...
Click to collapse
Only the Xperia E1 with KitKat has this issue. They decided to just quickly make the KK for the E1 and didn't care about the bugs (most likely).

xezrunner said:
Only the Xperia E1 with KitKat has this issue. They decided to just quickly make the KK for the E1 and didn't care about the bugs (most likely).
Click to expand...
Click to collapse
There was an updated 4.4.2 build the .14 that states to improve camera stability in a members post. Does anyone know if the screen lock bug is still present. Sony developer world Emma is only flashing the 20.1.A.2.13 build number on unlocked bootloader devices at the moment, however it's advising that the first 4.4.2 .47 build is the latest available version whenever it checks for new updates. I have not seen a 20.1.A.2.14 ftf file for xperia flasher yet.

image45 said:
There was an updated 4.4.2 build the .14 that states to improve camera stability in a members post. Does anyone know if the screen lock bug is still present. Sony developer world Emma is only flashing the 20.1.A.2.13 build number on unlocked bootloader devices at the moment, however it's advising that the first 4.4.2 .47 build is the latest available version whenever it checks for new updates. I have not seen a 20.1.A.2.14 ftf file for xperia flasher yet.
Click to expand...
Click to collapse
Using XperiFirm you can get any of the firmwares you wish. And no, all the firmwares are buggy. Even the Dual versions. Also it's not just the lockscreen bug, it's VPN and overall system stability that's broken.

xezrunner said:
Using XperiFirm you can get any of the firmwares you wish.
Click to expand...
Click to collapse
I have not seen that normally a link to Google drive is posted for example that allows you to download an ftf file of the new build. Not many appear to use Sony Emma, or discussions are low on using this tool.
I was trialing a Z3 style unlock screen and got stuck without been able to get the swipe to Unlock option back. I had to use the philz recovery that K4sh provided for forum E1 users to get back to normal.

image45 said:
I have not seen that normally a link to Google drive is posted for example that allows you to download an ftf file of the new build. Not many appear to use Sony Emma, or discussions are low on using this tool.
I was trialing a Z3 style unlock screen and got stuck without been able to get the swipe to Unlock option back. I had to use the philz recovery that K4sh provided for forum E1 users to get back to normal.
Click to expand...
Click to collapse
If you want to get Swipe to unlock back, you can just simply sync your phone with your Google account (gmail), set up a pattern, go to lockscreen, type in pattern wrong 5 times, select Forgot pattern, type in your creditnals, then exit out from the thing that appears. Then lock the device and see for yourself.

xezrunner said:
If you want to get Swipe to unlock back, you can just simply sync your phone with your Google account (gmail), set up a pattern, go to lockscreen, type in pattern wrong 5 times, select Forgot pattern, type in your creditnals, then exit out from the thing that appears. Then lock the device and see for yourself.
Click to expand...
Click to collapse
So there are workarounds but no current fix.
Is XperiaFirm another program tool or a site? I have visited the sony developer world site, however it does not seem to have any ftf files for the Xperia flasher.

image45 said:
So there are workarounds but no current fix.
Is XperiaFirm another program tool or a site? I have visited the sony developer world site, however it does not seem to have any ftf files for the Xperia flasher.
Click to expand...
Click to collapse
XperiFirm is a tool for downloading Xperia phones' firmwares, even from different countries. It downloads FILESETS or if unpacked by the tool, ftf contents which can be put together in Flashtool to an ftf file, then flashed to your device.
I sent an email regarding issues with the KitKat build to Sony, though I don't think they will care.

I tried but ist it's not working

Aryan Chaurasiya said:
I tried but ist it's not working
Click to expand...
Click to collapse
Try writing ro.config.low_ram=false to the bottom of the file, then reboot and check Settings.
What tool did you use to edit the file?

[5.0.2][D6708][ZIP] Sony Xperia Z3v Prerooted Lollipop Firmware 23.1.D.0.509

Hello all, I've come to bring you news that I have the latest Lollipop firmware for the Xperia Z3v with Verizon. From my understanding, it seems a couple of people are having trouble prerooting their downloaded firmware and are encountering trouble with it. I grabbed my FTF from Xperifirm and followed the instructions on my guide as it went to get it all together hassle-free.
Without further ado, here it is: https://mega.nz/#!24swjQgQ!7o4tB05IEqNEC88UwE5cbESG_8hQFi7YVHZazz8h8iQ
NOTE: I have also attached to the zip brighter flashlight since stock one is terrible.
PLEASE HIT THANKS BELOW IF I'VE HELPED SAVED YOU THE ANNOYING PROCESS!

Yeah, can't wait to try it

Thanks for the file! Can't wait to use it. Any noticeable changes between .485 and .509?

GigaSPX said:
Hello all, I've come to bring you news that I have the latest Lollipop firmware for the Xperia Z3v with Verizon. From my understanding, it seems a couple of people are having trouble prerooting their downloaded firmware and are encountering trouble with it. I grabbed my FTF from Xperifirm and followed the instructions on my guide as it went to get it all together hassle-free.
Without further ado, here it is: https://mega.nz/#!24swjQgQ!7o4tB05IEqNEC88UwE5cbESG_8hQFi7YVHZazz8h8iQ
NOTE: I have also attached to the zip brighter flashlight since stock one is terrible.
PLEASE HIT THANKS BELOW IF I'VE HELPED SAVED YOU THE ANNOYING PROCESS!
Click to expand...
Click to collapse
Hey so I just debloted this and I deleted 87 apps and 570 mb space..
And my phone works 100%. I could delete more maybe 10 to 15 max it just depends on what your needs/uses for the phone are. Thanks again. Some food for thought You can get the project desire 4.0 sound mod for z2 z3 it works awesome. (take a back up just in case) The z4 bootanimation is better and smoother than ours. Xposed modules= -no device check- - xblast tools- -native freezer- -xinternalsd- -xperiafmwohs- -Xperia xposed LP - all of these are worth your time enjoy.

Can you give meFTF Link

haizachary said:
Can you give meFTF Link
Click to expand...
Click to collapse
Well the FTF link is in the above post so..
But the other way XDA home- search - z3..- then go into Z3v Android Development you will find the new firmware there...
If your not rooted Read the root guide first if you got this far you can find it.

Delebird said:
Thanks for the file! Can't wait to use it. Any noticeable changes between .485 and .509?
Click to expand...
Click to collapse
All I've really noticed is a boost in performance. Also, I believe I was getting around 5 hrs of SOT with .485 and now I'm getting around 5:30, but I haven't gone through enough battery cycles to make any definitive conclusions. Only thing you have to worry about is the fact that 509 is a lot zippier and feels a lot lighter than .485

GigaSPX said:
Hello all, I've come to bring you news that I have the latest Lollipop firmware for the Xperia Z3v with Verizon. From my understanding, it seems a couple of people are having trouble prerooting their downloaded firmware and are encountering trouble with it. I grabbed my FTF from Xperifirm and followed the instructions on my guide as it went to get it all together hassle-free.
Without further ado, here it is: https://mega.nz/#!24swjQgQ!7o4tB05IEqNEC88UwE5cbESG_8hQFi7YVHZazz8h8iQ
NOTE: I have also attached to the zip brighter flashlight since stock one is terrible.
PLEASE HIT THANKS BELOW IF I'VE HELPED SAVED YOU THE ANNOYING PROCESS!
Click to expand...
Click to collapse
If someone can find me the z3 5.1.1 update it's only 2.93mb if you have 5.0.2 for the z3. not the whole ftf cause that obviously would not work. this might be need for root though. This 5.1.1 is for the z2 and z3 and we share a alot of the Same libs so I'm willing to be a Guinea pig please someone...

Tigerhoods said:
If someone can find me the z3 5.1.1 update it's only 2.93mb if you have 5.0.2 for the z3. not the whole ftf cause that obviously would not work. this might be need for root though. This 5.1.1 is for the z2 and z3 and we share a alot of the Same libs so I'm willing to be a Guinea pig please someone...
Click to expand...
Click to collapse
I might suggest going with the Z2 compatible version since the Z3v is basically the same as the Z2 in terms of physical design and they both run under the same production name Sirius.

GigaSPX said:
I might suggest going with the Z2 compatible version since the Z3v is basically the same as the Z2 in terms of physical design and they both run under the same production name Sirius.
Click to expand...
Click to collapse
Dude I was going to do this to get the stagefright exploit patched but it's already patched on 509 check for yourself and I checked my build prop and all my stagefright media is on true.- not vulnerable- so I have to say I'm very happy and if verizon ever pushes the ota we will have advanced calling. (Edit) I belive this 509 firmware may actually be 5.1.1 even though it says it's 5.0.2- this could be possible since when I looked up firmware 485 it had 66xx so... -because my stagefright exploit is fixed and I can't activate advanced calling - meaning I can get into the menu but not to the verizon part- 5.1.1 integrates advanced calling so.. This may be 5.1.1 (edit)- it's not - its 5.0.2 with stagefright patch and some ui updates over 5.0.2 -485 firmware

Tigerhoods said:
Dude I was going to do this to get the stagefright exploit patched but it's already patched on 509 check for yourself and I checked my build prop and all my stagefright media is on true.- not vulnerable- so I have to say I'm very happy and if verizon ever pushes the ota we will have advanced calling.
Click to expand...
Click to collapse
Oh wow, that's incredible! Verizon does (slightly) care about us! LOL

GigaSPX said:
Oh wow, that's incredible! Verizon does (slightly) care about us! LOL
Click to expand...
Click to collapse
Yea but verizons way why on 5.0.2 and not 5.1.1 the media librarys are completely different.

I am on build 23.0.E.1.44 - do I need to change that to flash this FTF?

mrrodgersss said:
I am on build 23.0.E.1.44 - do I need to change that to flash this FTF?
Click to expand...
Click to collapse
You can only flash this through a custom recovery. The actual ftf is elsewhere. While I'm here, if you want root you must get it on KitKat then flash this zip to maintain root. If you don't need root find the ftf and flash through flashtool. You can not get root once on lollipop, other then downgrading back to KitKat.

JediDru said:
You can only flash this through a custom recovery. The actual ftf is elsewhere. While I'm here, if you want root you must get it on KitKat then flash this zip to maintain root. If you don't need root find the ftf and flash through flashtool. You can not get root once on lollipop, other then downgrading back to KitKat.
Click to expand...
Click to collapse
So, if I understand correctly, after I've obtained root with KitKat, I then flash the zip provided in this thread using a custom recovery such as TWRP, and then I will have a rooted lollipop device?

mrrodgersss said:
So, if I understand correctly, after I've obtained root with KitKat, I then flash the zip provided in this thread using a custom recovery such as TWRP, and then I will have a rooted lollipop device?
Click to expand...
Click to collapse
That is correct
Sent from my D6708 using XDA Free mobile app

Delebird said:
That is correct
Sent from my D6708 using XDA Free mobile app
Click to expand...
Click to collapse
Are you guys wiping anything prior to flashing the rooted .zip? or just dirty flashing without a wipe?

hunter82i said:
Are you guys wiping anything prior to flashing the rooted .zip? or just dirty flashing without a wipe?
Click to expand...
Click to collapse
I flashed dirty kept all my apps and data- my phone is working great. But you may want to go clean to avoid problems

The only issue I've run into is WiFi not staying on through a reboot, neither soft nor full. Only device I have on 5.x.x that does so

Has anyone else gotten a "system uids inconsistent" error? I keep getting that error and a force close on Google music (continuously) even after a full wipe. Any ideas?