Related
Hi,
I currently run rooted 4.03 R1A Wifi only and want to update to R5A wifi only. I would prefer the german firmware instead of CONDIs prerooted US version.
How to do this with dubleflash feature? Is following procedure enough? Or is there a difference to Condis version? Means hidden.img doubleflash?
1.Download ICS FIRMWARE,
2.Copy it to external SD,
3.Run v5.3 AiO - goto 'Custom Rom' submenu, choose 'Decrypt Update' function,
(after it will copy decrypted update, device will reboot and again it will be copied to PC - be patient!)
4.Follow AiO tool instructions,
5.Choose YES for add root etc.,
6.If its R5+ firmware then choose yes for hidden.img replace,
7.Choose YES for sign new custom update,
(JAVA required - if you dont have, then install it, and manually run 'Sign' function),
8.Choose YES for flashing new custom update
9.Wait for finish
Just in case it doesnt work, what is difference between US and Germany? Any problems to expect?
Can I downgrade again to R1A if I run into the bug with powering off all the time?
just follow allinone help,you can get any contry roms
it change temply to us,and chanage back after flash done.
only if you system back to org after wipe,not every one need double flash
you can make you doubleflash by edit rom\META-INF\com\google\android\updater-script
it check blfalg to select to flash one of mmcblk0p2 OR mmcblk0p3
but doubleflash flash BOTH of 2 partions.
(condi's doubleflash rom NOT include any region files)
if you have root and replaced hidden.img,you can always downgrade
Just had some time to give it a try.
After chosing Custom Rom => Create decrypted zip I got stuck with error 7 after booting to recovery. Just gives me option, install from SD or cancel.
I have adb drivers (From BluechipJ) and my revision is 30. Reinstalled the drivers but same error. adb devices shows the tablet as attached.
rubbel4 said:
Just had some time to give it a try.
After chosing Custom Rom => Create decrypted zip I got stuck with error 7 after booting to recovery. Just gives me option, install from SD or cancel.
I have adb drivers (From BluechipJ) and my revision is 30. Reinstalled the drivers but same error. adb devices shows the tablet as attached.
Click to expand...
Click to collapse
OK, solved by myself. Took me some time and reading several threads until I figured out that I had to manually update driver when in recovery.
Required:
- Flashtool in the latest version from: http://flashtool.net
- DualRecovery by NUT as installer.zip: http://nut.xperia-files.com (Download the correct one for your device and at least version 2.8.1+!)
- Root on 23.0.A.2.93 (Download) for example with this method: http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Featurelist:
- SuperSU integrated
- DualRecovery by NUT integrated (2.8.1)
Can be used on locked and unlocked bootloader.
Firmware Files:
D5803 and D5833
- Flashable.zip's and FTF files in folders - sorted by devices
The Flashable.zip i've created with the mighty tool PRFCreator by zxz0O0.
Installation/Update (short) guide:
0. Downgrade to the firmware 23.0.A.2.93 and root it (with giefroot)
0.1. Install the LockedDualRecovery by NUT with the installer.zip (install.bat)
1. Put the downloaded update file (ROM.zip) on your device. I recommend you to put it directly on the device.
2. Boot into the recovery (While rebooting -> when the info LED flashs -> press shortly the VOL button for the Recovery you prefer)
(On Recovery you may create a twrp/cwm backup of your device if you get any issues on updating process!)
3. Flash the ROM update file (.zip) with "install zip".
4. Wipe cache and dalvik cache (perhaps under advanced).
5. Reboot to system.
You may have to wait some minutes on the first boot because of initializing system for first time (optimizing apps etc.).
What to do if you get permission errors? (While installing for example the Recovery)
Untill NUT updates his DualRecovery you should fix permissions with ADB with the following commands:
(tested with command line from the giefroot_V...\files\ directory -> shift + right mouse -> open cmd "here")
Either you could try the modified DualRecovery (installer) by NUT (modified by monx): http://d-h.st/iM9p
Code:
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
Special Thanks to:
[NUT] (DualRecovery and his efforts!)
zxz0O0 (giefroot rooting tool, PRFCreator and his efforts!)
XDA: DevDB Information
[STOCK][D58XX][4.4.4] Firmware 23.0.1.A.5.77 Generic [ROOT/XZDR/SuperSU], Stock Firmware Xperia Z3 Compact
Contributors
meetdaleet
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Stock - 23.0.A.2.93
Version Information
Status: Stable
Release Date: 2015-01-25
Created 2015-01-25
What about d5833 ftf
@muzab a
I'm currently creating the firmware files and will upload them further.
I think they will be available at the evening
Kind Regards
meet
Which ftf to use for d5833?
Great , thanks! In case we can go back to totally stock? (For any case) And for lollipop I imagine will have to flash a rom, right?
Matteo Mazzu said:
Great , thanks! In case we can go back to totally stock? (For any case) And for lollipop I imagine will have to flash a rom, right?
Click to expand...
Click to collapse
You may delete some specific folders on internal SD (sdcard0) and flash a ftf without changing anything (like wipes etc.).
abj2aqua said:
Which ftf to use for d5833?
Click to expand...
Click to collapse
I've just added the D5833 files to the OP.
Kind Regards
meet
The firmware file is D6603, not D5803
Sorry i've just put the wrong link on the OP.
Corrected it right now
Thanks for yozr help!
You can find all my files under:
http://mega.leetbox.net
Kind regards
Meet
Thanks a lot!
i read in the op that this can be flashe don locked bootloaders aswell as unlocked but i also heard that if we want to flash any rom so we must unlock bootloader , so im a bit confused now? can i just flash it on locked bootloader?
pw1nce said:
i read in the op that this can be flashe don locked bootloaders aswell as unlocked but i also heard that if we want to flash any rom so we must unlock bootloader , so im a bit confused now? can i just flash it on locked bootloader?
Click to expand...
Click to collapse
The "ROM" i've opened to you on this thread is a stock rom (just with SuperSU and DualRecovery integrated).
There is the stock kernel inside why it runs on both. Locked and unlocked bootloader!
meetdaleet said:
The "ROM" i've opened to you on this thread is a stock rom (just with SuperSU and DualRecovery integrated).
There is the stock kernel inside why it runs on both. Locked and unlocked bootloader!
Click to expand...
Click to collapse
ok thnx broo , do we need to wipe system , data and then flash or dirty flash ? thanks
edit : i just did as mentioned in op , after flashing i downloaded the recovery and ran install.bat , it installed the new recovery mentioned in op , it rebooted into that recovery , the icons are too damn big , i can only see ''install'' , wipe , backup option on all the screen , now i have no idea how to get out of here , power buttonn evn if i hold wont work , any suggestion?
pw1nce said:
ok thnx broo , do we need to wipe system , data and then flash or dirty flash ? thanks
edit : i just did as mentioned in op , after flashing i downloaded the recovery and ran install.bat , it installed the new recovery mentioned in op , it rebooted into that recovery , the icons are too damn big , i can only see ''install'' , wipe , backup option on all the screen , now i have no idea how to get out of here , power buttonn evn if i hold wont work , any suggestion?
Click to expand...
Click to collapse
Press on Power + high Volume
Two questions, the .93 fw was country specific, this update doesn't require a specific version?
I feel kind of clumsy asking this but i haven't found the meaning of "XZDR", what does it mean?
Thanks!
My root seems to have broke after flashing.Can't mount in root explorer
@pikeylfc,
Did you read the OP?
pikeylfc said:
My root seems to have broke after flashing.Can't mount in root explorer
Click to expand...
Click to collapse
meetdaleet said:
@pikeylfc,
Did you read the OP?
Click to expand...
Click to collapse
There's a problem with RIC on .5.77, making it impossible to mount system r/w. Nothing to do with root, as you can do other root actions just fine.
You just need to update XZDR, [NUT] just uploaded 2.8.1, which has been fixed for Z3C on .77. Also TWRP has been updated.
Edit: Sorry, see that you already updated OP for XZDR 2.8.1.
Sydrox said:
I feel kind of clumsy asking this but i haven't found the meaning of "XZDR", what does it mean?
Thanks!
Click to expand...
Click to collapse
Same question here what is XZDR?
Sydrox said:
I feel kind of clumsy asking this but i haven't found the meaning of "XZDR", what does it mean?
Click to expand...
Click to collapse
ovizii said:
Same question here what is XZDR?
Click to expand...
Click to collapse
XZDualRecovery
What is XZDR? There are two versions one with that and other one without...
Another question: after done all the steps in the op, if we flash another kernel (with locked boot) it will boot?
Thanks
Sent from my D5803 using XDA Free mobile app
Required:
- Flashtool in the latest version from: http://flashtool.net
- DualRecovery by NUT as installer.zip: http://nut.xperia-files.com (Download the correct one for your device and at least version 2.8.1+! And only if you have no working recovery on your device. )
- Full Root on 23.0.A.2.93 (Download) for example with this method: http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598 / 23.0.1.A.5.77
Featurelist:
- SuperSU integrated (2.46)
- DualRecovery by NUT integrated (2.8.3) - Currently not working on Android 5.X!
- Fixed RW (/system) - Thanks to javierdsv
Can be used on locked and unlocked bootloader.
Be careful with encrypted devices. It may cause a softbrick on updating- process and afterwards.
Firmware Files:
D5803 (other Versions will be released asap!)
- Flashable.zip's and FTF files in folders - sorted by devices
(Tanks to javierdsv for sharing the "fixed rw flashable.zip"!)
The Flashable.zip i've created with the mighty tool PRFCreator by zxz0O0.
Installation/Update (short) guide:
0. Downgrade to the firmware 23.0.A.2.93 and root it (with giefroot) (only if you have no root!=
0.1. Install the LockedDualRecovery by NUT with the installer.zip (install.bat)
1. Put the downloaded update file (ROM.zip) on your device. I recommend you to put it directly on the device.
2. Boot into the recovery (While rebooting -> when the info LED flashs -> press shortly the VOL button for the Recovery you prefer)
(On Recovery you may create a twrp/cwm backup of your device if you get any issues on updating process!)
3. Flash the ROM update file (.zip) with "install zip".
4. Wipe cache and dalvik cache (perhaps under advanced).
5. Reboot to system.
You may have to wait some minutes on the first boot because of initializing system for first time (optimizing apps etc.).
What to do if you get permission errors? (While installing for example the Recovery)
Untill NUT updates his DualRecovery you should fix permissions with ADB with the following commands:
(tested with command line from the giefroot_V...\files\ directory -> shift + right mouse -> open cmd "here")
Either you could try the modified DualRecovery (installer) by NUT (modified by monx): http://d-h.st/iM9p
Code:
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
Special Thanks to:
[NUT] (DualRecovery and his efforts!)
zxz0O0 (giefroot rooting tool, PRFCreator and his efforts!)
Chainfire (for amazing SuperSU)
XDA: DevDB Information
[STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU], Stock Firmware Xperia Z3 Compact
Contributors
meetdaleet
ROM OS Version: 5.0.2 Lollipop
ROM Firmware Required: Stock - 23.0.A.2.93/23.0.1.A.5.77
Version Information
Status: Stable
Release Date: 2015-03-16
Created 2015-03-16
Thanks!!! A question. Is it working Mount R/W; R/O?
Thanks!
PherChe said:
Thanks!!! A question. Is it working Mount R/W; R/O?
Thanks!
Click to expand...
Click to collapse
R/O
sototallycarl said:
R/O
Click to expand...
Click to collapse
Just need to flash a zip, i dont need flash other files with Flashtools like .93 to .77 and to hold root access? Did tu flash it? what about blotware?
thanks thanks,
Yeah, I just flashed the zip. No other steps. I have root but cannot write to /system. I see no additional bloatware. Any disabled/frozen apps I did in 4.4.4 remained that way.
Could I just install the flash.zip from rooted .77?
Does anybody try this way?
Can i flesh the zip on my d5833
is android l worthwhile if i lose xzdualrecovery?
sototallycarl said:
Yeah, I just flashed the zip. No other steps. I have root but cannot write to /system. I see no additional bloatware. Any disabled/frozen apps I did in 4.4.4 remained that way.
Click to expand...
Click to collapse
Did you try the steps for "What to do if you get permission errors? "
i making a own flash.zip i will see.
meetdaleet said:
Required:
- Flashtool in the latest version from: http://flashtool.net
- DualRecovery by NUT as installer.zip: http://nut.xperia-files.com (Download the correct one for your device and at least version 2.8.1+! And only if you have no working recovery on your device. )
- Full Root on 23.0.A.2.93 (Download) for example with this method: http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598 / 23.0.1.A.5.77
Featurelist:
- SuperSU integrated (2.46)
- DualRecovery by NUT integrated (2.8.3) - Currently not working on Android 5.X!
Can be used on locked and unlocked bootloader.
Click to expand...
Click to collapse
Im currently on 4.4.4 unlokced bootloader with drm fix. Going to lock it up and restore TA just for this. Im on a custom kernel right now, will this flash a new kernel, propably yes? So i dont have to worry
PherChe said:
Did you try the steps for "What to do if you get permission errors? "
i making a own flash.zip i will see.
Click to expand...
Click to collapse
Should have mentioned I did not. Didn't have a cable handy.
Okay, so right now I'm running the Sony Xperia 4.4.4 ROM with unlocked bootloader and ROOT. But I'm using a custom kernel. Can I apply this update, keep root, and not even wipe data??
bofis said:
Okay, so right now I'm running the Sony Xperia 4.4.4 ROM with unlocked bootloader and ROOT. But I'm using a custom kernel. Can I apply this update, keep root, and not even wipe data??
Click to expand...
Click to collapse
from what i understand you need to restore ta partition and lock up bootloader before updating to stock loli. but you can keep root with the method in the first post
So, just flash the ZIP? Does it overwrite current installed apps? No need to flash kernel and everything else from an ftf file?
How to keep root?
I'm currently on 23.0.1.A.5.77 rooted with no custom recovery installed
Can someone explain me in a simplest way how to upgrage do Lollipop and keep roooted?
Locked bootloader
lamale78 said:
I'm currently on 23.0.1.A.5.77 rooted with no custom recovery installed
Can someone explain me in a simplest way how to upgrage do Lollipop and keep roooted?
Locked bootloader
Click to expand...
Click to collapse
I think you could try to install NUT recovery using the installer for Windows (you have root, so adb commands should work), then flashing this firmware over the one you're using.
Hi guys, thanks for all your posts, I currently have kk version 5.77, pre rooted and dual recovery working, I would like to try this lollipop release pre rooted, I am aware of the inability to use dual recovery, however I will still try it if there is a way to revert back to the release compatible with giefroot, anyone that could help me with this, it will be highly appreciated.
unable to install/boot into recovery
Jac0verflow said:
I think you could try to install NUT recovery using the installer for Windows (you have root, so adb commands should work), then flashing this firmware over the one you're using.
Click to expand...
Click to collapse
I'm trying to install/boot into recovery and nothing works
Downloaded already latest release od xNUT dual recovery installer zip. file , ADB seems to install everyhing, at the end appears: "enjoy recoveries" and that is all,
boots normally as phone always boots. No volume up and down combination works
What I do wrong?
wait for new rec that can work on 5.0
Sent from my D5833
But I have now 4.4
DISCLAIMER:
before doing anything to your device do a backup, im not responsable for any damage to your device
all needed files: http://www.mediafire.com/download/d9egpgwlh2a2c65/Desire610.zip
1) from device open xposed app and uninstall the framework ( you will install it back when the update is finished)
2) now extract debuggerd from the zip i provided and transfer it to your phone, copy it to system>bin folder with a filemanager ( i used root browser) overwrite the existing one and give permissions rwxr-xr-x
3) now put adb folder (extract it because is zipped) to disk c in your pc and put there the stock recovery
4) power off your device, then with power and lower volume key reboot it do fastboot mode
5) connect your phone to usb. over adb folder hold shift and right click it, choose open the command window here
6) a window will pop up write there: fastboot flash recovery recovery.img wait until its done
7) now reboot and finally flash the update
8) now you need twrp and root back. for twrp redo all the 3-4-5-6 steps ( put the twrp recovery in the adb folder)
9) for root download from xda the flashable zip of supersu and flash it with recovery ( before that remove any updates of supersu if you have any)
10) open xposed and install the framework back
11)done.
my english is bad so if you dont understand something let me know
what update is this? is it the stagefright patch or something else?
MGfusion said:
what update is this? is it the stagefright patch or something else?
Click to expand...
Click to collapse
yes for the ota that fixes stagefright, and for the future ones
Stuck
porozex said:
DISCLAIMER:
before doing anything to your device do a backup, im not responsable for any damage to your device
1) from device open xposed app and uninstall the framework ( you will install it back when the update is finished)
2) now extract debuggerd from the zip i provided and transfer it to your phone, copy it to system>bin folder with a filemanager ( i used root browser) overwrite the existing one and give permissions rwxr-xr-x
3) now put adb folder (extract it because is zipped) to disk c in your pc and put there the stock recovery
4) power off your device, then with power and lower volume key reboot it do fastboot mode
5) connect your phone to usb. over adb folder hold shift and right click it, choose open the command window here
6) a window will pop up write there: fastboot flash recovery recovery.img wait until its done
7) now reboot and finally flash the update
8) now you need twrp and root back. for twrp redo all the 3-4-5-6 steps ( put the twrp recovery in the adb folder)
9) for root download from xda the flashable zip of supersu and flash it with recovery ( before that remove any updates of supersu if you have any)
10) open xposed and install the framework back
11)done.
my english is bad so if you dont understand something let me know
Click to expand...
Click to collapse
Hey man need some help here. I followed all your steps but still can't manage to update my device. when it starts to update in recovery mode it gets upto 40% and then a red triangle appears. And then I am still in my old software (1.29.707.1)
adnan.rakib said:
Hey man need some help here. I followed all your steps but still can't manage to update my device. when it starts to update in recovery mode it gets upto 40% and then a red triangle appears. And then I am still in my old software (1.29.707.1)
Click to expand...
Click to collapse
If you have jmz kernel flash the stock one and overwrite again debuggered, if still dosent work get the debuggered file of your stock untouched Rom ( 100% clean no root,removed system files etc). If still fails that means you removed some system files from your device and ota blocks update
porozex said:
If you have jmz kernel flash the stock one and overwrite again debuggered, if still dosent work get the debuggered file of your stock untouched Rom ( 100% clean no root,removed system files etc). If still fails that means you removed some system files from your device and ota blocks update
Click to expand...
Click to collapse
hi,
I flashed the stock kernel, stock recovery and pasted the debuggered you attached but it still fail on 40%...I don't know where to get the ruu for the eu rom...any ideas?
vacs03 said:
hi,
I flashed the stock kernel, stock recovery and pasted the debuggered you attached but it still fail on 40%...I don't know where to get the ruu for the eu rom...any ideas?
Click to expand...
Click to collapse
Maybe you remove some apps from the system? If yes install them back from the at&t version here on this forum with the odex files. The only way to update is to have a 100% untouched Rom and a clean debuggered file
Need some help here
vacs03 said:
hi,
I flashed the stock kernel, stock recovery and pasted the debuggered you attached but it still fail on 40%...I don't know where to get the ruu for the eu rom...any ideas?
Click to expand...
Click to collapse
How did you flash the stock kernel?
adnan.rakib said:
How did you flash the stock kernel?
Click to expand...
Click to collapse
You can use the zip from jmz kernel and past there the stock lib files and kernel from a backuped stock Rom, then flash
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...