Related
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
Bugs :
1. Reboot->Recovery doesn't work as required. Reboots to system instead.
Please do report any, if found.
Click to expand...
Click to collapse
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt of your phone.
5.Check only Recovery, Preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware > Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11. Disconnect your phone.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : https://github.com/neomanu/android_device_micromax_a116-twrp
Credits :
@suhas.holla (for original device tree)
NO PORT REQUESTS
NO QUOTING THE WHOLE OP
You will be reported!
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-29
Reserved
Changelog :
2.8.3.0u1 :
- Added F2FS tools. Can be used to format filesystems to F2FS.
- Removed SuperSU (to fit into partition)
2.8.3.0 :
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
2.8.2.0 :
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
2.8.1.0 :
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1 :
- Fix a bug that caused weird graphics and touch issues
2.8.0.0 :
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
2.7.1.0 :
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
Reserved
Awsome work bro.. :thumbup::thumbup:
Thank you so much.. Downloading
good work bro!!:good::good:
thanks for compiling this !!
Can we use this to flash Android 5.0.1 by kashifmin ?? !!
and anyway to solve reboot --> recovery problem ! ?
Awsome work once again MAN!!!!! Really, very greatful to you.... Just one more request to you...... Can you just compile a new kernel for our device from this Source (a tweaked kernel) so that we can have it on cm11.... because the kernel used in cm for now is not tweaked and a bit poor performance... i would have done that work but busy with my exams... so if you can please .. or i would be back within few weeks....
Once AGAIN , NICE WORK!! Keep it UP!!
Regards
Andy
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
vaas kr said:
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
Click to expand...
Click to collapse
Sure... you can with mobileuncle tools... (AND RECOVERY(S) ARE MEANT FOR FLASHING )
Regards
Andy
neomanu said:
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
Bugs :
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt of your phone.
5.Check only Recovery, Preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware > Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11. Disconnect your phone.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : --to be updated--
Credits :
@suhas.holla (for original device tree)
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-26
Click to expand...
Click to collapse
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
Click to expand...
Click to collapse
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?....
Click to expand...
Click to collapse
neomanu said:
No, you don't. .....
Click to expand...
Click to collapse
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
m0han said:
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
Click to expand...
Click to collapse
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
neomanu said:
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
Click to expand...
Click to collapse
your twrp v2.8.3.0u1 seems to work ok :good:.backup got saved in /emmc/TWRP/BACKUPS/Canvas_HD. how about shortening that to A116?
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
m0han said:
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
Click to expand...
Click to collapse
The font used is the new default in TWRP, from v2.8.1.0.
Refer to this commit.
All you need to do is to unpack the ramdisk, add RobotoCondensed-Regular.ttf to /res/fonts/ and change the following in /res/ui.xml according to the required resolution.
Repack and you have the font.
neomanu said:
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
Click to expand...
Click to collapse
In my twrp 2.7.0.0 it shows wipe option with dalvik,cache,factory reset..in single swipe.. What should i do to separate them..
Sent from my Micromax A116
jam884 said:
....What should i do to separate them....
Click to expand...
Click to collapse
try clicking advanced wipe and choosing what you need....
m0han said:
try clicking advanced wipe and choosing what you need....
Click to expand...
Click to collapse
Thanx a lot friend...
Sent from my Micromax A116
@neomanu
Thanks for TWRP_2.8.3.0
I have one issue some time stuck when flash zip on TWRP_2.8.3.0u1-NK
When flash same zip in preview recovery (TWRP 2.8.0.0 hyperion70) it work fine
any news on an update to fix the boot to recovery option ??
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy Tab 4 7.0 LTE (T235/T235Y).
DO NOT USE IT FOR T230(NU)/T231 OR YOU WILL BRICK YOUR DEVICE
Although T235 and T230(NU)/T231 (T230:WiFi / T231:3G) share the "Galaxy Tab 4 7.0" name they are not related in terms of hardware due to the different SoCs used (Samsung Exynos3470 vs. Marvell PXA1088).
Hence please do not ask for support or ROMs for the T230(NU)/T231.
Working features
Receiving and making calls
Hardware sensors (Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
MTP storage
GPS
USB-OTG (Mass-Storage, Keyboard, Mouse working, USB-Audio untested)
Camera (pictures+video: Back+Front)
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Tab 4 7.0 SM-T235 and SM-T235Y (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v1.85
TWRP 2.8.7.0 recovery image [09/08/2015] (AndroidFileHost Mirror)
CM 12.1 ROM (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see links above). Otherwise TWRP might not be able to flash the ROM.
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
09/08/2015:
*Update kernel to T235XXU1AOD1
*Synchronize with newest CM 12.1 sources (contains stagefright patches)
*Fixed black screen on minimal brightness
12/07/2015:
* Charging animation in standby-mode fixed
11/07/2015:
* Update to newest CyanogenMod sources (LMY48G)
* Left touchkey working now (configured as App-Switch button)
* Camera Preview working (saving a picture might still crash)
30/06/2015:
* Image sizes reduced to fix "unable to mount /system" problems
28/06/2015:
* Initial test-build
This section is for developers:
A README file with build instructions can be found here:
https://github.com/cm-3470/patcher_degaslte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_degaslte
https://github.com/cm-3470/android_vendor_samsung_degaslte
https://github.com/cm-3470/android_kernel_samsung_degaslte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
XDA:DevDB Information
[T235][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for T235(Y) [Alpha 09/08/2015], ROM for the Samsung Galaxy Tab 4
Contributors
hennymcc
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 09/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-06-29
Last Updated 2015-09-24
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
any marvell devices will not work with this or any other custom rom.
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
this is an exynos device not marvell
and now for some reason i cant restore the backup i made
i tryed restorng the backup with twrp 2.8.6.0 recovery from this thread and the 2.8.1.0 from the other.
one gives boot animation loop and the other is stuck at boot
hennymcc said:
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Click to expand...
Click to collapse
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
thisisapoorusernamechoice said:
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
Click to expand...
Click to collapse
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
sub77 said:
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
Click to expand...
Click to collapse
The default selinux setting is enforced. As the selinux configuration files are not complete, Android would not boot.
Setting androidboot.selinux=permissive might work, but when I tested this setting on my S5 mini, it was rather unstable for some reason.
interstellar22 said:
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
Click to expand...
Click to collapse
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
interstellar22 said:
this is an exynos device not marvell
Click to expand...
Click to collapse
T235 and T235Y definitely use Exynos 3470 SoCs. Here an extract from the T235Y default.prop:
Code:
ro.product.model=SM-T235Y
ro.product.name=degasltezt
ro.product.device=degaslte
ro.product.board=universal3470
ro.chipname=exynos3470
The default.prop file of the T235 is similar, only that the product name is degasltexx.
Marvell's PXA1088 SoC is used in the T230/NU which is the non-LTE (WiFi-only) variant of the Tab 4 7.0.
Marvell's PXA1088 and Samsung's Exynos3470 are totally different and have nothing in common (except an ARM core), the same applies to Qualcomm's Snapdragon. There are many websites that mention wrong SoC names as Samsung's naming scheme is rather confusing.
The same applies to the S5 Mini: G800F/M/Y -> Exynos3470, G800H -> Qualcomm Snapdragon.
corneo said:
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
Click to expand...
Click to collapse
Code:
Info: format successful
I:mkfs.f2fs -t 1 /dev/block/mmcblk0p18 process ended with RC=0
Done.
Why was the system partition formatted with f2fs? The default file system is ext4.
The TWRP partition table is hardcoded to ext4 so that's probably the reason for these lines:
Code:
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p18', current file system: 'ext4'
Could you reformat it with ext4?
interstellar22 said:
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
Click to expand...
Click to collapse
Did you flash the stock ROM with Odin?
And afterwards wipe the data partition and then the cache with the _stock_ recovery (as TWRP is not available after flashing the stock ROM)?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
hennymcc said:
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
Click to expand...
Click to collapse
i've created the log in recovery and copied it to sd.
now i flashed the tab again with odin and try it again. same issue...
Gesendet von meinem One M8
i managed to get the original firmware back with odin
could it be that the system.new.dat file is corrupted ?
i had formated system with ext4 then did the update and was still getting unable to mount /system afterwards
so most probably the system.new.dat file has some problems or i have no idea why i cant mount /system afterwards
Maybe it is caused by wrong BOARD_...IMAGE_PARTITION_SIZE values in BoardConfig.mk.
Could you please post the contents of /proc/mounts and /proc/partitions:
Code:
cat /proc/mounts
cat /proc/partitions
The above should be performed from the stock ROM. The device must be rooted.
Hmm, the problem might be here:
Code:
Patching system image unconditionally...
blockimg version is 2
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
588800 * 4096 = 2411724800 bytes (2,2GB)
This is the value of the BoardConfig.mk taken from the S5 Mini (BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2411724800).
But the system partition is only 2233466880 bytes:
Code:
/system | /dev/block/mmcblk0p18 | Size: 2096MB Used: 1828MB Free: 268MB Backup Size: 1828MB
Code:
I:wipe_path '/system'
Formatting System using make_ext4fs function.
Creating filesystem with parameters:
Size: 2233466880
The system.img itself is only 500MB in size. So I guess reducing the image size should fix the problem.
An updated ROM is available. The image sizes have been reduced. I hope this fixes the problems with the system-partition.
Also use the new TWRP recovery as the partition sizes might be hardcoded in the old one.
good news! new recovery and system image works! very smooth so far, searching for bugs now. the only one i found are the extended settings option. it doesn't work but thats no problem for me. thank you very much!
Gesendet von meinem One M8
[GUIDE/TUTORIAL] Asus Transformer Prime to Android 7.1/LineageOS 14.1
[GUIDE/TUTORIAL/HOWTO] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat/LineageOS 14.1
This detailed step-by-step guide helps you transform your Asus Transformer Prime with Android 4.1.1 to a powerful one with Android 7.1 (Nougat).
### I'll make a few comments like this, read these or you may miss something.
### The Asus Transformer Prime codename is TF201.
Try to prefer USB2 connections, but USB3 works fine too.
CHANGELOG
v11. Improvemed unlock section
v10. Updated links
v9. ROM v39 and removed obsolete info
v8. ROM v35 and enhenced link for OpenGapps
v7. Refresh pack for ROM v32 and TWRP recovery 3.2.3-0
v6. Google Play certification
v5. Updated djibe pack for easier install (kang recovery 3.1.0-1, SuperSU, drivers if fails at Step 6) + switched to v26 of Katkiss
v4. TWRP Kang recovery 3.1.0-1
v3. Tweaks and walkthrough
v2. Android 7, many hints added for more accurate tutorial
v1. Initial release
BEFORE STARTING
Make sure you have the latest official updates for your tab :
In Android, go to Settings -> About tablet -> System Update
### Make sure you read all comments starting by ###
To make sure your tab is the correct model, go to Settings -> About tablet.
The details below are listed :
• Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot)
bootloader V 10.4.2.18
### To verify bootloader version, shut down tab. Then hold Power + Volume- for 3 seconds and release.
### You are in bootloader : on top left corner is written Android (...) epad-10.4.2.18.
### To quit bootloader, press Volume- to go over the Android icon, then Volume+ to confirm.
### If not V 10.4.2.18, check official updates for your tab before starting this tutorial
### or check more info on Asus support web page and download the version identical to the Firmware Description written top left corner of the bootloader
### Asus support is here : https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_BIOS/
• GPS 7.9.13
• Wi-Fi 7.1.0.24
• BT 10.33
• Camera FT201-0x9900
• Ecran MXT-2.0 build-170
• Kernel 3.1.10.00002-9599d0cf [email protected]
o #1 SMP PREEMPT Thui Nov 22:12:01 CST 2012
• Build nr JR003C.WW_epad-10.4.2.18-20121122
Still in Settings -> About tablet, tap 7 times on build number to unlock Developer menu.
0) BACKUP YOUR DATA
Backup SMS, photos, contacts before going any further (ex: use the backupyourmobile app).
Check that backup is located on microSD card.
Then copy the backup on your PC.
1) DOWNLOAD
djibe Transformer Prime pack v2: http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
+ ROM KatKiss Nougat v39 Android 7.1
XDA Thread: https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Download here: https://downloads.timduru.org/android/tf201/K.A.T/KatKiss/7.x/dev/ or https://www.androidfilehost.com/?fid=14943124697586357425
+ OpenGapps ARM 7.1 ARM Pico (NO OTHER DISTRIB THAT ARM PICO please): https://opengapps.org/?arch=arm&api=7.1&variant=pico
You must have a microSD card (FAT32 format), copy the zip files from Katkiss ROM, OpenGapps and SuperSU.
Then insert it in the tab.
2) INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual.
- Windows Vista/Windows 7 :
Go to folder /Universal Naked Drivers 0.72 you unziped earlier (on Windows desktop).
Select file android_apxusb.inf, then right click -> Install.
Force driver installation and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Then plug tablet to PC (USB2 port) to end driver installation.
### If it fails to install you may try using Windows device manager :
### In Windows Device Manager menu -> Right-click on Asus Android Device -> Update Driver Software -> Let me pick -> Have disk -> Browse to the .inf file and install BOTH .inf files.
### See this post if still doesn't work : https://forum.xda-developers.com/showpost.php?p=75240547&postcount=166
- For Linux, I have no experience. Every tools should be here : https://github.com/AndroidRoot/androidroot.github.io/tree/master/download
- Copy the UnLock_Device_App in tablet's internal memory
Tab should normaly be seen in Windows explorer as TF201.
Check MTP file transfer protocol is active on the tab.
Copy the UnLock_Device_App_V6.apk in the root folder of the tab.
3) UNLOCK BOOTLOADER OF ASUS TF201
Tablet must be fully charged to 100 %.
In Android, go to Settings -> Security -> Check Unknown Sources.
Then Settings -> Developer options -> Enable USB debugging.
Launch the preinstalled app File Manager to install UnLock_Device_App_V6.apk.
### If it fails to install, delete your Google Account. Go to Settings -> Accounts. Delete the Google Account.
Launch the UnlockApp.
Accept User agreements. Your warranty is now void.
Accept and click to unlock the tab,
let the tab restart and work.
After reboot , "This device is unlocked" is written on top left screen.
### It probably won't work that simple.
### The solution is here, but I didn't have to test it: https://forum.xda-developers.com/t/howto-unlock-tf700t-in-2020.4157143/post-85255809
4) PREVENT BRICK : NVFlash
This step is optionnal but highly higly highly recommended, your tab will never be bricked after it !!!
1ST PART --------------------
Tab shut down, press Power + Volume- for 3 seconds and release, you are in the bootloader.
Use Volume- to move cursor over the USB logo, confirm with Volume+, you are in the fastboot mode.
Connect Transformer Prime to PC.
Select the "Files" folder you you unziped earlier.
Do Shift + right click on folder -> Open a Command Line.
Type:
Code:
fastboot -i 0x0b05 flash recovery flatline_tf201.img
and confirm with Enter.
### If you get error "fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program",
### type the command starting with a dot :
Code:
.\fastboot -i 0x0b05 flash recovery flatline_tf201.img
A blue bar appears on the tablet indicating flash success.
Wait until command line reports the flashing success.
then type :
Code:
fastboot reboot-bootloader
and confirm with Enter.
This time in Bootloader, use Volume- to select RCK (recovery) and confirm with Volume+.
You are in the flatline recovery.
Use Volume- to go to Advances, confirm with Power.
then wheelie, confirm (Power button),
then i accept the above statement (Power button),
then Step 1: flash AndroidRoot BL, tab powers down.
Start tab with Power only,
let the blue bar fill completly and start Android normally.
Once in Android, shut it down.
Start tab in bootloader Mode again (still Power + Volume- ;-) ), go to recovery again (RCK).
Connect tab to PC.
In recovery, return to Advanced -> wheelie then select Step 2: generate wheelie blobs.
It generates the backup files !!!
Open another Windows command prompt for fastboot mode and type :
Code:
adb pull /data/media/AndroidRoot
.
Backup files are stored in your "Files" folder. Make another backup of these files in a safe place.
(7 files are saved : recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log)
### If
Code:
adb pull /data/media/AndroidRoot
doesn't work : start Android normally, connect to PC as multimedia storage and
### navigate to My Computer -> Transformer Prime TF201 -> Internal Memory -> Android Root and copy the files in here.
Shut down tab.
2ND PART, NvFlash ----------------
Copy these 7 files in the folder "files/nvflash" (Another copy, in addition to the backup you made).
Connect tab to PC.
Start tab in Nvidia APX Mode : Hold Power + Volume+ for 3 seconds.
Anything happens, it's normal, screen stays black.
The tab is visible as an external drive and is called APX.
Open another Windows command prompt on the nvflash folder.
Type :
Code:
wheelie --blob blob.bin
and confirm with Enter.
If successful : the tab launches in bootloader mode and the Command prompt writes a few lines.
Type in command :
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
then :
Code:
nvflash --resume --read 14 factory-config.img
then :
Code:
nvflash --resume --read 7 unlock-token.img
You have to backup 3 new files : bricksafe.img, factory-config.img and unlock-token.img.
Copy these files in a safe storage with your blobs for future repair if needed.
### If you need to restore those backups one day, follow the tutorial of craigacgomez : https://forum.xda-developers.com/showthread.php?t=1927818
### If you have error "not enough space for GApps (error 70), follow this tutorial https://forum.xda-developers.com/showpost.php?p=73403429&postcount=137
5) RECOVERY
(Only applies to stock bootloader V 10.4.2.18).
Charge tab to 100% before continuing.
Start it in bootloader mode (Power + Volume-).
Connect it to PC.
Set the icon over the USB selection.
Confirm with Volume+; you are again in fastboot mode.
Open a command prompt on the /files folder.
Type :
Code:
fastboot devices
.
if the serial number is written, tab is well connected.
### Or check driver installation if not.
then type :
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
and wait for the "finished" success message,
then type :
Code:
fastboot -i 0x0b05 reboot-bootloader
,
and confirm with Volume+ to get into RCK (recovery, again), it is now TWRP 2.6.3.0.
6) BOOTLOADER
Once in TWRP recovery, type in command prompt :
Code:
adb devices
-> terminal returns : 012345678ABCDEF recovery.
Type :
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now on the tab, still in TWRP recovery, go to Install then click on HairyBean_Bootloader_TWRP2.5.zip
(file is in Internal memory, in folder /sdcard).
Swype to the right to confirm flashing, wait until Successful message appears.
Now click Reboot System and Do Not Install when SuperSU is proposed.
Let the tab reboot with another blue bar. Let it work.
The tab reboots and launches the HairyBean TWRP recovery (androwook).
In Windows command prompt, type :
Code:
adb reboot-bootloader
,
tab reboots in bootloader mode and the USB icon is gone, it's perfect.
### If Windows doesn't recognize your tab, or recognizes it as VID_0B05&PID_4C83, try the fix from XTCrefugee included in my pack : folder \Drivers android_winusb if hairybeen TWRP not recognized
### Install this .inf driver file as you did earlier
###
### YOUR BOOTLOADER IS NOW IN 10.6.1.27.1 VERSION
###
In command prompt, type :
Code:
fastboot -i 0x0b05 flash recovery twrp-3.2.3-0_KANG-tf201t.img
Wait till blue bar completes.
When finished message appears in terminal,
type :
Code:
fastboot -i 0x0b05 reboot-bootloader
, tab reboots.
Now enter in new recovery with Volume+ : recovery is now TWRP Kang 3.2.3-0 Recovery
### Your tablet will be seen by Windows as a TF201T now !
7) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Go to Wipe -> Advanced Wipe, select only the Data partition,
then tap on Repair or Change File System -> Change File System and tap on F2FS.
Swype to force partition system as F2FS. Wait till done prompts. Then go back to Advanced Wipe.
### If TWRP sends you this log in red : E:Failed to get default contexts and file node for storage files,
### Reboot to TWRP recovery again before going any further.
Repeat the operation of F2FS conversion for the Cache partition.
8) INSTALL ANDROID NOUGAT 7.1
Still on TWRP Advanced Wipe menu,
select Dalvik Cache, System, Cache, Data AND Internal Storage and Swype to force cleanup. Wait till completion.
Back to Home screen, tap Install, then Storage: Internal Storage and change it to microSD card -> OK.
Select KatKiss* .zip, and Add More Zips,
select SuperSU.zip, and Add More Zips,
then open_gapps-arm-7.1-pico*.zip and Swype to force install. Be patient.
### Make sure once again you have the Pico Gapps version or system will hang.
### If TWRP crashes to its Home screen, you microSD might be in cause. Find another one, and then try to install Zips 1 by 1.
### If error installing Gapps, see this thread : https://forum.xda-developers.com/android/help/fix-error-70-install-gapps-t3311779
When done prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Go back to Home when done.
Then Reboot -> System.
Let the tab start during at least 15 minutes.
9) START ANDROID N 7.1
### During first setup, manually toggle Wifi ON using the Wifi icon on the bottom right corner. If you don't, the setup app will crash.
### It can crash a few times before turning on, keep activating it.
Configure Android as you like.
In Settings -> Mediascanner filters, uncheck Scan.
In Settings -> About, tap 7 times on build number, it unlocks the Options for developers in Settings.
Enter this new menu.
In the Hardware acceleration, try both GPU rendering active and disabled.
I can't figure which one works best. Share with us.
Good to know about this ROM:
Bluetooth requires to be turned on twice before it turns on.
A few things including the navbar buttons can be tweaked in Settings => System UI Tuner.
AND more on XDA Katkiss thread (See DOWNLOAD CHAPTER ABOVE)
10) ROOT
Open app SuperSU to see more details about the Root access.
After ROM first launch, go to Settings -> About tablet.
Tap 7 times on build number, it will unlock the Developer menu.
In the developer menu -> Try to turn ON and OFF the Force GPU option and tell me what is the faster one.
(I think I prefer when GPU forcing is disabled).
11) PERFORMANCES AND OVERCLOCK
Source of benchmarks: http://androidmodguide.blogspot.fr/p/blog-page.html
Install Kernel Adiutor app from Google Play Store.
Launch app and go to Settings -> Kernel -> CPU :
Check Apply on boot and change CPU Maximum Frequency to 1600 or 1700 Mhz, set Governor to Interactive
Now Kernel -> I/O Scheduler :
Check Apply on boot and set Scheduler to Zen, then Readahead to 1024 Ko (or 2048. Try yourself)
Now Kernel -> Various :
Check Apply on boot and set TCP congestion to Cubic (or Westwood)
12) VARIOUS FIXES
### Your tablet doesn't see the Wifi ? (that is on Channel 13 by example).
Try this first : in the Wifi screen (where you see all visible networks), tap on the three-dots icon to open the menu -> Advanced wifi parameters.
Tap on the Wifi region code item to select the region : chose the corresponding region.
Now verify your Wifi network is visible.
If not, try this :
Open Kernel adiutor, Menu -> Build.prop editor.
In key search field, type wifi.
Click ro.wifi.channels -> Edit -> in the value field, set 13. Confirm with OK.
At the same time, you can set wifi.supplicant_scan_interval=180 to 180 (seconds) to reduce number of scans and reduce battery usage.
Restart tab, your wifi network should be visible again.
### Your keyboard isn't in the correct language
Go to Android Settings menu -> Languages & inputs -> Physical keyboard -> Android keyboard
Enjoy your new tab ;-)
djibe
Thanks : @timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
HorthLithperer said:
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thanks for your support. It was a tough job to explain step by step.
Took me 3 days to discover all the details.
thanks
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
yo29570 said:
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
Click to expand...
Click to collapse
Thx for feedback.
I had the same problem and used the tab factory reset.
I've updated tutorial and told to delete the Google Account.
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Woodrow256 said:
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Click to expand...
Click to collapse
Glad you liked it and tab is healthy again !
I've made tuts for Xperia Tablet Z and Samsung devices too if you are interested
Problem with step 8 - INSTALL Android 6 ROM
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
deltabert said:
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
Click to expand...
Click to collapse
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
djibe89 said:
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
Click to expand...
Click to collapse
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today (27 dec.) i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
Got the tab in APX mode again (Windows Device Manager shows Asus T. P. APX..)
So i went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
deltabert said:
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
But unfortunately i am not able to get the tab in APX mode again.
Then i skipped this en went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
Besides this, I am still worried that NvFlash might be no longer on the tab...
And i don't get the FlatLine booting with volume-up and power anymore...
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
Click to expand...
Click to collapse
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
ALDO_MAC12 said:
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
Click to expand...
Click to collapse
Hi ALDO-MAC12,
Unfortunately, i have not yet got my TF201 working. I'l wait now until djibe89 has time to react.
(When i opened his zip file i noticed he has also a France language description, and he is at the moment in France, So i guess he is a French-Canadian, on vacation in France.)
I did study the original posts from timduru and TacoNikky, but i can find no differences with the description of djibe89. Noticed there is also a Android 7 rom from timduru. But i think i should first get to manage the hole process.
For me all this is new. My tab became so horribly slow that i only sparsely used it anymore. So that's why i would like to give it a try.
BTW, i do get the tab in APX mode; with volume up and power, i get a black screen but in Windows Device Manager there shows up the Asus Transformer Prime APX ... driver.
If you're running Windows 10, you need to delete all your other android drivers, then disable the signature checking on your driver installation and install the Naked Universal driver.
Super SU wants update
Works for me on windows 10. Make sure tablet is plugged in directly and not into keyboard also. Although Super SU is now reporting an update in necessary. Is it recommended in update Super SU after installation? Btw thanks for bringing new life to my tablet!
Have you tried not to change /cache partition to f2s2. The original KatshMallow thread says:
This ROM is for TF201 and F2FS only
Convert just /data partition to F2FS
Click to expand...
Click to collapse
...
Hello all,
Thank you for thinking with me, I appreciate this very much! I will react to the suggestions given.
@lazuhrus, I think the Universal Naked Drivers 0.72 are correctly installed on my Win-10 PC. I followed the procedure for Win-10 to disable driver control. To confirm this: I am able to use fastboot from Win-10; fastboot devices gives me the serial number of the tf201.
Also the command adb devices gives me: 012345678ABCDEF recovery.
Further, when I bring the tf201 (with volume UP and power) in APX mode, I get a dark screen on the tab, but in Windows Device Manager there shows up the Android device: Asus Transformer Prime APX Interface.
So for me this seems OK. This lets me conclude that the Universal Naked Drivers 0.72 are correctly installed and working. Or am I overlooking something here?
Btw, I do this on the bare tablet, without the keyboard dock.
With volume DOWN and power, I get the tab in TWRP version 2.8.3.0.
And installing KatKiss seems to go well (see the screenshots I posted in #10 from the TWRP format and install process).
@ shaDNfro, I did change the /cache partition to f2fs, as the screenshots are showing too.
However, there is one strange thing. After the last install (post #10) when I am in TWRP and connect the tab to my PC (win10) I see in the File Explorer an entry for an ASUS Transformer Pad TF300T; while mine is an TF201!!
Picture File Explorer: https: // deltabert.stackstorage.com/s/Nj1C01jTyZ5MoWB
And in the Device Manager I see also references to the wrong tab type!
(But you can see the Asus Android Composite ADB Interface.
Picture Win10 Device Manager: https: // deltabert.stackstorage.com/s/zK2LIoAthr4jKJ7
(added spaces around // because i am as novice not (yet) able to post links)
Hopefully anyone can help me with this...
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
djibe89 said:
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
Click to expand...
Click to collapse
Thank you djibe89,
I really hope you can help me with this, I become a little desperate...
I wonder if there is something wrong with the bootloader (HairyBean_Bootloader_TWRP2.5.zip). When I boot the tab with vol-down and power I get the following bootloader info: Android cardhu-user bootloader <1.00 e> released by “WW_epad-10.4.2.15-20120917†A03
Do you know if this is correct?
OK, I put the tab in TWRP 2.8.3.0 mode.
Formatted the /Cache partition using make_ext4fs
Then I wiped Dalvik Cache, followed by /System, which formats to ext4fs.
Then format /Data, first with make_ext4fs, and when finished, I change the filesystem of /Data to f2fs. Wiped all other partitions, except Micro SDcard (not sure if this is the internal or external SDcard)
Then I installed the three .zip files. KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip and BETA-SuperSU-v2.52.zip.
I also put the MD5 checksum file of KatKiss-6.0_TF201_029.zip on the sdcard and the install procedure checks the .zip successful.
When install is done: Successful, I wiped Dalvik Cache and rebooted the tab.
But then I have the same reboot problem: First i see a blue bar for one second, then the tab boots with the ASUS splash screen at medium intensity, then switches for a moment to high intensity and back to medium intensity, and after a few seconds it reboots and it starts over again.
When I leave the tab booting for two hours, I can feel it is doing something; the backside is becoming slightly warm; processor: ~ 45°C.
The bootloader is part of HairyBeen isn't it? Could I re-install the correct HairyBean_Bootloader_TWRP2.5.zip again, by putting it on the external sdcard and selecting it from TWRP 2.8.3.0?
fastboot, adb and Nvidia APX Mode are still functioning, so there must be a solution...
Hopefully you have a good suggestion?
Kind regards, Bert
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
djibe89 said:
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
Click to expand...
Click to collapse
Hi djibe89,
I will look into the restoration option. I do have the APX backup files.
Will be continued....
Nexus 4 Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Installation
HTML:
# Before processing further we highly recommend you to use our TWRP which has support of EFS/Persist backup
# Or you might lose your IMEI/WIFI + BT mac addresses
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors.
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you using this guide to restore your phone back
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- ddaggebi for 8GB model layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 4 Repartition, Tool/Utility for the Google Nexus 4
Contributors
Clamor, sudokamikaze
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. To be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You shoud check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to discribe what you did and enclose partition.log to your post.
MAKO STOCK
Code:
21 159383552B 1040187391B 880803840B system
22 1040187392B 1627389951B 587202560B cache
MAKO MODIFIED
Code:
21 159383552B 1732247551B 1572864000B system
22 1732247552B 1994391551B 262144000B vendor
23 1994391552B 2099249151B 104857600B cache
4. If you have touchscreen problems use common instructions till you reach entering word. Than plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
5. Flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
bgoel4132 said:
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
Click to expand...
Click to collapse
Plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
ddaggebi said:
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
Click to expand...
Click to collapse
PM me, I need a partition table and I'd ask you to test if you have 8GB model.
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
cyberon said:
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
Click to expand...
Click to collapse
Sure. In PM.
OK so my nexus 4 can't transfer files to or from PC at all so if I do this and have the ROM downloaded it will wipe the ROM and the ROM would be gone and my phone would be a nice brick because I can't transfer any files to my PC like it charges with the PC but data transfer doesn't work so again would I be screwed?
@Nathan4923 correct. Usb connection and PC are mandatory
For those who downloaded repartition pack before this message is published, please redownload pack since previous version might have a problems with repartition. If repartition was already made, don't worry everything should be fine. Just use up-to-date pack.
can i return back to old partition if i want to? i hope someone would post a video tut for this one
@jluspo you can with same zip and same steps as for repartition. You didn't read first post carefully.
Clamor said:
@jluspo you can with save zip and same steps as for repartition. You didn't read first post carefully.
Click to expand...
Click to collapse
im using xda appits different layout on browser
I'm I doing it right? I still can't flash gapps
failed to mount Vendor, any suggestions ?
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are designed to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Clamor said:
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are desined to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Click to expand...
Click to collapse
Thanks for the help !
I've found that even with that error, i still succed the process
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Mato_xXx said:
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Click to expand...
Click to collapse
just read the OP carefully it already mentioned that you had to resize system after installing rom
you can do that by going to advanced wipe in twrp
**** Disclaimer: I'm not responsible if you destroy your device. Learn at your own risk!!! ****
Alright, So I am a bit Moderately skilled to Custom Development. I do not know a lot of in-depth either.
However, I do know enough to help other new beginners out.
As I continue to learn more info and details, I will update this post frequently.
Completed guide, I'm saving and typing as not to lose progress. Last Updated- 01/03/2021
Please do note, CROSS-VERIFY if the info here is correct before following it.
What is a Custom ROM?
Simply put, it is a new Operating System [OS].
People find their stock (the one you got with your phone) to be boring, or they dislike it or want more customization and optimization, lesser bloatware (useless unwanted system apps).
Thus some Developers made their own ROM (aka OS). Then others made it compatible with our phone. Sometimes this works perfectly, most of the time it doesn't. Thus Asking people how the ROM is, is always good to ask.
STABLE means almost no errors, UNSTABLE means a few/lots of errors.
OFFICIAL means the Developer in charge will keep updating it and has been granted the task officially. EOL means End Of Life, aka Developer, won't work on it anymore.
FOD means finger on display icon, FP means fingerprint sensor, SOT means screen on time or how long your battery will last.BB means Battery backup, or how long the battery will last.
Click to expand...
Click to collapse
How To Get a Custom ROM?
So, to flash (insert) a new Custom ROM, we first need to unlock the Bootloader. The Bootloader is what allows us to wipe (remove/erase) our data, and current OS and flash a different one.
Then we flash a Recovery. (A software that makes flashing and wiping and other stuff easy)
Then flash the ROM, Then (if needed) vendor+firmware, gapps, magisk.
So in k20 pro/Mi 9t pro, there are 5 vendors. Indians use Indian Vendor, Chinese users use Chinese Vendor, similarly for EEA, Russian, and Global.
In this Vendor zip file, nowadays, the firmware is included in them, so it isn't required to flash it separately.
If you are coming from miui 11 and want to flash custom ROM you don't need to flash the vendor.
If you are coming from miui 10 to custom ROM Android 10, you need to flash the miui 11 vendor along with the ROM.
Click to expand...
Click to collapse
How To Unlock Bootloader?
So, you should first update your software to the latest miui OS [current: MIUI 11].
Go to Settings > About Phone > tap on MIUI Version 7 times -> you unlock developer settings
Go to Settings > Additional Settings > Developer Options > enable (switch on) USB Debugging > OEM Unlocking > click on MI Unlock status > link account and device.
To link the account, you must first have a Xiaomi MI account. You can make this in settings, or head to https://account.xiaomi.com
Wait 7-15 days
Once 7-15 days have passed,
USING WINDOWS PC
BACKUP ALL FILES, CONTACTS, WHATSAPP, ANY APP settings (if any), AND SYNC/LINK accounts to cloud => YOU WILL LOSE EVERYTHING NOW
Now download the Mi Unlock tool onto your PC https://xiaomitools.com/mi-unlock-tool-en/
IN A SEPERATE FOLDER
Then download Platform Tools from attachments below.
Then download TWRP (team win recovery project) from https://dl.twrp.me/raphael/
Then download Orange Fox Recovery (OFRP) from https://files.orangefox.tech/OrangeFox-Stable/raphael/ and download the latest file. [Currently: OrangeFox-R-10.1_3-Stable-raphael.zip]
Then download Disable force encrypt zip file from attachments below
Then download adb drivers from https://www.xda-developers.com/what-is-adb/ version 1.4.3 onto your PC and run the application. (Follow from How do I install ADB?) (Or you can skip that and just get the file from attachments below and extract it to C drive as a separate folder directly)
Then download the ROM (links are given below)
Then download gapps (optional). from https://opengapps.org/ and select ARMx64 and PICO then the download button.
Then download Magisk (optional). from https://github.com/topjohnwu/Magisk/releases download the Latest Magisk-vXX.xx.zip file there.[Currently: Magisk-v20.4.zip]
Download the latest vendor file from the below links. (make sure it's the proper file for your device's variant.)
Vendor and firmware are both combined and included in the same zip file.
Global, EEA (Europe), China, Russia Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphael/
Indian Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphaelin/
Check my third comment to learn how to recognize which device variant is yours, and what vendor to download and flash.
NOW! GET READY!
Now, connect your device.
Use your cable included in the box (the charging wire) and connect it to your phone and PC.
Go to 'adb' folder in your C-drive, (on that address bar thing where it shows) This PC >OS(C> adb click on it and type cmd . This will open a Command prompt to that folder.
Type adb devices and on your phone tap on the authorize button that pops up when unlocked. Now type adb devices again.
you will get
Code:
List of devices attached
365278234e device
Now, Switch off your phone.
Open the MI Unlock Tool on your PC, run the file that is an application. Read through everything, click on unlock, confirm.
Wait till the phone fully reboots itself. DON'T TOUCH IT NOW!
Congrats, the phone is now unlocked, and you have stock MIUI 11.
Now skip everything in the setup (we wanna add a custom ROM now remember, why stop here?)
again do the adb devices. You should get the same results.
Now, on your PC
Extract the Platform Tools zip file so you get its folder.
Move the TWRP.img file into the folder.
Open that folder. on that address bar, type cmd to get a new command prompt window.
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
342524356 fastboot
Then type fastboot flash recovery twrp(press the TAB key to autofill)
Now it's done! you have TWRP, but it isn't permanent.
Now, TWRP usage.
Now press and hold power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data
Now go to MENU > Reboot > Recovery
Now, to Flash your first Custom Rom.
Now from your PC copy the ROM zip file, Disable decrypt zip file, gapps ( if specified, optional), magisk ( if you want to root, optional)
Now go to MENU > Reboot > Recovery
Now go to FILES > tap on the ROM zip > add to queue > tap disable decrypt zip file > add to queue > (add gapps , magisk if needed) > flash
Now wait for a while (approx 10mins) till ROM boots up and complete the setup process.
Congrats you have your new ROM.
Now just let google download all your apps
Before you change settings like dark mode or use custom launchers etc...
Reboot once for the heck of it. Then Customize the way you like.
**** Backup Your Persist and save it on your PC always. ****
You can backup persist by having root then downloading a terminal app from Playstore. then typing these two commands
Code:
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Click to expand...
Click to collapse
How To Change My ROM? I wanna Try them all!
Now is the easy part, since all the setup is done!
First remove all passwords, fingerprints, and so forth.
For AOSP ROMs: (MIUI below)
AOSP ROMs will not break your L1
First Download the AOSP ROM you want, given below are some examples. (MIUI below)
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Then go to WIPE > select Dalvik, Cache, System, Data > then wipe them all.
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from miui and flashing AOSP, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the Vendor (if it's needed) (not required if moving between any android 10 ROMs) (Just make sure it's the right Vendor for your device/region) (If the previous AOSP rom uses OSS vendor, then you need to wipe vendor as well and flash the stock before proceeding) and flash it.
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (not required if you want to be encrypted, which is not recommended.) (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Gapps (if it isn't already included in the ROM, ask first).
and Magisk (optional if you want root).
For MIUI ROMs: (AOSP above)
First Download the MIUI based ROM you want ( stock, EU, MortalOS, etc), given below are some examples.
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Select the Vendor (if it's needed) (not required if it's currently the proper Vendor, cause EU ROMs to use a custom vendor that works on all devices) (Just make sure it's the right Vendor for your device/region) and flash it.
Then go to WIPE > select Dalvik, Cache, System, Data, Vendor > then wipe them all. (make sure you are on your device's vendor region before wiping it.)
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from AOSP and flashing MIUI, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Magisk (optional if you want root).
Some Android ROMs
With ROMs being built, changed, and modified on a daily/weekly basis. Some changing to Mi9 fod or LOS fod or using Stock or OSS vendors. Sometimes maintainers shifting or 2 devs building the same rom. The below list is not being maintained anymore. We currently have 50 ROMs. YAY Raphael!
Update: I'm removing most of the ROMs listed here and only adding my personal favorite ROMs
AOSP ROMs
DerpfestOS (two variants, I like em both) - by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-derpfest-t4132757
SuperiorOS by @HSgod -> https://forum.xda-developers.com/k20-pro/development/rom-superioros-t4130867
MortalOS (miui12) by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-havoc-os-3-3-t4063081
LineageOS, Pixel Experience, PE+, PE+ Fan Edition, ParanoidOS, MookeOS, TitaniumOS, MSM Xtended, OxygenOS, OmniOS, TreskMod, AOSIP, ColtOS, ArrowOS, BootleggersOS, ExtendedUI (exui), CRdroidOS, RevengeOS, IonOS, AICP, BlissOS, CorvusOS, DerpfestOS, HavocOS, NitrogenOS, HentaiOS, Corvus, TitianiumOS, CygnusOS, CesiumOS, Project 404, DescendantOS, SyberiaOS, EvolutionX, AOSPA, POSP, LegionOS, AncientOS, RebellionOS, SuperiorOS, ShapeshiftOS, WrathOS, ZenX, AIM OS, ConquerOS, PixelDustOS, CygnusOS, StagOS, Ressurection Remix OS, Quartz, PixysOS, PePlusUI, MalluOS, StatixOS, GrapheneOS, ShapeshiftOS, MortalOS, SuperiorOS, AwakenOS, DotOS, Lemon Branch, FluidOS, LiquidOS + more!
MIUI ROMs
EU ROMs, MortalOS, RevolutionOS, Miroom, MMX, Masik + 5 other ROMs
Kernels
Perf (miui kernel), F1xy, Immensity, Englezos, Marisa, R4v3n, Void, NotKernel, Smurf, Candy, Supermad, Antarctica, Evira
MY SUPPORT
I got help from multiple telegram guys for this.
Shoutout to @ishtiak02, @ComicoX, @logosA, Bruce Wayne, SSS, @Noobmaster69 @Lacentix @Raaj52 @nevoness @joshuah1971 and a lot of others teaching me about ROMs and answering my numerous questions.
I am using the Indian variant K20 pro (aka Raphaelin)
You can always ask in the Our Telegram Group, or me, or in the comments. (not allowed to link telegram group I think)
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Reverting Back to PIE, moving from Android 10+ to Android 9 -Just don't- (RIN users)
Right, so Anti-Rollback protection is not implemented for k20 pro or mi 9tp. YOU CAN REVERT IF YOU WANT TO.
This is confirmed by users who have reverted, and by Xiaomi.eu website. Which I trust regarding this.
We've done experiments regarding this and have concluded this applies to raphaelin users (Indian variant devices) only. Unsure why, and how it is not affecting the mi9tp variant. (no confirmation with RCN)
However,
When moving from an Android 10 vendor to an Android 9 vendor, your SENSORS will break!
You can fix this simply by flashing your persist img (Hope you took that backup).
You can also fix your sensors by flashing someone else's persist img. BUT YOU WILL LOSE L1 FOREVER.
You can get L1 back by replacing the motherboard which can be done via your warranty at a service center, or by playing a hefty sum of money. nearly half the cost of the phone. NO OTHER WAY. Also, they open your phone, so it isn't SPLASHPROOF as much anymore.
You can also fix sensors by simply updating back to android 10 via the OTA method, which is found in your settings remember. (Unsure if this will retain your L1 though)
BOTTOM LINE, IF YOU ARE ON ANDROID 10, don't go to ANDROID 9 back.
Stuck at Fastboot Fix
Best Recovery
So regarding Recoveries. Choose the one you like the most.
I prefer the latest OrangeFox recovery cause it looks better, has a better UI, better settings, more functionality, and so forth. https://files.orangefox.tech/OrangeFox-Stable/raphael/
You can also choose TWRP if you like. Completely your choice. You can get that from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363 and choose the most recent one, and follow the instructions given there.
If you are just comfortable with TWRP. Always use Mauronofrio's, which is recognized as OFFICIAL.
To flash either recovery, just download the zip file, and simply flash it directly in your recovery like you do for a rom (no need to wipe anything) and it will auto-reboot into your desired recovery.
All credits to those who made the recoveries and those people who helped them.
Stuck in Stock Recovery when Rebooting Fix
Full credits to @ SivSomRao (telegram handle, since no XDA)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, I was scared half out of my mind. A guy named Shivsom helped me.
Basically what he made me do was
Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder in my WindowsOS C drive.
Now, on your PC. Copy your TWRP.img file, or your OrangeFox.img (I prefer the TWRP.img file by Mauronofrio.)
Open the Command prompt in that folder
You can do this by clicking on the address bar of File Explorer and typing > cmd > then Enter
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
Press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
3e2f2d356 fastboot
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Now, TWRP usage.
Now press and hold the power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on the "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data > type 'yes' (This will delete everything in your Internal Storage so Caution)
Then quickly flash the latest miui vendor,
Now go to MENU > Reboot > Recovery
I was OverJoyed when this worked.
Now you can flash your Favourite ROM (normal clean flash, tutorial is given above), and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right, so I tried LR-twrp (it's in Chinese, but I can change the language to English). PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did.
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.
ERROR 7 fix and how to modify UpdaterScript
WHAT IS ERROR 7? :
Error 7 is an error that says the ROM you are flashing is not meant for your device.
It does so by comparing the phone's codenames.....
k20p and mi9tp have two codenames, one is RAPHAEL and the other is RAPHAELIN (the Indian variant)
Flashing the Raphael/raphaelin ROM on either device won't cause any problems at all.
feel free to flash it.
Latest orangefox 10.8 works with Raphael (global and Chinese variant) and orangefox 10.6 works with Rapahelin (Indian variant).
Alternatively, It could also be caused because you are required to flash the latest vendor, which you may have not.
So please read the one-line error message that appears above the ERROR 7 red message for more details
SOLUTION to ERROR 7:
I'd recommend flashing the orangefox 10.6 recovery as it's a lot simpler.
However if this doesn't work you can try updating script.
Right, so instead of using a different recovery, you choose to update the updater-script.
Copy the zip folder of the ROM to your PC
You can use 7zip software on your Windows PC. Download this software if you don't have it.
Double click the zip (don't extract it!!!) to open the zip.
Navigate to meta_info> com > Google > Android > you'll find update_script
Find the updater-script. Right-click on it, and choose the "EDIT" option. And edit the word Raphael to raphaelin (if you have the Indian variant of the phone)
Save and exit.
Click to expand...
Click to collapse
Creating Backups
Creating backups is always the safest thing to do, and you can do so via your recovery (OrangeFox or TWRP)
First, make sure you have everything working, nothing is broken in the ROM.
Second, go to your recovery and tap on Backup. Then Click on Create Backup, rename the file if you want to.
Third, Select all the partitions, cause why not, and let it finish creating the Backup.
Finally copy the backup file created to your PC in a safe location, and later when and 'if' you mess up, you can copy the backup file back and restore it.
You can restore by first wiping everything and formatting. (For safety) Then using the same recovery you used to create the backup, Flash the backup file. DO NO FLASH SOMEONE ELSE'S BACKUP FILES!!!!!! ONLY YOURS!!!!!!
How to Decrypt Your Phone.
So encryption is the safest thing for devices, It uses a secret code/key that only your phone knows to read data and information. However, when in Recovery, we Custom ROM enthusiasts like to have our data DECRYPTED. Now, This is because we can access our files from the recovery, flash ROMs only when decrypted, and transfer files. (If we have MTP enabled in recovery)
Somehow you've found yourself encrypted, which means all the files in your recovery are showing random letters + alphabets. and you cant transfer files to your phone via recovery anymore!
To solve this, or decrypt yourself. You will have to format your data partition (this will delete everything in your internal storage, so I hope you have a backup of your photos, vids, gifs, contacts, and so forth)
Just a bit of quick advice, If you can boot into your OS, go there, and transfer all your internal storage to your PC or laptop before formatting to avoid losing your stuff.
If you can't boot into your ROM, then you'll have to lose all your data in internal storage. No known method is known YET to help without losing the files.
Now the SOLUTION: Go to Orangefox settings > manage partitions > select data > tap on format > type 'YES' > swipe to confirm > you lose all your internal storage data contents, and you are now successfully decrypted.
OR if you are using TWRP. Go to WIPE > (right side button) FORMAT DATA > type 'YES' > you lose all your internal storage data contents, and you are now successfully decrypted.
You can now transfer files to your phone properly.
To stay decrypted and not get encrypted again, flash the DFE (Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip) from attachments below (or from the file attachment called disable_force_encrypt.zip above in the first post/comment) and then boot into your ROM, or if you are flashing a new custom ROM, follow the tutorial above(first post/comment)
If you want to stay encrypted. (I advise against this) Just don't flash the DFE file.
The newer latest updated dfe file I have attached in this comment is from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and all credits for the file go to him. The dfe file in the first comment/post is different and also works.
How to Recognize Which Device You Have And What Vendor Should You Use?
Global, EEA, China, Indian, Russian variant?
All credits for this list go to @joshuah1971 aka Superuser1958 on telegram.
Box Packaging
k20 pro-China: purple+black box with Chinese writing.
k20 pro-India: angled photo of the phone on top+ white box (NO NFC capability. hardware, not software), identifier: raphaelin.
mi 9t pro-Global: black box+ picture of the device on top, English text on side sticker. (model: M1903F11G)
mi 9t pro-RU: same as global but with Russian text+ orange sticker on the phone.
mi 9t pro-EEA: white box.
Software Differences
miui Global: version number will include "QFKMIXM", google dialer, and messages.
miui EEA: version number will include "QFKEUXM", google dialer, and messages.
miui China: version number will include "QFKCNXM", miui dialer, and messages.
miui India: version number will include "QFKINXM", miui dialer, and messages.
miui Russia: version number will include "QFKRUXM", miui dialer, and messages.
So check which device variant it is, and use the appropriate Vendor when flashing. (Go to ROM's Settings-> About phone-> MIUI Version [code in the brackets])
Vendor Links
So regarding Vendors. Choose the one your device needs.
Namely, The Indian Variant is called Raphaelin. So get your vendor from https://xiaomifirmwareupdater.com/vendor/raphaelin/
The Global, Europe, China, and Russian Vendors are gotten from https://xiaomifirmwareupdater.com/vendor/raphael/
What is OSS Vendor? How to switch to the F2FS file system on OSS ROMs only?
What is OSS Vendor?
So our device has 5 variants.
Xiaomi firmware website has all 5 official (firmware+vendor) zip files.
"Always flash your variants vendor."
"Xiaomi never showed us what's in them. Aka closed source"
But this is so confusing for some people. Idky.
Therefore, some devs decided to make a universal vendor that will work on all variants. Since they are making it. They can optimize it and also always know what's in it.
This universal vendor is called an OSS vendor. (Open Source Software) (It's not yet perfect though)
Some custom ROMs don't include vendor (cause OSS isn't perfect yet)
Some custom ROMs include OSS vendor (so we can observe how good it is in daily use)
It's always good to know if the rom is using OSS or if we have to flash the official.
Currently. Since OSS isn't perfect yet. If the rom doesn't include vendor (or it's a custom miui) do not flash/use OSS with it.
How to switch to F2FS File system?
• Go to the rightmost tab on orange fox recovery > manage partitions > data > change FS > tap on f2fs > change FS
• Now reboot recovery
• Now reboot recovery again
• You are now f2fs.
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Info about Persist and why it is IMPORTANT to make a Backup
To make a Backup: Go to orangefox/TWRP recovery and select the Backup option and choose the persist.img option and back that up. Make a copy on your PC for added protection.
Persist.img is "persist" which contains data that shouldn't be changed after the device shipped, for example, calibration data of chips(wifi, bt, camera, etc.), certificates, and other security-related files. Persist is having keys to decrypt several pieces of stuff, it is device-specific and you shouldn't flash persist of others, very very bad idea.
How you are losing L1? By flashing someone else persist.img file, and if you have done that you already lost it. You cannot recover it. You can still restore your own old persist back up, and if you are lucky you will get L1 back. Never play with the persist partition it has important information specific to your device.
In case you've just lost it, and you've realized it immediately (cause sensors, pop-up, L1 are broken), & haven't done anything to modify yet. Then you can try to restore the context. Try doing this in a terminal emulator like termux (case-sensitive) Termux is an app on play store (requires root):
Code:
su
restorecon -F -R /mnt/vendor/persist/
There is also this really nice guide by William Feng that explains the same but a bit better here:
Backup and restore persist on K20 Pro and 9T Pro
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
Xiaomi.eu and other Custom MIUI ROMs
Right, so Xiaomi.eu is a forum like XDA where devs make miui like ROMs without the Mi ads and tracking and are more optimized.
The website is: https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Under there, you go to MIUI 11 ROMs > stable ROMs > download the proper ROM zip file.
The direct download link is https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/ or you can use: https://androidfilehost.com/?w=files&flid=300229
Now download xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip CAUTION, the word PRO has to be there. we have k20p not k20.
This works for only Raphael users, not Indian raphaelin users. (For raphaelin users use Orangefox 10.6 it will work then.)
The difference between Stable and beta is that in beta, newer features, security is implemented and tested, this has bugs, once those features are stable, it becomes a STABLE rom, then the next batch of features are added to the beta. Get STABLE though, it's better, the beta has weekly 2GB updates.
Now flashing is easy, Follow the rules in the first post/comment on how to flash a miui ROM.
Equally, you may also choose to use MortalOS which is a debloated MIUI ROM which can be found here -> https://forum.xda-developers.com/k20-pro/development/memeui-12-rc5-09-05-2020-t4097469
Issues Related to L1, restoring, and china-based miui roms
Thanks to @Raaj52 for conducting experiments to confirm and collect this information.
You must have a global/Indian variant phone which currently has widevine working properly to have a chance at restoring it later. China phones can't get L1 (or at least, I haven't learned a way to do so yet.)
What is Widevine L1 and L3?:
Right, so L1 or widevine L1 is a DRM security made by google after they noticed people use root, etc to steal copyrighted videos and movies in full HD and post them somewhere else for free. (Netflix and Amazon prime video app being affected.)
Losing this, means you get L3, and widevine L3 does not allow you to stream Full HD videos anymore, but you can stream SD low-quality videos. Which is never ideal.[
Now, EU latest stable, MortalOS uses modified china vendor with k20p L1 patch
So how do I save my L1 then? L1 Retention?:
Fortunately @Raaj52 found out that if you take a full Ofox or TWRP backup or everything from EU rom, (making a save on the PC, just in case) before moving to those aforementioned China-based ROMs is good.
When you try flashing miui EU latest stable after losing it by flashing a MIUI custom ROM based on China vendors, your phone gets L1, it shows you have L1 too, however, the apps on your phone DO NOT recognize it, technically the phone recognizes the widevine L1 as broken, and somehow considers it L3.
Here is where the Backup you made comes in handy, Clean flashing the backup completely and perfectly restores your L1. He also states that moving from China-based ROMs to AOSP ROMs like EvoX via clean flash (wiping vendor as well and flashing the proper vendor before flashing the AOSP ROM in the recovery) will also restore L1 (remember to format data partition when moving from miui to AOSP)
Now, It should be noted that cross-flashing vendors is very DANGEROUS, as this may break your Fingerprint Sensor, DTBO and proximity sensors. Therefore you must always flash the proper vendor for your phone (global, Indian, china) don't try flashing a vendor that isn't for your device. Unless if it's a custom MIUI rom as custom MIUI Roms come included with a Vendor. (wipe vendor before flashing custom miui ROM, after flash, don't touch the vendor)
Global vendor and Indian vendor are partially similar, and we have reason to believe that EU stable uses a modified vendor that works for both Raphael and Rapahelin. This is why EU ROMs works on both devices (MI 9t-pro and K20-pro)
Some Things to be Cautious about and to note:
Quoting our messages on telegram here:
The basic is, EU rom comes with vendor file so no need to flash a separate vendor for them. Flashing any vendor over the EU might break something because we don't know really which vendor they are using, assuming stables are global and betas are china.
On the other hand, AOSP comes without any vendor file, so it becomes mandatory to flash a vendor based on your device default vendor.
We flash vendors only when we flash AOSP's. In miui custom ROMs vendor is included.
Exception: If something is broken, clean wipe, flash your vendor, and then (advance wipe everything, including vendor) clean flash miui custom/AOSP.
Practically speaking, if you are moving from your stable own rom to Evox or any AOSP, no need to flash vendor since it is already having the default files but this is double confirm that the vendor is correct and it will not harm anyone. (AOSP to AOSP, not required to wipe vendor, but you can if you want to, I recommend wiping it and flashing your vendor again)
These are separate partitions and it will not override but to be on the safer side most rom devs prefer vendor and then rom.
If you flash an AOSP rom and want to move to a custom/stock miui rom make sure that you are own correct vendor. (Prior to wiping it in advance wipe) If not sure flash your vendor once again, then clean wipe and flash miui based rom.
Click to expand...
Click to collapse
How Get Back To My Stock ROM and/or Lock Bootloader?
To get back to your stock ROM, you have two methods, namely recovery zip ROM flash or fastboot ROM flash.
Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphael/
or if you need the Indian variant, Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphaelin/
Now, AND THIS IS SUPER IMPORTANT. Make sure you double-check and download the proper device's Region, codename, android version, and THE TYPE!!! (there are two types: recovery and fastboot types, choose the one you need)
Now for the recovery method, flash the recovery type .zip file the same way you flash any miui custom ROM. Check guide in first post/comment for method.
Now for the fastboot method, go to your mi-flash tool and enter fastboot on your device, and flash the rom there. (Now, I personally never did this method, so I can't guide the exact steps for this method, sorry)
LOCKING BOOTLOADER: You must first be using the proper stock vendor, stock rom via fastboot, and not have magisk or any MODs running on your phone. If you violate these, you WILL Hard brick your device. It is because of this I VERY STRONGLY advise against locking your bootloader for any reason whatsoever. JUST DON'T!!!
However, you can you the mi-flash tool (safest) or the debloater tool to lock your bootloader if you definitely must do it.
• Download MiFlash tool from MiFlashTool Website . The latest is the top left, marked with a NEW tag.
extract the file, and run the program "XiaoMiFlash.exe"
• Download the stock fastboot miui rom from Fastboot Website and extract the file (if its a .tgz or .tar extract again) you'll end up with a folder with one folder and 11 files (images, flash_all.bat.......misc.txt)
• Now in whatever rom you are on, go to developer settings, enable "OEM Unlocking" and "USB Debugging"
• Now boot into fastboot mode
• Connect your device to your PC
• Now in MiFlash tool, at the bottom, choose Clean all (and dont LOCK IT, I repeat do not choose to lock)
• Then on the top click on the "select" button and navigate to the folder with the 11 files & 1 folder and choose that folder.
• Click on the "Refresh" button and check if your device is shown (indicated by random numbers/letters)
• Now (recheck if its only CLEAN ALL only, and NOT lock or anything else)
• Now flash
• Wait 420s approx, or more, or less.
• It'll finish with an error and the message will say
• "error: Not catch checkpoint (\$fastboot -s . ' lock),flash is not done"
• This is cause it did not lock your bootloader. THIS IS GOOD.
• Now wait 5-10mins while miui 12.5 loads up/boots, it takes a while.
• Now, close MiFlash program, its done, no more needed.
• Now that's done, use miui 12.5 if you want, or go to recovery
• You'll see you have stock recovery now
• So go to fastboot mode, (phone connected to PC)
and flash the ofox recovery.img to get ofox recovery. via the cmd command like usual.
• Then go to recovery ofox.
• Go to wipe > format > type yes > format data to decrypt
• Reboot to recovery
• Now copy your ofox zip file to phone,
• Now flash that file to make OFOX permanent
• Now reboot to recovery again.
Click to expand...
Click to collapse
Latest MIUI-CN builds and miui custom ROMs soft bricking your device? (Mostly Raphaelin users)
Right, so this is a Xiaomi thing, which happens to many Xiaomi-based devices. It was later observed by a member on telegram that this usually happens to devices without NFC. In our case of Raphael - This would be Indian devices or Raphaelin devices.
I personally haven't experienced this, so I can't give a personal experienced-based guide on fixing this. However, another user on telegram @rockyanexpert solved his problem and shared this guide given below with me.
[
System has been destroyed. What I did:
1. Panicked a little
2. Started my lappy
3. MiUnlock Tool was pre-installed v3.xx
4. It took almost 10 minutes to show the login prompt. The connected device in fastboot. It failed to recognize the device. Started MiFlash. It did recognize the device.
5. Downloaded the latest MiUnlock. It too failed to recognize the device.
6. Downloaded XiaoMiTool v2
7. It detected the device fastboot serial correctly
8. Manually selected model Raphael.
9. Started with My device is bricked
10. It detected a locked bootloader. Opened its own version of Unlock Tool. Logged in to binded Mi Account. (My Mi Account n the binded one is the same)
11. Unlocked.
12. Tool went on ahead with waiting for the device to boot in fastboot mode.
13. I removed the device n forced boot in recovery mode. Ofox showed "Updating" n booted in orange ofox screen.
14. Rebooted system
15. Newly flashed Eu 21.2.3 started initial setup.
No data lost.
Click to expand...
Click to collapse
By these same people, they made a guide here: System destroyed issues
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
nice work @Sandeeep Kiran, keep it up.
Just got my 12/512 yesterday but my wait time is 15days (it said 360hours).:fingers-crossed:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
salva93 said:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
Click to expand...
Click to collapse
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Sandeeep Kiran said:
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Click to expand...
Click to collapse
Many thanks for your answer, so for now i will not risk and i will follow instructions on xioami.eu website, i'm in clean situation so i should not have any issue
bump
Good guide. Have a bump.
But till this day (Jan 6, 2020), no custom roms are stable or bugfree enough for the exception of xiaomi.eu
Default MIUIrom just works. But I hope in the near future we get to see bugfree roms and I will certainly try it! I have always used PE on my previous phones.
Cheers!!!!
bumpity bump
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
bigatim said:
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
Click to expand...
Click to collapse
Nah, Mount is to send/transfer files.
Since you arent doing that, you dont have to mount system or vendor, but mount your internal storage though.
and for the L1 flash, mount vendor for that only, soon a magisk mod will be available for it.
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
I've tried RevOS and I came back to mmx.
And widevine L1 is not break. Everything gone fine.
Krullendhaar said:
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case, you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
Click to expand...
Click to collapse
DFE is to remove encryption.
when you format data partition, you remove the dfe. You do this when moving from AOSP to miui or vice versa.
you can't decrypt before flashing cause there isn't a system or any data to decrypt. After you add a ROM or data, you can decrypt that.
yes, the format will get rid of your encryption. (but you also lose all your data) so flashing dfe helps retain your data. If you're scared someone will go to your recovery and steal data, add an orangefox password in its settings. Alternatively, you also have the dm-verity settings in orangefox settings you can enable. But redundant as its all included together in the dfe file I've attached.
Sandeeep Kiran said:
L3 Fix, Getting L1 after getting L3 for Global and Indian Users.
@Raaj52 Found a solution to fix L3 and get L1 again.
This fix however only works on Global and Indian vendors. (i.e mi 9t pro and k20p Indian variant)
No such solution has been found for china phones, using china vendor, DO NOT CROSS FLASH VENDORS!! it will cause a bootloop.
This patch was made for the latest EU beta, miroom. We hope it also works for future versions, and previous versions, but we are unsure. You can experiment and inform us though in the comments below.
Always have a proper fully working backup of everything rom. As caution. It's always good to take precautions.
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Click to expand...
Click to collapse
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
uurturk said:
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
Click to expand...
Click to collapse
The patch was intended to work on security patch Jan 20th and above, which maisk is not yet updated too.
(however, @ QasimXAli in the official telegram group did manage to make it work. you can tag and ask him there.)
Currently, the person who made the mod is still working to converting it to a perfect magisk module so it's easier to flash. Also, he is waiting for the next stable update to check whether the magisk module patch will continue to work.
We just gotta wait a bit longer.
ghaf85 said:
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Click to expand...
Click to collapse
Thanks.
Under add-ons, I added how to get WhatsApp dark (currently in WhatsApp official beta, which will roll out to stable in three months.)
For root, everyone just uses magisk latest stable.
and Solid Explorer or Mi-explorer
I like swift, liv and flux too. but those are straight-forward. I can add them to "add-ons" if you like.