[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?
please fix dead links
dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.
please fix dead links
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.
[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient
[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone
server stilll unreachable.
I have had my fair share of problems modifying android before but I have never had a phone flat out lie to me and say an operation was successful and actually nothing happened at all.
Have had my nexus 6 for a year or so now. Have had minor issues rooting / modifying marshmallow in the past but I figured out it was all caused by the system partition having basically 0 free space. Made a huge mistake and installed to the latest 7.0 OTA. Wanted to simply enable tethering and edit the thermal config to not shut cores down. Should be as simple as pulling the files, editing them, pushing them back to the phone in twrp with the system partition mounted and thats the end of it right? Wrong.
First of all twrp 3.0.2 refuses to let me touch the system partition without some giant prompt about how its going to make itself stick and offer to root the phone. Simple enough I have seen it in previous versions I say yes as usual except twrp proceedes to immediately spew a bunch of superuser files that do nothing throughout the system partition without asking me if I want root. Dumb but whatever. I mount /system as read write and I go edit and replace my two files like usual (build.prop and thermal config). No matter if I ADB push or use twrps built in file manager it claims the file replacement is successful. Reboot into android and not only have both files not been touched (Verified by adb pull) but the recovery gets overwritten with the factory recovery anyways. (NEVER had issues with twrp sticking on marshmallow. Now after every reboot it gets wiped out)
Second of all if I select yes to twrp mounting system as writable and it does its spewing as I mentioned before then installing SuperSU instantly causes the phone to not boot. Rewrite the boot.img to factory and it boots fine OR Rewrite the clean factory system image and the SuperSU boot works fine. But modifying /system with twrp and then running supersu at the same time is a no go. TWRP is obviously doing something stupid to system that pisses off supersu so undoing twrps mess or uninstalling supersu makes it bootable again.
I dont even want root! Everyone is claiming you need to run "settings put global tether_dun_required 0" as root along with adding the usual "net.tethering.noprovisioning=true" in the build.prop to get native tethering working again! On 6.X only the build.prop edit was needed to get it working.
So long story short. I just want native tethering to work and to tweak my /system/etc/thermal-engine-shamu.conf . Is there anyone here who has done this successfully on nougat? I feel like its all twrps fault but im far too tired and frustrated to try another version tonight.
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Strephon Alkhalikoi said:
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Click to expand...
Click to collapse
It's stated in the op he's using twrp 3.0.2.
Didgeridoohan said:
It's stated in the op he's using twrp 3.0.2.
Click to expand...
Click to collapse
I misread his post then. I wonder if perhaps he is running TWRP via fastboot instead of installing it.
Flashing recovery using "fastboot flash recovery XXX.img"
I'm almost entirely new to messing around with stock firmware on a locked bootloader, its been unlocked for 2 years. I relocked it, TA keys are fine, I had TWRP, I was able to write to the system partition, I had external storage write permissions, and all of those things have dissapeared entirely. I was able to use an xposed module for getting external storage permission back.
-I can't install TWRP again because the installer on a locked bootloader requires the system to be remounted rw or already have access to a recovery.
-The xposed solution to the exteral sd isn't ideal, and again I need TWRP or to do it manually by mounting the system rw.
-FlashFire doesn't work regardless of what variation of options I give it.
-I pulled the kernel image out of the pre-rooted zip I initially used but it won't fastboot. It says USB debugging isn't enabled when I try it using flashtool, though it is on when the system is up. I was hoping that the rewrite permissions or possibly even TWRP would be available if I reflashed the kernel image. This won't work.
The reason for being on Lollipop is that for whatever reason, push notifications still really suck for me on Marshmallow, enough so that it isn't a workable option.
Having either TWRP or being able to remount the system rw would, from the look of it, lead to being able to fix the thing entirely.
The only workable solution I have right now is to flash stock Marshmallow, install TWRP which is rather easy on current MM, then reinstall the pre-made zip I already had for Lollipop. This is a huge pain given that I just put a lot of time into my setup and even just the settings I'm using in Xposed would in itself be difficult to restore as its quite a lot. Everything is backed up via Titanium.
Essentially, "Is there a workable solution to my problem that doesn't involve flashing MM, putting TWRP back, reflashing LP, then setting up what I know I need to all over again followed by the inevitable supprise down the line of still needing to re-do some of my apps that didn't quite go well? The goal is to get TWRP back, and this seems like it isn't going to happen if I can't write to the system.
??
Also, If I just pull /data entirely via adb, my laptop already uses ext4 for the filesystem, but it there a way in this scenario where I could absolutely ensure that I could do it, and then put it back while not screwing up file permissions assuming I did the whole falsh MM, install TWRP, flash LP thing?
I download Magisk and No Verity from http://www.desinerd.co.in/how-to-huawei-p20-pro-root-twrp-recovery/.
I have TWRP official installed 3.2.1 with security disabled on the EMUI. I'm trying to install the Magisk and No Verity but I can't find the zip files in the file system. Where is the Download folder located in the file system? Do I have to move the files somewhere else in order to access it from TWRP? I read that the Download folder is in /sdcard, but there are multiple folders with random letters and numbers, like maybe it's encrypted or something?
If I'm rooting wrong, can you tell me how to root?
I tried using the Patched ramdisk of Magisk, but it didn't do anything after reboot and Root Check says not rooted, hence, that's why I'm following this guide to see if this works.
Same
Did you find out how to root as I'm having the same problem
Install the unofficial TWRP. Remove fingerprint/password/pin etc then try again. TWRP doesn't decrypt when they're active.
Hi, having the same issue with TWRP (twrp-3.2.2-0-charlotte.img and twrp-3.2.1-0-charlotte.img) from dl.twrp.me/charlotte/.
How can I repair it? Cant flash Magisk.
Thanks
I've posted before/then it worked (once)/I deleted etc.
I read in another post to try to install busybox, I can not from the Manager.
I thought I'd screwed up the system R/W in TWRP (this is LineageOS 16.x on a Galaxy S5) but it is R/W.
It's not a critical thing, but does bug me. It's taken a month of twiddling everyday to get the phone JUST where I want it and everything working JUST the way I want them to - except this.
I've been looking for a zip of 19.3 (this did work fine with 18.x) to install via TWRP, but can not find one - I'm assuming that there might have been an error installing 19.x through the manager.
As I'm going to put the whole enchilada on my wifes phone this weekend (I REALLY don't need that to backfire ...), I'd like to figure this out. I have NOT tried installing the zips from recovery, but copied to a PC they are intact and the zip is not damaged.
MANY THANKS!