Join us on Tl   Wh

Hovatek Forum DEVELOPMENT Android [Please help] Unable to boot compiled or online generated TWRP

[Please help] Unable to boot compiled or online generated TWRP

[Please help] Unable to boot compiled or online generated TWRP

hasano
hasano
hasano
Newbie
2
03-12-2024, 04:02 PM
#1



Hi everyone,

I need some help regarding booting/building TWRP, and for that here's the context :
Not so long ago i bought an android based gaming handheld, namely the pimax portal retro, it's based on XR2 SOC which is a binned snapdragon 865
It's coming with an unlocked bootloader and an Android 10 version
It is rootable using patched boot.img 
I have the Qfil stock rom and i know the motherboard pins to short  to access EDL which make the device pretty much unbrickable
Althought it is an A/B device i can see a recovery partition, and also recovery.img in the stock rom

Here is the stock situation
if i adb reboot recovery i land on this screen (basically i can do nothing in it) 
https://imgur.com/M96MAHz

if i adb reboot fastboot i land on this screen (basically fastbood)
https://imgur.com/LtGmgkN

i can then access stock recovery from there :
https://imgur.com/iESsjkp

I tried the following : 
  • Building the twrp using the hovatek online builder, i manage to feed it my recovery.img, feeding boot.img was not successful 
  • Compiling TWRP using twrp-11 branch based on device tree generated by aospdtgen
  • Compiling TWRP using twrp-11 branch based on device tree generated by twrpdtgen
  • Compiling orangefox using fox_11.0 branch  on device tree generated by aospdtgen

I built the boot.img mainly, because as you can see in the device tree the flag  :  BOARD_USES_RECOVERY_AS_BOOT := true
but i also tried with a compiled recovery.img
The results are always the same : 
  • flashing boot.img results in a stuck boot logo, device is not able to boot to twrp or rom
  • flashing recovery.img results in a bootloader bootloop

Also, I'm not able to fasboot boot, it's unsupported, i can only fastboot flash, since i can revive the device it's not an issue 
When flashing i tried to disable verity for vbmeta and vbmeta_system, results are the same
i always flashed over stock rom (i.e not rooted)
i tried adding/updating different flags on the device tree but again same results

Here are my device trees : 

https://github.com/hmajdouli/pimax_porta..._aospdtgen
https://github.com/hmajdouli/pimax_porta..._twrpdtgen

Sorry for the long post but i wanted to add as much details as possible
This post was last modified: 03-12-2024, 04:07 PM by hasano.
maxpayne
maxpayne
maxpayne
Intern
4,059
05-12-2024, 11:46 PM
#2
(03-12-2024, 04:02 PM)hasano Sorry for the long post but i wanted to add as much details as possible

Run 2 quick tests:
1. Flash the stock recovery in fastbootD. Confirm all works fine
2. Unpack and repack the stock recovery (no modification made) then flash the repacked recovery (to recovery partition) and see if it still boots fine

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
hasano
hasano
hasano
Newbie
2
10-12-2024, 12:00 AM
#3
(05-12-2024, 11:46 PM)maxpayne
(03-12-2024, 04:02 PM)hasano Sorry for the long post but i wanted to add as much details as possible

Run 2 quick tests:
1. Flash the stock recovery in fastbootD. Confirm all works fine
2. Unpack and repack the stock recovery (no modification made) then flash the repacked recovery (to recovery partition) and see if it still boots fine


Thanks for your help but i already tried that.
In fact the issue was my trust toward the TWRP device tree generators
In the end i started from twrpdtgen device tree and added some flags from oneplus 8t twrp device tree (a device with a similar SOC)
it worked perfectly
This post was last modified: 10-12-2024, 12:00 AM by hasano.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
Join us
WhTlYt