Develop Bugs

[Update] Pre-rooted stock 6.2.1 update (secure and unsecure boot images)

I've put together a rooted version of the stock 6.2.1 update if anyone wants to have at it. I flashed this on my own Fire with TWRP and it boots and runs fine, but I haven't done any other testing. Shouldn't need to wipe /data if you're coming from a 6.2 system, not sure about other ROMs like CM. Of course, I highly recommend you make a backup before flashing (good habit, and all that). To install just put it onto your Fire's /sdcard partition, boot into TWRP and install the zip. Note that TWRP will complain that it can't find the /misc or /sd-ext partitions. This is normal, those partitions don't exist on the Fire, but it won't affect the installation.
I downloaded the stock zip from the link in this post: http://forum.xda-developers.com/showpost.php?p=20509203&postcount=91 and then I changed the following from the stock zip file:
Removed the bootloader and recovery.img updates
Removed the backup_data.zip because it doesn't make sense, really (it looks like it just extracts to /backup/, but if you flash it it will wipe your /data partition?)
Added busybox, Superuser and the su binary. Should be properly symlinked and permissions set correctly.
Modified the updater-script for the above things.
Additionally, if you have the Market installed you may need to re-install it after updating since Amazon didn't do this as a patch - it just formats /system and replaces it. If you updated the Market manually then the newer version should survive in /data/app. Also, if you installed any custom frameworks or libraries (e.g. the maps framework to use Google Currents and whatnot) then you'll need to reinstall those. Basically, anything you added or modified on /system will be gone.
Edit: Thanks sadlius for pointing me to dsixda's kitchen! I've added a version with an unsecure boot image (so you get root by default on a shell). I'll leave the old one in case anyone would prefer the secure boot image. I've also uploaded the boot image itself for anyone who might have already flashed the secure 6.2.1 zip. I tried it with fastboot and it booted up fine, so you can test it first with:
Code:
fastboot boot 6_2_1rootboot.img
If it works, you can flash it (permanently overwrites your current boot partition) with:
Code:
fastboot flash boot 6_2_1rootboot.img
Downloads
MOD EDIT: Links no longer valid so removed.
Multiupload, courtesy sadlius:
update-6.2.1-rooted-secureboot.zip
Stock rooted update 6.2.1, secure boot image
update-6.2.1-rooted-unsecureboot.zip
Stock rooted update 6.2.1, unsecure boot image
Multiupload, courtesy intel352 (md5's should be the same):
update-6.2.1-rooted-secureboot.zip
Multiupload:
6_2_1rootboot.img Unsecure 6.2.1 boot image
Original Downloads:
Removed these so Dropbox won't yell at me anymore ​

First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.

You sir are a good Man....

sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
Click to expand...
Click to collapse
I got the "Cannot load volume /misc!" error, too, but it seems to be okay anyway. The KF simply doesn't have a /misc partition.
Curious that it can't open the zip, though, but I'll wait until after your second attempt to try troubleshooting.

sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
Click to expand...
Click to collapse
I have seen the same errors when I installed TWRP. It didn't seem to make a difference to it loading.
All but the last line.
E:Unable to open zip file.
Click to expand...
Click to collapse
I think that is the real error.

I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?

isn't 6.2 is latest ? where did 6.2.1 came from?

HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!

sadalius said:
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
Click to expand...
Click to collapse
I do it manually. The update had a .bin extension but it was really a .zip, so I renamed it, extracted it, and made the modifications I wanted (like adding su/Superuser). Then I just re-zipped it.
Don't know if it's the most "efficient" way to do it, but it's straightforward enough and it's how I've always done it...

Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.

tes5884 said:
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
Click to expand...
Click to collapse
Edit: Pointed out in another post - the system image might be too big to flash via fastboot (like I said, I've never actually tried to use these). If you can get into fastboot you can try flashing a recovery, though, and then use that to try dd'ing the system image over or something.
Edit 2: Took down links since I exceeded my Dropbox bandwidth.

Can anyone verify this works? I mean the 6.2.1 pre rooted update zip
Sent from my Triumph using XDA App

dueltothedeath said:
Can anyone verify this works?
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.

sadalius said:
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
Click to expand...
Click to collapse
Anychance you could explain them to me? Working for me as well just curious what they mean.

sadalius said:
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
Click to expand...
Click to collapse
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!

fbm111 said:
Anychance you could explain them to me? Working for me as well just curious what they mean.
Click to expand...
Click to collapse
When I first tried to install I got these error messages:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
since the kindle fire does not have a /misc volume or /sd-ext/ partition, it would give those errors. Those are nothing to worry about. The last error, Unable to open zip file was a real error, but it was cause when I transferred the file to flash to the KF, it got corrupted somehow. I just deleted it from the kindle using file expert and re-transferred it then tried flashing again. All was well at that point. I still got the cannot load volume /misc! and unable to stat '/sd-ext' but like I said, those do not exist on the kindle, thus the messages. But it still installs correctly.
---------- Post added at 05:05 PM ---------- Previous post was at 04:49 PM ----------
eldarerathis said:
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
Click to expand...
Click to collapse
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.

I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.

sadalius said:
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
Click to expand...
Click to collapse
I just tried using dsixda's kitchen to modify the boot image and it looks like it worked. I can boot it in fastboot at least! I'm going to package it up and try flashing it for some testing. Thanks a lot!
neilrl79 said:
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
Click to expand...
Click to collapse
It seems like a lot of little changes, so far. You can remove things from your carousel by long pressing them, and you can restrict certain access to your one-click and stuff. It also looks like the "Device" menu in settings got a little facelift because it lists "Application Storage" and "Internal Storage" separately (which I don't think it did before).

I flashed 6.2.1 unsecured .zip via twrp and received two E:Cannot load volume /misc! errors. I then wiped cache and dalvik, and booted up. Everything including Voodoo OTA root works fine. As you said though, google market was obliterated. I am about to put it back.
Edit: after sticking vending.apk back in /system/app and fixing permissions it appears everything is 100% back to order including market and running 6.2.1. I can't thank you enough. 6.2.1 feels much snappier, although it might be a placebo effect.

does this work if i am already on 6.2.1?

Fastmode and Recovery Mode error with KFU e TWRP

Hello All!!! I have a question about TWRP. Actually my Kindle Fire (6.3.1) was rooted with KFU and I use JB rom.
When I launch the Fastboot Mode or Recovery mode from KFU i received an error. (pic attached)
Could you help me??:laugh:
Regards
Marco

geppo78 said:
Hello All!!! I have a question about TWRP. Actually my Kindle Fire (6.3.1) was rooted with KFU and I use JB rom.
When I launch the Fastboot Mode or Recovery mode from KFU i received an error. (pic attached)
Could you help me??:laugh:
Regards
Marco
Click to expand...
Click to collapse
I was running ics before and I noticed the driver ids changed on jelly bean your winusb ini needs to be augmented to make it work drivers removed and reinstalled as for your error did kfu indicate your bootmode and online status before starting?

Thepooch said:
I was running ics before and I noticed the driver ids changed on jelly bean your winusb ini needs to be augmented to make it work drivers removed and reinstalled as for your error did kfu indicate your bootmode and online status before starting?
Click to expand...
Click to collapse
OK. I tried to uninstall the driver, but I'm not sure. How I can delete safely the driver and how I can augment the winusb.ini??
TKS.....

geppo78 said:
OK. I tried to uninstall the driver, but I'm not sure. How I can delete safely the driver and how I can augment the winusb.ini??
TKS.....
Click to expand...
Click to collapse
Also quick question if your using the new twrp likey it breaks some of the abilities of kfu
As kinfuans has suggested here http://forum.xda-developers.com/showthread.php?t=1592681&page=16
I will have to peer into the issue of the id change later to give you a solid answer as I am not near my pc at the moment but go to device manager and under android phone if it says android adb interface and not android composite adb interface then its using the wrong driver at the moment. Right click and go to properties and select hardware id that shows you what the winusb ini should be changed to. I will look later to see if I can show you how it should be changed as a form of reference read this thread http://forum.xda-developers.com/showthread.php?t=1625356 hope it helps
---------- Post added at 07:38 AM ---------- Previous post was at 07:33 AM ----------
Also what are you trying to do exactly cause there could be an easyier way?

Thepooch said:
Also quick question if your using the new twrp likey it breaks some of the abilities of kfu
As kinfuans has suggested here http://forum.xda-developers.com/showthread.php?t=1592681&page=16
I will have to peer into the issue of the id change later to give you a solid answer as I am not near my pc at the moment but go to device manager and under android phone if it says android adb interface and not android composite adb interface then its using the wrong driver at the moment. Right click and go to properties and select hardware id that shows you what the winusb ini should be changed to. I will look later to see if I can show you how it should be changed as a form of reference read this thread http://forum.xda-developers.com/showthread.php?t=1625356 hope it helps
---------- Post added at 07:38 AM ---------- Previous post was at 07:33 AM ----------
Also what are you trying to do exactly cause there could be an easyier way?
Click to expand...
Click to collapse
Ok actually on my device manager I find Android Composit ADB Interface and I can't change......

How to install TWRP 2.2?

ray124 said:
How to install TWRP 2.2?
Click to expand...
Click to collapse
to install TWRP use KFU.

ray124 said:
How to install TWRP 2.2?
Click to expand...
Click to collapse
if your already rooted the easyiest way is smirkis scripts http://forum.xda-developers.com/showthread.php?t=1500935
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
geppo78 said:
Ok actually on my device manager I find Android Composit ADB Interface and I can't change......
Click to expand...
Click to collapse
well that what you want te see that is the correct form I think you misunderstood

ok I looked into your error And my drivers are good kfu fails to enter the device into recovery mode or fastboot and I get the same error you do seems that part of kfu is broken for us here is how to manually fix that problem http://forum.xda-developers.com/showthread.php?t=1414832

Thepooch said:
ok I looked into your error And my drivers are good kfu fails to enter the device into recovery mode or fastboot and I get the same error you do seems that part of kfu is broken for us here is how to manually fix that problem http://forum.xda-developers.com/showthread.php?t=1414832
Click to expand...
Click to collapse
I'm sorry ... I made ​​a mistake installing J.B. I tried as you said, but remains locked at bootlogo, and I need KindleUnbrick to solve, other ideas??

pm sent

SOLVED

Sucessfully flashed 98.18.78 recovery into Locked 98.30.1

I understand it is currently not possible to unlock a Razr M with 98.18.94 or 98.30.1 OTA. Never the less, I had been trying to restore a previous VooDoo root that I deleted before the last OTA. Through the experimenting, I screwed up the flash on my phone, and recovering it, I found something that might be interesting.
As others pointed out, downgrading does not work. Flashboot gives various errors. When I screwed up my file system, I was able to flash from 98.18.94 (which I had) to 98.30.1 (which was the only download I could find) using RSD Lite. I was lucky it worked. And since I have been able to experiment and keep flashing 98.30.1 over and over.
I would like to report that in my experiments, I noticed an interesting fact about the recovery.img:
I am able to flash stock 98.18.78 recovery to my phone running 98.30.1.
I have verified the recovery.img contents are not the same, according to a WinMerge file compare, they are ~10% the same
When I try to flash twrp or cwm recovery, the only fastboot error is to the effect "wrong partition size".
The size of .78 and 98.30.1 recovery are the same, 10,485,760 bytes
On the other hand, if I try to flash the .78 system.img fastboot, or use RSD lite to flash .78, I see different security related errors on the phone's fastboot screen- none of which mention partition size. Of course, this is related to the Locked Bootloader I have.
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Right now my Razr M has gone from 98.18.94 to 98.30.1 with a 98.18.78 recovery. And I'm working ok.
I am not a professional Android Dev. But I am going to do the research and try to modify a cwm type recovery to match the size of a Moto recovery, and see what happens.
I invite anyone with real experience to contribute.
Bryan

bryanwieg said:
What did you say?
Click to expand...
Click to collapse
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.

aviwdoowks said:
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
Click to expand...
Click to collapse
I have already found that if I take the OTA recovery and unpackbootimg and then mkbootimg without changing anything.. it recompiles down to aprox 5mb, which is different than the size it started from Moto.
So I am looking at if the size is set in how the img is compiled.

30.1 and .94 are the same updates, just different system versions. As for the other stuff, I'm not even sure what to say. I'm with Avi on this, I definitely would like to see what a dev has to say.

New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004

aviwdoowks said:
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
Click to expand...
Click to collapse
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.

bryanwieg said:
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
Click to expand...
Click to collapse
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.

aviwdoowks said:
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
Click to expand...
Click to collapse
Well, you'r right on the money. I appended data to a CWM recovery the same as Moto did to thiers, including the certificate at the end.
I didn't get a partition size error this time, but I did get a 'Failed to hab check for recovery'.
Granted, I didn't manage to place the 'empty data' at the same point in the file as the stock roms did. Other than that, it must be the certificate.

bryanwieg said:
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Click to expand...
Click to collapse
No, because it first checks the size (or whether it's a valid image at all) and if the size is correct, it checks the signature.

I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.

Really glad to see someone is still trying to find some sort of exploit for this device in it's updated state, it seemed like everyone had completely given up on it. My girlfriend recently grabbed a used Razr M to use for a while but it's fully updated, and I would love to be able to root it for her. I'll be following this thread to see if anything comes of this recovery downgrading

I'm pretty sure you can edit the props from what I can remember.
Sent from my XT907 using xda app-developers app

bryanwieg said:
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Click to expand...
Click to collapse
You can use root eplorer free to extract the single img from the 404 or 411 xml.zips
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Here http://sbf.droid-developers.org/phone.php?device=8
---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------
The razr hd (2), atrix hd, photon Q all use a recovery w/ same key. Git to work man!

Re:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.

815turbo said:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
Click to expand...
Click to collapse
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.

I am willing to try it out. Win 7 64bit... pass me needed staf to flash it
Sent from my XT907 using xda app-developers app

please do
815turbo said:
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
Click to expand...
Click to collapse
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".

benya274 said:
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
Click to expand...
Click to collapse
I'll post it in just a few minutes. I will also post the required commands and we'll be backing up current recovery. If it fails, it should be no problem to restore your backed up recovery.
Download TWRP image on your phone from: titanroms.com/upload/rec.img
Please get to an adb prompt and run these commands:
su
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak2.img
Please ensure that both copies are 10MB. The dd command should end by saying "10485760 Bytes Copied" on all of the "dd" commands.
Now, you should have two backups of the recovery partition and the TWRP Image you downloaded from here all on your sdcard.
You can follow with these commands AFTER your backup has completed.
cp /sdcard/Download/rec.img /sdcard/rec.img
dd if=/sdcard/rec.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=twrprecbak.img
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.bak
reboot recovery
In the event of a failed attempt at this you can run the following from adb:
su
cd /sdcard/
dd if=/sdcard/recbak1.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give me a holler if you don't understand this well. Good luck, guys.

I am gonna try it out tomorrow,i dont have time to do it tonight cause i need to go to work. My pc on work does not have internet connection I will keep u guys posted on any progress.
Sent from my XT907 using xda app-developers app

Just wanted to say I flashed the old ICS recovery to mine using fastboot commands but it didn't get me very far though.if I then try and flash the corresponding blur zip from recovery it just says invalid signature. Was trying to find a way to downgrade so I could get rooted..
Sent from my XT907 using Tapatalk

[ROOT][D5322][Lollipop][Update]Stable root guide, r/w fix, no FTF requirements

Hello guys,
Today I am presenting stable rooting method for D5322_19.3.A.0.470_Lollipop 5.0 without any old FTF requirement or fear of data loss etc.
Requirements
D5322 with Unlocked bootloader
Current firmware version should be 19.3.A.0.470
Flashtool with updated fastboot and flashmode drivers
50% Battery and a Safe backup (In case of error)
Happy mind
Downloads
1. Recovery kernel (Please download DUAL_RECOVERY_D5322-LP.img for best result) ====>> Here (16 MB)
(Recovery kernel credits goes to our respectable XDA Recognized Contributor @abcdjdj)
2. SuperSU.zip ===> Here (Tested)
3. Download BusyBox ===> Here Tested v1.23.1-Stericson.zip
Rooting procedure
Move SuperSu.zip, BusyBox.zip to your devices and turn off it.
Put downloaded D5322_19.3.A.0.470_Lollipop 5.0.ftf in flashtools firmware folder
Open Flashtool and connect your device in FASTBOOT mode by holding volume UP key.(Blue LED)
Flash recovery kernel in fastboot mode and disconnect the device.
Turn on device,press volume down button continusly when you see pink LED.
Flash SuperSU and BusyBox
Wipe cache and delvik
Turn on device -- Rooted + No read write issue + No SD card problem
Rare issue
=> Some users may face system app removal problem ==> Fix Here
=> Flashtool Cannot unbundle files (Very rare) ==> Fix Here
Feel free to ask questions ......

Not able to perform step 10.
error as :
Click to enlarge image
10/010/2015 18:10:29 - INFO - Selected Bundle for Sony Xperia T2 Ultra (D5322). FW release : 19.3.A.0.470. Customization : Lollipop 5.0
10/010/2015 18:10:29 - INFO - Preparing files for flashing
10/010/2015 18:10:29 - ERROR - Cannot delete C:\Users\'@#&\.flashTool\firmwares\prepared\boot
10/010/2015 18:10:29 - INFO - Cannot open bundle. Flash operation canceled
---------- Post added at 06:45 PM ---------- Previous post was at 06:12 PM ----------
any help?
---------- Post added at 07:18 PM ---------- Previous post was at 06:45 PM ----------
stuck at step 10, help me buddy.. I am waiting

Buddy, It seems your end problem == user account permission // corrupt download // file is using by another process

what to do?
no process is running or using any file..
---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------
all I think is problem is with this file only
4. D5322_19.3.A.0.470_Lollipop 5.0 kernel (9MB)
can you reupload or send me this file? 5.0 or 5.0.2 kernel so I can start my device
---------- Post added at 07:58 PM ---------- Previous post was at 07:30 PM ----------
step 10 problem SOLVED
Figured it out! thnx to @ kentexcitebot
I went through C:\Users\name\.flashTool\firmwares and deleted the "prepared" folder under the folder "firmwares".
That fixed the problem, apparently.
Now device is about to boot.. waiting for boot complete

I went through C:\Users\name\.flashTool\firmwares and deleted the "prepared" folder under the folder "firmwares".
That fixed the problem, apparently.
Now device is about to boot.. waiting for boot complete
Click to expand...
Click to collapse
Similar to "FILE IS USING BY ANOTHER PROCESS" Delete means you forced to terminate the process..

rrajesh said:
Similar to "FILE IS USING BY ANOTHER PROCESS" Delete means you forced to terminate the process..
Click to expand...
Click to collapse
yes... my bad.. you need to update steps.. as someone else might get same problem.
root access worked properly. :good:
now my problem is xposed installer.. how to install?
tried flashing zip, but device won't boot.

Xposed is not not available for our device yet...Wait until it fixed for our device. .. You can delete all xposed files to get rid on bootloop.
Solution
1. Flash recovery kernel from #1 post
2. Get rid on Xposed bootloop HERE manually : no flash required

I am not being harsh
I am just letting know what is happening, sorry if I sound harsh
already uninstalled xposed.
ok, so finally I manage to get it working,
1st performed clean installation of 5.0.2 ftf
then followed steps 1 to 9
then deleted the "prepared" folder under the folder "firmwares", (If existed).
then followed step 10 & 11.
started device & updated everything.
I got proper root access & everything is working fine :good:
Thank you :good:
Only problem is, cant boot in Recovery now, after everything is done successfully.

Hw u managed to work xposed on our phne its nt possible as it is not working anymore @rrd84

Thanks bro, root successful but cannot remove/uninstall system apps please help

Check Dis thread @joseph LR http://forum.xda-developers.com/showthread.php?t=3096863

pvnsai73 said:
Hw u managed to work xposed on our phne its nt possible as it is not working anymore @rrd84
Click to expand...
Click to collapse
NO, xposed is not working, bootloops, I said I managed to fix my problem of step 10.
you misunderstood me
---------- Post added at 08:03 PM ---------- Previous post was at 07:56 PM ----------
joseph LR said:
Thanks bro, root successful but cannot remove/uninstall system apps please help
Click to expand...
Click to collapse
yes.. preinstalled apps are not uninstalling by this root method, everything else is good.
but kingo root method can uninstall them, kingo root is chinese root tool,
but I am not able to replace kingo root SuperUser with supersu,
thats y I am sticking with this thread root method.
---------- Post added at 08:11 PM ---------- Previous post was at 08:03 PM ----------
pvnsai73 said:
Check Dis thread @joseph LR http://forum.xda-developers.com/showthread.php?t=3096863
Click to expand...
Click to collapse
I am having this problem, any help?
whichever option I select, mobile either reboot or poweroff
click image to enlarge

joseph LR said:
Thanks bro, root successful but cannot remove/uninstall system apps please help
Click to expand...
Click to collapse
Dear joseph LR,
You can download following apps from PlayStore
Download R/W Checker from HERE
[Open and tap to R/W, if successful your root is with r/w is ok]
System App remover (Using since 2012) Download
Enjoy!!

Dear @rrd84,
I worked on recovery and Xposed with different methods whole Sunday,,,but not working.. RC LED blinks but phone boot normally always
I think we should wait until @Nut (XZ Developer) fix it..
.

@ rrajesh
Thanks for R/W Checker
working perfectly now
yes.. we should wait until @Nut (XZ Developer) fix it..

No Recovery Mode D5322 since rooted Kitkat 4.4.3
I am not able to do Step 6 as my device doesn't boot into recovery mode. Is there any other way of flashing SuperSU and BusyBox? Please help me. Can I flash them using flashtool?
Thank you

badboy_0077 said:
I am not able to do Step 6 as my device doesn't boot into recovery mode. Is there any other way of flashing SuperSU and BusyBox? Please help me. Can I flash them using flashtool?
Thank you
Click to expand...
Click to collapse
No, you can't flash them using Flashtool
Read 1st post carefully for recovery mode...

????
about step no. 4 Flash recovery kernel in fastboot mode and disconnect the device can any one tell me what to do exactly in pic if possible

rustynail1985 said:
about step no. 4 Flash recovery kernel in fastboot mode and disconnect the device can any one tell me what to do exactly in pic if possible
Click to expand...
Click to collapse
#Download recovery kernel an put it on C:\Users\[ UR NAME] \.flashTool [latest flashtool]
#Connect your device in fastboot mode ( Hold volume up and now inset usb...Wait 15Sec)
#Open flash tool ,, click on Flash Device (First icon)
#Select fastboot
#Select flash kernel (Browse downloaded file. change file type sin to img in explorer)
#OK

rrajesh said:
No, you can't flash them using Flashtool
Read 1st post carefully for recovery mode...
Click to expand...
Click to collapse
I did all the steps successfully . But im not able to use flodermount. It gives error unable to write to sd. Root explorer also not mounting to r/w. NextappSd also showing error. Phone is successfully rooted. Please help

[ROOT] [MAGISK] Global ROM on CN Device - WORKING ROOT

THIS IS NOT FOR FAINT OF HEART. DON'T BLAME ME IF YOU BREAK SOMETHING.
Mount system as RW in TWRP. (this took mounting, unmounting, then remounting for me)
Use the following commands CAREFULLY from a computer.
cat /system/build.prop > /sdcard/build.prop
Open the build.prop from the sdcard and edit the following line numbers: 25, 26
You are changing:
ro.product.name=perseus
ro.product.device=perseus
To this:
ro.product.name=perseus_global
ro.product.device=perseus_global
save the file on the sdcard
Go back to ADB session and do this:
cat /sdcard/build.prop > /system/build.prop
IF THIS FAILS YOUR SYSTEM IS NOT RW, UNMOUNT AND REMOUNT IN THE MOUNTS MENU.
Go back to the mounts menu and unmount /system
Flash Magisk 17.3 (18.0 seems to be having intermittent issues with passing checks)
Reboot, and enjoy your CN device running Global with ROOT.

out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal

Great find, works!!
Thanks!!

You're welcome. I may try to make a flashable zip to do this automatically, but I haven't had a chance to look at it.

Work so well, Thanks @PWn3R!

xterminater07 said:
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Click to expand...
Click to collapse
Here is the clue. " 'C:\sdcard\build.prop'."
What is a Windows drive letter doing on an Android? Adb session?

@PWn3R YOU ARE THE MAN

Has anyone tried a custom kernel on the latest global? I tried androplus v 0.6 and it didnt really work. It allows me to replace files in system but not rename because when I overwrite it still says there is an existing file with same name.
Any kernel that works please let me know. I am working with defcomg to get gcam modded more than the current ones.

I would like to try, i already had install last global, and this rtemove my twrp instead the official recovery.... Can you give me all the steps to do from this position? Thank you

I have a problem with camera, force close no matter what I've done. may be build.prop change?

kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
i got this as well... oh well going back to xiaomi eu rom

Hi the change to the build.prop did not break the camera. Mine is working fine. Maybe clear app data for that app?

I do many times, didn't work,
---------- Post added at 11:45 PM ---------- Previous post was at 11:23 PM ----------
This is the error:
java.lang.RuntimeException: unSupported Saturation
at com.android.camera2.compat.MiCameraCompatBaseImpl.applySaturation(MiCameraCompatBaseImpl.java:248)
at com.android.camera2.compat.MiCameraCompat.applySaturation(MiCameraCompat.java:49)
at com.android.camera2.MiCamera2.applySaturation(MiCamera2.java:2486)
at com.android.camera2.MiCamera2.applyCommonSettings(MiCamera2.java:2858)
at com.android.camera2.MiCamera2.applySettingsForCapture(MiCamera2.java:2971)
at com.android.camera2.MiCamera2ShotNormal.generateRequestBuilder(MiCamera2ShotNormal.java:141)
at com.android.camera2.MiCamera2ShotNormal.startShot(MiCamera2ShotNormal.java:59)
at com.android.camera2.MiCamera2.captureStillPicture(MiCamera2.java:2042)
at com.android.camera2.MiCamera2.triggerCapture(MiCamera2.java:1892)
at com.android.camera2.MiCamera2.takePicture(MiCamera2.java:991)
at com.android.camera.module.Camera2Module.startNormalCapture(Camera2Module.java:1130)
at com.android.camera.module.Camera2Module.onWaitingFocusFinished(Camera2Module.java:406)
at com.android.camera.module.loader.camera2.FocusManager2.capture(FocusManager2.java:767)
at com.android.camera.module.loader.camera2.FocusManager2.doSnap(FocusManager2.java:326)
at com.android.camera.module.Camera2Module.onShutterButtonClick(Camera2Module.java:1057)
at com.android.camera.fragment.bottom.FragmentBottomAction.onSnapClick(FragmentBottomAction.java:1653)
at com.android.camera.ui.CameraSnapView$1.handleMessage(CameraSnapView.java:67)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6806)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

@PWn3R, the root is working but there are some functionalities that disappeared in the setting menu such as slider settings, screen color.
For those who wants to revert to CN rom, revert the changes you have done and DO NOT forget to remove Magisk by flashing the uninstaller zip otherwise the device will bootloop.

I restore the original build.prop and boot.img, the camera came back to work. Any workaround?

kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
I didn't notice if the slider settings were there before changing the build.prop. The problem here is that when you flash magisk it's enabling secure boot, which is triggering a check that normally runs when the device is locked. I think we can probably fix that by modifying the file that causes it and then this will work without build.prop changes. I have not had a chance to look into that, but will try to do so.