Develop Bugs

[STOCK][C6502&C6503&C6506] Update to 10.1.1.A.1.253 [Root&XZDualRecovery][LB/UB]

[STOCK][C6502&C6503&C6506] Update to 10.1.1.A.1.253 [Root&XZDualRecovery][LB/UB]
After my release for the Z and the success stories on it, i had some requests to do the same for the ZL. Finally I'm ready for it's release! :victory:
Thanks go to @butatx for his invaluable testing contribution and taking one for the team.
Requirements:
Flashtool
A recovery (can be both CWM and TWRP)
NOTE: As some people have problems flashing the update, please update your existing recovery to the latest (BETA) recovery with XZDualRecovery
Current FW version: 10.1.A.1.350 or 10.1.A.1.434: maybe others too, try and let me know!
From the users in the original thread I noticed people using CWM running into trouble because their cache partition is gone. See the 'Known Issues' in the OP of the XZDualRecovery link above for more info and links to a fix. Fix that first before you attempt this update using CWM!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.3 RELEASE (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 his post for it! Thanks m8!
TIP: This ROM is compatible with the shutdown/reboot MOD by @niaboc79
TIP: This ROM and the integrated recovery are compatible with the reboot wrapper by @DooMLoRD, get it here!
C6502: How to update to 10.1.1.A.1.253:
For C6502: Download C6502.flashable.253.zip (Bittorrent: 752MB) and Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6502.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6502-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6602.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6503: How to update to 10.1.1.A.1.253:
For C6503: Download C6503.flashable.253.zip (Bittorrent: 715MB) and Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6503.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6503-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6503.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (Bittorrent: 730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6506.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
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, It will update your NFC with a firmware and after that, all is done!
IMPORTANT NOTE:
For some devices the first or second reboot after the successful upgrade may be used by the ROM/Kernel to upgrade some low-level firmware. This will be done from the screen which normally shows you the kernel logo. This upgrade flash will also happen when on a custom kernel by @DooMLoRD. DO NOT INTERRUPT THAT WHATEVER YOU DO OR HOWEVER LONG IT TAKES! Just let it do it's thing and wait, your phone will continue boot as soon as it's done.
I have done this myself, using my own method on the Z and I have not found any problem yet. :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
All known issues in TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Be especially careful with the cache partition when using CWM. Hopefully version 2.0 solved the cache issues but in case of problems with /cache use the FTF in my files to restore the cache partition if yours ever stops mounting due to the CWM issues, read this and this for more info on that. This FTF was created for .434 but as the cache did not change between .350, .434 and .253 you can still use it to fix the cache partition.
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery the 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
If even that is too much to handle for you, see the patch at the bottom of the OP to flash the fix.
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 .434 /system ONLY using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
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.13
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 SuperUser (default in this ROM) to SuperSU 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 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.

Reserved, just in case

There seems some error with the instructions why you created a stripped file as a zip as it is nota ftf file which cannot be used with flashtool.
I just waiting for the other file currently downloading to finish so I assume you mean used the .253 zip file inside moved to the sdcard of smartphone and the ftf firmware inside of it to the flashtool/firmware folder to flash so I seem confusion on your part.

That will be big help for us
Thank you

Just downloaded both files the stripped file in a zip file not an ftf so what do I do this please as it will need to be convert into a ftf file somehow?
Can you create a stripped ftf file please.

Darkfunnyguy said:
Just downloaded both files the stripped file in a zip file not an ftf so what do I do this please as it will need to be convert into a ftf file somehow?
Can you create a stripped ftf file please.
Click to expand...
Click to collapse
paullu said:
That will be big help for us
Thank you
Click to expand...
Click to collapse
There was a small issue with the download site, which now has been fixed. You can rename the ZIP file you downloaded and change the extension from .zip to .ftf
From there on you can flash it using flashtool.
Sorry guys

Hi NUT, tested your rom, it work flawlessly + rooted , thanks for your work :good:

confused
Is it right that the file called in instruction as"C6506.flashable.253.zip " in real is C6603??:
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
the total confusion with what file has to be renamed and used by Flash tool and which one with CWM. In order to avoid misinterpretation may be NUT closes this thread and open a new one with all corrections.

Successfully updated to 10.1.1.A.1.253 with everything intact including roots and recovery.

Hi, NUT. It works fine. Thanks for your work!

rfg13 said:
Is it right that the file called in instruction as"C6506.flashable.253.zip " in real is C6603??:
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-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 everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
the total confusion with what file has to be renamed and used by Flash tool and which one with CWM. In order to avoid misinterpretation may be NUT closes this thread and open a new one with all corrections.
Click to expand...
Click to collapse
Whups, i might have linked to the wrong file then... Check my download link in my signature in case you get the wrong file, my bad
Sent from my C6603 using xda app-developers app
-- EDIT --
Fixed links in the OP and a typo. Sorry for the confusion!

Thanks Mr. NUT...i'm downloading it now

Kylez said:
Thanks Mr. NUT...i'm downloading it now
Click to expand...
Click to collapse
did i lose everything in phone if i flash this zip?

daniLaLaLaLaLa said:
did i lose everything in phone if i flash this zip?
Click to expand...
Click to collapse
No. Data, programs and settings will be saved.

Bird40 said:
No. Data, programs and settings will be saved.
Click to expand...
Click to collapse
Good, i tried it tomorrow after i wake up from sleep .:thumbup:
Sent from my C6502 using xda app-developers app

Hi,
I seemed to have run in a little trouble with this. Heres what happened - I was running a stock but rooted build 434 before attempting this. My BL cannot be unlocked so also stock Kernel. I wasnt running any recoveries. So I followed the steps in the post to install recovery "XZDualRecovery" which ran the bat file successfully and then rebooted my phone into the CWM recovery for the first time. I then tried to go back to recovery with no luck... tried several times wether with Vol+ (CWM) or Vol- (TWRP). I then followed a different post to install a single recovery which installed properly and I was able to boot my phone in CWM all the time... So Success!!
So i then copied the ZIP to my EXT Card and flashed my phone with the Stripped FTF file, I then rebooted straight to CWM and installed the ZIP from SD Card. Perfect, it rebooted, Android was upgrading x out of 293 apps... That was successfull and I was rooted and inside the ROM. The Gmail app kept crashing so I decided to reboot. Here is the problem, The Sony logo appears followed by the wrench in the white triangle. I wasnt even able to turn off my phone by holding Vol+ and Power. I could only reset with little yellow button next to the SD Card.
I tried to flash my phone with the stock FTF file using flashtool but no luck (Nearly crapped my pants)
Anyway after several attempts, I finally managed to get into flashmode and I am now with build 253 and no root.
Ill flash back to 434 later but would really like to know what I did wrong?
Geez, I think I just wrote a book but I wanted to be clear with everything I did..
Thanks

Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
Click to expand...
Click to collapse
You are steller [NUT], great work here.
as quested above is the cwm backup for safety in case there are issues?
and flash everything, as i have not tried yet do we need to un check wipe, data, cache, appslog?
or does the ftf have the wipe options already unchecked?
Thanks again for the great work.

HackitZ said:
and flash everything, as i have not tried yet do we need to un check wipe, data, cache, appslog?
or does the ftf have the wipe options already unchecked?
Click to expand...
Click to collapse
Yes, when I flash the ftf-file, there were no wipe options.

Crash338 said:
Hi,
I seemed to have run in a little trouble with this. Heres what happened - I was running a stock but rooted build 434 before attempting this. My BL cannot be unlocked so also stock Kernel. I wasnt running any recoveries. So I followed the steps in the post to install recovery "XZDualRecovery" which ran the bat file successfully and then rebooted my phone into the CWM recovery for the first time. I then tried to go back to recovery with no luck... tried several times wether with Vol+ (CWM) or Vol- (TWRP). I then followed a different post to install a single recovery which installed properly and I was able to boot my phone in CWM all the time... So Success!!
So i then copied the ZIP to my EXT Card and flashed my phone with the Stripped FTF file, I then rebooted straight to CWM and installed the ZIP from SD Card. Perfect, it rebooted, Android was upgrading x out of 293 apps... That was successfull and I was rooted and inside the ROM. The Gmail app kept crashing so I decided to reboot. Here is the problem, The Sony logo appears followed by the wrench in the white triangle. I wasnt even able to turn off my phone by holding Vol+ and Power. I could only reset with little yellow button next to the SD Card.
I tried to flash my phone with the stock FTF file using flashtool but no luck (Nearly crapped my pants)
Anyway after several attempts, I finally managed to get into flashmode and I am now with build 253 and no root.
Ill flash back to 434 later but would really like to know what I did wrong?
Geez, I think I just wrote a book but I wanted to be clear with everything I did..
Thanks
Click to expand...
Click to collapse
The triangle showing is your phone flashing a new update to a low level device, NEVER interrupt that process, I believe it's not even possible to skip it.
XZDualRecovery not working is related to a 2.1 incompatible method of reading the keypress. You could have noticed it was already superseded by a BETA release fixing that. It's even included in this Rom release
Your Gmail app crashing can be fixed by clearing its cache from the apps menu. If that doesn't help you can remove it using a root app like titanium backup. Then install it again from play store.
HackitZ said:
You are steller [NUT], great work here.
as quested above is the cwm backup for safety in case there are issues?
Click to expand...
Click to collapse
Exactly, it is just a precaution, a case of better safe then sorry. Your other question got answered by @Bird40.
Sent from my C6603 using xda app-developers app

[NUT] said:
The triangle showing is your phone flashing a new update to a low level device, NEVER interrupt that process, I believe it's not even possible to skip it.
XZDualRecovery not working is related to a 2.1 incompatible method of reading the keypress. You could have noticed it was already superseded by a BETA release fixing that. It's even included in this Rom release
Your Gmail app crashing can be fixed by clearing its cache from the apps menu. If that doesn't help you can remove it using a root app like titanium backup. Then install it again from play store.
I actually started everything over by flashing a clean 434 FTF. Mine was a mess, I had played a lot with the system files. So this second try, the phone reboots properly, no triangle, no app crash but the Recovery still doesn't work and I also tried with the latest 2.2 BETA (same result). I also re-installed Root Explorer and when going from R/W to R/O, it reboots the phone, so I switched from SuperUser to SuperSU but same result.
Any suggestions?
Click to expand...
Click to collapse

Device not detected

Hello everybody,
Here my problem :
I tried to install a custom rom, I failed. Now, my smartphone stay on the Asus logo screen. I tried to follow this - http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 - to fix the problem, but when I connect phone and laptop, adb doesn't find the device.
If I continue and go in recovery mode (using TWRP), laptop can access the phone (I can see internal memory but not external).
And if I try the ADB sideload, there is no device again...
It's the first step, I don't see any other way to unbrick the phone...
Thanks in advance

http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 be lucky your phone is recognized

Hello,
Frist, thank you for your answer. I had already tried this way but nothing. Finally, I fixed the problems (detect phone and unbrick phone).
1-In TWRP, I loaded recovery.img, boot.img and droidboot.img. Reboot in recovery mod, but I had the dead droid... so I pushed on power and volume up till I have a new screen.
2-In this part, I did a Wipe/Factory reset (useless I think), reboot in recovery mode (still dead droid). This time I selected the line "update with adb" (with an ASUS firmware). Then I had a message who told me update adb sideload. I did it and it installed the firmware. The smartphone reboot correctly.
Now, I have the same problem I had yesterday. In TWRP, my external storage isn't detected...

you use stock recovery or custom recovery, if you use stock recovery external-storage won't detected

Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Edit : I guess custom, TWRP. It's why I don't understand why it doesn't allow me to mount SD card or doesn't detect this same SD Card.

Mara Udé said:
Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Click to expand...
Click to collapse
i use twrp 3.0 too, but external sd detected. no need to put on external storage, you can flash Cm 13 through internal storage
if you want to install custom rom it's better if you make a backup first, so if happen you failed when installing new rom or maybe you don't like it (new rom) you can go back to stock rom through TWRP restore

Ok, failed again...

Try a different rom or redownload the rom it might have been a bad download.
The error message says there is no updater script in the zip meaning it can't install anything as the updater script tells what directories to install the files if I seen it correctly that is.
Sent from my ASUS_Z00AD using Tapatalk

Mara Udé said:
Ok, failed again...
Click to expand...
Click to collapse
maybe the CM 13 zip file you have download corrupted, try to re-download and re-flash it again. if still failed try another rom
( i'm using AICP Rom "based on CM 13 too") try it, it's awesome Rom ---> do clean install wipe all except internal storage and external storage
http://forum.xda-developers.com/zenfone2/development/rom-c-p-t3285951/post64645756#post64645756
http://opengapps.org/ ( select x86-6.0-nano )

Hi,
Sorry for this late answer. As I failed to install those roms (CM13, Bliss), I'm going to stop here and wait for the Marsmallow update. But I'm happy my phone isn't brik anymore.
Thank you all.

Carliv Touch Recovery v6.5

This is a CWM based recovery built by my Master Shifu Carliv for our Honor 5x.... :highfive: :good:
Features
EXT4 and F2FS support
Full touch menu
All cwm functionalities are up and working => adb, sideload, backup, restore, install, usb-otg support
Advanced backup and restore menu for backing or restoring only a specific partition with multizip flashing function.
At Carliv menu there is now a new section for flashing boot and recovery images.
Aroma File Manager, Rainbow mode
Added support for dencrypting and mounting data partition using the builtin minivold from cyanogenmod with vdc commands
To install it either use Rashr or Flashify or below command
Code:
adb reboot bootloader
fastboot flash recovery [COLOR="Blue"]recovery-ctr-65-kiwi.img[/COLOR]
XDA:DevDB Information
[RECOVERY] Carliv Touch Recovery v6.5, Tool/Utility for the Honor 5X
Contributors
yuweng, carliv
Source Code: https://github.com/carliv/carliv_touch_recovery_new/tree/cm-13
Version Information
Status: Stable
Current Stable Version: v6.5
Stable Release Date: 2016-07-05
Created 2016-07-06
Last Updated 2016-07-08

BUG Reporting
There is absolutely no way that a DEV will know what is happening on your device, that's why it is very important to provide logs !
Code:
adb pull /cache/recovery/last_log
OR
Repeat the steps to reproduce the bug then at CTR...
Code:
Main Menu => Advanced Menu => Report Error => look for it at Internal SdCard => clockworkmod folder => backup folder => recovery.log => attach it to your post when reporting bug
How to Report Bugs Effectively
Aroma File Manager
Aroma File Manager version 1.90 , 1.91 & 2.00 works on CTR... :good:
Code:
Create a new folder => Internal SdCard => clockworkmod => [COLOR="Blue"].aroma[/COLOR] => rename [aromafm-1.90.zip] [aromafm-1.91.zip] [aromafm-2.00-b6.zip] [aromafm-2.00b7.zip] to [COLOR="Blue"]aromafm.zip[/COLOR]
To use it...
Code:
Main Menu => Carliv Menu => Aroma File Manager

Ctr , I never thought we will get it . even I dint assumed getting a cwm pure port for our phone .
Thanks a big.
Edit: @yuweng , bro recovery isn't showing external sdcard to flash zips . there is only one single option that is to flash internal memory which showing that as sdcard and can't backup to external sdcard too , only to backup into internal memory.
A bit lagging but except the above I found no other bugs
[emoji4] [emoji108]
Sent from my KIW-L22 using XDA-Developers mobile app

gopinaidu77 said:
Ctr , I never thought we will get it . even I dint assumed getting a cwm pure port for our phone .
Thanks a big.
Edit: @yuweng , bro recovery isn't showing external sdcard to flash zips . there is only one single option that is to flash internal memory which showing that as sdcard and can't backup to external sdcard too , only to backup into internal memory.
A bit lagging but except the above I found no other bugs
[emoji4] [emoji108]
Sent from my KIW-L22 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you don't use adopted storage download the recovery-ctr-65-kiwi-nas.img and you will see the external sdcard too. For adopted storage I don't have yet a solution and therefore only the internal memory and usb-otg is supported (recovery-ctr-65-kiwi.img - this is for adopted storage).
I rebuilt the recovery and should be no more lag, or at least should be better than before, and for my friend yuweng I hide the text from screen when using aroma (the progress icons and virtual keys are still there because I can't hide those without breacking the UI).

carliv said:
If you don't use adopted storage download the recovery-ctr-65-kiwi-nas.img and you will see the external sdcard too. For adopted storage I don't have yet a solution and therefore only the internal memory and usb-otg is supported (recovery-ctr-65-kiwi.img - this is for adopted storage).
I rebuilt the recovery and should be no more lag, or at least should be better than before, and for my friend yuweng I hide the text from screen when using aroma (the progress icons and virtual keys are still there because I can't hide those without breacking the UI).
Click to expand...
Click to collapse
after so many years i saw a new recovery apart from TWRP. Thank you for this wonderful piece of code....

Great work on bringing this recovery to our device! More choice is always better. Still hoping for a better solution for adopted storage. It seems I have to do a full wipe and lose internal and external every time I want to use a different ROM.

tamcdonald said:
Great work on bringing this recovery to our device! More choice is always better. Still hoping for a better solution for adopted storage. It seems I have to do a full wipe and lose internal and external every time I want to use a different ROM.
Click to expand...
Click to collapse
No it won't touch your external SD . a full format is data+data/media/0/ ..
Your SD card has a different mount point and u don't need to worry about it . untill u had an option it won't go through it .

@carliv I first saw your work on the Lenovo Tab 2. It was a god send and the only thing available when i got the Tablet.
Thanks for this release

What advantages does this have over TWRP?

Added in Index thread

narangkunal said:
What advantages does this have over TWRP?
Click to expand...
Click to collapse
This is not in a competition with twrp. I created this recovery as an alternative for those that liked cwm and wanted to use it post kitkat. Also, this one works even without touch and that could be in handy for those devices without touch in recovery (twrp can't be used without touch).

carliv said:
This is not in a competition with twrp. I created this recovery as an alternative for those that liked cwm and wanted to use it post kitkat. Also, this one works even without touch and that could be in handy for those devices without touch in recovery (twrp can't be used without touch).
Click to expand...
Click to collapse
Can we get a pure cwm recovery ?
Or philz recovery ?
Just in case if possible ?

gopinaidu77 said:
Can we get a pure cwm recovery ?
Or philz recovery ?
Just in case if possible ?
Click to expand...
Click to collapse
Sorry but that's not possible. Too much work to do and I worked alone for this for last three - four months in my free time. I won't start it from begining again. There is not much support for this.

Im stuck in the recovery. If i reboot it boots back into the recovery i had to refresh. Im on Emui 4

Demian3112 said:
Im stuck in the recovery. If i reboot it boots back into the recovery i had to refresh. Im on Emui 4
Click to expand...
Click to collapse
You have to give more details. What did you do in recovery before the issue? Did you tried to wipe cache and reboot the recovery then reboot to android or reboot to bootloader and reboot to android with fastboot command [fastboot reboot], and so on...
I don't have this phone but maybe some of the people that have it will help you. Just learn to report a problem and don't be laconic.

carliv said:
You have to give more details. What did you do in recovery before the issue? Did you tried to wipe cache and reboot the recovery then reboot to android or reboot to bootloader and reboot to android with fastboot command [fastboot reboot], and so on...
I don't have this phone but maybe some of the people that have it will help you. Just learn to report a problem and don't be laconic.
Click to expand...
Click to collapse
I flashed it twice.. Rebooting device with power button brings me in the recovery. Fastboot reboot also. i cant boot my device without getting into the recovery. It looks great but i cant boot ;/

Demian3112 said:
I flashed it twice.. Rebooting device with power button brings me in the recovery. Fastboot reboot also. i cant boot my device without getting into the recovery. It looks great but i cant boot ;/
Click to expand...
Click to collapse
Are you sure you didn't flash it on boot partition? If you say you flashed it twice... Try to flash again your boot image.

carliv said:
Are you sure you didn't flash it on boot partition? If you say you flashed it twice... Try to flash again your boot image.
Click to expand...
Click to collapse
I flashed it but i couldnt boot without ging into the recovery. So flashed default twrp and everything is fine. Flashed it again same issue. If i reboot in the recovery it reboots again in the recovery.. I dont know what it is.

Demian3112 said:
I flashed it twice.. Rebooting device with power button brings me in the recovery. Fastboot reboot also. i cant boot my device without getting into the recovery. It looks great but i cant boot ;/
Click to expand...
Click to collapse
I had same problem when I flashed it just boot phone into bootloader then load twrp via adb commands then flash twrp and that should get u where u can flash or restore a rom
Fast boot boot kiwi_twrp.img
The name of ur twrp file may differ from mine
Sent from my KIW-L24 using XDA-Developers mobile app

@carliv could you please tell me that if I'm rooting my Honor 5X for the first time, could I use your recovery instead of TWRP, or I would have to have to flash it sometime later?
And I cannot see a download link in the OP. Help me!

[SOLVED] TWRP doesn’t let browse /sdcard files

I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me

Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps

Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?

So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.

Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads

tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?

Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .

AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.

Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:

Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.

AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM

[9 SE] OTA update encrypted storage

Hi,
Everytime I try to OTA update de weekly rom, I get the message that says that my memory is encrypted and directs me to recovery.
In recovery when I select the ROM, it returns ERROR 7, I know that it is related with 2 command lines in the updater script.
My question is, how can I fix this problems so I can normally OTA update?
Xiaomi MI 9 SE
TWRP 3.5.0_9-0
xiaomi.eu weekly (it happens in all versions)
Thanks

Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info

flairepathos.info said:
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
Click to expand...
Click to collapse
You're right, I think this is a generic problem, that's why I've not specified the model.

vmlc said:
You're right, I think this is a generic problem, that's why I've not specified the model.
Click to expand...
Click to collapse
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery

flairepathos.info said:
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
Click to expand...
Click to collapse
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards

vmlc said:
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
Click to expand...
Click to collapse
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible

flairepathos.info said:
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
Click to expand...
Click to collapse
So this is not fixable, keep TWRP and have OTA update?

vmlc said:
So this is not fixable, keep TWRP and have OTA update?
Click to expand...
Click to collapse
Yes but now that you mention if you could edit the twrp recovery_id to match that of the stock recovery ,it might work because the system/ ota file calls for a specific recovery_id