Related
Hello,
3 day's ago I bought Se arc and first thing what I want to do was find the latest version of firmware for this phone. I connect to my wifi, downloaded the latest soft version 4.0 and clicked install. After installing the phone has shutdown and does not respond now. After pressing the power button flash only for a moment the green light and thats all. After reading forum I tried to flash it and install 3.0.1.A.0.145 FT but still no reaction what can i do next ?
maybe you have an unlocked bootloader?!
Maybe your bootloader was unlocked and the OTA update brick your phone.
Just look in: Fix FOTA bricked phones
If that's the problem, you will find some usefull information to repair.
Bukest
yessssssssss it works
thanks
strange thing that you bought a bootloader unlocked phone, you can get problems with your warranty
depulle87 said:
strange thing that you bought a bootloader unlocked phone, you can get problems with your warranty
Click to expand...
Click to collapse
thats why was so cheap ;/
ok, my phone work now and I wont to get new software version 4.0 what can I do ?
When I take update software in telephone always after instalation it doesn't wont turn on, but after connecting to pc companion 2.0 also I have error "Your phone contains a modified software, which can not be updated"
You have two options:
1.As you are already unlocked simply flash a custom ROM (Check for DoomLord's kernel in the forum).. U get root, ability to overclock and tons of other stuff..
2. If you want to stick to stock SE.. Relock bootloader and then update.. (Check the namaste guide..)
I'd go with the first one
I have new soft in my ARC
i do this i my way - I search forum xda for new soft for arc 4.0 and using flashtool instaled that soft and working ;] symply and quickly
Does anyone have a copy of the stock firmware from the Xperia Pro MK16a or MK16i.
I messed up the phone and want to re-flash the stock firmware back into my phone.
I dont know what else to do and I am desperate....
If you have it in ftf it would be great. Please put it up on mediafire to share.
THANKS!!!
First, it should be usefull to know what you did to brick your phone.
Thinking quickly, here are your options:
1. If you damaged the system partition(mtd0), you may restore it with fastboot having a stock one. Also, it may be possible to restore it with from ClockWorkMod recovery(started via fastboot), with an update created from the stock firmware.
2. If you accidentally damaged the kernel, that would be a bit more difficult. Currently, there's no custom kernle for MK16, so you would have to wait until there's one, or recompile the stock kernel from source(SE makes sources available).
If it's the first, I may be able to help you providing my system partition. It's not the stock one, because the first thing I did when I got to root my phone was start Titanium Backup and begin to delete some system applications I considered useless. But I think you could find my system partition useful. Just explain a little more what you did.
Thanks for trying to help.
Basically I flashed another firmware for it and it didnt go as expected.
I cant restore it because now my phone is recognize as another phone so i cant download the stock firmware for my phone via PC Companion.
Mine is a MK16a with all the bloatware from fido.
I dont really care about rooting it or not.
I just wanted to get raid of some of the stock apps so it doesnt take up so much internal memory.
I think what I really need is the stock MK16i firmware and flash it to my phone or if someone got the stock MK16a firmware I can flash it again to get it running again.
If you anyone have any other suggestions please let me know.
Thanks
i also need a mk16i firmware packed as ftf, can someone help?
TeamXperia has MK16's now, so a stock firmware should be coming pretty fast from them.
I think ftf is for kernel & loader, not for system partition....
ichidakira, I managed to make a dump of my system partition, I think that will fix your phone. Note that it's not the original system partition, as I've deleted some of the default apps and changed the bootanimation.
To restore it in your device, follow this steps:
WARNING: This will clear all your data, including (but not only limited to) contacts, sms, applications, configurations, etc.
1. Download & extract this file: http://soporte.opensysperu.com/downloads/system.zip & the Xperia Pro recovery image from FreeXperia Project: http://www.megaupload.com/?d=8L3DC0UQ .
2. Copy the system.img to your sdcard(using any method).
2. With the phone turned off, hold the menu button and connect the USB cable. If windows asks you to install the driver, do it as specified in the thread about rooting Xperia Pro.
3. Open a command prompt on the folder where you have downloaded recovery.img .
4. Run "fastboot boot recovery.img"
5. The phone will turn on and get detected as a ADB device. Also, the CWM menu will appear on the screen, but you will not need it for now.
6. Run "adb shell". Then, run the following commands: (It may take a few minutes)
cat /sdcard/system.img > /dev/mtd/mtd0
exit
7. On the CWM menu, use thew Vol Down key to highlight "Wipe data/factory reset", and then press the power button. Confirm the action if needed.
8. When finished, type "adb reboot" on your command prompt.
Then, your phone should boot normally.
rcummings100 said:
TeamXperia has MK16's now, so a stock firmware should be coming pretty fast from them.
Click to expand...
Click to collapse
Thanks for the info.
Please let me know when they release it.
For anyone looking for mk16i ftf...
http://forum.xda-developers.com/showthread.php?t=1323730
Thanks to Jozinek
MK16i system partition
Guys, could anyone provide me stock or at least his semi-stock system partition, as alvaroag did above? I have rooted xperia pro MK16i (via xperia recovery) and I'm experiencing weird problems after hard reseting my phone. Everything works virtually fine now, but:
- home button works, but doesn't act as home should
- after USB connecting to PC the PC says that my SD card is not inserted (however I can see its content while in the phone)
- PC Companion software can't find the phone
If anyone would have any advice how to solve this, it would be much appreciated also.
Edit: I had rooted this phone month ago and until yesterday there were zero problems. But then suddenly I lost some of my synced contacts from MS Exchange, so I decided to hard reset it and reinstall apps to fix this little issus. And then everything started...
Try with the latest SE firmware:
{PRO}[DEVELOPMENT] - CM7.2.0 - FXP047 FreeXperia Project
At the bottom of the post are the links for the MK16i SEMC 4.0.2.A.0.42 & MK16a SEMC 4.0.2.A.0.42. Select the one according to your device. Flash them with FlashTool. No this will permanently erase all of your user data.
Then, if you want to root it, try with the zergRush exploit: [16/Nov][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v3.0](zergRush Exploit)
If the phone still presents problems, reflash the stock firmware & take it to your service provider for warranty.
Thanks, alvaroag. I was fixing further and further on and ended up with reflashing Jozinek's stock firmware which solved everything. But then, even with virtually out-of-the-box phone, SEUS still denied to update firmware, saying that the phone has altered software. Not sure if anybody really tried to wipe out EVERYTHING from the phone and pretend, that it hasn't ever been rooted or hasn't been did anything else, but I doubt SE repair service can be fooled that much - even stupid updater still sees some difference between my phone (which obviously lost all changes I made to keyboard, root access, everything after successfull revert to stock firmware provided by Jozinek) and regular not altered phone. So to make the story short - now everything works fine, I have virtually brand new phone, rooted via [16/Nov][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v3.0](zergRush Exploit). But on the other hand I really doubt that these changes can be reverted to the state, that SE repair center would not be able to detect them and thus maybe cancel my warranty. Which is a bit sad and I did not expect it.
BTW: What is the procedure now to update my firmware, once SE will release it? SEUS refuses to do it... And for sure I would prefer to keep my data, if possible...
If you have unlocked your bootloader, then you will not be able to use SEUS. Try using PC Companion. Even with the bootloader unlocked, PC Companion will work, as long as you use stock firmware.
alvaroag said:
If you have unlocked your bootloader, then you will not be able to use SEUS. Try using PC Companion. Even with the bootloader unlocked, PC Companion will work, as long as you use stock firmware.
Click to expand...
Click to collapse
Not true that unlocking bootloader automatically stops SEUS from working. I had Alejandrissimo unlock my bootloader remotely via the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1254416
And even with an unlocked bootloader SEUS worked just fine (that is until i flashed to the latest firmware posted on XDA in the Xperia Pro CM thread). But that's only true if you use his exact method. It seems that all other methods do prevent SEUS from working.
But yes, as soon as you've unlocked the bootloader, regardless of the method, your phone's warranty is void. That includes unlocking it the official way via the sony ericsson website! PITA
And technically, if you even root your phone, you've lost your warranty as well.
rcummings100 said:
But yes, as soon as you've unlocked the bootloader, regardless of the method, your phone's warranty is void. That includes unlocking it the official way via the sony ericsson website! PITA
And technically, if you even root your phone, you've lost your warranty as well.
Click to expand...
Click to collapse
Yes sure, but my point was not that this act voids warranty, which is clear and obvious. My point was about the fact that many people in forums are understanding rooting and other hardcore activities in the way, that "if something would go wrong with my phone, I still can revert all changes, reflash it to out-of-the-box condition and send it to repair service, while they will not be able to detect the phone used to be rooted or altered in similar way", but in fact there must be some detection mechanism which in certain circumstates (as is my reflashed phone) will recognize that phone has been rooted in the past. And my phone is now not upgradable by both SEUS and PC Companion.
Not exactly. If you root your phone without unlocking the bootloader(zergRush exploit), then you can reflash it using SEUS or PC Companion & any track of the rooting will disappear. But if you unlock the bootloader, that's permanent. Even if you relock the bootloader, you will not be able to lave it as it was before unlocking, as the DRM keys are deleted when unlocking.
If there's still interest, I have a stock SEMC/MK16a:2.3.4/4.0.2.A.0.58/xf_v3w:user/release-keys phone and I'm yet to start fiddling with it.
If there's anything worth extracting from it just let me know and I'd try.
mk16a stock firmware - wanna unlock phone
hi. i'm totally new to android platform and rooting stuff! i have a xperia pro mk16a which is locked to fido canada. i want to unlock and debrand it. what i have learnt till now is that i can debrand it by flashing it to stock firmware. please help!
about phone:
see attachment
ichidakira said:
Does anyone have a copy of the stock firmware from the Xperia Pro MK16a or MK16i.
I messed up the phone and want to re-flash the stock firmware back into my phone.
I dont know what else to do and I am desperate....
If you have it in ftf it would be great. Please put it up on mediafire to share.
THANKS!!!
Click to expand...
Click to collapse
Did you tried to do it with phone repair menu in pc suite?
-DON'T PLUG THE PHONE!
-go to SUPPURT ZONE
-and in the software update check phone repair
-check mk16 on the phone list and follow the instructions!
Firmware ftf
I have some links to generic firmware but i can not publish links.
If anyone wants me for the requested by pm
Hi
I have just unlocked the boot loader on my SEXplay and was wondering about updating the phone to a newer firmware then putting doomkernel on.
Basically to cut a long story short, Can I do it through the PC companion or do I have to flash a newer version onto it?
Also if I have to flash could one of you fine members provide me with a link to the new one.
Thanks All
I think you'll have to flash. Btw, SEXplay sounds.. Well.. Wrong.
Hi,
I have the CDA 1280-7858 Sony Xperia Z1 Compact model. I have yet not been able to upgrade my phone to latest lollipop, since T-mobile UK have not released it yet.
My phone is carrier unlocked, but bootloader CANNOT be unlocked, this leaves no possible way for me to add a custom rom , right?
What are my options here? Sit and wait forever or just get a new phone?
As you can see in the attachment, only T-mobile remains on the 14.4.A.0.157 release in the UK carriers.
You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.
templeka said:
You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.
Click to expand...
Click to collapse
Ok, but this would erase my phone completely right? i would use flashtool to upgrade?
Is t here any reason why its taking so long to get the OTA update? I mean, optimally, i want that one and not really need to bother to reset the phone entirely for this update.
You can always make a backup in recovery (I'm thinking you have a recovery already) just in case you don't like lollipop (I didn't). You lose any app installed and preferences (for sms u can backup those and contacts you can sync with Google account) so you will have to reinstall those. If you want root for your phone you need one of those prerooted ones and those are flashed from recovery usually. Best thing is to read the instructions in those threads.
I don't have recovery mode i think. Since this comes with unlocking bootloader, which i CANNOT on my phone.. (its not possible, not even paid with jinx13).
You don't need unlocked bootloader for recovery. Just go here http://nut.xperia-files.com/ and browse to XZDualRecovery > XZDualRecovery 2.8.15 > Z1C-lockeddualrecovery2.8.15-RELEASE.installer.zip and install that from your PC (with the phone connected to your PC via USB). I think you need to enable USB debugging before doing this and you definitely have to be rooted. You should read around how to install stuff there are some guides and resource threads in General forum.
Edit: Also get the flashable version and store it somewhere safe on your phone. Anytime you flash a new ROM you need to also flash the recovery else you have to connect phone to PC and do the install version and that takes longer.
Thanks templeka, I have been unsuccessful in any attempt to root this phone also.. What would be the best way? it just seems to be locked in all ways possible for me to get this done.
edit: i tried the towelroot selection 3 from file you suggested.. it just stopped after libdvm opened (loljavasucks), and after reboot, i was unable to enter recovery mode. (pressed volume up or down, and there was no light on any diode, at any time)
You need to flash a stock .108 rom, root and install dual recovery.
Towelroot will not work on v157. Follow the guide here http://forum.xda-developers.com/showthread.php?t=2977774
In short you need to flash v108 kernel, root and flash v157 kernel back with Flashtool. Be sure to install the necesary drivers after installing Flashtool (they are in the folder where you installed it).
Sorry for being noob still.. But how do i enter flash mode now? I mean reboot and holding volume down will only enter Safe Mode of the phone. (i think its because i have the wrong kernel?)
Just when i was about to give up.. 14.5.A.0.270 just released on t-mobile.. FINALLY!
Hello all
I've been watching the forum for years now and I admit there are plenty of nice guides ( I even rooted my z3 dual first try using the guides)
Now I have purchased Z5 premium dual e6883 model and it's been sitting in the box for almost 2 months now, waiting on a root guide
Most of the guides are either for different models like e6853 or for experts who are into testing and experiencing options
I know there are successful attempt to root this model so I ask if there is any comprehensive (complete) guide on how to get the root for this device?
I would appreciate if anyone can refer to a post or even a guide that I can follow
Model 6883
Android 5.1.1
Build 332.0.A.6.170
Karnel 3.10.49-perf-g9a3c9a8-04532-g75e6207
Many thanks for all the support
Any help please?
I think the first thing that you want to know is, currently you can't root without your bootloader unlocked.
(Please Google search for more details regarding the "side effects" of the unlocked bootloader Sony smartphones, though tobias.waldvogel has created the DRM functions restoration mod.)
My advice, why don't you wait until Android 6 rolls out? Maybe more developers would focus on the latest ROM and bring out various ROOT methods (for unlocked bootloader and locked bootloader maybe?)
I wanted to ROOT my Z5 premium dual since the first day I bought it, but it is a sad thing to lose the DRM keys (my opinion), and unless the DRM functions restoration mod becomes "better", I will not unlock my bootloader just yet...
Novioo said:
Hello all
I've been watching the forum for years now and I admit there are plenty of nice guides ( I even rooted my z3 dual first try using the guides)
Now I have purchased Z5 premium dual e6883 model and it's been sitting in the box for almost 2 months now, waiting on a root guide
Most of the guides are either for different models like e6853 or for experts who are into testing and experiencing options
I know there are successful attempt to root this model so I ask if there is any comprehensive (complete) guide on how to get the root for this device?
I would appreciate if anyone can refer to a post or even a guide that I can follow
Model 6883
Android 5.1.1
Build 332.0.A.6.170
Karnel 3.10.49-perf-g9a3c9a8-04532-g75e6207
Many thanks for all the support
Click to expand...
Click to collapse
keep waiting.. I received 6.0.1 ota on an amazon z5p e6883. The phone worked famously.. .loved it.
Some compulsive and sick part of me wanted to root the phone.. no good reason.. the phone worked perfectly.
I didn't research enough to know that unlocking the bootloader wipes drm keys.. (my hastiness there, no one to blam)
I unlocked the bootloader -
Followed a few guides on this site (full of some knowledgeable folks, but most are tards.. including the site designer who decided to fill the site with shockwave flash ads..WTF)
I can safely say, NONE of the guides worked on this model.
So I've got no rooted phone, but lost DRM keys, so lost phone functionality.
Here's my understanding of the procedure, asuming the obvious.. you have fastboot, flashtool and adb all working
1. unlock bootloader
2. get modified 'premissive' kernel (there are a couple flying around.. I tried both Z5PDual_AndroPlusKernel_v5b.zip, and E6883_MM_ROOTABLE_PERMISSIVE_boot.img during different attempts..
3. get twrp (I tried both twrp-2.8.7.0-E6883-20151130_material.img and twrp-3.0.2-0-E6653-20160504.img. on different runs)
4. flash boot with permissive or andro plus
6. flash recovery with 2.8 or 3.0 twrps
7 reboot and watch You'll see the sony banner then yellow led... Press and hold vol down during yellow led)..
8. Blam. you're in twrp.. All good right.. time to install su.zip or su and drm repair zip...
gravy right..
not for me..
my phone doesn't boot at any point after this point. The OS starts, but I get either a continuous animated 'sony waves' banner OR Android is Starting.. starting apps. (I've waited a long time for this to progress but did not make it to OS..
My recovery..
Flash tool 9.0.22
Sony Xperia Z5 Premium(E6883). FW release : 32.2.A.0.224_R6C. Customization : India Generic_1299-6238
After this, I'm back in business, but without unlocked bootloader and no DRM keys or patch..
during debugging I tried several combinations and found that the OS will not boot after these two modified kernels are pushed
AND twrp won't install without the modified kernel
Would be appreciate if someone could guide me through this, without saying "did you unlock your boot loader..?"
Otherwise, I'd suggest taking that phone out of the box and using it stock.. it's a great phone.
giz
I'm going to side with Giz on this one. Take the phone out of the box and use it without trying to unlock the bootloader. It is a nice phone and the camera is pretty awesome as long as your DRM keys are intact. I'd love to unlock my bootloader too so I could root the phone but I'm not willing to loose some functionality to do so. One thing that really annoys me is those 2 worthless SIM card icons in the tray. They are worthless. All we need are the signal icons. Anyway that's my .02.
foopy said:
I'm going to side with Giz on this one. Take the phone out of the box and use it without trying to unlock the bootloader. It is a nice phone and the camera is pretty awesome as long as your DRM keys are intact. I'd love to unlock my bootloader too so I could root the phone but I'm not willing to loose some functionality to do so. One thing that really annoys me is those 2 worthless SIM card icons in the tray. They are worthless. All we need are the signal icons. Anyway that's my .02.
Click to expand...
Click to collapse
Pardon the pun, but I think I found the "root" of the problem ... at least for myself anyway..
this is for those who *HAVE* unlocked the boot loader.
I couldn't get my 6.0.1 phone (32.2.A.0.224) rooted. I've got the E6883 Dual Sim.
To recap:
I've Unlocked
I've downloaded E6883 MM Permissive Kernel
I've Downloaded E6533 TWRP
What happens after this is that my phone will not ever boot. It just hangs on the animated xperia waves screen.
My Fix is to reflash with flashtool
During Flash AFTER installing the permissive kernel I noticed that the flash tool detected a .163 build number. I thought this was odd because I just flashed to .224
I believe the issue is that the 6883MM permissive boot loader (required to install twrp) was built from a 163 kernel AND the boot loader is not compatible with the system flash that loads up.
I believe all that is required for root on 6.0.1 is a new 6883MM permissive (built using a .224 parent).
Does any of this theory hold any water?
This thread has helped me for E6853 http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
The procedure supports E6833/E6853/E6883 models.
try to downgrade to backup TA, with firm .209 5.1.1 china and had problems,i not to wipe downgrade .. I used xperi firm for download.the cell begins with many errors , xperia z5 premium e6883, i found firm .209 Malaysian but flashtools show firm Z5 normal to flash, I downloaded and blog xperia same name e6886
@Novioo , i have E6833, on 6.0.1 ,,,, build .224
when you were on 5.02 and 5.1.1, KINGROOT can root it EASILY,
however 6.0 , 6.0.1 onwards there is no known xploit (yet)
so i rooted via replacing stock kernal with MODIFIED KERNAL
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
if you are ready to UNLOCK you BOOTLOADER then download your modified kernal from
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!ngpAhbSL
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
danilo_scala said:
try to downgrade to backup TA, with firm .209 5.1.1 china and had problems,i not to wipe downgrade .. I used xperi firm for download.the cell begins with many errors , xperia z5 premium e6883, i found firm .209 Malaysian but flashtools show firm Z5 normal to flash, I downloaded and blog xperia same name e6886
Click to expand...
Click to collapse
downgrading did not work with me also,,,,, malaysian version keeps crashing
YasuHamed said:
@Novioo , i have E6833, on 6.0.1 ,,,, build .224
when you were on 5.02 and 5.1.1, KINGROOT can root it EASILY,
however 6.0 , 6.0.1 onwards there is no known xploit (yet)
so i rooted via replacing stock kernal with MODIFIED KERNAL
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
if you are ready to UNLOCK you BOOTLOADER then download your modified kernal from
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!ngpAhbSL
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
downgrading did not work with me also,,,,, malaysian version keeps crashing
Click to expand...
Click to collapse
@YasuHamed you downgrade wipe all?, i no and have problem with firm china .209, malaysian i found to my xperia premium e6883 but in flashtools show to z5 normal, strange I was afraid to flash, i dont no if bug flashtools
giz02 said:
Pardon the pun, but I think I found the "root" of the problem ... at least for myself anyway..
this is for those who *HAVE* unlocked the boot loader.
I couldn't get my 6.0.1 phone (32.2.A.0.224) rooted. I've got the E6883 Dual Sim.
To recap:
I've Unlocked
I've downloaded E6883 MM Permissive Kernel
I've Downloaded E6533 TWRP
What happens after this is that my phone will not ever boot. It just hangs on the animated xperia waves screen.
My Fix is to reflash with flashtool
During Flash AFTER installing the permissive kernel I noticed that the flash tool detected a .163 build number. I thought this was odd because I just flashed to .224
I believe the issue is that the 6883MM permissive boot loader (required to install twrp) was built from a 163 kernel AND the boot loader is not compatible with the system flash that loads up.
I believe all that is required for root on 6.0.1 is a new 6883MM permissive (built using a .224 parent).
Does any of this theory hold any water?
Click to expand...
Click to collapse
I haven't unlocked my bootloader or attempted to root the phone so I don't have any experience to go on for this particular phone. I do know that sometimes you have to do a factory reset even though you have just flashed a new kernel and/or system image. If you haven't done so you might try that. Also keep in mind after a factory data reset the phone usually takes considerably longer to boot up than normal the first time so be patient. There is a thread that contains a modified .224 kernel so make sure you are using that one and not the .163. After flashing everything and BEFORE first boot perform a factory data reset in recovery and see if that makes a difference.
danilo_scala said:
@YasuHamed you downgrade wipe all?, i no and have problem with firm china .209, malaysian i found to my xperia premium e6883 but in flashtools show to z5 normal, strange I was afraid to flash, i dont no if bug flashtools
Click to expand...
Click to collapse
@Novioo i tried downgrading but could not find right version for E6833. Malaysian version kept crashing.
later i found stock modified roms for E6833 so i made deal with the devil and gave up my DRM KEYS by unlocking the boot loader,,,, but since the stock modified kernal has DRM Stimulation it works fine...
in my views, sooner or later, with or without DRM KEYS restored, you will be unlocking your boot loader anyway!
Z5 deserve to be FREED
i found this firm but in flashtools show to z5 and no premium, i dont no if bug http://www.xperiablog.net/forum/res...dual_e6883_32-0-a-6-209_malaysia_generic.519/
foopy said:
I haven't unlocked my bootloader or attempted to root the phone so I don't have any experience to go on for this particular phone. I do know that sometimes you have to do a factory reset even though you have just flashed a new kernel and/or system image. If you haven't done so you might try that. Also keep in mind after a factory data reset the phone usually takes considerably longer to boot up than normal the first time so be patient. There is a thread that contains a modified .224 kernel so make sure you are using that one and not the .163. After flashing everything and BEFORE first boot perform a factory data reset in recovery and see if that makes a difference.
Click to expand...
Click to collapse
Just wanted to say thanks for taking the time for the response.
I did try the factory reset, then let the phone sit overnight on one occasion, but to no avail.
It turns out that there was a parallel thread using the modified 224 kernel that got me much futher along, but I had other issues with is, so I ended up rolling back to the 163 build on 6.0.0 with root and drmfix. I'll look again once in a few weeks I think. I took the time to get my phone set up again, at least this time I have root and the luxury of running titanium.. such a pain to get everything manually installed and configured.