yashsingh1/xdaforums huggingface dataset:
[Android General] HepCat86:
Hi LineageOS 17.1 pioneer! GAPPS should be installed after Dm-Verity zip that's for sure. After Step 6 I did a resize of system partition, then wiped data and then mounted data and copied GAPPS zip and flashed it, reboot and OS successfully started.
[Android General] snoopy20:
Magisk comes as part of dm-verity, you need only install the manager app to get the "su permission" trigger.

If you just need Google Play store, see Fdroid -> Aurora.
[Android General] edg3:
Brilliant, I managed get the GApps mini package installed and a clean boot - it must be the additional wipe of data as I definitely tried it both before and after my Step 6 otherwise.

Although it is now back to a bootloop after trying to get Magisk working haha!

If I install the Magisk Manager app, then it says Magisk isn't installed, and gives me the option to download the zip or patch an image... it doesn't seem like it is installed by dm-verity for me.

From reading a couple of other threads/posts (not specifically for this device) someone says they had success by installing Magisk and then the dm-verity script so I'll give that a go another time.
[Android General] Swimming33:
yep, actually used the right zip, then gapps, and now it's aalllll working fine, Android 10 on the little Palm phone :)
[Android General] edg3:
Following up on this... reading the thread by [MENTION=4467696]AndyYan[/MENTION] it says:

"LineageOS 17.x has lost some features in the process of transitioning to Android 10, e.g. Privacy Guard and built-in SU."

"If using Magisk on an A-only device, a modified Magisk is required."

Reference: https://xdaforums.com/project-treble/trebleenabled-device-development/gsi-lineageos-17-0-gsi-archs-t4004673

Will give it a go with the modified version and report back.
[Android General] sergio_chichi:
Any success in getting root on Lineage OS 17.1?
[Android General] edg3:
None whatsoever. It always bootloops after any install of Magisk.

I even tried it on AOSP 9.0 (which runs great with PHH Superuser fyi) and that also bootloops after trying to put any version of Magisk on.

I'm also struggling with TWRP... it never seems to mount data unless you've just wiped it. It doesn't seem and to decrypt the partition to be able to mount it - is this the same for you?
[Android General] sergio_chichi:
I just tried once and got bootloop.

For AOSP 9.0 I patched the bootimage (the one with Bxxxxxx.mbn) in magisk to get root. The AOSP seems to have a much better battery management than the Lineage OS (16.0 and 17.1.). So I will try to get AOSP 10.0 on my Palm or stick with the AOSP 9.0 (which runs great and needs 15-20% battery/day in standby).
[Android General] snoopy20:
I'm finding Lineage 16 battery life to be equal to ASOP (so fantastic).
[Android General] edg3:
Yep that way worked :) So I'm now running this (https://github.com/phhusson/treble_experimentations/releases/tag/v123) with the Verizon stuff removed using inspiration from [MENTION=1096286]snoopy20[/MENTION]'s debloat thread/script.

Haven't used it heavily but so far everything I have tried appears to be working - including the hardware button imitate stock behaviour with the help of an app. It won't be a daily so my battery life will vary but as a novelty/backup device it's looking pretty good so far.
[Android General] sergio_chichi:
Recommondation for hiding the navigation bar: "adb shell wm overscan 0,0,0,-100". This pushes the nav-bar out of the screen. if you want just to navigate with the 3-Dot hardware button.
[Android General] snoopy20:
I have found the 3 dot too laggy to be useful.

Hopefully everyone knows there is a hardware bug around the USB port. If you switch from enumerated power (computer) to non-enumerated (standby, USB powerbank) without unplugging the USB at the Palm end then it will fail to charge and drain the battery from 100 to 0% within 7 hours, guaranteed. It's annoying as I standby my PC at night and have to remember to unplug/replug.

Also looks like all the cheap Verizon phones from the U.S are finished. Shame as I went to buy a second.
[Android General] delawaresace:
I'm a little embarrassed to say that I'm stuck and I feel that it's a simple fix but still can't seem to find the solution. I followed the steps, got TWRP, and tried to load LineageOS 17, but it didn't work. Then I remembered someone said to wipe data. Long story short, I wiped everything. I don't have an OS and I can't use Sugar because when I hold down the power button,my phone now only boots into TWRP instead of fastboot. So now my phone is stuck in a boot loop with no OS. the LineageOS file I have (lineage-17.1-20200511-UNOFFICIAL-treble_arm64_avN.img) is in a .xz format and I'm not sure how to flash that onto my phone using TWRP. Any suggestions?
[Android General] edg3:
Don't feel embarrassed!

So first, the .xz file, you need to unzip that with 7-Zip or similar, and then it's an .img file, which you can rename to the Y___.mbn file.

Now to rescue your phone, boot into TWRP because you can (hold power for 3 reboots). Then go to advanced and terminal, and type in "reboot edl" and then you're back in the emergency download mode you've used before and can either flash stock files, or your modified ones, in Sugar.
[Android General] delawaresace:
Thank you sooo much! I now have LineageOS 17 booted up and am now setting it up. this is great.
[Android General] delawaresace:
So I'm not sure what I'm doing wrong. I can't seem to keep data mounted. I use Sugar to flash TWRP and LineageOS 17. I push Disable_Dm-Verity_ForceEncrypt and GAPPS nano and flash the zips. I reboot and it just sticks on the Lineage boot screen. I read that maybe resizing data might work, but when I go back into TWRP, data isn't even mounted and when I try to mount it, I cant check the box. it just highlights when I press it but doesn't check. any ideas?
[Android General] CaptainElwood:
When you first got to TWRP you needed to have formatted data, this removes the encryption so the partitions are available to see/use in TWRP. You can do it now but it will wipe everything.
[Android General] CaptainElwood:
I was having trouble getting Android 10 (AOSP or LOS) to boot and tried multiple images with no luck, every time it would lead to very fast bootloops after rebooting from TWRP. I finally looked to go back to 9 and had a saved copy of the Sugar downloaded files that I was previously running without issue. I noticed that I had changed the file extension on the TWRP image to .mbn but the system image was still .img. When I was trying all the android 10 images I had been changing the file extensions to .mbn, so just to try it one last time I left the system image as a .img and for whatever reason it worked with LOS 17 on the first try. I have no idea why changing the file extension on the TWRP image doesn't matter but changing the system image extension does. Maybe this is the same thing others are doing that have had trouble getting this process to work.
[Android General] delawaresace:
So I've done these steps and I'm still not able to get LineageOS 17 to work

1: open Sugar and download/install the stock rom

2: copy device folder from sugar

3: replace and rename the two files

4: move the folder back, open sugar, and hit install to flash the new recovery and lineage onto the device

5: boot into twrp, hit format data.

6: transfer over the DM-verity zip to the device and install it via twrp

I've double checked the MD5 hash of all the files (TWRP, LineageOS 17, DM-verity) and everything matches. When I reboot, it just hangs on the LOS17 boot screen. I try to then go back into TWRP and when I do, I can't mount or format data.

also, I've tried to resize the data partition, but was not able to at any point. I kept getting errors in TWRP.

UPDATE: So, I finally got LineageOS 17 loaded. I tried to load AOSP 9, failed, and tried LineageOS 17 again and it worked. made a test phone call and some other stuff. So that's good news. but now I'm trying to get GAPPS loaded. i boot into TWRP and data isn't mounted. when I try to mount it and just as before, I can't check the box. without data mounted, I can't install the zip file for gapps.

UPDATE 2: I seem to have everything working now. Gapps is loaded and I am testing everything out now
[Android General] tuuure:
Trying to unbrick a Verzion Palm, but got an error flashing the stock firmware with Suger. The Suger log file shows

2020-06-14 07:56:30.164 Handset.cpp 3848 LOG Upload report in imei failed C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\tool\..\output\QP_[IMEI_MAC ADDRESS]_SUBRECella_2020-06-14-23-56-24.nck, download after

2020-06-14 07:56:30.165 PEPITO.cpp 0150 LOG COM7 Backup NCK File failed!

2020-06-14 07:56:30.165 FirehoseHandset.cpp 0576 LOG [COM7] Download secrity file failed!

2020-06-14 07:56:33.170 EmmcModel.cpp 1728 LOG reset:<?xml version="1.0" ?><data><power value="reset" /></data>

And I notice the Original Ver becomes 2AGMM0M0. It used to be 2AGGUFG0. I spent hours but couldn't make it work. Any idea how to fix it?
[Android General] snoopy20:
Lineage 16 - the ROM defaults to 3g mode. When switching to 4G/LTE it bricks the phone.

Now trying 17...
[Android General] snoopy20:
As a guess your modem partition is corrupted, this is where the imei lives. IIRC it's /dev/mmcd0p0 or something like that. Anyhow, it's a fat drive which is how the modem chip loads the firmware. Maybe you can mount it in twrp and run fsck?

---------- Post added at 03:01 PM ---------- Previous post was at 02:23 PM ----------

Lineage 17 -

1. you MUST recreate the ext4 partitions right after running dmverity before you reboot. You can tell if it's worked as going back into twrp after a reboot the data is mounted. If it isn't mounted redo it as you won't get into lineage.

2. as I've said before there is a bug with the USB cable on first boot, you must remove it or it hangs on the animation screen.

Also I'm using the patched B file for root. The B file has never changed file size so feel free to use a previous one (as I did). For the European R file (haven't tested the Verizon one) the Modem defaults to 3G. Change it to LTE if you're wondering why internet is a bit slow. :)

I had 1. exactly like everyone has and resolved it, now on L17.
[Android General] james20n:
thanks for this thread, im a total newbie with all this stuff but I was able to get Lineage17 running on the palm. I skipped the gapps tho and now want to try adding them but when I boot into TWRP and try 'adb reboot edl' i get abd: not found...is there something else I need to do first to get back in edl
[Android General] a.vandelay:
It sounds like that's a PATH issue on your computer, not the device. Where did you put adb.exe (or just adb on *nix)? Make sure you can run it from your shell first
[Android General] a.vandelay:
Update for those having trouble with certain system images!

I noticed that before using the Disable_verity.zip, the device would boot loop after ~5 seconds. You can force into TWRP and get the failed boot dmesg (it's in /sys/fs/pstore/) and see that boot is failing due to AVB. After flashing the Disable_verity.zip, the boot loop was immediate (less than 1 second) which indicates boot.img corruption.

First, you can use TWRP to flash boot images. Push the boot image to the device (renamed to <something>.img) and use Install->Image. Putting the stock boot image back returns to the 5 second boot loop. Then I pushed the stock boot image to another device running MagiskManager and used Magisk to patch the boot image. Use TWRP to flash it to the Palm, and it works.

So perhaps the Disable_verity.zip script does not always work, in particular on AOSP 10. I am currently running Phh latest Android 10 (arm64 A-only with Android Go) using the above method.
[Android General] james20n:
thanks, fixed it.

Now when i try to install gapps nano in TWRP i get an error for insufficient storage in system partition, i don't see an option to increase partition size anywhere?

Also when Lineage17 was running i couldnt get it to recognize my SIM card...anyone run into that?
[Android General] james20n:
So here's what I've done:

1. Reflashed to stock in Sugar

2. booted into stock, it recognizes the SIM, have 4g data voice and text

3. Flashed back to lineage17 from the source linked here

4. Formated data, ran DM_verify and Gapps nano

5. No boot loop, everything sets up fine, gapps installed but will not recognize SIM card. IMIE is intact

The weird part is I can receive texts and calls just fine, but I can not use data or send call/text .

EDIT: Wiped everything and flashed AOSP 9.0 and same thing, no SIM card
[Android General] zoomer296:
Is the EDL tool necessary to switch GSIs once TWRP is installed? I see no option for a direct image flash to system.
[Android General] a.vandelay:
TWRP doesn't flash system images directly, only boot and recovery. At the moment it seems like EDL/Sugar is the only way.
[Android General] a.vandelay:
Another method is to backup your working boot image on say, AOSP 8.1 or Lineage 16/17. That is, back up a patched/working boot image from a GSI enabled device. You can then use that boot image in your Sugar flash to avoid having to re-disable verified boot each time you switch system images.

I did the following: Flash Phh Treble AOSP 8.1, patch the boot image, backup/download the boot image from the working device, and then flash that boot image with AOSP 10.0 from Phh and it booted up straight from Sugar.
[Android General] zoomer296:
So the stock recovery has to be reflashed?
[Android General] a.vandelay:
No. You can replace any stock MBN with a custom image (renamed to match the stock image) with your preference, similar to how you replaced the system image. Rename TWRP to RXXXX.MBN and flash it with Sugar.
[Android General] zoomer296:
Is there a way to get into EDL without stock recovery?
[Android General] a.vandelay:
adb reboot edl
[Android General] james20n:
Update on my situation

Went and picked up a few SIM cards from other carriers. It recognizes all GSM SIMs, but any CDMA SIMs get the no sim card message.

This was on LineageOS 17.1, I assume it's the same for AOSP 9 since I was having the same issue when that one was flashed.

And once again when I flash back to stock CDMA works fine
[Android General] th3_gunn3r:
Thanks for your work devlopers
[Android General] hardbodyrichert:
Try just "reboot edl" from the terminal in twrp (no computer needed) instead of "adb reboot edl." That worked for me. :good:
[Android General] HepCat86:
Might be cool if someone would manage to boot Ubuntu Touch GSI rom as instruction is already posted online here at xda.
[Android General] mlgmxyysd:
Can this twrp mount /data?

I flashed with dd if=/sdcard/twrp-3.3.1-0-pepito-nofirmwaremount.img of=/dev/block/mmcblk0p26, the recovery log says "Could not mount /data and unable to find crypto footer. Failed to mound /data (Invalid argument) Unable to recreate /data/media folder"

Should I format /data partition?
[Android General] dedero:
Thanks for the info!, would you please share which LineageOS 16 image have you installed?

Cheers,

Bruno
[Android General] dedero:
Thanks a lot for sharing your experience!, it helped me a lot.

I bought a PVG100E using Vodafone Germany SIM and I had almost the same experience you had so far, in my case I couldn't ran any Android 10 ROM, it kept in a bootloop every time, even with Havoc OS..

The problem I had with Android 9 ones was that I couldn't unlock my SIM card, for some reason this phone everytime I flashed an Android 9 Rom, include Lineage, I've never got the prompt to insert the unlock code so my SIM was unusable, so far I can agree with you that the most compatible ROM around is Phh AOSP 8.1

I've always used arm64 Aonly vanilla ROMS

For some reason, for most of the ROMs I've tried, I had to return to the stock firmware and then install a new custom ROM, otherwise Sugar showed "your device was rooted" and I couldn't go forward..

Using "adb reboot edl" for emergency download and "adb reboot recovery" saved a huge amount of time during the process..

Still hoping some day a LineageOS 16 or 17 will come up for Pepito

Cheers,

Bruno
[Android General] zoomer296:
Ubports GSI requires a Halium-patched kernel.

---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------

Any chance of a proper ROM? Also, what prevents us from flashing system via TWRP?
[Android General] C_CWang:
i wonder if this guidance can be applied on chinese version of this tiny phone:silly:
[Android General] zoomer296:
Any chance of a proper ROM?
[Android General] a.vandelay:
The phone doesn't have fastboot or any way of flashing images online, so I don't know. It seems like we're stuck with EDL.
[Android General] kxkixi:
Take this with a grain of salt, on a completely "works for me" basis. I am not responsible for what you do with your own device. Do not blame me should anything negative come from this advice.

That said, flashing new images without Sugar-QCT after TWRP is installed:

# While booted to TWRP recovery...
adb push your_gsi.img /tmp/
adb shell /sbin/simg2img /tmp/your_gsi.img /dev/block/mmcblk0p27

Be aware that, unlike using Sugar-QCT, this does not reset any other partitions to their default state. You will probably need to, at least, format the data partition after flashing a new ROM, since all of our efforts to keep data decrypted so far have been in vein.
[Android General] delawaresace:
I need a little help. I don't know what went wrong. I was rocking LineageOS with no problem until one day it rebooted on me and then came up with a blank screen. I believe that the LineageOS is still there working, just that the screen or the launcher isn't working. For example, I had a short cut to long press the power button to turn on the flashlight. This still works. I can boot up into TWRP with no problem. I thought I'd just reload everything again from the start, but it seems that Sugar is now a no go and the log in doesn't work anymore. does anyone have any ideas? I've tried to wipe the data through TWRP but data isn't mounted. I've tried to connect the phone to my computer, but it doesn't reconize any devices when in powershell I type adb devices. I'm out of ideas and am hoping it's just something simple that I overlooked. Thank you
[Android General] kxkixi:
Do not wipe data, format data. From the TWRP main screen, go to "Wipe", and then tap the button towards the bottom right that says "Format Data". As opposed to wiping, this action should prompt you to type "yes" to complete the format.

Sugar and associated credentials from the post linked in the OP are still working fine for me.

If you no longer have access to Sugar but still have access to TWRP, my advice from my last post also works with the stock image if you still have a backup of it. The file to flash would be the Y*.mbn file. You would need to make sure data is mountable and use /sdcard/ instead of /tmp/ because the file is too large to fit in the RAM.
[Android General] delawaresace:
Thank you for your help. I don't know why I got wipe and format mixed up. it's as if I had blinders on and not only did I forget about the format button, but I didn't even see it the multiple times I was on that screen.

Either way, formating my phone worked. I also went in and resized data again just to make sure. I rebooted into the system, but I still got the black screen. I rebooted again and it worked! I'm setting up my phone again, but I only really use it as a GPS tracker for running and my Audible device, so it's not to hard to set up. :victory::laugh:
[Android General] zoomer296:
TWRP should support flashing system images, but that's probably an option enabled during compilation.

Could we try Using TWRP from a device that supports flashing system as a base?
[Android General] gophersalesman:
How do I enable root access? I follow all the steps have my rom successfully installed, however, when I download Magisk Manager it says I do not have Magisk installed. I saw edg3 had this issue on page 8, but I didn't see a solution? What am I missing. Any help would be appreciated :)

Edit: Additional info. I am able to root my phone using the method in the [Release] Root the Palm phone post. However I am unable to root my phone using this guide. Any help?
[Android General] PrinterB:
Any updates on this, [MENTION=5719791]kxkixi[/MENTION]? I've spent the past few hours following in your footsteps with no more success than you.

8.1 works great other than not being able to use VoLTE on Verizon. I wasn't able to get 10 past its boot anim. 9 worked, but wasn't recognizing the SIM at all.

For now, I'm unfortunately moving back to stock since nothing else seems to be working. Guh! x.x
[Android General] halbertweber:
No Cell Service

I've been able to get LOS 17.1 up and running with everything except cell service. I'm on Verizon in the US. I can't even select Mobile Network in settings. It's grayed out. It worked fine on stock. Any suggestions?
[Android General] a.vandelay:
I think there are known issues with verizon on GSI roms. some searching might yield some troubleshooting ideas, but I never got it to work.
[Android General] halbertweber:
That's what I was afraid of. Back to stock I go :-/
[Android General] Altham06:
I've read that running unencrypted improves performance and battery life a little bit. So i wanted to test that out.

So after booting with the magisk patched img, installed magisk manager and a root explorer, searched for an "fstab" file and found "fstab.qcom" under: vendor/etc.

Opened it, edited "forceencrypt" to "encryptable", saved it, boot into TWRP, format data and boot into system.

I honestly didn't think that would work, but phone stays decrypted.

(Using phhusson's AOSP 8.1 v32)
[Android General] ddjljbb:
I never succeeded in getting the phone rooted (taking another stab this weekend), but using these instructions I was able to install TWRP and flash trebel's android 8.1; less luck with later versions. This has been my daily for a few months now (quarantine means the terrible battery life is less of an issue) and I'm surprised how much I'm enjoying it. I'm hoping a successful root will help me take steps to improve battery life. I saw this question earlier, but wifi hotspot does work, just slow.

This is the first time I've futzed with firmware and I wanted to thank the forum (especially @phhusson, @deadman96385, @snoopy20 and @a.vandelay) for the hard work and great documentation that made this possible for me. I feel so proud every time I boot up--I did this! Sorry this is corny, I'm just new to this and very grateful for the guidance :)
[Android General] ObtuseFox:
I can't get my phone to boot into twrp;

it just enters the stock recovery.

I've tried packing the twrp as described,

using snoopy20's twrp image,

but to no luck :(

what would I be missing?

when I change the system image from stock to other GSI images in the Sugar folder

bootloops occurs, so I guess the flashing is done properly
[Android General] kxkixi:
If you're just trying to get TWRP to work with the stock image, you need to make sure that you boot directly into recovery after the flash is done, otherwise the stock ROM will automatically overwrite the recovery image. Watch towards the end of the flash and hold the power button immediately when it finishes until it says "Entering Recovery". I usually just put the phone in my hand when it reaches around 8 minutes on the flash, and you'll know it's done when the phone vibrates. Once in TWRP, swipe to enable modifications, and it will automatically fix the stock image so that it will not rewrite the recovery image. You may then reboot into system and be able to get back to TWRP again.

Speaking solely from my experience, older GSI's (based on Android 9 and earlier) will have a lot more luck than more recent ones. Android 10 and later has been having issues booting with verity, and any method that I have tried of patching verity out of the boot image has caused sub-second bootloops. Depending on the image that you're using, some odd combination of the disable-dm-verity zip and/or a Magisk-patched boot image made on another device will get it to boot.
[Android General] ObtuseFox:
Oh great! it was just as you've said.

Though I tried to install phh 8.1 GSI but failed, some progress was made :)