Related
I followed the instructions on the TheUnlockr, How To - Root Your HTC Magic in One Click, and when I did everything and came to the part where I need to backup Recovery Image error occurred.
Recovery Flasher Backup FAILED: Could not run command
Does anyone know what it is, and what to do?
every day the same questions.... use the search....!!!
recovery flasher does not work with the new roms. they are bug fixed.
you do not need a backup, there are enogh on the net.
follow this thread to flash a recovery:
http://forum.xda-developers.com/showthread.php?t=756918
I tried this method [Guide][ALL DEVICES]ROOT + flash custom recovery + fix perfected spl [25 OCT 2010], but it ended up with "Not Enough Memory" message. What should I do now?
Such questions should be asked in the thread in which you followed the guide :0)
Try to remove an app or two and try again.
Else, ask again in the thread and i'll help you out.
use Universal Androot be sure to download the beta and select "Do not install superuser"
This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.
I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.
Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?
Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.
Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance
The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.
Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters
Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.
Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk
It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.
Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.
Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?
After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
gaguzman said:
After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
Click to expand...
Click to collapse
Alternatively... just install TWRP !!
ascot17 said:
Alternatively... just install TWRP !!
Click to expand...
Click to collapse
Agree it would be much easier and cleaner, if it had worked for me. Touch didn't work after install of 2.7.0.0b, so I gave up on it, and had to reflash CWM to get recovery function and proceed with root. I guess there are still some variations in there that can't be accounted for. I posted this as an interesting observation that might be useful to the devs.
Hello Everyone
I understand that many of the users have tough time rooting their device and thus I have decided to look into Rooting using Exploit method over USB commands rather than flashing ROM. I would just look into what could be done as there are few differences between Z3 Compact device series but all use the same Snapdragon 801. This guide is intended for UNLOCKED & LOCKED BOOTLOADER. Make sure you check each method if it supports locked/unlocked bootloader or not. In case it is not mentioned, it is to be understood that it supports locked bootloader as well. However, if the method fails, please provide feedback and also update SuperSU in the script files.
All Credits to the developers for their tools!
HTML:
I take no responsibility for world wars, broken phones, flying machines,
UFO invasions, bricked phones, dead sd card . If you agree to go ahead with this,
it is your choice and no blame should come to any developer/contributor whatsoever
PREREQUISITE
-USB DEBUGGING
For this guide to work, make sure usb debugging is enabled.
Go to Settings> About>Build Number> tap it 7 times and "Developer Options" should appear in settings.
In Developer Options> Enable USB Debugging.
-USB DRIVERS
For these I suggest use Flashtool. However if you still have problem. I would update a guide for that as well
http://www.flashtool.net/index.php
METHOD 1 (Kitkat/Lollipop. Unlocked/Locked Bootloaders)
1.Download latest SuperSU from HERE
2.Place supersu in your sd card
3.Install recovery from the link HERE and use the method as stated in the thread.
4.Once booted into recovery, flash supersu.zip. Make sure it is 2.37 or above for LP.
5.Done
Check FAQ 1
How to make a TA backup.
1. Download the latest version of Backup TA from here DOWNLOAD HERE
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.bat
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
Someone pointed out that the script needs root to work.
UNLOCK bootloader from Official Website
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Please note! It will only be possible to unlock the boot loader for certain releases of this model. You can check if it is possible to unlock the boot loader of your device by checking the service menu.
Open the Contacts app.
Click the menu button in the top right.
Click Settings.
Long press (for about 5 seconds) somewhere in the empty space just above soft key bar, and then release your finger. A button named Enter service code will then appear in the same area (this may take a few tries).
Click Enter service code. A dialler will appear.
Enter *#*#7378423#*#* in the dialler.
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(bootloader).
If your bootloader can be unlocked, proceed to the above website and follow the on screen instructions. You do not need to download full adb , just download the platform tools attached with this guide.
Once you have working drivers, unlock bootloader, made backups and have usb enabled, you can proceed to the actual rooting process.
Backs are highly recommended but not a must .
There are a few methods due to differences in devices and one might work on all, one or none. The methods are arranged in preferred order but not necessarily to work in the same order.
METHOD 2: Kitkat Unlocked Bootloader
Download boot.img from attachment
unlock bootloader via Sony
Flash boot.img via flashtool or fastboot commands
METHOD#3
Use Kingo Root app
Enable USB debugging and run the application.
Download from here
http://www.kingoapp.com/
You can use apk file as well but PC method is more effective.
METHOD 4
CHINESE METHOD
http://www.mgyun.com/en/GetVRoot
KingUser be installed.
Install SuperSU from market and replace Kinguser with SuperSU in SuperSU options
METHOD 5
Run kingo and Vroot at the same time using a PC!
At times this works with few devices
ROOT CHECKER BASIC FROM PLAYSTORE to check if you have root.
Credits
zxz0O0 for rootkit
If you think I have missed your name and you deserve to be in the list, please do not hesitate to inbox and I would gladly update it.
Reserved FAQ
FAQ 1
If you do not wish to flash recovery and only want to gain root. Use boot command instead of flash. Or delete files as stated in the recovery guide
I have an error/question!
stuck at cleaning up
Close the tool and run again.
.
error: more than one device or emulator
Check if you have installed any windows android emulater like bluestacks etc
.
stuck at Waiting for device
Make sure device is connected
Make sure USB-debugging is enabled
Make sure no Sony PC Companion or other Sony software is running
Make sure you have adb drivers installed
Make sure the computer is permanently authorized for connection on the phone (you get a dialog the first time you connect)
.[*]How to unroot?
Flash factory firmware in flashtool. Exclude everything except system. No need to wipe anything.
.
[*]Will I keep root after factory reset?
Yes
"PREREQUISITE : USB DEBUGGING + USB DRIVERS"
"Firstly I suggest you make a full backup of your applications/data especially TA backup."
As you make a backup of TA without root?
Backup TA -> http://forum.xda-developers.com/showthread.php?t=2292598
Q: Do I need root for this?
A: Yes, you do need root for both backup and restore to work. I would advice to use @DooMLoRD's excellent Easy Rooting Toolkit for this, when not already rooted.
kvi said:
"PREREQUISITE : USB DEBUGGING + USB DRIVERS"
"Firstly I suggest you make a full backup of your applications/data especially TA backup."
As you make a backup of TA without root?
Backup TA -> http://forum.xda-developers.com/showthread.php?t=2292598
Q: Do I need root for this?
A: Yes, you do need root for both backup and restore to work. I would advice to use @DooMLoRD's excellent Easy Rooting Toolkit for this, when not already rooted.
Click to expand...
Click to collapse
Thank you so much for your feedback. The guide is still in process and I would make necessary changes as well once it is completed.
Making TA is a suggestion and NOT by any means a step to the process. I am going to work a bit as it needs editing at places
UPDATE :
Guide updated
waichai said:
Hi Hnk1,
Sorry bothering you.
I have read so many threads on xda, and they all have too many steps and risk. I found your thread is simple and easiest to follow.
I have read your thread from http://forum.xda-developers.com/z3-tablet-compact/general/root-flashing-construction-t3091763
My device: SGP621 (LTE version) Build number 23.1.A.0.167 Kitkat 4.4.4. Bootloader is Locked.
I would like to root and TA backup. Can I just follow these step from your tutorial below? Thanks.
PREREQUISITE..............................................
Click to expand...
Click to collapse
Firstly always quote me in the right forum and NEVER ASK me questions in PM. If you next time do it, I will simply ignore.
Well, The recovery clearly states it works for your device so go ahead and flash it.
Hnk1 said:
Firstly always quote me in the right forum and NEVER ASK me questions in PM. If you next time do it, I will simply ignore.
Well, The recovery clearly states it works for your device so go ahead and flash it.
Click to expand...
Click to collapse
I apologize for the PM. I should have read your signature. Thank you for your reply.
I am on 4.4.4 and 23.0.1.A.0.167. I tried method 1,3,5 and none of them works, i thinks it's because of the 23.0.1.A.0.167 is not rootable using the exploit method ?
-Zeta- said:
I am on 4.4.4 and 23.0.1.A.0.167. I tried method 1,3,5 and none of them works, i thinks it's because of the 23.0.1.A.0.167 is not rootable using the exploit method ?
Click to expand...
Click to collapse
I suggest you try the Chinese method. I rooted with that but download the Chinese version because it's 1.83 while English version stands at 1.78
Noob question... unlocking bootloader will make me lose DRM right?
Lrclaros said:
Noob question... unlocking bootloader will make me lose DRM right?
Click to expand...
Click to collapse
It is wise to make @ backup. However, I have always unlocked my boot loader via official Sony website and never had any problems even without a TA backup.
Good luck
Guide updated and changes made!
I have unlocked bootloader, by oficiall way (Sony site). Phone is full reseted now. Can I back all data, whole system? I've made backup of all on the internal mem with TRWP. Will everything works normaly after that?
So if I access the service menu in the root section it says I cannot unlock the bootloader.
Is there a way to do so through unofficial means?
I did backup my TA so I just need to be able to do that :/
So far I'm unable to unlock the bootloader and never upload a custom recovery.
My model is D6603 with version 6.x of Android OS.
Is the capacity to to unlock the Bootloader bound to the android version?
I heard that I could root the phone if I downgrade to an older OS version and then do it... anybody can confirm?
For those with any trouble and that can't flash twrp, a full procedure for injecting TWRP into the kernel is here:
https://forum.xda-developers.com/showpost.php?p=74528751&postcount=22
After several hours last night comparing tons of guides to find the fastest, easiest and newest guides this is a summary of what i came up with. (No need to downgrade or mess around with a bunch of complicated steps). Tested on Z3 D6603, Firmware 23.1.A.28.
Rooting
I used these guides, but they both had outdated apps.
From XDA: http://forum.xda-developers.com/xperia-z2/general/root-t3108230
Better grafical guide: http://www.whattechsays.com/android/root-xperia-z2-z3-lollipop/
Links to the updated apps:
KingRoot: http://androidxda.com/download-kingroot-application
MOD EDIT by @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
Busybox: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
XZRecovery: https://www.androidfilehost.com/?fid=95916177934556263
SuperSU: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Troubleshooting
XZRecovery didnt work for me so i had to use another guide to install TWRP dual recovery.
http://techtrickz.com/how-to/install-twrp-recovery-xperia-z3-locked-bootloader/ ...software: http://nut.xperia-files.com/ (choose the newest XZDualRecovery version and then choose the Z3 installer )
The standard version of SuperSU didnt work but the newest beta version did work
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Unlock bootloader
Best and straightforward guide: http://www.android.gs/unlock-bootloader-sony-xperia-devices-universal-tutorial/
Command promt
Guide for using the command promt http://www.7tutorials.com/command-prompt-how-use-basic-commands (if you wanna go directly to one folder in the command promt: navigate to the folder, press shift + right click and choose open command window here)
Troubleshooting
I had a problem to get into fastboot mode, heres alternative ways
http://www.theandroidsoul.com/boot-sony-xperia-z3-fastboot-mode-63226/
Drivers. I then had a problem with the drivers in Windows 10.
Windows didnt let me install my own drivers, only the drivers that it recommended. Heres how to byepass that and install unsigned drivers. http://club.myce.com/f189/how-disable-driver-signature-enforcement-command-line-338073/
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Flash ROM
Theres a guide on how to flash rom inside this popular official rom.
http://forum.xda-developers.com/z3/development/rom-blisspop-team-bliss-2-2-z3-t3064669
Then most popular Z3 rom:
http://forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Thanks everyone for your time and work creating these amazing apps and guides!
Making it possible for us noobs to enjoy a great mobile experience.