Team Win Recovery Project 3.1.1-0
This is for the International Oppo R7S, Snapdragon models only! Do not flash on Mediatek R7Sm models!
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://twrp.me/devices/oppor7sf.html
For Official TWRP Changelog see Official TWRP News page:
https://twrp.me/
Old changelog listing:
CHANGELOG for 3.0.2-2:
-Fix subpartition restore bug (ex: EFS)
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords).
This fixes decrypt of full device encryption on devices that support decrypt.
This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese
won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_oppo_r7sf (master)
Thanks! & Contributors!
My wife for her patience love you baby!
Team Win, especially Dees-Troys, MSF, Captain_Throwback
Most of all! Uberlaggydarwin , without you this would not have been possible
As promised I have created a Guide on how to install TWRP permanently on the Oppo R7S. It is attached. See below!
Update: Updated Guide to V3 due to TWRP Update and minor fixes in the Guide.
Counter:
GuideV1.pdf = ~1000 Downloads
GuideV2.pdf = 3700 Downloads
GuideV3.pdf = 2918 Downloads
Does it mean that bootloader is unlocked ?
lapocompris said:
Does it mean that bootloader is unlocked ?
Click to expand...
Click to collapse
You are able to unlock the bootloader. For me it's just not possible to enter twrp. Everytime gets overwritten by color os recovery.
OK. Just tested it on the R7 Lite. It works well. Also, as expected, it has soft keys and the hard keys dont work.
Could anyone point me to a step by step instruction on how to install twrp recovery. Sorry for the novice question. Sorry without Root as I'm on latest 5.1.1 and cannot root with oppo tools.
smokeyrider said:
Could anyone point me to a step by step instruction on how to install twrp recovery. Sorry for the novice question. Sorry without Root as I'm on latest 5.1.1 and cannot root with oppo tools.
Click to expand...
Click to collapse
Just head over to the twrp page. The is an instruction written down. Don't forget to unlock your bootloader.
Hi I have followed the instructions. I can "adb reboot bootloader" and get oppo bootloader screen. When I enter "fastboot flash recovery twrp.img" My phone just reboots to normal and the CMD prompt just hangs "waiting for device". Any assistance appreciated. I have latest 5.1.1 Color OS and Windows 10 machine. Thanks.
Ravikirancg said:
OK. Just tested it on the R7 Lite. It works well. Also, as expected, it has soft keys and the hard keys dont work.
Click to expand...
Click to collapse
if you have root and could provide me with the output of the partition details I can build a TWRP specific for the R7 Lite. if it has not been done yet.
I will need information output of:
ls -l /dev/block/bootdevice/by-name/
and
cat /proc/partitions
you will need to have root and switch to "su" in the shell before entering the commands.
celoxocis said:
if you have root and could provide me with the output of the partition details I can build a TWRP specific for the R7 Lite. if it has not been done yet.
I will need information output of:
ls -l /dev/block/bootdevice/by-name/
and
cat /proc/partitions
you will need to have root and switch to "su" in the shell before entering the commands.
Click to expand...
Click to collapse
Your alive celoxocis!
Do you have some news on twrp for ps, your cm build etc?
MacLaughlin said:
Your alive celoxocis!
Do you have some news on twrp for ps, your cm build etc?
Click to expand...
Click to collapse
CM is still work in progress. I will be leaving tomorrow for a one week getaway. After that I plan to write a PDF guide for those with PS how to install TWRP as PS fastboot allows for bootloader unlocking.
celoxocis said:
CM is still work in progress. I will be leaving tomorrow for a one week getaway. After that I plan to write a PDF guide for those with PS how to install TWRP as PS fastboot allows for bootloader unlocking.
Click to expand...
Click to collapse
I thought you need to update the twrp version? The only problem was twrp didn't get recognized and gets overwritten by color os recovery.
MacLaughlin said:
I thought you need to update the twrp version? The only problem was twrp didn't get recognized and gets overwritten by color os recovery.
Click to expand...
Click to collapse
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
celoxocis said:
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
Click to expand...
Click to collapse
But I get a success notification...? Fastboot oem unlock
MacLaughlin said:
But I get a success notification...? Fastboot oem unlock
Click to expand...
Click to collapse
if you do "fastboot OEM unlock" twice. does it show "already unlocked" the second time?
celoxocis said:
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Device already : unlocked!
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.874s
So the bootloader is unlocked. DTB stands for Device Tree Blob and is a mechanism to pass low level hardware information between bootloader and kernel. So I guess it's just not for PS.
---------- Post added at 07:05 PM ---------- Previous post was at 06:44 PM ----------
celoxocis said:
if you do "fastboot OEM unlock" twice. does it show "already unlocked" the second time?
Click to expand...
Click to collapse
Yes!
MacLaughlin said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Device already : unlocked!
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.874s
So the bootloader is unlocked. DTB stands for Device Tree Blob and is a mechanism to pass low level hardware information between bootloader and kernel. So I guess it's just not for PS.
---------- Post added at 07:05 PM ---------- Previous post was at 06:44 PM ----------
Yes!
Click to expand...
Click to collapse
I know what DTB stands for I can see that you are on Project Spectrum. The DTB for PS (Marshmallow) is different than that for ColorOS (Lollipop) there fore it is not working. The offical TWRP is based on ColorOS for the mainstream available. Project Spectrum is only available for beta testers. However "fastboot flash recovery TWRP. IMG" should work. To enter TWRP simply hold down volume-down + power button. When I finish CM I will release a TWRP with kernel+DTB based on Android 6.0!
celoxocis said:
I know what DTB stands for I can see that you are on Project Spectrum. The DTB for PS (Marshmallow) is different than that for ColorOS (Lollipop) there fore it is not working. The offical TWRP is based on ColorOS for the mainstream available. Project Spectrum is only available for beta testers. However "fastboot flash recovery TWRP. IMG" should work. To enter TWRP simply hold down volume-down + power button. When I finish CM I will release a TWRP with kernel+DTB based on Android 6.0!
Click to expand...
Click to collapse
Sadly this is not working. I can flash TWRP but if I try to enter TWRP the screen just stays black. At the moment I'm not able to enter recovery, with key buttons. Also Color Os recovery isn't working at the moment.
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
celoxocis said:
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
Click to expand...
Click to collapse
I will flash stock recovery again. Maybe later on the new version of ps.
celoxocis said:
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
Click to expand...
Click to collapse
Okay stock recovery isn't working anymore as well. The screen just stays black. Got exactly the same error as when flashing twrp. Now I'm without a working recovery ???? maybe I can extract the recovery img. from spectrum. See if this is working.
Related
Attention: To be able to flash, the bootloader needs to be unlocked (https://en.miui.com/unlock/). Please be warned though: Xiaomi changed something in the method of unlocking the device from May 2018 security update onwards. Now all data will be flushed if you unlock a previously locked device. So please be warned and check the .bat/ .sh scripts for "lock" and "unlock" commands and remove these lines if unsure. If you don't want to unlock your device, you can use everything without the need of editing anything.
Side note: Before everyone is complaining about that kind of change, it makes sense from security point of view: Say, someone steals your phone and he could just unlock the bootloader, he has any possibility to get to your most private data. Just some technical background, but I am not related to Xiaomi or anything, just applying logic.
Introduction:
XIAOMI offers for their official releases also fastboot images including easy to use shell/ batch scripts for flashing.
Luckily, this is also the case for our Mi A1, delivering us a very neat way to easy flash or even emergency rescue our phone via fastboot.
The included shell scripts (*.sh) are meant to be used on Mac/ Linux,
the included batch files (*.bat) are for the Windows users.
Prerequisite:
adb & fastboot have to be installed for the scripts and the flashing to work properly. Please ensure, that your versions are up2date, if you should run into any issues.
Warning: Do not use the flash_factory.bat or .sh file, as it deletes your IMEI.
Android Pie Fastboot Link (official): http://c.mi.com//miuidownload/detail?device=1700333
Version: V10.0.10.0.PDHMIXM (Android P)
Size: 1166M
md5:
Code:
n.a.
No Fastboot image found (yet) --> Please use V10.0.9.0 available here under "Previous versions" and update via OTA
V10.0.10.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] June 2019 Security patch
[/LIST]
Previous versions:
Version: V10.0.9.0.PDHMIXM (Android P)
Size: 1616M
md5:
Code:
3ded3e7b82097f27ddf176e0399fceba
https://bigota.d.miui.com/V10.0.9.0...0.PDHMIXM_20190514.0000.00_9.0_3ded3e7b82.tgz
V10.0.9.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] Max 2019 Security Patch
[/LIST]
Version: V10.0.4.0.PDHMIXM (Android P)
Size: 1616M
md5:
Code:
2cee840c96cdb6e0a9b14fc3c3105ff7
https://bigota.d.miui.com/V10.0.4.0...0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
V10.0.4.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] FM Radio Adaptive battery and brightness
[*] Simpler ways to navigate your phone
[*] Recommended apps and actions based on your context
[/LIST]
Version: V9.6.8.0.ODHMIFE (Android O, 8.1)
Size: 1616M
md5:
Code:
9ea450fe98fbf4883439a934847f9f5d
https://bigota.d.miui.com/V9.6.8.0....0.ODHMIFE_20181031.0000.00_8.0_9ea450fe98.tgz
V9.6.8.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the November 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
Version: V9.6.7.0.ODHMIFE (Android O, 8.1)
Size: 1615M
md5:
Code:
47d6fd23c7ca5aa538258782aceb3bd2
https://bigota.d.miui.com/V9.6.7.0....0.ODHMIFE_20181015.0000.00_8.0_47d6fd23c7.tgz
V9.6.7.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the October 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
[*] [B]Version: V9.6.4.0.ODHMIFE (Android O, 8.1)[/B]
Size: 1559M
md5: [CODE]735823083fba68350ba27f418114f388
https://bigota.d.miui.com/V9.6.4.0....0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
V9.6.4.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the July 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
Version: V9.5.11.0.ODHMIFA (Android O, 8.0)
Size: 1462M
md5:
Code:
1a04581058dc7f27ca18cf8fd74f9413
https://bigota.d.miui.com/V9.5.11.0...0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
V9.5.11.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update June Security Patch
[/LIST]
Version: 9.5.10.0.ODHMIFA (Android O)
Size: 1462M
md5:
Code:
b9e697ed56b49f3657fa13229241519a
https://bigota.d.miui.com/V.9.5.10....0.ODHMIFA_20180405.0000.00_8.0_b9e697ed56.tgz
V9.5.10.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update April Security Patch
[/LIST]
Version: 9.5.9.0.ODHMIFA (Android O)
Size: 1422M
md5:
Code:
5773957dcda9a89495e1d0bfa84ab220
https://bigota.d.miui.com/V9.5.9.0....0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e.tgz
OPR1.170623.026.V9.5.9.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update Mar Security Patch
[*] Fix “couldn’t flash ROM in 9008 mode”
[*] Fix “[IN_User Feedback][Reboot][Mi A1]Random reboot while using the device on V9.5.4.0.ODHMIFA”
[/LIST]
Version: V9.5.4.0.ODHMIFA (Android O)
Size: 1422M
md5:
Code:
5773957dcda9a89495e1d0bfa84ab220
https://bigota.d.miui.com/V9.5.4.0....0.ODHMIFA_20180226.0000.00_8.0_5773957dcd.tgz
OPR1.170623.026.V9.5.4.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update Feb Security Patch
[*] Fix “received call recognized as missed call”
[*] Fix rebooting issue
[*] Update E-label for India
[/LIST]
Version: Android 8.0.0 [OPR1.170623.026.8.1.10]
Size: 1407M
md5:
Code:
8ea503201bb0b594e02e5ed2bf6dea09
https://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
OPR1.170623.026.8.1.10 ROM for Mi A1 Changelog
Code:
[LIST=2]
[*] Optimize audio parameters.
[*] Remove the “quick charge” on the lockscreen when charging.
[*] Integrate the performance optimization of MIUI.
[*] Fix “bluetooth power consumption issue”.
[*] Add Korean input method.
[*] Fix “the dialer icon is missing after the upgrade”.
[*] Fix “camera cannot connect sometimes”.
[*] Fix“couldn’t connect to network sometimes”.
[*] Update the Feedback APP.
[*] Fix “fingerprint unlocking speed is slow ”.
[/LIST]
Version: N2G47H.7.12.29 (Android O)
Size: 1084M
md5:
Code:
c9a6ea979b58b9a2fa4dc9e81d70796e
https://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
no changelog found
Version: N2G47H.7.12.19
Size: 1396M
md5:
Code:
d39fa89aafcaaaa2203324313c964706
https://bigota.d.miui.com/7.12.19/tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
N2G47H.7.12.19 ROM for Mi A1 Changelog:
Code:
[LIST=2]
[*] D2Acontinuous annoying sharp Sound problem in A1
[*] D2A is transferred to 112 when the local emergency number is called in the Czech Republic
[*] Transition version for Android Oreo
[/LIST]
Short Flashing Guide:
Choices for flashing/ Which script to run?
flash_all = Full flash, like factory reset, bootloader stays unlocked
flash_all_except_storage = Keep your data, bootloader gets re-locked
flash_all_lock = Full flash, like factory reset, bootloader gets re-locked
(*.bat for Windows/ *.sh for Linux & Mac)
Download and extract the *.tgz archive
Shutdown your Mi A1 and start it in fastboot mode (Vol- + Power)
Connect it to your computer/ mac via usb cable
Open a terminal, shell or command line prompt depending on your OS; make sure you are in the same folder as all the just extracted files, if in doubt use the "cd" command
Run the script of your choice to start the flashing process (e.g.: "flash_all.bat" or "./flash_all.sh")
Wait for the script to complete and enjoy your official version of AndroidOne for Mi A1
Hints:
You need to have an up-to-date version of adb and fastboot to be installed properly on your system. For that please just follow the guide here
To get the device in fastboot mode, turn it off, hold VOL(-) & the power button
To check for successful connection type in shell/ terminal "fastboot devices" after device is connected via USB in fastboot mode
If you want/ need to have an unlocked bootloader, you can still use any of the above described scripts and just when finished flashing, reboot again into fastboot mode and run the terminal/ shell/ cmd command "fastboot oem unlock" (locking and unlocking does not mess with your user data)
Just to be clear, inspite of the URL containing "miui" in its name, it is official Android One for Mi A1 (tissot)
Please do not attempt to do downgrades, without factory reset
If you are feeling unfamiliar and/ or unsafe, please use the Mi Flash Tool for Windows instead to install (Guide for Mi Flash Tool; if you had a previous version of Mi Flash tool installed it needs to be uninstalled first)
If you want to force, that you get OTA updates when they become available and you check in system settings manually for them, please ensure that you are using the Google Play Beta Services
Everything seems so complicated, isn't there a tool to assist me? --> I did some research and there seems to be one: https://toolaio.tk/
{
"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"
}
All credits for this tool go to its creator mauronofrio
Hi , thank you for the update because I find only bin files on the official site.
The script .bat don't work on my laptop so I flashed manually all the images files.
I didn't succeed by flashing dummy, fs_image.tar.gz and persist image files. I'm pretty sure it's because there weren't on my version of the OS so if someone could help me by telling me how to push these images files, where and thanks which command, it could be great! ^^
lelozerien said:
Hi , thank you for the update because I find only bin files on the official site.
The script .bat don't work on my laptop so I flashed manually all the images files.
I didn't succeed by flashing dummy, fs_image.tar.gz and persist image files. I'm pretty sure it's because there weren't on my version of the OS so if someone could help me by telling me how to push these images files, where and thanks which command, it could be great! ^^
Click to expand...
Click to collapse
Hi, what error message do you get, when trying to run the batch script? Did you try via command line (cmd) or via powershell (Win10)?
The things you tried to flash without succeeding seem to be not necessary. Please find here all fastboot commands used by "flash_all_except_storage":
Code:
fastboot oem unlock
fastboot flash modem_a /images/modem.img
fastboot flash modem_b /images/modem.img
fastboot flash sbl1 /images/sbl1.img
fastboot flash sbl1bak /images/sbl1.img
fastboot flash rpm /images/rpm.img
fastboot flash rpmbak /images/rpm.img
fastboot flash tz /images/tz.img
fastboot flash tzbak /images/tz.img
fastboot flash devcfg /images/devcfg.img
fastboot flash devcfgbak /images/devcfg.img
fastboot flash dsp /images/adspso.bin
fastboot flash sec /images/sec.dat
fastboot flash splash /images/splash.img
fastboot flash aboot /images/emmc_appsboot.mbn
fastboot flash abootbak /images/emmc_appsboot.mbn
fastboot flash boot_a /images/boot.img
fastboot flash boot_b /images/boot.img
fastboot flash system_a /images/system.img
fastboot flash system_b /images/system.img
fastboot flash lksecapp /images/lksecapp.img
fastboot flash lksecappbak /images/lksecapp.img
fastboot flash cmnlib /images/cmnlib.img
fastboot flash cmnlibbak /images/cmnlib.img
fastboot flash cmnlib64 /images/cmnlib64.img
fastboot flash cmnlib64bak /images/cmnlib64.img
fastboot flash keymaster /images/keymaster.img
fastboot flash keymasterbak /images/keymaster.img
fastboot reboot bootloader
fastboot set_active a
fastboot oem lock
fastboot reboot
majamee said:
Hi, what error message do you get, when trying to run the batch script? Did you try via command line (cmd) or via powershell (Win10)?
The things you tried to flash without succeeding seem to be not necessary. Please find here all fastboot commands used by "flash_all_except_storage":
Click to expand...
Click to collapse
great! I will study which steps are missing! thank you!
Edit: I'm on Win 8 and I'm not able to read the error message because it disappears very quickly! I tried by double clik on the .bat.
lelozerien said:
great! I will study which steps are missing! thank you!
Edit: I'm on Win 8 and I'm not able to read the error message because it disappears very quickly! I tried by double clik on the .bat.
Click to expand...
Click to collapse
Ok, that info should be already enough to help you First press the Windows button and enter "cmd" to start the command line. Once there you have to "cd" (change directory) into the extracted directory (the one where also the *.bat/ *.sh files are in).
Once there you should be able to verify that you are correct by entering "dir" which lists you all the files in the current folder.
After that you just need to call the batch script you want to run by entering its full name and press enter. Then you can sit back and enjoy the show
Edit: Of course you have to have your phone already connected in fastboot mode
Xiaomi just released the full fastboot image for Oreo, which they labeled stable. I disagree, but for everyone who wants to enjoy Oreo already it is the best option we have so far. In comparison to the manual update to Oreo you can also close your bootloader and don't end up in a bootloop, so that is... something!
The flash all command will not relock the bootloader ??? Or will all three choices relock the bootloader ?
Is this same patch level "December 1"?
coremania said:
The flash all command will not relock the bootloader ??? Or will all three choices relock the bootloader ?
Click to expand...
Click to collapse
flash_all does not lock the bootloader.
If you are in doubt and want to keep an unlocked bootloader, I would recommend to choose the script which matches the best what you are looking for.
Then afterwards let your phone reboot, once completed turn it off and start it again in fastboot mode (Volume- + Power) and run in command line/ terminal/shell the following command:
Code:
fastboot oem unlock
Pezmet said:
Is this same patch level "December 1"?
Click to expand...
Click to collapse
Yes
Pezmet said:
Is this same patch level "December 1"?
Click to expand...
Click to collapse
It is, but for instance the slow camera opening bug is gone for me. So I consider it worth the effort so far.
majamee said:
flash_all does not lock the bootloader.
If you are in doubt and want to keep an unlocked bootloader, I would recommend to choose the script which matches the best what you are looking for.
Then afterwards let your phone reboot, once completed turn it off and start it again in fastboot mode (Volume- + Power) and run in command line/ terminal/shell the following command:
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thanks,
I don't like to relock my bootloader ever,
until selling the device.
Flashing and a locked bootloader never were or will be friends
I do a flash all and restore my data with TWRP.
coremania said:
Thanks,
I don't like to relock my bootloader ever,
until selling the device.
Flashing and a locked bootloader never were or will be friends
I do a flash all and restore my data with TWRP.
Click to expand...
Click to collapse
Alternatively, you could also use flash_all_except_storage, when opening it as a text file first, by removing the line which includes the "oem lock" command. Start looking from the very end of the script file, it is one of the last commands
Hey
I downloaded rom from official site
But when i extracted .tgz file i got payload.bin file
I did not get any .img or any scripts
majamee said:
It is, but for instance the slow camera opening bug is gone for me. So I consider it worth the effort so far.
Click to expand...
Click to collapse
Still slow camera here, are you clean stock ? Or on TWRP and magisk like me ?
Edit: that's funny camera gets fast after opening a few times
how about battery drain fixed or not any test ?
¿ Have The Same bugs that oreo [OTA] ?
-Slow open Camera.
-Bluetooth Drain Battery.
-Some Apps Crashed Like Whatsapp
there is an another .bat file named flash factory.bat..
dont flash this "flash_factory.bat"
i did it and my phone is screwed up..
it fails and doesnt boot..
i dont think this is for our phone..
Blackheart151 said:
dont flash this "flash_factory.bat"
i did it and my phone is screwed up..
it fails and doesnt boot..
i dont think this is for our phone..
Click to expand...
Click to collapse
Sad, to hear that, but just to be clear this one I did not even mention in my guide/ OP. Hope you find a way to recover from it though.
coremania said:
Still slow camera here, are you clean stock ? Or on TWRP and magisk like me ?
Click to expand...
Click to collapse
Clean stock and it got way better for me.
Hi, everyone. After reading posts of (and having experienced my own) boot loops and seeing as how there is a guide for the first Huawei watch,
I've decided that there should also be a guide for restoring the Huawei Watch 2 to stock ROM.
Getting Prepared
The bootloader unlocked on the watch. For instructions on how to do so, read janjan's TWRP Recovery guide.
ADB/fastboot and drivers already setup on your computer
ADB debugging enabled on the watch. You can find instructions for this at the same URL link above.
Restoring Via Batch/Shell Executable
The stock image files in janjan's thread are no longer available, so you'll have to go to this Reddit thread for the file.
Under the "Flashing back to stock" section, download the appropriate version for your watch.
Reboot your watch to bootloader either manually or via the ADB command:
Code:
adb reboot bootloader
Unzip the file
For Sawfish Devices:
At the command line, type in the following:
Code:
flash-all.bat (for Windows) or .flash-all.sh (for Linux)
fastboot oem lock
fastboot reboot
For Sawshark Devices: (or if you were having trouble executing the flash-all file successfully. NOTE: There's a missing image
file in the Sawshark stock file, so the flash-all file will not run successfully.)
Go to the folder where you extracted the stock image file and extract the zip file that's there.
Then go to the command line and type in the following:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot oem lock
fastboot reboot
Credits/Thanks
janjan - HUAWEI WATCH 2 (LTE-Sawshark) & (BT-Sawfish)-OWDE.180926.001.A1
- [RECOVERY]+[sawshark(4G)+sawfish(BT)]Unofficial TWRP 3.1.1-0-[29-3-18]
travis82 - [ROM] [KERNEL] [SAWSHARK] Oreo OWDE.180215.017 [DEC/24/2018]
Skin1980 - [GUIDE] [HOWTO] Return to stock for Huawei Watch
davpel - [GUIDE][HOW TO]Boot into Fastboot Mode
CadBuRy.VN - [Rom][NXG46W] Huawei Watch 2 4G L-09S Global Fastboot [Factory Images]
Great guide.
Will try this on my watch.
Thanks.
does not work on leo-dlxx...it will kill the device i restored via twrp another rom
anyone have a stock rom for leo-dlxx?
Timewolf said:
does not work on leo-dlxx...it will kill the device i restored via twrp another rom
anyone have a stock rom for leo-dlxx?
Click to expand...
Click to collapse
I actually have the Leo-DLXX and I wrote this guide mainly for that watch. Do you remember what error messages you received? How does it kill the device?
How prevent upgrade after this? I flash it and all good, but it upgrades to last firmware and I see no solution to stop it
"Invalid sparse file format at header magi" while trying to flash system.img
Thanks!!! You saved my Smartwach because it was bricked and I couldn't find orginal stock firmware
not work with sawshark leo-dll only stuck in logo
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
square_eyes said:
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
Click to expand...
Click to collapse
Well, I haven't ever seen sth like you're trying to do, but can you point me to the source of the rom you're trying to flash?
square_eyes said:
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
Click to expand...
Click to collapse
And the second question: Do you own sawfish (WiFi) or Sawshark (LTE) watch?
(I'm going to sleep soon but I'll take a look on this tomorrow)
Lord Sithek said:
And the second question: Do you own sawfish (WiFi) or Sawshark (LTE) watch?
(I'm going to sleep soon but I'll take a look on this tomorrow)
Click to expand...
Click to collapse
sawfish sorry! Will update post. ROM is in the link but I'll have to ask the dev for the source.
Lord Sithek said:
square_eyes said:
sawfish sorry! Will update post. ROM is in the link but I'll have to ask the dev for the source.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Can you share the link or the site where it was posted?.I just wanted to take a look Anyway, maybe you could try the approach from the instructions for sawshark from the opening post here. I mean extract zip and flash images separately in fastboot mode.
Also make sure you have the correct rom version for wifi variant
Lord Sithek said:
Can you share the link or the site where it was posted?.I just wanted to take a look Anyway, maybe you could try the approach from the instructions for sawshark from the opening post here. I mean extract zip and flash images separately in fastboot mode.
Also make sure you have the correct rom version for wifi variant
Click to expand...
Click to collapse
I ended up getting it working. See here for how I rolled back the Wear OS version... https://github.com/NightscoutFoundation/xDrip/issues/749#issuecomment-850037862
Below is the link from above with the files (not source sorry - I'm not sure where that's kept). If you know how to make the demigod patch compatible with the latest official firmware/or even an unofficial ROM, that would be awesome.
See Huawei Watch 2 Care Pack .zip on...
Patching Android Wear devices for use with the G5
Nightscout version of xDrip+. Contribute to NightscoutFoundation/xDrip development by creating an account on GitHub.
github.com
the zip has two patches, and instructions.
square_eyes said:
I ended up getting it working. See here for how I rolled back the Wear OS version... https://github.com/NightscoutFoundation/xDrip/issues/749#issuecomment-850037862
Below is the link from above with the files (not source sorry - I'm not sure where that's kept). If you know how to make the demigod patch compatible with the latest official firmware/or even an unofficial ROM, that would be awesome.
See Huawei Watch 2 Care Pack .zip on...
Patching Android Wear devices for use with the G5
Nightscout version of xDrip+. Contribute to NightscoutFoundation/xDrip development by creating an account on GitHub.
github.com
the zip has two patches, and instructions.
Click to expand...
Click to collapse
Great, glad it worked for you. Unfortunatelly, Im not that skillfull to help you with latest firmware...
Blu G90 device shipped from factory with Android 10
as with other devices from blu they do not have a public download of there roms. So here is the stock rom pulled from the device with SP-Flash tool.
Both the shipped rom build fingerprint
Code:
ro.bootimage.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020/1585383273:user/release-keys
And the ota update from June fingerprint
Code:
ro.system.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020/1592848714:user/release-keys
are in android file host flash-able with spflash tool, if needed.
I know the first thing to have before modifying android is the method to recover from bad edits. So here they are.
Other works will be stored in this same folder.
https://www.androidfilehost.com/?w=files&flid=315927
First stock rom is Dumped to github, If you need or want specific files, without needing to download whole rom.
https://github.com/mrmazakblu/blu_g0310ww_dump
Stock kernel source:
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device INFO
*******Above links are pulled firmware. Below is an official firmware file, w/ verified images.********
https://www.mediafire.com/folder/ocmvgrcd73bqy/G90
**
.
Bootloader unlock is same as past devices.
1. enable develper options
2. enable OEM unlock , from inside developer options
3. Reboot to bootloader (adb reboot bootloader, or button combo)
4. fastboot flashing unlock
5. Select confirm on device
6. fastboot reboot (causes factory reset)
Flashing GSI
few more steps than Pie devices, but not too complicated.
You will need recent fastboot tools as tested these steps were done with V30.0.4
https://developer.android.com/studio/releases/platform-tools
Verified boot is enabled on device. The verity key is stored into 3 section.
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
All found in stock rom. Shared in first post.
1. Unlock bootloader. (see last post)
2. Reboot to bootloader to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
3. Reboot from bootloader to fastboot(new interface for android 10)
Code:
fastboot reboot fastboot
4. flash sysem from "fastbootd"
Code:
fastboot flash system **gsi-system.img**
Use 64 bit AB GSI
5. Wipe data so the new system will work
Code:
fastboot -w
ROOT::
Not yet confirmed yet. Magisk patched_boot has not provided root as of yet.
Currently looking into pre-rooting the system.img, but not success yet.
TWRP;;
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-blu-g90-g0310ww-t4163497
.
I have been able to edit the stock /system and flash it back to phone.
--I have added adaway host file
--Removed the SIMO app
-- Removed the IGNITE adware app (dti.blu)
--Removed The Verizon Remote SIM lock app
--Removed Blu-Privacy app
--Removed Opera browser app
--Deodexed Rom (rom would not boot past splash screen without this)
Uploaded edited sysem.img to device folder listed in OP.
Flash with same instructions as How to flash GSI
--Attempting to add SU binary makes rom fail to boot. So still no stock rooted.
Maybe soon.
/
Blu released kernel source today. 8-27. The tar.hz is dated April, eh, whatever.
I added the source files to the wip twrp tree, it compiles without error. (Not my normal experience , on first time out with Blu kernel).
But as mentioned before, the twrp will not pack the image correctly. Because of the need for new dtb commands that twrp 9.0 build environment does not accept.
And when building in the twrp 10.0-wip tree, the results have not booted for me yet. (I'm on build attempt 12, or so)
I'm rambling, sorry.
When I repack the twrp using the built kernel, twrp has only blank screen, and adb is active. So kernel is slightly off.
Build did not output separate dtb or dtbo.
Well I confirmed it, the screen on this phone is not the one the kernel is building for.
I compared the defconfig from source, the one that matches the name in build prop, to the one I pulled from /proc. And they are different, and the kernel errors out during build when using right defconfig. So, waiting again for Blu to provide the files.
There does not appear to be any interest in this phone, other than my own.
Well maybe it will catch on
It's been advertised on many mm ore locations than the average BLU phone.
Amazon
Ebay
Walmart
Newegg
Best buy
B&H photo
Time will tell.
mrmazak said:
Well I confirmed it, the screen on this phone is not the one the kernel is building for.
I compared the defconfig from source, the one that matches the name in build prop, to the one I pulled from /proc. And they are different, and the kernel errors out during build when using right defconfig. So, waiting again for Blu to provide the files.
Click to expand...
Click to collapse
Any luck with Blu providing the correct kernel files?
Ivisibl3 said:
Any luck with Blu providing the correct kernel files?
Click to expand...
Click to collapse
Not yet. They acknowledged my email, but as yet have not updated there posted source.
Root is half way achieved.
Factory rom was found. It included a boot-debug.img
When this image is used in boot partition, adb root is allowed.
It is only limited root. Example: blockdev command , used to allow remount / to rw, is not permitted. Bit is start.
Factory flashtool rom shared on Blu developers mediafire page.
Will add link to debug-boot.img soon
added to device folder listed in OP
google information on debug-boot.img
https://source.android.com/compatibility/vts/vts-on-gsi
if you have the stock boot.img, and magisk manager, why cant you patch the boot.img and then disable dm-verity by flashing vbmeta.img/vbmeta_system.img/vbmeta_vendor.img and then flash the boot.img via sp flash tool to give you root access?
aryanhington said:
if you have the stock boot.img, and magisk manager, why cant you patch the boot.img and then disable dm-verity by flashing vbmeta.img/vbmeta_system.img/vbmeta_vendor.img and then flash the boot.img via sp flash tool to give you root access?
Click to expand...
Click to collapse
because magisk init is not starting on a patched image. have no sign on magisk in the any of the logs.
the issue is posted on magisk github issue tracker. no solution as of yet.
mrmazak said:
because magisk init is not starting on a patched image. have no sign on magisk in the any of the logs.
the issue is posted on magisk github issue tracker. no solution as of yet.
Click to expand...
Click to collapse
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
aryanhington said:
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
Click to expand...
Click to collapse
different brand, so built differant. just like ther are redmi (xiamoi) devices with mtk, but fastboot unlock doe not work, it needs redmi app to unlock. and flash tool not work on all devices with MTK, like amazon fire device , they have mtk and do not work with fastboot unlock, or spflash.
mrmazak said:
I have been able to edit the stock /system and flash it back to phone.
--I have added adaway host file
--Removed the SIMO app
-- Removed the IGNITE adware app (dti.blu)
--Removed The Verizon Remote SIM lock app
--Removed Blu-Privacy app
--Removed Opera browser app
--Deodexed Rom (rom would not boot past splash screen without this)
Uploaded edited sysem.img to device folder listed in OP.
Flash with same instructions as How to flash GSI
--Attempting to add SU binary makes rom fail to boot. So still no stock rooted.
Maybe soon.
/
Click to expand...
Click to collapse
which steps did you take to modify the stock /system?
aryanhington said:
which steps did you take to modify the stock /system?
Click to expand...
Click to collapse
used superr script to unpack stock super.img and continued to extract system.img
manually went through the extracted system/system/app folder and deleated the aps I did not want (adware// bloate)
used the rom tools option / deodex
then repacked the system.img
aryanhington said:
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
Click to expand...
Click to collapse
This is not entirely true.
Many Umidigi phones have been upgraded from 9 to 10. So the partitions would be very similar and considerably easy to root.
But for new phones coming with 10 the story changes. Read the last pages of your link's article. In addition, I know why and effect on Umidigi Power 3 still has limitations on root.
So this BLU G90 is not very different and depends on a lot of experimentation and tests. I believe that the OP is doing a great job mainly taking everything to github and trying to compile the kernel and firmware.
DragonPitbull said:
This is not entirely true.
Many Umidigi phones have been upgraded from 9 to 10. So the partitions would be very similar and considerably easy to root.
But for new phones coming with 10 the story changes. Read the last pages of your link's article. In addition, I know why and effect on Umidigi Power 3 still has limitations on root.
So this BLU G90 is not very different and depends on a lot of experimentation and tests. I believe that the OP is doing a great job mainly taking everything to github and trying to compile the kernel and firmware.
Click to expand...
Click to collapse
can you elaborate what you mean by this?
{
"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.
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.
IntroductionROG Phone 1 is no longer receiving any update since android 9 and no custom rom were made, which is sad since s845 is still a well performed CPU even now. However, by the help of Project Treble, we're able to install the latest android 12 (and so on) on this device.
The guide requires some basic knowledges of using SDK Platform Tools and recovery. But feel free to ask if you don't understand anything.
Hardware support
ComponentCommentCameraWorksSpeaker / MicWorksBluetoothWorks** (Bluetooth in call, all Bluetooth codec supported by the hardware) *(No A2DP)
(Update: All bluetooth functions was now fixed on A13 and above)WiFiWorksSIM / Mobile Data / VoiceWorksVoLTEUnknownFingerprintWorks (see "workarounds and recommendations" to enable fingerprint wakeup)NFCWorksOffline ChargingBroken90Hz Refresh RateWorksAuto-brightnessWorks (May depend on the Rom)Proximity sensorWorksVibrationBrokenRGB backlight on the logoWorks* (Basic functions with an app on google play) *(Will need to set the light again whenever restart the phone)HDR content playbackBroken (Have some wired lines on the screen)
Steps to installWe have 2 ways to install, either through Fastboot or with TWRP. For data safety, I do not recommend break the force encryption whatsoever.
Make sure to Unlock Bootloader before proceeding any further!
A. Install through fastboot:
1. Extract vbmeta.img from the offical rom you're running.
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".3. Flash the gsi you choose in fastboot. Do "fastboot flash system (system image name.img)" .4. Reboot to offical recovery and do a factory reset.5. You are good to go!
If you wish to use Magisk (I recommend Lygisk over Magisk since these gsi are force encryped), patch the boot image extract from the offical rom and flash it through Fastboot.
You can also boot to TWRP without flash it onto the device and use adb sideload to install zips, not recommend if you don't know what I'm talking about!
B. Install through TWRP:
1. Extract vbmeta.img from the offical rom you're running.
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".3. Flash the TWRP(attached) in fastboot. Do "fastboot flash boot twrp-3.4.0-0-Z01Q-16.0410.2003.24.img" .4. Reboot to TWRP. Do "fastboot oem reboot-recovery".5. Format data, cache and system parition in recovery.6. Flash the gsi you choose in recovery. (flash the "image" into "system partition").7. Flash any modification zips now.8. (Optional) Flash "disforsenc_daisy__zero.zip"(attached) in TWRP to disable force encryption.
It is not recommend to do this step if you really care about your data safety. If someone get your phone, they will be able to access all the files.
9. You are good to go!
You can still use adb sideload to install zips(and lots of other functions) without disable force encryption. So it's really not recommend to disable it.
Workarounds and Recommendations
To fix Bluetooth not opening or other Bluetooth related issue, refer to this guide I made. You will need Magisk to enable Aptx. This should NOT be needed anymore, since A13 builds have fix this.
Recommend to use this Gcam. It can utilize all the camera moudules and it's stable.
If you have any problem with mobile network/phone call, try to install and enable the ims apk in "phh/IMS features".
Most builds based on phh's build(which were listed on the wiki page) have a working safetynet, and the Universal Safetynet Fix will work with Magisk installed.
However some of them are still broken. So make sure the safety net is working without Magisk, then install Magisk.
RGB backlight of the ROG logo in the back can be control with this app found in google play. It's not made for this device, but basic functions will work.
My personal recommendation of gsi is crDroid maintain by Nazim. It have working safetynet and lots of customizable features I like. (Especially it can get rid of the search bar and at a glance which I HATE A LOT)
If you do want to enable fingerprint sensor while screen is off, set these two props using adb.
Code:
persist.asus.fp.wakeup=true
If you do want to use bottom usb port rather than the one on the side, set this prop. Also, to go back to the bottom one, set it to a600000.dwc3 .
Code:
persist.vendor.usb.controller.default=a800000.dwc3
If you do want to use double tab to wake, enable related settings in the GSI you use (also settings in "phh treble settings") if needed, and set this prop.
Code:
persist.asus.dclick=1
CreditsRocky7842xspx for testing the device with meNumerous people and threads on the forum for some workaround or inspiration
And all the other devs for creating these wonderful modules/ROMs
reserved
whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??
Dj.GriM said:
whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??
Click to expand...
Click to collapse
arm64 versions are all fine.
I got a rog phone 1 for a little more than a year now or so, its nice to see that we can at least have a update even if its not oficial. Im getting tyred of the same look of the UI and the aod, my god the stock ones are horrible but if i use another app for the aod it just drains the battery so fk quick. I will give a try to the pixel experience gsi
Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!
Dj.GriM said:
Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!
Click to expand...
Click to collapse
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob
Dj.GriM said:
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob
Click to expand...
Click to collapse
First of all, since the system partition on this phone is designed for android 8/9, it didn't leave much spare space. So a lot of highly modified gsi is too big for the phone. If you wish to flash them, you'll need to follow along this guide to resize partitions (tested and work).
As for the lygisk (magisk) part, take the boot image of the stock ROM you were running (the exact same version is recommended), and use the app to patch the boot.img.
Or if you have installed TWRP, simply flash the zip file through TWRP. If it's encrypted, flash it through adb sideload and it'll be fine too.
does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.
edzraaa said:
does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.
Click to expand...
Click to collapse
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.
Rocky7842 said:
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.
Click to expand...
Click to collapse
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it
edzraaa said:
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it
Click to expand...
Click to collapse
There are crDroid 9 A13 builds maintain by Nazim.
I'd recommend you to try different ROMs and versions to see which one serve you the best.
i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?
edzraaa said:
i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?
Click to expand...
Click to collapse
Welp, i think i F'd it up . Do i need to do the vbmeta.img everytime? And im not sure what to do now. Changing back to partition A stuck on ROG loading. Since i f'd up i might play around and see what i can do.
UPDATE: I got it to work finally. Flashed EVERYTHING back to "WW-16.0420.2009.39" payload.bin incase you got an error and get stucked (bootloop, wont boot). THEN follow the steps above WITH NO MISTAKES!
I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore
Yusop said:
I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore
Click to expand...
Click to collapse
That is the only way AFAIK. Try to contact Asus for help.
{
"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"
}
Requirements
Android 10 firmware for your device:
Redmi 9C/9C NFC angelica: LINK.
Angelica
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-xiaomi_angelica-api29-armhf-nightly_XXXXXXXX.zip
Installation
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
Notes
The default password is 1234.
List of working things can be found at https://github.com/droidian-mt6765/device-page
Bugs
Encryption is not supported.
Mobile data needs an APN to be set up from Settings -> Mobile -> Access Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or receiving phone calls. Toggle Mobile Data from the settings off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strenght is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Mobile hotspot does not work.
Final notes
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Attached images are from different devices but the interface looks and acts the same.
will it work on redmi 9c nfc ?
skrepka287 said:
will it work on redmi 9c nfc ?
Click to expand...
Click to collapse
Not tested
FakeShell said:
Not tested
Click to expand...
Click to collapse
Ok
It looks very promising. Isn't this something similar to Ubuntu Touch? I'd love to set this rom as my daily driver, but the bug list and its seriousness is way too much for a daily driver phone. I will, however, try it as a tester. Nice work though!
i trying it on my device rn, will give some responses for the system later.
<edit>
i just already install it on my device i trying the wifi is working perfectly and can play youtube video (via firefox) normally at 320p resolution (sorry but i just doing some slight test here.)
the DE just slower (remember, this is a freshly ported linux to for this device / Redmi 9C angelica)
but the main problem is when i try to lock the phone as usual, the display not showing anything. then forcing the phone for rebooting it sometime not help, just showing a white blank screen but the device gives a response when i pressing volume buttons (except if the device stuck at redmi logo), and i can look around for errors / problems (maybe) using "dmesg -w" command from ssh via putty.
i attach some photos where the device (under laptop's display) stuck at blank white display after reboot, and the device can comunicate via putty (the usb connection managed to be an RNDIS device when connected to the laptop)
Hanhan.i7 said:
i trying it on my device rn, will give some responses for the system later.
<edit>
i just already install it on my device i trying the wifi is working perfectly and can play youtube video (via firefox) normally at 320p resolution (sorry but i just doing some slight test here.)
the DE just slower (remember, this is a freshly ported linux to for this device / Redmi 9C angelica)
but the main problem is when i try to lock the phone as usual, the display not showing anything. then forcing the phone for rebooting it sometime not help, just showing a white blank screen but the device gives a response when i pressing volume buttons (except if the device stuck at redmi logo), and i can look around for errors / problems (maybe) using "dmesg -w" command from ssh via putty.
i attach some photos where the device (under laptop's display) stuck at blank white display after reboot, and the device can comunicate via putty (the usb connection managed to be an RNDIS device when connected to the laptop)
Click to expand...
Click to collapse
This is a known issue with droidian on MTK devices
Screen touching and power button not work on Dandelion · Issue #1 · droidian-mt6765/adaptation-droidian-garden
Hi @FakeShell: Thanks for your porting Droidian to Redmi 9A (Dandelion), is amzing! I followed the guide and got it running successfully! I'm having some problems with the touch screen and power bu...
github.com
skrepka287 said:
will it work on redmi 9c nfc ?
Click to expand...
Click to collapse
hello i doing exacly like in solution but it wont boot ;/ dont work on redmi 9c NFC Angelican
Not tested on angelican
only dandelion and angelica
FakeShell said:
View attachment 5665903Requirements
Android 10 firmware for your device:
Redmi 9A dandelion: LINK.
Redmi 9C angelica: LINK.
Dandelion
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Angelica
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Dandelion installation
Flash boot-dandelion.img: fastboot flash boot boot-dandelion.img.
Flash dtbo-dandelion.img: fastboot flash dtbo dtbo-dandelion.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-dandelion.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Angelica installation
Flash boot-angelica.img: fastboot flash boot boot-angelica.img.
Flash dtbo-angelica.img: fastboot flash dtbo dtbo-angelica.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Notes
The default password is 1234.
Xiaomi has not updated their kernel source tree and as a result some models of 9A and 9C have non functional display panels with our kernel.
Droidian GSIs are experimental! Bugs and missing features are expected.
List of working things can be found at https://garden.bardia.tech
Bugs
Mobile data needs an APN to be set up from Settings -> Mobile -> Acess Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or recieving phone calls. Toggle Mobile Data from the settins off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strengh is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid which is currently not available on angelica and dandelion.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Just like bluetooth, hotspot does not work from settings either and has to be used from a GUI application (such as the default advanced network app) or from terminal
Flashlight can be used via the desktop icons only.
Final notes
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Click to expand...
Click to collapse
Hello
I can't get the OS to work on my device. Please help.
Device Name: Xiaomi Redmi 9C Angelica prep
Initial Process Completed
- Switched device to developer mode
- Rooted device
- Fastbooted device
- Downloaded and setup installation kit/packages
Commands and Results
>fastboot flash boot boot-angelica.img
Sending 'boot' (25000 KB) OKAY [ 0.692s]
Writing 'boot' OKAY [ 0.326s]
Finished. Total time: 1.130s
>fastboot flash dtbo dtbo-angelica.img
Sending 'dtbo' (115 KB) OKAY [ 0.009s]
Writing 'dtbo' OKAY [ 0.006s]
Finished. Total time: 0.019s
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.014s
>fastboot flash recovery OrangeFox-R11-garden-droidian.img
Sending 'recovery' (65536 KB) OKAY [ 1.962s]
Writing 'recovery' OKAY [ 0.846s]
Finished. Total time: 2.813s
>fastboot format:ext4 userdata
Warning: userdata type is f2fs, but ext4 was requested for formatting.
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
>fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.113s]
Finished. Total time: 0.117s
I booted into recovery. Device booted OrangeFox successfully.
I initiated sideload.
>adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip
serving: 'droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip' (~38%) adb: failed to read command: No error
Device booted up, showed Redmi logo. A day later ther device is still at the Redmi logo.
--- sideload fails a 38% everytime. Even if I use the arm64 droidian image.
--- tried the alternative method. It doesn't work as well.
Please assist anyone. If you require logs or details, let me know where to locate them or how to generate them and I will post them.
MarvinG_88 said:
Hello
I can't get the OS to work on my device. Please help.
Device Name: Xiaomi Redmi 9C Angelica prep
Initial Process Completed
- Switched device to developer mode
- Rooted device
- Fastbooted device
- Downloaded and setup installation kit/packages
Commands and Results
>fastboot flash boot boot-angelica.img
Sending 'boot' (25000 KB) OKAY [ 0.692s]
Writing 'boot' OKAY [ 0.326s]
Finished. Total time: 1.130s
>fastboot flash dtbo dtbo-angelica.img
Sending 'dtbo' (115 KB) OKAY [ 0.009s]
Writing 'dtbo' OKAY [ 0.006s]
Finished. Total time: 0.019s
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.014s
>fastboot flash recovery OrangeFox-R11-garden-droidian.img
Sending 'recovery' (65536 KB) OKAY [ 1.962s]
Writing 'recovery' OKAY [ 0.846s]
Finished. Total time: 2.813s
>fastboot format:ext4 userdata
Warning: userdata type is f2fs, but ext4 was requested for formatting.
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
>fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.113s]
Finished. Total time: 0.117s
I booted into recovery. Device booted OrangeFox successfully.
I initiated sideload.
>adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip
serving: 'droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip' (~38%) adb: failed to read command: No error
Device booted up, showed Redmi logo. A day later ther device is still at the Redmi logo.
--- sideload fails a 38% everytime. Even if I use the arm64 droidian image.
--- tried the alternative method. It doesn't work as well.
Please assist anyone. If you require logs or details, let me know where to locate them or how to generate them and I will post them.
Click to expand...
Click to collapse
hey
try another recovery such as pbrp. also make sure you use armhf and not arm64 and it must be api29 not api30 (look in the image name)
make sure to also reflash stock a10 before even starting the process
FakeShell said:
hey
try another recovery such as pbrp. also make sure you use armhf and not arm64 and it must be api29 not api30 (look in the image name)
make sure to also reflash stock a10 before even starting the process
Click to expand...
Click to collapse
pbrp worked . Thanks for the guidance!
Hi, I have successfully installed Droidian on my device but I have run on these issues:
- Landscape is broken (it turns on landscape but register touches in wrong positions) and because of that I have to use portrait all times
- Sim card not recognized, so no calls and texts
- Sometimes scrolling is slow on some apps
What I need to do to solve these problems? I really want to use real Linux on my phone. It is a Redmi 9C NFC
Mario6w891 said:
Hi, I have successfully installed Droidian on my device but I have run on these issues:
- Landscape is broken (it turns on landscape but register touches in wrong positions) and because of that I have to use portrait all times
- Sim card not recognized, so no calls and texts
- Sometimes scrolling is slow on some apps
What I need to do to solve these problems? I really want to use real Linux on my phone
Click to expand...
Click to collapse
Landscape issue is present in a few other mediatek devices as well (there was also a touch issue on all mediateks which we fixed) no fix for that yet
Check which slot your simcard is in and change it in /etc/ofono/ril_subscription.conf
change the values ril_0 to ril_1 and slot1 to slot2
systemctl restart ofono ofono2mm
you also have to set your apn settings manually in gnome control center/settings app
its a low end device and mediateks were always in the slower end on linux so you will experience slow downs nothing we can do
Thank you, Sim works now! But all of my contacts are gone now. Shouldn't I ejected the Sim card before flashing the OS?
Also I do not know how to set Access Point settings :/
Mario6w891 said:
Thank you, Sim works now! But all of my contacts are gone now. Shouldn't I ejected the Sim card before flashing the OS?
Also I do not know how to set Access Point settings :/
Click to expand...
Click to collapse
You can find your carriers APN in their website or by just searching the web
Thank you again, but I switched my OS due to missing features I needed like WhatsApp.