{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Instructions
For now you can only boot TWRP you do this by executing the command:
fastboot boot
Bugs: slow bootup
Downloads
Latest v11-10-21
twrp-11-10-21.img
drive.google.com
twrp-pstar-06-10-21.img
drive.google.com
Old
twrp-pstar.img
drive.google.com
Donations
What's new:
Fixed Vibration
Fixed Bootctrl
Contributors
@Electimon, betaxab ko_hi
Version Information
SourceCode: https://gitlab.com/nihonnofanboi/twrp-motorola-pstar
Version Information
Status: Stable
Release Date: October-2-2021
Last Updated: October-11-2021
thnks
Say does this TWRP allow access to data partition (encrypted)?
Right now I'm running a GSI with vendor untouched so data is encrypted. It would be great if it could (after providing credentials), so backing up stuffs would become easier.
LSS4181 said:
Say does this TWRP allow access to data partition (encrypted)?
Right now I'm running a GSI with vendor untouched so data is encrypted. It would be great if it could (after providing credentials), so backing up stuffs would become easier.
Click to expand...
Click to collapse
Yes the decryption works at least on stock rom untested on GSI and unsure about A12 roms
ko_hi said:
Yes the decryption works at least on stock rom untested on GSI and unsure about A12 roms
Click to expand...
Click to collapse
Just tested. FBE can be correctly decrypted using User 0's security credentials, even though I'm using GSI. I think the encryption is enable/enforced by vendor fstab config and performed independent from ROM itself.
When I start TWRP I see an error saying unable to mount /product (block device required). For GSI usage, this is intended, as it's necessary to remove that ~2.7GB partition (erasing it and set its size to zero) in order to provide enough space in Super to resize and flash the GSI. I don't know if it's possible to suppress this error, though it's harmless.
By the way, there are two Super options when backing up, one simply says "Super", the other says "Super (system, system_ext, product, vendor)". Are the two options different?
Well, despite this TWRP is currently not flashable (boot-only), it looks good enough. I really hope it could be installed and also fastbootd-capable in the future.
LSS4181 said:
Just tested. FBE can be correctly decrypted using User 0's security credentials, even though I'm using GSI. I think the encryption is enable/enforced by vendor fstab config and performed independent from ROM itself.
When I start TWRP I see an error saying unable to mount /product (block device required). For GSI usage, this is intended, as it's necessary to remove that ~2.7GB partition (erasing it and set its size to zero) in order to provide enough space in Super to resize and flash the GSI. I don't know if it's possible to suppress this error, though it's harmless.
By the way, there are two Super options when backing up, one simply says "Super", the other says "Super (system, system_ext, product, vendor)". Are the two options different?
Well, despite this TWRP is currently not flashable (boot-only), it looks good enough. I really hope it could be installed and also fastbootd-capable in the future.
Click to expand...
Click to collapse
I'll look into it later! AFAIK Fastbootd is working (I think I've flashed this twrp to confirm it) regarding the backup options I can't tell I must check! But thanks for pointing out! More bugs coming in and needs to be resolved!
Updated TWRP will come later today or tomorrow
Fixed Boot time to twrp
instead of 50s+ it's now dropped down to 14-16s
ko_hi said:
I'll look into it later! AFAIK Fastbootd is working (I think I've flashed this twrp to confirm it) regarding the backup options I can't tell I must check! But thanks for pointing out! More bugs coming in and needs to be resolved!
Click to expand...
Click to collapse
ko_hi said:
Updated TWRP will come later today or tomorrow
Fixed Boot time to twrp
instead of 50s+ it's now dropped down to 14-16s
Click to expand...
Click to collapse
Good news. You said you "flashed" this TWRP to confirm fastbootd functionality so... does flashing work? As you currently only recommend booting it instead of flashing, I'm not sure.
If fastbootd also works, I really hope if I could actually flash TWRP at some point, as it's more convenient to make and manage backups with it.
LSS4181 said:
Good news. You said you "flashed" this TWRP to confirm fastbootd functionality so... does flashing work? As you currently only recommend booting it instead of flashing, I'm not sure.
If fastbootd also works, I really hope if I could actually flash TWRP at some point, as it's more convenient to make and manage backups with it.
Click to expand...
Click to collapse
I'm 100 sure I've tested it but i can confirm it soon again
Edit latest test us broken but i see the cause
thanks ,but i have a question . is this twrp forever in Edge 20 pro (or edge s pro (china)) ? i tried ，now ,my phone is bricked
sexyDog said:
thanks ,but i have a question . is this twrp forever in Edge 20 pro (or edge s pro (china)) ? i tried ，now ,my phone is bricked
Click to expand...
Click to collapse
Only tested on edge 20 pro
ko_hi said:
Only tested on edge 20 pro
Click to expand...
Click to collapse
Tested on the Moto Edge S Pro as well.
sexyDog said:
thanks ,but i have a question . is this twrp forever in Edge 20 pro (or edge s pro (china)) ? i tried ，now ,my phone is bricked
Click to expand...
Click to collapse
I don't think this TWRP is safe to flash yet, but you can boot. I have booted this on my own Edge S Pro and it worked fine... so not sure what caused it to brick.
LSS4181 said:
I don't think this TWRP is safe to flash yet, but you can boot. I have booted this on my own Edge S Pro and it worked fine... so not sure what caused it to brick.
Click to expand...
Click to collapse
Only temp boot is working, I've managed to boot TWRP as boot but it crashed system quite good!
Hello, developer！I flash your twrp file，it’s good on my device（moto edge s pro china version），very thank you ,but it just temp working,it's a little disappointing. I wrote a script file to solve this problem，reboot to recovery，need root permission , and i not find recovery partition,maybe in bootloader.img?
my script
Bash:
if [ -f "/sdcard/boot_a.img" ];then rm -rf /sdcard/boot_a.img;fi
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/sdcard/twrp-11-10-21.img of=/dev/block/by-name/boot_a
reboot
MrZZZ123 said:
Hello, developer！I flash your twrp file，it’s good on my device（moto edge s pro china version），very thank you ,but it just temp working,it's a little disappointing. I wrote a script file to solve this problem，reboot to recovery，need root permission , and i not find recovery partition,maybe in bootloader.img?
my script
Bash:
if [ -f "/sdcard/boot_a.img" ];then rm -rf /sdcard/boot_a.img;fi
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/sdcard/twrp-11-10-21.img of=/dev/block/by-name/boot_a
reboot
Click to expand...
Click to collapse
From what I recall our device doesn't have a standalone recovery partition, so it's inside boot.img.
Now that Motorola has released the kernel source code it might be possible to build a kernel with TWRP included.
LSS4181 said:
From what I recall our device doesn't have a standalone recovery partition, so it's inside boot.img.
Now that Motorola has released the kernel source code it might be possible to build a kernel with TWRP included.
Click to expand...
Click to collapse
This news is a hundred years old, but the development of TWRP has stopped and it seems forever...
ko_hi said:
Team Win Recovery Project (TWRP) — это настраиваемый образ восстановления программного обеспечения с открытым исходным кодом для устройств на базе Android. Он предоставляет интерфейс с сенсорным экраном, который позволяет пользователям устанавливать сторонние прошивки и создавать резервные копии текущей системы, функции, которые часто не поддерживаются стандартными образами восстановления. Поэтому он часто устанавливается при рутировании устройств Android, хотя его установка не зависит от рутируемого устройства.
инструкции
На данный момент вы можете загрузить только TWRP, выполнив команду:
быстрая загрузка
Баги: медленная загрузка
Загрузки
Последняя версия 11-10-21
twrp-11-10-21.img
drive.google.com
twrp-pstar-06-10-21.img
drive.google.com
Старый
twrp-pstar.img
drive.google.com
Пожертвования
Какие новости:
Фиксированная вибрация
Фиксированный Bootctrl
Авторы
@Electimon, бетаксаб ko_hi
Информация о версии
Исходный код: https://gitlab.com/nihonnofanboi/twrp-motorola-pstar
Информация о версии
Статус: Стабильный
Дата выхода: 2 октября 2021 г.
Последнее обновление: 11 октября 2021 г.
Click to expand...
Click to collapse
Good time, tell me if there will be further development?
otmitia said:
Доброго времени, подскажите, будет ли дальнейшее развитие?
Click to expand...
Click to collapse
XDA is an english speaking site. You can type a message in your language, but you must provide a translation as well.
C:\Users\User\Desktop\Bon\ADB\platform-tools>fastboot flash recovery C:\Users\User\Desktop\Bon\ADB\platform-tools\twrp-11-10-21.img.img
Sending 'recovery' (90216 KB) OKAY [ 2.084s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
C:\Users\User\Desktop\Bon\ADB\platform-tools>
HEY FELLAS, HOW TO FIX THIS KIND OF ISSUE?
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"
}
This is only for Honor 8 Pro (DUK)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-duk.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official PHH Superuser Beta 310[/U][/B]
1. download and flash [URL="http://superuser.phh.me/superuser-r310-beta.zip"]official PHH Superuser Beta 310[/URL]
2. install "Phh Superuser" from Google Play
3. Enjoy!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_duk/releases/download/3.1.1-1/twrp-3.1.1-1-duk.img"][U]download twrp-3.1.1-1-duk.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 25. June 2017
Q: which H8 Pro models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with fileencryption disabled in fstab
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin/android_device_honor_duk
Version Information
Status: Beta
Created 2017-06-23
Last Updated 2017-06-25
Reserved
Changelog
Code:
[B]TWRP 3.1.1-1[/B]
* fix twrp on emmc based devices
Man that was fast. Will definitely flash this after I get my H8 Pro.
Sent from my Honor 8 using XDA Labs
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
blattes86 said:
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
Click to expand...
Click to collapse
this should work for every h8 pro utilizing emmc storage:
https://drive.google.com/open?id=0BxWP2gF_0Bd_OHBPWDctZmJCanc
It has been tested.
Regards
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
OldDroid said:
this should work for every h8 pro utilizing emmc storage:
It has been tested.
Regards
Click to expand...
Click to collapse
I flashed it, it works fine.
Thanks
adriansticoid said:
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
Click to expand...
Click to collapse
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
-=MoRpH=- said:
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
Click to expand...
Click to collapse
That's great news. Thanks for confirming. :highfive:
Sent from my Honor 8 using XDA Labs
I flashed emmc version and supersu. For going in twrp I've to clic in the middle of the volume button and the power on.
Interesting, i tried to install it but i'm stuck with installion...i know how to enter fastboot mode with phone plugged to my computer with android sdk on, but the adb files look to be missing when i check with cmd...
Can anyone here give a quick tutorial ? Thanks
New Version (3.1.1-1) available - You can find more infos in OP.
This release fixes partition mounting on emmc 5.1 based devices
Source code is now also up and can be built!
https://github.com/OpenKirin/android_device_honor_duk
Regards
Wow that was faster than I could learn to do it.
Great job. May I ask how you got the important informations to build this?
Did you inject su into the image to gain root and then read all the detailed data through terminal or adb or root file explorer?
Just asking cause i train my brain more and more in my spare time and want to get behind the knowledge base to learn. :good:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do I need to choose?
Cheers
Would this work on the Chinese V9 variant?
smouker said:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do IP need to choose?
Cheers
Click to expand...
Click to collapse
Format the whole internal storage to remove encryption.
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
can I restore Data via TWRP without problems?
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
smouker said:
can I restore Data via TWRP without problems?
Click to expand...
Click to collapse
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
blattes86 said:
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
Click to expand...
Click to collapse
What do you mean to restart the partition is new encrypt?
adriansticoid said:
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
What do you mean to restart the partition is new encrypt?
Click to expand...
Click to collapse
sorry for my bad english.
After restart the phone...
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Decryption
Installation :
Procedure:
1.Boot into TWRP(using old twrp that u guys use)
2.Go to wipe option (optional reason on 3 rd step)
3.Select format data ((if you want to make internal storage readable)(This will erase all data on internal storage)
4.Then go back and flash twrp installer from the install option.
5.After installation,go to reboot option (select recovery) and reboot.
6.Done!
Download Link : Download
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP-3.2.3-0 Permanent Installer [20190122], Tool/Utility for the Nokia 7 Plus
Contributors
nageen9211, sriram prakhya
Source Code: https://github.com/Ram9199/TWRP_Basil_Device_tree
Version Information
Status: Stable
Created 2019-01-22
Last Updated 2019-01-22
nageen9211 said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Decryption
Installation :
Procedure:
1.Boot into TWRP(using old twrp that u guys use)
2.Go to wipe option (optional reason on 3 rd step)
3.Select format data ((if you want to make internal storage readable)(This will erase all data on internal storage)
4.Then go back and flash twrp installer from the install option.
5.After installation,go to reboot option (select recovery) and reboot.
6.Done!
Download Link : Download
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP-3.2.3-0 Permanent Installer [20190122], Tool/Utility for the Nokia 7 Plus
Contributors
nageen9211, sriram prakhya
Source Code:https://github.com/Ram9199/TWRP_Basil_Device_tree
Version Information
Status: Stable
Created 2019-01-22
Last Updated 2019-01-22
Click to expand...
Click to collapse
Make it normal flash able and also provide order twrp link
Great work bro.:good:
Purak6 said:
Make it normal flash able and also provide order twrp link
Click to expand...
Click to collapse
Normal flashable won't work with every rom , as every one is using different variant and different security patches .. that's why I have made it ...
nageen9211 said:
Normal flashable won't work with every rom , as every one is using different variant and different security patches .. that's why I have made it ...
Click to expand...
Click to collapse
And older twrp link ?
It's possible to use with TA-1055 or isn't tested on that variant?
death_jax said:
It's possible to use with TA-1055 or isn't tested on that variant?
Click to expand...
Click to collapse
test it and report. Bdw, android pie is preffered. It is reported that it stuck at boot logo on oreo roms
Purak6 said:
And older twrp link ?
Click to expand...
Click to collapse
i dont know about them, this is the fresh twrp . and we will maintain this only..
nageen9211 said:
[...] TWRP-3.2.3-0 Permanent Installer [20190122] [...]
Click to expand...
Click to collapse
can you please clarify what is mean "Permanent Installer"?
1) is this TWRP universal for any Android9 version? does not require exactly version?
2) is persistend after OTA update?
i ask because N7p don't have separate recovery partition and use hybrid boot for boot+recovery, this TWRP is not in boot partition?
k3dar7 said:
can you please clarify what is mean "Permanent Installer"?
1) is this TWRP universal for any Android9 version? does not require exactly version?
2) is persistend after OTA update?
i ask because N7p don't have separate recovery partition and use hybrid boot for boot+recovery, this TWRP is not in boot partition?
Click to expand...
Click to collapse
yes, This installer will unpack your boot.img from your current rom , and patch the twrp in it and repack it.
it works on almost all pie roms . have problem on oreo gsi .
and i think.. as long as boot partition is not affected by ota (which most of the times is affected ) twrp will persist. other wise u have to repatch your boot.img with this installer.
How to install twrp recovery on Nokia tell me set by step
bharath moram said:
How to install twrp recovery on Nokia tell me set by step
Click to expand...
Click to collapse
You can use this me howto for Magisk install:
https://forum.xda-developers.com/nokia-7-plus/help/pie-october-update-failed-t3862758/post78285662
Where is say Magisk.zip you use TRWP installer zip from first post in this thread..,
Good work, sir.
By the way, does it have format data to f2fs support? TWRP images for this device out there doesn't have.
Lot of warnings in recovery.log
Thanks for making this!
I'm getting lots of warnings like this one:
Code:
WARNING: linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
Should I be worried about TWRP correct functioning?
Busybox seems to be all well and good though!
k3dar7 said:
You can use this me howto for Magisk install:
https://forum.xda-developers.com/nokia-7-plus/help/pie-october-update-failed-t3862758/post78285662
Where is say Magisk.zip you use TRWP installer zip from first post in this thread..,
Click to expand...
Click to collapse
Hi, thanks for this.
But after I fastboot boot the twrp boot img, all the folder names in TWRP are strange, like they're encrypted. How do I get around this?
Read step 3 in the OP. You have to format data.
I've found that using another twrp image to boot (not flash) it decrypts the data by asking the pattern I've set up in the os.
Now I want to ask the dev @nageen9211 if he can use that image to make this script.
ban.codrut said:
Read step 3 in the OP. You have to format data.
I've found that using another twrp image to boot (not flash) it decrypts the data by asking the pattern I've set up in the os.
Now I want to ask the dev @nageen9211 if he can use that image to make this script.
Click to expand...
Click to collapse
Thanks for the reply - actually I tried the OP originally, but formatting data got rid of my google play services as well, and I couldn't use my phone at all as a result, because a popup saying "google play services stopped working"/"google battery saver had stopped working" kept popping up repeatedly.
I had to reflash using OST and start over again. Which is why I was interested in another method without formatting data
Unless there is a way around fixing the Google Play services issue after formatting data?
Iam using Nokia 7 pLus rom having Android pie how to install twrp recovery tell step buy step
bharath moram said:
Iam using Nokia 7 pLus rom having Android pie how to install twrp recovery tell step buy step
Click to expand...
Click to collapse
If you have unlocked bootloader, howto i write before some mess on this page of this thread.. then first step is read this thread
I saw that on 15 of april was out the 3.3.0-0 of TWRP...how can we get it?
There is a very good changelog, especially for our A/B device(s):
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
Freshly built for cepheus twrp 3.3.0
Now working with standard builds of opengapps no need for the custom build.
Known issues:
Global FW only unless you flash matching dtbo and boot.img
Does not support encryption
Instructions: unzip and flash the image via fastboot.
Changelog:
v11 hope this fixes backup/restore issues some were having
TWRP v12 Download:
https://www.androidfilehost.com/?fid=6006931924117882399
Kernel source
https://github.com/randomblame/android_kernel_xiaomi_sm8150/tree/twrp
serious things start ! Keep it up
stuck at logo screen..then bootloop. flashed recovery-mi9-3.2.3.img right away and i'm back to recovery.
impressive gapps arm64 compatibility with all recoveries collected:
recovery-mi9-3.2.3.img - nope
twrp-3.2.3-6-cepheus-mauronofrio.img - nope
twrp-3.2.3-10-cepheus-mauronofrio.img - nope
Twrp_3.3.0_Cepheus.img - nope
twrp_cepheus.img - nope
twrp_en.img -nope
doggydog2 said:
stuck at logo screen..then bootloop. flashed recovery-mi9-3.2.3.img right away and i'm back to recovery.
impressive gapps arm64 compatibility with all recoveries collected:
recovery-mi9-3.2.3.img - nope
twrp-3.2.3-6-cepheus-mauronofrio.img - nope
twrp-3.2.3-10-cepheus-mauronofrio.img - nope
Twrp_3.3.0_Cepheus.img - nope
twrp_cepheus.img - nope
twrp_en.img -nope
Click to expand...
Click to collapse
I'll throw the stock kernel in and that should fix it. This one seems to have an issue with some devices that I haven't figured out
randomblame said:
I'll throw the stock kernel in and that should fix it. This one seems to have an issue with some devices that I haven't figured out
Click to expand...
Click to collapse
thanks. the upstream kernel you published also bootlooped. is it the one you will push in it?
doggydog2 said:
thanks. the upstream kernel you published also bootlooped. is it the one you will push in it?
Click to expand...
Click to collapse
New build is up with the stock kernel. Should be more compatible. I still have people running off revos who say it will not boot. I believe there is a partition layout difference. This has been tested to work with GLOBAL firmware and gsi's on top
randomblame said:
New build is up with the stock kernel. Should be more compatible. I still have people running off revos who say it will not boot. I believe there is a partition layout difference. This has been tested to work with GLOBAL firmware and gsi's on top
Click to expand...
Click to collapse
v2twrp is not booting with revos, stucking at bootlogo, will go back to previous twrp
portfolio said:
v2twrp is not booting with revos, stucking at bootlogo, will go back to previous twrp
Click to expand...
Click to collapse
Revos and anything based on the china firmware kills it dead. I'm gonna try to pull the kernel out of the china fw next and see if that is compatible with both global and china firmware layouts
Please be sure encryption has been disabled before testing otherwise it's not going to load
Backup works?
Hi @randomblame for the decryption/encryption problems, if it doesn't work just disable it in compilation process hiding TW_INCLUDE_CRYPTO := true and others crypto flags.
For the clock you can see this commit: https://github.com/mauronofrio/andr...mmit/3647d514f905764e2d095a54213e4d52085d28da
Maybe you will need to set it to 84 more or less.
For adb, you should build the twrp with -eng and not with -userdebug, userdebug build is not more used since android 8.1
I didn't find a device tree source so i decided to write here.
Hope this will help you fix your problems
Thank you so much, finally a recovery with working gapps installation WOHOO!
Tested with https://treble.andro.plus/ FolokoROM with newest opengapps mini package
EDIT: Sorry its not working, the gapps package was flashed successfully, but after a reboot there were no gapps installed. ?
MindtheGapps works but there is no faceunlock
Is Nandroid working on this one?
mauronofrio said:
Hi @randomblame for the decryption/encryption problems, if it doesn't work just disable it in compilation process hiding TW_INCLUDE_CRYPTO := true and others crypto flags.
For the clock you can see this commit: https://github.com/mauronofrio/andr...mmit/3647d514f905764e2d095a54213e4d52085d28da
Maybe you will need to set it to 84 more or less.
For adb, you should build the twrp with -eng and not with -userdebug, userdebug build is not more used since android 8.1
I didn't find a device tree source so i decided to write here.
Hope this will help you fix your problems
Click to expand...
Click to collapse
Hey thanks for the tips clock needed an offset of 80, adb is fixed and hopefully encrypted devices will not fail to boot and allow /data to be formatted. Backup seems to be working.
The problem with the opengapps packages is that it is not set up for system as root I'm pulling down their git and I'll build one to host as well
v4 test:
MTP: working (auto mount)
ADB sideloading: working
OTG: no (( -> only one time setup via sdcard or PC sideloading
Encryption: no
OpenGapps64: yes (after resize thou)
Backup: not tested
Reboot to fastboot: ok
Reboot to recovery: ok (not with fastboot thou, don't know why this is common)
Advanced functions={Copy log,ADB sideload,Terminal,File Manager,Reload Theme,Fix Contents}
Partitions mountable={System,Vendor,Data,Cache,persists,cust,metadata,sdcard}
The problem with the open_gapps package is here:
https://github.com/opengapps/opengapps/commit/82538ba5b07e3093a11d583463b07a848a4a32b9#diff-4b4d756dd3b2a232970b47588e486edd
The device is not detected as system as root or a/b I'm gonna try to put together a package for us.
if [ -n "$(cat /proc/cmdline | grep slot_suffix)" ];
then
ui_print "- AB DEVICE DETECTED";
device_abpartition=true
SYSTEM=/system/system
VENDOR=/vendor/vendor
elif [ -f /system/system/build.prop ];
then
ui_print "- SYSTEM_AS_ROOT DEVICE DETECTED";
device_abpartition=true
SYSTEM=/system/system
VENDOR=/vendor/vendor
else
device_abpartition=false
SYSTEM=/system
VENDOR=/vendor
fi
this should work
*edit ok toolbox is not properly linked in twrp so these changes will do nothing for now. I did compile a version of opengapps that DOES install through this recovery and will link it in the OP I also modified it so that it should pass the architecture test that it fails in the china twrp if anyone prefers that one. It is only micro but if there is demand maybe I can make a couple options but I would prefer to find a better fix.
The working version of gapps is here: https://www.androidfilehost.com/?fid=1395089523397955923
also started working on this for fun
{
"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"
}
v4 still not booting into recovery with ROS
portfolio said:
v4 still not booting into recovery with ROS
Click to expand...
Click to collapse
ok, I have to correct, it is working with ROS, this time I flashed v4 over fastboot and it boots into recovery (1st I flashed v4 in my previous TWRP, so one has to use fastboot command to flash this TWRP).
Also this TWRP is really nice to understand and to handle, Thx for that, I'll try corrected gapps later, also no problem to mount system and seeing gapps have to install into /system/system
:good::good::good:
anyway strange: booting into recovery only succeeds when usb-connected to a PC over adb command/vol up+pwr/on-off menu,
when not usb-connected, no way to boot into recovery, always boots into system after a short waiting time showing the mi logo
???
also: other TWRPs show the partition /system/system as /system_root/system and /vendor/vendor just as /vendor and I suppose
the downloadable opengapp-version will only work with v4 twrp and not with other twrps mounting partitions in a different way
randomblame said:
also started working on this for fun
Click to expand...
Click to collapse
Can't wait to test, thanks for working on it!
{
"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"
}
NOTE: Decrypting data is not currently working. This is my initial release and i'm planning to fix as many bugs i can. When it's stable enough , only then i will push to official
Team Win Recovery Project 3.x, or twrp3 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.
Code:
/*
* I am not responsible for bricked devices,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Sources: https://github.com/TeamWin
Device tree: https://github.com/Suicide-Squirrel/android_device_huawei_charlotte
Download
Flashing:
Code:
fastboot flash recovery_ramdisk recovery.img
Special thanks to @Dees_Troy for the Huawei Blanc device tree, which this is based on.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL]TWRP:Team Win Recovery Project[P20 PRO], ROM for the Huawei P20 Pro
Contributors
kessaras, steadfasterX
ROM OS Version: 9.x Pie
ROM Firmware Required: v195 or newer
Based On: OMNIROM,TWRP
Version Information
Status: Beta
Created 2019-06-14
Last Updated 2019-06-14
I will use this post to share my work
Sorry for making another TWRP thread, but i've had enough with our current TWRP.
I have enabled logcat and strace.
This is the initial release so keep in mind that it has (probably) currently the same bugs with the official.
The only difference is that you can grab any kind of log and help me improve it and only when it will be stable enough , only then, i will push to the official.
------------------------------------------------------------------------------------------------------
VERSION: recovery-3.3.1-0-b.img | date: 15-06-2019
FIXED:
1. mounts correctly all partitions
2. backup to usb-otg enabled
3. backup all partitions except data (i need to fix decryption)
4. restore fixed.
5. ADB sideload fixed.
6. you can flash a kernel and a recovery .img directly inside TWRP. No more rebooting to bootloader.
NOT TESTED:
1. I don't know about format yet. i haven't tested it because im not ready to format yet.
If anyone is about to format anyway, please after format do:
Code:
adb pull /tmp/recovery.log
and
Code:
adb logcat -b all > logcat.txt
And send me these two logs so that i can fix format and we don't need stock Huawei recovery anymore.
2. Can't flash GAPPS exactly like in the official.
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
FIXED:
1. GAPPS flashing fixed. Same goes for any other flashable package.
2. backup data and wipe data are fixed. (not tested restore yet)
NOT FIXED:
1. Even if wipe data and backup data are fixed, and even though we can restore data ! Sadly there are bugs when we wipe data or perform a restore. Until i fix (if i fix it) decryption, please keep using the stock Huawei recovery to format your data and avoid restoring data.
ISSUE: Data partition is fine and it sais that it's 128gb but apps think that we don't have enough "free space". It may just be an issue in vold too in the rom where i tested it.
VERSION: recovery-3.3.1-0-d + e.img | date: 20-06-2019
FIXED:
- minor bug fixes for stability
- added nvme partition which is needed during the decryption
- adb sideload fixed. No need to push and install
NOT FIXED:
- decryption
- format
It's great news man. Looking forward to your further progress! Fully functional twrp is the juice.
Amazing, hope we can have finally fully functional twrp
Thanks
aoryx said:
Amazing, hope we can have finally fully functional twrp
Thanks
Click to expand...
Click to collapse
adb sideload and gapps flashing are fine too.
Format data needs to be fixed and decryption
Legend.
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
dladz said:
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
Click to expand...
Click to collapse
not yet. gimme some hours. im trying to fix something and then ill share a new build.
i have 2 errors left:
1. linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/sh" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
That problem is in bionic.
in bionic/linker/tests/linker_config_test.cpp or in
bionic/linker/ld.config.format.md. But i can't figure it out yet. That will fix the gapps flashing issue with latest TWRP and mine.
What's strange is that it doesn't happen to everyone. So i'm confused.
Me i can't flash any gapps, when others reported to me that they can.
Click to expand...
Click to collapse
We can finally backup data partition. And we can use MTP. And we can restore data. And everything is ok, BUT
i still can't decrypt the internal storage. it's a work in progress.
Click to expand...
Click to collapse
At least wait for 1. otherwise you may need 3.2 official TWRP to flash gapps and it's boring to flash other TWRP every time.
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
titi66200 said:
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
Click to expand...
Click to collapse
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
kessaras said:
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
Click to expand...
Click to collapse
stop working in RL the PR is waiting for you :laugh:
https://github.com/Suicide-Squirrel/android_device_huawei_charlotte/pull/1
as said: needs testing ofc as I do not own that device
.-
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
Sounds painful, the other twrp does something similar..
Would the chap who made the unofficial one be able to assist?
His threads looked but he's still active .
Feel for you mate, sounds like a massive ballache.
kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Lukas do not wipe data at an encrypted and non-decrypted partition.
When you will boot again to the rom, the system will think that data is clean so it will attempt to encrypt the already encrypted.
At settings you will see that you have 128gb data partition but you will have only a few mb actually.
wipe data does NOT remove encrption, only a format can remove the encryption.
djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Did it actually wipe though? If it didn't the ROM may still boot as it would simply be a dirty flash.
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
pmatj said:
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
Click to expand...
Click to collapse
the only way to know that is to flash it and test it.
what are you afraid of ? if twrp doesn't boot, you can flash back the stock huawei recovery again.
>> the device won't have any issues if twrp is not for that device <<
It should work if it can boot. The only difference is our resolution. So if you see TWRP boot , then it's ok to use it.
* It will probably work because i don't force any specific resolution here.
But if it doesn't , change this to your resolution https://github.com/Suicide-Squirrel...43104c493e172dc469d7838153/BoardConfig.mk#L53
and build TWRP for p20 lite
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
pmatj said:
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
Click to expand...
Click to collapse
If it's a/b try talking to OnePlus 6/6t recovery.
They have a/b there too and if the dev answers to you then you probably have it
{
"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"
}
Lineage-os 18 for Redmi Note 3 pro, ported from Mi Max by @nasim7500
What's working:
----------------
Boot
Bluetooth
Camera / Camcorder
Fingerprint Sensor
FM Radio
GPS
RIL
WiFi
WiFi Hotspot
USB (ADB/MTP)
Video Playback
Touch
Sensors
Bugs:
-------
DT2W (if you need this then install magisk & use any kernel manager app)
Some hidden bug there maybe, not sure
Installation instructions:
---------------------------
Install a compatible Recovery (orangeFox recomended)
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM & Gapps then reboot
After boot, again reboot one more time
Optional: Install Magisk for Root.
Special thanks to these guys (For help me)
----------
@MrJarvis698, @trax85, @Jrchintu @Magicxavi
Also This guy for Testting this Rom
-----------------
@JeSsyB007, @H39AR
BUG FIXING FULL CREDIT: OUR GOD (Allah)
NOTE:
We are not responsible for bricked devices, dead sdcard, etc
If you find any other bug you can tell me, I will try to fix but no promises
All mejor bug fixed, now enjoy!!
if you face rendom reboot problem then just format data partition after install this Rom, from twrp thnx to @QantivirusP & @Ardityo
you want selected text feature in normal version? click here
This is my first post in xda so if somthing i wrong then tell me
Still alive poor battery backup then just flash this kernel
chines character kernel have obb bug
SCREENSHOTS:
A11 screen shot - Google Drive
drive.google.com
ROM Download Link:
------------------
lineage-os-18.1_ported_for_kenzo_by-nasim7500 25-8-2021.zip
FlameGApps-11.0-basic-arm64-20210822.zip
[MODED_ROM] lineage-os-18.1_ported_for_kenzo_by-nasim7500 24-8-2021.zip
Changelogs
25/08/2021
Fixed safetynet by default thnx to @Rajat_Prime & @sairam60
Fixed Fingerprint won't wakeup screen
Fixed weak wifi signal
Fixed weak vibration
Fixed poor battery backup again (cause min cpu value set to high) thnx to @trax85
Obb Fixed Big Thnx to @trax85 for compiling new kernel && @alonsoj636 & @Rajat_Prime for give me the Commit file
>>>>> MODE VERSION <<<<<
Gapps included
added selected text feature by default
add Solid explorer to system app thnx to @SkullMax01
1/06/2021
Fixed Camera
Fixed Fingerprint
Fixed FM Radio.
Fixed Heaing Issue
fixed Poor Battery backup
Fixed TWRP Installation error on kenzo device thnx to @nshussain (for findout why this problem)
Rom ported by nasim7500.
Guys if you like my work plz press like button & support to my helper or respect him, thank you..Now Enjoy!!
And Last i Want to say Thank you so much from my heart for All Kenzo dev for your hard & awseome Work...
Nice work bro..
ullas377 said:
Nice work bro..
Click to expand...
Click to collapse
Thank you bro.
nice
I am getting an error:
E1001 failed to update system image.
update process ended with error 1
I tried with the latest TWRP and OrangeFox recovery,
Formated data,
Flash stock boot.img.
Bootloader is unlocked.
Flashed stock Rom using the Mi Flash tool.
Nothing worked.
Other roms like RR and LineageOS 17.1 works fine.
Can anyone please suggest on this? Thanks.
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
Thanks
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
Thanks
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
nshussain said:
I am getting an error:
E1001 failed to update system image.
update process ended with error 1
I tried with the latest TWRP and OrangeFox recovery,
Formated data,
Flash stock boot.img.
Bootloader is unlocked.
Flashed stock Rom using the Mi Flash tool.
Nothing worked.
Other roms like RR and LineageOS 17.1 works fine.
Can anyone please suggest on this? Thanks.
Click to expand...
Click to collapse
1st flash orangefox recovery 2nd boot to orangefox recovery 3rd wipe system,data,catch,vendor 4th format data by type yes from orangefox recovery 5th reboot to recovery 6 try flashing Rom. & Report back here, thank you
nasim7500 said:
1st flash orangefox recovery 2nd boot to orangefox recovery 3rd wipe system,data,catch,vendor 4th format data by type yes from orangefox recovery 5th reboot to recovery 6 try flashing Rom. & Report back here, thank you
Click to expand...
Click to collapse
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the issue?
Dnt
nshussain said:
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the is
Click to expand...
Click to collapse
nshussain said:
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the issue?
Click to expand...
Click to collapse
Don't know but this zip install in my device just fine without any error,,, okay I will update my post letter && fix this issue
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
nshussain said:
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
Click to expand...
Click to collapse
Could you please tell me that how did you reduced the img size? I'm facing at the same error says
update process ended with error 1.
xykshun said:
Could you please tell me that how did you reduced the img size? I'm facing at the same error says
update process ended with error 1.
Click to expand...
Click to collapse
Install Ubuntu os on a VM, copy img file you converted over there.
On terminal browse to location where you saved img and run commands:
e2fsck -f -y system.img
resize2fs -M system.img
Copy img from Ubuntu to computer and then phone. (I used internet, couldn't understand how to copy directly)
From recovery:
flash system.img to system partition.
Reboot to recovery.
Mount system partition,
Resize system partition.
Install gapps.
Dont forgot to flash boot.img to boot partition as well.
Regards,
removed
nshussain said:
Here is the link for the file I converted.
https://drive.google.com/file/d/1xEwm_cYJvatXSwq0P0WgWL2RhagMJMR-/view?usp=sharing
I think 16 GB Kenzo variant has only 2.5 GB system partition and that's why this issue is coming.
Click to expand...
Click to collapse
Thank you for your detailed instructions. The system.img worked perfectly to boot into the system. LOL
But I can't resize the partition, and I don't know the reason. And obviously it went wrong when I'm trying to flash gapps.
It says that
system available size: 0 KB
/product available size: 0 KB
I know the storage might not be enough, but at least it can't be 0KB.
nshussain said:
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
Click to expand...
Click to collapse
your Welcome
nshussain said:
Install Ubuntu os on a VM, copy img file you converted over there.
On terminal browse to location where you saved img and run commands:
e2fsck -f -y system.img
resize2fs -M system.img
Copy img from Ubuntu to computer and then phone. (I used internet, couldn't understand how to copy directly)
From recovery:
flash system.img to system partition.
Reboot to recovery.
Mount system partition,
Resize system partition.
Install gapps.
Dont forgot to flash boot.img to boot partition as well.
Regards,
Click to expand...
Click to collapse
nice job brother
xykshun said:
Thank you for your detailed instructions. The system.img worked perfectly to boot into the system. LOL
But I can't resize the partition, and I don't know the reason. And obviously it went wrong when I'm trying to flash gapps.
It says that
system available size: 0 KB
/product available size: 0 KB
I know the storage might not be enough, but at least it can't be 0KB.
Click to expand...
Click to collapse
Post are updated && issue fixed
Thank you,
for some reason Clash of Clans hangs a lot of times on this Rom, what could be the reason?
Pubg works fine. strange.
Once I flashed this ROM, I launch it into the system, it immediately throws it into Fastboot mode!
At first I tried to flash the latest version with twrp. (I did it all by instrumentation. The effect is the same!)
And then I switched from twrp to ofrp, using the earlier version ofrp. (I did it all by instrumentation. The result is zero!)
My kenzo phone with 2gb RAM.