Please be aware I am not the project developer. I am posting this build for feedback and debug purpose
OrangeFox is a modded recovery based on TWRP 3.3.x with a customizable UI.
More info at https://orangefox.tech/
This build is based on @redispade twrp 3.3.1 device tree and its code can be found on github:
The recovery is supporting Android Pie and Q builds (both AOSP and MIUI based ROMs).
Decryption is working.
How to install:
1. Download Orange Fox 0509 build:
2. Reboot to Recovery
3. (Optional) take a full backup (data+media) and export it outside your device.
4. Flash the OrangeFox file as a recovery image (install/install image/select file and swipe to flash to recovery partition).
5. Reboot to recovery from reboot menu in TWRP.
6. Profit
If you are using a MIUI-based ROM that support OTA, follow this guide on OrangeFox website to set up OTA on your device.
If you flash OrangeFox and then, for any reason, you cannot access to recovery partition anymore, reboot your device to fastboot, connect it to a PC and flash any TWRP recovery using fastboot.
Once you flashed TWRP, reboot to recovery using button combo Power+VolumeUp
Reserved
Which version redispade recovery?
The latest which support android 10?
fatjoez said:
Which version redispade recovery?
The latest which support android 10?
Click to expand...
Click to collapse
The one posted in the first post won't work, op will be edited soon.
Faust build is based on latest twrp 3.3.11 so I assume it should work on Android 10.
As usual, keep a full backup of your device handy before trying.
I installed faust93 23-10 build (downloaded from his web page). Tested wipe, install (Derpfest) and restore (full backup). All good and running. :good:
elpaablo said:
I installed faust93 23-10 build (downloaded from his web page). Tested wipe, install (Derpfest) and restore (full backup). All good and running. :good:
Click to expand...
Click to collapse
Did you had to reboot to recovery after flashing ROM before flashing other zips, if any?
Flounderist said:
Did you had to reboot to recovery after flashing ROM before flashing other zips, if any?
Click to expand...
Click to collapse
I always do that to avoid errors. The only issue I had was with data restore, but that's usual behavior, I always have to reboot to system before restore data.
elpaablo said:
I always do that to avoid errors. The only issue I had was with data restore, but that's usual behavior, I always have to reboot to system before restore data.
Click to expand...
Click to collapse
Did you performed a clean flash, is it?
I got this message on a log, but I'm not sure it is a bug because I didn't try to mount any partition yesterday.
I'm using the OF build posted in OP (not the faust93 one):
I: Data backup size is 8239MB, free: 15364MB.
I:Unable to mount '/storage'
I:Actual block device: '/data/media/0', current file system: 'ext4'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
Flounderist said:
Did you performed a clean flash, is it?
I got this message on a log, but I'm not sure it is a bug because I didn't try to mount any partition yesterday.
I'm using the OF build posted in OP (not the faust93 one):
I: Data backup size is 8239MB, free: 15364MB.
I:Unable to mount '/storage'
I:Actual block device: '/data/media/0', current file system: 'ext4'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
Click to expand...
Click to collapse
I installed OF from redispade twrp, rebooted to recovery, wiped system and data (I already had the right vendor, so nothing to do here) and installed Derpfest. Rebooted to system, to see if installation had succeded, then passed my backup to orange backup folder and made a full restore. I only had issues with restoring data, probably because I made a backup with pin protection, which is not the best choice. So I had to complete google initial setup and redefine a pin protection so that I could be able to restore data from recovery.
elpaablo said:
I only had issues with restoring data, probably because I made a backup with pin protection, which is not the best choice.
Click to expand...
Click to collapse
Yep, disabling any FP or pin is recommended when clean flashing.
MIUI OTA working? Now can't testing.
X_SaG_X said:
MIUI OTA working? Now can't testing.
Click to expand...
Click to collapse
I am running an AOSP ROM, so I can't tell you.
The same has been mentioned in the Mi9 SE (Devs) Telegram Group.
p.s. I found the time to test in depth the build posted in the first post and everything is working (themes, backup, decryption, ADB, MTP, OTG and so on).
New Build added
I added new build download link in OP.
I also added some additional information on how to get out of troubles, if any.
The 102619 build should fix Magiskboot and MIUI OTA should work.
Any MIUI user please test and report with logs.
OTA need testing
It has been reported by a MIUI 11 user that OTA is not working, but no logs were provided.
If someone is willing to help, please try OTA and grab some recovery logs if it fail.
I edited OP as well with a warning.
103019 has working MIUI OTA :good:
Updated OP with download link.
Please report any issue with logs, if any.
I found a bug. System partition is mounting in read-only mode and I can't change it to full access.
Kirhe said:
I found a bug. System partition is mounting in read-only mode and I can't change it to full access.
Click to expand...
Click to collapse
Are you able to flash any .zip file to system?
Are you using MIUI, AOSP based ROM or GSI?
Flash zip to system doesn't works. I'm using MIUI. Stock TWRP works well
Kirhe said:
Flash zip to system doesn't works. I'm using MIUI. Stock TWRP works well
Click to expand...
Click to collapse
Could you provide for recovery log after attempting a .zip flashing?
Flounderist said:
Could you provide for recovery log after attempting a .zip flashing?
Click to expand...
Click to collapse
Have you any idea how to fix a bug?
Related
Requeriments:
Locked bootloader (Unlocked bootloader can flash a custom kernel with this included).
You must be root, if you not be root do this --> http://forum.xda-developers.com/showthread.php?t=2783885 NEW
You need enable USB Debuging Options (go settings->about phone->compilation number and hit seven times, then go settings->developer options and Enable USB debugging..
Installation:
1.) down CWM_SP_#.#.#.zip file.
2.) unzip it on your desktop.
3.) go to the CWM_SP_#.#.# folder
4.) run the install.bat file in windows (use others for linux or mac)
5.) select option number 1 to install.
6.) stay tuned on the phone as it calls super user permissions.
7.) Read the directions to see that everything went well.
8.) If all went well you press a key to continue and after press 3 for reboot phone or 4 to finish.
Click to expand...
Click to collapse
If something goes wrong, reboot your computer and phone and try again.
For new installs in recovery, i add the flashable zip in downloads section.
Operation:
Turning on the phone will see four lights advancing (GREEN-WHITE-RED/BLUE) when the blue light show press:
Volume up -> Philz
Volume Down -> TWRP
Camera button -> CWM Touch
Click to expand...
Click to collapse
If you have a problem you can put your questions once they have exhausted all options and read the comments of others.
In CWM Touch the backups are stored in /data/media/clockworkmod or /storage/removable/sdcard1/clockworkmod
If you only need ClockworkMod (without philz and TWRP ) you can use a MOD made by @Dark Passenger (any doubt about this release or updates, please ask him), just go to this post <<---- clic here (credits for MOD to @Dark Passenger)
Bugs:
For now, restoring backups in 4.3 with CWM touch have troubles. Fixed!
The date in recoverys are wrong, please rename the backups. Fixed!
Click to expand...
Click to collapse
Changes:
2014.07.09 ver. 4.4.1
- Improvements in product number and version number detection.
2014.07.04 ver. 4.4
- added support to CM 11 KitKat by bagyusz.
- all version are supported (4.1, 4.3 ) in same installer.
2014.06.27 ver. 4.3.8
- added sd-ext suport to backup
second partition of sdcard to all
recoverys(if exists). Needed if you
use link2sd or similar.
- CWM is default recovery (when you
do "reboot in recovery" system enter
in CWM automatically. The buttons keep
same function.
2014.06.16 ver. 4.3.7
- added linux and mac installers
- fix autocreate init.d directory
if not exist.
2014.06.09 ver. 4.3.6
- reverted enhanced ramdisk.
- fixed some bugs.
2014.05.21 ver. 4.3.5
- Updated CWM Touch to 6.0.4.7
- Updated TWRP to 2.7.0.0
- Added enhanced ramdisk.
- Added init.d support.
- Added compression to ramdisk's.
- Fixed "reboot in recovery" feature.
2014.05.16 ver. 4.3.4
- Loaded stock exfat driver.
- Added improvements.
- Fixed wipedata permissions.
2014.05.15 ver. 4.3.3
- Philz updated to 6.41.6.
- Disabled Glove mode in TWRP.
- Fixed DateTime in recoverys.
- Changed script to wipedata.
- some bugs fixed.
- support only for 4.3 Roms. (Sorry )
2014.04.04 ver. 4.3.2
- philz updated to 6.25.0.0
- CWM Touch updated.
- some bugs fixed.
2014.03.18 ver. 4.3.1
- added ZIP recovery flashable.
2014.03.11 ver. 4.3.0
- added Philz touch (thanks to @Phil3759).
- Some fixes to TWRP
2014.02.17 initial version
- added external sdcard for backup / install
- Fixed problems mounting/unmounting system partition
Click to expand...
Click to collapse
Credits:
@Phil3759 for PhilZ touch.
@FXP for CWM
@teamwin for TWRP
@DooMLoRD for ramdisk´s and scripts
@bagyusz for hijack ramdisk.
@KeiranFTW for hijack ramdisk.
Cheers and enjoy :good:
Download:
Installer:
CWM_SP_4.4.1.zip - 11.81 MB NEW!
Flashable:
recoveries_SP_4.4.1_signed.zip - 10.62 MB NEW!
Click to expand...
Click to collapse
anyone tried this already?
Im gonna try right now... Risking flashing on a Sunday... God protect me
Works.... Tested CWM Touch.
Nice Job Man, now we dont have to reflash 4.1.2 and root and flash 4.3 again n again n again n again
Life saver.
---------- Post added at 10:53 AM ---------- Previous post was at 10:25 AM ----------
Tested All recoveries:
1. CWM works fine
2. TWRP fine
3. CWM-touch (some difficulty in navigation, but works ok)
is there any way .. with out installing purerome.. .for rooting ?
i dont wanna change my stock rom....
I tested it, but only TWRP make backup. CWM says "can't mount system". CWM touch says "backup completed", but there is no backup files on any of storages.I tested two others CWM mods and they also says "can't mount system".
Ohh, I found CWM Touch backup files. After I read log file, I saw this row -> "I:using /data/media for /sdcard/0/clockworkmod". Backup folder is in /data/media/clockworkmod/backup/..
There is something wrong with filesystem table. I saw several lines that say Unable to get recovery.fstab info for: /datadata, /emmc, /sdcard, /ed-ext and /external_sd.
yep. this works. haven't tried backing up yet though. thanks.
thanks, its work.... but, why i cant mount system, its always "mount system Eror"....????
can any body help...
Can cwm mount sdcard0/1 and system?
Sent from my C5303 using xda premium
CWM shows "error in mounting system" when I try to mount system. As a result, can't take nandroid backup.
CWM Touch shows "error in unmounting system" when I try to unmount system. Though it can take backup, when I try restore, it shows error in unmounting system.
TWRP though not showing error, and seeming to backup correctly, when I try restore, it shows error in unmounting system.
In other words,
not working for me.
I'm on CE 4.3 stock, rooted, LB.
Deepam7325 said:
CWM shows "error in mounting system" when I try to mount system. As a result, can't take nandroid backup.
CWM Touch shows "error in unmounting system" when I try to unmount system. Though it can take backup, when I try restore, it shows error in unmounting system.
TWRP though not showing error, and seeming to backup correctly, when I try restore, it shows error in unmounting system.
In other words,
not working for me.
Click to expand...
Click to collapse
Same for me, i use existenz v2
Sent from my C5303 using xda premium
kuriboo said:
Same for me, i use existenz v2
Sent from my C5303 using xda premium
Click to expand...
Click to collapse
For 4.1.2 backups use CWM or TWRP, for 4.3 backups use CWM Touch.
Remember, if you restore an 4.1.2 backup you need change kernel to 4.1.2.
Enviado desde mi C5303 mediante Tapatalk
dssmex said:
For 4.1.2 backups use CWM or TWRP, for 4.3 backups use CWM Touch.
Remember, if you restore an 4.1.2 backup you need change kernel to 4.1.2.
Enviado desde mi C5303 mediante Tapatalk
Click to expand...
Click to collapse
I tried to restore 4.3 backup in cwm touch & twrp. it showed error "unable to unmount system" after md5 verification.
I tried to restore 4.3 backup in cwm. It verified md5 and erased boot image. after that it showed error "error, can't mount system" . As a result, I got soft brick on booting.
Its as if, CWM has its "mount system" freezed. CWM & TWRP have their "unmount system" freezed
Same for me, can't mount /system, so it's basicaly unusable ;/
Deepam7325 said:
I tried to restore 4.3 backup in cwm touch & twrp. it showed error "unable to unmount system" after md5 verification.
I tried to restore 4.3 backup in cwm. It verified md5 and erased boot image. after that it showed error "error, can't mount system" . As a result, I got soft brick on booting.
Its as if, CWM has its "mount system" freezed. CWM & TWRP have their "unmount system" freezed
Click to expand...
Click to collapse
in cwm touch you need mount system and data first, if you have trouble try use advanced restore.
i test full backup and all are ok,
---update --
Restoring backup in 4.3 don´t work, i´m working for fix that.
dssmex said:
in cwm touch you need mount system and data first, if you have trouble try use advanced restore.
i test full backup and all are ok,
---update --
Restoring backup in 4.3 don´t work, i´m working for fix that.
Click to expand...
Click to collapse
Pray for that
I decide UBL again after Relock
Sent from my C5303 using xda premium
flashed the rom n its working great but now if i want to enter cwm m nt able to plz help
saurabh808 said:
flashed the rom n its working great but now if i want to enter cwm m nt able to plz help
Click to expand...
Click to collapse
once you flash the custom rom yo need flash root too, once reboot need install CWM again because the recovery image are in system partition.
@ OP
Suppose i am on a 4.3 ROM, and i want to flash a MOD or add-on, which recovery will be compatible with 4.3?
I am on LB, so if the recovery formats system, i have a very long process to get back to where i was.
Currently no compatible custom recovery for LB, but there are people working on it!
We all wait!
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
alexounet2 said:
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
Click to expand...
Click to collapse
Hey i had this issue and finally pinned it down to the TWRP I was using. It turns Official TWRP has this issue. This can easily be resolved if u flash Squid's TWRP
Download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
That was the problem apparently. Thank you!
Thank you! I was having this problem as well and that fixed it.
Thanks very much for your help!!!
I was scared of loosing my phone...
Thanks.
I have a US Cellular XT1526 and was unable to install GApps on CM13 without this. CM13 installed fine, and GApps looked like it installed, but on reboot nothing was there; GApps failed to install. Using Squid's TWRP fixed it; thanks!
ayush rao said:
hey i had this issue and finally pinned it down to the twrp i was using. It turns official twrp has this issue. This can easily be resolved if u flash squid's twrp
download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Click to expand...
Click to collapse
thank you so much :d
thank you buddy.....
my mother is using Motorola E 2nd gen LTE and i flashed it with cyanogenmod 13 used officialTWRP recovery... and i faced the same problem. thank you very much for your answer and also the other guy for asking the question.
Should I select boot or recovery as partition when flashing this img
cannot restore system mounted read only
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Djoul33 said:
Hi
I have a problem with my Mi5s plus.
I have updated my rom.
I can boot with my custom rom I just installed. It is ok. I can browse the directories with the file manager. I can use the stock browser, SMS...ok
But when I want to install GAPPS (That I downloaded before)(I know it's no longer called that) with TWRP, I no longer see the installation file, the ZIP. The directories are empty with TWRP but accessible and with files with the Android file manager.
So I can't install applications without open apps.
Of course, when I want, by example, to delete cache I have theses messages : unable to mount /data (invalid argument), error 8 etc.
Help me?
I hope to be able to recover the data so that when I reinstall my applications. I have the data.
Thank you again.
Click to expand...
Click to collapse
In TWRP, go to mount and see if data is mounted.
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Djoul33 said:
No, it is not mounted in TWRP (But, in Android, it is OK, il see my datas)
But, I can just check :
DSP
System
Cache
Cust
Persist
But I am not able to check
Data
USB OTG.
it is locked.
Click to expand...
Click to collapse
I have flashed things that did not properly unmount a partition afterwards so I could not mount it in twrp. Try flashing something that mounts data, if not mounted, then unmounts data properly.
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
2016...
Djoul33 said:
Maybe my TWRP is deprecated ?
I have flashed a ROM 8.x then, my TWRP is old : 3.0.2.x By XM maybe ?
Click to expand...
Click to collapse
Try that first.
Hi,
My TWRP was too old, deprecated. It is OK now.
Thanks.
This is a modified unofficial version of Migrate to work on devices with system as root partition ,as I have the permission from the Author of the app i'm posting here . Since new devices which shipped with pie have system as root, migrate backup will fail to flash as it can't mount /system like earlier.
The backups created by this version will able to flash and restore without any issue. This will depend on the recovery, as twrp of these devices should mount system under /system_root , some recoveries mount system under / so it may not work on that devices.
Tested on Violet using Peter's wrapped key twrp.
download : drive.google.com/open?id=1HUvqwmAH-qKTd0YMAg-Vc_9e8jeAPZDg
1.Uninstall previous versions and Install the APK
2.Make Backups and restore as normal
Will this also work on Note 7 (Lavender) ?
@anoop1507 thanks for sharing.
Can i backup my data on galaxy s8 with this version of app and restore it on redmi note 8?
does it still need the helper after reboot ?
GooglecrDroid ROM 14-01-2020
FULL last openG(OOGLE)APPS included! (v.12-01-2020)
Last stable crDroid 6.2 based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe data, cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
I don't use this ROM, help each other who use it. Thnx.
DOWNLOAD SF
DOWNLOAD AF
Updates, previous and all ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage 17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 14-01-2020 V0 version
Last Updated 14-01-2020
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
I'd like to get feedback on whether VOLTE is working? Thanks.
wow thanks i'm gonna test now
---------- Post added at 07:26 AM ---------- Previous post was at 07:11 AM ----------
can you share device tree, kernel, vendor for android 10??
szanalmas said:
GoogleDroid ROM 2019-12-27
FULL open GOOGLE APPS included!
Last stable crDroid based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
DOWNLOAD ROM
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140
ROM info: Q10 system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
Created 2019-12-27 V0 version
Last Updated 2019-12-27
Click to expand...
Click to collapse
Thanks for you great rom again, @szanalmas :good:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
I cant install magisk
please make a original TWRP 3.3.1 like 3.2.1
GonzaloxCOM said:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
Click to expand...
Click to collapse
Unfortunately, I can't test VOLTE, Hungarian Telekom is filtering phone model the use of VOLTE...
DT2W works for me, no need to fix it. (I built it into /vendor.)
Your welcome!
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Use Canary: LINK
(But i haven't tested Magisk yet.)
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
cpglbitm said:
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
Click to expand...
Click to collapse
I can't install this version either. It always ends with error 1.
Endys111 said:
I can't install this version either. It always ends with error 1.
Click to expand...
Click to collapse
Use orangefox recovery.
cpglbitm said:
Use orangefox recovery.
Click to expand...
Click to collapse
Thanks, already installed.
Can I flash this rom in Redmi Y1
arvind787 said:
Can I flash this rom in Redmi Y1
Click to expand...
Click to collapse
I do not think so.
Y1 Q10 vendor image and Y1 kernel would be nice.
But I don't know for sure.
If the kernel starts, it is possible. If the LCD and touchscreen match, then the cameras are in question.
But I know that the kernel does not have msm8940 support and Y1 uses 8940 as far as I know.
So you probably won't boot the kernel.