TWRP Recovery 3.2.1-0 For Cubot X18 Plus
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Welcome all Cubot X18 Plus users, This is Lastest TWRP Recovery For your device By TWRPBuilder Team
CHANGELOG for 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
DownloadsCubot X18 Plus Recovery img
Sources:
Code:
[CENTER][URL="https://github.com/TwrpBuilder/android_device_cubot_cubot_x18"][COLOR="bule"]Device tree[/COLOR][/URL]
[URL="https://github.com/TeamWin/Team-Win-Recovery-Project"][COLOR="bule"]TeamWin Github
[/COLOR][/URL][/CENTER]
How to install:
you must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
Don't Forget to Hit Thanks :good:
Thank you kindly for the work to get TWRP working on the X18 Plus! Are new versions of TWRP automatically built now along with all the other versions supported. How has the feedback been on the release?
James.Harking said:
Thank you kindly for the work to get TWRP working on the X18 Plus! Are new versions of TWRP automatically built now along with all the other versions supported. How has the feedback been on the release?
Click to expand...
Click to collapse
Yes, a new release is auto-built every month.
Tested by @iNFeRNuSDaRK and confirmed it's working. Except for encryption support.
Encryprion
yshalsager said:
Yes, a new release is auto-built every month.
Tested by @iNFeRNuSDaRK and confirmed it's working. Except for encryption support.
Click to expand...
Click to collapse
My phone is encyipted. How to get it off ??? Thanks
Hi all,
I just wanted to post an interesting message from the X18 plus 'forum' regarding the functionality of the TWRP.
Cheers guys!
Quote:
Originally Posted by HûnSt°rJonnyt
yes, got it successfully running with SP Flash Tool, i couldn't flash it with fastboot.
twrp runs and i could install magisk.
Badly it seems there are some x18 Plus modifications missing in the recovery img
when i want to update the system i get things like
E3004: This package is for CUBOT_X18_Plus devices this is a cubot_x18.
even if try to modify the updater-script to ignore these checks, i fail at least at updating the system partitions, maybe some problems with encryption or file system layouts modifications for x18 plus are missing
ok i tried to recompile the recovery and tried to find the right parameters but this gets much more confusing, when i try to update to the latest official rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HûnSt°rJonnyt said:
ok i tried to recompile the recovery and tried to find the right parameters but this gets much more confusing, when i try to update to the latest official rom
Click to expand...
Click to collapse
Test the new build (will be uploaded here with today's date in some minutes) and check
[Build Progress]
yshalsager said:
Test the new build (will be uploaded here with today's date in some minutes) and check
[Build Progress]
Click to expand...
Click to collapse
same as with the old build
E3004: This package is for CUBOT_X18_Plus devices this is a cubot_x18.
Edit: ok i see, i think the build wasn't successfull so there where no changes in the .img
---------- Post added at 04:47 PM ---------- Previous post was at 03:51 PM ----------
so i tried more stuff, when reverting back to original recovery i get
E3005: "EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot:10138528:fcf3cc2d6ac345fa071fb12e409df7234de130cb:10156960:84a65157b0daa69dd9559f7d7b109ad2909e225b" has unexpected contents.
so i think maybe it's an issue with original update and unlocked bootloader, not sure how to understand this. Maybe TWRP is fine and this issue don't come when using custom rom
HûnSt°rJonnyt said:
same as with the old build
E3004: This package is for CUBOT_X18_Plus devices this is a cubot_x18.
Edit: ok i see, i think the build wasn't successfull so there where no changes in the .img
---------- Post added at 04:47 PM ---------- Previous post was at 03:51 PM ----------
so i tried more stuff, when reverting back to original recovery i get
E3005: "EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot:10138528:fcf3cc2d6ac345fa071fb12e409df7234de130cb:10156960:84a65157b0daa69dd9559f7d7b109ad2909e225b" has unexpected contents.
so i think maybe it's an issue with original update and unlocked bootloader, not sure how to understand this. Maybe TWRP is fine and this issue don't come when using custom rom
Click to expand...
Click to collapse
Well, build errored that's why it's the same.
This error you posted means you have modified boot partition, are you trying to flash an OTA?
New build is out!
https://github.com/TwrpBuilder/andr...a9fb23dad3e/TWRP-3.2.1-cubot_x18-20180629.img
Good morning everybody, I tried the new build but i have again the same error "Failed to mount '/data' (Invalid argument).
Any new?
yshalsager said:
Well, build errored that's why it's the same.
This error you posted means you have modified boot partition, are you trying to flash an OTA?
Click to expand...
Click to collapse
yes it's ota.
i will try new release soon
HûnSt°rJonnyt said:
yes it's ota.
i will try new release soon
Click to expand...
Click to collapse
You can't flash ota if you made modifications to boot/system
So first flash full rom, flash ota, backup boot, flash magisk or whatever
when you get another ota, restore boot then flash, and so
I ported Philz recovery to x18 plus, got it working, everything works fine except it can't mount /data
So just asking asking between TWRP and now Philz recovery being ported is the X18 plus are we in a position where there is a working recovery that can install a GSI so we could use the Project Trebble ROMS? If not then what is the impediment stopping this? I am happy to try and contact Cubot directly if it helps out?
@yshalsager : I saw that you wrote in the other thread that you need the /vendor/etc/fstab.* files. Do you still need these? If I can get some instructions on how to provide these to you I happily will do.
Thanks all for continued work on this phone.
James.Harking said:
So just asking asking between TWRP and now Philz recovery being ported is the X18 plus are we in a position where there is a working recovery that can install a GSI so we could use the Project Trebble ROMS? If not then what is the impediment stopping this? I am happy to try and contact Cubot directly if it helps out?
@yshalsager : I saw that you wrote in the other thread that you need the /vendor/etc/fstab.* files. Do you still need these? If I can get some instructions on how to provide these to you I happily will do.
Thanks all for continued work on this phone.
Click to expand...
Click to collapse
The recoveries are working alright, its just an issue with Oreo's force encryption of the data partition (the system automatically encrypts the data partition on 1st boot) if you do a full wipe of /data the encryption is cleared, you'll see TWRP can access it but after first boot its back to encrypted.
As for GSI I guess you can install (haven't had time to test thought), you may need to do a full wipe of /data before you boot the new system.
I just tested out the official RR GSI from https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299 on x18_plus everything working okay except MTP, you have to disable adb. And network when using dual SIM is not very stable
James.Harking said:
So just asking asking between TWRP and now Philz recovery being ported is the X18 plus are we in a position where there is a working recovery that can install a GSI so we could use the Project Trebble ROMS? If not then what is the impediment stopping this? I am happy to try and contact Cubot directly if it helps out?
@yshalsager : I saw that you wrote in the other thread that you need the /vendor/etc/fstab.* files. Do you still need these? If I can get some instructions on how to provide these to you I happily will do.
Thanks all for continued work on this phone.
Click to expand...
Click to collapse
Give this a try and check if force encryption disabled
https://forum.xda-developers.com/showpost.php?p=77091359&postcount=1
Hi @kamwash @yshalsager,
Great work guys, could I request for the lurkers on this forum that you might point people to a guide for installing your recoveries? Or conversely write a few lines here if you have a few spare minutes. I think it would help out as other tutorials are not really specific for the X18 plus and people are scarred of bricking their working phones.
Many thanks gents!
James.Harking said:
Hi @kamwash @yshalsager,
Great work guys, could I request for the lurkers on this forum that you might point people to a guide for installing your recoveries? Or conversely write a few lines here if you have a few spare minutes. I think it would help out as other tutorials are not really specific for the X18 plus and people are scarred of bricking their working phones.
Many thanks gents!
Click to expand...
Click to collapse
Install using fastboot
As I already wrote in the first post
How to install:
you must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Nothing really "new", just a dedicated thread for the updated CWM.
People will no longer need to look for it in the CM11 Thread
Installation:
Make sure you have a JB bootloader (and not ICS)
flash it with flashify from play store or via fastboot using following command:
Code:
fastboot flash recovery recovery-cwm-shreps-6.0.5.0-a510.img
Download:
recovery-cwm-shreps-6.0.5.0-a510-a511.img [2ad0a1c72dcfce5ba617b408971130a4] (LZMA Compression+LVM support enabled){based on CM11/Android 4.4.4}
recovery-cwm-shreps-6.0.4.9-a510-a511-lvm.img [781d89a6ed452255cc77a1c12187e892] (LZMA Compression+LVM support enabled){based on CM11/Android 4.4.4}
Warning !
Booting on CWM with LVM enable will format /system and remount it using LVM => /system will be 677MB free space instead of 350MB
Make a backup before flashing & booting on it !
Only ROM with LVM support will be compatible with this Recovery.
To get back to normal "/system", flash a regular CWM or TWRP recovery and format /system
Then restore a backup or flash a "normal" ROM (without LVM)
Click to expand...
Click to collapse
Download (old build):
recovery-cwm-shreps-6.0.4.9-a510-a511.img [4bb1324a9f977cb3265c4ed99918d620] (LZMA Compression enabled){based on CM11/Android 4.4.3}
recovery-cwm-shreps-6.0.4.7-a510-a511.img [870a8e341afc7b0fab7cd665d6772c57]{based on CM11/Android 4.4.2}
recovery-cwm-shreps-6.0.4.5-a510-a511.img [82ad171363dbc897dac4501729ea3209]{based on CM11/Android 4.4.1}
CWM 6.0.1.9 by NoThrills{based on CM10/Android 4.1}
Additional info:
My Github
credits to @pawitp, @NoThrills and CM Team
credits to @Elibl for LVM implementation !
just press thanks
XDA:DevDB Information
CWM Recovery for A510/A511, Tool/Utility for the Acer Iconia A700 and A510
Contributors
Shreps
Version Information
Status: Stable
Created 2014-07-01
Last Updated 2014-10-26
any advise on "remove_recovery_from_rom.zip"
Hi Shreps,
do you advise on any particular "remove_recovery_from_rom.zip", if coming from stock?
Many thanks for your work/help/answer
best regards
m
meikelrix said:
Hi Shreps,
do you advise on any particular "remove_recovery_from_rom.zip", if coming from stock?
Many thanks for your work/help/answer
best regards
m
Click to expand...
Click to collapse
Hi,
yes, it's like all other custom Recovery for A510, if you are on a stock ROM you have to remove the stock recovery by flashing the "remove_recovery_from_rom.zip" script
Shreps said:
Hi,
yes, it's like all other custom Recovery for A510, if you are on a stock ROM you have to remove the stock recovery by flashing the "remove_recovery_from_rom.zip" script
Click to expand...
Click to collapse
Hi Shreps,
thanks for the answer. I was more asking, if there's a preferred "remove_recovery_from_rom.zip" script => if there's only one script, I guess it's the one, that is in the NoThrills thread (CWM-based recovery 6.0.1.9 for the Acer Iconia TAB A510)?
Many thanks for your work and help
best regads
Shreps said:
Download:
recovery-cwm-shreps-6.0.4.7-a510-a511.img [870a8e341afc7b0fab7cd665d6772c57]
recovery-cwm-shreps-6.0.4.5-a510-a511.img [4da9d7f716aeb347336682079697960a]
Click to expand...
Click to collapse
Both downloads doesn`t work ....
Can you fix it pls ?
THX
Working fine for me
Try to use another web browser ?
Shreps said:
Working fine for me
Try to use another web browser ?
Click to expand...
Click to collapse
Very interessting,
I can download everything from your downloadpage except this 2 cwm recovery links.
If i try with "save target as..." it saves only a .htm file.
When i direct click the downloadlink - it will open the .img in the browser. !?!
My browser is latest IE11
Edit: Now downloaded with Opera but 6.0.4.7 MD5 not matching, 6.0.4.5 is ok!
Thanks for the updated recovery. The MD5 on this thread is incorrect. I downloaded the recovery a few times on different devices and each time got the same different MD5 so figured flashing it was safe. It was and I am now on the new recovery.
MD5 should now be fixed
After lots of hair-pulling, I learned that this recovery version can not flash the original Acer images, including the nothrills customized one. Maybe it is not made to work with anything pre-JellyBean?
I was trying to flash back to Acer rom in order to update the bootloader to the JB version and had no luck with this recovery. Kept getting error status 6 and 7.
After I went back to the nothrills recovery (older version), I was able to flash without any issue.
Just a heads up for anyone trying the same.
It was my first time to use Flashify, and wow, that was easy.
Came from NoThrill's 6.0.1.x CWM Recovery. On my stock rooted JB rom (on JB Bootloader too).
Thanks @Shreps!
Updated to 6.0.4.9
Changelog on Github by CM team : https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0
Added the latest version with LVM support !
Please read FP.
oh yeah the crappy recovery of the year.....
it ****s my tablet, entered in eternal loop after flash...
whats this message?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
unable to reflash the recovery adb says unauthorized.....
grrrrrrrrrrrr! !!!!!!:crying:
harmakhis said:
oh yeah the crappy recovery of the year.....
it ****s my tablet, entered in eternal loop after flash...
whats this message?
unable to reflash the recovery adb says unauthorized.....
grrrrrrrrrrrr! !!!!!!:crying:
Click to expand...
Click to collapse
You have an old update.zip on your sdcard, the recovery try to flash it.
Flashing a recovery is done via Fastboot/Bootloader, not ADB.
Did you read carefully FP ? Did you flash the correct version ?
CWM with LVM is compatible only with ROM with LVM.
yes i dit that as always adb devices for correct usb link and flash after that with fastboot
but now the recovery is on eternal loop and search update.zip i dont have any on sd card
it doesnt show the normal menu as 6.0.4.7 directy tryin' his crappy update.zip
before that tablet always on adb devices connected but now she is offline or unauthorized
Boot in fastboot with hardware key, and you will be able to boot or flash any Recovery you want
Shreps said:
Boot in fastboot with hardware key, and you will be able to boot or flash any Recovery you want
Click to expand...
Click to collapse
hmmmm yeah, and how to do that?
Don't have my tab with me, but try :
Volume- (two dots) and Poweron and then toggle the rotation switch on and off a few times
Shreps said:
Don't have my tab with me, but try :
Volume- (two dots) and Poweron and then toggle the rotation switch on and off a few times
Click to expand...
Click to collapse
tried that and reflash with lvm img but still the same bug
trin' another img
---------- Post added at 03:41 PM ---------- Previous post was at 03:34 PM ----------
hmmmm
erased the recovery still searching the update
erasing of internad sd possible?
formated internal sd no success always searching update.zip no zip anywhere
flashing the 6.0.4.7 its ok
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
I would like it to be known that I am only the OP. None of this would be possible if it were not for @bbelos! A HUGE thank you and shout out to him!
Download Links:
ROM
OpenGApps
TWRP
Root Add-on
Official LineageOS Changelog
Installation:
1 - Unlock bootloader via fastboot
2 - Flash TWRP
2.5 - Backup your device!
3 - Download Rom
4 - Place Rom and Gapps on internal or external storage
5 - Flash Rom via TWRP
Original Development Discussion Thread
Bugs:
Time reverts to 1970 when wifi is off during reboot - Fixed!
You tell us
Source Code
LineageOS
Device Tree
Vendor
Kernel
XDA: DevDB Information
LineageOS, ROM for Lenovo TB-X103F
Contributors:
bbelos
LineageOS Team
Version Information: Beta
Bootloader Unlock
Instructions for unlocking bootloader can be found here
Thank you @20tibby_gt06 for these instructions
TWRP Installation
1 - Download TWRP
2 - Reboot into boootloader mode
Code:
adb reboot bootloader
3 - Check to see if fastboot mode is working
Code:
adb fastboot devices
4 - Change working directory in terminal to your Downloads folder (or whatever folder TWRP is located)
Code:
cd Downloads
5 - Then type:
Code:
fastboot flash recovery recovery.img
Replace "recovery.img" with the name of your file (I always change mine to recovery.img for less typing in the terminal)
For reasons unknown to me, some people have reported a successful flash with this method but TWRP ends out being non-existent when rebooting to recovery. If this is the case for you try this:
1 - Follow steps 1-4 above
2 - Enter this command instead for step 5:
Code:
fastboot boot recovery.img
This will temporarily boot TWRP onto your device allowing you to flash the needed files to boot LineageOS
Reserved #2
Which Gapps works best?
Yakuman said:
Which Gapps works best?
Click to expand...
Click to collapse
I use opengapps arm 7.1 pico. The package size however is up to you
Could the OP add the following tags?
Code:
lenovo, tb-x103f, za1u0000us
The idea is to make it easy to find with information from the tablet itself. Thanks!
bornagainpenguin said:
Could the OP add the following tags?
The idea is to make it easy to find with information from the tablet itself. Thanks!
Click to expand...
Click to collapse
I tried to edit to add tags and I couldn't seem to do it. This is my first thread so I may be missing something
Edit: got it!
This is awesome. Thanks guys!
Quick question. I know own I shouldn't dirty flash but if I do will it keep the encryption in my external SD?
I use it as internal so I don't want to have to go through setting it all up again!
Will back it up anyway just in case
ownjoouk said:
This is awesome. Thanks guys!
Quick question. I know own I shouldn't dirty flash but if I do will it keep the encryption in my external SD?
I use it as internal so I don't want to have to go through setting it all up again!
Will back it up anyway just in case
Click to expand...
Click to collapse
I am unfortunately unfamiliar with encrypted storage, so you will have to tell us!
GartimusPrime said:
I am unfortunately unfamiliar with encrypted storage, so you will have to tell us!
Click to expand...
Click to collapse
Will give it a go later when I get home from work. Baptism of fire!!!!!
---------- Post added at 12:33 PM ---------- Previous post was at 12:16 PM ----------
Also another random question. I find the WiFi in the other lineage rom to be slow.
This to me isn't a deal breaker as the performance difference overall is so much better but it would be interesting to know other people thoughts and if you think it is quicker in this new ROM.
For example I tried remote play and it's a laggy mess and downloading from the play store seems to take much longer than all my other devices.
fastboot twrp install wont work
as stated i cant for the life of me get TWRP to install! CMD fastboot install says its complete but when i boot into recovery i get the standard recovery menu! A step by step guide would be helpfull! Thanks!
EsRgood4u said:
as stated i cant for the life of me get TWRP to install! CMD fastboot install says its complete but when i boot into recovery i get the standard recovery menu! A step by step guide would be helpfull! Thanks!
Click to expand...
Click to collapse
I will work on a tutorial this evening for everyone for unlocking bootloader and installing twrp. It will be in post 2
One thing for now for you to try is instead of doing fastboot flash recovery recovery.img try fastboot boot recovery.img. that will temporarily boot it allowing you to flash the ROM, Gapps and root if you choose.
GartimusPrime said:
I will work on a tutorial this evening for everyone for unlocking bootloader and installing twrp. It will be in post 2
One thing for now for you to try is instead of doing fastboot flash recovery recovery.img try fastboot boot recovery.img. that will temporarily boot it allowing you to flash the ROM, Gapps and root if you choose.
Click to expand...
Click to collapse
Thank you GartimusPrime! Ill give it a go and report back if i succeed!
Ok encrypted sd caused me no end of issues so did a full wipe.
First bug I have got is in the camera. Keeps asking for sd to be inserted even though storage permission enabled.
ownjoouk said:
Ok encrypted sd caused me no end of issues so did a full wipe.
First bug I have got is in the camera. Keeps asking for sd to be inserted even though storage permission enabled.
Click to expand...
Click to collapse
That's strange, camera works great for me. Can you post logs?
Something is wrong. Magisk won't write to sd.
Log collector can't get access to collect the log.
Not sure what's going on!!
EDIT: Sorted it. It was because I had used external sd as internal. For some reason even after a full wipe it was looking for it. I had to tell it to forget it and now all is well.
EsRgood4u said:
as stated i cant for the life of me get TWRP to install! CMD fastboot install says its complete but when i boot into recovery i get the standard recovery menu! A step by step guide would be helpfull! Thanks!
Click to expand...
Click to collapse
Tutorial updated in post #2. Let me know if I left anything out!
ownjoouk said:
Something is wrong. Magisk won't write to sd.
Log collector can't get access to collect the log.
Not sure what's going on!!
Click to expand...
Click to collapse
Hmm I am unfamiliar with Magisk so this may be a tough one
GartimusPrime said:
Hmm I am unfamiliar with Magisk so this may be a tough one
Click to expand...
Click to collapse
It's ok. I edited my post. All is well now.
Magisk is systemless root.
---------- Post added at 11:34 PM ---------- Previous post was at 10:38 PM ----------
A lot of my daughters games fail to load on this rom. For now I will be returning to linage mm.
Getting a few tantrums!!
Installed tom using the 2nd method
I managed to install your ROM using the temp twrp install method! Enabled root within rom settings! Installed flashify and gave it root permission then I was able to flash twrp.img permanently via flashify! Rom is lightning fast compared to the stock ROM! WiFi not as fast but I can live with that! Screencast doesn't find my Philips TV but other casting apps find it fine! Excellent ROM! Congratulations to the developer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Supports Treble and Custom ROMs
Download
INSTALLATION:
0. Backup your ROM and all your data
1. Download the OrangeFox zip file to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
Frequently Asked Questions, MIUI OTA, Troubleshooting and Information:
https://wiki.orangefox.tech/en/guides
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Password
* Support for Miui and Custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Screenshots
See https://files.orangefox.tech/Screenshots/R10/
XDA:DevDB Information
[RECOVERY][OFFICIAL] OrangeFox Recovery Project for Samsung Galaxy J4 Core [R11], Tool/Utility for the Samsung Galaxy J4+
Contributors
SebaUbuntu
Source Code: https://gitlab.com/OrangeFox/
Version Information
Status: Stable
Current Stable Version: R10.1
Current Beta Version: R11
Created 2020-02-29
Last Updated 2020-07-25
hi @SebaUbuntu ,
great that this project exists! I'd definetly like to test this recovery for j4 core.
but am a bit confsd. there are some recoverys in the net, claiming to be for this device but are for j4, j4 plus, etc.
none of them worked for me when I tested. so I did some research & found out, that these devices have a different processor & ramdisk(size).
now I want to ask you, if it's really neccessary that they have the same processor & ramdisk(size) to be compatible for different devices as a recovery. I think yes, but maybe I'm wrong.
the second question I have is: do I need a twrp already installed before I can flash your recovery, or can I flash it right away? can I (try to) flash orange fox recovery through odin or through commandline? and where can I find a working twrp for this device -j4 core- ?
did you or somebody else already test the recovery & found it is working?
thimprfct said:
hi @SebaUbuntu ,
great that this project exists! I'd definetly like to test this recovery for j4 core.
but am a bit confsd. there are some recoverys in the net, claiming to be for this device but are for j4, j4 plus, etc.
none of them worked for me when I tested. so I did some research & found out, that these devices have a different processor & ramdisk(size).
now I want to ask you, if it's really neccessary that they have the same processor & ramdisk(size) to be compatible for different devices as a recovery. I think yes, but maybe I'm wrong.
the second question I have is: do I need a twrp already installed before I can flash your recovery, or can I flash it right away? can I (try to) flash orange fox recovery through odin or through commandline? and where can I find a working twrp for this device -j4 core- ?
did you or somebody else already test the recovery & found it is working?
Click to expand...
Click to collapse
this recovery is installed on my device
I passed Orange Fox through twrp
https://forum.xda-developers.com/ga...ecovery-unofficial-twrp-3-1-1-galaxy-t4046189
thimprfct said:
hi @SebaUbuntu ,
great that this project exists! I'd definetly like to test this recovery for j4 core.
but am a bit confsd. there are some recoverys in the net, claiming to be for this device but are for j4, j4 plus, etc.
none of them worked for me when I tested. so I did some research & found out, that these devices have a different processor & ramdisk(size).
now I want to ask you, if it's really neccessary that they have the same processor & ramdisk(size) to be compatible for different devices as a recovery. I think yes, but maybe I'm wrong.
the second question I have is: do I need a twrp already installed before I can flash your recovery, or can I flash it right away? can I (try to) flash orange fox recovery through odin or through commandline? and where can I find a working twrp for this device -j4 core- ?
did you or somebody else already test the recovery & found it is working?
Click to expand...
Click to collapse
Yeah, recoveries are device-specific, you can't install a recovery for another phone on j4corelte, this is for j4corelte, already tested, and official
To install this you first need to flash TWRP by kapmino269, then flash this as a zip file
Or you can extract recovery.img, repack it in a tar file and flash it with Odin, but TWRP method is easier
hey, it works for me, too & it's awesome - the recovery of the future! keep up the good work & thank you so much! ?
may I link to it in my thread (have a thread for j4 core with root guide)?
/data is not mounted in recovery, same for internal storage. tried many times.
now I'm searching for a workaround to remove encryption without losing my files...
does aroma manager work with this device & could it possibly help? on older androids this often fixed problems when the /data or internal storage partitions were not mounting.
or is there a command to force mount /data & remove encryption? I've read smth like this on stackexchange. mh, not sure. will do some research tho.
will there be an update for orangefox for j4core?
thimprfct said:
/data is not mounted in recovery, same for internal storage. tried many times.
now I'm searching for a workaround to remove encryption without losing my files...
does aroma manager work with this device & could it possibly help? on older androids this often fixed problems when the /data or internal storage partitions were not mounting.
or is there a command to force mount /data & remove encryption? I've read smth like this on stackexchange. mh, not sure. will do some research tho.
will there be an update for orangefox for j4core?
Click to expand...
Click to collapse
Format data (not wipe!)
Then flash this:
https://androidfilehost.com/?fid=11410963190603865586
This will disable encryption on stock ROM
thimprfct said:
hey, it works for me, too & it's awesome - the recovery of the future! keep up the good work & thank you so much! ?
may I link to it in my thread (have a thread for j4 core with root guide)?
Click to expand...
Click to collapse
Yeah, no problem
SebaUbuntu said:
Format data (not wipe!)
Then flash this:
https://androidfilehost.com/?fid=11410963190603865586
This will disable encryption on stock ROM
Click to expand...
Click to collapse
Is it tested? Format data. Flash the encryption disabler then it will boot? Even on gsi rom?
Star Dust said:
Is it tested? Format data. Flash the encryption disabler then it will boot? Even on gsi rom?
Click to expand...
Click to collapse
Yes
Thread closed per OP request.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ubuntu Touch for Xiaomi Mi Mix 3
With Support for OTA Updates
DISCLAIMER:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
REQUIRED:
- Unlocked bootloader
- Enable USB Debugging
INSTALLATION:
Download official installer from ubuntu-touch.io and follow on-screen instructions.
KNOWN BUGS:
Automatic brightness
Proximity sensors
GPS
Others: Please test and report
BUGS STATUS:
See here.
CHANGELOGS:
01 July 2021:
- Added ubports installer support (one-click installer)
- Fixed call audio
- Added Anbox 10 early support
22 June 2021:
- Added OTA support
- Fixed audio
- Fixed fingerprint
- Fixed MTP and ADB
- Fixed charging icon
27 May 2021:
- Switched from GSI to manual build using UBPorts CI
- Battery icon doesn't show as charge during charging, but it is charging fine
- Anbox is now working
Build info:
Build author: xperseus
Repo: https://gitlab.com/ubports/community-ports/android9/xiaomi-mi-mix-3
References:
Ubports' CI Guide: https://github.com/ubports/porting-notes/wiki/GitLab-CI-builds-for-devices-based-on-halium_arm64-(Halium-9)
Ubports' Documentation: https://docs.ubports.com/en/latest/
Halium Documentation: https://docs.halium.org/en/latest/index.html
Common tree: https://github.com/LineageOS/android_device_xiaomi_sdm845-common/tree/lineage-16.0
Device tree: https://github.com/LineageOS/android_device_xiaomi_perseus/tree/lineage-16.0
Kernel source: https://github.com/LineageOS/android_kernel_xiaomi_sdm845/tree/lineage-16.0
Credit to UBPorts & Halium team for support and guides. Specially thanks to NotKit.
Created 20 May 2021
Last Updated 01 July 2021
Screenshots
thanks!!
can i dualboot with android ?
Sorry english not my main language
Tungpham99 said:
can i dualboot with android ?
Sorry english not my main language
Click to expand...
Click to collapse
No you cannot.
Hi,
No matter how hard I try I cannot get past the MI logo.
I tried several twrp img (not every, and on most recent ones I get a treble zip compatibility error btw, seems normal tho)
I wonder if I missing something obvious...
Finally the possibility of Linux on this phone I waited for this day so long thank you so much for your work. Sadly Im unable to boot. On what TWRP Version are you? The current one wouldnt work with any Miui Android 9 version i tried. Tried flashing via TWRP / ADB both end in stuck Mi Logo.
xN&5NP said:
Finally the possibility of Linux on this phone I waited for this day so long thank you so much for your work. Sadly Im unable to boot. On what TWRP Version are you? The current one wouldnt work with any Miui 10 / Android 9 version i tried. Tried flashing via TWRP / ADB both end in stuck Mi Logo.
Click to expand...
Click to collapse
What Rom did you have previously installed? And did you do a full wipe / format before installing Miui 9?
luigi024 said:
Hi,
No matter how hard I try I cannot get past the MI logo.
I tried several twrp img (not every, and on most recent ones I get a treble zip compatibility error btw, seems normal tho)
I wonder if I missing something obvious...
Click to expand...
Click to collapse
Pls try this version of twrp as i used this one: https://dl.twrp.me/perseus/twrp-3.2.3-0-perseus.img.html
xN&5NP said:
Finally the possibility of Linux on this phone I waited for this day so long thank you so much for your work. Sadly Im unable to boot. On what TWRP Version are you? The current one wouldnt work with any Miui Android 9 version i tried. Tried flashing via TWRP / ADB both end in stuck Mi Logo.
Click to expand...
Click to collapse
Please use 3.2.3: https://dl.twrp.me/perseus/twrp-3.2.3-0-perseus.img.html
xN&5NP said:
What Rom did you have previously installed? And did you do a full wipe / format before installing Miui 9?
Click to expand...
Click to collapse
Please follow this steps:
1. Install Android 9 MIUI as base (I used CN 9.2.15) < Mi Flash fastboot as I was on android 11
2. Install and boot to TWRP < use TWRP 3.2.3, don't use the latest version
3. Download and flash Ubuntu Touch GSI v10 from here in TWRP < flash ubports GSI
4. Flash halium-boot.img attached in this post via fastboot/TWRP. < flash my halium-boot.img
5. Download and flash Halium-boot_no_console_patch from here in TWRP. < THIS IS A MUST, otherwise bootloop
6. Wipe data and reboot.
Note: u will lose all data in step 1, pls backup
luigi024 said:
Hi,
No matter how hard I try I cannot get past the MI logo.
I tried several twrp img (not every, and on most recent ones I get a treble zip compatibility error btw, seems normal tho)
I wonder if I missing something obvious...
Click to expand...
Click to collapse
Did you download and flash Halium-boot_no_console_patch as mentioned in op, this is very important to get out of bootloop.
Yes I flashed Halium-boot_no_console_patch each time I tried to boot, but it wasn't even booting, only MI logo...
I use the recovery package to reflash android 9, it may have caused the issue... Gonna wait a few more hours to download the fastboot package ! And while waiting I'll try just with this TWRP version if it works !
luigi024 said:
Yes I flashed Halium-boot_no_console_patch each time I tried to boot, but it wasn't even booting, only MI logo...
I use the recovery package to reflash android 9, it may have caused the issue... Gonna wait a few more hours to download the fastboot package ! And while waiting I'll try just with this TWRP version if it works !
Click to expand...
Click to collapse
Yes pls do that, and let me know.. i did it a few time, always working from my side. I think u might need to fastboot flash CN9.2.15 like me.
@luigi024, @xN&5NP hi both, I just tried to simulate my steps and realized that I failed to mentioned one important step, you need to flash LineageOS 16 on top of CN9.5.12. I have updated the op, if you cannot download LineageOS please pm me.
xperseus said:
@luigi024, @xN&5NP hi both, I just tried to simulate my steps and realized that I failed to mentioned one important step, you need to flash LineageOS 16 on top of CN9.5.12. I have updated the op, if you cannot download LineageOS please pm me.
Click to expand...
Click to collapse
Followed your steps and got Ubuntu Touch up and running. Great work!
xperseus said:
Please follow this steps:
1. Install Android 9 MIUI as base (I used CN 9.2.15) < Mi Flash fastboot as I was on android 11
2. Install and boot to TWRP < use TWRP 3.2.3, don't use the latest version
3. Download and flash Ubuntu Touch GSI v10 from here in TWRP < flash ubports GSI
4. Flash halium-boot.img attached in this post via fastboot/TWRP. < flash my halium-boot.img
5. Download and flash Halium-boot_no_console_patch from here in TWRP. < THIS IS A MUST, otherwise bootloop
6. Wipe data and reboot.
Note: u will lose all data in step 1, pls backup
Click to expand...
Click to collapse
Where do I find halium-boot.img as described in 4.? I'm obviously blind. Thanks in advance.
chromanju said:
Where do I find halium-boot.img as described in 4.? I'm obviously blind. Thanks in advance.
Click to expand...
Click to collapse
Please read the OP, the installation now is supported by Ubuntu Touch installer (UBPorts Installer), just download it from https://ubuntu-touch.io/get-ubuntu-touch and follow on screen instructions. Let me know if u still have questions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.7.0_12-v2
For device: denver
Android 12 Device Tree: https://github.com/juic3b0x/twrp12_device_motorola_denver
Maintainer/Authors build: ragarcia87
Android 12 Installation Instructions
DO NOT FLASH ZIP, UNZIP FIRST
First unzip the ANDROID-12-UNZIP-ME-FIRST.zip file to get a12v2-twrp-boot.img and Magisk-v25.2.zip files.
Copy a12v2-twrp-boot.img and Magisk-v25.2.zip to either internal storage or external SD card.
Then do:
Code:
adb reboot bootloader
fastboot boot a12v2-twrp-boot.img
Once TWRP boots up, go to Advanced > Install Recovery Ramdisk
Then choose the a12v2-twrp-boot.img
Then go to Install and choose the Magisk-v25.2.zip file to re-root the device
Then go to Reboot > System
Working
Everything, including touchscreen. No need to flash 3rd party kernel.
Troubleshooting
If you get the error createTarFork{} process ended with ERROR: 255
Go to /data/ folder and delete the fonts folder then reboot and try backup /data again.
//DISCONTINUED//
Android 11 Installation Instructions
Spoiler
DO NOT FLASH ZIP, UNZIP FIRST
Spoiler
First unzip the ANDROID-11-UNZIP-ME-FIRST.zip file to get twrp-boot.img and Magisk-v25.2.zip files.
Copy twrp-boot.img and Magisk-v25.2.zip to either internal storage or external SD card.
Then do:
Code:
adb reboot bootloader
fastboot boot twrp-boot.img
Once TWRP boots up, go to Advanced > Install Recovery Ramdisk
Then choose the twrp-boot.img
Then go to Install and choose the Magisk-v25.2.zip file to re-root the device
Then go to Reboot > System
Thank you for this! I will give it a shot.
jpearson82 said:
Thank you for this! I will give it a shot.
Click to expand...
Click to collapse
You're welcome. Let me know! I am personally using it if course and so far only complaint I got is a little lag but touchscreen works out the gate with no need of a script or anything. Got it set to load the modules from vendor partition for touchscreen to work properly.
Really ? It reboots to system instead of to a brick? What's next custom ROM? People like you restore my faith in humanity. Confirmed working
ddougg said:
Really ? It reboots to system instead of to a brick? What's next custom ROM? People like you restore my faith in humanity. Confirmed working
Click to expand...
Click to collapse
Glad, to be of service
And thank you for confirming it's working. No problems with touchscreen or anything? (not that I am expecting there to be issues, just curious)
i flashed the zip multiple times before realizing i was supposed to unzip it
Practixal said:
i flashed the zip multiple times before realizing i was supposed to unzip it
Click to expand...
Click to collapse
My bad, I updated the post with explicit don't flash zip, unzip first. I apologize man. That's why on the expanded install instructions I named the zip like I did, lol. Did you get it sorted though?
ragarcia87 said:
My bad, I updated the post with explicit don't flash zip, unzip first. I apologize man. That's why on the expanded install instructions I named the zip like I did, lol. Did you get it sorted though?
Click to expand...
Click to collapse
yea its all good
Practixal said:
yea its all good
Click to expand...
Click to collapse
K good. Wanted to make sure all was well. Confirmed working for you as well?
ragarcia87 said:
K good. Wanted to make sure all was well. Confirmed working for you as well?
Click to expand...
Click to collapse
yup, it does take a second after loading for the touch to work but it does work.
Practixal said:
yup, it does take a second after loading for the touch to work but it does work.
Click to expand...
Click to collapse
Yeah that's normal. It's loading the modules from the vendor partition so it's mounting that first then searching for the modules then loading them
Does this work on Android 12?
jpearson82 said:
Does this work on Android 12?
Click to expand...
Click to collapse
Um, I haven't tried it on Android 12. I will see about also compiling with Android 12 TWRP base. If you wanna try it on A12 and report back that would be awesome
ragarcia87 said:
Um, I haven't tried it on Android 12. I will see about also compiling with Android 12 TWRP base. If you wanna try it on A12 and report back that would be awesome
Click to expand...
Click to collapse
I'll give it a try :}
jpearson82 said:
I'll give it a try :}
Click to expand...
Click to collapse
Awesome! Let me know. Decryption might not work on A12. I'm compiling A12 based TWRP now. Seeing if it compiles anyways, lol.
ragarcia87 said:
Awesome! Let me know. Decryption might not work on A12. I'm compiling A12 based TWRP now. Seeing if it compiles anyways, lol.
Click to expand...
Click to collapse
Question. Do I need to do this from a stock/rooted device. What if I already have root with magisk installed? Do I need to uninstall Magisk first before doing this?
jpearson82 said:
Question. Do I need to do this from a stock/rooted device. What if I already have root with magisk installed? Do I need to uninstall Magisk first before doing this?
Click to expand...
Click to collapse
No you dont have to uninstall it first. You can just use
Code:
fastboot boot twrp-boot.img
to just try it out first and see if it boots and works properly before picking Advanced Install to Ramdisk...
ragarcia87 said:
No you dont have to uninstall it first. You can just use
Code:
fastboot boot twrp-boot.img
to just try it out first and see if it boots and works properly before picking Advanced Install to Ramdisk...
Click to expand...
Click to collapse
Alright. touch screen works after i turn off the screen and turn it back on. umm it also wont let me backup any data.
jpearson82 said:
Alright. touch screen works after i turn off the screen and turn it back on. umm it also wont let me backup any data.
Click to expand...
Click to collapse
Ok thank you. Yeah I didnt think decryption would work. It's meant for A11... but I will work on A12 compile version of it now. Just gotta get the right modules, etc from A12. Once It's done I'll add it to this thread in addition to the A11 version.
I look forward to trying it out!