Database Info

recovery mode not working

Ok, so I was trying to reflash the modified rc30 update to start from scratch because when trying to do the auto rotate browser tweak I kept getting the not enough space message. I rebooted into recovery mode thinking all I had to do was run the update and it didn't do it. I thought maybe I needed to reflash the modified recovery image so I did that, but now when I reboot into recovery mode I get the G1 logo and then a blank screen. I tried pushing home+back to restart and get nothing. So I used adb to push the recovery image on the device and I get "no space left on device" Tried doing a factory reset and it hangs up on a blank screen there too. can I just wipe the data partition to fix it then reflash the recovery image to the device? The phone works fine, I just can't do anything with recovery. Can someone help me out here in getting back recovery mode? Thanks

When you tried to push the recovery image, did you do so to the sdcard?
I am referencing these pages:
http://android-dls.com/wiki/index.php?title=Keeping_Root
http://code.google.com/android/reference/adb.html

Just remount /system as rw and adb push the recovery.img directly in. Also, if you have the engineering bootloader installed, you could try using fastboot to reflash the recovery partition from the bootloader.

doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?

jdwme said:
doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?
Click to expand...
Click to collapse
If you're on RC30 v1.2 put the recovery.img in /data not /system

so then my it should look like this?
mount -o remount,rw /dev/block/mtdblock3 /data
cd /data
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img

jdwme said:
so then my it should look like this?
mount -o remount,rw /dev/block/mtdblock3 /data
cd /data
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img
Click to expand...
Click to collapse
mtd3 is system. mtd5 is userdata. Don't execute that first step! userdata partition is rw anyway. Just start with step 2.

ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data

jdwme said:
ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data
Click to expand...
Click to collapse
Not sure. What do you get if you type mount with no args in the terminal emu?

nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?

jdwme said:
nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?
Click to expand...
Click to collapse
Really? What it should do is return a list of mounted devices, like so (this is a Mod RC30 v1.2 device):
Code:
# mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/loop0 on /system/modules type cramfs (ro)
/dev/block/loop1 on /system/xbin type cramfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8)
Stock bootloader can't be used to flash images to the mtd partitions.

ok i misunderstood, i did type just mount now and it shows what you posted. could i have two modified recovery images on there and it cant pick one so thats causing the problem?

Did you change directory to /data? If you can't get it to work from the terminal, as long as you have the recovery.img in /data, just power the G1 off completely and power it back on. It automatically writes the recovery partition every time you cold boot.
Btw make sure that in the mount report the following two lines read exactly as such:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)

yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.

jdwme said:
yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.
Click to expand...
Click to collapse
On your cold reboots were you seeing the flashing screen (arrow onto chip) before booting into Android?

nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode

jdwme said:
nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode
Click to expand...
Click to collapse
Are you sure you have the recovery.img in the /data directory? Strange. Maybe someone else has some ideas about whats going on here?

So I decided to show all my partitions listed on the system using cat
/proc/partitions and this is what I got. Does this look normal? Not sure
what it looks like on anyone else device
major minor #blocks name
7 0 2248 loop0
7 1 3176 loop1
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 69120 mtdblock3
31 4 69120 mtdblock4
31 5 76544 mtdblock5
179 0 7977472 mmcblk0
179 1 7973376 mmcblk0p1
I pushed it to the data directory before, followed the instruction thread, but using oi file manager recovery.omg shows in system, nothing shows in data

so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader

jdwme said:
so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader
Click to expand...
Click to collapse
Give me an IM if you want. I may be able to help fix your recovery mode. (debugging things like that is such a pain on a forum. real-time is much easier)

/efs not mounted - need help from Linux experts and others rooted i580x users!!!

After a sleepy ODIN flash, using SPICA ops with G3 firmware => STUPID??? NO, not done yet , next ODIN flash segment, accidentally stick clear phone EFS via Debug options (DOUBLE CRAZY!!!) NOW i lost the precious IMEI and /efs partitions corrupted as well.
i've got the fixed nv_data.bin and both stl4.img and bml4.img from [email protected] (attached). Thanks for his kindness and supportive to the community!
But even with those i still can't fix the issue!!!! /efs did not mounted via mount command...
as in a GOOD G3, mount command result will be as below:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/stl6 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
[B]/dev/block/stl4 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0[/B]
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0702,dmask=0602,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
in my case the bold line just missing... so this is must be the problem.
I tried to do the same as SPICA's method as below:
Code:
$su
#dd if=/sdcard/bml4.img of=/dev/block/bml4
#reboot
It's OK then but...
Code:
$su
#dd if=/sdcard/stl4.img of=/dev/block/stl4
/dev/block/stl4: cannot open for write: Invalid agrument
With this error my /efs cannot be mount... and still missing from the mount command. I'm just a linux noob so pls help me out. How can i restore the stl4 partition properly???
My girlfriend now really mad at me due to she don't have her beloved phone this christmas already. OMG!!!!!
and to all rooted i580x user Pls kindly help compare your "good" /efs folder... maybe mine missing something???? due to one time Erase Phone EFS using Odin Debug Options.
Mine /efs now as below:
Code:
/efs/nv_data.bin
/efs/imei/.nvmac.info
/efs/.files/.dm33 (empty folder)
/efs/.files/.dx1 (empty folder)
/efs/.files/.mp301 (empty folder)
And if you can do adb shell, it'll be very kind of you by sharing your good backup stl4 and bml4 - for research purpose (those partitions did not content any of yours personal data - so PLS HELP!!!). Pls do the backup partions as below and share your img here if possible.
Code:
$su
#cat /dev/block/stl4 > /sdcard/efs_dev-block-stl4.img
#cat /dev/block/bml4 > /sdcard/efs_dev-block-bml4.img
TIA and Best Regards
P/S: when do the ls /dev/block/stl* the stl4 is there but cannot restore using the backup img. it's weird...
Code:
#ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
same for bml4...

I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.

Szaby59 said:
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Click to expand...
Click to collapse
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.

kenblat said:
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
Click to expand...
Click to collapse
fixed ur phone yet? noob idea: can u try flashing but this time with the right ops?

were you able solve the problem? I am facing exactly same problem.

[SOLVED] [Q] cant get dexter's native ext2/3 support working

Trying to get Dexter's native ext2 support working.
I pulled my SD card (8gb) and using GParted within Ubuntu, deleted my FAT32 partition, created 1st partition FAT32 ~7gb, 2nd partition ext2 (1gb), 3rd partition SWAP (64mb)
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Under memory/sd card sotrage, phone is reading ~6.9GB as expected of the FAT32 partition.
Am I missing a step? Nothing ever gets moved from the phone to the card's ext2 partition.

ext2,3 problem on dexters rom
Sorry first post noob, hopefully im doing this right
I used mini tool partition wizard... i tried ext2 then ext3, made them logical and primary, with the swap partition. (do we need that swap ..i haven't tried it without it).
And the entire memory card wouldn't be recognised/mount at all when turning on the phone. I had to remove the partitions to be able to use the memory card in the normal manner.
is there another step? i was hoping all i had to do was make the partition and it would be done.
help!

did u guys set the ext partition to active?

I did not mark any partition active (none of the many guides on the net say anything about setting partition flags). My layout (per parted) looks like this:
Code:
Number Start End Size Type File system Flags
1 1049kB 6818MB 6817MB primary fat32
2 6818MB 7892MB 1074MB primary ext2
3 7892MB 7959MB 67.1MB primary linux-swap
Which matches every screenshot I have seen of parted/Gparted in any formatting guide.
I did find one that had fat32 marked as lba, but that makes no difference.

R-D said:
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Click to expand...
Click to collapse
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.

I realised what i did wrong ..I tried to make the ext2 partition after I 'installed/flashed' dexters rom ...this messed everything up for me.
So I re-did the entire process but made my ext2 partition first. Now its allgood
Don't know if that helps
Sent from my XT720 using XDA App

kousik said:
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
Click to expand...
Click to collapse
Here's the default mount output:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
tmpfs /skttmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock7 /system/lw yaffs2 ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
When I try and mount it manually, which device name is preferred? I found the partitions (1 = fat32, 2 = ext2, 3 = swap) as these names:
/dev/block/vold/179:1
/dev/block/mmcblk0p1
/dev/block/vold/179:2
/dev/block/mmcblk0p2
/dev/block/vold/179:3
/dev/block/mmcblk0p3
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Thanks for your help.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?

R-D said:
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
Click to expand...
Click to collapse
"No such device" is indication that the kernel module is not loaded properly.
You may have to insmod ext2.ko yourself to get it to work. If you do not have the .ko files, you can download from http://dateno1.egloos.com/27191 yourself and copy to /system/lib/modules. Also you can see this thread http://forum.xda-developers.com/showthread.php?t=929871 for reference.

Okay, mystery solved!
I am missing these modules as I grabbed the "original" 1.1b update (1.1a-update.zip). This original file was missing these modules and had an incorrect overclock module.
I just re-downloaded 1.1b again, and found that if I look in the ZIP file, it has the missing modules I didnt initially get.
In speaking with Dexter, it seems that he updated the 1.1b (1.1a-update.zip) file twice, but kept the same file and version name. So the 1.1b everyone else is using, is newer than the 1.1b I downloaded, as I downloaded it right after it was first posted and missed the next update as it had the same filename.
Essentially, what amounted to 1.1c was also released as 1.1b ...
So lesson is, either redownload and apply the 1.1b update, or update to 1.2 (or newer as they come).
Thanks for your help.

Oh ! Confusing this 1.1a/b/c !

is it nid to do it manually? 1.1b did detect my ext2.. but in 1.2 did not detect.. i try put ext2 and ext4 ald..

Rooting the LG Optimus 2x (P999) Wind Mobile

kk i am very desperate for help
i have been seeking help regarding rooting my optimus 2x for 2 months
heres the story:
i rooted my phone using superoneclick and everything worked out fine
then i flashed MIUI on my phone and it worked fine except the GPS was very slow
then i had flashed a recovery rom to go back to the stock Froyo
then i flashed Cyanogenmod 7.1 and it worked fine
i saw that MIUI had some new updates and that it was much better than Cyanogenmod in my opinion
So i went to ROM Manager and tried to reboot my phone into recovery but nothing happened at all
I've tried every way to boot into recovery but it goes to the stock recovery
I downloaded a root checker and it tells me my device is not rooted
now when i try to use superoneclick i get stuck
can any1 please help me
i've been posting in the superoneclick forum and no1 has been able to help me for 2 months

lol, use NVflash one click and flash CWM, you dont even need root, flash it then flash another rom.
if that doesnt work: factory reset, unroot, then re-root

Help me too!
I know this is going to sound incredibly dumb (and thats because i barley know anything about all of this stuff)
I've been trying to root my LG G2x for a couple days now, but it just wont work.
Ive followed all the steps to use superoneclick to root my device and the program works as far as i can tell. It finishes step 7 and gives me this message: "Killing ADB and restarting as root... enjoy!"
Unfortunately before i can even use my phone more messages start flowing out. I have absolutely no idea what any of it means, but the program and my phone both crash until i hard boot both so i would really appreciate any help!
This is the message i get: "$
$ export TEMPRANDOM=29169;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount -o rw,remount /system
mount: permission denied (are you root?)
END:29169export PS1=""
export TEMPRANDOM=92557;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /system type ext3 (ro,noatime,data=ordered)
/dev/block/mmcblk0p7 on /data type ext3 (rw,relatime,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,nosuid,nodev,noatime,data=ordered)
tmpfs on /mnt/extasec type tmpfs (rw,noatime,mode=755,gid=1000)
/dev/block/mmcblk0p6 on /nvdb type ext3 (rw,nosuid,nodev,relatime,data=ordered)
/dev/block/vold/179:8 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:8 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/sdcard/_ExternalSD type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:17 on /mnt/extsecure/extasec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/_ExternalSD/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
END:92557export PS1=""
"

Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
Sent from my LG-P999 using XDA Premium App

chipis said:
Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
can u tell me exactly what u did? like step by step?

nydmt said:
can u tell me exactly what u did? like step by step?
Click to expand...
Click to collapse
Go to the root thread in my signature and then in that thread there is a link to the One Click Recovery Flasher using NVFlash. That thread is detailed, step by step and even has a link to a video. Not to be a smartass, but if you cannot follow that thread to install recovery on the phone then you should not be flashing roms on your phone. This is basic stuff you need to know and understand first or you are going to royally screw up your phone.

Guide to Treble/GSI on the Palm Phone

From this thread: https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559, the TrebleCheck app indicates we need an arm64 "a-only" ROM. The Palm Phone is running vendor version 8.1.
Step 1: Download Sugar. This thread: https://forum.xda-developers.com/android/general/release-root-palm-phone-t4021201, has everything you need to know about Sugar. I ran the upgrade once to download the full stock ROM (make a backup as described). Warning, this erases all of your data.
Step 2: Follow this guide: https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473, to build a TWRP for the Palm Phone without source. I used the latest TWRP for the Asus Nexus 7 2013 LTE as my base. From your Palm upgrade backup, the recovery image is the one that starts with 'R', about 36MB. Rename your new TWRP image to match the stock recovery and replace it similar to the rooting guide for replacing the boot image.
Update: snoopy20 has shared his TWRP image here: https://forum.xda-developers.com/showpost.php?p=82654073&postcount=26
Step 3: Extract the system image you downloaded and rename and replace the stock system image. It's the largest file in your Sugar device folder.
Step 4: Re-run the upgrade in Sugar with your replaced images in place.
Step 5: You're probably stuck in a boot loop. Press and hold the power button until you get into recovery, which is now TWRP. First, I formatted data. Then push or otherwise copy this zip to the device: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and install it from TWRP. The stock configuration should be fine, i.e. don't worry about re-naming the zip. Note, do NOT use adb sideload, since that seems to wreck the zip installer's ability to use its own file name to configure itself.
Update: The Universal dm-verity zip may not always work, in particular on AOSP Android 10 images. In this case, you can use another Android device and Magisk Manager to patch the Palm boot image. Push the boot image from your Palm backup (described in Step 1) to the other Android device. It's the mbn file that starts with 'B'. I chose to rename it to boot.img for easier use. Than use Magisk Manager to patch it. Push the modified boot image back to the Palm (in TWRP) and use TWRP to Install->Image it.
Step 6: Reboot! Wipe data and cache for good measure, and you should be set!
All credit goes to the folks from the links above for creating the Treble system image, TWRP guide, and dm-verity script. Thanks to snoopy20 for his TWRP image.
Things that work so far:
* Almost everything
Doesn't work
* Soft key requires an app, such as Key Mapper, to use
* Screen auto brightness is missing

Can you post the TWRP you created?

snoopy20 said:
Can you post the TWRP you created?
Click to expand...
Click to collapse
Is it kosher to publicly post a TWRP created like this (i.e. not from source)?
Additionally, I'm not entirely confident I didn't screw something up, so I'm a little wary to risk everyone's device. Specifically, I do not know what would happen if you get caught in a boot loop and don't have a functioning recovery to boot into in order to restore...

Yeah you just write "Unofficial" or something in the title. Right now I'm happy to brick the Palm, I'm 99% of the way to dropping it but it would be fantastic if I can get a stock Android on it.
By the way do the restrictions, i.e wifi tethering, get applied by the Vendor package?

snoopy20 said:
Yeah you just write "Unofficial" or something in the title. Right now I'm happy to brick the Palm, I'm 99% of the way to dropping it but it would be fantastic if I can get a stock Android on it.
By the way do the restrictions, i.e wifi tethering, get applied by the Vendor package?
Click to expand...
Click to collapse
Hard for me to test since I don't have a supported SIM, but the tethering menu is available in Settings. You'll have to try it and let us know.

If you post the TWRP I'll do so. My biggest concern is if I **** up building it. I sent you a PM.

snoopy20 said:
If you post the TWRP I'll do so. My biggest concern is if I **** up building it. I sent you a PM.
Click to expand...
Click to collapse
Just waiting for android file host to approve

I've attempted to repack but found:
1. Two fstab files are fstab.qcom and fstab.grouper, don't know if I should delete them but instructions seem to indicate I should.
2. Stock ramdisk folder doesn't have a fstab.* file to copy over.
I ended up with this twrp.fstab. Note the encryption part from /data is gone? Unsure if this is ok.
# mount point fstype device
#twrp.fstab
/system ext4 /dev/block/bootdevice/by-name/system
/cache ext4 /dev/block/bootdevice/by-name/cache
/data ext4 /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"
/usb-otg auto /dev/block/sda1 flags=removable;storage;display="USB-OTG"

Just a big heads up, when trying to connect to the network today (Visible) I noticed that my IMEI was 0000.... I have never successfully connected the Palm phone and while the behavior now is consistent with my issues before, I can't say whether or not flashing the GSI as outlined here erased my IMEI.
Proceed with caution.

I'm not proceeding at all unless you post your twrp or verify the issues I've had creating it.
I read the IMEI is held on another partition, type 'efs'. I can't see Sugar killing it. More likely your fstab options aren't mounting it.
---------- Post added at 06:57 PM ---------- Previous post was at 06:33 PM ----------
Here is a list of all the mountpoints on a working phone. At a guess the IMEI is held in /firmware. Do you have this mounted?
rootfs on / type rootfs (ro,seclabel,size=1358776k,nr_inodes=339694)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1439668k,nr_inodes=359917,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p27 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/mmcblk0p28 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
none on /acct type cgroup (rw,relatime,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1439668k,nr_inodes=359917,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/mmcblk0p52 on /fotadata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p29 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/mmcblk0p12 on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/mmcblk0p1 on /firmware type vfat (ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p30 on /persist type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1439668k,nr_inodes=359917,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
tmpfs on /sbin type tmpfs (rw,seclabel,relatime,size=1439668k,nr_inodes=359917,mode=755)
/sbin/.magisk/block/persist on /sbin/.magisk/mirror/persist type ext4 (rw,seclabel,relatime,data=ordered)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered)
/sbin/.magisk/block/system on /sbin/.magisk/mirror/system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/sbin/.magisk/block/vendor on /sbin/.magisk/mirror/vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/sbin/.magisk/block/data on /sbin/.magisk/mirror/data type ext4 (rw,seclabel,relatime,discard,noauto_da_alloc,resuid=10010,data=ordered)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid)
The original firmware recovery has the /firmware mounted as the sdcard so depending on how you mounted for twrp could you have wiped it?
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,verify
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/fotadata /fotadata ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait,verify
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check
/dev/block/mmcblk0p1 /sdcard vfat nosuid,nodev wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/fsg /fsg emmc defaults defaults

Added my TWRP to the OP

OK I've compared and I can't see anything major. The only thing you do have is a few more mount points which I've not had in mine (listed). Where are they from? I think mounting the sdcard (modem firmware) is a bad idea so I'm going to skip that.
/sbl1 emmc /dev/block/bootdevice/by-name/sbl1
#/sbl2 emmc /dev/block/bootdevice/by-name/sbl2
#/sbl3 emmc /dev/block/bootdevice/by-name/sbl3
/tz emmc /dev/block/bootdevice/by-name/tz
/rpm emmc /dev/block/bootdevice/by-name/rpm
/aboot emmc /dev/block/bootdevice/by-name/aboot
#/sbl2b emmc /dev/block/bootdevice/by-name/sbl2b
#/sbl3b emmc /dev/block/bootdevice/by-name/sbl3b
#/tzb emmc /dev/block/bootdevice/by-name/tzb
#/rpmb emmc /dev/block/bootdevice/by-name/rpmb
#/abootb emmc /dev/block/bootdevice/by-name/abootb
#/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
/external_sd vfat /dev/block/mmcblk0p1
/usb-otg auto /dev/block/sda1

So, I have twrp installed, and a fast bootloop almost instantly on start. I haven't been able to solve it thus far. I can get into twrp which is something though.

snoopy20 said:
OK I've compared and I can't see anything major. The only thing you do have is a few more mount points which I've not had in mine (listed). Where are they from? I think mounting the sdcard (modem firmware) is a bad idea so I'm going to skip that.
/sbl1 emmc /dev/block/bootdevice/by-name/sbl1
#/sbl2 emmc /dev/block/bootdevice/by-name/sbl2
#/sbl3 emmc /dev/block/bootdevice/by-name/sbl3
/tz emmc /dev/block/bootdevice/by-name/tz
/rpm emmc /dev/block/bootdevice/by-name/rpm
/aboot emmc /dev/block/bootdevice/by-name/aboot
#/sbl2b emmc /dev/block/bootdevice/by-name/sbl2b
#/sbl3b emmc /dev/block/bootdevice/by-name/sbl3b
#/tzb emmc /dev/block/bootdevice/by-name/tzb
#/rpmb emmc /dev/block/bootdevice/by-name/rpmb
#/abootb emmc /dev/block/bootdevice/by-name/abootb
#/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
/external_sd vfat /dev/block/mmcblk0p1
/usb-otg auto /dev/block/sda1
Click to expand...
Click to collapse
I think the guide for porting TWRP mentioned to add it, so I did.

snoopy20 said:
So, I have twrp installed, and a fast bootloop almost instantly on start. I haven't been able to solve it thus far. I can get into twrp which is something though.
Click to expand...
Click to collapse
Sounds similar to me. Did you flash the new system as well? If so, this is when you use TWRP to flash the zip to disable dm-verity.

I did, then the dm-verity but with no success. Assuming /system was corrupt or wrong I've deleted it. I'm now trying to work out how to flash the system.img without fastboot (which I don't have).
So far dd is ending up with a corrupt partition and twrp insists on a zip for system flash. Trying to figure out how to convert it.
---------- Post added at 09:44 PM ---------- Previous post was at 09:26 PM ----------
I did, then the dm-verity but with no success. Assuming /system was corrupt or wrong I've deleted it. I'm now trying to work out how to flash the system.img without fastboot (which I don't have).
So far dd is ending up with a corrupt partition and twrp insists on a zip for system flash. Trying to figure out how to convert it.
Actually you said you tried 10 unsuccessfully, so how did you then flash the v8 image?

snoopy20 said:
So far dd is ending up with a corrupt partition and twrp insists on a zip for system flash. Trying to figure out how to convert it.
Click to expand...
Click to collapse
TWRP doesn't say "Install Image" at the bottom when you go to Install?
Actually you said you tried 10 unsuccessfully, so how did you then flash the v8 image?
Click to expand...
Click to collapse
I'm assuming the 2nd link down in OP (github).
This is exciting!

Anytime I got stuck, from TWRP I used
Code:
adb reboot edl
then I used Sugar to reflash everything all over again.

Phew, I didn't know about that one. I'll try again.
You can't flash an img from TWRP, there's no boot partition to enter fastboot mode.

I'd originally downloaded the nogapps without su and added Magisk.zip after, this caused an instant bootloop. The one with build in gapps+su works. It's possible to disable all gapps and related services except GoogleOne (I installed OpenLauncher into /system/app then removed GoogleOne by force). After this "Google" can be removed and all notifications about Google Services end.
I recommend you take down the twrp and remove the line which mounts the firmware partition as sdcard in case this is what wiped your IMEI. I build my own without this line and IMEI survived.
Tested
Wifi hotspot is working!
Bluetooth, camera, all USB,
Stability
Not working
Thee dots button (don't think it's a big deal as you get the three icons for back etc by default).
Auto screen brightness