[DEODEX][C69XX] 14.3.A.0.681 deodex patch - all Z1 variants! - Xperia Z1 Android Development

Read the full topic before doing anything, I am not responsible for any problem that this may cause to your device!
Information
This will deodex 14.3.A.0.681 firmware for Xperia Z1.
This will work on C6902 / C6903 / C6906 / C6943 (be sure to use the correct version).
Requirements
Xperia Z1 with 14.3.A.0.681 stock KitKat.
Working recovery (Don't have recovery? Try XZDualRecovery by @[NUT])
Instructions
Flash the zip on recovery.
Clear dalvik-cache.
Reboot to system.
Additional info
Before you flash, create a backup on your recovery (in case anything goes wrong).
This won't root your device!
Base files
C6902_14.3.A.0.681_Customized_IN_1277-2364_R4C.ftf
C6903_14.3.A.0.681_Generic_FR_1276-5833_R5C.ftf
C6906_14.3.A.0.681_Generic_CA_1276-7484_R4C.ftf
C6943_14.3.A.0.681_Generic_BR_1276-7099_R4C.ftf
Downloads
For C6902:
File: C6902_14.3.A.0.681_deodex.zip
Size: 440.4 MB
MD5: 599B0631DF52B3509198D3382883529E
For C6903:
File: C6903_14.3.A.0.681_deodex.zip
Size: 449.8 MB
MD5: 74D7CD5F9A9A1B619C65633EB56F8866
For C6906:
File: C6906_14.3.A.0.681_deodex.zip
Size: 426.3 MB
MD5: 1DECD72A08F945DA9C01A4CC2B7F27D7
For C6943:
File: C6943_14.3.A.0.681_deodex.zip
Size: 452.8 MB
MD5: C159CDF636F53A46AB1291E25FEEF431
Enjoy your deodexed KitKat ROM! And please hit "Thanks" if you liked it.

Thank you for bringing Deodexed package for C6902 and all other variants. :good:

Thank you.
Can you write up a quite guide how to deodex for xperia? I tried, but i got error.

tiunilohmu said:
Thank you.
Can you write up a quite guide how to deodex for xperia? I tried, but i got error.
Click to expand...
Click to collapse
I used Android Kitchen v0.224, with smali/baksmali v2.0.3 on a Ubuntu 12.04 environment.
Take a look: http://forum.xda-developers.com/showthread.php?t=633246

Do I have to do a full wipe before flashing a deodex patch?

Is the dedoxed rom pre rooted?

Suryasis said:
Is the dedoxed rom pre rooted?
Click to expand...
Click to collapse
rpcherrera said:
Do I have to do a full wipe before flashing a deodex patch?
Click to expand...
Click to collapse
Deodex patch has script (installer script) which will delete your framework/app/priv-app folder/files (dex and apk) and copy deodexed apk files with right permissions.
So no, you don't have to delete anything, just flash patch and restart
BTW - in 99.9% it's not prerooted because that's not ROM, that's patch.
To be sure you'll preserve recovery and root you can always flash latest recovery by NUT and superSU after flashing deodex patch but before you restart.
Sent from my C6903 using Tapatalk

funky0308 said:
Deodex patch has script (installer script) which will delete your framework/app/priv-app folder/files (dex and apk) and copy deodexed apk files with right permissions.
So no, you don't have to delete anything, just flash patch and restart
BTW - in 99.9% it's not prerooted because that's not ROM, that's patch.
To be sure you'll preserve recovery and root you can always flash latest recovery by NUT and superSU after flashing deodex patch but before you restart.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Forgive my ignorance, I'm on Stock rooted .681, so if I flash this patch I will lose recovery and root?

rpcherrera said:
Forgive my ignorance, I'm on Stock rooted .681, so if I flash this patch I will lose recovery and root?
Click to expand...
Click to collapse
No...I just said that...
Just flash patch and you'll be fine .
If you are not sure, flash latest recovery after deodex patch and restart to be 100%.
Sent from my C6903 using Tapatalk

funky0308 said:
No...I just said that...
Just flash patch and you'll be fine .
If you are not sure, flash latest recovery after deodex patch and restart to be 100%.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Done! Also flashed the latest XZDualRecovery.

On 6906 flashing the deodex rom causes FC on both Location service (when choosing Detection accuracy) and on language/input option in settings. Tryed with and without the deodex rom and it is working fine without.

slayer2333 said:
On 6906 flashing the deodex rom causes FC on both Location service (when choosing Detection accuracy) and on language/input option in settings. Tryed with and without the deodex rom and it is working fine without.
Click to expand...
Click to collapse
Can I have the MD5 hash of the zip that you downloaded?
MD5.exe
Place md5.exe and the deodex zip on the same folder, open an elevated prompt window and type:
Code:
md5 C6906_14.3.A.0.681_deodex.zip >> md5.txt
Then open the file md5.txt that is in the same folder now.
I think you downloaded an old zip that was in the topic on the first day, which had Settings.apk deodexed with API 19, which is the right API for KitKat but it force closes in some menus.
The solution come from @krabappel2548 he suggested to deodex Settings.apk using API 16, then I updated the packages for the 4 variants.
Instead of downloading and applying the entire zip you can replace your Settings.apk
Settings.apk
Using a root file explorer, place it on "/system/priv-app" and set the permissions to 0644 (rw-r--r--).
Sent from my Xperia Z1 using Tapatalk Pro

RHBH said:
Can I have the MD5 hash of the zip that you downloaded?
MD5.exe
Place md5.exe and the deodex zip on the same folder, open an elevated prompt window and type:
Code:
md5 C6906_14.3.A.0.681_deodex.zip >> md5.txt
Then open the file md5.txt that is in the same folder now.
I think you downloaded an old zip that was in the topic on the first day, which had Settings.apk deodexed with API 19, which is the right API for KitKat but it force closes in some menus.
The solution come from @krabappel2548 he suggested to deodex Settings.apk using API 16, then I updated the packages for the 4 variants. ]
Instead of downloading and applying the entire zip you can replace your Settings.apk
Settings.apk
Using a root file explorer, place it on "/system/priv-app" and set the permissions to 0644 (rw-r--r--).
Sent from my Xperia Z1 using Tapatalk Pro
Click to expand...
Click to collapse
Here's what i get with your command
Code:
BF0770C607FE311B832D98EE79C3F452 C6906_14.3.A.0.681_deodex.zip
You're right, its different from the actual one. Thanks !

When I flash zip file for my C6902 with CWM (6.0.4.7), my screen is of and on suddenly, nothing happen.
When I do with TWRP, it says "unable to mount system".
My rom's still not deodexed.
What should I do?

Raxtinhax said:
When I flash zip file for my C6902 with CWM (6.0.4.7), my screen is of and on suddenly, nothing happen.
When I do with TWRP, it says "unable to mount system".
My rom's still not deodexed.
What should I do?
Click to expand...
Click to collapse
Are you using XZDualRecovery? Take a look at the version number > External SD Card > XZDualRecovery > XZDR.prop
If it shows something between 2.7.96~2.7.98
Run this as administrator with your phone connected to the computer with Debug mode ON, this will update your XZDualRecovery to version 2.7.99 which fix system mount as writable on KitKat.
C69XX_14.3.A.0.681.patch.zip (9.15MB)

RHBH said:
Are you using XZDualRecovery? Take a look at the version number > External SD Card > XZDualRecovery > XZDR.prop
If it shows something between 2.7.96~2.7.98
Run this as administrator with your phone connected to the computer with Debug mode ON, this will update your XZDualRecovery to version 2.7.99 which fix system mount as writable on KitKat.
C69XX_14.3.A.0.681.patch.zip (9.15MB)
Click to expand...
Click to collapse
I can't find folder XZDualRecovery in my Sdcard folder.
I use this rom so I thought my version is 2.7.99 already.
http://forum.xda-developers.com/showthread.php?t=2687443

Raxtinhax said:
I can't find folder XZDualRecovery in my Sdcard folder.
Click to expand...
Click to collapse
How did you installed recovery on your device?

RHBH said:
How did you installed recovery on your device?
Click to expand...
Click to collapse
I use this rom so I thought my version is 2.7.99 already.
http://forum.xda-developers.com/showthread.php?t=2687443
Oh, I see now. My fault, I was searching in Sdcard while it in Extcard. It doen't say anything about version.

Raxtinhax said:
I use this rom so I thought my version is 2.7.99 already.
http://forum.xda-developers.com/showthread.php?t=2687443
Oh, I see now. My fault, I was searching in Sdcard while it in Extcard. It doen't say anything about version.
Click to expand...
Click to collapse
If you're already on KitKat, flash the patch I posted.

RHBH said:
If you're already on KitKat, flash the patch I posted.
Click to expand...
Click to collapse
But I can't flash your patch.
Just like I said. :crying:

Related

[ROM] i9000B deodexed froyo VJJPA

This is the froyo of Vivo from Brazil deodexed, its /system/app and framework inside a tar file
http://www.2shared.com/file/38XhmrXs/DeodexSysFw.html
just extract in / and then rm al the odex
Luis,
can you please post a more detailed procedure on how to update to Froyo using this file? btw... my Galaxy is from Claro. Do you know if all the functions will work normally?
thanks a million!
if you have the same rom it should work, but just to be sure, you can make a backup of framework and app under /system
what i do to use this is:
Code:
adb push this_file /sdcard/
adb reboot recovery
//choose apply update.zip (it fails, but it will mount the internal sd) in recovery
cd /
tar xvf /internal_sd/this_file.tar
reboot
and thats all, it should take a few more minutes to boot than normal until the cache is built
hi all
it is possible to put the full rom froyo of Vivo from Brazil deodexed for download.
I need it to install the theme beautiful ANDRODeNa GaLaSSiA because in my normal rom froyo I9000BVJJPAI can not install.
link of theme:http://forum.xda-developers.com/showthread.php?t=770507
image of theme:http://img46.imageshack.us/i/jdytetjnbvmvcxjhfyjgfcj.jpg/
thanks.
you mean a full PDA/odin image ?
Yes
I am using this rom installed by odin (http://forum.xda-developers.com/showthread.php?t=858483) , but I do not know change these files of topic
[HACK] i9000B deodexed Froyo VJJPA
or a guide to teach me
Swype
luismanson said:
This is the froyo of Vivo from Brazil deodexed, its /system/app and framework inside a tar file
http://www.2shared.com/file/38XhmrXs/DeodexSysFw.html
just extract in / and then rm al the odex
Click to expand...
Click to collapse
Could you, please, extract the swype.apk from this ROM? I'd like to add the pt-BR swype keyboard to my i9000
Thanks
dclobato said:
Could you, please, extract the swype.apk from this ROM? I'd like to add the pt-BR swype keyboard to my i9000
Thanks
Click to expand...
Click to collapse
hi, i have a mess here, but this is the file
luismanson said:
hi, i have a mess here, but this is the file
Click to expand...
Click to collapse
Thanks a lot for the file!
luismanson said:
hi, i have a mess here, but this is the file
Click to expand...
Click to collapse
Sorry for asking, but could you please share the libSwypeCore.so from /system/lib? I suppose that I should match the swype.apk version with the libSwype version...
Thanks a lot
luismanson said:
if you have the same rom it should work, but just to be sure, you can make a backup of framework and app under /system
what i do to use this is:
Code:
adb push this_file /sdcard/
adb reboot recovery
//choose apply update.zip (it fails, but it will mount the internal sd) in recovery
cd /
tar xvf /internal_sd/this_file.tar
reboot
and thats all, it should take a few more minutes to boot than normal until the cache is built
Click to expand...
Click to collapse
Luis, i don't understand the procedure you suggested. If this file is .tar file, my question is:
1 - do i have to zip this file before flashing it?? Recovery will not recognize a .tar file!
2 - Why does it fail when flashed?
criscan said:
Luis, i don't understand the procedure you suggested. If this file is .tar file, my question is:
1 - do i have to zip this file before flashing it?? Recovery will not recognize a .tar file!
2 - Why does it fail when flashed?
Click to expand...
Click to collapse
Its just a tar it has to be extracted on the phone manually
Sent from my GT-I9000B using Tapatalk
hi luismanson
you know if it's possible to install the theme androdena galassia in i9000B Froyo VJJPA ?

[APP][Update] SGS kernel flasher v1.6.2 - flash a kernel within android

This application *requires* root.
This app can flash a kernel within android on Samsung i9000, Captivate, Fascinate, Vibrant and more.
Features:
* backup kernel as update.zip (for recovery)
* flash kernel from zImage, any .tar or .zip that contains a zImage
* reboot
Usage:
backup kernel: creates an update.zip (for recovery) containing a backup of the current kernel with time and date in /sdcard/sgs-kernel-flasher/backup/
choose kernel: choose kernel image (mostly named zImage) or any .tar or .zip that contains a zImage
flash kernel: flashes the kernel
reboot: reboot the phone
Android market: SGS kernel flasher
DISCLAIMER:
The author of this app is not responsible for any damage to your phone that may be caused by usage of this app or by deficient kernel images.
Im curious, is it "bad" to flash to the partitions when in use ?
Shouldn't it be done via recovery ? Something like cwm where you'd choose flash kernel, it would safely restart your phone into recovery where it would flash your zimage and reboot.
Thnx
Daneshm90 said:
Im curious, is it "bad" to flash to the partitions when in use ?
Shouldn't it be done via recovery ? Something like cwm where you'd choose flash kernel, it would safely restart your phone into recovery where it would flash your zimage and reboot.
Thnx
Click to expand...
Click to collapse
This partition is safe to be flashed from within android - otherwise i would not publish an app that can do that.
The partition is not used while android is running - only read at boot.
Just dont use the app with wrong files - you have to know what you are doing.
I improved the app:
v1.0.1 stable:
* added: manual reboot
* added: check selected file for valid zImage
This app is now stable - happy flashing.
oooh naice!
What are the benefits of flashing the kernel while the OS is running ?
EarlZ said:
What are the benefits of flashing the kernel while the OS is running ?
Click to expand...
Click to collapse
For me, it hurts when pressing the Volume keys up/down in Recovery!
Whats the difference between this and the Tuxility app.? It does the same thing..?
/H
Sent from my GT-I9000 using Tapatalk
what about checking ( disabling ) lagfix?
Hrc4u said:
Whats the difference between this and the Tuxility app.? It does the same thing..?
/H
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
This app does not use the redbend_ua binary - no forced reboot.
And the only purpose of this app is to flash the kernel, nothing else.
iiixda said:
what about checking ( disabling ) lagfix?
Click to expand...
Click to collapse
I will implement a check that will show a warning, but disablinf or removing of a lagfix is too much at the moment. There are too much different lagfix approaches and considering them all is pretty complex.
I keep most of kernels on /sdcard/kernals/ directory in .zip (CWM) format.
Any chances of adding support of such files?
Adding .tar should be straightforward too
I have updated the app one more time:
v1.2.1:
added: PDA.tar and update.zip file support
added: choose file starts in /sdcard/sgs-kernel-flasher/
added: lagfix detection and warning
That means you can now select any .tar or .zip that contains a zImage and the app will automatically extract and flash that zImage.
Major break through for easy kernel flashing on i9000, Captivate, Fascinate and Vibrant- please propagate this awesome news.
Btw. the app is now on market.
Ok this is awesome!
(you beat me to it, you know, congrats!)
I'm running the 2.2.1 firmware ( JPX trough KIES) and used the "SuperOneClick 1.5.5" application to root.
When I run the kerner installer, it would tell me that I have a lagfix installed (AFAIK I don't have any) and also tells me that my device is not rooted.
I can confirm that it's rooted by using the root-explorer and have super-user and busybox installed.
Pierreken said:
I'm running the 2.2.1 firmware ( JPX trough KIES) and used the "SuperOneClick 1.5.5" application to root.
When I run the kerner installer, it would tell me that I have a lagfix installed (AFAIK I don't have any) and also tells me that my device is not rooted.
I can confirm that it's rooted by using the root-explorer and have super-user and busybox installed.
Click to expand...
Click to collapse
Did you see the root request dialog?
If not, you may restart the app or just have look what the superuser app says about the permissions of the sgs kernel flasher.
Does it support 'CWM' .zip files?
I mean these where not only zImage resides, but also some other thingies.
I ask this question because I wasn't able to flash SO_4_5_1 kernel using CWM file provided in this topic: http://forum.xda-developers.com/showthread.php?t=811660
file: http://forum.xda-developers.com/attachment.php?attachmentid=467462&d=1292684343
Attempt on JPX+SO_4_5_1 kernel (so basically it was an attempt to reflash of the same kernel)
Code:
zImage extraction failed!
Kernel flash failed!
xan said:
Does it support 'CWM' .zip files?
I mean these where not only zImage resides, but also some other thingies.
I ask this question because I wasn't able to flash SO_4_5_1 kernel using CWM file provided in this topic: http://forum.xda-developers.com/showthread.php?t=811660
file: http://forum.xda-developers.com/attachment.php?attachmentid=467462&d=1292684343
Attempt on JPX+SO_4_5_1 kernel (so basically it was an attempt to reflash of the same kernel)
Code:
zImage extraction failed!
Kernel flash failed!
Click to expand...
Click to collapse
I will check that.
edit: fixed will be released in a few minutes
Bugfix release:
v1.2.8:
fixed: zImage not correctly extracted from .zip-files
Hello,
Many thanks for this so nice app .
I have to inform You that he detects lagfix is running on my phone, but that is not true.
My phone is running on 2.2.1 Froyo, XXJPUI9000, and i flashed all .PIT, PDA, MODEM and CSC files trough Odin.
I rooted My phone with CF-Root.
And ofcourse differenc is visible, I charge my phone each 3 days .
So if this BUG can be fixed would be nice.
Thanks.
xipod said:
Hello,
Many thanks for this so nice app .
I have to inform You that he detects lagfix is running on my phone, but that is not true.
My phone is running on 2.2.1 Froyo, XXJPUI9000, and i flashed all .PIT, PDA, MODEM and CSC files trough Odin.
I rooted My phone with CF-Root.
And ofcourse differenc is visible, I charge my phone each 3 days .
So if this BUG can be fixed would be nice.
Thanks.
Click to expand...
Click to collapse
I will also check that - it is only a warning message, you can ignore that for the moment.
Edit: I need some mount listings, if you have working adb, please run something like this: "adb shell mount > mount-listing.txt" and attach that file to a post in this thread. That will help me to improve the lagfix detection. Thanks.

[10 JAN][SCRIPT]IMG2CWM Converter 1.2.2

birkoffsjunk's HD2 IMG2CWM Converter​
A simple windows batch script to convert DAF builds to Clockwork Recovery ZIPs.
Originally designed for MDJ's Gingerbread NAND and posted here. Results may vary!
Instructions​
Download DAF based NAND ROM
Download & Extract this script
Place Boot.img & System.img into the 'in' folder
Double click 'RunMe.cmd' (not as admin)
Manually make any changes you wish (when prompted)
Once done, update.zip will be in the same location as 'RunMe.cmd'
META-INF Info​How to: Create Clockwork Recovery flash files
How to Create Android Update Zip Package
An updated updater-script (META-INF\com\google\android\updater-script) is required for various other Builds.
Downloads​v1 >>> here <<<
v1.1 attached (7z changed to 9.20 (ghostkid2010) & renamed out folder to temp)
v1.2 attached (Added error checking & support for system.img only)
v1.2.1 attached (Specified xcopy path & removed old 7z.exe)
v1.2.2 >>> here <<< (arif-ali's linux bash script)
Addons​arif-ali's NexusHD2-Gingerbread_V2.0 updater-script
TODO​
Add error checking
Add support for system.img only
META-INF Information
Most importantly keep it simple
License​BSD License for the script not the tools
7zip is GNU LGPL
unyaffs is GNU GPL v2
same post from MDJ
Your script works great extracting the .img file. But it's not able to create zip file. Let me edit your script with the missing file/info.
Download this file and put in folder tools;
http://downloads.sourceforge.net/sevenzip/7za920.zip
change this line;
"%LOC%\tools\7z.exe" a "%LOC%\update.zip" "%LOC%\out\*"
to;
"%LOC%\tools\7za.exe" a "%LOC%\update.zip" "%LOC%\out\*"
and it should work. it will create a zip file.
Enjoy
how it works?
How does it use? What things do I have to put in the folder "IN"?
sathara said:
how it works?
Click to expand...
Click to collapse
let you extract system.img and boot.img from android build, once you extracted all the fill, it will put all the file into a zip file so you can load via CWM
VuNhatVan said:
How does it use? What things do I have to put in the folder "IN"?
Click to expand...
Click to collapse
boot.img & system.img
It has a function to edit apk. But how do you use that function and where do you add your own apk?
10507 said:
It has a function to edit apk. But how do you use that function and where do you add your own apk?
Click to expand...
Click to collapse
it does not have a function to edit apk (correct me if i'm wrong). once you extracted all the files, go into app and add your apk there.
ghostkid2010 said:
let you extract system.img and boot.img from android build, once you extracted all the fill, it will put all the file into a zip file so you can load via CWM
Click to expand...
Click to collapse
In the Build MDJ_FroYo_Revolution_v._2.2_NAND, there is only system.img, no boot.img. How could I have boot.img?
what a usefull tool, thank you!!
VuNhatVan said:
In the Build MDJ_FroYo_Revolution_v._2.2_NAND, there is only system.img, no boot.img. How could I have boot.img?
Click to expand...
Click to collapse
If there's no boot.img, it should still work. all the boot file is already in the system.img
Let me download that build and I can tell you for sure on how to do it.. I smell that a new version of this script will be out..
Yeah it's very much a work in progress, please feel free to attach updated versions... I'll add them to the first post with accreditation
ghostkid2010 said:
If there's no boot.img, it should still work. all the boot file is already in the system.img
Let me download that build and I can tell you for sure on how to do it.. I smell that a new version of this script will be out..
Click to expand...
Click to collapse
Is it work if there is only system.img?
drizztzou said:
Is it work if there is only system.img?
Click to expand...
Click to collapse
with a little bit of editing yes
ghostkid2010 said:
same post from MDJ
Your script works great extracting the .img file. But it's not able to create zip file. Let me edit your script with the missing file/info.
Download this file and put in folder tools;
http://downloads.sourceforge.net/sevenzip/7za920.zip
change this line;
"%LOC%\tools\7z.exe" a "%LOC%\update.zip" "%LOC%\out\*"
to;
"%LOC%\tools\7za.exe" a "%LOC%\update.zip" "%LOC%\out\*"
and it should work. it will create a zip file.
Enjoy
Click to expand...
Click to collapse
can u more detail about "change this line" location ? u mean u have done it already or i have to do it myself ? which file should i edit ?
ikkon said:
what a usefull tool, thank you!!
Click to expand...
Click to collapse
YEAH! Your not kidding man...i was stoked while playing with it...Id also like to know from here...Is there a similar script for SD->NAND bc my favbe ROM has always been CORECells builds of EVO/HD based...Gave me the best batttery of all SD except for the now current NAND builds. So i figure maybe itll be even better on NAND! TAHNKS again so much for your pos t BIRKOFF! ANYone know of the SD->NAND question?
psuser said:
can u more detail about "change this line" location ? u mean u have done it already or i have to do it myself ? which file should i edit ?
Click to expand...
Click to collapse
YOU have to add an "a" after the z in 7z WITHIN the RUNME script...you have to right click it and open with NOTEPAD on PC and add the "a"
psuser said:
can u more detail about "change this line" location ? u mean u have done it already or i have to do it myself ? which file should i edit ?
Click to expand...
Click to collapse
download the new version on page 1, its fixed
Really cool idea!! I gave it a shot, it just reboots after the MAGLDR screen showing the HTC logo over and over until you boot back into recovery. It flashed fine but just wouldn't boot.
VuNhatVan said:
In the Build MDJ_FroYo_Revolution_v._2.2_NAND, there is only system.img, no boot.img. How could I have boot.img?
Click to expand...
Click to collapse
Use the following "RunMetest.bat"
http://hotfile.com/dl/95408413/0c085bd/RunMetest.rar.html
I tested with different build, system.img only, both boot.img and system.img, it was able to create a zip with all the file.
I'm not uploading the whole folder since this was started by birkoffsjunk, I'm just helping
Test it out

[Tool] [SS/DS] [LB] [Deprecated] Nicki Root - Full root on latest firmware

UPDATE: check out TowelRoot app by @geohot! One-click root solution that works with latest firmware released for Xperia M single/dual (provides half-root only, don't forget to apply root fixer)
Nicki Root is deprecated, it got merged in my new dd Flasher tool and works across many devices, not only Xperia M. The attachments and changelog from Nicki Root were kept below for archiving history, but I won't provide support for it anymore. For any problem you may encounter, go to dd Flasher thread. If you want to root Xperia M through dd Flasher, downgrade your device to Android 4.1 or 4.2.2 firmware, root it with Cydia Impactor and follow the instructions from dd Flasher thread.
Changelog
Version 2.0
• Nicki Root now is called dd Flasher
Old versions
Version 1.3.3
• Bugfixes for Linux script
• Updated SuperSU to 2.02
Version 1.3.2
• Make sure the temporary folder exists before pushing the script
Version 1.3.1
• Now compatible with Linux
Version 1.3
• Implement log capabilities (users can pull last log by selecting appropriate option in main menu)
• Drop "reboot in flash mode" (after using dd, system partition layout is different and device can't be rebooted)
• Check if LED can be used to indicate status, otherwise disable it
• Minor code changes
Version 1.2
• Rewrote most of the code
• Script now uses LED to indicate status
• By popular demand, dropped choice command in favour of set command (should work with Windows XP again)
• For every single command, script will now check if it failed or not and warn the user if anything get wrong
• Rewrote the mount/umount routine, loop device is selected automatically and resource busy issues are fixed now
• Can be used with half-rooted devices now (script check if device is fully rooted and apply root fixer at runtime if needed)
• Implemented "reboot in flash mode" command to avoid needing to pull/reinsert battery manually (experimental, sometimes doesn't work)
Version 1.1
• Make sure busybox is installed after first boot (previous versions pushed busybox but didn't install it)
• Drop choice32/choice64 applets and use built-in OS command (Windows XP no longer supported)
Version 1.0.1
• Typo fix (Nicky => Nicki)
• Updated busybox to 1.22.1
Version 1.0
• Initial release
Will test as soon as Indian Firmware Update show up...
Sent from my C2004 using Tapatalk
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
I'll be trying this (probably) in the next hour, I'll post results for the Single SIM afterwards.
RESULTS TIME: This method of rooting worked and I am now running 4.3 with root access. Thank you.
Sent from my C1905 using xda app-developers app
Gonna test after I download 4.1.2 ftf, hope it works
rizla2 said:
Gonna test after I download 4.1.2 ftf, hope it works
Click to expand...
Click to collapse
It works perfectly, I'm now rooted on 4.3 thanks to this. The only error I had was when the tool first tried to push the system.ext4 to the SD Card, it said there wasn't enough space, I just deleted the incomplete copy and then ran the tool again and it worked.
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
mbc07 said:
It took me a lot of time and I tried a lot of methods but I finally managed to root the new 4.3 update without unlocking the bootloader, let's root that thing.
Requirements:
You will need FlashTool and the FTF file of 4.3 update for your phone
You should be running Android 4.1.2/4.2.2 firmware with full root. If you already updated to 4.3, sorry, you'll need to downgrade to 4.1.2/4.2.2 and root it, otherwise this method won't work
You should have at least 1.5GB of free space in your Internal Storage or in your SD Card. If you don't have enough space, the installation will be aborted and your phone will be left intact
Make sure you have full root (eg. your phone doesn't reboot when you remount /system with RW access). Using this method without full root may reboot your phone during the procedure, getting you in a bootloop
Currently the script works only on Windows, I'll try to get a Linux version soon
Getting system.ext4 file: before continuing, we'll need to extract system.ext4 from system.sin present in the update. Open the FTF it with WinRAR or 7-zip and extract system.sin somewhere, then open FlashTool, go to Tools => Sin Editor, locate the system.sin file extracted previously and then click in "Extract Data". You'll get system.ext4 in the same folder you extracted system.sin. Now you're good to go
Procedure:
Download the attached ZIP and unzip its contents somewhere
Move system.ext4 extracted previously to the same folder where root.bat is
Open root.bat and follow the instructions
After the process finished, the script will tell you and your phone will be in a frozen state (it's normal). At that point, you should manually remove the USB cable and then pull/reinsert your battery. DON'T TURN IT ON, we haven't finished yet (turning it on now will get you in a bootloop).
Open FlashTool again and flash the entire 4.3 FTF, but exclude system (if you forget to do so, the root will be removed and you'll need to start over)
After flashing finished, disconnect the USB cable and start your phone. If everything went well you should be in 4.3 now, with full root access
NOTE: I'm not that good with BASH/Shell scripts, and although I had implemented some sanity checks, something may have escaped that checks. So, if you do this procedure and the shell script finish with errors, it's better to start over since something may have not worked and you may be in a partial root state...
Click to expand...
Click to collapse
It worked for me thanks to you
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
iks8 said:
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
Click to expand...
Click to collapse
Flashtoll wil wipe data and cache when you flash 4.3 You don't need to do anything else.
paper13579 said:
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
Click to expand...
Click to collapse
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
joemarshall said:
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
Click to expand...
Click to collapse
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
mbc07 said:
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
Click to expand...
Click to collapse
Yes it did, sort of. The first time I did it I got an error saying there wasn't enough space (I had over 10GB free however). Once I got the error I deleted the incomplete file from my SD Card and then I ran the script again, this time it copied the file fully and then installed properly.
This occurred on the Single SIM C1905 Xperia M by the way.
Yes! Finally rooted. Thanks a lot!
Btw don't forget to change usb mode to mtp instead msc (I've tried msc and it can't copy files)
mbc07 said:
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Click to expand...
Click to collapse
At first time i've had also 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or res
ource busy'
Flash new, clean Android 4.1 solve problem.
Thank you very much.
Hey guys, does this give you full root?
sent from wadiya using my mafroom
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes it does.
I'll check about the loop device errors (apparently they may occur in Xperia M single SIM), thanks for reporting guys...
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes. I implemented the disable ric service method from [NUT] root fixer too
Man, this is a great achievement, you should be proud. Im about to try it now. Wish me luck
sent from wadiya using my mafroom
Before your script use dd it should check:
1. That there is no any apps mounted in /dev/block/loop0 (for example Swift Key). If yes, you will see 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or resource busy' (you can it by type losetup)
2. Phone is in MTP USB MODE. If you set to memory storage mode, Android will not access to sd card with system.ext4 image (script would check that can it access to /sdcard) and you will get mount argument error

The easiest way to root xperia T2 ultra dual { 5.0.2 & 5.1.1 } {.472 & .182}

well friends, its my first post here on xda.
Eventually I found the easiest way to root D5322 (.472 lollipop 5.0.2 firmware)
and
that is
just run kingroot (I tried english version)
kinguser works like a charm
no need to have superuser or superSU
every app that requires root, works as smooth as butter
like busybox force2SD and all.
I attached the english version of kingroot with this post
those who had rooted their (.470) phone with kingroot and repented later , can also try..
well..
.
.
and if you want to get rid of kinguser that had gotten installed after rooting with kingroot
here is a trick..
I am attaching a zip (thanks to @edwuard )
download that zip
put it in internal memory
extarct that zip in internal memory
now you will get a folder named mrw in your internal memory
..
..
install terminal emulator from market
write the following commands
su
(now grant superuser access)
$ will change in to #
now write the second command
sh /sdcard/mrw/root.sh
(there is space after sh . You can copy this command from here and paste to terminal emulator)
after some sequences in terminal emulator..it will launch SuperSU
and ofcourse remove kinguser
update the binary of superSU
verify root with root checker
.
.
that's it !!
Sequel: Rooting D5322 (Android 5.1.1) :
Well it's for those who have a rooted phone (any previous version) [/COLOR]
Download the ftf file of latest firmware 19.4.A.0.182
Download latest version or V 0.8 of prf creator
Download SuperSU.zip
Now put the prf creator somewhere in your PC (let's say on desktop) extract it there.
Add ftf file and superSU.zip in prf creator
Mark all the boxes on right side of prf creator window
Hit create. In 15-20 minutes you will get a zip file named "flashable" in prf folder
Copy this flashable zip and put it in root of SD card of your phone.
Now reboot your phone in recovery
Follow in sequence :
Wipe>Advanced wipe >select cache,dalvik,system,data, internal memory >swipe to wipe>go back to recovery home>tap install>select external sd card >select that flashable zip>swipe to flash>wipe dalvik>reboot to system.
To install recovery:
Download latest nut's xzdr installer zip
Put it somewhere in your computer
Extract it, you will get a folder of same name
Connect your phone to pc in USB debugging mode
Open the extracted folder
Double click the windows installer batch file
Grant superuser access on your phone's screen
Follow the instructions on terminal
(press 1 on your pc as you have SuperSU in your phone)
After successful instalation of recovery, your phone will reboot into recovery.
Reboot the phone into system
.
.
Now you have a rooted 5.1.1 D5322 with latest Dual recovery.
Thanks alot it's so easy way and it work with me
So easy way
Kinguser Not going off
And i am not able to update to 19.3.A.0.472 stuck on 19.3.A.0.470
I have uploaded the Attachment for it...
plzzzz help
read threads before post
there is already a thread for the same and ask dev before sharing his work
XDA rules
excellent.. 5 stars
awesome... working great
aniket553 said:
And i am not able to update to 19.3.A.0.472 stuck on 19.3.A.0.470
I have uploaded the Attachment for it...
plzzzz help
Click to expand...
Click to collapse
1st I had same problem..
Stucked on . 470
Then I relocked bootloader
Then flashed .472
Then tried above method
Working like charm
Sent from my D5322 using XDA mobile app
Bro did I need to unlock my bootloader to follow this prosiser
............
Zx9. said:
Bro did I need to unlock my bootloader to follow this prosiser
Click to expand...
Click to collapse
No.. You don't need to unlock the bootloader
I'm really interested on following your instructions on how to root this, but first... Will this trick also work on the LTE version?
Sent from my D5303 using XDA Free mobile app
rituraj_singh said:
No.. You don't need to unlock the bootloader
Click to expand...
Click to collapse
Thnx bro ur guide is really easy I successfully rooted my phone yeppy??
kyu0911 said:
I'm really interested on following your instructions on how to root this, but first... Will this trick also work on the LTE version?
Sent from my D5303 using XDA Free mobile app
Click to expand...
Click to collapse
Well.. I don't have D5303, so I haven't tried it on that. You may try.
Zx9. said:
Thnx bro ur guide is really easy I successfully rooted my phone yeppy??
Click to expand...
Click to collapse
That was something I had eventually found..I just shared..
aniket553 said:
And i am not able to update to 19.3.A.0.472 stuck on 19.3.A.0.470
I have uploaded the Attachment for it...
plzzzz help
Click to expand...
Click to collapse
copy the command below
sh /sdcard/mrw/root.sh
paste it to terminal emulator after "su" command
Thank you so much!
Thank you so much for sharing. I can now transfer some of my apps to ext sd card. I can now install more games. Though it can't be changed to supersu using the script and the file you've provided due to unable to update binary, foldermount is working perfectly with kingroot. By the way, I'm using the LTE version D5303 with lollipop .472 and it's now rooted.
Great
Hey can anyone tell how to backup ta partition(dmr keys) on t2 ultra dual d5322 i want to unlock my bootloader.
http://forum.xda-developers.com/showthread.php?t=2292598 use Backup Ta from above link. To backup ta partition
everything working great with this method...
can anyone succeeded installing Xposed properly, working?
rrd84 said:
everything working great with this method...
can anyone succeeded installing Xposed properly, working?
Click to expand...
Click to collapse
The Xposed is not working in our unit, the installation makes the device has bootloops.

Categories

Resources