[RECOVERY][UNOFFICIAL] TWRP-3.2.3 [20181212] - Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other

{
"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!
BUGS:
You tell
NOTE:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
XDA:DevDB Information
TWRP recovery, Tool/Utility for the Xiaomi Poco F1
Contributors
vasishath
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Beta
Current Stable Version: v2
Stable Release Date: 2018-12-12
Created 2018-10-11
Last Updated 2018-12-14

Reserved
Download links:-
https://www.androidfilehost.com/?w=files&flid=283470
THIS TWRP DOES NOT DISABLE FORCE ENCRYPTION. IT WILL DECRYPT THE ENCRYPTED DATA WITHOUT THE NEED OF FORMATING IT

DO NOT POST WITHOUT READING THIS:
Two reasons why you are unable to successfully decrypt data. (unable to get past the lock)
1. You must have flashed older security patch rom
Example: You have flashed a rom which has december security patch. Later flash a rom with November or Oct security patch. Decryption Fails
Reason: In Android 8.x, devices implementing Keymaster 3 or earlier were required to verify the version info (ro.build.version.release and ro.build.version.security_patch) reported by the running system matched the version info reported by bootloader. Such information was typically obtained from the boot image header. Further, they disallow any downgrade to older security patch or android version.
2. The person who compiled the rom failed to add encryption support.
Solution: Ask that person to add support or flash the one that supports encryption.

great work

Nice work!

Great work as always :good:

Many thanks Vasi for huge efforts!. Will give me another try with the encryption of LOS 16!

Inshallah boys played well

Great work!!!

Thanks! Its great!
Enviado desde mi POCOPHONE F1 mediante Tapatalk

Finally thank u very much!

Hello, I am kinda confused. What's the advantage of this over the other recovery? What decryption bug fix is applied onto this?

kishore1998 said:
Hello, I am kinda confused. What's the advantage of this over the other recovery? What decryption bug fix is applied onto this?
Click to expand...
Click to collapse
No need to flash force decryption anymore.

@vasishath does this support usb otg, and MTP?
Edit: nvm I flashed it and answer is yes & yes lol

Well done! I don't need to smash my head over it anymore
But where is source link? To device tree, not TWRP...

If I flash twrp every time I update ROM should I flash it again;
Στάλθηκε από το Mi A1 μου χρησιμοποιώντας Tapatalk

So if i have a encrypted phone with MIUI 10 Global Beta with this TWRP i can go to recovery type my PIN and it will decrypt so i can flash things and keeps the ROM encrypted ? or the things with this TWRP is that is keeps roms decrypted ?

tlf55 said:
So if i have a encrypted phone with MIUI 10 Global Beta with this TWRP i can go to recovery type my PIN and it will decrypt so i can flash things and keeps the ROM encrypted ? or the things with this TWRP is that is keeps roms decrypted ?
Click to expand...
Click to collapse
From the OP:
"NOTE:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit."
So, MIUI Global Beta 'might work'

Thanks for your hard work

Good job.
Thank you.

Related

[RECOVERY][CHM-U01][Unofficial] TWRP 3.0.2-0 for Huawei Honor 4C Android 5.1.1-6.0.0

{
"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"
}
TWRP 3.0.2 for Huawei Honor 4C CHM-U01 (All Regions) Android 5.1.1-6.0.0​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.
CHANGELOG for 3.0.1-0:
- support new CM 13.0 pattern encryption (sultanqasim)
- fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
- libtar updated to latest upstream and fixes (jcadduono)
- fixes for loading custom themes (_that)
- TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
- translation updates - added Italian, Czech and Polish and significant updates to Dutch
- progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
- fix input box text display (Dees_Troy)
- reboot option after zip install complete (bigbiff)
- other mostly invisible bug fixes and improvements
DEVICE SPECIFIC CHANGELOG:
Changelog for r1
- Fixed Reboot to System from TWRP Device powered off instead of rebooting
- Switched to Android 6.0 Kernel Fixed various bugs including touch screen not working after a small delay and black screen on boot
- Add backup and wipe of Cust Partition Cust partition should be backed up when downgrading from higher Android version to lower Android version through TWRP
Changelog for r2
- Fixed Mass USB Storage support Corrected file paths
- Bumped TWRP to 3.0.1-0 release
- Unified device identity parameters Prepping for AOSP releases. Avoiding model/device mismatch in TWRP before flashing
Changelog for r3
- Cleaned Ramdisk and now using Kernel compiled from sources
- Bumped TWRP to 3.0.2-0 release
Changelog for r4
- Fixed tzdata issues which lead to zone and posixr errors in recovery logs
TODO
- Fix /data/cust symlink and /data/custom.bin being destroyed after wiping /data/partition (This won't be implemented now as the recovery will be in near future used to flash custom ROMs)
- Add double tap to wake (will look into it, it's just a bonus)
SCREENSHOTS
DOWNLOADS
Unauthorized mirroring of any download file is strictly forbidden. No direct linking to the file below. Redirect all users to download TWRP from this page only.
I released TWRP 3.0.0-0 on other forums and what happened. They just decompiled my image, made changes to prop file and changed TWRP title to their names so as to claim as if it's built by them. Please respect the developer (I ain't one, just a starter) and if you want to build one, build one from the source.
TWRP 3.0.1-0 r4: https://www.androidfilehost.com/?fid=24521665358595470 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
TWRP 3.0.1-0 r3: https://www.androidfilehost.com/?fid=24499762636007214 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
TWRP 3.0.1-0 r2: https://www.androidfilehost.com/?fid=24459283995313249 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
TWRP 3.0.0-0 r1: https://www.androidfilehost.com/?fid=24459283995309979 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3​
XDA: DevDB Information
Unofficial TWRP 3.0.1-0 Recovery Project for Honor 4C CHM-U01
Contributors
@mfbcool , @XePeleato (for fixing Black Screen issue on newer Kirin devices)
TWRP Source Code: https://github.com/TeamWin
Recovery Device Source Code: https://github.com/muhammadfahadbaig/recovery_device_huawei_honor4c
Version Information
Status: Stable
Created 2016-04-01
Last Updated 2016-04-05
XDA:DevDB Information
TeamWin Recovery Project, Tool/Utility for the Huawei Honor 4C
Contributors
mfbcool
Source Code: https://github.com/muhammadfahadbaig/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.0.2-0_r4
Stable Release Date: 2016-04-30
Created 2016-04-15
Last Updated 2016-05-09
Reserved
Cool!
Android小楼阁
来自搭载Android 2.3 GingerBread的华为Y220-T10
zhaozihanzzh said:
Cool!
Click to expand...
Click to collapse
Thanks! :victory:
Great work..... Am compiling Cyanogenmod soon... May be i needed this recovery for proper flashing cm12 or cm13 for proper binaries updates....
inshaalmirza said:
Great work..... Am compiling Cyanogenmod soon... May be i needed this recovery for proper flashing cm12 or cm13 for proper binaries updates....
Click to expand...
Click to collapse
CyanogenMod 12 or 13 for Honor 4C?That's great!
来自搭载Android 2.3 GingerBread的华为Y220-T10
great job.
Root
So how to root huawei honor 4c according to your method on android Marshmallow.
drag0nslayer said:
So how to root huawei honor 4c according to your method on android Marshmallow.
Click to expand...
Click to collapse
Root method doesn't changes. It remains the same. Follow @inshaalmirza guide on rooting Marshmallow.
@drag0nslayer follow this guide for rooting marshmallow
http://forum.xda-developers.com/general/general/root-honor-4c-root-recovery-bootloader-t3318406/
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Guyz i need some support and members....cant compile cyanogenmod alone... Or it gonna take months... Am a university level student so... Have patience till vacations!!
Hi mfbcool,
Which one should I take for honor 4c MM.
r1 or r2 ??
Why different versions?
*confused*
Thx4answer
br
Utze
utze said:
Hi mfbcool,
Which one should I take for honor 4c MM.
r1 or r2 ??
Why different versions?
*confused*
Thx4answer
br
Utze
Click to expand...
Click to collapse
Both are compatible with Marshmallow. r1 and r2 just indicates releases. r2 has more bugs fixed than r1. Hence go with r2.
mfbcool said:
Both are compatible with Marshmallow. r1 and r2 just indicates releases. r2 has more bugs fixed than r1. Hence go with r2.
Click to expand...
Click to collapse
works flawlessly and charm,,,thanks OP,,,,
Salam
Thanks for the recovery.
How to install it. it is image file?
and which rom u have on your device currently?
I am on kitkat, Should I go for Andriod M or stay here?
Last thing, My boatloadrer is unlocked and have TWRP recovery by Inshal. Any easy way to go to Marshmallow?
I have not changed my region yet.
Regards
Waqar90 said:
Salam
Thanks for the recovery.
How to install it. it is image file?
and which rom u have on your device currently?
I am on kitkat, Should I go for Andriod M or stay here?
Last thing, My boatloadrer is unlocked and have TWRP recovery by Inshal. Any easy way to go to Marshmallow?
I have not changed my region yet.
Regards
Click to expand...
Click to collapse
1. It is an image file and can be flashed through fastboot.
Code:
fastboot flash recovery recovery_name.img
2. It is not for Kitkat but if you need one, I can upload a test version for you
3. You can download Android Marshmallow Beta for Pakistan from here https://cloud.mail.ru/public/Gzqd/mJNsxm6AB . However, I haven't personally tested it.
mfbcool said:
1. It is an image file and can be flashed through fastboot.
Code:
fastboot flash recovery recovery_name.img
2. It is not for Kitkat but if you need one, I can upload a test version for you
3. You can download Android Marshmallow Beta for Pakistan from here https://cloud.mail.ru/public/Gzqd/mJNsxm6AB . However, I haven't personally tested it.
Click to expand...
Click to collapse
Which Rom are you using on your Honor 4c?
And If Andriod M, how did you update it?
What you suggest, Andriod M is better or Andriod L for honor 4C?
This beta version is developed by you or someone else?
and can it directly be flashed on Pakistan Lolipop Rom?
I am sorry, I am at Lolipop, not kitkat.
Waqar90 said:
Which Rom are you using on your Honor 4c?
And If Andriod M, how did you update it?
What you suggest, Andriod M is better or Andriod L for honor 4C?
This beta version is developed by you or someone else?
I am sorry, I am at Lolipop, not kitkat.
Click to expand...
Click to collapse
1. I am on Marshmallow. Changed my region to Malaysia when I was on Kitkat.
2. Android M is much better, stable and smoother than Android 5.1.1
3. I didn't developed the beta version. It's officially released by Huawei in a closed beta test.
Beta version is released by Huawei Pakistan?
Hi.
Looks und feels good.
For first time I was irritated, because the backup folder changed. So I can't find my backups with previous TWRP version.
And the backup duration needs the double time.
TODO
- Fix /data/cust symlink and /data/custom.bin being destroyed after wiping /data/partition
Should I not use "wiping data partition" for the moment?? Because it destroy sometimes or is it harmless??
br
Utze
utze said:
Hi.
Looks und feels good.
For first time I was irritated, because the backup folder changed. So I can't find my backups with previous TWRP version.
And the backup duration needs the double time.
TODO
- Fix /data/cust symlink and /data/custom.bin being destroyed after wiping /data/partition
Should I not use "wiping data partition" for the moment?? Because it destroy sometimes or is it harmless??
br
Utze
Click to expand...
Click to collapse
Yes, you shouldn't wipe Data partition and Factory Reset using TWRP. It destroys custom.bin and /cust/ symlink which holds vendor and firmware information. I have fixed it but the method isn't robust at the moment. As soon as I find a good alternate to the fix, I'll update TWRP.

[RECOVERY][UNOFFICIAL] TWRP-3.2.3-x [beryllium][20180831]

{
"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!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
twrp*.img
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
/data decryption does not work
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [beryllium], Tool/Utility for the Xiaomi Poco F1
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Alpha
Created 2018-08-31
Last Updated 2018-08-31
Reserved for changelog.
Shivam Kumar Jha 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!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod as /data decryption doesnt work.
twrp*.img
Kernel source: Prebuilt stock
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [beryllium], Tool/Utility for the Xiaomi Poco F1
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Alpha
Created 2018-08-31
Last Updated 2018-08-31
Click to expand...
Click to collapse
HAHAHA nice to see you here , finally things starting to pop . Thanks for the twrp , well how's you now ?
Downloading

			
				
Vatumb said:
View attachment 4584746
Click to expand...
Click to collapse
You have unlocked the device as well ?
+1
Harry_00s.HS said:
You have unlocked the device as well ?
Click to expand...
Click to collapse
Yes already unlocked the bootloader and rooted the phone
Vatumb said:
Yes already unlocked the bootloader and rooted the phone
Click to expand...
Click to collapse
Whoa,
I am not able to do as mi unlock gives error for 720 hours now
can you help and give steps how did you do ??
PrathaM X said:
Whoa,
I am not able to do as mi unlock gives error for 1440 hours
can you help and give steps how did you do ??
Click to expand...
Click to collapse
Even I get an unlock error for 720 hours ...
Noice
Can I restore vendor image from current rom on gsi treble rom?
Sent from my Mi A1 using Tapatalk
we have treble support for poco f1?
When i saw your name, I thought I landed on cancro thread by mistake great to see you here!
Mind sharing how you unlocked the bootloader? Official tool is asking me to wait 360hours. :/ Thanks.
Anybody interested about Custom Kernel for poco f1? I will need testers?
Sent from my Mi A1 using Tapatalk
themarine.sujit said:
we have treble support for poco f1?
Click to expand...
Click to collapse
Yes. Any phone shipping with Android Oreo and above is treble compliant.
anyone with root willing to test this?
https://forum.xda-developers.com/poco-f1/help/poco-f1-lte-bands-unlock-t3835467
please backup your efs and persist before you try.
munchy_cool said:
anyone with root willing to test this?
https://forum.xda-developers.com/poco-f1/help/poco-f1-lte-bands-unlock-t3835467
please backup your efs and persist before you try.
Click to expand...
Click to collapse
Do you mind sharing the method you used to unlock the bootloader? Waiting for 360 hrs is a bit too long.
Nigam666 said:
Do you mind sharing the method you used to unlock the bootloader? Waiting for 360 hrs is a bit too long.
Click to expand...
Click to collapse
there is no method buddy. if the app tells you to wait for 360 hrs you have to. no way around it. for those who have already unlocked the bootloader no one why they didnt have to wait for 360 hrs.
PS:- I do not own the device nor have I unlocked the bootloader. I am waiting for someone to test band 2 and 4 so I can buy it.
Wow! Thanks, gonna test soon.

[ROM][9.0.0_r21 - 64bit] GZOSP [Berkeley][Honor View 10][10-12]

GZOSP Pie​
Brought to you by :
{
"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"
}
Ground Zero ROMs​
Pie status: Alpha​
Download
GZOSP: AndroidFileHost
Gapps: Open Gapps
Device tree: https://github.com/berkeley-pie/android_device_huawei_berkeley
XDA:DevDB Information
GZOSP Pie for Honor View 10, ROM for the Honor View 10
Contributors
GtrCraft
Source Code: https://github.com/GZOSP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, 0.7 TWRP Recovery
Based On: GZOSP
Version Information
Status: Beta
Created 2018-11-21
Last Updated 2018-12-10
Flashing Instructions
Needed files:
-TWRP with encryption disabled by @vache
-No Verity & Disable Force Encryption Zip by @Zackptg5
This will disable encryption, don't boot into erecovery or restore stock as it will wipe your internal storage to re encrypt it
1. Copy Rom, the disable verity & encryption zip, Gapps and Magisk (optional) to microsd or adb folder on PC
2. Install the TWRP and verify if it works.
3. Make backup of internal storage, next steps will format it.
4. Boot to fastboot and do the following command (it will give an error):
Code:
fastboot -w
5. Boot to TWRP and do Format Data.
6. Reboot to TWRP and wipe system, data and (dalvik-)cache.
7. Flash rom and disable verity & encryption zip (microsd or adb sideload)
8. Flash gapps & magisk if you want root.
9. Reboot
Steps and files are from this guide
Reserved
I remember running and liking Ground Zero roms on my LG G3 - Validus, Tesla, and Tipsy. Will have to give this a try.
I successfully flashed magisk 17.1, 17.2, and 17.3 in multiple install attempts but the rom was never rooted.
Hi, I'm asking for help with uploading this rom. I have honorv10 - BKL-L09 8.0.0.169C (432) Czech market, I tried Bliss rom, AOSCP rom. I've always finished logging, 2 - 3 restarts and then just erecovers and uploading official rom. Everything I do according to various tutorials, but I never manage to record rom with android 9. Before honoring I had a lot of other phones and never a problem. Otherwise, bootloader I have unlocked, root also, twrp I use from pretorian - twrp bkl 0.7.img. Can you describe me step by step how to upload this rom to me? I would be very grateful. I apologize at the same time for my English, I translate using google compiler
blazios said:
Hi, I'm asking for help with uploading this rom. I have honorv10 - BKL-L09 8.0.0.169C (432) Czech market, I tried Bliss rom, AOSCP rom. I've always finished logging, 2 - 3 restarts and then just erecovers and uploading official rom. Everything I do according to various tutorials, but I never manage to record rom with android 9. Before honoring I had a lot of other phones and never a problem. Otherwise, bootloader I have unlocked, root also, twrp I use from pretorian - twrp bkl 0.7.img. Can you describe me step by step how to upload this rom to me? I would be very grateful. I apologize at the same time for my English, I translate using google compiler
Click to expand...
Click to collapse
Pretorian doesn't work with encryption on Android P, use one with either encryption disabled or fixed.
Good. So what should I use? Thanks
blazios said:
Good. So what should I use? Thanks
Click to expand...
Click to collapse
You can try using the one from Bliss maintainer recommended: https://androidfilehost.com/?fid=11410932744536984613
I use another one, but I won't recommend mine to use as it requires some knowledge with adb as MTP isn't working on my TWRP.
thanks, I say it
Codebucket said:
You can try using the one from Bliss maintainer recommended: https://androidfilehost.com/?fid=11410932744536984613
I use another one, but I won't recommend mine to use as it requires some knowledge with adb as MTP isn't working on my TWRP.
Click to expand...
Click to collapse
I won't use that one either, I needed to recover with erecovery or had a broken cache partition.
I will write a step by step guide in second post.
blazios said:
Good. So what should I use? Thanks
Click to expand...
Click to collapse
Check second post, I wrote a step by step
Stuck at bootanimation
Took this log while being stuck at bootanimation.
Followed your flashing steps.
bkl l09 here though..
Update:
https://www.androidfilehost.com/?fid=11410963190603871487
-Updated to r21 (november patch)
-Enabled dexpreopt
GtrCraft said:
Needed files:
-TWRP with encryption disabled by @vache
Click to expand...
Click to collapse
Do you know what version of TWRP this is? I assume it would work fine for all normal uses and other rom's if desired?
thecdn said:
Do you know what version of TWRP this is? I assume it would work fine for all normal uses and other rom's if desired?
Click to expand...
Click to collapse
3.2.3-1
GtrCraft said:
3.2.3-1
Click to expand...
Click to collapse
I have downloaded the linked twrp twice and successfully flashed it four different fimes and it states it is 3.2.1-0 by Pratoriano80 and zxz000. Is this correct?
After that I followed the directions but after trying to boot it twice - getting to the start install gapps screen, it booted to the erecovery screen.

[RECOVERY][UNOFFICAL] TWRP 3.1.1-0 For SM-G313HU a.k.a Ace4/S Duos 3.

{
"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.
this Image of Twrp is Compiled with Latest 2018 Source Code. So enjoy.
Bugs:
You Tell
DOWNLOAD:
see attached files below.
Installation Instructions:
Method-1:
If you have already any custom recovery installed. you can Download that twrp zip file and directly flash it with custom recovery. after flashing select reboot and select reboot to recovery.
Method-2:
just Download recovery.img.tar and flash it via odin in AP.
TWRP For S Duos 3/Ace 4
Thanks to @itigr for Device Trees.
Contributers: @JaskaranSM
Status : Stable
Created: 5-Feb-2019
THANKS Please make Android GO ROM ))
bestttt regards
Thank
JaskaranSM 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.
this Image of Twrp is Compiled with Latest 2018 Source Code. So enjoy.
Bugs:
You Tell
DOWNLOAD:
see attached files below.
Installation Instructions:
Method-1:
If you have already any custom recovery installed. you can Download that twrp zip file and directly flash it with custom recovery. after flashing select reboot and select reboot to recovery.
Method-2:
just Download recovery.img.tar and flash it via odin in AP.
TWRP For S Duos 3/Ace 4
Thanks to @itigr for Device Trees.
Contributers: @JaskaranSM
Status : Stable
Created: 5-Feb-2019
Click to expand...
Click to collapse
Where is the device tree link?
TriDiscord said:
Where is the device tree link?
Click to expand...
Click to collapse
Yup good question

[ROM][OFFICIAL][12.1][Beryllium] Pixel Experience [AOSP][2022/04/03]

{
"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"
}
PixelExperience for Poco F1 [Beryllium]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
What's working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
Lights
Sound / vibration
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Donate
Liked our work? Give us a beer
Lakshay
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 12L
Security patch level: March 2022
Build author/Device Maintainer: lakshay18
Kernel Source: https://github.com/PixelExperience-Devices/kernel_xiaomi_polaris
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
PixelExperience 12, ROM for the Xiaomi Poco F1
Contributors
lakshay18
Source Code: https://github.com/PixelExperience
ROM OS Version: Android 12.1
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2022-12-19
Last Updated 2022-12-19
Flashing Instructions:​
Download ROM
Boot to latest TWRP (V3.6.0_9-0 Official required).
Go to Wipe > Advanced Wipe. Check Dalvik, Cache, System, Data & Vendor. Swipe to wipe.
Flash the ROM zip.
After a successful flash, Go back to Wipe > Format > type yes. [Mandatory]
Reboot
NOTE
Force Encryption is Enabled by Default.
Clean Flash is MANDATORY!
Any Recovery present will be overridden by PE recovery in order to make OTA updates work as other recoveries currently doesn’t supports Decryption!
Encrypted users are RECOMMENDED not to use Custom Recoveries! Or else OTA won’t work and have to update manually through adb sideload or external storage.
If you are a decrypted user flash Latest TWRP again and follow the steps to update ROM manually.
OTA doesn’t work for Decrypted Users
Flash Latest TWRP first before proceeding for installation!
RESERVED #2
I followed the steps and i have the twrp version mention in post #2, still i get booted into recovery again!
I don't know if i did something wrong.
Hope logcat helps!
PixelExperience 12 STABLE Beryllium
Android 12 STABLE
lakshaygarg.in
wherebi can get twrp 3.6
singh.mohit787 said:
wherebi can get twrp 3.6
Click to expand...
Click to collapse
You can download the TWRP app. Search for the device name and the TWRP version. The file can be flashed from the app as well as from the recovery.
I was almost on the verge to buy a new phone. Thanks for this! Long live the poco.
Thank you for the contribution! @lakshay18
Can somebody tell me the function of recovery image on the website download section? The instruction doesn't tell to install it. I'm coming from last Pixel Experience PLus 11 ROM.
Btw, the website still says it is in Beta.
Does this have face unlock?
deepydarkness said:
Does this have face unlock?
Click to expand...
Click to collapse
no.
deepydarkness said:
Does this have face unlock?
Click to expand...
Click to collapse
we should wait and see, there is a new feature auto rotation with face based, i saw only this thing new till now.
singh.mohit787 said:
wherebi can get twrp 3.6
Click to expand...
Click to collapse
TWRP - https://dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
hyper21 said:
Thank you for the contribution! @lakshay18
Can somebody tell me the function of recovery image on the website download section? The instruction doesn't tell to install it. I'm coming from last Pixel Experience PLus 11 ROM.
Btw, the website still says it is in Beta.
Click to expand...
Click to collapse
it isn't important at the end after flashing the rom recovery will be flashed automatically, and this is stable rom written on this forum i think website have to be updated.
Does PE recovery allow flashing of TWRP recovery?
i dont know how to report bugs, but im putting here, in first image the icon of link on top and icon of image on middle doesn't come automatically, i have to press an option called select in multitasking menu and after cancelling select option these buttons starts appearing otherwise dont, i recently saw in youtube video that this is working fine for other this means this bug is for me only
The steps given were clear and precise.
ROM installed successfully.
Thanks for the great work.
a9k1t said:
Does PE recovery allow flashing of TWRP recovery?
Click to expand...
Click to collapse
no, only ota updating.
Will OTA work with magisk/root?
Does magisk work ? Or do I need Canary Magisk ? Also regarding OTA, is it the same as Android 11 ? Updating then flash magisk from recovery ?
Cheers

Categories

Resources