Palma 2 Released

[Renate]

Originally Posted by InStim

My order arrived today. Syncing books to it now.

Please do me (and yourself) a favor. Copy /system/lib64/libota_jni.so and post it. It's necessary for unpacking future updates for the Palma2.

[InStim]

Originally Posted by Renate

Please do me (and yourself) a favor. Copy /system/lib64/libota_jni.so and post it. It's necessary for unpacking future updates for the Palma2.

Attached

[Renate]

Originally Posted by InStim

Attached

Thank you! It has been added where such things are added.

[Renate]

Can I ask you another favor? Have you used EDL before?
If not, read the instructions on my website.

adb reboot edl

Then install the Windows driver using Zadig as in the insns. Then:

edl.exe /l

Then we can get the HWID and hash and see how to proceed.
After that, just hold the power button for about 10 seconds until it blinks and reboots.

I've not even heard this info for the Palma1.
We know it's the "Bengal" family, but not sure exactly which one.

[InStim]

Originally Posted by Renate

Can I ask you another favor?.

Found EDL 9008, handshaking... version 2.1
HWID: 0013f0e100000000, JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)

[Renate]

Huh. That's a new one. Thanks!
It's a Snapdragon 690 SM_BITRA 0013F0E1
Note that Snap# and codename and HWID still does not tell you what is written on the chip itself. <slaps forehead>

The good news is the d40eee. It's (apparently?) not Secure Boot.

You might try https://github.com/bkerler/Loaders/b...81db_fhprg.bin as Firehose loader.
Do a fresh restart, then (as a sanity test):

edl.exe /lshortername.bin
edl.exe /u /g

If you have 128 GB space somewhere and are the nervous type you can save a full backup that will get you back working no matter how deep a hole you dig (presuming that the Firehose loader works).

[InStim]

Downloaded the loader and renamed to sd765.bin. Did a restart and loaded, but not the right one it seems.

Found EDL 9008, handshaking... version 2.1
HWID: 0013f0e100000000, JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending sd765.bin 0%
Error 0x12, Invalid destination address

[Renate]

Thanks again!

At least we get a clear error.
Try this. It may not work, but we might get rid of the destination error.
https://github.com/bkerler/Loaders/b...ivo_pd2020.bin
If we had a copy of the xbl I could tell you in a minute which Firehose we wanted.

[InStim]

Glad to try things out. I'd be glad to be able to root eventually.

Unfortunately, that didn't work either.

Found EDL 9008, handshaking... version 2.1
HWID: 0013f0e100000000, JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending vivo_pd2020.bin 0%
Error 0x12, Invalid destination address

[Renate]

Hmm, not looking good. I picked the most innocuous one that I could find. The memory map may be something entirely odd. We might have to wait for an update to get that xbl. We still may not have a Firehose loader for this if it's really a new chip.

Here are two very new ones:

https://github.com/bkerler/Loaders/b...f9b1_fhprg.bin

https://github.com/bkerler/Loaders/b...c38e_fhprg.bin

[InStim]

The first one worked.

PS C:\adb> .\edl.exe /lsamsung7f9b1.bin
Found EDL 9008, handshaking... version 2.1
HWID: 0013f0e100000000, JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending samsung7f9b1.bin 100% ok, starting... ok, waiting for Firehose... ok

/u /g output attached in txt file for readability

[Renate]

Originally Posted by InStim

The first one worked.

Nice! You're currently on slot _a.

Could you pull xbl_a so I can check for the best compatibility of the Firehose loader?

edl.exe /u1 /r /pxbl_a xbl.img

Are you interested in a backup? I agree that a raw backup is a huge use of storage. I only run 32 GB and it's over 50% full, so it's not as bad. But don't start until I check the Firehose loader.

[InStim]

I have space on this laptop to make a full backup and local storage to keep it. If you can share those steps too that would be great.

[Renate]

Originally Posted by InStim

I have space on this laptop to make a full backup and local storage to keep it. If you can share those steps too that would be great.

Ok, I looked around and I don't see a better match. That seems to be working just fine.

edl /u0 /r backup0.img
edl /u1 /r backup1.img
edl /u2 /r backup2.img
edl /u3 /r backup3.img
edl /u4 /r backup4.img
edl /u5 /r backup5.img

The sizes of the files will be:

0  123,371,237,376
1        8,368,128
2        8,368,128
3      134,197,248
4    4,294,946,816
5      134,197,248

So that first one will take forever.
I don't know who comes up with these schemes of divvying stuff up.

Also, since you have this raw, you can "cherry pick" a single partition out if you ever need it using dd. There's one for Windows too.

[InStim]

Thanks! All backed up. Being basically a script kiddie, the information is appreciated.