[ROMs][TREBLE] OpenKirin AOSP Collection - Mate 8 Original Android Development

{
"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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei Mate 8.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 4 ROMs in total as of now - LineageOS (Unofficial), CarbonROM (Official), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei Mate 8
Contributors
OldDroid, XePeleato, rcstar6696, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-13

Thanks @OldDroid for all the efforts.
I have used all 4 and all are working awesome, especially RR beta 2.
Awesome work....

What about the deep sleep issue on 950?
Will it be fixt in the future?

Hey guys, I have a spare mate 8 which is actually on build 829. Followed the instructions to the letter on Openkirin website, on RR beta 2right now,. But each time I reboot it, it says that decryption is unsuccessful and to reset the device. Is this normal?

malekowsky said:
Hey guys, I have a spare mate 8 which is actually on build 829. Followed the instructions to the letter on Openkirin website, on RR beta 2right now,. But each time I reboot it, it says that decryption is unsuccessful and to reset the device. Is this normal?
Click to expand...
Click to collapse
Yes, decryption problem remains with OK ROMs. You need to either decrypt with twrp or with fstab through adb shell. Once done, you won't get it again till you flash stock room again.

apat26 said:
Yes, decryption problem remains with OK ROMs. You need to either decrypt with twrp or with fstab through adb shell. Once done, you won't get it again till you flash stock room again.
Click to expand...
Click to collapse
Thank you buddy, basically same issue I ran in to when I tested AOSP a while ago except that ROMS are now more elaborated and functioning smoothly.

I try rr beta 2 and omnirom but i have only one sim (sim 2) sim 1 does not exist.Nice sim 2 does not work with all operators. For the idea?

For everyone else who has been struggling with the decryption issue, I finally figured out how to get OpenKirin's LineageOS image to boot without first encrypting. You lose FDE in the process (a tradeoff I'm willing to make to get a working phone).
1. Start with stock EMUI 8 and a stock recovery. You can get EMUI 8 using the HWOTA packages. If, anywhere in the process you make a mistake, you can restore EMUI by flashing the HuRUpdater zip.
1a. Boot into EMUI 8 to make sure it is intact. You may need to run a factory reset from the recovery (the complete, stock recovery which you can reach by holding Power + VolUp. Do not reset from eRecovery.) Once you see the language select screen you can be satisfied that it works.
2. Boot into fastboot (power off, hold VolDown and plug into USB).
3. Flash your OpenKirin ROM of choice:
Code:
fastboot flash system openkirin_ROMNAME.zip
4. Exit fastboot and immediately perform a factory reset from stock recovery, just like the OpenKirin instructions tell you to. Do not boot into the OS first. For me, the factory reset appears to fail. I ran it anyway just to be sure, and it does seem to make a difference even if it fails.
5. Once the reset is done, return to fastboot.
6. Flash this version of TWRP (originally for Mate 9):
Code:
fastboot flash recovery_ramdisk twrp_mate9_0.1.img
7. Boot into TWRP recovery: run
Code:
fastboot reboot
, unplug the phone, and hold down VolUp until the logo appears. (You have to be quick.)
8. Once in TWRP, load up an adb shell and remount /vendor with write perms:
Code:
mount -o remount,rw /dev/block/bootdevice/by-name/vendor /vendor
If your devices differ, use
Code:
df -h .
to see what the device name is.
9. Alter the following files, removing any boot flags that say "avb" or "forceencrypt":
Code:
/vendor/etc/fstab.f2fs.hi3650
/vendor/etc/fstab.ext4.hi3650
Make sure the comma-separated lists stay valid.
10. Save your files, and tell TWRP to reboot to system.

Georgian51 said:
I try rr beta 2 and omnirom but i have only one sim (sim 2) sim 1 does not exist.Nice sim 2 does not work with all operators. For the idea?
Click to expand...
Click to collapse
I also had that problem, a developer told me its because of the cdma modem, which is in the AL10 variant. Max connection i got was Edge.
So im back to stock an wait till they fix that problem.

Are these projects working for mate 8? I see that the rom has not been updated

Georgian51 said:
Are these projects working for mate 8? I see that the rom has not been updated
Click to expand...
Click to collapse
yup this is for Mate 8..there are few peoples already tested it but seems like there are still got few bugs like signal and etc. i'm waiting for a new build and will test it.

I'm another that has tested LOS, RR, and OR, and all have the issue with not getting any SIM card signal. Obviously I can't use, as a smartphone without the phone, isn't that smart.
Keenly hoping this gets resolved, as I certainly like the look of these ROMs.

lindsaytheflint said:
I'm another that has tested LOS, RR, and OR, and all have the issue with not getting any SIM card signal. Obviously I can't use, as a smartphone without the phone, isn't that smart.
Keenly hoping this gets resolved, as I certainly like the look of these ROMs.
Click to expand...
Click to collapse
What version did you test?
On AL10 I tried and I had the same problems. I went to
* DL00 and no problems

Georgian51 said:
What version did you test?
On AL10 I tried and I had the same problems. I went to
* DL00 and no problems
Click to expand...
Click to collapse
I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.
Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?
If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?

lindsaytheflint said:
I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.
Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?
If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?
Click to expand...
Click to collapse
I made a rebrend at DL00. Try the variant you say, maybe it works

lindsaytheflint said:
I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.
Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?
If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?
Click to expand...
Click to collapse
Did you flashed cust after upgraded to B596?if you noticed that you don't have signal or no service at that time?

ceriqdesign said:
Did you flashed cust after upgraded to B596?if you noticed that you don't have signal or no service at that time?
Click to expand...
Click to collapse
Yes, and signal was fine at B596. Signal is also fine on either stock b829 or KangVIP b828/829.
Firmware Finder's been offline, but looks like it's coming back online soon, so I'll try installing DL00 b829 stock ROM, then OpenKirin, to see if that helps.
(I tried flashing just DL00 b829 Cust.img yesterday, but it didn't seem to make a difference.)
For those that do have working signal on OpenKirin, what full base stock ROM did you come from? i.e. b829, DL00, AL10 etc, and which country region C00, C92, C17, etc?

Hi, looks like I am having the same signal issues as every one else on NXT-AL10. Have flashed back to stock EMUI 8 for now after hard bricking my device and using Dc-Phoenix to recover by shortinng out the testpoints.
Like every one else have been looking in to possible solutions. After booting in to open kirin roms and looking in to phone info in setting I noticed my IMEI was blank. At this point flashed back to stock after hard bricking and loaded in to HCU-client to repair fortunately this was not the case and IMEI was intact.
So digging around other Huawei boards I fond this maybe a possible solution to signal issue. Don't have time to try just now will let you know how it goes.
Honor 6X [GUIDE] Update to EMUI 8
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
found in instruction on first post
Bugs Fixing:
Unknown or invalid IMEI:Use any root file manager and go to cust/all/cn/prop/local.prop and edit local.prop change the line full network support: true to false
sounds like the problem we are all having with our devices.
If anyone tries this before me can you let us all know

Brokendroid994 said:
Hi, looks like I am having the same signal issues as every one else on NXT-AL10. Have flashed back to stock EMUI 8 for now after hard bricking my device and using Dc-Phoenix to recover by shortinng out the testpoints.
Like every one else have been looking in to possible solutions. After booting in to open kirin roms and looking in to phone info in setting I noticed my IMEI was blank. At this point flashed back to stock after hard bricking and loaded in to HCU-client to repair fortunately this was not the case and IMEI was intact.
So digging around other Huawei boards I fond this maybe a possible solution to signal issue. Don't have time to try just now will let you know how it goes.
Honor 6X [GUIDE] Update to EMUI 8
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
found in instruction on first post
Bugs Fixing:
Unknown or invalid IMEI:Use any root file manager and go to cust/all/cn/prop/local.prop and edit local.prop change the line full network support: true to false
sounds like the problem we are all having with our devices.
If anyone tries this before me can you let us all know
Click to expand...
Click to collapse
Tried this, and confirmed that my IMEI is also missing from OpenKirin, but after changing the local.prop file and rebooting, it was worse. Rather than the SIM being detected, but having no signal, the SIM was no longer being detected at all (slot showing as empty). Tried OpenKirin RR.

deja_wu said:
For everyone else who has been struggling with the decryption issue, I finally figured out how to get OpenKirin's LineageOS image to boot without first encrypting. You lose FDE in the process (a tradeoff I'm willing to make to get a working phone).
9. Alter the following files, removing any boot flags that say "avb" or "forceencrypt":
Code:
/vendor/etc/fstab.f2fs.hi3650
/vendor/etc/fstab.ext4.hi3650
10. Save your files, and tell TWRP to reboot to system.
Click to expand...
Click to collapse
Hello . I modded this files .
remove "avb" flags and change "forceencrypt" to "encryptable" . work fine (Resurrection Remix OS Beta 3
Released September 27, 2018 - 575.05MB , NXT-L29 (dual sim) changed to NXT-DL00)
View attachment hi3650.rar

Related

[ROM][UNOFFICIAL][ZTE Axon 10 Pro] [9] LineageOS 16.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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps/addons
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps/addons
Reboot
Downloads :
Builds : http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/ {link modified by mod on behalf of OP}
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
LineageOS, ROM for the ZTE Axon 10 Pro, ROM for the ZTE Axon 10 Pro
Contributors
Unjustified Dev, DrakenFx
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Kernel source: https://github.com/C457/android_kernel_zte_sm8150 {link added by mod on behalf of OP}
Version Information
Status: Beta
Created 2019-10-27
Last Updated 2019-10-27
//
Rock solid ive been running this for about two weeks, besides fp not working everything else works as intended, the only thing is i messed up my fastboot by replacing abl.elf with stock one, so im bootloader unlock with twrp, but no fastboot
Here are some screenshots:
rafyvitto said:
Rock solid ive been running this for about two weeks, besides fp not working everything else works as intended, the only thing is i messed up my fastboot by replacing abl.elf with stock one, so im bootloader unlock with twrp, but no fastboot
Here are some screenshots:
Click to expand...
Click to collapse
I'll upload a flashable able.elf to get fastboot back later .....
with the abl.img the fastboot has go in the system no mtp modus
can you both abl.img without fastboot and abl.img the fastboot did not combine so we have fastboot but can still switch to mtp on system ?
Ps
with the abl.img the fastboot makes it possible for me every few minutes the sd card out but then again nen recognized
After a little trial and error, I finally got it installed on my Chinese version. Thank You! Running through the setup now. Once again, Thank You
Chris axon 7 said:
with the abl.img the fastboot has go in the system no mtp modus
can you both abl.img without fastboot and abl.img the fastboot did not combine so we have fastboot but can still switch to mtp on system ?
Ps
with the abl.img the fastboot makes it possible for me every few minutes the sd card out but then again nen recognized
Click to expand...
Click to collapse
Yes, with the Fastboot abl.elf ,MTP on System is disabled for whatever reasons......
But if I'm honest, with TWRP installed if you don't have the need to have fastboot, just keep stock abl for MTP and TWRP to flash anything.
Beside you can just use the AxonTool to get fastboot abl without problem.
I'm also leaving here a link for the TWRP Flashable Fastboot abl in case anyone wants it.
https://drive.google.com/file/d/148eMqi--WCXBnZsMhxiIB7rudb9A7jZ3/view?usp=drivesdk
@DarkenFX
've edited your zip times and the stock abl.elf as purely copied so you can turn off via twrp fastboot again
https://drive.google.com/file/d/1-FM9Szs3Q2TQRPWU5J8iO6FQKt6YpRvm/view?usp=drivesdk
no need to change the modem ?
i have the us version.
ty
le011 said:
no need to change the modem ?
i have the us version.
ty
Click to expand...
Click to collapse
Why would you change the modem? That's a device specific firmware you'd lose your service and more than likely sound
Sent from my ZTE A2020U Pro using Tapatalk
hi man , may i ask you a question ?
it is possible build a ROM or kernel permanently set selinux to permissive mode ? i mean AXON 10 Pro .
thanks..
Hi!
I have two problems with the rom.
The first one and most important is, that it sometimes just stops at LOS boot animation and I have to flash the entire rom and gapps.
The second one is that LOS recovery always overwrites TWRP, is there any option to avoide that?
Thanks!
imregy said:
Hi!
I have two problems with the rom.
The first one and most important is, that it sometimes just stops at LOS boot animation and I have to flash the entire rom and gapps.
The second one is that LOS recovery always overwrites TWRP, is there any option to avoide that?
Thanks!
Click to expand...
Click to collapse
Not sure about your first problem because you have not provided a log (I haven't ran into that issue yet). It could be something you have installed or some option causing an issue. The second problem is something that cannot be stopped. Newer devices don't have a recovery partition it's packed into the boot partition. The ROM provided a boot IMG so TWRP isn't replaced it's just not part of the boot.IMG that's being flashed. After you flash the ROM, flash the TWRP installer again (this cannot be changed)
Sent from my ZTE A2020U Pro using Tapatalk
Installed and working on 2020
I live in Canada and couldn't order an Axon10 anywhere here, so i got one from China. It is the A2020 not the G or the U. I managed to flash TWRP and this LineageOS ROM on it successfully, except for one detail.
I can't seem to get the mobile data networks to connect. I can make calls and send and receive texts, but no data networks. I've tried flashing the original modem, resetting the cache, and reinstalling the rom. I can't seem to change the APN settings either as they're all greyed out.
Any advice would be appreciated.
scionoics said:
I live in Canada and couldn't order an Axon10 anywhere here, so i got one from China. It is the A2020 not the G or the U. I managed to flash TWRP and this LineageOS ROM on it successfully, except for one detail.
I can't seem to get the mobile data networks to connect. I can make calls and send and receive texts, but no data networks. I've tried flashing the original modem, resetting the cache, and reinstalling the rom. I can't seem to change the APN settings either as they're all greyed out.
Any advice would be appreciated.
Click to expand...
Click to collapse
I too have the Chinese version. I was on Lineage, but went back to stock. even though there are some annoyances with the Chinese rom, there were some issues with the Lineage rom. Such as, No face unlock, FP scanner or wireless charging don't work and sound was rather low. I'm sure all these issues will be worked out in time.
jim262 said:
I too have the Chinese version. I was on Lineage, but went back to stock. even though there are some annoyances with the Chinese rom, there were some issues with the Lineage rom. Such as, No face unlock, FP scanner or wireless charging don't work and sound was rather low. I'm sure all these issues will be worked out in time.
Click to expand...
Click to collapse
Which Chinese there are two models one is 5g and one is 4g from my understanding. getprop ro.product.board
Sent from my ZTE A2020U Pro using Tapatalk
Unjustified Dev said:
Which Chinese there are two models one is 5g and one is 4g from my understanding. getprop ro.product.board
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
I have the 4G version. I just don't personally like light modes, so I have kept mine BL unlocked so that I can theme so that most apps are dark, but the other annoyance I have with the Chinese rom is the over agressive memory management that constantly shuts down Google Assistant. This causes me to constantly have to reset it. That is why I was asking if anyone had the capabilities or knew of a rom that had Chinese setting, but system images with Google Play. I have also tried eliminating Z-assistant, which seems to manage things, but Google Assistant is still shut down. Are you knowledgeable as to which app/service might be responsible for shutting things down?
@Unjustified Dev
hey wanted to ask if the fingerprint already works on los16 from 31.10 ?
Sent from my ZTE A2020G Pro using XDA Labs
Chris axon 7 said:
@Unjustified Dev
hey wanted to ask if the fingerprint already works on los16 from 31.10 ?
Sent from my ZTE A2020G Pro using XDA Labs
Click to expand...
Click to collapse
Fp is almost impossible. After a few weeks we finally got ZTE audio changes it may not be the same for fp. I'm not sure who makes the decisions but they modified the default Android service for fp. You can't really do that it's against vts. I've tried myself to do the same and the build give a big warning. It's not impossible to get it working, I just refuse to go that far to get something working when it could have been done differently.
Sent from my ZTE A2020U Pro using Tapatalk
jim262 said:
I have the 4G version. I just don't personally like light modes, so I have kept mine BL unlocked so that I can theme so that most apps are dark, but the other annoyance I have with the Chinese rom is the over agressive memory management that constantly shuts down Google Assistant. This causes me to constantly have to reset it. That is why I was asking if anyone had the capabilities or knew of a rom that had Chinese setting, but system images with Google Play. I have also tried eliminating Z-assistant, which seems to manage things, but Google Assistant is still shut down. Are you knowledgeable as to which app/service might be responsible for shutting things down?
Click to expand...
Click to collapse
Could you grab a logcat? Since the modem is working it could be the network mode is different for this device even though it's the Chinese one.
Sent from my ZTE A2020U Pro using Tapatalk

[RECOVERY][UNOFFICIAL] TWRP 3.4.0 for 2019 Galaxy Tab A 8.0 [SM-T290] (old)

{
"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"
}
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this inexpensive tablet. Many thanks to @mehanik6 on 4PDA for blazing the trail.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and rely on the latest posted kernel source.
This is unofficial and unsupported, so the usual caveats apply. Since we don't mess with the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5 (Odin tarball)
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img
Build archives:
Android File Host
Change Log:
v3.5.0_9-0: (2021-01-02)
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
v3.4.0-1: (2020-12-09)
New custom T290XXS3ATC1 kernel that actually fixes MTP support.
v3.4.0-0: (2020-12-04)
Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.
v3.4.0-0: (2020-11-01)
Initial release based on T290XXS3ATC1 OEM kernel
Fixed MTP support
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gtowifi
Donations:
Your support is always appreciated! Just click here.
After weeks of waiting Samsung has finally provided the Source for the Q update. Is there anyway you can update the Kernel base for the Q source?
Source is here: https://opensource.samsung.com/uploadSearch?searchValue=T290
Thank you!
jimbo77 said:
After weeks of waiting Samsung has finally provided the Source for the Q update. Is there anyway you can update the Kernel base for the Q source?
Source is here: https://opensource.samsung.com/uploadSearch?searchValue=T290
Thank you!
Click to expand...
Click to collapse
Yes, I've been requesting this since I got my SM-T290 in mid-October (when it went on sale for $89 at Costco) and Samsung finally posted it on Monday, along with the SM-T500. I'm actually building the custom kernel right now and should have an update for TWRP and a Nexus Stock custom ROM very soon.
UPDATE: Samsung seems to have changed the bootloader in Android 10 so that it won't support custom recovery even if the bootloader is unlocked and we substitute an empty vbmeta.img. This is another one of those Samsung VaultKeeper "features" that I find infuriating.
UGH!! I own both of these tablets (290 and 500) and just rooted the 500. I was hoping there would be some some custom ROMs coming out early next year for the 500.
Well, at least with the SM-T290 we can roll back to the Android 9 bootloader (minimally aboot and vaultkeeper), but that might not be an option with the SM-T500. We'll find out this weekend when I attempt to build TWRP for that newer tablet, which released with Android 10 and dynamic partitions.
The fact that you've been able to root the SM-T500 is promising, since Majisk modifies the recovery partition to do that.
Does this work with the Kids Edition of the SM-T290?
Really disappointed with this tablet, I figured since it only allows the user less than 32 gigs of space I could use an SD card in order for my daughter to download all the games she wants... only to find out there is no possible way to move any app to the SD whatsoever, actually the option to move apps to sd is not even greyed out it's just gone completely.
Doesn't seem to be many roms for the t290 available, and or if any roms out there could force that option back in.
sal84x said:
Does this work with the Kids Edition of the SM-T290?
Really disappointed with this tablet, I figured since it only allows the user less than 32 gigs of space I could use an SD card in order for my daughter to download all the games she wants... only to find out there is no possible way to move any app to the SD whatsoever, actually the option to move apps to sd is not even greyed out it's just gone completely.
Doesn't seem to be many roms for the t290 available, and or if any roms out there could force that option back in.
Click to expand...
Click to collapse
My Nexus Stock custom ROMs do allow formatting the SD as internal so that you can store apps on it (although there are performance issues with SD vs. EMMC to consider). I've already got this working on Android 9, but was holding out for the Android 10 kernel source to be posted so that we can roll out on the latest OEM firmware. This issue with the Q bootloader is a setback, but I expect that we'll be able to work around it.
The Kid's edition is just a characteristic of the OEM firmware you install, and the hardware is identical, so you should be fine after you upgrade to T290XXU3BTI2. If you really want the Kid's Edition splash screen, I suspect that T290UEU3BTI3 will work with custom ROMs based on T290XXU3BTI2 just fine.
Magendanz said:
My Nexus Stock custom ROMs do allow formatting the SD as internal so that you can store apps on it (although there are performance issues with SD vs. EMMC to consider). I've already got this working on Android 9, but was holding out for the Android 10 kernel source to be posted so that we can roll out on the latest OEM firmware. This issue with the Q bootloader is a setback, but I expect that we'll be able to work around it.
The Kid's edition is just a characteristic of the OEM firmware you install, and the hardware is identical, so you should be fine after you upgrade to T290XXU3BTI2. If you really want the Kid's Edition splash screen, I suspect that T290UEU3BTI3 will work with custom ROMs based on T290XXU3BTI2 just fine.
Click to expand...
Click to collapse
Oh ok thanks for breaking that down for me, I just was worried it wouldn't be compatible.
I would love to have a Nexus like experience on this thing, the more vanilla and pure Android, the better to me.
Would games on the sd card still play? Thats really my biggest reason as my daughter has already maxed out her space on it.
The last rooting/flashing I've done is from years back on an S3 and S5. I wish I could say my memory was good enough to feel confident about doing it.
So it would be unlock oem on developer mode, hook it up to a correct version of odin to put twrp in, then from twrp install magisk and also flash the rom right? I know I'm missing a ton of little details but just wanted to see what I could remember .
Thanks for your help
Quick Note: I just modified the Odin tarball to include legacy aboot and vaultkeeper images so that you can flash this custom recovery on Android 10 OEM firmware releases. The recovery image itself is unchanged.
sal84x said:
The last rooting/flashing I've done is from years back on an S3 and S5. I wish I could say my memory was good enough to feel confident about doing it.
So it would be unlock oem on developer mode, hook it up to a correct version of odin to put twrp in, then from twrp install magisk and also flash the rom right? I know I'm missing a ton of little details but just wanted to see what I could remember.
Click to expand...
Click to collapse
Well, a custom ROM and rooting a ROM are two very different things. You can look at my Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.1 (SM-T510) and see that it's very similar to Pixel Experience custom ROMs. Both are attempts to reproduce the "pure Nexus" experience, but with more modern Pixel boot animations, backgrounds, and Google apps.
Rooting can generally be done for any ROM now using Magisk to allow you to make changes, and there's a pretty good tutorial on that for the Galaxy Tab A7 here. My personal preference is not to root the system partition, but to simply make any changes using the TWRP File Manager where you already have root access.
Magendanz said:
Well, a custom ROM and rooting a ROM are two very different things. You can look at my Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.1 (SM-T510) and see that it's very similar to Pixel Experience custom ROMs. Both are attempts to reproduce the "pure Nexus" experience, but with more modern Pixel boot animations, backgrounds, and Google apps.
Rooting can generally be done for any ROM now using Magisk to allow you to make changes, and there's a pretty good tutorial on that for the Galaxy Tab A7 here. My personal preference is not to root the system partition, but to simply make any changes using the TWRP File Manager where you already have root access.
Click to expand...
Click to collapse
Oh ok, i see.
Your Nexus rom for the SM-T510 looks awesome! Also, that Tab A7 tutorial is great.
On your original post, the first 2 downloads you have, the first one, "twrp-3.4.0-0-T290UES3ATC1-20201204.tar.md5 (Odin tarball)" that puts the custom recovery on the phone via ODIN. The second download, "twrp-3.4.0-0-T290UES3ATC1-20201101.img", is your Nexus Stock Rom for the T290, and is run from the TWRP recovery itself.
Does your T290 feel more responsive - less laggy with your Nexus rom?
sal84x said:
The second download, "twrp-3.4.0-0-T290UES3ATC1-20201101.img", is your Nexus Stock Rom for the T290, and is run from the TWRP recovery itself.
Click to expand...
Click to collapse
Samsung doesn't do flashing via fastboot, so the .img file is really only for incremental updates via TWRP.
sal84x said:
Does your T290 feel more responsive - less laggy with your Nexus rom?
Click to expand...
Click to collapse
I think so, but I might be biased and I haven't had time to run any performance tests. I just posted the first release, though, so you can judge for yourself.
BTW, the $89 Costco deal is back until 12/27.
Quick question, I am having an issue using Smart Switch to make backups for my T500 on my Win10 machine. Seems like it just started and hangs up on applications. Any ideas? Want to install a few Magisk modules but want a back up first.
Magendanz said:
BTW, the $89 Costco deal is back until 12/27.
Click to expand...
Click to collapse
Wow and a free 32GB SD card. Awesome deal! I got mine for $99 from BestBuy with no card.
Would this work on the LTE variants (SM-T295)? I have one of those and I'm kinda tired of the performance issues plaguing One UI on that tablet. :/
TenSeventy7 said:
Would this work on the LTE variants (SM-T295)? I have one of those and I'm kinda tired of the performance issues plaguing One UI on that tablet. :/
Click to expand...
Click to collapse
I've been told that it does, but I haven't confirmed it myself because I don't have an SM-T295.
The links seem to be broken?
TenSeventy7 said:
The links seem to be broken?
Click to expand...
Click to collapse
XDA Forum seems to have lost my last edit. Very strange, but I've tried to recreate it as best I could recall.
Magendanz said:
XDA Forum seems to have lost my last edit. Very strange, but I've tried to recreate it as best I could recall.
Click to expand...
Click to collapse
Okay, apparently the forum now forks a thread if you change the title. Bug or feature?
The new thread for TWRP v3.5.0 on the SM-T290 is here.
Any chance to get a working TWRP for latest stock firmware as of now?

[RECOVERY][UNOFFICAL][LINK FIXED] TWRP 3.5.0 for Samsung Galaxy A6+ 2018

Team Win Recovery Project 3.5.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"
}
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
How to install:
Coming From Stock:
1. Download This TWRP Release and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
2. Under Developer Options, Tick OEM Unlock. It will tell you to factory reset. Do it.
3. After the phone shuts down, press Vol + & - button and at the same time, insert a usb cable to phone connected to a PC.
4. Check KG Status. If it is Prenormal, reboot the phone and follow this guide : (1) How to bypass KG State and/or RMM state prenormal | XDA Developers Forums (xda-developers.com)
5. Zip the TWRP recovery image to tar format and put in the AP slot of Samsung Odin.
6. Flash and after the phone screen turns off, press vol+ and power button.
7. If there is "Set Warrenty Bit : recovery" text on the top left, success!
8. Format data, flash zip downloaded from above.
9. To boot stock rom, install magisk.
From Other Recovery:
Reboot to recovery and flash this TWRP image as recovery and reboot recovery.
ChangeLog:
2021/3/2 Inital Release
Sources:
Kernel : Junak/android_kernel_custom_a6plte (github.com)
Device Tree: roynatech2544/TWRP_device_samsung_a6plte (github.com)
Recovery Source : TeamWin (github.com)
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
NOTE :
I was developing custom roms for A6+ despite of my computer specs. But my phone's LCD went out and I can't test anymore... And it takes 1 day to build in i5-5200U (2C/4T) CPU and 8GB RAM.. Now I can only build TWRP.​
where is the twrp file ?
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
CRDhani said:
where is the twrp file ?
Click to expand...
Click to collapse
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
little_beppo said:
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
Click to expand...
Click to collapse
yes it works.
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Hello
Is this recovery for android 10?
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
abhisekh010 said:
Hello
Is this recovery for android 10?
Click to expand...
Click to collapse
Yes it is compiled in android 10 tree but recovery doesn't depend on android version..
Naddi2Niic3 said:
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
Click to expand...
Click to collapse
PM me
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
okwhateverok said:
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
Click to expand...
Click to collapse
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Thanks, ill hope there will be some users which ow the Galaxy A6 and not using this device as their main phone to be willing to test.
As a IT specialist myself i did try anything to at least help testing for this version of TWRP for our device. I did try to take several rom dumps with professional fabric software and hardware like software dongles but it was impossible to make a full rom dump.
With this said and knowing that a complete data wipe within TWRP is necessary to make the recovery find the internal storage makes it impossible for me to test no matter the fact that the biggest part of this recovery already exist and confirmed working.
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
nqnxev said:
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
Click to expand...
Click to collapse
I could help with the OEM unlock button. What a waist of time these lost 10 days and still no OEM unlock button while the solution is easy...
Follow guide with screenshots: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
And for those who could test on the A600 the recovery image is already uploaded within this thread thanks to Royna
I've tried that many times (no only that, but many similar guides) - and still nothing. From what I read, Samsung just fixed that "date & time" trick and I have to wait.
Ok that is strange, im on android 10 with One UI version 2.0 and got it working. If im allowed to post this link then the rom could be found here: https://www.sammobile.com/samsung/galaxy-a6/firmware/SM-A600FN/PHN/#SM-A600FN
You should do a clean flash without having the phone connected to the internet, not even once because it will do some synchronization. After the flash just follow the guide which could be found on the xda forum..
Thank you for a hint. Because of that I'm waiting so long already I'll wait till end of week and if things still will be the same then I'll try rom you've proposed. Thanks again.
Royna said:
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Click to expand...
Click to collapse
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Adam7336 said:
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Click to expand...
Click to collapse
Well because i don't own that device, it is highly experimental. I will try again.

[DISCONTINUED][ROM][12.1][PAYTON] PixelExperience [AOSP]

{
"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 Moto X4 [payton]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
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
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet ?
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a coffe
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
NOTES (Read First):
* You should be on latest stock firmware
* Clean flash with full data storage wipe is mandatory if coming from older android versions (PE) or any other custom ROM
* JIO VoLTE not working ? Place sim in second slot, clean phone app storage and reboot. Still nothing ? Restore persist/efs or flash stock and go back.
* Installation guide if coming from stock
* If coming from other ROM or older android version:
boot twrp (lastest preferably)
wipe data (full storage wipe) or better fastboot -w
flash rom (twrp installer optionally)
reboot (if you want to flash magisk - reboot recovery and do)
Join Telegram group if you have any questions left !
Android OS version: 12
Security patch level: May 2022
Build author/Device Maintainer: ExactExampl
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Thanks!
Hi, I want to install magisk but now it requires the use of boot.img. I tried a lot but could not extract it. Can you provide it ? Or tell me another way to install magisk.
I managed to do it now
RobinPharswan said:
Hi, I want to install magisk but now it requires the use of boot.img. I tried a lot but could not extract it. Can you provide it ? Or tell me another way to install magisk.
I managed to do it now
Click to expand...
Click to collapse
convey the method
I used this guide.
But you do need to install TWRP. The boot.img file is extracted in the the internal storage unless specified. I have attached my stock boot.img file
https://www.droidwin.com/extract-boot-img-directly-from-device-without-downloading-firmware/
RobinPharswan said:
Hi, I want to install magisk but now it requires the use of boot.img. I tried a lot but could not extract it. Can you provide it ? Or tell me another way to install magisk.
I managed to do it now
Click to expand...
Click to collapse
Why not to just boot twrp and flash magisk apk there (via sideload or from sdcard since encryption is not supported now)
ExactExampl said:
Why not to just boot twrp and flash magisk apk there (via sideload or from sdcard since encryption is not supported now)
Click to expand...
Click to collapse
I didn't know we could do that. I was following the guide where it said you need to have boot image and then modify it using magisk app. Next time I will try this method. Do we have to rename the apk file to .zip
RobinPharswan said:
I didn't know we could do that. I was following the guide where it said you need to have boot image and then modify it using magisk app. Next time I will try this method. Do we have to rename the apk file to .zip
Click to expand...
Click to collapse
No need to rename or anything, it should just flash as normal zip despite it is an apk
ExactExampl said:
No need to rename or anything, it should just flash as normal zip despite it is an apk
Click to expand...
Click to collapse
Thank you.
Hi guys, i installed this rom, starting in the stock rom, but when i start to put some apks, the phone is slow and then goes into boot loop.
this happen since i installed the first version, and then i made some updates via ota, and yet continues with the same problem.
i made a clean flash again, althoug the same problem!
someone with the same problem?
Douglas Miranda said:
Hi guys, i installed this rom, starting in the stock rom, but when i start to put some apks, the phone is slow and then goes into boot loop.
this happen since i installed the first version, and then i made some updates via ota, and yet continues with the same problem.
i made a clean flash again, althoug the same problem!
someone with the same problem?
Click to expand...
Click to collapse
Can you tell me when it happens ? Only while you trying to install apk's ?
Hi, first of all, thanks a lot for the effort of making this rom possible. I would like to ask you, if there's a way to disable/turn off completely the gesture navigation? I only found an option to hide the indicator on the bottom
Vega_ said:
Hi, first of all, thanks a lot for the effort of making this rom possible. I would like to ask you, if there's a way to disable/turn off completely the gesture navigation? I only found an option to hide the indicator on the bottom
Click to expand...
Click to collapse
There's no way to actually do that. But you are free to edit build.prop (qemu.hw.mainkeys=1 should work for this purpose)
Hi,When I inserted the sim card, the phone started to restart automatically repeatedly. It can be used normally without inserting the card or in flight mode, how can I fix this problem
wilber.Y said:
Hi,When I inserted the sim card, the phone started to restart automatically repeatedly. It can be used normally without inserting the card or in flight mode, how can I fix this problem
Click to expand...
Click to collapse
First - which carrier, second - variant of the phone ?
ExactExampl said:
There's no way to actually do that. But you are free to edit build.prop (qemu.hw.mainkeys=1 should work for this purpose)
Click to expand...
Click to collapse
Actually this worked flawlessly for me. Now I was able to get rid of that annoying extra space under the keyboard. Thanks a lot
ExactExampl said:
First - which carrier, second - variant of the phone ?
Click to expand...
Click to collapse
thank you for your reply!
1. The carrier is China Telecom. 2G:CDMA 4G:TD-LTE/FDD-LTE.
2. I changed to another carrier's card and the problem persists. These two cards work fine in other phones. Also works fine in the original Motorola system.
wilber.Y said:
thank you for your reply!
1. The carrier is China Telecom. 2G:CDMA 4G:TD-LTE/FDD-LTE.
2. I changed to another carrier's card and the problem persists. These two cards work fine in other phones. Also works fine in the original Motorola system.
Click to expand...
Click to collapse
I can't tell you what causing this for sure. Did you came from stock right away ? If so, you should make sure that it is latest firmware. Also tell me which variant of the phone you have (XT 1900-x)
ExactExampl said:
Can you tell me when it happens ? Only while you trying to install apk's ?
Click to expand...
Click to collapse
Its happen When I install all apks that I need...
I use about 68...72% of interna memory, and then the Phone starts to come in boot loop...
I restart the Phone some times, until the normal boot....
Sometimes I need to do a factory reset to start The Phone normally...
I can use the rom, but if I add many apks, like Google apks, (PDF, note,) security câmera, WhatsApp, telegram, Facebook and others, The Phone does not work properly
I made downgrade for stock rom using RSA of Motorola, and waiting The weekend to try a New instalation of The rom
@ExactExampl Thanks for having this rom for X4
I'm having an issue where when JioSaavn app reaches its main screen, phone reboots. Kindly check. Let me know if any extra info is needed
Build number: SQ3A.220605.009.A1
PixelExperience_Plus_payton-12.1-20220616-1019-OFFICIAL

Ane-Lx3 update emui 9 [half resolved]

Hi, does anyone know how I can flash the base, curt and preload of the p20 lite ane-lx3?
I got them with hisuite proxy but they give me an error when verifying update.
I need it because I can only go back to emui 8 from hi suite emui 9 does not appear, I had downloaded it to unlock the bootloader. I already unlocked them but I want to go back to the most updated emui or at least more than 9.1.0.142 since it still has the app drawer button.
I have seen that the multi tool 8 can be used to flash but I don't understand how to do it.
antonyx2016 said:
how I can flash the base, curt and preload of the p20 lite ane-lx3?
Click to expand...
Click to collapse
this can be done via modified TWRP, HuRupdater 0.4 or Multi-tool if you are running EMUI 9.1.
But these methods are risky when upgrading from 8.0 to 9.1 and are not recommended.
You can safely manually upgrade to 9.1 only by installing the service ROM using the dload method from the SD card.
What is your full build number? (settings > About phone).
Also check your vendor/country information via the Project Menu (*#*#2846579#*#*) and post the result.
Thank you for taking the time to respond, here I leave what you asked for. I would appreciate it if you could explain a little more how to do the process.
{
"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"
}
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
-Alf- said:
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
Click to expand...
Click to collapse
Good brief update: I tried all the stock roms of ane-l23 all with the same result in the case of emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046 so far everything is fine after reading several forums here I have found one to see the files with root everything is fine up to here I enter /cust/hw and find two folders (la or latam) and normal. and in special cust only after all the props are fine, that is, it is 5.0.0.20.
Then looking for more information to see where the 8.0.0.046 was, I found it in version.prop. Additionally, enter splash2/cust.log and throw a lot of errors in the following post or answer. I leave you the images to see if we can solve something because the problem that bothers me is not being in emui 8 or 9 but that it is not so stable all that works if when installing any firm again the huawei id does not work first playstore and update hsm core after that everything works either themes etc etc.
but it lags a lot in emui 8 and in emui 9 google maps doesn't work so I don't care if I stay in emui 8 or 9 honestly but I do want the equipment to work correctly. Thank you very much for your willingness and willingness to help.

			
				
antonyx2016 said:
emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046
Click to expand...
Click to collapse
It means wrong or incomplete FW. As I said before,
-Alf- said:
service ROM via dload.
You can download Service ROM for your phone
Click to expand...
Click to collapse
-Alf- said:
Here
Click to expand...
Click to collapse
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
antonyx2016 said:
I tried all the stock roms of ane-l23
Click to expand...
Click to collapse
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
-Alf- said:
It means wrong or incomplete FW. As I said before,
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
Click to expand...
Click to collapse
Yes I understand that, but what I wanted to say is that I already tried all the c605 firmware that there is, whether it is emui 8 and emui 9, they all install without error but apparently they do not install at all, I don't know if it is cust the oem partition or something like that but whatever the method, it always ends in .046 the only thing I know for sure is that it started to be like that a year ago when I used hisuite to go back and from there I could no longer update after what happened with hisuite I bought the code in dc to unlock the bootloader but I still can't remove the .046 in a few words hisuite screwed my phone xD because it was never rooted or unlocked until after what I told you
Okay, I don't know what the problem is, two last tips from me:
A) follow this method
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
(reliable source)
B) rebrand to global version C432. But this requires downgrading to Oreo, and this is only possible through HiSuite (because there are no files needed for HuRupdater). It could help to get a fully working phone.
It could happen that before using hisuite you had a different region, not hw/la (claro/la etc.) hisuite couldn't recognize it and downgraded your phone to hw/la. Maybe you should try flashing oeminfo C605.
In fastboot mode run commands :
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the result.
If you decide to rebrand, I will give you instructions.
-Alf- said:
If you decide to rebrand, I will give you instructions.
Click to expand...
Click to collapse
If that helps me, ok, I tried option a) it was installed but it is incomplete with the pink background. If doing a rebrand will help me, ok
antonyx2016 said:
with the pink background
Click to expand...
Click to collapse
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
-Alf- said:
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
Click to expand...
Click to collapse
I think I achieved it in a while I'll tell you what happened but I'm hopeful something changed with the hisuite proxy
Ok, let me tell you, I managed to install firmware 9.1.0.355. I know it's not the latest and it didn't free me from system component 9.1.0.040 either, but at least now everything works correctly.
I'll tell you what I did in case it helps someone else:
1- I did the point a) that you sent me
2- I kept the pink wallpaper and I went to the proxy hisuite and downloaded the cust, preload and base .355
3- it marked an error when installing in the 1% of hisuite the proxy already warned me that it was going to fail and to cancel
4- cancel it and deactivate the 3 checks of point, cust and preload
5-I put in developer mode and look for the update in hisuite
6- This time I no longer throw any errors and it was completely flashed. I imagine that because of step a) the cust was updated and that is why it allowed the .355 to be installed
7-it was still half incomplete but I went into settings and updated and I got the same .355 version and it was installed correctly in quotes as I said I still have the .40 system but everything works now I imagine that if you keep messing around a bit that way it will I could install the .390 but I'm satisfied with the .355

Categories

Resources