New update (23.4.A.1.264) hits the Xperia Z2 and Z2 Tablet with full Stagefright fix!
Info About The Firmware
Device: Xperia Z2 (D6503)
CDA: 1281-4640
Market: Germany
Operator: Customized DE
Network: GLOBAL-LTE
Release: 23.4.A.1.264 / R4C
Download FTF ::::: CLick ME (MEGA)
Download PreRooted Zip ::::: https://mega.nz/#!G05VzJoa!okaLrXeYiLa2I4eS8-Oow7F7eXWd500KaljFXNfJMDw[/COLOR][/SIZE]
How To install
FlashTool Method:
1. Download Flashtool from http://flashtool.net
2.Install it Then Go To C:\Flashtool\drivers.... Open The Installer And Install FastBoot And FLashmode And Xperia Z2 Drivers
3. after it's finished restart your computer
4. Copy The Downloaded FTF file into C:\Users\YOUR USERNAME\.flashTool\firmwares or Too C:\Flashtool\Firmwares
5. Open Flashtool and click the black thunder icon
6. choose flashmode and choose the firmware ,,, then check wipe : USERDATA (you'll lose all your data)
7. after a couple of minutes it will show you how to connect your device
8. after you successfully flash the firmware , just un-plug your device and boot it up!
Recovery Method: ( You won't lose any data,,pics,,apps etc..)
1. Reboot Into TWRP (see the tutorial below on how to get it)
2. Click On Install
3. Choose The Flashable zip (you can create it in the guide below)
4. Flash It
5. After it's done Wipe Cache And Dalvik cache
6. REBOOT!
In order to flash this firmware through a custom recovery ... you should know two things..
a. How To Install a Custom Recovery
b. How To Create A Prerooted Flashable zip
A: Installing the custom recovery:
You can check my own tutorial on how to install a custom recovery here ====> Click Me
Or Check NUTs Dual Recovery Guide Here ===> Click Me
B: Creating The Flashable Zip
Download PRFcreator from here ==> Click Me http://forum.xda-developers.com/attachment.php?attachmentid=3492498&d=1443713502
1. Open The program and you'll see this window
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Choose Your FTF File
3. If You Want Root ... Download The SuperSU zip file from here Click Me
4. If You Want Recovery Download it From here Click Me
5. Check Kernel , FOTAKernel ,,, Modem ,,,, LTALabel
finally it should look like this
6. click on create and when it's done ,, the zip will be in PRFCreator FolderCredits : @[NUT] for dual recovery @zxz0O0 for prfcreator
Hit the Thanks Button if you found this usefull!
Good method, i will try it.
Tested and fully working with root,dual recovery and Xposed…
Everything's working fine, thank you for the file!
Lamantin001 said:
Everything's working fine, thank you for the file!
Click to expand...
Click to collapse
You're welcome mate!
One thing to keep in mind if you follow the PRFcreator tool route is that before you flash your device with your pre-rooted image, is that to go into system - Apps and then check for any apps that you have moved to your SD card. Move any apps that you have on the SD card back to Phone Memory before you boot to recovery and start flashing your phone. Once you done, you can move them back if you want to, to free up phone memory.
Don't worry, you have not lost your apps, only downside is when you scroll through all your pages and you see all those "app missing" icons, you have that WTF? moment
The reason for this is that after the upgrade, it doesn't see the apps any more when looking at your apps pages as if the SD card is missing. If you go to System - Apps and looking at all your installed apps, you will see they are still then. To fix the issue, simply move them back to phone memory.
...hope my explanation makes sense.
JJD809 said:
One thing to keep in mind if you follow the PRFcreator tool route is that before you flash your device with your pre-rooted image, is that to go into system - Apps and then check for any apps that you have moved to your SD card. Move any apps that you have on the SD card back to Phone Memory before you boot to recovery and start flashing your phone. Once you done, you can move them back if you want to, to free up phone memory.
Don't worry, you have not lost your apps, only downside is when you scroll through all your pages and you see all those "app missing" icons, you have that WTF? moment
The reason for this is that after the upgrade, it doesn't see the apps any more when looking at your apps pages as if the SD card is missing. If you go to System - Apps and looking at all your installed apps, you will see they are still then. To fix the issue, simply move them back to phone memory.
...hope my explanation makes sense.
Click to expand...
Click to collapse
Thanks bro for this helpful info
Doesnt work for me
Thats my way how to get the prerootet .264.
i flash the .402 and rootet it with easyrootool.
as i am later in twrp i choose my own prerootet .264, build it wit prfcreator, exactly how it should be.
after i have flashed the prerootet, no mater if i wipe cache + dalvik cache, when i want to reboot the system it says:
Root Access is missing/broken. Roo [..%] Time
- No
- Yes - Aplly root (/system/xbin/su)
- No
and no matter if i choose yes or no, after rebooting and updating the apps, there is no supersu or ndr utils to find.
dont know what the problem is
I have exact the same problem.
Cilow said:
Doesnt work for me
Thats my way how to get the prerootet .264.
i flash the .402 and rootet it with easyrootool.
as i am later in twrp i choose my own prerootet .264, build it wit prfcreator, exactly how it should be.
after i have flashed the prerootet, no mater if i wipe cache + dalvik cache, when i want to reboot the system it says:
Root Access is missing/broken. Roo [..%] Time
- No
- Yes - Aplly root (/system/xbin/su)
- No
and no matter if i choose yes or no, after rebooting and updating the apps, there is no supersu or ndr utils to find.
dont know what the problem is
Click to expand...
Click to collapse
Flash the .232 through flashtool then update using zip file and make sure you added the correct SuperSU file and the correct recoveyr and make sure to include Kernel , FOTAkernel , Modem , LTAlabel ,,, then try again
Thats it!
With the .232 it works.
After the .264 reboots, i had to install supersu again, without updating it. supersu works fine know and i have finally my 5.1.1. wit root - yes!
Thanks alot!
Can you give us other mirror please
Sent from my D6503 using xda Forums PRO
nafa ragab said:
Can you give us other mirror please
Sent from my D6503 using xda Forums PRO
Click to expand...
Click to collapse
Could you edit your post and delete that full quote.
Sent from my SGP311 using XDA Free mobile app
Cilow said:
Thats it!
With the .232 it works.
After the .264 reboots, i had to install supersu again, without updating it. supersu works fine know and i have finally my 5.1.1. wit root - yes!
Thanks alot!
Click to expand...
Click to collapse
You are welcome!! I'm glad it's working for all of you
guys, I just went back to 4.4, rooted, then used the recovery to install the 264 zip file, the same message of cillow's appeared to me:
"Root Access is missing/broken. Roo [..%] Time
- No
- Yes - Aplly root (/system/xbin/su)
- No"
When I rebooted the phone was without superUS and when I installed it it said that I didn't have root oO
Anyone knows what happened/what can be used to fix it?
Thanks!
PHZ2 said:
guys, I just went back to 4.4, rooted, then used the recovery to install the 264 zip file, the same message of cillow's appeared to me:
"Root Access is missing/broken. Roo [..%] Time
- No
- Yes - Aplly root (/system/xbin/su)
- No"
When I rebooted the phone was without superUS and when I installed it it said that I didn't have root oO
Anyone knows what happened/what can be used to fix it?
Thanks!
Click to expand...
Click to collapse
Before installing the XZDR on 4.4 copy/upload the prerooted zip on your phone. After you install the XZDR the phone will reboot; now you can proceed to install the prerooted zip, it will include SuperSU and recovery. The phone reboots to recovery so you can install the SuperSU .zip, but there is no need for that. All we need to install a prerooted .zip is the recovery. SuperSU will be after restarting the phone on the new software.
cachanilla86 said:
Before installing the XZDR on 4.4 copy/upload the prerooted zip on your phone. After you install the XZDR the phone will reboot; now you can proceed to install the prerooted zip, it will include SuperSU and recovery. The phone reboots to recovery so you can install the SuperSU .zip, but there is no need for that. All we need to install a prerooted .zip is the recovery. SuperSU will be after restarting the phone on the new software.
Click to expand...
Click to collapse
I did that, like, downgrade > root > install recovery > boot on recovery > install prerooted .264. BUT after restarting, superSU wasn't there and not even the recovery. As I said, before I boot after installed the 264, it showed me the message about root.
Thanks!
PHZ2 said:
I did that, like, downgrade > root > install recovery > boot on recovery > install prerooted .264. BUT after restarting, superSU wasn't there and not even the recovery. As I said, before I boot after installed the 264, it showed me the message about root.
Thanks!
Click to expand...
Click to collapse
prerooted zip wasn't build correctly.
Just made it, but went downgrade > root > install recovery > boot on recovery > install prerooted .232 > install prerooted .264 and it worked. I used the prerooted zip file that is avaible at the begnning of the topic, didnt made it myself. Thanks anyway =)
ERROR - Drivers need to be installed for connected device.
I tried installing every single one on the list and still get this error.. and i do restart after.. anyone know what could be wrong ?
10/037/2015 12:37:06 - INFO - Opening device for R/W
10/037/2015 12:37:06 - INFO - Start Flashing
10/037/2015 12:37:06 - INFO - Processing loader.sin
10/037/2015 12:37:06 - INFO - Checking header
10/037/2015 12:37:06 - ERROR - Processing of loader.sin finished with errors.
10/037/2015 12:37:06 - INFO - Ending flash session
10/037/2015 12:37:06 - ERROR -
10/037/2015 12:37:06 - ERROR - Error flashing. Aborted
10/037/2015 12:37:07 - ERROR - Drivers need to be installed for connected device.
10/037/2015 12:37:07 - ERROR - You can find them in the drivers folder of Flashtool.
Related
When I saw that I could upgrade to Lollipop I was interested. Then I realized there probably was no root for this yet. So I went about figuring out a way to root it before going to it. Technically this isn't a root once you have already gone to Lollipop.
THIS WILL ONLY WORK IF YOU ARE STILL ON KITKAT, ROOTED, WITH RECOVERY (TWRP is what I use via NUT's Dual Recovery for the Z1).
Requirements:
PRFCreator - Creates pre-rooted firmware - Click Here to Download
Flashtool - Allows you to flash the FTF - Click Here to Download
The FTF for the upgrade - C6916_14.5.B.0.236_T-mobile_US.ftf - Click Here
The latest SuperSU zip from ChainFire - Click here to Download
I'm assuming you have adb, drivers installed and a general understanding of how to navigate the tools above, if not read up on how they work.
Create a pre-rooted flashable firmware with PRFCreator. Install/Download PRFCreator and put the FTF and the latest SuperSU binary zip in the spot labeled SuperSU Zip. Make sure to check the box next to kernel in the include box on the top right side. See screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Congrats you have just created a flashable zip with SuperSU loaded into it. You might ask why you're not gonna add NUT's XZDualRecovery into there. Reading on the forms at the time of this post and it apppears that PRFCreator and/or Nut's recovery doesn't play well with Lollipop and causes bootloops. So run NUT's Z1xzdualrecorvery installer via bat or sh after the fact and not during via PRFCreator until they can work it out.
Make sure you have the original C6916_14.5.B.0.236_T-mobile_US.ftf in the firmwares folder either C:\Flashtool\Firmwares or C:\User\[username]\.flashtool\firmwares
Now take the flashable zip you created via PRFCreator and put it on your phones internal storage, sdcard etc.
Now that you have the flashable zip with SU preinstalled and ready to fire, reboot your phone into recovery. adb reboot recovery etc.
Once your phone has rebooted into recovery you will need to flash the flashable zip you created with PRFCreator.
After flashing the zip I'd suggest wiping the cache/dalvik. And then you will want to go to the reboot screen and power off the device.
Once the device is powered off open Flashtool.
After it loads and syncs the devices (takes a second) you'll want to double click C9XX from the list (Z1).
Next click the BOLT icon in the top left navigation that has a tooltip that says "Flash"
When the flash screen comes up select the right firmware based on the FTF location, check SYSTEM and BASEBAND under the exclude section and uncheck DATA under the wipe section, I unchecked APPSLOG but you don't have to uncheck it (to be honest I think it slowed my initial bootup by upgrading my apps) via this screenshot:
Now click the "Flash" button with your device disconnected and powered off. Follow the directions. For your Z1s you'll want to hold the "DOWN VOLUME" button and then plug the USB connector into it.
Next you will see Flashtool flashing away. Once it's complete you can unplug your phone and then power it up.
Your device is now rooted and running Lollipop. In terms of installing a custom recovery, again all of that is untested and you'll need to play around with the latest XZdualrecovery from NUT to see how it works.
REMINDER: This doesn't solve killing ric etc. Which is important to note for being able to mount the system etc. You can kill ric via tasker and an .sh script like I do or via a flashable kill ric (seen a few floating around) if you get recovery installed after the fact etc.
Thanks to:
Chainfire for his SUPERSU
zxz0O0 for his PRFCreator tool
Androxyde for keeping flashtool going
greatremix for posting up the FTF
I'll be uploading the flashable zip that I made from PRFCreator. It's over a gb obviously so it might be just as easy for you all to create it yourself.
Reserved
To solve most issues with not being able to write to the system which most root apps need. Install NUT's latest xzdualrecovery which can be found at this address under xzdualrecovery. I installed 2.8.15 via the installer (not the flashable)
http://nut.xperia-files.com/
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Lavievn said:
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Click to expand...
Click to collapse
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Yazuken1 said:
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Click to expand...
Click to collapse
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
joedeveloper said:
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
Click to expand...
Click to collapse
i'm stuck now, do you have a C6902 stock kernel, or any way to change phone infomation by flashtool ?
it's show that my phone is C6902 in flash tool now, so i can't flash any rom or back to stock now
@joedeveloper I'm currently on 4.4.4, rooted with baseband .59, but noticed by your directions with "prfcreator" that you do not have us "check" modem when building the flashable zip. Would it hurt to include the modem so as to get the updated baseband to .69?
Also being deodexed, will that cause issues?
Thanks for the help
Not to distract from joedevelopers hard work, but I think its important for me to inform you guys that if you have already upgraded to lollipop through sony pc companion, or ota, King root does in fact work just fine. It will give a screen saying that it could not find that xperia z1s is rootable, but it will also give an option to try to root anyway. After pressing it, it will tell you the device was sucessfully rooted. And if you check with root verifier it will let you know root was successful. So you're still good if you upgraded to lollipop.
@joedeveloper Settings>About Phone reports baseband .69 after update, so that answers that.
I went back to tft .37 and did a fresh install so I have no information if one with a deodexed phone will be effected.
Many thanks to this update method.
SOLVED
Anyone get xposed to work after this update?
Can you clarify the ric thing?
So far so good, got recovery installed, now im going to try to install the audio mod, cause i desperately need that lol
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
throonis said:
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
Click to expand...
Click to collapse
This is what I'm referring to as the issue with sony ric being enabled. It's sony's way of preventing you from writing to the system, and most root apps need this. If you were to run:
adb shell
then
su
then
mount -o remount,rw /system
What does it tell you? "Denied"?
In order to prevent sony ric from blocking it, try installing NUT's xzdualrecovery version 2.8.15. Z1-lockeddualrecovery2.8.15-RELEASE.installer.zip
http://nut.xperia-files.com/
It has a built in ric killer and will solve your issues.
So all I have to do is flash the zip on my z1s to have.recovery correct I have root supersu
Got root, thanks.
Okay, got root. Thank you. The trick is to keep doing the ADB root until it works. It doesn't work the first couple of times. I gave it 20 minutes each time before trying to install again.
Jellybean
I tried your steps from Jellybean but got no root on lollipop but I can't get root from 4.4.4. Is there a 4.4.2 firmware floating around and could that be the problem? I did the steps twice and followed it exactly. The only difference is 4.3.
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
HOW TO INSTALL CWM AND ROCKZ1L KERNEL ??? STEP BY STEP ! MY Z1S IS ON STOCK 5.0.2, BOOT LOADER UNLOCKED : YES.
SORRY , MY ENGLISH IS VERY BAD ! THANKS SO MUCH .
Details:
Code:
Firmware: 14.6.A.1.236_CustomizedIN (R3D)
SuperSU version: STABLE v2.46
Recovery: Z1C-lockeddualrecovery 2.8.21-RELEASE with system mountable patch.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research or ask questions here if you have any concerns about the work done here
* before flashing it. Remember that you are choosing to make these modifications,
* and I'm not responsible for what you are doing with your device, and I don't take any
* responsibility of bricked devices or any sort of damage that may be caused by you.
*/
Instructions for flashing:
- Backup your data using recovery or as You always do. Sony Backup and restore may work if You will be backing up on Lollipop and then restoring on Lollipop again.
If You don't have root:
If You are on Lollipop
Flash any 14.4.A.0.108 FTF. You can find one here.
Root using the exploit. You can find the root exploit here.
Since You are one .108 firmware already, there it no need to flash the kernel ftf again. Simply run the install.bat in "Root kernel .157.zip>rootkitXperia_20140719.zip"
Install Locked bootloader Dual Recovery by NUT from here. Use Z1C-lockeddualrecoveryX.X.XX-RELEASE.installer.zip.
Download and copy the PRF zip to phone.
Boot into recovery
Wipe the System, Data, Cache, Dalvik cache partitions.
Flash the copied PRF zip.
Wipe Cache and Dalvik Cache
Reboot to phone!
You have got a rooted Lollipop firmware!
If You are on Kitkat:
Root using the exploit. You can find the root exploit here.
If You are on .108 firmware, simply run the install.bat in "Root kernel .157.zip>rootkitXperia_20140719.zip".
If not, then flash the .108 kernel ftf via flashtool, and then run the install.bat .
Install Locked bootloader Dual Recovery by NUT from here. Use Z1C-lockeddualrecoveryX.X.XX-RELEASE.installer.zip.
Once You have recovery:
Download and copy the PRF zip to phone.
Boot into recovery
Wipe the System, Data, Cache, Dalvik cache partitions.
Flash the copied PRF zip.
Wipe Cache and Dalvik Cache
Reboot to phone!
You have got a rooted Lollipop firmware!
If You have root:
Backup Your apps and their data. Take only user apps backups, system apps backups are not recommended.
Go to recovery, take a nandroid backup.(optional, but recommended)
Wipe system, data, cache and dalvik cache.(Wiping data can be optional, but is recommended)
Flash the PRF zip.
Restore apps and their data.
At least one reboot is recommended for phone to settle after restoring apps.
Done!
Download Links:
Flashable zip: D5503_14.6.A.1.236_Generic_India-SuperSU_V2.46-lockeddualrecovery_2.8.21-.zip
Firmware used: D5503_14.6.A.1.236_Generic_India.ftf
Credits:
@zxz0O0 for PRFCreator
@Chainfire for SuperSU
@Nut for Recovery
NOTE: If You were using xposed on 5.0.2, it is compulsory that You must uninstall it first. Else You will have bootloops when You enable Xposed on 5.1.1 You might also need to unsinstall SDK21 to install SDK22 for xposed on 5.1.1 .
If Xposed is needed, You can go here.
14.6.A.1.216 version can be found here.
How can we completely remove Xposed?
Sent from my D5503 using XDA Free mobile app
pathaniya said:
How can we completely remove Xposed?
Sent from my D5503 using XDA Free mobile app
Click to expand...
Click to collapse
I think if You flash the uninstaller from first post here, it will get uninstalled. Though I have not tried it.
Thanks
Sent from my D5503 using Tapatalk
---------- Post added at 04:29 AM ---------- Previous post was at 04:27 AM ----------
Downloading..........
Sent from my D5503 using Tapatalk
Thanks for the new prerooted stock. When making a clean install I noticed that a number of google services and receivers were disabled (especially google play services and google services framework). What is strange is that when I try to enable those with any app like DisableService, MyAndroidTools, AutorunManager etc, they get disabled by themselves in a short period of time. My problem is that GooglePlayServices and GoogleMaps are causing a huge ammount of wakelocks. I thought it might be related to the disabled services.
Can anyone confirm that it is rather caused by the latest firmware update and not by this customized build?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zandgreen said:
Thanks for the new prerooted stock. When making a clean install I noticed that a number of google services and receivers were disabled (especially google play services and google services framework). What is strange is that when I try to enable those with any app like DisableService, MyAndroidTools, AutorunManager etc, they get disabled by themselves in a short period of time. My problem is that GooglePlayServices and GoogleMaps are causing a huge ammount of wakelocks. I thought it might be related to the disabled services.
Can anyone confirm that it is rather caused by the latest firmware update and not by this customized build?
Click to expand...
Click to collapse
Did you figure out the problem? Any solution?
Sent from my D5503 using XDA Free mobile app
I'm still experimenting with google services and receivers (they seem to be behaving differently compared to Kitkat and even Lollipop 5.0.X). At present I'm loosing 1%-1.2% of battery per hour when the phone is idle (in the first place it was 3%-4%).
As for the wakelocks caused by Maps ("net_scheduler"), the only solution I have found so far is to kill Maps process in a task manager when not using it (closing the app and removing it from the tray didn't help). When getting those wakelocks caused by Maps I noticed "OfflineRegionManagementService" running in the background though I'm not sure that it is responsible for the wakelocks.
Why can't i uninstall system apps neither from titanium nor with system app remover? On this rom.
pathaniya said:
Why can't i uninstall system apps neither from titanium nor with system app remover? On this rom.
Click to expand...
Click to collapse
This helped:
http://forum.xda-developers.com/showpost.php?p=65159229&postcount=162
Mirhawk said:
Details:
Code:
Firmware: 14.6.A.1.236_CustomizedIN (R3D)
SuperSU version: STABLE v2.46
Recovery: Z1C-lockeddualrecovery 2.8.21-RELEASE with system mountable patch.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research or ask questions here if you have any concerns about the work done here
* before flashing it. Remember that you are choosing to make these modifications,
* and I'm not responsible for what you are doing with your device, and I don't take any
* responsibility of bricked devices or any sort of damage that may be caused by you.
*/
Instructions for flashing:
- Backup your data using recovery or as You always do. Sony Backup and restore may work if You will be backing up on Lollipop and then restoring on Lollipop again.
If You don't have root:
If You are on Lollipop
Flash any 14.4.A.0.108 FTF. You can find one here.
Root using the exploit. You can find the root exploit here.
Since You are one .108 firmware already, there it no need to flash the kernel ftf again. Simply run the install.bat in "Root kernel .157.zip>rootkitXperia_20140719.zip"
Install Locked bootloader Dual Recovery by NUT from here. Use Z1C-lockeddualrecoveryX.X.XX-RELEASE.installer.zip.
Download and copy the PRF zip to phone.
Boot into recovery
Wipe the System, Data, Cache, Dalvik cache partitions.
Flash the copied PRF zip.
Wipe Cache and Dalvik Cache
Reboot to phone!
You have got a rooted Lollipop firmware!
If You are on Kitkat:
Root using the exploit. You can find the root exploit here.
If You are on .108 firmware, simply run the install.bat in "Root kernel .157.zip>rootkitXperia_20140719.zip".
If not, then flash the .108 kernel ftf via flashtool, and then run the install.bat .
Install Locked bootloader Dual Recovery by NUT from here. Use Z1C-lockeddualrecoveryX.X.XX-RELEASE.installer.zip.
Once You have recovery:
Download and copy the PRF zip to phone.
Boot into recovery
Wipe the System, Data, Cache, Dalvik cache partitions.
Flash the copied PRF zip.
Wipe Cache and Dalvik Cache
Reboot to phone!
You have got a rooted Lollipop firmware!
If You have root:
Backup Your apps and their data. Take only user apps backups, system apps backups are not recommended.
Go to recovery, take a nandroid backup.(optional, but recommended)
Wipe system, data, cache and dalvik cache.(Wiping data can be optional, but is recommended)
Flash the PRF zip.
Restore apps and their data.
At least one reboot is recommended for phone to settle after restoring apps.
Done!
Download Links:
Flashable zip: D5503_14.6.A.1.236_Generic_India-SuperSU_V2.46-lockeddualrecovery_2.8.21-.zip
Firmware used: D5503_14.6.A.1.236_Generic_India.ftf
Credits:
@zxz0O0 for PRFCreator
@Chainfire for SuperSU
@Nut for Recovery
NOTE: If You were using xposed on 5.0.2, it is compulsory that You must uninstall it first. Else You will have bootloops when You enable Xposed on 5.1.1 You might also need to unsinstall SDK21 to install SDK22 for xposed on 5.1.1 .
If Xposed is needed, You can go here.
14.6.A.1.216 version can be found here.
Click to expand...
Click to collapse
Dear Sir ,
thanks for customization of stock rom loved it to bits ! but the problem arisd when i installed titanium backup , the need was to remove system apps and make it just tidy ! but the apps are shown uninstalled in titanium backup but they are actually not ! please help me over this
b. i also tried various system app removers from the play store , none of them did work ! this made me irritated , then i installed your 14..........368 version ! same problem arised over there ! seriously help me
c. lastly used root explorers to delete systm apps but this also failed !
plz sir plz help me soon !!:crying::crying::crying:
sp462308 said:
Dear Sir ,
thanks for customization of stock rom loved it to bits ! but the problem arisd when i installed titanium backup , the need was to remove system apps and make it just tidy ! but the apps are shown uninstalled in titanium backup but they are actually not ! please help me over this
b. i also tried various system app removers from the play store , none of them did work ! this made me irritated , then i installed your 14..........368 version ! same problem arised over there ! seriously help me
c. lastly used root explorers to delete systm apps but this also failed !
plz sir plz help me soon !!:crying::crying::crying:
Click to expand...
Click to collapse
Make sure system is rw - use terminal and type 'mount -o remount,rw /system', and/or do this - http://forum.xda-developers.com/sony...ition-t3226957, then try your apps again.
[/COLOR]
levone1 said:
Make sure system is rw - use terminal and type 'mount -o remount,rw /system', and/or do this - http://forum.xda-developers.com/sony...ition-t3226957, then try your apps again.
Click to expand...
Click to collapse
sir please explain ! and the link is dead ! thanks for paying ateention towards this very fast
The above command replies " mount pertion not permites "
sp462308 said:
[/COLOR]
sir please explain ! and the link is dead ! thanks for paying ateention towards this very fast
The above command replies " mount pertion not permites "
Click to expand...
Click to collapse
Sorry, try this - http://forum.xda-developers.com/son.../root-gaining-write-access-partition-t3226957
If you're getting 'not permitted' trying to run command, you must not have su. First, type 'su', then grant root access, then try command.
levone1 said:
Sorry, try this - http://forum.xda-developers.com/son.../root-gaining-write-access-partition-t3226957
If you're getting 'not permitted' trying to run command, you must not have su. First, type 'su', then grant root access, then try command.
Click to expand...
Click to collapse
sir , root access gained !
but it says the same ! mount : operation not permitted
sp462308 said:
sir , root access gained !
but it says the same ! mount : operation not permitted
Click to expand...
Click to collapse
Very strange - and you have a '#' in terminal, not a '$', right? I guess you could check /system/xbin/su file and see if permissions are set to 755. I'm not sure why you would get that message if you have root and su. Anyway, you could also use file manager in recovery and delete any system files you want...
sp462308 said:
sir , root access gained !
but it says the same ! mount : operation not permitted
Click to expand...
Click to collapse
Like screen shot...
sp462308 said:
sir , root access gained !
but it says the same ! mount : operation not permitted
Click to expand...
Click to collapse
Check /system/xbin/mount that permissions are 777
levone1 said:
Like screen shot...
Click to expand...
Click to collapse
yes sir , i do obtain "#" mark , ad the link you posted in the above post helped me ! the real problem was in dual recovery ! .
i just downloaded xz dual recovery from nuts page and re installed , entered to TWRP, wiped Dalvik cache and rebooted ! voila ! this trick worked like charm ! and now able to remove ! system bloatware
! btw can u help , I am on supersu 2.46 by chainfire , should i update it to latest 2.78 ? will it loose root access ? does installing 2.78 zip and updating supersu from play store is diffrent !
sp462308 said:
yes sir , i do obtain "#" mark , ad the link you posted in the above post helped me ! the real problem was in dual recovery ! .
i just downloaded xz dual recovery from nuts page and re installed , entered to TWRP, wiped Dalvik cache and rebooted ! voila ! this trick worked like charm ! and now able to remove ! system bloatware
! btw can u help , I am on supersu 2.46 by chainfire , should i update it to latest 2.78 ? will it loose root access ? does installing 2.78 zip and updating supersu from play store is diffrent !
Click to expand...
Click to collapse
It's good to update if you get update notification from Supersu app. Then, try to so it through normal method in app. If it doesn't work, (installation failed), then download 2.78 zip from Chainfire site, and flash in recovery.
XPERIA Z2 D6503 23.5.A.0.570 UNLOCKED/LOCKED BOOTLOADER
FLASHABLE ZIP
YOU WANT THE NEW ANDROID 6.0.1 MARSHMALLOW UPDATE ON YOUR XPERIA Z2 BUT YOU WANT TO KEEP ROOT, RECOVERY & XPOSED?
THEN KEEP READING THIS THREAD!
features::angel:
prerooted (BETA-SuperSU-v2.68)
recovery (twrp)
byeselinux
RICDefeat
bootloop fix
signed zip file
optional:
xposed framework v82
Sound 3 in 1 Bass Loud Stereo MM
DMR Function Restore V3 [Team HSxEXR]
and more!#
ftf:
D6503_23.5.A.0.570_1281-9715_R4D [AUSTRALIA]
https://youtu.be/Zx02x357Mo0
Checklist:
lollipop (stock or stock based)
root
busybox
recovery
USB Debugging + Unknown Sources
ADB Drivers
non-xposed stock (USE xposed-UNINSTALLER)
Introduction:
Download the "Marshmallow_D6503.zip"
extract the zip file
boot into recovery
X. OPTIONAL flash "xposed-uninstaller-20150831-arm.zip" to remove LP xposed
FACTORY RESET
flash "flashableMM.zip"
flash "byeselinux_flashable.zip"
flash "RICDefeat.zip"
flash "Z2-6.0.1_570_bootloop_fix.zip"
wipe cache & dalvik
now it`s time to flash your favourite zip files like:
X. OPTIONAL XPOSED flash "xposed-v82-sdk23-arm.zip"
X. OPTIONAL UB flash "[Team HSxEXR] DRM function restore V3.zip"
X. OPTIONAL UB SOUND flash "Sound 3 in 1 Bass Loud Stereo MM.zip"
wipe cache & dalvik
reboot
install "BusyBox.apk" and install newest available version
X. OPTIONAL install "XposedInstaller_3.0_alpha4" for Xposed
Enable USB Debugging + Unknown Sources
Run "install.bat from /Z2_MM_TWRP_Recovery_V2_By_Serajr/ to install the Recovery
connect the Z2 to PC, phone will reboot into twrp
DONE:victory:
GOT TROUBLE WITH YOUR RECOVERY? RECOVERY FIX in 2 MINUTES:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
MEGA.nz] DOWNLOAD:
OPTIONAL UB... optional step for unlocked bootloader
OPTIONAL... optional step for locked and unlockedd bootloader
DO NOT FORGET THAT IF YOU HAVE A LOCKED BOOTLOADER YOU ARE NOT ALLOWED TO FLASH ZIPS FOR UB LIKE THE DMR FUNCTION V3 ZIP FILE!
LIST OF WORKING FLASHABLE ZIPS:
xposed framework v82 sdk 23 arm [XPOSED
Sound 3 in 1 Bass Loud Stereo MM [SOUND MOD]
DRM function restore V3 [UB MOD]
thank you!
:good:
seems to work fine on my z2
can I also flash other zips like this one:
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
?
elitephantompro said:
:good:
seems to work fine on my z2
can I also flash other zips like this one:
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
?
Click to expand...
Click to collapse
if the zip file is comptible with marshmallow and the z2 of course you can i recommand to flash the zip files directly after "the bootloop fix file wipe"!
Recovery fix
UPDATE:
I FINALLY FOUND A SOLUTION FOR THE AFTER A WHILE DISAPPERAING TWRP RECOVERY!
SOMETIMES IT`s GOOD TO SEARCH IN OLDER THREADS
Problem! :/
I have some problems about speaker and headset with microphone.
Anyone can't hear me when I speak with speaker
And I can't talk to anyone with headphone. I hear toppy sound.
I think problems source is boomsound, how can I uninstall other extra mods?
Help me please!
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
SoloTheWolf said:
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
Click to expand...
Click to collapse
Well if you don't have recovery you have to flash a ftf with flashtool.
If u have recovery you can wipe amd start the process again.
Have you tried the MMbootloop
fix.zip?
nice tutorial
works 100%
SoloTheWolf said:
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
Click to expand...
Click to collapse
did you flash the bootloop fix.zip? did you try to flash a recovery like the NUT`s Dualrecovery after flashing the needed files? because there is no working recovery except the one in my tutorial! try to only flash the needed files, and skip every optional step! you can try all the zips you want to install after installing the twrp recovery. this tutotial works 100%
Abdülcelil said:
I have some problems about speaker and headset with microphone.
Anyone can't hear me when I speak with speaker
And I can't talk to anyone with headphone. I hear toppy sound.
I think problems source is boomsound, how can I uninstall other extra mods?
Click to expand...
Click to collapse
hey! you installed a soundmod? then i am sorry, you have to reinstall a lollipop ftf, root it (i do it with kingsroot) and install a recovery (i prefer NUT`s dualrecovery)
then do the whole procedure again but skip all the oiptional steps with xposed and so on! dont forget to install the recovery, and use the fix if it disappears after using it for one time. after doing that, check your sound, if its not working, its 100% a hardware bug. if its working, make a full backup using the recovery, and then flash one zip file, check if sound is working, then flash another one (mabye it`s becasue of an incompatible zip!) thats why you should backup the system.
freaky2xd said:
hey! you installed a soundmod? then i am sorry, you have to reinstall a lollipop ftf, root it (i do it with kingsroot) and install a recovery (i prefer NUT`s dualrecovery)
then do the whole procedure again but skip all the oiptional steps with xposed and so on! dont forget to install the recovery, and use the fix if it disappears after using it for one time. after doing that, check your sound, if its not working, its 100% a hardware bug. if its working, make a full backup using the recovery, and then flash one zip file, check if sound is working, then flash another one (mabye it`s becasue of an incompatible zip!) thats why you should backup the system.
Click to expand...
Click to collapse
I actually don't know these things. I just like some advantages of root and wanted to see android mm. I actually don't know what should I do. If there is a video, instruction, photo etc. I follow them and do it. Could you tell me what should I do at first? If I just turn back to 5.1.1 pre rooted and do that process again, will it be fixed?
not worked
it says md5 skipping (sucessful in 1 sec). pls help sony z2
use my own tft file with your tutorial
Hello, I am still waiting for release of CE1 .570 version by Sony. After that I want to create my own pre-rooted file. Should it work with your tutorial? Any special steps needed when creating own tft file to make it work with your tutorial?
miroslav.novotny said:
Hello, I am still waiting for release of CE1 .570 version by Sony. After that I want to create my own pre-rooted file. Should it work with your tutorial? Any special steps needed when creating own tft file to make it work with your tutorial?
Click to expand...
Click to collapse
of course you can use another .570 ftf for the z2! it works the same way, all the zip files (most important the bootloopfix) do work.
but you have to use the same supersu zip file like in my flashablemm file! download it and extract the supersu zip out of the flashablemm zip using winrar you can also try the newest beta from supersu but the one i used is more likely to be safe. (NOT 2.46!!!) just use the prf creator, select your ftf, for root select the supersu zip i used, CHECK all the features (in the right upper box) like fotakernel and so on and ckeck "sign" the zip file to avoid trouble while flashing it. you are invited to press the thanks button!
SidhuZ said:
it says md5 skipping (sucessful in 1 sec). pls help sony z2
Click to expand...
Click to collapse
model= D6503 or D6502?
did you wipe cache and dalvik and made a factory reset via recovery before trying to flash the flashablemm?
of course you need to exctract all the files from "Marshmallow_D6503.zip" and then flash "FlashableMM.zip" and then the other files like me...
maybe you " checked" something like "zip file signature verification" before "swipe to confirm flash"?
try it with and without enabling the zip file signature verification.
if it still doesnt work`, redownload the file! maybe the file got broken while downloading it
miroslav.novotny said:
Any special steps needed when creating own tft file to make it work with your tutorial?
Click to expand...
Click to collapse
I just tried make my own prerooted flashable zip from US ftf and it works for me. See pic. of my settings.
Now i have [LB] D6503 .570 fw SuperSu 2.71 and twrp 3.0.2.0 after rebooting to twrp again I flashed busybox 1.24
Good luck
btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
petrmelis said:
I just tried make my own prerooted flashable zip from US ftf and it works for me. See pic. of my settings.
Now i have [LB] D6503 .570 fw SuperSu 2.71 and twrp 3.0.2.0 after rebooting to twrp again I flashed busybox 1.24
Good luck
btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
Click to expand...
Click to collapse
I see you used higher version of (beta) SuperSU, any reason? Or you just wanted to try and it worked?
I have no special reason waiting for CE1 .570 apart from wanting to have ROM for my region (despite the fact most of the ROM code is probably the same)
freaky2xd said:
of course you can use another .570 ftf for the z2! it works the same way, all the zip files (most important the bootloopfix) do work.
but you have to use the same supersu zip file like in my flashablemm file! download it and extract the supersu zip out of the flashablemm zip using winrar you can also try the newest beta from supersu but the one i used is more likely to be safe. (NOT 2.46!!!) just use the prf creator, select your ftf, for root select the supersu zip i used, CHECK all the features (in the right upper box) like fotakernel and so on and ckeck "sign" the zip file to avoid trouble while flashing it. you are invited to press the thanks button!
Click to expand...
Click to collapse
Thanks freaky2xd, maybe will give it a try even before the CE1 .570 release!
miroslav.novotny said:
I see you used higher version of (beta) SuperSU, any reason? Or you just wanted to try and it worked?
I have no special reason waiting for CE1 .570 apart from wanting to have ROM for my region (despite the fact most of the ROM code is probably the same)
Thanks freaky2xd, maybe will give it a try even before the CE1 .570 release!
Click to expand...
Click to collapse
I used the supersu beta because the newest "stable" version 2.46 doesn`t with Xperia´s marshmallow! but don`t panic, the beta zips are nearly as stable as the 2.46 but not finally completed for marshmallow. when the final supersu zip for marshmallow is available you can download and simply flash it on your marshmallow system if you want. I used this supersu version because I knew 100% that it will work. everything higher than the version I used will work too
petrmelis said:
....btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
Click to expand...
Click to collapse
Just wanted to make sure it will be the same as I have currently.
BTW where did you get the Z2_RecRootV3_combined.zip? I can find only RecrootV4 for Z3 in some other thread....
BTW where did you get the Z2_RecRootV3_combined.zip? I can find only RecrootV4 for Z3 in some other thread....
Click to expand...
Click to collapse
I took it from here: http://forum.xda-developers.com/showpost.php?p=66534297&postcount=535
I dont know what is a different between V3 and V4 except V3 has Z2 in its name.
(1) Install MTK drivers
Download link: MTK Vcom Preloader Driver 2.0
Guide: Guideline / Install MTK drivers / How to Root / Flash a Rom / IMEI Restore
(2) Install TWRP 3.0.2 Recovery
NEW version TWRP: recovery-unofficial-twrp-elephone-p9000
Download Link: SP_Flash_Tool_Windows_v5.1520.00.000
- Unzip p9000 TWRP 3021.zip
- Open SP_Flash_Tool_Windows_v5.1520.00.000
View attachment 3779843
- Select the MT6755_Android_scatter.txt file from TWRP folder. (1)
- Select the recovery recovery_TWRP_3021_P9000.img file from TWRP folder. (2)
- Turn off the phone
- Click Download button. (3)
- Connect the phone (turned off) to a USB Port.
Program after recognizing phone will flash recovery and display Download OK. Done
(3) Root Stock Rom 31.05.2016 / 08.06.2016
- If you want to Root your prefered Stock Rom
- Place SuperSU [UPDATE-SuperSU-v2.65-20151226141550] into your Sdcard
- Turn off the phone
- Hold Vol+ and Power to get into Bootloader Menu
- Move the slider from left to right.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Click [install].
- Click [Select Storage] (Micro SDCard). Select the zip file SuperSU from memory card. Move the slider from left to right.
After installation:
- Click [Wipe cashe/dalvik] (Deletes files from the cache virtual machine system. This wipe is recommended primarily for updating or changing the ROM.)
- Click [Reboot System]
It works on 31.05.2016 / 08.06.2016 ROM Good luck:laugh::good:
Remember before you do the next update OTA need to do a flash recovery on the orginal.
=============== OTA 2016.06.08 =============== OTA 2016.06.08 ===============
If you have root before installing OTA flash orginal P9000 recovery from p9000_RECOVERY.zip
- Unzip p9000_RECOVERY.zip
- Open SP_Flash_Tool_Windows_v5.1520.00.000
View attachment 3779843
- Select the MT6755_Android_scatter.txt file from p9000_RECOVERY folder. (1)
- Turn off the phone
- Click Download button. (3)
- Connect the phone (turned off) to a USB Port.
Program after recognizing phone will flash recovery and display Download OK. Done
Now you can do the OTA update
- For safety before you do OTA remove fingerprints from the security options.
- Remove the SD card (if inserted), insert the SIM card into the slot 1.
- Make OTA update.
- Again ROOT the phone. (Install TWRP 3.0.2 Recovery and UPDATE-SuperSU-v2.65) see above.
It works on 08.06.2016 ROM Good luck:laugh::good:
Worked perfect for me in stock 31052016 !
Hello. Thanks for this guide. However since I am not much into android I got one question. Will rooting my phone delete all the data I have on it? I set up my phone, installed all the programs and so on but I'd like to have rooted device cause I got used to use some apps on my previous rooted phone.
So:
Following this guide will erase everything or no(make it as factory reset)?
Thanks for reading and moreover thanks for your answer. Best wishes.
stewakg said:
Hello. ....
So:
Following this guide will erase everything or no(make it as factory reset)?
Thanks for reading and moreover thanks for your answer. Best wishes.
Click to expand...
Click to collapse
You can skip erase cache dalvic and just click reset. Everything will be as it was. The phone will have a ROOT, everything should work as expected.
Thanks. I will update you tomorrow with results.
Just so you know: "wipe cache/dalvik" does NOT do a factory reset and will not delete your apps/messages/whatever. There is a separate option in TWRP to do a factory reset (aka "full wipe").
Wipe cache/dalvik should always be safe to do, without any data loss. After you wipe cache/dalvik the next reboot will take long and you will see the "Android is updating ... Optimizing app x of y" screen. Other than that, there are no bad side effects to wipe cache/dalvik. On the contrary: it can sometimes solve problems if you have random random crashes or "app has stopped working" popups.
Keksmeister said:
Just so you know: "wipe cache/dalvik" does NOT do a factory reset and will not delete your apps/messages/whatever. There is a separate option in TWRP to do a factory reset (aka "full wipe").
Wipe cache/dalvik should always be safe to do, without any data loss. After you wipe cache/dalvik the next reboot will take long and you will see the "Android is updating ... Optimizing app x of y" screen. Other than that, there are no bad side effects to wipe cache/dalvik. On the contrary: it can sometimes solve problems if you have random random crashes or "app has stopped working" popups.
Click to expand...
Click to collapse
My mistake, I installed the root after changing the rom on a clean system.
The day after I made wipe again, but that from the menu and there is added whipe date, did not pay attention to it.
It turns out that doing wipe cache/dalvik is safe.
Thanks. Regards :laugh:
Now you can do the OTA update
- For safety before you do OTA remove fingerprints from the security options.
- Remove the SD card (if inserted), insert the SIM card into the slot 1.
- Make OTA update.
-> not work. have only Sim1 inside.
says update.zip is not correct
I had a problem with the 08.06 update. I flashed the stock rom and the device was OK but than the PC didn't recognize anymore the device, so now I can't flash twrp or anything else. I tried to reinstall the drivers but nothing changed
giaggio13 said:
I had a problem with the 08.06 update. I flashed the stock rom and the device was OK but than the PC didn't recognize anymore the device, so now I can't flash twrp or anything else. I tried to reinstall the drivers but nothing changed
Click to expand...
Click to collapse
The same thing happened to me on my Windows 8.1 after 31.5.16 OTA. Because on the other laptop I have Windows Vista I installed the drivers there and there did the last update.
For now, I did not have time to delve into my Win8.1, tried different drivers without success.
Write if you solve the problem.
demien_max said:
The same thing happened to me on my Windows 8.1 after 31.5.16 OTA. Because on the other laptop I have Windows Vista I installed the drivers there and there did the last update.
For now, I did not have time to delve into my Win8.1, tried different drivers without success.
Write if you solve the problem.
Click to expand...
Click to collapse
I'm having this issue from the same PC running w10. The drivers were working before the update to the new ota.
giaggio13 said:
I'm having this issue from the same PC running w10. The drivers were working before the update to the new ota.
Click to expand...
Click to collapse
Elephone changed something in the preloader, after flash with version from ROM 2016.03.15 (I use a second PC with Win Vista) everything works again on my Win8.
However, probably after the next OTA preloader again be changed. So I think that this is a temporary solution.
demien_max said:
(1) Install MTK drivers
Download link: MTK Vcom Preloader Driver 2.0
Guide: Guideline / Install MTK drivers / How to Root / Flash a Rom / IMEI Restore
(2) Install TWRP 3.0.2 Recovery
Download Link: SP_Flash_Tool_Windows_v5.1520.00.000
- Unzip p9000 TWRP 3021.zip
- Open SP_Flash_Tool_Windows_v5.1520.00.000
View attachment 3779843
- Select the MT6755_Android_scatter.txt file from TWRP folder. (1)
- Select the recovery recovery_TWRP_3021_P9000.img file from TWRP folder. (2)
- Turn off the phone
- Click Download button. (3)
- Connect the phone (turned off) to a USB Port.
Program after recognizing phone will flash recovery and display Download OK. Done
(3) Root Stock Rom 31.05.2016 / 08.06.2016
- If you want to Root your prefered Stock Rom
- Place SuperSU [UPDATE-SuperSU-v2.65-20151226141550] into your Sdcard
- Turn off the phone
- Hold Vol+ and Power to get into Bootloader Menu
- Move the slider from left to right.
View attachment 3779844
- Click [install].
- Click [Select Storage] (Micro SDCard). Select the zip file SuperSU from memory card. Move the slider from left to right.
After installation:
- Click [Wipe cashe/dalvik] (Deletes files from the cache virtual machine system. This wipe is recommended primarily for updating or changing the ROM.)
- Click [Reboot System]
It works on 31.05.2016 / 08.06.2016 ROM Good luck:laugh::good:
Remember before you do the next update OTA need to do a flash recovery on the orginal.
=============== OTA 2016.06.08 =============== OTA 2016.06.08 ===============
If you have root before installing OTA flash orginal P9000 recovery from p9000_RECOVERY.zip
- Unzip p9000_RECOVERY.zip
- Open SP_Flash_Tool_Windows_v5.1520.00.000
View attachment 3779843
- Select the MT6755_Android_scatter.txt file from p9000_RECOVERY folder. (1)
- Turn off the phone
- Click Download button. (3)
- Connect the phone (turned off) to a USB Port.
Program after recognizing phone will flash recovery and display Download OK. Done
Now you can do the OTA update
- For safety before you do OTA remove fingerprints from the security options.
- Remove the SD card (if inserted), insert the SIM card into the slot 1.
- Make OTA update.
- Again ROOT the phone. (Install TWRP 3.0.2 Recovery and UPDATE-SuperSU-v2.65) see above.
It works on 08.06.2016 ROM Good luck:laugh::good:
Click to expand...
Click to collapse
I am getting error :
"---------------------------
Smart Phone Flash Tool
---------------------------
BROM ERROR : STATUS_DEVICE_CTRL_EXCEPTION (-1073414143)
[HINT]:
---------------------------
&OK
---------------------------
"
I am on P9000_Android_6.0_20160419. Trying to flash 08.06.2016 ROM. Or even TWRP
All drivers installed properly. I could not find any solutions anywhere else. Any ideas?
Error: Initialize scatter file failed. Please check the scatter file name you load is legal.
Can somebody help?
Mariocorn said:
I am getting error :
"---------------------------
Smart Phone Flash Tool
---------------------------
BROM ERROR : STATUS_DEVICE_CTRL_EXCEPTION (-1073414143)
...
I am on P9000_Android_6.0_20160419. Trying to flash 08.06.2016 ROM. Or even TWRP
All drivers installed properly. I could not find any solutions anywhere else. Any ideas?
Click to expand...
Click to collapse
On the elephone forum from hong kong (look at google) someone wrote that solved this problem by installing new drivers, you can try.
[What's your system? Maybe try a different]
good luck
Ant-man said:
Error: Initialize scatter file failed. Please check the scatter file name you load is legal.
Can somebody help?
Click to expand...
Click to collapse
Check the archive, may download again or from other sources.
Good luck
Cheers
I used different laptop ( both with Windows 10, but AMD vs Intel) It worked .
demien_max said:
On the elephone forum from hong kong (look at google) someone wrote that solved this problem by installing new drivers, you can try.
[What's your system? Maybe try a different]
good luck
Click to expand...
Click to collapse
after resetting to stock recovery i got the message "no command" when trying to enter recovery menu with vol+ + power button. Any Ideas how to solve this?
Already flashed back to TWRP and then to stock recovery but still the same problem
catboy84 said:
after resetting to stock recovery i got the message "no command" when trying to enter recovery menu with vol+ + power button. Any Ideas how to solve this?
Already flashed back to TWRP and then to stock recovery but still the same problem
Click to expand...
Click to collapse
Try flash recovery from the last ROM. Write if it works, good luck.
If you're trying to flash the entire rom it should work but flashing OTA's to an older firmware version sometimes errors out as the firmware doesn't have the correct base... I.E. - you're missing essential services and files from the other OTA's missed .
Do not work with Nougat 7.1.1 / 32.4.A.0.160 (Bootloop)
New TWRP (You dont need otg and mouse anymore!):
https://www.androidfilehost.com/?fid=745425885120733410 (thanks to andralex8!)
GUIDE UPDATED, TESTED AND SIMPLIFIED 15.2.2017 (thanks to munjeni)
Tested with Saudi Arabia, Germany and Nordic (.378) firmwares
I managed to get my Xperia Z4 Tablet (SGP771) LTE model to have root, TWRP-recovery*, munjenis DRM fix and Adaway working with Nougat firmware (Saudi Arabia). I will share steps that I have done with my own tablet. If this guide brick your device or something goes wrong, I am not responsible for loss of your device. Use this guide only with your own RISK!
This tutorial is not for beginners. You need to have working adb installed yout pc, unlocked tablet, sonys special driver for fastboot. and TA backup (example TA-21062016.img). Use only this tutorial with Sony USB-cable.
*To get TWRP working, you need: OTG-cable and a mouse with wire or wireless mouse with a dongle.
0. Download Nougat 32.3.A.0.376 (Saudi Arabia) firmware with Xperiafirm 32.3.A.0376. to your PC
1. Flash Nougat 32.3.A.0.376 (Saudi Arabia) with Flashtool 0.9.23.2.
2. Boot your device and enable Developer settings from setting
3. Enable USB debugging setting from Developer settings
4. Download Supersu and Magisk to your device:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
http://tiny.cc/latestmagisk
5. Shutdown your device
6. Download munjenis DRM fix and serajr script package v2 to your pc:
http://munjeni.myiphost.com/ta_poc.rar
https://forum.xda-developers.com/showpost.php?p=70959962&postcount=65
7. Decompress files from munjeni and serajir to same folder.
8. Extract kernel.sin from your nougat firmware ftf (You can use 7zip to do this). Copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin
9. Copy your TA backup to same folder with DRM fix and rename it TA.img
10. Open Cmd with admistrator persimmions and use DOUBLECLICKME_NOUGAT.bat (search cmd rght mouseclick use admistrator).
11. Follow munjenis tool tutorial: You can choose if you want Sony Ric off. I left it on but turned dm verity off.
12. Download TWRP: https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8cnhQamtxRWVtRmc
13. Press vol up and connect your device to pc to use fastboot. Use command: fastboot flash boot new_boot.img
14. After that use command: fastboot flash recovery TWRP-3.0.2-0-20160604.img
15. Disconnect your device and put otg-cable to tablets usb and connect mouse to otg-cable.
16. Press vol down + power to boot to TWRP. Touchscreen is not workin but you can use your mouse to navigate in TWRP!
17. Allow TWRP to make changes to your device and flash Supersu 2.79 and Magisk 11.1.
18 Boot your device and install magisk manager from the play store.
19. Enable from magisk manager settings: busybox, magisk hide and systemless hosts and Install Adaway (Will not work without Magisk, strange).
I have not managed to get my CTS profile approved but that is not major issue if not playing with Pokemon go (You can use magisk to detect this).
Note1 : Change LTE to 1 priority from mobile setting. Default for SA firmware is GSM
Note2: If you have already tried rootkernel to get drm working; do a full wipe and reflash firmware with flashtool. Rootkernel messes something. Tablet do not boot if you have used rootkernel and after that try to use munjenis DRM fix.
Note3: Magisk 11.1 wont work with Xperia Z4 Tablet without Supersu. So flash Supersu first and Magisk 11.1 after that
Note4: You cannot boot to TWRP by using root and reboot to recovery apps. You need to boot to the recovery with keycommand voldown+power
I hope this guide helps some fellow flashers
Special thanks for
munjeni
serajr
Chainfire
Androplus
topjohnwu
Teamwin
Androxyde
mrRobinson
If I forgot someone I am truly sorry!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just tried unable to boot to recovery
sahilg009 said:
Just tried unable to boot to recovery
Click to expand...
Click to collapse
Did you do a full wipe? Try to fastboot flash boot new_boot.img after flashing recovery!
Tried wiping now flashing kernel gives me a no sim card error
sahilg009 said:
Tried wiping now flashing kernel gives me a no sim card error
Click to expand...
Click to collapse
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
halfvast said:
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
Click to expand...
Click to collapse
Even tried that still giving me signal problem
sahilg009 said:
Even tried that still giving me signal problem
Click to expand...
Click to collapse
Strange, I Did not encourter this problem because I could boot to TWRP and do adb trick there. Do you use orginal Sony usb to flash in fastboot? I had once a problem with Samsung Phone (S7) to flash recovery because the usb was not the one that came with my Phone.
Yeah
Try redownload TWRP image and flash it. If not working do a clean flash and try again or wait for Androplus kernel
Tried it all nothing worked still no sim error
sahilg009 said:
Tried it all nothing worked still no sim error
Click to expand...
Click to collapse
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
halfvast said:
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
Click to expand...
Click to collapse
Couldnt I just do the root and recovery method you have given on the wifi version as im not too bothered about drm fix for now as it looks abit complicated at the moment for me. It would be much more simple for me to flash recovery then super su. I just wanna know if this is possible?
Thanks
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
halfvast said:
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
Click to expand...
Click to collapse
Ok then dont think id like to try incase it doesnt boot so I think I might just wait for andro to do his stuff.
I have updated the guide and tested it today (13.2.2017) and it is working again
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
halfvast said:
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
Click to expand...
Click to collapse
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
RJASSI21 said:
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
Click to expand...
Click to collapse
You need to extract it from ftf-image. I used 7zip. My device was Nee with stock. I used DE with Marshmallow and I am currently using Saudi Arabia. So I dont think it will matter, which kernel you use with your device. But I would use same kernel version with rom. So If you are using Saudi Arabia rom use Saudi Arabia kernel. For Russia rom use Russia kernel, and so on
I will add tft-image extract to tutorial!
DRM fix doesn't work. XReality (among other things I assume) are ever disabled.
On Marshmallow DRM fix was working fine (was using XReality engine despite the unlocked bootloader)
For me it is working!