yashsingh1/xdaforums huggingface dataset:
[Android General] LimeBerry:
Which custom images actually work with Verizon 4G? Looks like Lineage is out.
[Android General] ObtuseFox:
Thanks for all you guys! I've stuck in the bootloop for a while, regardless of the rom. I don't know which one solve my problem, but one of these did its work:

1) I plugged off the device from PC as soon as the flashing is complete.

2) I used "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip", instead of 11.02.2020

3) I only changed "R***.mbn"(recovery) and "Y***.mbn"(system image)

4) I used "lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img" and "open_gapps-arm64-9.0-pico-20210211.zip"

5) Immediately after the flash, the phone entered some blank screen after the proper boot logo of lineageOS.

Ijust reboot and it worked fine after a reboot.

And my experience: everything's better except that I needed to spend some time struggling with Magisk and button remap apps to make it work flawelessly. Especially the battery life. I've done everything I could do with the stock rom, but LOS16 just works much better :)
[Android General] NeedScotch426:
Hello, I may have effectively bricked my Palm. I am wondering if there is any solution. I bought it very recently and of course wanted to get a custom ROM on it.

Here was my process:

-After playing around with it stock, used Sugar to put TWRP and Lineage 16 on it.

-Bootloops, go into TWRP, install the dmverity zip.

-Still bootloops. Decide to use 'reboot edl' and to use Sugar to go back to stock.

-Bootloops still. Go into recovery, it goes to stock recovery.

-Emergency download mode does not work. At the screen it asks you to hold down the power button, it doesn't seem to detect holding down power and instead goes back to the menu.

-Cannot do anything with ADB, says device unauthorized.

-In the stock android recovery, see error saying "E:Failed to save locale to /cache/recovery/last_locale: no such file or directory." Also, poweroff or reboot options in the stock recovery menu just hang the system, have to hold power button to turn off.

If anyone has any solution or insight that'd be nice, I don't quite feel like spending more money another... Thanks if you can help.

Edit: So I let it drain it's battery as it was stuck at the recovery screen. Trying to go into EDL, it shows "No command" with a picture of a fallen android robot. At this point, it looks like I might need an EDL cable, but if I can't get into EDL normally would the cable even force it? Going to try, a $10 cable isn't an issue... But I am not confident.

I am guessing while going back to stock with Sugar, maybe it didn't complete fully or something and the filesystem got messed up. No clue why ADB doesn't have permissions while in recovery, because the options to sideload are in the recovery, but it still doesn't work. I can't go into the OS to enable ADB debugging there, so it's stuck. EDL cable is my last hope, if that doesn't work I guess I'll bite the bullet and buy another one and just be more careful.

Edit 2: SUCCESS! An EDL cable worked. The one I bought is branded as Martview All Boot Cable. Put it in to EDL and Sugar worked just fine, restored my phone back. Now to do this right.
[Android General] ronii1123:
Is anyone able to get GPS working on their GSI rom?

I was on Lineage OS 16 GSI and was not able to get GPS.

If you have working GPS, can you tell me which version of the GSI you're using?

Thanks!
[Android General] tekk42:
Hello,

I'm a silent reader at XDA, having flashed some devices by the manuals provided here within the last 10 years.

Now I got 2 Verizon PVG1000 off eBay recently and intended to change their radio ROM to the PVG1000E/EU version as I live in Germany. Unfortunately, in the threads I read over the past hours, I learned about the different public keys in PVG1000 & PVG1000E hardware and the boot loops this caused when cross-flashing radio ROMs. So, just to exclude misreads on my side: is this still true or does the TWRP recovery ROM represent a way past this, granting LTE connections in the EU even on Verizon PVG Palms?

Thanks for any clarification & keep up your fabulous research,

tekk42
[Android General] LA_Exeter:
Has someone lately tied flashing a GSI ROM?

Last year with my PVG100 everything was working.

When I ty it now, it fails. The same with my PVG100E

Thanks..
[Android General] cfkf:
First of all, thanks a lot to all people here who are helping us getting the most out of our Palm :-)

A few questions:

1) The TWRP build Snoopy uploaded here doesn't seem to be available anymore https://xdaforums.com/t/guide-to-treble-gsi-on-the-palm-phone.4101947/page-2#post-82654073 . Could anyone reupload this? I could try and rebuild it myself but I'm a total noob so I'll probably brick my palm at some point.

2) I am trying to get Lineage OS on my palm. As someone who doesn't know anything about this at all (never rooted a phone before, never installed custom ROM): am I correct in assuming that I have to go through this TWRP stuff (https://xdaforums.com/t/guide-to-treble-gsi-on-the-palm-phone.4101947/post-82614001 - by the way is this still up to date?) before I try and put Lineage OS on my palm?

If so, what is the procedure for getting LineageOS running after doing the TWRP stuff?

3) I see people have succesfully loaded LOS 16.1 and 17.1. Anyone tried 18.1 yet? Seems to be available at Any Yans source here https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/ (I suppose it's lineage-18.1-20210808-UNOFFICIAL-treble_arm64_avS.img.xz that should be used). If not, would it be safe for me to give it a try or am I risking bricking my phone?

Thanks in advance guys.

Fyi I did manage to root my palm already so I'm all set as far as that goes. Didn't go through the debloating process yet though, but I guess I can do that after getting LineageOS (?).
[Android General] Truelan:
Most people does not see this thread anymore.

But, some people see this thread. so, I will post this.

First of all, I'm not good at english. Sorry.

My Device is PVG100E, Japanese Version. I worked this way.

I have no responsibility about brick. so DO IT YOUR OWN RISK.

Just do this way. SUPER EASY.

1. OEM UNLOCK your palm phone.

Only can do in stock rom. so, if in custom gsi, revert to STOCK ROM.

and enter to DEVELOPER OPTION.

2. You can see OEM Unlock option. Turn it on. and your data will be deleted.

without this, you cannot unlock your bootloader.

and turn on USB DEBUGING, open terminal on your pc and hit this.

adb reboot bootloader

fastboot oem unlock

select yes and all done. all data removed.

3. now your phone will reboot and skip setting

go to developer setting and check oem unlock turned on and grayed out.

turn on usb debuging

in PC terminal hit this.

adb reboot bootloader

and now you will see state message UNLOCKED.

4. Just do what you could find how to flash gsi.

No vbmeta needed.

I use this way.

fastboot -w

fastboot erase system

fastboot erase recovery

fastboot flash recovery snoopy20's_twrp.img

fastboot flash system your_gsi.img

fastboot -w

fastboot reboot

5. I tested Andy's LOS18.1, HAVOC 3.12, HAVOC 4.5, and LiRmod

LiR mod worked great with great battery life.

But I find out that LiRmod does not work bluetooth.

so that now testing another gsi.

UPDATE : Bluetooth does not work on AOSP 11 based GSI.

now using HAVOC 3.12 and working great.
[Android General] LA_Exeter:
when flashing system I got the following errors
[Android General] Truelan:
when you download img file, that is compressed as xz. you should extract it first, not renaming it. the img size is 1.8GB, and when you flash it, sparsed 4 part.

also checking you are using latest platform-tools, not minial adb fastboot.
[Android General] Xray2000:
Hi,

Would it be possible to send me the download link of the LiRmod you have installed and tested on your Palm phone ? Thanks!
[Android General] Truelan:
Just google it.

I googled treble gsi.

you will see treble gsi listed wiki.
[Android General] Xray2000:
Do someone has a link for HAVOC 4.5 GSI for the Palm Phone i can not found it anywhere it seems to be offline or something i can only found HAVOC 3.12...

Thanks!
[Android General] Truelan:
Generic System Image (GSI) list

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

GSI LIST. and I tested, 4.5 does not boot.
[Android General] Xray2000:
Oh ok thanks any Android 11 that boots ? you have tested....
[Android General] Truelan:
almost worked. but some rom did not work and havoc 4.5 unofficial included.

Im now using crdoroid mod rom.

But, you should know that, A11 rom has bluetooth issue, so that you cannot use bluetooth.
[Android General] Xray2000:
Ok thanks bluetooth i never use that, will try also crdoroid mod rom then thanks!
[Android General] Xray2000:
To make shure you use this one Unofficial 11 crdrom-v313-210921-arm64-avZ.img.xz ?
[Android General] Truelan:
I used boz. bvz has no gapps.
[Android General] Xray2000:
Ok thanks! What would be best one lite or the normoly bvz ?
[Android General] Truelan:
sorry. not boz. aoz. arm64_aoz image. boz does not match. I confused. aoz has no vndklite image.
[Android General] Xray2000:
Ok thanks!
[Android General] Xray2000:
crdoroid mod rom is a nice rom i only thing it has more battery drain as Havoc has... not shure yet...

EDIT: I was wrong battery keep same as Havoc-OS.
[Android General] Xray2000:
Do you have and use also the Mophie case battery pack? I have buyed one into the USA waiting for it's underway to my country Belgium ;)
[Android General] Truelan:
I tested many gsi rom.

and found some infomation.

Well, stock kernel Version was 3.18...

Simple. Too low for android 10, 11.

so that, I gave up using android 10, 11 rom.

and tested PIE, OREO rom with magisk patched boot img.

in oreo, Lineage 15.1(not phh porting rom) worked.

in Pie, DotOS, ArrowOS, HavocOS, AOSIP worked.
[Android General] lmore377:
For anyone curious, these are all the partitions and the order they're flashed in according to sugar's log file

N1AML0L0CV00.mbn - NON-HLOS
C1AML0L0CV00.mbn - SBL1
W1AML0L0CV00.mbn - RPM
T1AML0L0CV00.mbn - TZ
J1AML0L0CV00.mbn - DEVCFG
V1AML0L0CV00.mbn - ADSPSO
s1amgfl0cv10.mbn - STUDY
Erased - fsg
Erased - MODEMST1
Erased - MODEMST2
q1amgfl0cv10.mbn - SPLASH
L1AML0L0CV00.mbn - EMMC_APPSBOOT
B1AML0L0CV00.mbn - BOOT
R1AML0L0CV00.mbn - RECOVERY
Y1AML0L0CV00.mbn - SYSTEM
21amgfl0cv10.mbn - VENDOR
I1AML0L0CV00.mbn - CACHE
Erased - devinfo
Erased - misc
Erased - config
A1AML0L0CV00.mbn - MDTP
31AML0L0CV00.mbn - CMNLIB_30 / Flashed twice
41AML0L0CV00.mbn - CMNLIB64_30 / Flashed twice
51AML0L0CV00.mbn - KEYMASTER64 / Flashed twice
Erased - fotadata
U1AML0L0CV00.mbn - USERDATA
O1AML0L0CV00.mbn - GPT_MAIN0
K1AML0L0CV00.mbn - GPT_BACKUP0

Z1AML0L0CV00.mbn - PATCH0 / I don't think this is an actual partition. Not exactly sure what happens here but there's a couple of lines that say "Patch: DISK, x, x, x" (where x is a random number) after this

x1a0gf00cv10.mbn - SIMLOCK

There might be some stuff I missed
[Android General] tgraneberg:
Anybody managed to get anything newer than Pie running on their phone?
[Android General] Truelan:
A11 works. but could not use bluetooth, auto brightness.

A10 works. but could not use auto brightness.

A9 works. but could not use auto brightness.

if you want daily driving, choose A10 or A9

in A10, crdroid mod will be a good choice.
[Android General] tgraneberg:
Do you have a link for some that work?

I've tried Crdroid but after the boot animation it reboots.
[Android General] Truelan:
Generic System Image (GSI) list

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

Generic System Image (GSI) list

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

CAOS Project

GSI Treble patches. Included Phh, Andy Yan and my personal Treble works. You can using patches/solutions from here and from linked manifests (all or few my own) in none-commercial usage only and yo...

github.com
[Android General] codemaster256:
I beg you, please help me get rid of encryption. I also modified this file, replacing forсencrypt=footer with enсryptable=footer, then I formatted the /data partition in TWRP and hoped that after that the system would not encrypt the user data partition. But unfortunately, after loading the phone and then rebooting into TWRP, I do not see the contents of the /data section.

please share these files. I really want to disable dm-verity.

Thank you for the most interesting story about the research of this phone. I use it with pleasure, since this phone is very convenient to carry in a case that is attached to the arm (a place from the shoulder to the elbow). I would like a bigger battery, but by turning off everything unnecessary and reducing the performance of the processor and video card, you can achieve an increase in battery life)
[Android General] xerootg:
Are you mounting vendor in twrp? What is the full file path your editing? I change forceencrypt=footer to encryptable, not encryptable=footer. It results in a kernel message at boot about no such tag, so I suspect outright deleting the entire value would work. I've done quite a bit of massaging of the vendor partition on my desktop, its very much a thing to mount a vanilla vendor image on your machine, modify it, and then flash it with something like emmcdl or the patched version of qdl that I have on GitHub. https://github.com/xerootg/qdl (the pepito branch, I filed a PR against the original repo w/ no response from the owner)

kernel is here - https://drive.google.com/drive/folders/1pgZVMFX9Azzaknl9K22l7ekih9FKVjeZ

Flashing the kernel - do it from recovery:

or do it via qdl/emmcdl w/ this xml, but understand that it's on you to ensure that your GPT matches mine AND that you have a COMPLETE BACKUP. I have destroyed one phone with emmcdl, to the point that I cannot get the imei to register. It's a glorified 3.3" android tablet now. remember, the bootloader on this phone is jankey, see below.

in other news:

I'm very green at the android build mess, but I'd like to get a device root together. This phone deserves so much more than the stock rom. I really really don't think that the stock bootloader is unlockable, atleast for the pvg100 sku, so we are stuck with the 3.18 kernel, and therefore android 10 max. I'm saying, temper your expectations, no matter what we achieve with the vendor partition and GSI images.

I've tried every single thing I can with the devinfo, misc, and config partitions to unlock the bootloader or attempt to modify the boot process. All of the usual tricks, with their addresses validated in the decompiled aboot dump, do not seem to circumvent kernel signature validation. It really seems like the aboot code was modified in such a way that it was compiled with fastboot and unlockability codepaths in the binary, but not reachable. Decompiled code is incredibly hard to follow, so its not like I can understand everything going on without the original code or another set of eyes on the decompiled mess. I've been using a build of lk2nd with a device tree I extracted from the stock kernel, and the phone reboots before the palm phone comes up, telling me that it fails to validate the boot image and reboots.

We can't replace aboot because the pbl validates aboot's signature. Aboot is what validates the kernel image, and it is not unlockable. this means the pbl needs to be breached (I'm not sure that's happened, I don't have the skills either), or we do tethered boot. There's some very interesting stuff for a xiaomi phone where the edl is used to patch aboot, which is then re-executed to enable kernel signature validation to be bypassed, but means that the entire boot process is only possible with a desktop to execute the whole mess. Not my idea of a small, convenient phone.

so, keep your eye out for a GitHub repo to hack on, I'll post it here.
[Android General] braxtron:
Every time I install lineage os I get a boot loop with the message:

"Your device has loaded a different operating system"

I'm pretty sure the flash via sugar is working correctly because TWRP *is* installed and I can boot to it by holding the power button long enough. I've tried:

lineage-17.1-20210808-UNOFFICIAL-treble_arm64_avS

lineage-17.1-20210714-UNOFFICIAL-treble_arm64_avS

lineage-17.1-20200808-UNOFFICIAL-treble_arm64_avN

lineage-17.1-20200511-UNOFFICIAL-treble_arm64_avN

with a magisk patched boot image flashed from TWRP.

When I go to reboot or power off in TWRP it says "No OS Installed!" But I can't understand why...Is it just my boot.img that's messed up? If I let sugar run with the backup I took the first time I ran it, it boots the stock OS just fine.

In sugar I'm using "PVG100" as the device but I also noticed there is a PVG100E. I believe this is the Verizon no sim pop-out version.

Any help is appreciated!

EDIT: So it looks like the problem is most likely my patched boot image I'm flashing via TWRP. I've tried the automated Disable_Dm-Verity_ForceEncrypt_11.02.2020 script, as well as manually magisk patched boot images using different combinations of the 3 options, in parentheses are what I think the correct option is:

Prserve AVB 2.0/dm-verity (False)

Preserve force encryption (False)

Patch vbmet in boot image (True)

So the first post says the automated Disable_Dm-Verity_ForceEncrypt_11.02.2020 script has problems with AOSP 10, so I installed AOSP 9 and then ran that script and it results in a quick boot loop, about 1-2 seconds between reboots. I can still successfully flash stock OS and boot, I'm about losing my mind lol.

I tried magisk patching the boot image on a PVG100 and a Pixel 3, both result in same bootloop/No OS Installed message in TWRP
[Android General] Gestalt73:
Wow, so exciting to see anyone working on palm / pepito stuff...

UPDATE: I'm trying this recipe again to see if it has the same problem as the one below. I'll check back in a couple of weeks and let you know.

Ok, here's my recipe:

snoopy's "twrp-3.3.1-pepito-nofirmwaremount.img" as R*.mbn

andyyan's "lineage-17.1-20200808-UNOFFICIAL-treble_arm64_avN.img" as Y*.mbn

(TWRP > Wipe > Advanced > System > Resize then System > Repair)

"Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip"

"open_gapps-arm64-10.0-nano-20220215.zip" (nocheck-modified)

"Indistract Minimalist Launcher"

The gapps was a bit of a pain. If you try to install the zip as-is you'll get an error about an incorrect android version (10.0 vs 8.0). Editing install.sh in the zip to disable both version checks allows you to complete the install just fine. My guess is that earlier versions didn't do a version check, but later versions do and it trips up the install.

What's been working for you? I'd also be interested in your Android 10 and 11? recipes.

Alan
[Android General] Gestalt73:
UPDATE: This runs perfectly for about 2 weeks, then hard locks and requires a hard reset and format. I haven't had time to figure out why. :-(

Ok, here's my new favorite recipe:

snoopy's "twrp-3.3.1-pepito-nofirmwaremount.img" as R*.mbn

magisk-patched B*.mbn, you need this to complete the framework-res install

andyyan's "lineage-17.1-20210714-UNOFFICIAL-treble_arm64_avS.img" as Y*.mbn

(TWRP > Wipe > Advanced > System > Resize then System > Repair)

"Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip"

"open_gapps-arm64-10.0-nano-20220215.zip" (nocheck-modified)

"Magisk-v25.2.apk"

MishaalRahman's "framework-res__auto_generated_rro.apk" for automatic brightness control

"Indistract Minimalist Launcher"

The gapps was a bit of a pain. If you try to install the zip as-is you'll get an error about an incorrect android version (10.0 vs 8.0). Editing install.sh in the zip to disable both version checks allows you to complete the install just fine. My guess is that earlier versions didn't do a version check, but later versions do and it trips up the install.

What's been working for you? I'd also be interested in your Android 10 and 11? recipes.

Alan
[Android General] xerootg:
I've got CAOS11 running, AND STABLE. I'm working on actually building a less-handrolled system partition, with the October patches (9033583/android-security-11.0.0_r60). I've been running r48 as my daily rom for two weeks on Friday, so there is still life to be had for us out of these phones. Still gonna be my patched magisk kernel and hand build vendor though... This phone rocks. Just to think I had almost given up after spending a couple weeks in ghidra to find the bootloader impossible to truly unlock.

EDIT: My current recipe is a super stripped-down vendor with my patches from above, the March release of CAOS11, and the magisk kernel I have on my google drive. The way I built that was with the magisk 23 zip from phh, followed by disable-dmverity, followed by magisk 25.2 as a zip, and only then reboot. The older disable-dmverity that works required a much older version of magisk to work, but I wanted a newer magisk. I extracted it after I got a good boot cause it was very finicky to get it to work.
[Android General] xerootg:
The 'E' is the European variant. Different alot of things. Different keys (which are burned into ROM for all intents and purposes) for signing the kernel and bootloaders. The NON-HLOS partition is apparently worthwhile for some extra bands, but I've been focused on a modern version of android. Maybe once I have a stable, patched build of android 11 I'll look at the E variant's NON-HLOS.
[Android General] braxtron:
Is this the step I skipped that caused the entire thing to fail and report "No OS installed?" I'd kiss you on the mouth after wasting so many hours. That hasn't been a clear step from all the research I've done lol.
[Android General] braxtron:
Sounds interesting. I Mine is VZW version as I'm on VZW.
[Android General] xerootg:
I'd add one more, I've had bad luck with any of the system partition provided mkfs.e2fs's. I make sure I am using the one from the recovery partition. Same with resize2fs. That might be why you get strangness when the rom resizes itself?
[Android General] braxtron:
I'm not sure what you mean by all that. I've only used the snoopy recovery and my own magisk patched boot file. I've never done any resizing, which it sounds like was my main problem. But I have not manually used, nor do I know the difference between, mkfs.e2fs or resize2fs, or what they do/are.
[Android General] xerootg:
Essentially, the vzw and non-vzw builds seem to differ in build.prop values only. the non-vzw vendor includes vzw specific apks. I'd say pick a kernel/vendor that is stable for your purposes and run with it. I think someone earlier in this thread had a very specific, 1 series kernel they liked for power consumption, but I use the latest 3 series builds cause it's one less thing to tweak with cause it just works.

essentially, some roms, at first-boot, resize the system partition to the full size the phone reports it's got available. There's something about the snoopy provided versions of the tools that are used that works whereas the ones that are baked into some roms produce non-booting phones. I really wish I could build snoopy's recovery, cause I'd love to add to it a bit and use a newer kernel, but I have failed to build a bootable twrp build many times.
[Huawei P30 Pro Questions & Answers] europc:
hi everyone i would like to ask you where can i find oeminfo for vog-l29?
[Huawei P30 Pro Questions & Answers] adambrown:
Is not settings, only using ADB commands can know it. But can i ask why you need it? You can't use it without root to rebrand phone.