yashsingh1/xdaforums huggingface dataset:
[Android General] xc-racer99:
Well, I finally decided to upgrade to a Palm phone :) I have en eBay unlocked PVG100. I'm curious to be able to try to bypass some of the bootloader security and be able to run a custom kernel.

Hmm, interesting. By "the reboot reason code also does not trigger the bootloader menu", do you mean that the fastboot special setting (eg from https://github.com/xerootg/android_...epito/drivers/power/reset/msm-poweroff.c#L303) gets ignored or that the register just isn't set and this code block is bypassed in the kernel (and the source isn't released...)? If the latter, we should be able to set it manually with devmem to the physical address.

You mention some test points - I don't suppose any of those are wired to the volume up/down trigger used to enter fastboot?

Do you know if the fastboot code gets loaded to RAM at all/do you think it would be feasible to write a shim that jumps to it from the early stage kernel init?

Although I believe already confirmed, I found the same. Magisk 25.2 did not work, while Magisk 23 did.

It seems strange to me that only the kernel in boot.img would be checked, and not the ramdisk (which we've proven we can modify by using Magisk). However, I guess this is possible. I don't suppose the stock kernel supports kexec?

Is the 0x14 a typo - the aleph security page (https://alephsecurity.com/2018/01/22/qualcomm-edl-2/) says 0x18 is the second offset. Have you tried modifying the existing devinfo? I'd rather not open up my only device and you seem to have mastered the force it into EDL mode :)

Out of curisoity, do you have a UART output from it? You seem to make mention of it. Where would this be?
[Android General] xerootg:
Sorry for not replying sooner. I've not been getting emails for posts which is unfortunate.

PLEASE get us a better kernel... most of our instability is caused by oldness.

Yeah, no good. setting the value does very unpredictable things.

You know, IDK. That's a good idea. I don't have my decompiled stuff handy at the moment, but I don't believe the code for this is very modified.

It should be. I was working on using some xiaomi exploit to figure out how to jump, but I'm low on steam to keep on this project. Please, by all means, have at it. ghidra is a fantastic tool for playing around with the aboot image.

I think it does, but I never got far enough into this.

I've patched the everliving snot out of that partition. It's read... but seems like values there are not being respected.

I dumped the uart via firehorse in EDL. I never determined if the uart is present elsewhere. I might take another pass at this soon, as I have been carrying a fairphone 4 as my daily for the last couple weeks, and while it's great and all, I hate large phones... lol.
[Android General] lmore377:
What's the best way to flash a GSI on this right now? I've tried pretty much everything in this thread and I can get TWRP to boot fine but when I flash boot through sugar I get stuck in a booploop (reboots about 5 seconds after getting past AVB screen) and when I try to flash it through TWRP it gets worse (instant reboot with no delay). Unfortunately pstore is just empty so I can't figure out what's going on

Edit: Not sure what I did but now I'm getting `Load NPRG Error 5002` even with a fresh sugar installation

Edit 2: Rebooted my PC and everything went along fine lol
[Android General] xerootg:
let us know how your stability is!
[Android General] lukars:
Hey xerootg,

first of all thank you so much for sharing your knowledge here 🤍! I have a PVG100E and I flashed CAOS11 on it, I like the ROM but I can't get Bluetooth to work. Its constantly restarting, logcat it tells me the following, and then restarts:

Then when I pm dump com.android.bluetooth I get these suspicious paragraphs (dozens of the same ones):

But when I try to grant this permission:

Also from the dump of com.android.bluetooth:

Doesn't this one literally say the permission is granted?

Maybe this is helpful too:

Edit: if you are not using CAOS11 anymore, what is your current favorite or can you recommend sth?

Thanks again, have a lovely day and biggest respect for still hacking the awesome pepito ;)
[Android General] lukars:
I tried all the previously mentioned ROMs on my PVG100E. On Havoc 3.12, Crdroid and LineageOs 16,17 the Bluetooth connection with another phone worked but was not able to connect to a speaker to play music. On LineageOS 18 the Bluetooth was not even startable, same as CAOS11.

Then I flashed your vendors on my phone, which was a pain because it is some 400mb bigger than my vendors, and I had to change the size of the partition etc. BUT then I was able to connect to my speaker and play music in all the ROMs (incl A11 / LineageOS18), however the Wifi stopped working. So I attempted to frankenstein a vendors.img from yours and mine by using my vendors as a base and adding these files from your vendors:

It did boot, and wifi was working but now the BT didn't work at all even on A10 ROMs. I have never doctored around with vendors, so please excuse my blunt approach here but maybe it is possible to go that route? Since its Friday the 13th I wasn't expecting it to work anyways... :P

Cheers!
[Android General] balthor80:
Hi all !

Is everything write here works also on a PVG100E ?

Thanks
[Android General] PapaBrickolini:
So with Sugar no longer usable, is there anyway to flash firmwares to the PVG100 anymore? I've tried my luck with some other Qualcomm flashing tools but nothing's worked. I have a PVG100 with TWRP still working, but I foolishly managed to wipe its System partition. 🙄 I'd just like to get it back to some GSI build - not picky which, just didn't want to go back to stock firmware. Any help would be appreciated!
[Android General] tgraneberg:
Have you successfully flashed a GSI on the Verizon version pvg100?
[Android General] PapaBrickolini:
I did! I just posted a guide here: https://xdaforums.com/t/release-root-the-palm-phone.4021201/post-89591435

Feel free to reply with suggestions/details for improvements.
[Android General] phigan:
Would you post your TWRP to see if there's a difference?
[Android General] snoopy20:
Will do but I have to wait for androfilehost access, a few hours perhaps.

The difference is it doesn't mount the modem firmware partition as the sdcard, which will be bad news if you accidently wipe it in twrp. I've already compared other areas and they're the same.

BTW I'm using the European firmware that was posted in the other thread. It has some small modem firmware changes which I like to thing enable the missing European bands of the Verizon release.
[Android General] a.vandelay:
Glad it's working! Can you expand on the mounting firmware as sdcard? I'm not really sure what I did to cause that. Thanks!

Ah, I see. Not sure why I did that. Must have put the wrong partition in for external. Thanks
[Android General] phigan:
Did you happen to try a 9.x gsi rom?
[Android General] snoopy20:
I'm still waiting for access so I can upload the modified file, or perhaps a.vandelay can modify his (and take down original since it's risky).

My phone is a daily driver so I can't play around. I'll probably order a second one though now I've got it with clean 8.1. I'll be testing battery life shortly but it's looking promising there, the logcat is a lot less chatty than the stock which hopefully means less wakelocks.

Be good if you can try a 9.x build. There's lineage builds that might work well.
[Android General] snoopy20:
Also tested

GPS

Battery life (tremendous compared to stock roms even when clean - most impressive!)

New TWRP (modem firmware safe)

https://www.androidfilehost.com/?w=files&flid=312806
[Android General] kludgebox:
y'all are incredible... the whole community. I took a leap of faith -- I'm a geek, but have spent very little time on android guts / xda community -- and followed the instructions at the start of this thread, but using the file attached above. I can happily confirm I'm the proud owner of a stock pepito. :victory:

I have a US model, with an AT&T SIM. The Verizon message is (of course) gone. Battery life is anecdotally much better. Everything seems to work... 4G, 3G, phone, wifi, bluetooth, camera, mic... I installed a volume control app since that's not in the pull down menu any more. what else is there ?!?

Two things I can think to mention:

1. I do get a message at boot that says something about the device has been modified, but it continues to boot fine regardless. I assume it has to do with the dm-verity (which I think I did correctly), but haven't dug into it yet.

2. If you run Sugar within Virtualbox, be sure to install the Virtualbox "extension pack" that enables the USB 3.0 hub ... that was the key to getting it to work for me.

THANK YOU!
[Android General] sergio_chichi:
[MENTION=1096286]snoopy20[/MENTION]: How do you handled the instant bootloop after installing the nogapps without su version? I'm at the same point and dont know how solve this problem.
[Android General] snoopy20:
Hi, you can't there's something not right with that image. You have to put the device into edl mode and flash again.

The good news is the gapps version is clean, you can easily disable all the google stuff and there's not that much.

I too discovered the lack of volume slider earlier today, a small price to pay but I'll need an app or mod at some point.

Anyone tried a 9.x variant yet?
[Android General] sergio_chichi:
Thanks for your fast reply. I was able to handle it. I will try some 9.x now.
[Android General] snoopy20:
OK I await in anticipation. There is a v9 lineage one in there which should have things enabled out the box like the audio slider.
[Android General] sergio_chichi:
AOSP 9.0 v123 vanilla is starting. i've not tested anything. no audio slider, three dot button is not working. wlan, bluetooth, camera are ok.
[Android General] tuuure:
How to flash the European modem? :confused: I tried to flash the European firmware, but it brick my phone.
[Android General] al07th:
Hi! can you be more specific? I have 5 days of life with fake GAPPS on a stock 'verizon' firmware without crap, and 2 hours of screen ON.

What are your numbers?

Also not having 'double tap to change volume' and 'physical button' (3 dots) not worth it i think :)
[Android General] snoopy20:
I couldn't get more than a day beforehand with virtually no usage. I'm dropping about 20% now. Take it with a pinch of salt though, we know the Android % is estimated.

---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------

Hmm, well I have a Verizon model and the Euopean one went on no problem. I didn't do anything special.
[Android General] a.vandelay:
Updated the first post. My battery life has been pretty phenomenal compared to stock.
[Android General] snoopy20:
Lineage would be the best if it's possible. Many more nice options out the box. I'm not really wanting to wipe mine, again,...
[Android General] sergio_chichi:
I'm with you. Wiping is annoying after a while. ;) If I have time, I will try some Lineage rom.
[Android General] al07th:
About 20% battery drain per day? That is the same as on the stock 'verizon' rom for me. I'm more interested how many hours can the phone survive with the screen been ON all the time from 100% to zero. Will be waiting for the test results. thx
[Android General] sergio_chichi:
Lineage OS 17.1. seems not running on the Palm. But I'm running "lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img" on one of my Palm now. It is pretty much the same as the AOSP 9.0 v123. But some features are included like soundcontrol on the notification panel. 3 Dot Button is sadly not working out of the box.
[Android General] CaptainElwood:
I followed these steps but get a persistent bootloop after rebooting in TWRP. I tried the "lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img" that [MENTION=10703731]sergio_chichi[/MENTION] suggested but I may have done it wrong. Do I need to start over with sugar or can I now treat this as if it was if it was any other phone with TWRP and flash from there?
[Android General] sergio_chichi:
I flashed Lineage with Sugar and wiped all except System, Data and Internal Storage. After that it took 5 min. for the first boot.

Got the 3 Dot Button working now with Keyboard/Button Mapper.
[Android General] snoopy20:
You have to unplug the USB cable on first boot. No idea why but on mine it bootloops otherwise.

Which lineage did you use Sergio, and which keyboard/button mapper or is that part of lineage?
[Android General] sergio_chichi:
I use lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img from Andy Yan's Source (https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download) and button-mapper-1-46.apk (root needed).

For me I now have everything I want. A nice and clean system, good battery life and every feature I need. Thanks to all the guys who made that possible!
[Android General] CaptainElwood:
Thanks for the link, I accidentally grabbed the LOS 17 version which you had already tested as not working...the LOS 16 version worked great.

Thankfully you can use "adb reboot edl" within TWRP or else I would have had no way to use sugar, I thought I had bricked my device until I tried that after seeing someone mention it in that original Sugar thread.

One thing I was kind of confused with was that I still had quite a few verizon apps and no GAPPS...

Thank you so much to everyone that helped with this!
[Android General] CaptainElwood:
Not sure how I did this but I found out the reason that I still have verizon apps is because TWRP cannot mount the data partition. It wont let me select it so my wipes weren't doing anything. I was able to install GAPPS nano but I still have to manually push everything to TWRP because I cannot access the sd card partition from within TWRP....really strange. Any idea how I could have messed this up? Sorry for the ignorance, I havent done anything like this since my LG G3 days and much has changed.

Edit:

Ignore all that...I'm way outa practice. For whatever reason I had to format data, reboot to recovery, mount data, format data again, then I was able to do the rest of the setup.
[Android General] snoopy20:
I'm also on Lineage 16 now and consider it nigh on perfect. It's the first time I can disable screen/sound wake-up on USB power which is a huge plus for me being a dynamo hub bicycle rider.

Also on the lineage you can add a sound shortcut to the notifications bar at the top so it's easy to get to the sound at any point. Another win is USB tethering is right there in the USB options.

On test today it only dropped 10% over 5hrs on a cycle ride, as good if not better than the 8.1 ASOP. I am _very_ happy!

Regarding having some Verizon, the vendor package isn't touched and gets installed on first boot so there is some minor work to do. I use the European package as my base so it's minimal.

If you mess up as explained you can get into edl mode by using twrp, advanced, terminal and type 'reboot edl'.
[Android General] phigan:
Anyone tried running the original PALM's launcher under Lineage? It has the shortcuts for volume and such..
[Android General] sergio_chichi:
Lineage has also a shortcut for sound in the status bar. So there is no need for the Palm launcher.
[Android General] phigan:
Sure, but it's also nice the way it makes the icons bigger, etc.
[Android General] edg3:
I just want to say a huge thank you to everybody in this thread - especially [MENTION=3099322]a.vandelay[/MENTION] for the instructions on the first page of this thread and to [MENTION=1096286]snoopy20[/MENTION] for his TWRP build.

I am successfully running Android 10 (LineageOS 17.1) on a Verizon PVG100 (purchased from eBay) using the lineage-17.1-20200511-UNOFFICIAL-treble_arm64_avN.img.xz file from sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/.

I want to caveat this by saying I have not tested anything at all (apart from WiFi as that connected during the setup process) so things may not be working as well as on the LineageOS 16.0 that most of you are running, however, I'll test everything in the coming days. I use a Pixel 3 as my daily and this is just a "fun" device purely because of the size/novelty.
[Android General] snoopy20:
I'm on Lineage 16. Good to know v17 is working but I'm sick to death of wiping. I'll probably burn the flash out at this rate. ;)
[Android General] sergio_chichi:
How long did you wait on the first boot? I'm still waiting (15min) but on my Palm Verizon PVG100 (ebay) I'm getting a bootloop.
[Android General] edg3:
Hi [MENTION=10703731]sergio_chichi[/MENTION] - thank you for posting the source links allowing me to try it :)

On the first boot (after formatting data and installing the additional zip) I left it about 15 minutes myself before giving up as it felt like it was taking too long.

So I held down the power button to switch it off, then I held the power button down to get back into recovery/TWRP where I formatted data again (no particular reason; just thought it'd wouldn't do any harm) and then rebooted the system.

This time it took about 5 minutes before getting to the LineageOS setup screen.
[Android General] sergio_chichi:
Ok cool! I will try your way and hope to be able to confirm that Lineage 17.1 is running on my Palm too. :)

Sadly I got no success. :/ Followed the way [MENTION=3422488]edg3[/MENTION] descript but stuck into bootloop.
[Android General] a.vandelay:
Lineage 17.1 working well here :D
[Android General] snoopy20:
Have you unplugged the USB cable on first boot?
[Android General] HepCat86:
hello guys! I can't proceed to TWRP on step 5 and still get into original recovery although I did everything as per instruction with renaming and replacing image and boot files. Any suggestions?
[Android General] sergio_chichi:
try this: start Sugar > upgrade > copy the whole folder of the original (27 files) > close Sugar > replace the copied files as described> restart Sugar > copy the folder with new files back > upgrade
[Android General] HepCat86:
Thanks! Could you also please describe how to push zip in TWRP? Can it work on Windows with adb?
[Android General] sergio_chichi:
check google/bing/yahoo/duckduckgo for "How to install zip in TWRP" and "How to install adb shell on Windows"
[Android General] snoopy20:
You don't need to, TWRP will mount the folder over MTP so drag and drop. Should remove that bit from the instructions.
[Android General] a.vandelay:
I've found that closing Sugar in particular is rather necessary.

I think the language around "pushing" is quite standard, so I'll leave that, but you're right, any method of putting the zip onto the device is obviously fine. Thanks for adding the MTP method!
[Android General] kludgebox:
Lineage 17 leaves only 64MB free on the System partition, so I'm unable to install opengapps, even pico. Just a word of warning to others.

EDIT: it failed the first time I tried, but on another try, I was able to use TWRP -> Wipe -> Advanced -> System -> Resize ... and the System partition grew to 3GB and I was able to install opengapps nano!
[Android General] HepCat86:
Thanks everyone! I've managed to get a clean 8.1. The trick was that you definitely need to close Sugar before Step 4. I tried to not to close Sugar and it somehow managed to copy cached files back onto device.
[Android General] HepCat86:
1) Can't install System Launcher_com.tct.pepitolauncher.apk Is this app missing a certificate in order to be able to install on clean 8.1?

2) Is there a way how to enable face recognition to unlock phone?

3) Can this OS receive any OTA updates? Security update is stuck on June 2019.

---------- Post added at 10:59 AM ---------- Previous post was at 10:23 AM ----------

OK, I got facial recognition working, need to figure out how to make screenshots now.

BTW how is battery on Android 9 and 10 comparing to 8.1?
[Android General] sergio_chichi:
For Screenshot hold the Powerbutton. I'm running Lineage 16.0 and AOSP 9.0 vanilla on two Palms. Seems that ASOP 9.0 has a better battery management (over night usage is better). I have to test a little more in the next days.
[Android General] HepCat86:
Thanks, that's the first thing I've checked with powerbutton, but there is only reboot and power off.

---------- Post added at 12:47 PM ---------- Previous post was at 12:29 PM ----------

BTW Now when I got a custom ROM with TWRP does it mean I can flash any other ROM via TWRP or do I need to proceed through Sugar all the time?
[Android General] snoopy20:
The Palm doesn't have a fastboot partition so we're limited to edl which requires a flashing program (sugar). We're at the mercy of their password protected login.
[Android General] HepCat86:
hi! How did you manage to mount data in TWRP in order to install gapps? I cannot mount it as it shows 0 MB
[Android General] Swimming33:
Yeah... I personally cannot get this working for my life. With Sugar, i can reflash the stock rom onto my Verizon Palm Palm, no problems. But if i attempt to use one of the custom roms (i've tried 8.1, 9, and 10, none seem to work), and the device goes into a boot loop. Anyone have any suggestions?
[Android General] sergio_chichi:
Wipe > Format Data

After that you should have ~20GB Internal Data for gapps.
[Android General] HepCat86:
Thanks! All is working very smooth on Lineage 17.1, I don't know about the battery yet, but in terms of apps and interface it is a lot better than AOSP 8.1 v32.

---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------

Did you close and reopen Sugar after renaming for Upgrade? Did you do Step 5 with wiping data and installing Universal DM-Verity?
[Android General] Swimming33:
I think so, this is what I'm doing:

Step 1: open Sugar and download/install the stock rom

Step 2: copy device folder from sugar install directory and put it into another section of my computer, then close Sugar

Step 3: replace the Recovery Image in the device folder (the one that starts with R) with the twrp img, renamed to match it. Replace the largest file in the device folder with the lineage os IMG, renamed to match it

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

Step 5: boot into twrp, hit format data, type in yes. Then transfer over the DM-verity zip to the device and install it via twrp

Step 6: this is where I'd figure everything works, but it doesn't. The device stays in it's bootloop, with the only thing I'm able to do is to go back into twrp (or do the whole EDM thing again)

---------- Post added at 09:30 AM ---------- Previous post was at 09:25 AM ----------

Wait... I think i wasn't using the dm-verity thing somehow, but some other thing I'd accidently downloaded instead. Oh man that's embarrassing. I assume that when i try it again *with the right thing*, it'll all work :P
[Android General] HepCat86:
Your procedure is correct so definitely might be the case with the dm-verity otherwise it will not get out of bootloop.
[Android General] edg3:
Having originally got LineageOS 17.1 running/working ok, I decided to start again so I can install GApps and am now struggling.

With no GApps, If I go:

Flash the modified recovery/system in Sugar

Unplug device as it finishes

Get into a bootloop (which is to be expected) so hold down power to turn it off

Hold power for 3 cycles to enter recovery (now TWRP)

Format data

Flash the Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip file

Reboot

Then I get LineageOS booting up great and can go through the setup process etc.

However, if I try to add in GApps (LineageOS says do it immediately after installing otherwise expect crashes) by flashing it directly before Step 6 above then LineageOS fails to boot, it just goes into a bootloop that no amount of wiping/flashing the Dm-Verity zip seems to solve, so I have to start again with Sugar. I also tried doing it after Step 6 to no avail.

For anyone that managed to get GApps with LineageOS, how did you do it?

And a separate question... what's the best way to add Magisk into this? Should I be flashing a modified boot partition, or can I add Magisk "afterwards'?