Hi guys, I've been reading a lot of different threads, but have gotten myself confused. Its been a long time since I done flashing of software, and things are completely changed since then.
Anyway,I currently have the z5 premium which was purchased in o2, however I have now moved to ee and would like the WiFi calling feature. My handset hasn't been rooted or nor can the bootloader be unlocked. Can I still download stock ee firmware and install it without any problems.
I find most branded firmware to be buggy in some way.
there is a tutorial for backing up your TA partition ( the bit that keeps your DRM keys)
https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
and a tutorial for unlocking your bootloader, and compiling a patched Stock Kernel. from there, you will be able to install any of our great Custom roms.
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
If you decide instead to keep your phone locked. you should still be able to flash a stock rom using the FTF and the flash tool. you should still backup all your data, photo's documents etc before doing anything at all with your phone.
and always try to start any new flash completely clean. and build up from there, instead of trying to retain your data, or restoring your apps.
If you want more help with backing up and rooting / unlocking your bootloader just ask. but post the exact model version of your device. as the z5p has 4 different models.
Thanks for the reply Patrick, I got all sorted. Unfortunately the bootloader can't be unlocked on my handset, so can't use custom ROMS. However, I was able to use Flashtool and XperiFirm to download EE's branded firmware, and now I have the WiFi calling feature. Thanks for your help.
Related
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.
So I think many people here know about the new xperia bootloader that allows the use of normal roms ans recoveries with dedicated partitions (more details here http://forum.xda-developers.com/showthread.php?t=3096835).
But I also heard that upgrading to this bootloader made flashing stock ROMs impossible, so I wanted to know if that was true.
If true, I have a backup of my actual unlocked bootloader (didn't make a backup before unlocking because the warranty is loooong gone now) and if I restore it after making the update, will that allow me to go back to stock ROMs ?
Really hope I could get an answer, has anyone tried flashing stock ROMs after updating the bootloader ?
Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!
razvu said:
Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!
Click to expand...
Click to collapse
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.
kevintm78 said:
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.
Click to expand...
Click to collapse
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!
razvu said:
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!
Click to expand...
Click to collapse
These are excellent questions that I'm sure a lot of members are thinking, but just haven't formally asked.
I have a Developer Device that I got directly from a Samsung 2 years ago. When hsbadr put out CM 14.1, I was still on Android 5.1.1. It seemed like a daunting task to do all that was required to get to CM 14.1, but I went ahead with it. I decided that it just made more sense to have my device CID changed to the one that everyone else was on, so I went through all the motions. Yes, the root thing was very touchy. But it really wasn't all that bad.
I'm now on bootloader CPD1, and just today upgraded the baseband by odin flashing the partial firmware for CPJ2 baseband.
Can't wait for hsbadr's next build!!!!
Ok, so in conclusion, which file needs to be flashed to upgrade to CPD1? Is it a stock tar, or the bootloader can be flashed just by itself? After flashing I'm gonna lose root again and have to start over before changing the CID?
You mentioned that you have a developer edition. I have one developer and one retail. My developer is still on an older Jasmine, but it needs to sent for repair. I'm trying to get the retail one done, so I can use it in the meantime. Then, the plan is to get the same thing done on the developer edition. I was hoping that would be easier, as the bootloader is unlocked, but apparently that's not the case.
Sent from my SM-N910V using XDA Free mobile app
Nobody can recommend the right file to flash?
Sent from my SM-N910V using XDA Free mobile app
I am also looking for advice on how to upgrade the bootloader. I am on BPA1 currently but everything I find keeps upgrading everything but the bootloader.
Thanks in advance for any help you can provide.
Hi!
I need to restore my Z1C to a "non-tampered" condition. I've got my TA backed up and I've restored the earliest TWRP I had. I'm now on stock T-Mobile branded ROM, 14.4.A.0.157, but still it remains rooted (I needed to backup the TA first somehow) and TWRP is still present. I just need to make sure that everything I've done is gone (I don't mind flashing stock LP if needed) and as far as I know only those two and TA are left. I tried looking it up, but found no reliable/sufficient info, so I've got few questions:
1. Is there any way in which i could get rid of root and recovery without flashing a clean TFT?
2. Am I correct in assuming, that flashing latest Lolipop TFT from XperiFirm with appropriate branding would get my phone in the same state as an OTA update and factory reset on an nontampered phone?
3. If I were to flash a TFT file right now, I should FIRST restore the TA, then flash stock using Flashtools, correct?
4. On the subject of preparing a TFT, I've read, that you shouldn't push .ta files. My chosen ROM contains following:
simlock.ta
cust-reset.ta
fota-reset.ta
boot/Amami_S1BootConfig_MiscTA.ta
Apart from simlock.ta, which sounds obviously horrible (this phone haven't ever had a simlock anyway), I heard, that I should leave out the *-reset.ta files, right? But what about the last one? My TA backup is made on a 4.4 system and this is a 5.1 ROM as far as I know and I wouldn't want it to cause any issues. I'm also very curious about the purpose of those "reset" files. When you would actually consider using them?
I would really appreciate any help and/or resources. Thanks in advance!
intpee said:
Hi!
I need to restore my Z1C to a "non-tampered" condition. I've got my TA backed up and I've restored the earliest TWRP I had. I'm now on stock T-Mobile branded ROM, 14.4.A.0.157, but still it remains rooted (I needed to backup the TA first somehow) and TWRP is still present. I just need to make sure that everything I've done is gone (I don't mind flashing stock LP if needed) and as far as I know only those two and TA are left. I tried looking it up, but found no reliable/sufficient info, so I've got few questions:
1. Is there any way in which i could get rid of root and recovery without flashing a clean TFT?
2. Am I correct in assuming, that flashing latest Lolipop TFT from XperiFirm with appropriate branding would get my phone in the same state as an OTA update and factory reset on an nontampered phone?
3. If I were to flash a TFT file right now, I should FIRST restore the TA, then flash stock using Flashtools, correct?
4. On the subject of preparing a TFT, I've read, that you shouldn't push .ta files. My chosen ROM contains following:
simlock.ta
cust-reset.ta
fota-reset.ta
boot/Amami_S1BootConfig_MiscTA.ta
Apart from simlock.ta, which sounds obviously horrible (this phone haven't ever had a simlock anyway), I heard, that I should leave out the *-reset.ta files, right? But what about the last one? My TA backup is made on a 4.4 system and this is a 5.1 ROM as far as I know and I wouldn't want it to cause any issues. I'm also very curious about the purpose of those "reset" files. When you would actually consider using them?
I would really appreciate any help and/or resources. Thanks in advance!
Click to expand...
Click to collapse
Not an expert on any of this, but I have done quite a bit of flashing etc, and my two cents is...
1. If I wanted 100% stock, I would probably use Emma. It's official Sony tool, and probably will wipe/reset whatever you're trying to. Also not as many expert-type options, etc...
2. You might be better off posting in Flashtool and/or XperiFirm threads for answers to technical questions.
Can I flash this variant (SM-G990U) over to the ATT, or even a stock unlocked firmware?
The goals are to enable WiFi calling, and remove the metro splash screen.
I cannot root the device as my work requires official firmware.
I am open to suggestions on what is best. I have not tinkered with flashing in quite some time.
U could try to root phone and use safynet fix if your apps requie official firmware non root. if you have (when i check model) standard S21FE phone with branding from ATT (?) you could flash stock rom with odin. I don't know where u from but you could flash your stock firmware for example for spain distribution.
I was able to flash the phone with stock firmware, changed csc to ATT and all works well now. This place has gone downhill. I remember when almost immediate replies to help. Now, not so much. Thanks for trying.