[Q] [D2303] x17 ROM root - Sony Xperia M2

Hi, i couldn't find any way to root x17 stock ROM on d2303 with unlocked bootloader. Kingroot is not an option. Can anyone help?
Wysłane z mojego D2303 przy użyciu Tapatalka

karden.pl said:
Hi, i couldn't find any way to root x17 stock ROM on d2303 with unlocked bootloader. Kingroot is not an option. Can anyone help?
Wysłane z mojego D2303 przy użyciu Tapatalka
Click to expand...
Click to collapse
Hi,I root my with Kingroot but after this replace kingo with supersu
Requirements:
Rooted Android device with Kinguser App installed.
Android Terminal Emulator App. this have at google play
Es File Explorer App.
Replacing Kinguser with SuperSU tool ver (i am not able to post outside links -mail me [email protected])
Replacing Steps:
Download the required zip tool, install “Android Terminal Emulator” and “Es File Explorer”.
Extract “Replace_Kinguser_with_SuperSU-vx.x.zip” to: /sdcrad/ directory.
Open “Terminal Emulator” and type:
su
suthen enter.
Give root permission to the emulator by tapping Allow.
Terminal Kinguser Permission
Type:
sh /sdcard/mrw/root.sh
sdcard mrw root.shthen enter.
Don’t touch your device and wait.
Once done, SuperSu App will launch automatically, if not launch it manually.
Update SU binary by tapping CONTINUE > NORMAL, don’t click TWRP/CWM, wait until it finish, then REBOOT your device.
( I must repeat,but second time work)
Check your device’s App drawer, you will find that this tool replace Kinguser and related applications with SuperSU.
Download “Root Checker” App to check if your device still have root access or not.
Notes:
Make sure you place “mrw” folder into /sdcard/, if not it will not work.
su and sh /sdcard/mrw/root.sh must be typed in lowercase-dont forget space between sh and slash
You can delete “mrw” folder after using it.
Check Google Play Store if there is update for SuperSU App to install it.

Did you not read his post "kingroot is not a option" I wouldn't use it if it was the only to get root sooner go without. Closed source for a start it could contain anything.
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.

karden.pl said:
Hi, i couldn't find any way to root x17 stock ROM on d2303 with unlocked bootloader. Kingroot is not an option. Can anyone help?
Wysłane z mojego D2303 przy użyciu Tapatalka
Click to expand...
Click to collapse
If KingRoot is not an option, use the downgrade method. It works flawlessly.
Use this: https://www.reddit.com/r/RootIt/comments/36ql1q/xperia_m2_1831c115_any_root_alternatives/

x17 ROM root
I used the 4.4.2 kernel (with CWM recovery) to flash superSU.zip after that I just flashed the x13 kernel of 4.4.4 and it works fine except its says in update centre to update firmware (to x17).Working fine with me. I am using D2303 rooted with unlocked bootloader.

Related

[ROOT][XM]Rooting Xperia M Using Framroot|Installing Busybox

Steps for Rooting
-download framroot(Download link given)
2-install framroot
3-Open framroot
4-You have to select install supersu
5-then select gandalf exploit wait for few seconds a
pop up message comes sucess ..........
6-do nothing the phone will reboot itself when the
phone turns on u will see super su is installed and u
have ur xperia m rooted
note: some time ur phone will b rooted with the first
attempt but i had tried these steps 3 times to get
rooted my xperia m for the first time(actually my friends xperia m) . but
some time u will get rooted ur phone with single
attempt so dont worry
-thats it....your xperia m is rooted sucessfully
Installing Busybox
1-download busybox
2-install busybox and open it wait for some time and
grand super su request
3-wait for some time busybox loads tweaks after
loading completes there is a install button on bottom
left corner click install then choose normal
4-busy box installs tweaks after compleation of
installation sucess popup message comes
5-installation of busy box is sucessfull
note:some time the phone will reboot in between the
busybox installation dont worry follow from the 3rd
steps. this is because of the system folder read write
error
-Done
Downloads
FRAMROOT>http://hotfile.com/dl/235017958/2abe894/
Framaroot.apk
Reserved For Changelogs
New download link
http://mediafire.com/?c5t0lav9j8e9tfh
I got this method sent to me and I shared it apparently only doing the first two steps installing framaroot then busybox it's only half rooted and requires another step here is the link for the method I was shown
http://forum.xda-developers.com/showthread.php?t=2457174
Sent from My Sony Xperia M C1905
dunc4n88 said:
I got this method sent to me and I shared it apparently only doing the first two steps installing framaroot then busybox it's only half rooted and requires another step here is the link for the method I was shown
http://forum.xda-developers.com/showthread.php?t=2457174
Sent from My Sony Xperia M C1905
Click to expand...
Click to collapse
Gud work

[NEW] [FTF] [4.4.4] [26.06.2015] Xperia M2 [18.3.1.C.1.16]

This is a minor update for D2303, later today I will upload for every phone variant. This might be the latest KitKat update since we are expecting Android 5.1 later this year. You can find more info about the update here
1. D2303 18.3.1.C.1.16 Customized CE1 (Central Europe)
{
"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"
}
Download links:
GOOGLE DRIVE
2. D2303 18.3.1.C.1.16 Customized PT (Portugal)
Download links:
GOOGLE DRIVE
D2403 CE1 also got an update 1.16. Just checked that.
D2303 Customized UK still waiting
D2303 18.3.1.C.1.15 kk deodexed, rooted, philz touch recovery, xposed, z1 bravia engine 2 + x-reality+ z3 super vivid, viper audio
My PC got some hard disk problems and I couldn't do much about it. Since I've fixed it now, give me some time to upload them all
Do i need to update to 18.3.1.C.1.15 first or can I update right to this using cyanogen recovery? Sorry, I'm new to Sony Android (much different that htc, samsung, and OPO), but what exactly is an ftf?
shiboby said:
Do i need to update to 18.3.1.C.1.15 first or can I update right to this using cyanogen recovery? Sorry, I'm new to Sony Android (much different that htc, samsung, and OPO), but what exactly is an ftf?
Click to expand...
Click to collapse
FTF is a file that contains the firmware of the phone. Use FlashTool to flash it. Yes, you can upgrade to .16 without actually flashing .15 firmware
I can't get the flashtool to download from uploaded.to (I even have an account for that) or userscloud, it keeps failing. Does anyone have another mirror for it? Or can I use Emma for this?
shiboby said:
I can't get the flashtool to download from uploaded.to (I even have an account for that) or userscloud, it keeps failing. Does anyone have another mirror for it? Or can I use Emma for this?
Click to expand...
Click to collapse
Emma? No. Use the torrent link or the usercloud. You might find mirrors from previous versions
Avast found a virus in HostSearchProtocol.exe. Does anyone know about this?
shiboby said:
Avast found a virus in HostSearchProtocol.exe. Does anyone know about this?
Click to expand...
Click to collapse
If talking about Flashtool, it's false/positive because of the rooting stuff that Flashtool have. If you download and Avast delete some stuff you'll be able to flash ftf but root will give you an error.
Xperia M2 D2303 on K.K. 4.4.4
DavidMKD said:
Emma? No. Use the torrent link or the usercloud. You might find mirrors from previous versions
Click to expand...
Click to collapse
Emma is the sony flash program that I used to a custom recovery on the phone. I have the flashtool downloaded and installed from the link you provided. Is there any particular proceedure I should follow? Anything I should keep in mind while using this? I look for a guide on the website you linked to, but didn't find anything.
Also, is there a way to back up everything in case I want to restore to factory later?
shiboby said:
Emma is the sony flash program that I used to a custom recovery on the phone. I have the flashtool downloaded and installed from the link you provided. Is there any particular proceedure I should follow? Anything I should keep in mind while using this? I look for a guide on the website you linked to, but didn't find anything.
Click to expand...
Click to collapse
If you are on Windows 8 and up disable driver signature reinforcement. For Windows 7 is not required. After that download the FTF file and put it in C:\Users\(yourusername)\.flashTool\firmwares. Open flashtool folder and install the drivers provided in the drivers firmware (check them all if you are not sure which one to get). Restart your PC and open the flashtool program (FlashTool64 if you are running 64 bit system), after that press that lightning (flash button) -> select flashmode -> select your firmware and press ok. Follow the instructions given after that
Thanks to your help, I've been running c.1.16 for several days now, but I'm having some problems I hope you could help me with. First, some apps see that I have root some don't. After getting C.1.16 installed, i went into cyanogen recovery and flashed news supersu. However, while Greenify, Avast, Root Check, and some other apps recognize the phone as rooted, some other progams, like Root App Deleter, do not.
Furthermore, I am having problems saving to and accessing the MicroSD with apps. I've checked it in my computer and it works just fine. I google searched and see that this is a known issue with KitKat (although one I never had on my Samsung or Oneplus). I found several tutorials for remedying this and I try to follow the instructions for modifying platform.xml. However, after I insert the line of code and hit save, everytime I get the following error: "Can'twrite file: /system/etc/permissions/platform.xml open failed: EROFS (Read-only file system). This is causing problems as I want to backup data, with apps like ROM Toolbox Pro, and they always fail.
Any ideas on how to resolve these two issues?
shiboby said:
Thanks to your help, I've been running c.1.16 for several days now, but I'm having some problems I hope you could help me with. First, some apps see that I have root some don't. After getting C.1.16 installed, i went into cyanogen recovery and flashed news supersu. However, while Greenify, Avast, Root Check, and some other apps recognize the phone as rooted, some other progams, like Root App Deleter, do not.
Furthermore, I am having problems saving to and accessing the MicroSD with apps. I've checked it in my computer and it works just fine. I google searched and see that this is a known issue with KitKat (although one I never had on my Samsung or Oneplus). I found several tutorials for remedying this and I try to follow the instructions for modifying platform.xml. However, after I insert the line of code and hit save, everytime I get the following error: "Can'twrite file: /system/etc/permissions/platform.xml open failed: EROFS (Read-only file system). This is causing problems as I want to backup data, with apps like ROM Toolbox Pro, and they always fail.
Any ideas on how to resolve these two issues?
Click to expand...
Click to collapse
First problem, try reinstalling SuperSU again with the latest binaries and check the log if something is wrong. Second use this command line in ADB, if it doesn't work use NextApp SDFix
Code:
su
mount -o remount,rw /system
busybox sed -i -e "/WRITE_EXTERNAL_STORAGE/,/<\/permission>/ s#^\(.*</permission>\)#\\t<group gid=\"media_rw\" />\\n\\1#" /system/etc/permissions/platform.xml
DavidMKD said:
First problem, try reinstalling SuperSU again with the latest binaries and check the log if something is wrong. Second use this command line in ADB, if it doesn't work use NextApp SDFix
Code:
su
mount -o remount,rw /system
busybox sed -i -e "/WRITE_EXTERNAL_STORAGE/,/<\/permission>/ s#^\(.*</permission>\)#\\t<group gid=\"media_rw\" />\\n\\1#" /system/etc/permissions/platform.xml
Click to expand...
Click to collapse
First problem
so i have supersu 2.46 which is the newest stable one. Should i go to 2.49 beta?
Second problem
adb isn't recognizing the phone. nothing is listed when i type "adb devices." so i used terminal emulator which said busybox isn't found. do i need to install busybox? I tried downloading the installer from play store,but it failed to install busy box. also NextAPP failed, it said it couldnt write to the xml file.
Sounds like Sony ric is still active if you don't have r/w permissions, have you tried connecting your phone to flashtool and forcing root with flashtool. Or run Sony ric killer on PC
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
[email protected] said:
Sounds like Sony ric is still active if you don't have r/w permissions, have you tried connecting your phone to flashtool and forcing root with flashtool. Or run Sony ric killer on PC
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
Click to expand...
Click to collapse
Not familiar with sony ric or forcing root with flashtool can you give me a walkthrough? I do have some root required applications running: adblocker, avast, ROM Toolbox (except it cant save to microsd), greenify, and a few more.
Here's the guide I followed to root my m2.
http://forum.xda-developers.com/showthread.php?p=53595220. just search on here for for Sony ric killer. It's sonys way of a read only system
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
[email protected] said:
Here's the guide I followed to root my m2.
http://forum.xda-developers.com/showthread.php?p=53595220. just search on here for for Sony ric killer. It's sonys way of a read only system
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
Click to expand...
Click to collapse
thats the guide i followed too to root. found and installed ricdefeat. still cant get newapp sd card fix or busybox installer to work
shiboby said:
thats the guide i followed too to root. found and installed ricdefeat. still cant get newapp sd card fix or busybox installer to work
Click to expand...
Click to collapse
I use this one
http://forum.xda-developers.com/showthread.php?p=58099150
And i don't have problem with root.
To make ext card writable go to
/system/etc/permissions
In platform.xml find :
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
You'll be missing " media_rw" part, add it, save, reboot. You need root for this, so first resolve rooting part
You can look on XDA for MiXplorer it's best explorer.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4

Root Nougat 32.3.A.2.33 (E6833 E6853 E6883) 1APR2017

UPDATE 01-APRIL2017
32.3.A.2.33 HAS BEEN RELEASED
ROOTED MODIFIED STOCK KERNELS CAN BE FOUND AT
https://forum.xda-developers.com/z5-premium/general/rooted-stock-modified-kernels-32-3-0-t3556874
IF YOU WANT TO ROOT YOUR NEWLY PURCHASED DEVICE PLEASE READ THE PROCESS BELOW THOROUGHLY
UPDATE 21-FEB2017
modified kernel added for 32.3.A.0.378 (E6853) (NOBA) ONLY
https://mega.nz/#F!3FYhTbSC!9MraM-zYNRNMPzmTkSSs9g
ref : https://forum.xda-developers.com/z5-premium/general/rooted-stock-modified-kernels-32-3-0-t3556874
---------------------------------------
UPDATE 16-FEB2017
REPOSITORY OF ROOTED KERNELS BY @tobias.WALDVOGL SCRIP https://mega.nz/#F!3FYhTbSC!9MraM-zYNRNMPzmTkSSs9g
----------
UPDATE 9FEB2017
32.3.A.0.376 IS OUT
ROOTKERNEL 5.20 BY @tobias.waldvogel SUPPORTS ALSO SUPERUSER https://superuser.phh.me/
-install superuser apk from playstore after flashing the zip file
-to give write permissions to system folder install busybox and via terminal type
Code:
su
mount -o rw,remount /system
-remove apps by system app remover
https://forum.xda-developers.com/showpost.php?p=70945409&postcount=21 / thanks @sceryavuz
UPDATE 31JAN2017
ROOTKERNEL for N is out / for unlocked boot loaders, extract kernel.sin to kernel.elf from 32.3.A.0.372.ftf and just repack it as boot.img and flash it.
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
thank so sir @tobias.waldvogel
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in terminal
Code:
su
mount -o rw,remount /system
-----------
UPDATE 27JAN2017
UPDATED WORKAROUND FOR DRM FIX, AND SONY RIC OFF ( 32.3.A.0.372 )
https://forum.xda-developers.com/showpost.php?p=70595975&postcount=1702
WHERE SONY RIC SWITCH-OFF CHECK POSTED HERE (if you get system mount error while removing bloatware
https://forum.xda-developers.com/showpost.php?p=70677335&postcount=92
...
UPDATE 17JAN2017
VERSION 32.3.A.0.372 - android N is out!
preparation
place in sd card SR5 2.78 superSU .
there is NO KNOWN DIRECT METHOD TO MODIFY KERNEL of 32.3.A.0.372 (YET) so the work around is posted by
https://forum.xda-developers.com/showpost.php?p=70595975&postcount=1702 ( by @serajr )
extract kernel as elf (by flashtool) from ftf file of .372 and use the same root kernel to build your custom kernel and put inside the following zip file at
https://forum.xda-developers.com/attachment.php?attachmentid=4006777&d=1484669198
there is no known direct way to edit kernel (yet) so the there is work around
Flash nougat with flashtools ( I erased everything so back up your photos videos etc)
2.After initial boot complete startup wizard.
3. Put attached file into root of sdcard
4. using classic adb ~ boot into fastboot and type fastboot boot boot.img image that has TWRP ( of MM Kernel) I used the one from latest MM
5. Boot into TWRP
6. Flash Zip and you're in.
https://forum.xda-developers.com/attachment.php?attachmentid=4006777&d=1484669198
thanks to @serajr
i will keep you posted
-----------------
UPDATE 7-DEC-2016
VERSION 32.2.A.5.11 IS OUT
download kernel for E6833
https://drive.google.com/open?id=0BwsQ_NLVjA_QMXNvRFNhOU1fYkE
flash SR3-SuperSU-v2.78-SR3-20161103171345 via twrp
reboot into system
u have ROOTED z5p e6833
@KbaB.BroS
plz help for rest of the kernels
UPDATE 5-NOV-2016
- SuperSU SR2 2.78 (flashable zip) working PERFECTLY on 32.2.A.0.305 on Kernel by @KbaB.BroS
https://mega.nz/#F!7gRDBIJY!af8WZfXMno2Pm_OgEMSqNQ (IMG FILES)
just flash superSU over previous one via recovery!
--------------------------------------------------
UPDATE 11-10-2016
NEW UPDATE 6.01 - 32.2.A.0.305 - OCT2016 has been pushed
THANKS TO @KbaB.BroS for updating E6XXX (all varients , kernels)
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!6hZj1DyK (depository of kernels)
i have tested my device, did NOT BRICK.
twrp working
flashed RC1 supersu2.78 ZIP
ROOTED
_______________________________________________________________________
This post is inspired/ result of work by following respected users
@KbaB.BroS , @tobias.waldvogel @Shadowboy23 @Fragmentation
Similar post (guide)
http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
GLOBAL thanks to following respected members for their valuable work
@Androxyde — Flashtool
@IgorEisberg — XperiFirm (integrated into Flashtool)
@Dees_Troy et al. — TWRP
@Chainfire — SuperSU
@zxz0O0 — iovyroot
MY VERSION ~ (HOW I DID IT)​focusing on z5p (all variants) however the process is same for Z5 variants and z3+ / Z3 / Z3 compact and all variants too​
SUMMARY
1. downgrading your 5.1.1
2. rooting
3. extracting DRM KEYS (ORIGINAL)
4. unlocking bootloader
5. FLASHING STOCK MODIFIED kernel (having recovery installed)
6. going in to recovery and flashing superSU.​
Before you begin must do/have following
Download SU and put it in your SD CARD - CLICK HERE
TAKE FULL BACKUP, CONTACTS, GALLERY, VIDEOS, EVERYTHING. Keep usb debugging ON ( I used Titanium backup )
Driver installed (sony pc companion will do that) ( http://support.sonymobile.com/global-en/tools/xperia-companion/ )
Install FlashTOOL ( http://www.flashtool.net/downloads_windows.php ). and after installing flashtool, install
motherboard drivers (of your device) C:\Flashtool\drivers
NOW, goto http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ , select your device xperia z5 premium from dropdown list and follow the instructions
To be able to unlock your Xperia Z5 Premium Dual, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning: Device protection features will not work on this device while this setting is turned on.Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked. Continue to http://developer.sonymobile.com/unlockbootloader/email-verification/ , give your email ID and they will send you link asking you your device's IMEI Number. once you give that sony will email you YOUR BOOTUNLOCK KEYS within minutes. (keep them aside for now)
NOW IF YOU ARE RUNNING Z5P ON LATEST FIRMWARE "32.2.A.0.253" AND "DONOT WANT TO RESTORE YOUR DRM KEYS" --- SKIP TO NO.5
4. --DOWNGRADING XPERIA Z5 TO LOLLIPOP 5.1.1 - IN ORDER TO RESTORE DRM KEYS
a. run FLASHTOOL, and click XPERIFIRM BUTTON, it will launch XPERIFIRM, select your device (eg. xperia z5p "satsuki" , E6833) here you will see CDA 1299-7506 build number "32.0.A.6.115 R2B". this is the base version of z5p at which your device left sony Factory (LP kernel)
b. download this version (1.9gb)
c. now FLASH (downgrade) your z5p with .115 using FLASHTOOL. tutorial can be found here ( http://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614 )
d . restart device, gothru the setup, enable wifi etc, download KINGROOT and root your android 5.x.x ( OR YOU CAN USE IVORYROOT ) ~ AS SOME MEMBERS SAY KINGROOT STORES DEVICE DETAILS ON THEIR CHINESE SERVER etc )
f. you are ready now to extract your DRM-KEYS / TA BACKUPS (FIDO KEYS) . use this simple TOOL given with tutorial at https://github.com/DevShaft/Backup-TA/releases // it will save your keys from ROOTED z5p , (allow root access to this application on your mobile screen)
g. WHY HAVING TA BACKUPS ? frankly I if you don't restore it, keeping your one time SONY given unique valuable keys of your device and having backup for future is logical.
unlocking bootloader.
- make sure the device is fully charged, (atleast 80%)
- IF your device has Android LP(5.x.x) / or MM (6.x.x) and you want to make TA backups, then GOBACK to point NO.4
- IF your device has Android LP(5.x.x) / or MM (6.x.x) and not interested in taking TA BACKUPS then proceed to
NO.5
Click to expand...
Click to collapse
5. while device is switch-off, click "BLU" button on FLASHTOOL, follow the instructions. when FLASHTOOL ASK KEY, paste the KEY sent to you by SONY ( read NO.3 ). the device will be unlocked and should boot. the first boot will take a while and everything will be wiped from your z5p (TA partitions, DRM KEYS, USER APPS, USER DATA.
if your device is already running on android 6.01 (32.2.A.0.253) then skip to NO.7.
Click to expand...
Click to collapse
6. again using xperifirm in FLASHTOOL download 32.2.A.0.253 for your Device and by using FLASHTOOL, Flash your Z5P. the TUTORIAL of flashing any xperia phone can be found HERE
7. @KbaB.BroS has build repository of modified STOCK KERNAL for z5p (all variants) running on .253 at HERE. download the .img file and FLASH your KERNEL it via flashtool.
while your device is charged and switch off after UNLOCKING BOOT LOADER (having .253 buildnumber)
click the THUNDER icon on flashtool
select FASTBOOT MODE
click "select kernal to flash"
connect device by toggling volume up/down keys as per instructions by FLASHTOOL.
FlashTool then, will ask .img file location. point it to the .img file. and your kernel will be flashed in 1 second
BOOT your device, on SONY LOGO press volume up, the led will turn AMBER, and you will TWRP recovery.
select install from zip, and flash the SUPERUSER .zip which you placed in your SD CARD in the VERY BEGINNING.
REBOOT YOUR DEVICE.
CONGRATULATIONS on ROOTED z5p ​
WHAT TO DO if your device is NOT z5p ?
using FLASHTOOL you can create your OWN modified kernel by
Downloading your device' latest build by SONY using XPERIFIRM (some 2.x GB of ftf file) , once done ..
EXTRACT the TFT file using 7zip
in flashtool click TOOLS>> SIN EDITOR >> in the extracted data, find kernel.sin and dump it as kernel.elf
DOWNLOAD TOOL "rootkernel_v5.0_rc4_Windows_Linux" mention at http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605, extract it,
Place the KERNEL.ELF file in this folder and open command prompt in that folder (right click menu while pressing shift key
type "roodkernel kernel.elf boot.img " it will ask four important questions, disabling dm-varity (yes), disabling sonyRIC (yes), installing busybox (no), installing recovery (YES) and later it will creat boot.img file of your device's variant.
FLASH YOUR CREATED .img file as explain in point no.7
Big Thanks to you bro
Working Perfect on E6833
kofta2020 said:
Big Thanks to you bro
Working Perfect on E6833
Click to expand...
Click to collapse
you are welcome,
yasuhamed said:
this post is inspired/ result of work by following respected users
@kbab.bros , @tobias.waldvogel @shadowboy23 @fragmentation
similar post (guide)
http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
global thanks to following respected members for their valuable work
@androxyde — flashtool
 @igoreisberg — xperifirm (integrated into flashtool)
@dees_troy et al. — twrp
@chainfire — supersu
 @zxz0o0 — iovyroot
my version ~ (how i did it)​focusing on z5p (all variants) however the process is same for z5 variants and z3+ / z3 / z3 compact and all variants too​
summary
1. Downgrading your 5.1.1
2. Rooting
3. Extracting drm keys (original)
4. Unlocking bootloader
5. Flashing stock modified kernel (having recovery installed)
6. Going in to recovery and flashing supersu.​
before you begin must do/have following
download su and put it in your sd card - click here
take full backup, contacts, gallery, videos, everything. Keep usb debugging on ( i used titanium backup )
driver installed (sony pc companion will do that) ( http://support.sonymobile.com/global-en/tools/xperia-companion/ )
install flashtool ( http://www.flashtool.net/downloads_windows.php ). And after installing flashtool, install
motherboard drivers (of your device) c:\flashtool\drivers
now, goto http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ , select your device xperia z5 premium from dropdown list and follow the instructions
to be able to unlock your xperia z5 premium dual, prepare it by following these steps:
Go into settings > about phone and tap seven times on build number to enable developer options.
From settings, go into developer options and enable oem unlocking.
Warning: Device protection features will not work on this device while this setting is turned on.please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap service info > configuration > rooting status. If bootloader unlock allowed says yes, then you can continue with the next step. If it says no, or if the status is missing, your device cannot be unlocked. Continue to http://developer.sonymobile.com/unlockbootloader/email-verification/ , give your email id and they will send you link asking you your device's imei number. Once you give that sony will email you your bootunlock keys within minutes. (keep them aside for now)
now if you are running z5p on latest firmware "32.2.a.0.253" and "donot want to restore your drm keys" --- skip to no.5
4. --downgrading xperia z5 to lollipop 5.1.1 - in order to restore drm keys
a. Run flashtool, and click xperifirm button, it will launch xperifirm, select your device (eg. Xperia z5p "satsuki" , e6833) here you will see cda 1299-7506 build number "32.0.a.6.115 r2b". This is the base version of z5p at which your device left sony factory (lp kernel)
b. Download this version (1.9gb)
c. Now flash (downgrade) your z5p with .115 using flashtool. Tutorial can be found here ( http://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614 )
d . Restart device, gothru the setup, enable wifi etc, download kingroot and root your android 5.x.x ( or you can use ivoryroot ) ~ as some members say kingroot stores device details on their chinese server etc )
f. You are ready now to extract your drm-keys / ta backups (fido keys) . Use this simple tool given with tutorial at https://github.com/devshaft/backup-ta/releases // it will save your keys from rooted z5p , (allow root access to this application on your mobile screen)
g. Why having ta backups ? Frankly i if you don't restore it, keeping your one time sony given unique valuable keys of your device and having backup for future is logical.
unlocking bootloader.
5. while device is switch-off, click "blu" button on flashtool, follow the instructions. When flashtool ask key, paste the key sent to you by sony ( read no.3 ). The device will be unlocked and should boot. The first boot will take a while and everything will be wiped from your z5p (ta partitions, drm keys, user apps, user data.
6. again using xperifirm in flashtool download 32.2.a.0.253 for your device and by using flashtool, flash your z5p. The tutorial of flashing any xperia phone can be found here
7. @kbab.bros has build repository of modified stock kernal for z5p (all variants) running on .253 at here. Download the .img file and flash your kernel it via flashtool.
while your device is charged and switch off after unlocking boot loader (having .253 buildnumber)
click the thunder icon on flashtool
select fastboot mode
click "select kernal to flash"
connect device by toggling volume up/down keys as per instructions by flashtool.
flashtool then, will ask .img file location. Point it to the .img file. And your kernel will be flashed in 1 second
boot your device, on sony logo press volume up, the led will turn amber, and you will twrp recovery.
select install from zip, and flash the superuser .zip which you placed in your sd card in the very beginning.
reboot your device.
congratulations on rooted z5p ​
what to do if your device is not z5p ?
using flashtool you can create your own modified kernel by
downloading your device' latest build by sony using xperifirm (some 2.x gb of ftf file) , once done ..
extract the tft file using 7zip
in flashtool click tools>> sin editor >> in the extracted data, find kernel.sin and dump it as kernel.elf
download tool "rootkernel_v5.0_rc4_windows_linux" mention at http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605, extract it,
place the kernel.elf file in this folder and open command prompt in that folder (right click menu while pressing shift key
type "roodkernel kernel.elf boot.img " it will ask four important questions, disabling dm-varity (yes), disabling sonyric (yes), installing busybox (no), installing recovery (yes) and later it will creat boot.img file of your device's variant.
flash your created .img file as explain in point no.7
Click to expand...
Click to collapse
thank you very much working on d6853 no issues so far
Is there any modified STOCK KERNAL for Z5 (dual)? or anything similar which contains TWRP recovery? I've been searching a lot of threads but I can't seem to find any. Thanks for the reply.
In which step are the DRM keys recovered/restored?
konstantinos3 said:
In which step are the DRM keys recovered/restored?
Click to expand...
Click to collapse
at the end you can restor DRM KEYS using same tool
https://github.com/DevShaft/Backup-TA/releases
however the Kernels by @KbaB.BroS already have DRM Stimulation so as of now even if you don't restore keys, it will be just fine. however keeping them SAFE for any future situation would be RECOMENDED
adize said:
Is there any modified STOCK KERNAL for Z5 (dual)? or anything similar which contains TWRP recovery? I've been searching a lot of threads but I can't seem to find any. Thanks for the reply.
Click to expand...
Click to collapse
you will find z5p (dual (e6833/53/83) ) modified stock kernels at
https://mega.nz/#f!kwzhjlik!unbdzr6lcxmaaw7jkfs1wq!uljjkdbj
thanks to @kbaB.bro
adize said:
Is there any modified STOCK KERNAL for Z5 (dual)? or anything similar which contains TWRP recovery? I've been searching a lot of threads but I can't seem to find any. Thanks for the reply.
Click to expand...
Click to collapse
you will find z5p (dual (e6833/53/83) ) modified stock kernels at
https://mega.nz/#f!kwzhjlik!unbdzr6lcxmaaw7jkfs1wq!uljjkdbj
thanks to @KbaB.BroS
Knows someone who can I Root mijn Sony Xperia Z5 premium dual sim? Please help!
Sent from my E6833 using XDA Free mobile app
YasuHamed said:
at the end you can restor DRM KEYS using same tool
https://github.com/DevShaft/Backup-TA/releases
however the Kernels by @KbaB.BroS already have DRM Stimulation so as of now even if you don't restore keys, it will be just fine. however keeping them SAFE for any future situation would be RECOMENDED
Click to expand...
Click to collapse
In case I don't want simulation, will the keys be restored normally onto these Kernels?
konstantinos3 said:
In case I don't want simulation, will the keys be restored normally onto these Kernels?
Click to expand...
Click to collapse
Use iovyroot, that other backup TA is a bit old last update was 2014...
When you backup with iovyroot using tabackup.bat you'll have TA-(numbers).img file (keep it safe somewhere as this is your unique and personnel backup)
To fully restore your keys on an unlocked bootloader, copy your TA partition backup to the rootkernel folder...command prompt to the rootkernel folder and type:
flash_dk TA-(numbers).img restore-drm-keys.ftf
You'll get a file called restore-drm-keys.ftf
Now use flashtool to flash it and all your keys will be restored (including fido)
-DM- said:
Use iovyroot, that other backup TA is a bit old last update was 2014...
When you backup with iovyroot using tabackup.bat you'll have TA-(numbers).img file (keep it safe somewhere as this is your unique and personnel backup)
To fully restore your keys on an unlocked bootloader, copy your TA partition backup to the rootkernel folder...command prompt to the rootkernel folder and type:
flash_dk TA-(numbers).img restore-drm-keys.ftf
You'll get a file called restore-drm-keys.ftf
Now use flashtool to flash it and all your keys will be restored (including fido)
Click to expand...
Click to collapse
"rootkernel folder" is where i have saved the kernel on my pc?
Thanx a lot for the instructions and excuse me if i make "silly" questions :angel::angel::angel:
konstantinos3 said:
"rootkernel folder" is where i have saved the kernel on my pc?
Thanx a lot for the instructions and excuse me if i make "silly" questions :angel::angel::angel:
Click to expand...
Click to collapse
The rootkernel folder from tobias tool, right click in that folder to open a command prompt...
Edit: if you go to the iovyroot thread, read the the 1st and 2nd post to understand what you're doing... In the 2nd post there is a link that will explain in details the all process, just adapt it to your own device...
To find out if your keys are re-enabled after you flashed them go to the services menu and under test/security you should see the 3 keys on top "active" and the fido key "provisioned"...that means that all your keys are back, if the fido key is not provisioned then your keys are only emulated...hope that it's a bit more clear now
konstantinos3 said:
In case I don't want simulation, will the keys be restored normally onto these Kernels?
Click to expand...
Click to collapse
the kernal made by @KbaB.BroS has DRM Stimulation enabled,
if you are making your own modified stock kernel then don't enable DRM Stimulation.
however modifying kernel is risky. be extra careful!
Mr @YasuHamed after 2 days rooting ,,, my google play store disconnected from the internet why ? how can i solve this problem i can't connect to the play store and everytime Check Connection
kofta2020 said:
Mr @YasuHamed after 2 days rooting ,,, my google play store disconnected from the internet why ? how can i solve this problem i can't connect to the play store and everytime Check Connection
Click to expand...
Click to collapse
is this problem
1. with play store only ?
2. how about rest of the apps? (chrome / viper / whatsAPP)
3. or are u facing connectivity issue globally?
you mentioned first two days after rooting this means initially it was working just fine... what apps you installed and allowed root access via superSU ?
please specify....
my WILD guess is that you might be having DNS issues (but that was OLD time issue in Cynogenmod (build in Gingerbread) that you have to specify DNS in settings globally....
YasuHamed said:
is this problem
1. with play store only ?
2. how about rest of the apps? (chrome / viper / whatsAPP)
3. or are u facing connectivity issue globally?
you mentioned first two days after rooting this means initially it was working just fine... what apps you installed and allowed root access via superSU ?
please specify....
my WILD guess is that you might be having DNS issues (but that was OLD time issue in Cynogenmod (build in Gingerbread) that you have to specify DNS in settings globally....
Click to expand...
Click to collapse
Yes with google play store only and the other apps working normally ... Iam using only xmod with root permision .. I dont know why play store only disconnected from the internet how can i solve it
kofta2020 said:
Yes with google play store only and the other apps working normally ... Iam using only xmod with root permision .. I dont know why play store only disconnected from the internet how can i solve it
Click to expand...
Click to collapse
check if
1. google play services in the apps is running or not.
2. select playstore from apps and clear the data and restore factory version. restart device and try.
YasuHamed said:
check if
1. google play services in the apps is running or not.
2. select playstore from apps and clear the data and restore factory version. restart device and try.
Click to expand...
Click to collapse
1- how can i check if play services running or not ?
2- Cleared data and cache and nothing happen same problem
i have another question . i backedup DRM Keys is that one DRM Keys or Change every time and must backup again ?
sorry for my english

Huawei P9 [ROM][Android 7.0][EMUI 5.0][European Firmware b386 based]*MagicRainbow* v2

{
"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"
}
Huawei P9 Custom Rom​
*MagicRainbow*​Version Two​Magisk Edition and Classic Edition​Teamwork by Tecalote and KangV
based on Android 7.0 (N) EMUI 5.0 European Firmware b386​
I'm happy to present you my new ROM It is tested and works without any problems on EVA-L09 C432 and EVA-L19 C432.
Other models must be tested first, which Firmware is required to get Developer Options and Fingerprint to work. Please report!
German-Thread:https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p9.2808/huawei-p9-rom-android-7-0-emui-5-0-magicrainbow-v2-by-tecalote.829450.html​
1) Difference between Magisk and Classic Edition:
The Magisk Edition was made to have a safteynet capable device that still offers much more features than a Stock Firmware ... It has the same features as Classic Edition, but with the difference that you can bypass safeteynet .... Apps such as Pokemon Go, various banking apps and others - which does not work anymore on rooted devices should work in this Rom
The Classic Editon is rooted with SuperSU and has the same features, but safteynet cannot bypassed. However, who does not run apps on this "questionable" service will have the same joy with this Rom
2) Requirements for MagicRainbow - short overview:
Basically: You must already be on Android 7 (Nougat), Bootloader must be unlocked, latest TWRP flashed with special settings (explained below)
A) Your device must not be rooted for installing this ROM - it is even better, if you start from clean original Huawei Stock Firmware.
Firmware-Requirement:
EVA-L09 C432 and EVA-L19 C432 need original Huawei Firmware b386 installed (flashable Firmware available - see below). But b386 is not for all other cust and models avilable!
EVA-L29C636 and EVA-L19C636 has currently only b361 as flashable Firmware available. Higher Firmwares comes only with OTA.
You should be with the Firmware for your device nearly to b386 - if not then Fingerprint may not work and perhaps not the Developer Options (which is very important for this ROM to work properly)
B) If you are on Stock Firmware and your device is rooted, backup your stuff, unroot your device and make a factory reset.
C) If you come from any Custom Rom like MagicRainbow v1 (based on b386) or @dkionline BlueWei - you must go back to original Huawei Stock Firmware b386 (see section 4 - How do flash firmware) It is not enaugh, just wipe with TWRP and flash the Rom!
D) If you are on Stock Firmware b387 (make just unroot - if you have Root - and do a factory reset) - but I think you can install this Rom just with the Wipes and without going back to b386
3) Flashable Firmware b386 c432 (for EVA-L09 and EVA-L19):
EVA-L09 c432 b386 Firmware update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84450/f1/full/update.zip
data.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84450/f1/full/EVA-L09_hw_eu/update_data_full_EVA-L09_hw_eu.zip
EVA-L19c432 b386 Firmware update.zip:http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84770/f2/full/update.zip
data.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84770/f2/full/EVA-L19_hw_eu/update_data_full_EVA-L19_hw_eu.zip
4) How to flash Firmware - or GOING BACK TO STOCK:
The simplest, preferred method to flash b386 (In accordance with your device and model!) can be done with TWRP - whether you come from the b383 or b387, or from BlueWei or MagicRainbow v1 - but note, you cannot use this method to update from Android 6 to Android 7:
1) Backup your apps with data (only User Apps, no System Apps, no Chat-Apps - Chat Apps should not be restored - but new installed with Playstore and new registered, use integrated Backup from Chat-Apps)
2) Backup all important files and folders from your internal memory (DCIM, WhatsApp folder, Downloads etc)
3) delete you Fingerprint and Google Account
4) Copy update.zip and ...hw_eu/update_data_full_EVA...zip to your external SD (dont unzipp it and dont do it into dload folder)
5) Bootloader must be unlocked
6) Make sure that you enable in developer options OEM Unlock and 2) ADB Debugging and 3) USB Debugging - in this order (if its not enabled yet)
7) TWRP must be installed
8) Flash with TWRP (Huawei Firmware) update.zip - after it is flashed do not reboot - go back to main menu
9) Flash with TWRP hw_eu/update_data_full_EVA...zip - after it is flashed do not reboot - down in the left corner klick on "wipe dalvik and cache"
10) Do not reboot - go back to main menu - use Tab: Restart - but do not restart system - RESTART RECOVERY
11) You are now in Huawei Stock Recovery - from there make 1) Wipe Cache Partition and 2) Factoryreset and 3) reboot to system
12) Huawei Stock Firmware b386 is succesful installed :good:
13) I would recommend to flash now the Firmware b386 once again, but now with dload-method. For this you must 1) unzipp update.zip on PC and 2) unzipp hw_eu...data.zip in a separate folder.
14) Make a folder on your external SD with the name: dload - Copy first the unzipped file from update.zip into this folder - but ONLY the UPDATE.APP (not the other files)
15) With VOL+ and VOL- (press in the middle down) and PowerButton flash b386
16) After restart to system, delete update.app in dload folder and copy now the unzipped files from hw_eu...data.zip into dload folder - but now you need ALL files (update.app, META-INF and the data folder)
17) flash it with the 3 Button Method
5) Important information for using this TWRP:
Made by @OldDroid v 3.1.1-1 (currently latest TWRP): https://www.androidfilehost.com/?fid=961840155545586361
A) Setup new flashed TWRP: allow system modification,
B) Open Settings Tab and configure the settings for your needs - example: I uncheck "prompt install TWRP app", I disable vibration and expand the screen timeout to 300 for seeing what TWRP shows me on screen, I set time zone and language...
C) Important in settings on last Tab - uncheck /disable "keep vendor partition mounted" - but leave ]enabled "exclude OEM-Path from data-wipe"
D) Have a look in main menu into Mount-Tab - For flashing Stock Firmware as shown above and for making Nandroid Backups with TWRP - you must not change anything in Mount!
E) But later, if you are ready to flash the ROM and you are going to wipe the partitions (explained below) - Immediately after the Advanced Wipe - before you want flash the ROM - you must go in main menu to: MOUNT and uncheck/disable everything in Mount - with the exception "Micro-SD" (this must be mounted!) If you dont do this step after wipe, before flashing ROM - the Rom would may not be flashed properly - and if so, it cannot work properly!!
6) Installing ROM
If you have MagicRainbow.zip already on external SD, do following steps:
Note: if you want boot sound to be played back in the future, then sound must be switched on before installing the Rom - if phone is in silent mode, there will be no boot sound in the future. Phone remembers the last status and this can not be changed afterwards!
A) In main menu of TWRP go to Wipe - do not use Factoryreset, use instead the Advanced Wipe
Wipe ONLY following partitions:
Dalvik / Art Cache
cache
Data
system
Do NOT wipe: vendor, internal memory, micro-SD
B) After wipe you navigate back to the main menu and open: Mount - uncheck all with the exception of Micro SD card! This is an important step - (especially vendor should not be mounted), since otherwise there will be errors in the installation. My script mounts itself, what it needs
C) Then navigate back to main menu and go to Install Tab - select MagicRainbow.zip and swype to flash
D) After flashing ROM, do not make a Wipe from Dalvik / Cache, just reboot. Reboot is relatively fast, but of course, the first boot takes a lot longer than usual - about 9 min
Differences during first boot: Classic-Edition interrupts the first boot process due to systemless rooting by SuperSU 2.82 SR1 and boot again - the Magisk edition does not need this additional loop.
7) Important for Magisk and Safetynet:
A) If you receive a root request during the first setup with Magisk Edition, please affirm it - no matter how strange it may seem to you!
B) After first setup dont open Magisk Manager and - before you doing anything else - go to settings and activate developer options.
Inside enable 1) ADB debugging and 2) USB debugging ( in this order! - not the other way)
C) After got to settings / expanded settings and enable in security: "unknown sources"
D) Immidiatly restart your P9 - this is an important step to keep safetynet green. After reboot you can open Magisk Manager.
E) Do not change anything in the settings or in the preinstalled module of Magisk - it is already set everything correctly! Also dont download module which you dont know for what they are and what they doing...
But I would recommend to download and install following two modules: Huawei Safetynet Fix and BusyBox 1.27.2
Please do it with following instruction: https://forum.xda-developers.com/showpost.php?p=73733872&postcount=564
F) Do not activate in Magisk Manager settings systemless hosts!
AdAway does not need this setting to work!
G) Start AdAway, download and activate hosts and reboot your Phone. After reboot open AdAway again, hosts are not activated yet, download hosts again and reboot your Phone a second time. Now hosts are activated (green) and safetynet stays also green.
It is not much to say to the Classic Edition, which you know already from MagicRainbow v1 b383 - but 1) ADB Debugging and 2) USB Debugging USB must also be enabled after the first setup and then restart the device before you do anything else! If you open AdAway and download and enable hosts, reboot your Phone. After reboot open AdAway again. If hosts are not activated yet, install again hosts and reboot. After it will work, cause its configured by an init.d script.
8) Important information to PMPlus:
The app PMPlus activates "auto-launch" on second page in the Phone Manager - so you have a very powerful Autostart Manager, which would otherwise not exist. This is optional, however - if you want to be sure that everything works smoothly, and does not want to adjust everything manually here, leave your fingers off. Note: If auto-launch is activated in phone manager, you can not undo this change, just by reinstalling the Rom!
Whoever wants it anyway:
A) Simply start PMPlus and go to Install, after succesful installed messeage, close this app! Autostart Manager is activated now in Phone Manager!.
B) You can then delete the app PMPlus.
C) But please note : All Autostarts are set to 0 and you have to manually enable the most important apps in auto-launch
D) Magisk Manager must be enabled in auto-launch, in the Magisk Edition - if you do not enabel, Root cannot work!
E) SuperSU must be enabled in auto-launch - in the Classic Edition - if it is not enabled, Root cannot work!
F) In both Roms Chat-Apps which should receive push notifications - must be enabled in auto-launch - and some apps must also enabled in "App activation" - which is a part of "auto-launch"
9) Features and Information:
Callrecorder - for manual and automated call recording
Viper4Android - Advanced Settings /more settings / Viper4Android Installation-Pool from here you can install: None, old viper and new viper - after reboot you have the App Symbol on Homescreen. Open it to configure Viper4Android.
Classic Edition ROOTED with SuperSU 2.82 SR1
Magis Edition ROOTED with Magisk 13.3
AdAway as ad blocker - look at Point 7 for further information
BusyBox 1.27.1
System deodexed
KangV-Settings (Advanced Settings on Homescreen) in nougat style - with the 4in1 restart menu and much more ....
Titanium Backup - you can use external SD with storage SD-Card and dont need Document Provider
MiXplorer - powerful Root Explorer which comes with PDF Reader, VLC Codecs and Archive Plugin, change language in settings
Debloaded - almost GApps from system removed - but Core GApps are integrated - so dont flash any GApps - you can install missing GApps with Playstore.
Full access to the external SD You can work on external SD with enabled Full Permissions - Example: TitaniumBackup automatically selects the external SD as the preferred location.
Optional: Path to the internal memory interchangeable with the external storage! To do this, you only need to use MiXplorer and navigate to /data. There is a file with the name: SDPath - open this file with text editor of MiXplorer. At the moment, the internal memory is set as default (ext_SD = 0). If you change the entry to: ext_SD = 1 and save it, all apps will only use the external storage after one-time reboot. Before you install apps like WhatsApp, think about it. Because if you like that all Apps store media and everything only on your external SD then enable this option. Example: The folder of WhatsApp will be created automatically on external SD ....
10)Disable Statusbar Lunar:
The Rom is European, but the Advanced Settings are made by KangV. He comes from China, thats why the Lunar component is built into Advanced Settings (these are the only Chinese letters in this Rom). To disable the chinese letters, go to Advanced Settings /Notification settings and disable the checkmark "Show statusbar lunar"
One known BUG: Do not use the "hide navigation bar" in Advanced Settings, it works with chinese models like AL10 - but not europaen models at the moment.
11) Restore orignial Huawei Bootanimation (if you dont like my integrated one):
Flash this zip with TWRP: https://forum.xda-developers.com/attachment.php?attachmentid=4262925&d=1504567957
Information: https://forum.xda-developers.com/showpost.php?p=73667280&postcount=541
12) DOWNLOAD *MagicRainbow* ROM v2:
P9-b386-MagicRainbow_Classic.zip: https://www.androidfilehost.com/?fid=889764386195921575
MD5 (please check after download): b350f2a37c88bd31c8373c57a4012344
P9-b386-MagicRainbow_Magisk.zip: https://www.androidfilehost.com/?fid=889764386195921598
MD5 (please check after download): 1587eeb1575d252f265f852ef3026dfa
Previous Version - MagicRainbow ROM v1 (based on b383, SuperSU EMUI 2.79 installed):
Requirement before installing this ROM:
EVA-L09 C432 and EVA-L19 C432 need Firmware b383 installed
EVA-L19 C636 need Firmware b381 installed
EVA-L19 C185 need Firmware b385 installed
P9_b383_Magic-Rainbow_v1.zip: https://www.androidfilehost.com/?fid=457095661767158149
MD5: 7c81a2684f45e0615972f12197552635
After first setup you must update SuperSU to Version 2.82 EMUI: https://www.androidfilehost.com/?fid=673368273298962637
HAVE MUCH FUN WITH THIS ROM
Many thanks to KangV for his great K-Settings Framework
If you like Advanced Settings by KangV - you can donate him:KangV: https://www.paypal.me/KangVIP
If you like *Magic-Rainbow* ROM, you can spent me some glass of wine https://www.paypal.me/Tecalote
Many thanks and credits to other great Developers:
@OldDroid - TWRP with DECRYPTION SUPPORT for P9 https://forum.xda-developers.com/p9/development/twrp-t3565703
@guitardedhero(Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@kishorerprem - SDCard-Write access
@Chainfire - SuperSU
@topjohnwu (systemless Xposed Framework and Magisk)
@dkionline - Custom Roms for P9
@Blackball - Custom Roms for P8 - P9 - P 10
@mr.mrcn - Dark Bloom for EMUI 5.0 Theme
​
[/LIST]
If you have in "About phone" build-number EVA-L09 or EVA-L19 b182c900 you dont receive the OTA Update to Nougat. You must change it to b182c432.
Here is described, what you have to do - please make every step careful and dont worry!
For EVA-L09 download this file: [url]https://www.androidfilehost.com/?fid=457095661767158957[/URL]
MD5 (please check after downloading): 21a70ae3b07b72277bf935bf4ed90320
For EVA-L19 download this file: [url]https://www.androidfilehost.com/?fid=817550096634767353[/URL]
MD5 (please check after downloading): 838d9634e22acce029c383ec780dd745
And you need for changing OEMinfo on b182 TWRP for Android 6 (not the one from OP = for Android 7) Download it here: [url]https://www.androidfilehost.com/?fid=457095661767122229[/URL]
Steps:
1) Your Bootloader must be open! Backup important files or folder from your internal memory (cause it will be completely wiped, except external SD will stay untouched)
2) Firmware b182 must be in dload folder (update.app 3,06 GB) Take the one for your device For EVA-L09 download full Firmware b182: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v63880/f1/full/update.zip
EVA-L19 can use same b182 - the Firmware works for both.
3) Unzipp oeminfo.emmc.zip - you get: oeminfo.emmc.win - this is the file what you need!
4) Store this file in following path on root of your external SD: \TWRP\BACKUPS\SNxxxxxxxxxxxxxx\C432\ (SNxxx folder must named with Serial Number of your phone and inside this folder copy the oeminfo.emmc.win
5) Enable Developer Options in Settings, go inside and enable OEM Unlock and USB-Debugging - after go to Advanced Settings /Security and allow "Unknown Sources"
6) Connect your Phone with USB to PC and wait until Windows installs the driver.
7) With Minimal ADB and Fastboot program for PC in administrative mode - boot the phone into fastboot mode and flash TWRP for Android 6.
https://www.androidfilehost.com/?fid=457095661767122229
(TWRP img must be in Minimal ADB and Fastboot Program Folder. You start the Program with right click as Administrator. You enter
adb devices
- you should get your SN and device. If on the screen pop up a request to allow connection, grant permission for always from this PC. Now:
adb reboot bootloder
-phone restart into Bootloader /Fastboot Mode. Bootloader must be unlocked and FRP unlocked.
You enter:
fastboot devices
- and get SN device, then
fastboot flash recovery Name-of-TWRP.img
8) If TWRP is succesful flashed disconnect USB from your Device and boot immidiatly after into TWRP. For this press Vol+ and Power Button. Stay holding this position until TWRP is booted (can take some minutes)
When TWRP is booted, allow Write Permissions for system.
9) In main menu and choose the button: RESTORE
10) Navigate to the C432 folder and restore oeminfo. (from folder C432 !) This changes oeminfo from b900 to c432!
11) Go back to main menu and reboot your phone - but not to system. You must press Vol+ and Vol- (in the middle) down until EMUI Software Installing begin and b182 will flashed again (it must be in dload folder!) If you see on screen text with red colour - ignore it, just press Vol+ and Vol- down, if it does not help, press also Power Button to reboot, but keep pressing Vol+ and Vol- because b182 must flashed again on this point!
12) If it was not successful and you receive after reboot a white screen and you will be promted to enter "the" password, dont worry, just use your password for Google. Phone reboots and make a factoryreset with EMUI low-level wipe. TWRP will be overwritten with Stock Recovery. Thats normal.
13) soon flashing again b182 was successful you reboot to system and perform from there another Factoryreset from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage.
14) SIM Card must be inserted - you can leave it in your phone from beginning.
15) Just make a short setup and you will see: You receive now the OTA Update to Nougat
reserved for future updates and changelogs
I'll try this ROM on my debranded L19C636B381, to test if finger print works, by next week.
Thanks for the ROM........
Why there are Chinese characters and Status bar Lunar in this European Firmware ?
lapocompris said:
Why there are Chinese characters and Status bar Lunar in this European Firmware ?
Click to expand...
Click to collapse
... Because KangV is Chinese and he made this Advanced Settings and included it into this European Firmware based Rom.
You can disable it in Advanced Settings (=K-Settings) /Notification settigs. Uncheck "Show Statusbar Luna"
Look at Screenshots...
May i instal this from b378?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
I have rooted b378 with adaway viper4android can i install on them or i must update to b383?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
Why rom is virus?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
scaniathe said:
May i instal this from b378?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
I have rooted b378 with adaway viper4android can i install on them or i must update to b383?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
Why rom is virus?
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Please read OP #1 before asking questions which are already answered
Well, you have to go back to Stock Firmware first. If you don't do this Rom will work too, but without Fingerprint Scanner.
Everything is working only if you are make the steps before flashing.
0) Backup your stuff
1) download the firmware and data zip from Links in OP for EVA-L09.
2) install it how it's mentioned in OP
3) Make the necessary wipes. (and only this - see OP)
4) Flash Magic-Rainbow
ROM doesn't have any Virus! It's on actual security Patch Level
I have stock but only rooted
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
scaniathe said:
I have stock but only rooted
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes, but you are on b378 and if you want to have full working nice Magic-Rainbow Rom, you must update to Stock b383 first as I have described in Original Post.
After you must do the Wipes I have told in OP.
Root is not necessary for installing my Rom
It's up to you...
I installed the rom and it is amazing
Everything is working perfectly
Thanks for this amazing rom
One question: anyone knows where bootanimation.zip is located??
Product/media
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Installed, working perfect. Thanks. Best rom
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
scaniathe said:
Product/media
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks bro
It is actually product/etc/media ??
scaniathe said:
Product/media
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Product/etc/media sorry
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
i have stock B378 and rooted with boot.img. how to update with this magic-rainbow rom ?
Thank you for the rom. I just installed it. I would like to flash magisk but I get an error on recovery as it cant be installed. Is there another way to do it?
lorvix said:
i have stock B378 and rooted with boot.img. how to update with this magic-rainbow rom ?
Click to expand...
Click to collapse
Hello First thing you should do : Take the time to read slowly Original Post (OP) #1.
You will find the answer detailed for your question.
But in short words :
1) Download the b383 Stock Firmware related to your device which is linked in OP.
2) Backup your data and Apps and contacts etc.
3) Flash b378 Stock Recovery with ADB.
4) Unzipp downloaded Stock Firmware and update yours as described in OP to Stock b383.
5) After make the Wipe which is described in OP (and not another)
6) Flash Magic Rainbow
I wish you success and let me know and feel free to ask if something isn't clear
mihairimia said:
Thank you for the rom. I just installed it. I would like to flash magisk but I get an error on recovery as it cant be installed. Is there another way to do it?
Click to expand...
Click to collapse
Of course, this Rom makes the Rooting with SuperSU, that's why you get the Error.
Some days ago I finished the development for this Rom. At this time, TWRP wasn't able to Root with Magisk.
But now it is!
I will release a Magisk Version of same Rom. But this week I have a lot of work - so I will do that probably during next week.
If you can wait for it
Great
Amazing rom ... all running perfectly for me.
K-setting is a great plus.
I'm testing all its features
Happiness is here.
Thank you for your hard work.

How to root xperia z2 D6502?

Can anybody please guide me through the process of rooting the xperia z2 [D6502]?
i have unlocked the bootloader. It is currently running on marshmallow.
All i need is root access.
To obtain the root on your Sony Xperia Z2, you will need to install ‘ADB Tools’ first. Then, you’ll need to go into the Developer Options of your Xperia Z2, enable USB Debugging and make sure that ‘Unknown Sources’ is enabled as well. From here, you can download the Community RootKit from the source link below and then follow these instructions.
– Plug in your Sony Xperia Z2
– Open a Command Prompt inside the folder with the rootkit and type RUNME.bat before pressing enter
– Read the instructions that you see appear in the command prompt and do what they say
– Reboot your device once it has completed and the device should be rooted.
Once your Sony Xperia Z2 has been rooted, you can install both SuperSU and Busybox from the Google Play Store and enjoy your freshly-rooted smartphone. Don’t forget to comment below and tell us your experience with the process, and your rooted phone.
Sent from my SM-J200G using Tapatalk
Adriel concessio said:
To obtain the root on your Sony Xperia Z2, you will need to install ‘ADB Tools’ first. Then, you’ll need to go into the Developer Options of your Xperia Z2, enable USB Debugging and make sure that ‘Unknown Sources’ is enabled as well. From here, you can download the Community RootKit from the source link below and then follow these instructions.
– Plug in your Sony Xperia Z2
– Open a Command Prompt inside the folder with the rootkit and type RUNME.bat before pressing enter
– Read the instructions that you see appear in the command prompt and do what they say
– Reboot your device once it has completed and the device should be rooted.
Once your Sony Xperia Z2 has been rooted, you can install both SuperSU and Busybox from the Google Play Store and enjoy your freshly-rooted smartphone. Don’t forget to comment below and tell us your experience with the process, and your rooted phone.
Sent from my SM-J200G using Tapatalk
Click to expand...
Click to collapse
i didn't find the source link. could you send me the link for community rootkit?

Categories

Resources