Hello,
I made some Backups with TWRP on my Xiaomi Remi Note 5 before.
When I tried now, I get this Error:
Failed to mount '/vendor' (Structure needs cleaning)
The filesize of "vendor" looks a bit strange (see picture).
I think there is a problem with the file-system. When I try to repair the filesystem I get:
Error:4 unable to repair filesystem.
Any help to fix this problem appreciated.
Thanks in advance,
Ingo
https://forum.xda-developers.com/album.php?albumid=15132&pictureid=58030
https://forum.xda-developers.com/album.php?albumid=15132&pictureid=58029
https://forum.xda-developers.com/album.php?albumid=15132&pictureid=58028
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flensburger said:
Hello,
I made some Backups with TWRP on my Xiaomi Remi Note 5 before.
When I tried now, I get this Error:
Failed to mount '/vendor' (Structure needs cleaning)
The filesize of "vendor" looks a bit strange (see picture).
I think there is a problem with the file-system. When I try to repair the filesystem I get:
Error:4 unable to repair filesystem.
Any help to fix this problem appreciated.
Thanks in advance,
Ingo
https://forum.xda-developers.com/album.php?albumid=15132&pictureid=58030
https://forum.xda-developers.com/album.php?albumid=15132&pictureid=58029
https://forum.xda-developers.com/album.php?albumid=15132&pictureid=58028
Click to expand...
Click to collapse
Hello I am getting the same error what did you do to solve the error?
Anirudh44 said:
Hello I am getting the same error what did you do to solve the error?
Click to expand...
Click to collapse
Till now, I did nothing and just leave it as it is. I want to flash the 9.6.4 Firmware (it is on now) and not the upgrade to Miui 10 because of the downgrade problem.
But I worry if I brick the phone when flashing the 9.6.4. So, I wait for the problem solving itself
Maybe you try it and report?
:angel:
i have same problem like you, and solved my problem.
1. enter recovery (twrp)
2. enter wipe data, checklist vendor
3. repair file system, change file system, look your vendor type. mine is ext4. so, i choose ext4. swipe
sorry for my bad english.
zhemenx said:
i have same problem like you, and solved my problem.
1. enter recovery (twrp)
2. enter wipe data, checklist vendor
3. repair file system, change file system, look your vendor type. mine is ext4. so, i choose ext4. swipe
sorry for my bad english.
Click to expand...
Click to collapse
O.K., I tried that. No so good, ended in a reboot-loop
I put back one my old Backups (the last which was working before the vendor-partition-**** started. Now I have to configure the phone again to get it working for me.
After that I will have a look on the vebdor partition, if it is o.k. again.
Flensburger said:
O.K., I tried that. No so good, ended in a reboot-loop
I put back one my old Backups (the last which was working before the vendor-partition-**** started. Now I have to configure the phone again to get it working for me.
After that I will have a look on the vebdor partition, if it is o.k. again.
Click to expand...
Click to collapse
It looks that you have a Redmi Note 5 pro (Whyred) so Redmi 5 Plus (Vince) doesn´t have any issue with downgrading. I guess this happened cause you flashed at some time a pie rom and then to it vendor is not longer used; maybe it solves wiping vendor partition.
SubwayChamp said:
It looks that you have a Redmi Note 5 pro (Whyred) so Redmi 5 Plus (Vince) doesn´t have any issue with downgrading. I guess this happened cause you flashed at some time a pie rom and then to it vendor is not longer used; maybe it solves wiping vendor partition.
Click to expand...
Click to collapse
I think, i did not flash apie rom, cause I don't know what that is
I only rootet it, installed TWRP and Magisk.
And yes, it is a Whyred.
The Vendor-Partition is still broken.
I can make a Backup with TWRP, but without the System. When I try to Backup System as well, I get the error:
Code:
Invalid encryption mode file /data/unencrypted/mode
Backing up System...
Invalid encryption mode file /data/unencrypted/mode
Error opening: '/system/app/AnalyticsCore/oat' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/1f6bac4b/2018-12-10--02-10-34_OPM1171019011/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Does it help if I post the complete TWRP-Log?
Flensburger said:
I think, i did not flash apie rom, cause I don't know what that is
I only rootet it, installed TWRP and Magisk.
And yes, it is a Whyred.
The Vendor-Partition is still broken.
I can make a Backup with TWRP, but without the System. When I try to Backup System as well, I get the error:
Code:
Invalid encryption mode file /data/unencrypted/mode
Backing up System...
Invalid encryption mode file /data/unencrypted/mode
Error opening: '/system/app/AnalyticsCore/oat' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/1f6bac4b/2018-12-10--02-10-34_OPM1171019011/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Does it help if I post the complete TWRP-Log?
Click to expand...
Click to collapse
Check if you swipe to allow modifications in recovery.
In this case it could be that your vendor partition is missing and it may solved by flashing stock rom again through MiFlash Tool if you´re not in ARB top code.
Also this recovery is actually better with more functions https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547 and if you switch to it you can share also there the issue so this forum is for vince and is not allowed to treat and solve here issues from other device.
SubwayChamp said:
Check if you swipe to allow modifications in recovery.
In this case it could be that your vendor partition is missing and it may solved by flashing stock rom again through MiFlash Tool if you´re not in ARB top code.
Also this recovery is actually better with more functions https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547 and if you switch to it you can share also there the issue so this forum is for vince and is not allowed to treat and solve here issues from other device.
Click to expand...
Click to collapse
Back again....
I installed the FOX recovery and tried the same repair and backup stuff. Also the "swipe to allow modifications" was on.
No success, "Vendor" eg. "system" Partition still damaged.
Then I installed the 9.6.4 Image via FOX. After that the partition was O.K. again. The installed Apps are untouched.
But now I face a new problem. Making a backup via FOX on to the SD-Card won't work because FOX claims the free space on the SD is 51 MB, but it is actually 51 GB.
I will try to go back to TWRP an see how that works.
Thanks
Flensburger said:
Back again....
I installed the FOX recovery and tried the same repair and backup stuff. Also the "swipe to allow modifications" was on.
No success, "Vendor" eg. "system" Partition still damaged.
Then I installed the 9.6.4 Image via FOX. After that the partition was O.K. again. The installed Apps are untouched.
But now I face a new problem. Making a backup via FOX on to the SD-Card won't work because FOX claims the free space on the SD is 51 MB, but it is actually 51 GB.
I will try to go back to TWRP an see how that works.
Thanks
Click to expand...
Click to collapse
O.K., now I solved the SD-problem as well by reading what's written in error log............
emptied the SD card :laugh:
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount_ramdisk for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount not tested yet
Instructions:
Flash twrpimgmount_ramdisk.img through fastboot
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
Press and hole both volume + power on to boot to erecovery OR volume up + power on to boot to twrp (i don't know which combination is of which one) i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup Ramdisk
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Flash Magisk 16.0+ to root
XDA:DevDB Information
[OREO]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, Pretoriano80, zxz0O0
Version Information
Status: Testing
Created 2018-03-17
Last Updated 2018-04-07
For Nougat : Go Here
Reserved
TWRP on my OREO Beta Not Detecting My Phone on Pc no Response Please Check Ur Recovery
Can I do this with the Bnd-L24 model that has the bootloader unlocked with TWRP installed?
Great bhai
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Sudeep Duhoon said:
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Click to expand...
Click to collapse
one further note, using the "complete_twrp_ramdisk.img" TWRP was able to see the installed OS, and offered to install the TWRP app.
Sudeep Duhoon said:
i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Click to expand...
Click to collapse
What does this mean?
---------- Post added at 10:08 AM ---------- Previous post was at 09:36 AM ----------
I couldn't get it to backup. It always fails at data or system (If I don't select data).
Tried both images.
how can i flash the stock recovery? i was able to brick my device
Edit: nvm i fixed it
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Hi, I'm glad to report that although the first recovery that is twrpimgmount_ramdisk.img failed to backup system as I got the same error message as above but I was able to flash some other partitions like kernel, recovery etc... I actually selected a bunch of them.
Anyway most importantly after flashing the complete_twrp_ramdisk.img, I was able to backup system successfully. I'm using the Indian variant BND AL10 MODEL. I hope this helps some one out there.
I have a dumb question: Now, that the system is backed up with twrp, if I mess up my phone ever, can I simply restore this system img and be able to boot back into the os? Do I need to install any other partitions? I don't care about data. Please let me know.
Hi, I flashed this complete_twrp_ramdisk.img and now I want to go back to stock recovery of oreo which is bnd_recovery_nocheck.img from the other post. I tried using adb and it fails. I tried using the this twrp but it shows a lot of partitions to choose from and I'm confused example: ramdisk recovery, recovery_vendor, recovery_ramdisk etc... there are sooooooo many. I tried recovery_vendor and also ramdisk but it doesn't work. Can you please tell me how to install the stock recovery?
Does anybody have a BND-L21 backup of the system partition?
Edit: nvm i found it
Can someone tell me how to install stock recovery after installing the above complete_twrp_ramdisk.img as I'm unable to flash using adb. I tried "fastboot flash recovery recovery.img" and also "fastboot flash recovery_ramdisk recovery.img" I tried flashing the BND_recovery_nocheck.img from the other post which is a stock one.
I also tried flashing it using this twrp to the partition recovery_ramdisk and gives the error saying "the size is larger than the device" Please someone help.
I have tried couple times to install new release
twrp_ramdisk_oreo_7-4-18.img
Click to expand...
Click to collapse
But I can only get to twrp splash screen.
OP change-log has no information about this new release, so maybe is still not ready.
telegram group has mention of this , but did not help Yet.
**EDIT**
It was suggested by DEV in telegram to just be patient and try again. This third time installed 4-7-2018 released version it loaded right into recovery, without any delay.
Don't know if it is coincidence or not but before I was on RRos ROM. and now I am back on EMUI 8
Well, the mess here you have gentlemen, nichrome you do not understand where the root for 7ku, where to 8ku, what tvrp to put for 8ki for everyday needs.
---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------
Which TWRP can I put in order to flush the root on the 8th oreo?
What TWRP should I be using on RROS Room? In order to install Magisk?
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
darkmage1991 said:
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
Click to expand...
Click to collapse
Afaik they are test builds (ports) of data decryption enabled twrp.
I had them working when on the Oreo beta but cannot get to work on RR or the new official Oreo.
With this tool is possible resize the system partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Precautions and warnings:
This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups.
Increasing the size of the system will decrease the internal storage in the same proportion, when using previous backup consider this, if the backup is too large it may not fit in the new partitioning.
To prevent bootloop, use a permanent installation of TWRP, do not use temporary boot.
I am not responsible for bricked devices or dead SD cards.
Use at your own risk
Instructions:
Part 1
1- Copy zip installer to external SD card, otherwise installation will be canceled. do not forget to also copy the custom rom and the gapps.
2- The installer uses Aroma ui, it is possible to choose several size for the system partition: 1GB, 1.25GB, 1.5GB, 1.75GB, 2GB, 2.25GB and 2.5GB.
3- Optionally it is possible to create a new partition, the vendor partition, it is required in the project treble and only used with treble roms and vendor partition compatible with Redmi 2.
4- The installer also creates a backup of some changed partitions and restores them automatically, a copy(110MB) is sent to the external SD card if an emergency restore is required.
5- After choosing all the options select Start, if all the requirements have been fulfilled the repartitioning will happen, otherwise it will be interrupted before any alteration. Then press the Reboot button to end.
Part 2
The most recent rom installer comes with the system inside an image file, it has the default size, and after installing the rom it is necessary to expand the file system so that it can see the new size.
This can be done with Twrp in the wipe advaced menu, but to make it easier I did an additional installer to do this task.
So summarizing:
1- Install 1Resize-System-Redmi2.zip (only when changing system size partition).
2- install your Custom-Rom.zip
3- install 3Expand-filesystem-Redmi2.zip (always required after installing custom rom and before gapps, this releases new size to use).
4- install gapps.zip
5- done !
Thanks the creators of content, for sharing knowledge:
@jsidney96 thread, @freeshared thread, @mirfatif thread, @osm0sis thread, @amarullz thread
.
Sorry my English.
.
[update]
v1.01: added reboot(recovery) after installation.
v1.03: (experimental) added option to create vendor partition and auxiliary zip installer.
Looks very cool! Have you heard of @Lanchon's RePIT? Similar idea but without the GUI. Perhaps you guys could collaborate? https://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
Edit: sorry it did not work. only the internal storage got reduced but the system partition remained the same.
log file attached below.
interesting
athish said:
Edit: sorry it did not work. only the internal storage got reduced but the system partition remained the same.
log file attached below.
Click to expand...
Click to collapse
Edit 2: So i was able to re-partition the system using the above script (i mean the script works). But after i installed lineageos 15.1 the system partition returned back to 1gb. Can anyone give me a solution for this? i tried the resize system after rom install but it failed. :crying:
screenshots below:
athish said:
Edit 2: So i was able to re-partition the system using the above script (i mean the script works). But after i installed lineageos 15.1 the system partition returned back to 1gb. Can anyone give me a solution for this? i tried the resize system after rom install but it failed. :crying:
screenshots below:
Click to expand...
Click to collapse
With me it works, but twrp only displays new size after exiting the wipe menu.
Then return to the main menu and enter the wipe menu again.
Error message appears if you press the "resize file system" button twice in a row.
Cecell3000 said:
With me it works, but twrp only displays new size after exiting the wipe menu.
Then return to the main menu and enter the wipe menu again.
Error message appears if you press the "resize file system" button twice in a row.
Click to expand...
Click to collapse
nope i press the "resize file system" only once and still gives the error.
can please explain what to do after installing a ROM (to get back the full size). And thank you for the making a zip installer:good:
Edit:
So after re-partiton of system to 2gb, i restored twrp backup and system remained 2gb :victory: :highfive:
@Cecell3000 Flash EDL mode rom miui, restores partition size?????????
xander21 said:
@Cecell3000 Flash EDL mode rom miui, restores partition size?????????
Click to expand...
Click to collapse
yes, edl / fastboot restore partition size.
But prefer reinstall the zip file by selecting (default) option.
Cecell3000 said:
yes, edl / fastboot restore partition size.
But prefer reinstall the zip file by selecting (default) option.
Click to expand...
Click to collapse
Im reinstall partition zip file and flash fastboot Rom. It can be like this?
xander21 said:
Im reinstall partition zip file and flash fastboot Rom. It can be like this?
Click to expand...
Click to collapse
yes, it's safer.
[update]
v1.01: added reboot(recovery) after installation.
v1.03: (experimental) added option to create vendor partition for project treble and auxiliary zip installer.
summary installation instructions:
1- Install 1Resize-System-Redmi2.zip (only when changing system size partition).
2- install your Custom-Rom.zip
3- install 3Expand-filesystem-Redmi2.zip (always required after installing custom rom and before gapps, this releases new size to use).
4- install gapps.zip
5- done !
Cecell3000 said:
With this tool is possible resize the system partition.
The installer uses Aroma ui
Click to expand...
Click to collapse
Is it possible to use this to only use Aroma's Remove stock apps functionality, without having to download and install the full Aroma? Can it be done without reinstalling/wiping the rom?
intresting
Where can I download this apps for other mobiles?
I need it for the Xiaomi Mi8.
Is it compatible?
Can I flash other ROMs such as Xiaom.eu if I have resized the partitions ?
Thanks
---------- Post added at 01:05 AM ---------- Previous post was at 12:58 AM ----------
What about resizing the data and cache partitions?
What partition is the culprit of the error of insuficient size when installing new apps?
Once resized will it remain 2gb forever or will it revert back to 1 gb as soon as I flash a custom rom?
I want to flash treble rom and then android p gsi files. So I need the vendor partition right?
thanks, it works for me
Which twrp to use to flash this installer?
hengkidermawan said:
thanks, it works for me
Click to expand...
Click to collapse
you can record on video? pleasee!!
Christian - Cuba said:
you can record on video? pleasee!!
Click to expand...
Click to collapse
the OP says clearly, bro..
1- Install 1Resize-System-Redmi2.zip (only when changing system size partition).
2- install your Custom-Rom.zip
3- install 3Expand-filesystem-Redmi2.zip (always required after installing custom rom and before gapps, this releases new size to use).
4- install gapps.zip
5- done !
---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------
Paleskin said:
Which twrp to use to flash this installer?
Click to expand...
Click to collapse
the latest twrp, and the important thing is permanent twrp that OP said
I started a little Android Generic System Image installation Guide on my Github :
https://github.com/GBouerat/xiaomi_mi_pad_4
(work in progress)
https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/TWRP
Code:
fastboot oem device-infov
Is it really device-infov or is it typo.
P.Kosunen said:
https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/TWRP
Code:
fastboot oem device-infov
Is it really device-infov or is it typo.
Click to expand...
Click to collapse
It's a typo, thanks
Code:
fastboot oem device-info
Thank you very much, mate! Can we expect to see an official TWRP release as well as LineageOS 15.1?
PS: Does Android P GIS work well? Are there any known issues so far?
Please do include the build.prop tweaks mentioned here - those are quite necessary for the device to function as a tablet.
cRaZy-bisCuiT said:
PS: Does Android P GIS work well? Are there any known issues so far?
Click to expand...
Click to collapse
None of those P GSIs boot.
Anyone able to root using Magisk on v9.6.23 boot.img (http://en.miui.com/thread-3538488-1-1.html)? Magisk patched boot.img doesn't seems to boot for me and I have to revert to stock boot.img.
Edit: hah, never mind. I forgot to disable forceencrypt when i flashed the new stock kernel and it encrypted data. Had to wipe data and unencrypt to root again.
Magisk on GSI is incompatible with adb usb debug mode, no ?
GBouerat said:
Magisk on GSI is incompatible with adb usb debug mode, no ?
Click to expand...
Click to collapse
works fine for me
Hi
Could You please write with recovery version is this? There are 2 recovery versions as of 2018.7.13 and 2018.7.11 with description like bellow:
2018.7.13 update
1. Fix the problem of not recognizing the external memory card.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
---------- Post added at 11:42 AM ---------- Previous post was at 11:12 AM ----------
I booted my pad with Your recovery and I can't see external SD card, so I expect that is the 2018.7.11 version. Am I right?
Hi again.
I found on another forum recovery that supports external sd-card. It's: recovery-TWRP-3.2.2-0713-MIPAD4-RuEn-Kirhe.img and it's working fine on my mi pad 4
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bartekm01 said:
Hi again.
I found on another forum recovery that supports external sd-card. It's: recovery-TWRP-3.2.2-0713-MIPAD4-RuEn-Kirhe.img and it's working fine on my mi pad 4
Click to expand...
Click to collapse
Hallo
Where did you find this TWRP?
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
bartekm01 said:
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
Click to expand...
Click to collapse
Tanks!!
Encryption
bartekm01 said:
Hi
Could You please write with recovery version is this? There are 2 recovery versions as of 2018.7.13 and 2018.7.11 with description like bellow:
2018.7.13 update
1. Fix the problem of not recognizing the external memory card.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
---------- Post added at 11:42 AM ---------- Previous post was at 11:12 AM ----------
I booted my pad with Your recovery and I can't see external SD card, so I expect that is the 2018.7.11 version. Am I right?
Click to expand...
Click to collapse
Hi,
Were you able to encrypt your Mi Pad after flashing the GSI?
jonklinger said:
Hi,
Were you able to encrypt your Mi Pad after flashing the GSI?
Click to expand...
Click to collapse
I didn't install gsi
Hi !
What's the difference between ab version and aonly version ?
EDIT: I flash today Android Pie GSI version.
After flashing GSI, you can found Open GAPPS unofficial here: https://builds.nezorfla.me/?dir=opengapps/pie/arm64
For no error 70, before flashing Open GAPPS, you must do that: Wipe -> Advanced Wipe -> Select System -> Repair or Change File System -> Resize File System -> Swipe to Resize
After, you can flash Open GAPPS, Magisk (for root) and Dm-Verity, and finally reboot
bartekm01 said:
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
Click to expand...
Click to collapse
Have you also flashed the misc file together with the TWRP? Or in this version there is no need?
snke said:
Have you also flashed the misc file together with the TWRP? Or in this version there is no need?
Click to expand...
Click to collapse
No only TWRP. I didn't flash misc - I think that misc changing region but I did not found any information about it.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
arkansis said:
Hi !
What's the difference between ab version and aonly version ?
EDIT: I flash today Android Pie GSI version.
After flashing GSI, you can found Open GAPPS unofficial here: https://builds.nezorfla.me/?dir=opengapps/pie/arm64
For no error 70, before flashing Open GAPPS, you must do that: Wipe -> Advanced Wipe -> Select System -> Repair or Change File System -> Resize File System -> Swipe to Resize
After, you can flash Open GAPPS, Magisk (for root) and Dm-Verity, and finally reboot
Click to expand...
Click to collapse
MiPad4 is only a partition. There is no b partition for seamless updates.
So far I didn't install any GSI but I've have installed China stable, developer and xiaomi.eu roms and I didn't have to resize system partitions. An ROMs are bigger maybe that's why You need to extend partitions but installation should end with error because of lack "b" partition
AICP 8.1 GSI works fine.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-t3839168
dzidexx said:
AICP 8.1 GSI works fine.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-t3839168
Click to expand...
Click to collapse
I'm agree, in my opinion It's the best GSI rom for MP4.
Root as well as Recovery galaxy a6plus (android pie).
REQ.
1-patched boot image.- https://drive.google.com/uc?id=1-d8HhTMc60cA3DExKe4xyUo2falMxeKf&export=download
2-Moded Recovery.- https://drive.google.com/file/d/10-3tGazfnt2RHZNkyx_RjmOn5YhChmkD/view?usp=drivesdk
3-Force Encryption Disabler.- https://drive.google.com/uc?id=1R7QyqUE4kadiCNciEDtcvJIoUSfFD7Ng&export=download
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
PLESAE BACUP ALL YOUR DATA BEFORE ROOTING AS AFTER ROOTING YOU WOULD HAVE TO RESTORE YOUR DEVICE ONCE.
AND make sure repartition is turned of in odin all the time.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1===ROOT
>turn oem unlocking on
>enter download mode and flash AP_a6plte_pie_root.img in AP SECTION.
>factory reset required at first boot do it.
>download and install latest magisk manager enjoy.
[WARNING =dont set any password,pin OR pattern on your device because it will give error of wrong pattern even if you try to unlock with the correct patern AND you cant login to your samsung account. {trying to solve these problems in next update}
2==RECOVERY
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
>enter download mode and flash a6plte_ONE_UI_TWRP.tar
>dont let system boot at first boot instead directly boot into TWRP
>change file system of data partition to fat and then back to exfat4
>again go to reboot and reboot to recovery and flash a6plte_PIE_Force_encryption_Disabler.zip
>wipe data reboot enjoy.
NOTE====PLEASE ROOT BEFORE FLASHING TWRP.
DM ME TO JOIN.
Parthkarmur said:
trying to solve these problems in next update
Click to expand...
Click to collapse
So your whole thing is useless? Rooting and installing TWRP was already possible, the problem was the lockscreen thing. Pretty pointless post if its not fixed.
pandavova said:
So your whole thing is useless? Rooting and installing TWRP was already possible, the problem was the lockscreen thing. Pretty pointless post if its not fixed.
Click to expand...
Click to collapse
Just try the recovery i uploaded once.(I recompiled IT)
And did we have force encryption disabler before for android pie?
====
one more thing i am working on knox right now if anybody intrested can help me link
https://forum.xda-developers.com/ga...inally-samsung-cheks-knox-bootloader-t3937529
My question is: Did you fix the thing that broke the lockscreen and the Samsung Account?
If not: Why did you rebrand TWRP when we already have a TWRP for the A6+ and why did you pretty much copy ashyx's Oreo Forced encryption disabler? You changed something in the fstab file and you removed ashyx's name in the updater-script.
Is there a problem with rooting a6+? That lockscreen etc?
joker.lg said:
Is there a problem with rooting a6+? That lockscreen etc?
Click to expand...
Click to collapse
Yes that problem does exists but if you have mistakenly set a password or pattern you can do this
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find) in TWRP RECOVERY:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Is it possible to get the device tree used to build this TWRP ?
Thank you in advance !
Parthkarmur said:
Yes that problem does exists but if you have mistakenly set a password or pattern you can do this
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find) in TWRP RECOVERY:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
I just want to know how to root a6+ without facing any problems? Or if i root with magisk which problems i will face ?
(I am not newbie for rooting but when i read comments i want to do it properly )
joker.lg said:
I just want to know how to root a6+ without facing any problems? Or if i root with magisk which problems i will face ?
(I am not newbie for rooting but when i read comments i want to do it properly )
Click to expand...
Click to collapse
In pie update samsung has used some new security method even if you flash custom kernal or you have
Set warrenty bit kernal . Elwarning you will not be able to login to samsung account even if you are not rooted.
And if you restore a data bacup of oreo using twrp
All the data would get restored except the samsung account.
Even when modifying a single file in sytem partition and then restoring stock bootimage(i.e. unrooting) would land you in boot loop
Parthkarmur said:
In pie update samsung has used some new security method even if you flash custom kernal or you have
Set warrenty bit kernal . Elwarning you will not be able to login to samsung account even if you are not rooted.
And if you restore a data bacup of oreo using twrp
All the data would get restored except the samsung account.
Even when modifying a single file in sytem partition and then restoring stock bootimage(i.e. unrooting) would land you in boot loop
Click to expand...
Click to collapse
Thank you for information. This is horrible samsung account not usable so we cannot use any rom except original ??
Parthkarmur said:
In pie update samsung has used some new security method even if you flash custom kernal or you have
Set warrenty bit kernal . Elwarning you will not be able to login to samsung account even if you are not rooted.
And if you restore a data bacup of oreo using twrp
All the data would get restored except the samsung account.
Even when modifying a single file in sytem partition and then restoring stock bootimage(i.e. unrooting) would land you in boot loop
Click to expand...
Click to collapse
I have 2 question ;
1)if i flash oreo official software than root my phone and use tnt rom will i lose Samsung account?
2) lets say i did #1 and i wanted to use official pie will i face any problem bcz of old root ?
joker.lg said:
I have 2 question ;
1)if i flash oreo official software than root my phone and use tnt rom will i lose Samsung account?
2) lets say i did #1 and i wanted to use official pie will i face any problem bcz of old root ?
Click to expand...
Click to collapse
1. No you can log in to your samsung account in oreo even if you are rooted
2.You will not face any problem unless your pie is rooted.
3. Be carefull you can trip knox(if its still not triped).
Parthkarmur said:
1. No you can log in to your samsung account in oreo even if you are rooted
2.You will not face any problem unless your pie is rooted.
3. Be carefull you can trip knox(if its still not triped).
Click to expand...
Click to collapse
your fstab still can trigger dm-verity...
/dev/block/bootdevice/by-name/system / ext4 ro,errors=panic wait,verify
should only "wait" without coma and verify
Hello everyone, problem.
after unbrick procedure
I am with miui 10 android 8.1.0.011019
boot in twrp format data wipe , yes
error failed to mont '/data' ( invalid argument )
install Magisk-v15.3 last line
failed to mont '/data' ( invalid argument)
... done
install MagiskManager-v5.5.5.apk
i don't get root permissions .
where am i wrong? thank you
patrizi said:
Hello everyone, problem.
after unbrick procedure
Click to expand...
Click to collapse
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
A thousand thanks . in order to perform the procedure I had to try 4 versions of MiFlash, to find the complete one .
i went back to miui 9.6 android 8.1.0 English / Chinese language .
now everything should be fine.
Thanks again, good evening everyone
same exact problem
failed to mont '/data' ( invalid argument)
... done
possible ?
NOSS8 said:
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
Click to expand...
Click to collapse
Drive with fastboot, I'm working on it
do I find on the forum? thank you
patrizi said:
Drive with fastboot, I'm working on it
do I find on the forum? thank you
Click to expand...
Click to collapse
What's the problem now?
NOSS8 said:
What's the problem now?
Click to expand...
Click to collapse
Good morning .
turned on this morning I find:
android system
there's an internal problem with your device. contact your manufacturer for details, ok. with audio notification
pressed ok everything seems to be OK / working
current firmware: miui 9.6 stable 9.6.3.0 (ocbcnfd). android version 8.1.0. android security patch level 2018-05-05
installed with MiFlash20210226 where I selected clean all in automatic configuration.
writes with 70 - 100 seconds the green line does not fill completely, shows reboot alert with pc notification sound, the phone is in fastboot
does not reboot, has not completed writing, the count does not stop I have waited up to 780 seconds does not reboot, does not
complete writing, stopped at that point, I unplugged the cable and restarted manually. as before failed to mont '/ data' (invalid argument)
TWRP always cactus Italian, previously I have tried others without Italian does not format DATA.
still write problem for protection? that zone (date) has not been overwritten.
you can do a deep format (eliminate protection problems) with fastboot or how?
thank you
patrizi said:
Good morning .
turned on this morning I find:
android system
Click to expand...
Click to collapse
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
NOSS8 said:
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
Click to expand...
Click to collapse
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
fixed format error , I install Magisk-v15.3 reboot does not install app MagiskManager-v5.5.5.apk goes into error starts in recovery
I try to delete everything again without errors ,
reboot, delete everything again
install lineageos without errors restart ,
vibrates does not turn on, I also tried detach / attach battery it's bricked now,
procedure for recovery
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
searched for info by mistake
everything is correct, i made no mistakes, i have to try with latest version of flasch tool
I can not understand . thank you
patrizi said:
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
Click to expand...
Click to collapse
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
NOSS8 said:
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
Click to expand...
Click to collapse
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
patrizi said:
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
Click to expand...
Click to collapse
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
NOSS8 said:
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
Click to expand...
Click to collapse
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
patrizi said:
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
Click to expand...
Click to collapse
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
NOSS8 said:
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
Click to expand...
Click to collapse
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
error : status_sec_img_too_large (0xc0020005)
hint
Verified boot in enabled .
Please download signed image(cust-verified.img) or disable verified boot .
I can't find info to disable verification.
the file is safe and I tried like this:
disconnect phone, uncheck write files before the error
connect phone, write, answer: writing completed disconnect phone
invert selection of file writing boxes (check for no selection errors)
connect phone write
writing completed disconnect phone
turn on phone in fastboot mode
turns on and enters fastboot
SP_Flash_Tool does not connect to the phone (first attempt)
test connection with Mi Flash, here it is ok
select file to write,
ok start writing never ends.
fastboot always ok
I'll try again tomorrow.
i can't understand these writing problems
patrizi said:
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
Click to expand...
Click to collapse
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
I have edited, not complete writing, I insert log
thank you
NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\Miflash\cactus11
if you manage to unlock it use this method post#11
NOSS8 said:
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\cactus11
if you manage to unlock it use this method post#11
Click to expand...
Click to collapse
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
patrizi said:
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
Click to expand...
Click to collapse
You have selected:
[12:37:55 bf4b07ea7d2a]:script :E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global\flash_all_lock.bat
result
[12:37:56 bf4b07ea7d2a]:err:FAILED (remote: not allowed in locked state)
You've made this mistake before.
Right path; E:\Miflash\cactus11
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}