Flash the rom with recovery Orangefox.I get a blank black screen after flashing latest A13 builds. I am directly flashing from stock Pie build. Installed custom TWRP recovery. A10 build got flashed without any issue. Any help?
Thanks for the file, I have flashed Orange fox recovery ([email protected]) but now I cannot see files on OTG drive. OrangeFox supports only certain types of file systems? My drive is formatted as NTFS and all files show up in TWRP!Flash the rom with recovery Orangefox.
Stable release vR11.1 for Asus ZenFone Max Pro M1 (x00t) | OrangeFox Recovery Downloads
Orangefox recovery for Asus ZenFone Max Pro M1 (x00t)orangefox.download
Some TWRP can't flash Android versions 11-13 (just like you said), that's why I recommended Orangefox.Thanks for the file, I have flashed Orange fox recovery ([email protected]) but now I cannot see files on OTG drive. OrangeFox supports only certain types of file systems? My drive is formatted as NTFS and all files show up in TWRP!
Update:
I got the OrangeFox show up OTG drive. Looks like OrangeFox sees exFAT. After manually mounting OTG drive, the rom files show and I was able to flash.
But, I get the same issue. After flashing the rom, all I get is blank black screen. Even charging/notification does not work. Only feedback I get is when I boot to recovery/bootloader.
I am doing format data and then in advance wipe, select Cache, data, vendor, cache, system. Then flash the rom. This works for 10 build but not for any thing above (all 11-13 have same issue). Do I have to flash any updated kernel before flashing rom?
Update 2:
After leaving the device in charging for couple of hours with it switched off, I could see charging updated charging indicator, sounds. Even after booting, I get feedback for touch (via vibration and sound) but the device is still blank. Looks like everything is working except for display. I was able to call it by inserting the SIM and swiping it roughly on display where the phone icon would be present during call.
Thanks for the detailed explanation.Some TWRP can't flash Android versions 11-13 (just like you said), that's why I recommended Orangefox.
- Whenever you do the Format Data, it is necessary to restart the recovery, the sdcard will only be recognized after restarting. It is not necessary to do advance wipe after Format Data.
-You don't need to install another kernel, the rom already comes with its own updated kernel. (I only recommend installing another kernel if this problem only happens on this rom)
So far I haven't had the same problem you're talking about. If I were you I would install FIRMWARE-087-X00T (63 and 87 is the most recommended for Android 11-13)
Remembering that this firmware is not a rom, it replaces some important files that are necessary to communicate with the hardware of this smartphone that Asus developed, you only need to flash it once, even if you do the Format data it will not be erased because it's a different partition.
First do the format data, install the firmware and then install the rom, if it doesn't work install another rom with android 11-13.
Nope ... Kernels are flashed after roms. Maybe you should try the recommended recovery only... That is.. latest recovery by VivekThanks for the file, I have flashed Orange fox recovery ([email protected]) but now I cannot see files on OTG drive. OrangeFox supports only certain types of file systems? My drive is formatted as NTFS and all files show up in TWRP!
Update:
I got the OrangeFox show up OTG drive. Looks like OrangeFox sees exFAT. After manually mounting OTG drive, the rom files show and I was able to flash.
But, I get the same issue. After flashing the rom, all I get is blank black screen. Even charging/notification does not work. Only feedback I get is when I boot to recovery/bootloader.
I am doing format data and then in advance wipe, select Cache, data, vendor, cache, system. Then flash the rom. This works for 10 build but not for any thing above (all 11-13 have same issue). Do I have to flash any updated kernel before flashing rom?
Update 2:
After leaving the device in charging for couple of hours with it switched off, I could see charging updated charging indicator, sounds. Even after booting, I get feedback for touch (via vibration and sound) but the device is still blank. Looks like everything is working except for display. I was able to call it by inserting the SIM and swiping it roughly on display where the phone icon would be present during call.
I tried flashing kernel before and after rom. Neither is working. For now trying PPUI 5.2 and it is rock solid. Thanks for everyone's help.Nope ... Kernels are flashed after roms. Maybe you should try the recommended recovery only... That is.. latest recovery by Vivek
yes i confirm it. but this problem is not only in this custom rom, but it has been confirmed that cts fails on all devices using the current custom rom. there was a bug from the google API that caused this problem, cmiiw I read about it in an article recently
yes i confirm it. but this problem is not only in this custom rom, but it has been confirmed that cts fails on all devices using the current custom rom. there was a bug from the google API that caused this problem, cmiiw I read about it in an article recentlyany way to fix
Any way to fix?yes i confirm it. but this problem is not only in this custom rom, but it has been confirmed that cts fails on all devices using the current custom rom. there was a bug from the google API that caused this problem, cmiiw I read about it in an article recently
try root and install safetynet fix
ThankyouUPDATE UPDATE UPDATE
=> Change logs (18th February, 2023)
1. PE13+ source upstremed (upto today)
2. Base source updated from CLO-3100
3. All AOSP dependencies updated to r30
4. Latest February security patch merged
5. GAPPS updated by PE team
6. Kernel rebased on top of CLO-3000
7. Kernel update from CLO-3100
8. WLAN drivers updated from CLO-3100
9. Audio kernel updated from CLO-3100
10. Overall performance improved
11. May be something else here and there
=> Notes
1. Camera bug is still present
2. You can dirty flash but as GAPPS updated, clean flash recommended
3. If you dirty flash, try to uninstall updates of ASI from Settings => Apps => All Apps => Android Settings Intelligence (ASI) => Three dots (above right) => Uninstall updates
=> Thanks
1. Pixel Experience team for PE13+ project
2. CLO LA.UM.11.2.1.r1-03100-sdm660.0 source
3. Pranav sir for device/vendor/kernel source
4. AOSP 13 revision 30 branch
Is the CTS fail fixed in this buildUPDATE UPDATE UPDATE
=> Change logs (18th February, 2023)
1. PE13+ source upstremed (upto today)
2. Base source updated from CLO-3100
3. All AOSP dependencies updated to r30
4. Latest February security patch merged
5. GAPPS updated by PE team
6. Kernel rebased on top of CLO-3000
7. Kernel update from CLO-3100
8. WLAN drivers updated from CLO-3100
9. Audio kernel updated from CLO-3100
10. Overall performance improved
11. May be something else here and there
=> Notes
1. Camera bug is still present
2. You can dirty flash but as GAPPS updated, clean flash recommended
3. If you dirty flash, try to uninstall updates of ASI from Settings => Apps => All Apps => Android Settings Intelligence (ASI) => Three dots (above right) => Uninstall updates
=> Thanks
1. Pixel Experience team for PE13+ project
2. CLO LA.UM.11.2.1.r1-03100-sdm660.0 source
3. Pranav sir for device/vendor/kernel source
4. AOSP 13 revision 30 branch
S fixed
Camera bug fixed by Vivek mayb you check pleaseUPDATE UPDATE UPDATE
=> Change logs (18th February, 2023)
1. PE13+ source upstremed (upto today)
2. Base source updated from CLO-3100
3. All AOSP dependencies updated to r30
4. Latest February security patch merged
5. GAPPS updated by PE team
6. Kernel rebased on top of CLO-3000
7. Kernel update from CLO-3100
8. WLAN drivers updated from CLO-3100
9. Audio kernel updated from CLO-3100
10. Overall performance improved
11. May be something else here and there
=> Notes
1. Camera bug is still present
2. You can dirty flash but as GAPPS updated, clean flash recommended
3. If you dirty flash, try to uninstall updates of ASI from Settings => Apps => All Apps => Android Settings Intelligence (ASI) => Three dots (above right) => Uninstall updates
=> Thanks
1. Pixel Experience team for PE13+ project
2. CLO LA.UM.11.2.1.r1-03100-sdm660.0 source
3. Pranav sir for device/vendor/kernel source
4. AOSP 13 revision 30 branch
But it says bug still present?
Thanks for the bug report.. Just pushed a new update.. Please test and inform if fingerprint working or not..
I guess the reason is from kernel side. Last build is based on Kummun's kernel. But this build is based on pk's kernel.
The charging problem is already the known issue in pk's kernel.
I did the throttle test in kernel 4.4 (Android 13 beta) from Pixel Experience, so others can see the difference in the results.