Database Develop

CWM Recovery and Root (Stock Kernel Sony 4.2.2)(pollux_windy)

Stock Kernel Packed with CWM
Requirements:
Sony tablet Z Wifi version aka pollux_windy
Unlocked Bootloader
Sony Firmware 4.2.2
a computer with working fastboot
Install Procedure:
connect device to pc
Open CMD/Terminal and cd to the folder you have placed the boot image
type this in CMD/Terminal:
Code:
adb reboot bootloader
Now Flash using:
Code:
fastboot flash boot boot.img
Now Reboot your tablet by:
Code:
fastboot reboot
How to Enter recovery:
The key combination to enter recovery is broken and will be fixed later on. Currently you can reboot to recovery using:
an app like Rom Manager
adb reboot recovery
using terminal emulator (su followed by reboot recovery)
Download Link: (POLLUX_WINDY ONLY)
boot.img
Credits:
Koush- for clockwork mod
DooMLoRD- for his recovery ramdisk
@dinitro - for actually taking the time to compile the cwm with stock kernel, this guy deserves all the credit
Since this is pure stock kernel with a custom recovery i assume i dont have to post the kernel sources, If there is a issue mods are welcomed to notify me via PM.
Rooting Instructions:
Download the latest zip from Here and move to device
Reboot to recovery
Flash
Reboot
​
XDA:DevDB Information
CWM Recovery and Root (Stock Kernel Sony 4.2.2), a Kernel for the Sony Xperia Tablet Z
Contributors
bluefa1con
Kernel Special Features:
Version Information
Status: Testing
Created 2013-09-05
Last Updated 2013-09-06

Woot! Thanks. Gonna try it out tonight.

drazyw said:
Woot! Thanks. Gonna try it out tonight.
Click to expand...
Click to collapse
releasing the kernel first so people can be ready when i release my dual boot for tablet z
more details on my pac thread

Damn, I spent ages getting the root on 4.2.2 sorted out this morning ! Thanks !

Thanx for your work !
I assume it will never work on with locked bootloader ?

ibis69 said:
Thanx for your work !
I assume it will never work on with locked bootloader ?
Click to expand...
Click to collapse
locked bootloader= cant flash a kernel other than stock sony kernel
there is a way to have recovery on locked bootloader but it still needs root
i am too busy these days, if only i had time i would look at xperia z root exploit and implement it on tab z
meanwhile here is what u can do
backup your TA parition
unlock bootloader and root via this method
flash back to stock sony kernel
restore your TA and your device would behave like it was never unlocked

Unlocked my bootloader a few moments ago .. Trying your kernel now.
...
It can access to the internal storage but i don't have any files to flash.
And error appears when trying to mount or install zip from the external storage.
Thank you So much we appreciate your hard work. =)

Half Alive said:
Unlocked my bootloader a few moments ago .. Trying your kernel now.
...
It can access to the internal storage but i don't have any files to flash.
And error appears when trying to mount or install zip from the external storage.
Thank you So much we appreciate your hard work. =)
Click to expand...
Click to collapse
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
{
"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"
}
Sent from my SGP311 using Tapatalk 4

bluefa1con said:
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
Sent from my SGP311 using Tapatalk 4
Click to expand...
Click to collapse
Just tried now flashing from the internal storage ,.. And it's Working.
Hope you can fix the external_sd problem ,.
And that Big surprise is coming soon like today ?
Can't wait to test it. :good::good:

bluefa1con said:
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
Sent from my SGP311 using Tapatalk 4
Click to expand...
Click to collapse
with that great surprise you say,since sony roms can only be primary,what if we have already installed an aosp rom?will we be able to move it to secondary rom partition or we will have to reinstall it from scratch?finally the second rom will be stored at /cache or at /sdcard?sorry if i reveal some of your surprise with these questions

pangiotis24 said:
with that great surprise you say,since sony roms can only be primary,what if we have already installed an aosp rom?will we be able to move it to secondary rom partition or we will have to reinstall it from scratch?finally the second rom will be stored at /cache or at /sdcard?sorry if i reveal some of your surprise with these questions
Click to expand...
Click to collapse
currently the project is in its infancy, we got basic dual boot done and we got more plans
copy your data partition to some other place (sdcard etc) and copy it back when u install pac on second rom
we got big plans for this and we are talking to recovery devs to customize the recovery for RomSwitch dual boot implementation

Dual Boot released HERE

Is this kernel from 311 or 312 version of Tablet Z?

Rootk1t said:
Is this kernel from 311 or 312 version of Tablet Z?
Click to expand...
Click to collapse
Should work on both, I have tested on 311 because that's the device I have but both are identical besides more storage capacity
Sent from my SGP311 using Tapatalk 4

bluefa1con said:
releasing the kernel first so people can be ready when i release my dual boot for tablet z
more details on my pac thread
Click to expand...
Click to collapse
Well it seems to work perfect. Followed all the steps and it worked flawlessly. After a few days of struggling to maintain root when updating to 4.2.2 with Sony's OTA, this took 5 min. Thanks for all the work. Can't wait to try out some dual boot stuff now.

I tried this procedure on my SGP321 LTE Tablet. After flashing the boot.img, my tablet refuses to boot up. There is just a Red LED. No Sony logo or nothing. I somehow managed to get it into Fastboot mode (Blue LED) but apart from that I cannot do anything. On trying Vol - and plugging the USB at the same time, the FlashTool recognizes the Flash Mode (but there is no Green LED) I even tried flashing the FTF through the FlashTool but it gets stuck on flashing data. I really am struggling since 5 hours. Is my Tablet dead? I really cannot figure out what to do next Please help me!!

aashayjardosh said:
I tried this procedure on my SGP321 LTE Tablet. After flashing the boot.img, my tablet refuses to boot up. There is just a Red LED. No Sony logo or nothing. I somehow managed to get it into Fastboot mode (Blue LED) but apart from that I cannot do anything. On trying Vol - and plugging the USB at the same time, the FlashTool recognizes the Flash Mode (but there is no Green LED) I even tried flashing the FTF through the FlashTool but it gets stuck on flashing data. I really am struggling since 5 hours. Is my Tablet dead? I really cannot figure out what to do next Please help me!!
Click to expand...
Click to collapse
Do not worry, you just flashed the wrong kernel for your device, happens to everyone. Just simply try to flash your FTF, or you could install Cyanogenmod.

mamenyaka said:
Do not worry, you just flashed the wrong kernel for your device, happens to everyone. Just simply try to flash your FTF, or you could install Cyanogenmod.
Click to expand...
Click to collapse
I tried flashing the 4.2.2 FTF but it gets stuck on loading data. I tried flashing the boot.img from CM10.2 but that too gets stuck on 'Flashing Selected Kernel'..

aashayjardosh said:
I tried flashing the 4.2.2 FTF but it gets stuck on loading data. I tried flashing the boot.img from CM10.2 but that too gets stuck on 'Flashing Selected Kernel'..
Click to expand...
Click to collapse
You need to flash the boot.img with fastboot.

mamenyaka said:
You need to flash the boot.img with fastboot.
Click to expand...
Click to collapse
Forgive my noobness...but where do I get the original 4.2.2 boot.img from? I extracted the 4.2.2 FTF but there is no boot.img in it. On the other hand I extracted the boot.img of CM10.2 but that gets stuck on Flashing selected kernel.

[RECOVERY][ROOT][TWRP 3.0.2-0]Galaxy A8 sm-a800i - Exynos5433 -UPDATE 5/4/2016

Unofficial original release -TWRP recovery for the SM-A800I, Exynos5433
UPDATE 5/4/2016: TWRP 3.0.2-0 released
SEANDROID warning fix.
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
TWRP is now v3.0.2-0
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
UPDATE: 12/3/2016
New feature available in TWRP 3.0.0-0 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
F2FS support added.
Internal SUPERSU root option removed. This is to prevent boot loops on 5.11/6.0 devices
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
twrp_3.0.2-0_sm-a800i
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the SuperSU zip below with TWRP.
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS OR YOU WILL BOOT LOOP, ONLY USE THE FILE BELOW:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
GUIDE
https://boycracked.com/2016/04/23/h...2-0-root-samsung-galaxy-a8-sm-a800i-sm-a800f/
DEVICE TREE: github.com
{
"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"
}
Credits: Me, Teamwin and my tester - abhinavparasher
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Rooted/Custom recovery installed successfully
Please refer to the attachments.

are you flash a800f????

davod84 said:
are you flash a800f????
Click to expand...
Click to collapse
This version is only for sm-A800i. Do not flash it on any other model.
Do NOT flash it on A800F

does it work with a800iz ? i will try it now
edit : no , it's not working , it's get restart but no root, recovery working but its stick at bootloop

A . S said:
does it work with a800iz ? i will try it now
edit : no , it's not working , it's get restart but no root, recovery working but its stick at bootloop
Click to expand...
Click to collapse
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.

ashyx said:
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
Click to expand...
Click to collapse
Your right ; my device is rooted now
Just do not twrp install supersu!
Sent from my SM-N910C using Tapatalk

Hello Everyone!. i experienced an issue with my rooting process. Now its stuck at the Samsung Galaxy A8 Logo with Red caption on top that says. Custom Binary Blocked by FRP lock. i tried flashing twrp that i downloaded from this thread but it failed with an error on my phone that says. Custom Binary(RECOVERY) Bloced by FRP Lock. I need your guidance, please help me.

ashyx said:
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
Click to expand...
Click to collapse
Hi,
I sent you a DM. Coukd you take a look at it??
Thanks in advance.
Sent from my SM-A700F using XDA Free mobile app

rissered said:
Hello Everyone!. i experienced an issue with my rooting process. Now its stuck at the Samsung Galaxy A8 Logo with Red caption on top that says. Custom Binary Blocked by FRP lock. i tried flashing twrp that i downloaded from this thread but it failed with an error on my phone that says. Custom Binary(RECOVERY) Bloced by FRP Lock. I need your guidance, please help me.
Click to expand...
Click to collapse
u need to enable usb debugging & oem unlock from devlper option on phone setting first before start flash root file with odin..
Sent from my SM-A800I using Tapatalk

ryez88 said:
u need to enable usb debugging & oem unlock from devlper option on phone setting first before start flash root file with odin..
Click to expand...
Click to collapse
Yeah. That's what I did wrong. I turned the OEM Unlock off after a successful root. that was yesterday, but today after restarting my phone the frp lock triggered.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
I guess what i need to do is to download the firmware from sammobile. when i go there i only see China and HongKong as country choices. my country isnt there and my fone says its from Vietnam.

rissered said:
Yeah. That's what I did wrong. I turned the OEM Unlock off after a successful root. that was yesterday, but today after restarting my phone the frp lock triggered.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
I guess what i need to do is to download the firmware from sammobile. when i go there i only see China and HongKong as country choices. my country isnt there and my fone says its from Vietnam.
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/59917/A800IXXU1AOJ1_A800IOLB1AOJ1_XXV/

Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help

rissered said:
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
Click to expand...
Click to collapse
Was the file in .rar/.zip format or did it end in .tar/.tar.md5?
Also, usb drivers can be found on samsungs official website for your country.
Most of the times, usb drivers do not need to be downloaded seperately if you are using an updated windows system.
Plug in your phone in download mode and start up odin. If the "com port" turns green, your phone is detected successfully.

Thanks for replying @abhinavparasher it was in zip file but when i extract it its in tar.md5. even when the error stating that the file is corrupted appears the whole extraction process still completes itself. and i already downloaded the USB driver and hope this works

rissered said:
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
Click to expand...
Click to collapse
Use 7zip to extract it not Winrar.
If it says corrupted again then the download is not complete.
USB driver: http://developer.samsung.com/technical-doc/view.do?v=T000000117
Also you say your phone is made in Vietnam.
Samsung manufacturer their devices in Vietnam and Korea so that doesn't mean that's the firmware you need.
If you are from the Philippines then download the firmware for the Philippines.
www.sammobile.com/firmwares/database/SM-A800I
There is an app called Samsung phone info that will tell you everything you need to know about your device.

@ashyx thanks! i pre downloaded the Stock Firmware from the Philippines. i chose Openline since it is indeed openline. That is also the file that says it is corrupted when i try to extract it. I am downloading 7zip right now. I'll update you as soon as i get somewhere with this.
I would lie to try the Samsung app you're talking about but right now the only thing happening to my phone is go to logo screen then turn off again.

hi i flashed the twrp .do i flash supersu with odin? my phone:a800i/5.1.1

mohannad22 said:
hi i flashed the twrp .do i flash supersu with odin? my phone:a800i/5.1.1
Click to expand...
Click to collapse
TWRP.
Sent from my HTC One_M8 using XDA Free mobile app

https://github.com/ashyx/TWRP_Samsung_Galaxy_a8hplte/pulls
Please accept those changes

How to root xperia z3+?!

Hi,
Please can anyone tell me if my device is rootable. I have an xperia z3+ version 5.0.2, build number 28.0.A.8.266, if it is possible can anyone tell in quick steps.
Thanks

Flash SuperSU via TWRP.

The safest way to do it, is by unlocking your bootloader and flashing a SuperSU-installer through either a permanent or a temporary TWRP Recovery. If your device won't boot after the flashing process, download a "rootable" kernel from here and flash that too through TWRP. Hope it helps

2minuutes said:
The safest way to do it, is by unlocking your bootloader and flashing a SuperSU-installer through either a permanent or a temporary TWRP Recovery. If your device won't boot after the flashing process, download a "rootable" kernel from here and flash that too through TWRP. Hope it helps
Click to expand...
Click to collapse
first i need to bkp TA, but i need to root and then install TWRP
any other way to root witouht recovery ?

Root
(rooted kernel attached in post)
Managed to successfully root my Z3+ Dual.
How I dit it:
1. Downgraded to LP in order to back up my TA (required by the tool = E6533 (28.0.A.8.266)). Enabled developer and USB debugging.
Used this guide to back up TA, resulting TA-17042016_Z3+Dual.img.
2. Unlocked bootloader using flashtool (I obtained prior the unlock code from Sony http://developer.sonymobile.com/unlockbootloader/)
3. Read thoroughly this thread and downloaded all necessary apps (SuperSU, fastboot adb, latest MM .ftf (32.1.A.1.185) - Customized HK in my case).
Attention! In addition to what you will find in that thread, you need fastboot.
4. Flashed MM 32.1.A.1.185. Enabled developer and USB debugging.
5. Extracted the kernel (kernel.elf) in order to root it. Prepared the rooted kernel (new_kernel.img) with the provided tool. Put phone in flashboot mode (power off. keep volume up and insert usb). Checked the kernel and flashed it. Uploaded the saved TA keys (TA-17042016_Z3+Dual.img). Attention! Copy the extracted kernel, TA keys and fastboot in the same directory.
Commands used (Shift+Right click on the containing directory):
Code:
rootkernel kernel.elf new_kernel.img TA-17042016_Z3+Dual.img
- Unpacking kernel
Found elf boot image
Found appended DTB
- Unpacking initramfs
- 64-bit platfrom detected
- Disabling dm-verity
- Disabling SONY RIC
- Installing TWRP
- Found SuperSU-v2.65-20151226141550.zip
Adding service entry for SuperSU
- Configuring secd
- Configuring wvkbd
- Configuring drmserver
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
fastboot boot new_kernel.img
downloading 'boot.img'...
OKAY [ 2.187s]
booting...
OKAY [ 0.562s]
finished. total time: 2.749s
fastboot flash boot new_kernel.img
sending 'boot' (24760 KB)...
OKAY [ 2.180s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 2.380s
flash_dk TA-17042016_Z3+Dual.img DK.ftf
- Extracting device key
- Creating FTF file for device E6533
- Cleaning up
Done
6. Booted the phone and...voila!
{
"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"
}
None of this would've been possible without the hard work of tobias.waldvogel and zxz0O0.
Hope it helps!

I followed nica_ro's steps exactly as he did it. I have a Z3+ (E6553).
However, my phone shows that it's not rooted. I have access to TWRP recovery though.
It seems as if SuperSU was not installed although I also had the version 2.65 zip file (like in the guide) in the rootkernel tool directory.
Also, I tried to manually flash SuperSU through TWRP without any noticeable change.
What could have gone wrong?
Edit: Solved it! I was using Version 4.23 of rootkernel, which didn't properly integrate SuperSU. After using 4.24 I'm now fully enjoying my rooted Z3+!
Thanks nica_ro!

Chrizes said:
I followed nica_ro's steps exactly as he did it. I have a Z3+ (E6553).
However, my phone shows that it's not rooted. I have access to TWRP recovery though.
It seems as if SuperSU was not installed although I also had the version 2.65 zip file (like in the guide) in the rootkernel tool directory.
Also, I tried to manually flash SuperSU through TWRP without any noticeable change.
What could have gone wrong?
Edit: Solved it! I was using Version 4.23 of rootkernel, which didn't properly integrate SuperSU. After using 4.24 I'm now fully enjoying my rooted Z3+!
Thanks nica_ro!
Click to expand...
Click to collapse
Glad you solved it!

Guys,
I use to mod my phone since sony ericsson time. I always root my android devices just to get rid of bloat,adblock,greenify and few customization. Never unlocked my bootloader in any case. Now I am really worried about my new Z3+ Dual.. I desperately need Root accesses.. But worried about bricking my device.. I am on MM .185, Is it possible to backup TA with this FW?.. Is all the steps required to root is safe and easy? Is TA backup mandatory?

dil2abu said:
Guys,
I use to mod my phone since sony ericsson time. I always root my android devices just to get rid of bloat,adblock,greenify and few customization. Never unlocked my bootloader in any case. Now I am really worried about my new Z3+ Dual.. I desperately need Root accesses.. But worried about bricking my device.. I am on MM .185, Is it possible to backup TA with this FW?.. Is all the steps required to root is safe and easy? Is TA backup mandatory?
Click to expand...
Click to collapse
For someone who's rooting devices for a long time, you should know better.
For the moment, there is no rooting without unlocking the bootloader. The locked bootloader only boots unmodified kernel packages signed by Sony. The stock kernel only mounts unmodified /system partitions (dm-veritiy) -> No modification without unlocking.
You CAN NOT backup TA with .185, you have to DOWNGRADE to LP.266. -> E6533 (28.0.A.8.266)
TA backup is not mandatory, but recommended, especially if you want stuff like X-reality and camera de-noise.
And finally, there are no guarantees that the steps required to root are safe and easy.

nica_ro said:
For someone who's rooting devices for a long time, you should know better.
For the moment, there is no rooting without unlocking the bootloader. The locked bootloader only boots unmodified kernel packages signed by Sony. The stock kernel only mounts unmodified /system partitions (dm-veritiy) -> No modification without unlocking.
You CAN NOT backup TA with .185, you have to DOWNGRADE to LP.266. -> E6533 (28.0.A.8.266)
TA backup is not mandatory, but recommended, especially if you want stuff like X-reality and camera de-noise.
And finally, there are no guarantees that the steps required to root are safe and easy.
Click to expand...
Click to collapse
Thanks for your reply. I read somewhere in this forum that TA backup is not required, we can activate X-reality and others with a drmrestore mod?

nica_ro said:
Managed to successfully root my Z3+ Dual.
How I dit it:
1. Downgraded to LP in order to back up my TA (required by the tool = E6533 (28.0.A.8.266)). Enabled developer and USB debugging.
Used this guide to back up TA.
2. Unlocked bootloader using flashtool (I obtained prior the unlock code from Sony http://developer.sonymobile.com/unlockbootloader/)
3. Read thoroughly this thread and downloaded all necessary apps (SuperSU, fastboot adb, latest MM .ftf (32.1.A.1.185)).
Attention! In addition to what you will find in that thread, you need fastboot .
4. Flashed MM 32.1.A.1.185. Enabled developer and USB debugging.
5. Extracted the kernel in order to root it. Prepared the rooted kernel with the provided tool, checked it and flashed it. Uploaded the saved TA keys. Attention! Copy the extracted kernel, TA keys and fastboot in the same directory.
Commands used (Shift+Right click on the containing directory):
Code:
rootkernel kernel.elf new_kernel.img TA.img
- Unpacking kernel
Found elf boot image
Found appended DTB
- Unpacking initramfs
- 64-bit platfrom detected
- Disabling dm-verity
- Disabling SONY RIC
- Installing TWRP
- Found SuperSU-v2.65-20151226141550.zip
Adding service entry for SuperSU
- Configuring secd
- Configuring wvkbd
- Configuring drmserver
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
fastboot boot kernel_x.img
downloading 'boot.img'...
OKAY [ 2.187s]
booting...
OKAY [ 0.562s]
finished. total time: 2.749s
fastboot flash boot kernel_x.img
sending 'boot' (24760 KB)...
OKAY [ 2.180s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 2.380s
flash_dk TA.img DK.ftf
- Extracting device key
- Creating FTF file for device E6533
- Cleaning up
Done
6. Booted the phone and...voila!
View attachment 3721907
None of this would've been possible without the hard work of tobias.waldvogel and zxz0O0.
Hope it helps!
Click to expand...
Click to collapse
i've done everything, and after 2nd restart, i cant see any yellow light to boot to recovery/twrp. i've the bootloader, its (maybe) locked again after flash_dk. the first restart after cmd section, i can see the yellow light, but the restart after that i cant. what am i need to do to boot to recovery/twrp? i need to flash some .zip

I literally can't understand what you described. Sorry. What yellow light are you talking about?

nica_ro said:
I literally can't understand what you described. Sorry. What yellow light are you talking about?
Click to expand...
Click to collapse
a yellow light to boot to recovery. i cant see it.

It did not work for me either (no yellow/orange light while booting).
I had to flash the rootable kernel from here:
http://forum.xda-developers.com/xperia-z4/development/rootable-kernel-sxz3-ivy-marshsmellow-t3336607
followed by the recovery from here:
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298

1. Making new kernel called new_kernel.img then flashing kernel_x.img???
2. rootkernel tools is for Z5, script said no twrp for ivy
Update:
1. Change script from kernel_x.img to new_kernel.img flash OK
2. New rootkernel 4.4 twrp OK but not rooted
Update again:
2. Seems to partial rooted on rootkernel 4.31. Partially means sometimes root sometimes not after reboot. Just copy ivy twrp folder from 4.4.
Update 3:
1. Change rootkernel kernel.elf new_kernel.elf
2. Rooted with beta su 2.71.
3. I think it should be 6th step flash DK.ftf created in flash_dk TA.img DK.ftf with flashtool.
4. Xposed with xposed-v84-sdk23-arm64.
Many thanks to nica_ro for paving up the way.

sarjarim said:
1. Making new kernel called new_kernel.img then flashing kernel_x.img???
2. rootkernel tools is for Z5, script said no twrp for ivy
Update:
1. Change script from kernel_x.img to new_kernel.img flash OK
2. New rootkernel 4.4 twrp OK but not rooted
Update again:
2. Seems to partial rooted on rootkernel 4.31. Partially means sometimes root sometimes not after reboot. Just copy ivy twrp folder from 4.4.
Update 3:
1. Change rootkernel kernel.elf new_kernel.elf
2. Rooted with beta su 2.71.
3. I think it should be 6th step flash DK.ftf created in flash_dk TA.img DK.ftf with flashtool.
4. Xposed with xposed-v84-sdk23-arm64.
Many thanks to nica_ro for paving up the way.
Click to expand...
Click to collapse
Changed guide based on minor misunderstandings. rootkernel is now v 4.50, with fixed adb and mtp file access in TWRP for 32.2.A.0.224. All one needs now is to wait for 32.2.A.0.224 (32.2.A.0.224 Algerika DZ and Customized Malayesia are already available for download).

Didnt understand
nica_ro said:
I literally can't understand what you described. Sorry. What yellow light are you talking about?
Click to expand...
Click to collapse
You said you need fastboot? how to achieve that,, when i click fastboot text in your post it takes me to ftf.266 google drive page ??
Will you please explain a little bit more too me ??

arokososoo said:
You said you need fastboot? how to achieve that,, when i click fastboot text in your post it takes me to ftf.266 google drive page ??
Will you please explain a little bit more too me ??
Click to expand...
Click to collapse
Updated the links. Also added the rooted kernel I made. Fastboot command was missing from the adb folder, so I added it.
UPDATE: Managed to root using the same method the lastest 32.2.A.0.224.

Might there be a difference with z3 plus one sim edition?
Do you think there's any difference or a chance that it might not work if done this way with the z3+ E6553?
I'm thinkin' on rooting my device but i wanna be sure before doing anything to it... specially i don't want to lose the DRM keys ...
thanks,

Stumped for upgrading ROM
Either my eyes and brain are getting tired from days of reading, or I'm getting old, or I only root every couple of years (ever since the W810i), so I may be out of practice, but I'm embarrassingly stumped. I understand everything from post#5 but I'm stuck at choosing the proper ROM for flashing and extracting the kernel.
Z3+ Dual (E6533)
The phone came with 28.0.A.8.251, did OTA update to 28.0.A.8.266 to do the TA backup (worked). I've included two screenshots of the before and after [.251 --> .266]:
Now I need to pick the proper updated ROM before I proceed. OTA wants to install 32.1.A.1.163, Xperia Companion is showing 32.2.A.0.253 as well as XperiFirm. The closest match on XperiFirm, I think, is cda 1295-0980? Ukraine? Also, on the box it shows a cda of 1293-8962, Russia?. In the past when I have rooted there has always been a North America Generic so it was an easy pick. On XperiFirm there are numerous Generics other than North America. I'm in North America (Canada), English. What's your advice on the proper ROM to use for my rooting adventures?
Thanks.

FLASH TOOL ERROR: no loader in the bundle. searching for one

( Please forgive me for my language )
First i downloaded latest flash tool from flashtool.net.but it is not detecting the ftf file stored in the firmware folder. But drivers installed correctly also it say that device connected in flashmode with no problem at all.because of the above problem i downloaded old version of flash tool, this time the tool detect my ftf ROM successfully. But when try to flash it i got the error no loader in the bundle. Searching for one.and a pop window shown to select device but nothing inside it (PLEASE HAVE A LOOK AT THE ATTACHED SCREENSHOT).
Downloaded a ROM from some XDA link ( https://drive.google.com/file/d/0B_d8uWGbkaetekphckhPd0dTUms/edit?pref=2&pli=1 )
File name: c6603_10.1.1.A.1.307_BE.ftf
Note: Iam flashing my device because its boot looping

vinchand said:
( Please forgive me for my language )
First i downloaded latest flash tool from flashtool.net.but it is not detecting the ftf file stored in the firmware folder. But drivers installed correctly also it say that device connected in flashmode with no problem at all.because of the above problem i downloaded old version of flash tool, this time the tool detect my ftf ROM successfully. But when try to flash it i got the error no loader in the bundle. Searching for one.and a pop window shown to select device but nothing inside it (PLEASE HAVE A LOOK AT THE ATTACHED SCREENSHOT).
Downloaded a ROM from some XDA link ( https://drive.google.com/file/d/0B_d8uWGbkaetekphckhPd0dTUms/edit?pref=2&pli=1 )
File name: c6603_10.1.1.A.1.307_BE.ftf
Note: Iam flashing my device because its boot looping
Click to expand...
Click to collapse
Connect your phone in the situation in the screenshot.
//For firmware recognizion, newer version of flashtool requires unpacked FTF, so the easiest way to do so is download the firmware from XperiFirm (see screenshot) inside flashtool, and it will unpack the file automatically.

iXaidyiu said:
Connect your phone in the situation in the screenshot.
//For firmware recognizion, newer version of flashtool requires unpacked FTF, so the easiest way to do so is download the firmware from XperiFirm (see screenshot) inside flashtool, and it will unpack the file automatically.
Click to expand...
Click to collapse
Thank you so much friend will try that and let you know. Thankbyou once again

[PERFECT][GUIDE] SP FLASH TOOL For Android One (First-Generation)

{
"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"
}
SP FLASH TOOL GUIDE
Why use sp tool to flash??
SP TOOL works perfectly until you follow a proper guide!
Or else it will make your Phone dEaD !!
When to use Sp Tool??
Use Sp Tool in Following Conditions:-
You want to downgrade your android version..
from MM to LP/KK...
You want your device with stock experience...(out of th box)
Soft Brick...(boot loops,Unable to access recovery,unconditionally stuck at boot,Hang at Boot Logo,etc)
Or Else Simply you want to learn how to flash by sp tool
Donot Use Sp Tool in Following Conditions:-
Unable to mount /system/data/cache in custom recovery...
If you are a complete noob :v
Requirements:-
Windows 7
[*]Active Internet Connection
[*]Some Basic Skills to Read And Understand The Guide
[*]Patience(A LOT!)
[*]Brain
Procedure:-
Download the below files..
Sp Tool & Firmware(As per device)
Extract both in A folder like on desktop/New folder ... or just where ever you like to...
(USE Winrar For Extracting)
After extracting,
STEP 1:-
Open Sp Tool (flash_tool.exe) from the extracted Flash Tool Folder
Click On Scatter Loading Box.
And search and load the SCATTER FILE
Mainly in firmware folder..
And click Open(this will load the Scatter File)
STEP 2:-
On the Flash Tool Screen,
You will Find "Download Only v"
In A Drop Down Box,
Click On It & Select
"FIRMWARE UPGRADE"
(IMPORTANT!! )
Or else you would Loose your
IMEI,MAC Add,etc
STEP 3:-
NOW after following above steps properly...
Make sure you are connected to the internet!
Hit the download button on the screen...
And connect you device without battery(Aslo without sim/sd card) by usb cable
(Prefer to connect usb in usb ports the back of the of pc)
Now As soon as you connect the device,
Windows will Search for the
"Mediatek Preloader USB VCOM Driver"
in the windows update...
Have patience, and let it search & install the driver...
after it has been installed..
The flashing process will start!
If the flash has been interrupted due to delay..
hit download again!
And it will Start!
STEP 4:-
Now wait until the Flash gets completed!
Keep Patience..
Until you See A dialogue box
with "TICK" & Green color background...
Which indicates flash has been completed!
Step 5:-
After successful flashing,
disconnect your device from usb,
insert battery
press power onn button
Done!
You have successfully flashed your phone with sp tool!
NOTE:-
IF your device booted... its well & good..
If not try flashing another firmware...
Hope this guide works for all...
As it worked for me..​

***Downloads***
Micromax Canvas A1 (AQ4501)
Android version - 4.4.4
Build number - KK
Firmware
Flash Tool
Android version - 5.1.1
Build number - LMY47O
Firmware
Flash Tool
Android version - 6.0.1
Build number - MOB30N
Firmware
Flash Tool
Rar Password:-
www.mobilecare107.com
Karbonn Sparkle V
Android Version - 4.4.4
Build Number - KK
Firmware
Flash Tool
Android Version - 5.1.1
Build Number - LMY47O
Firmware
Flash Tool
Spice Dream Uno (Mi-489)
Android Version - 4.4.4
Build Number - KK
Firmware
Flash Tool
Note:-
Code:
Use the Flash Tool provided with the Firmware!
Those are highly recommended
Use another version of Flash Tool,
Only If the recommended Flash Tool,
fails to fix your device!
Always use Firmware upgrade option..
if not then use Download Only!
In rare cases if you wanna try you can use
"Format All+Download"(not recommended)
Suggestions:-
Code:
Well,we all know that .... MMX/Karbonn/Spice..etc
came up with android one devices....
just from different manufacturer...
but those have nearly same Hardware & Software...
All are Sprout!!! (4/8)
So.... accordingly these above files should also work any sprouts as well!!!
​

Credits:-
@Mayur_Dhuri (For testing 6.0.1 Firmware)
@The-Immortal (For Karbonn Sparkle V KK Firmware)
 @Kunal.Kene.1797 (For Spice Dream Uno KK Firmware)
& Offcourse Me! :v
For more information check the official procedure
that micromax service center follows!
Micromax AQ4501 Flashing Guide:-
https://drive.google.com/file/d/1Y-UK2Oqu1g9iLDkv8A2Rct2rOCjSxX26/view?usp=sharing

Mobile not connecting through usb
My mobile is not onnecting through usb.. it does not download MTP Usb software .. what to do now?
Also i cant download firmware for 6.0.1.. @Mayur_Dhuri

prafullgupta said:
My mobile is not onnecting through usb.. it does not download MTP Usb software .. what to do now?
Also i cant download firmware for 6.0.1.. @Mayur_Dhuri
Click to expand...
Click to collapse
(1st check whether all driver's are installed properly)
Do you hear connecting or disconnecting sounds, after connecting your device to pc? (without battery)
If yes then choose upgrade firmware
If no then your system board is dead

By mistake I have flashed the stock rom using sp flash tool in this condition: "Unable to mount /system/data/cache in custom recovery" .
And now it is booting, not even the boot logo is appearing.
I have used all methods Download only, Format All+Download , but it is not booting.

Saurabhcr7 said:
By mistake I have flashed the stock rom using sp flash tool in this condition: "Unable to mount /system/data/cache in custom recovery" .
And now it is booting, not even the boot logo is appearing.
I have used all methods Download only, Format All+Download , but it is not booting.
Click to expand...
Click to collapse
same case here ( i'm a noob)