Note Max

[Renate]

Please give me the actual text that the attempt prints out.

I'm not Carnac the Magnificent.

[starkruzr]

Originally Posted by Renate

Please give me the actual text that the attempt prints out.

I'm not Carnac the Magnificent.

PS C:\Users\jtd\Downloads> .\edl /lprog_ufs_firehose_sdm8250_ddr.elf
Found EDL 9008, handshaking... nope, resetting...
Could not write device
PS C:\Users\jtd\Downloads>

so, it can find it, but my loader is clearly wrong. the chip is a Snapdragon 855 which is an SM8150 (in the thread I found this loader he said "this is the right one, some jerk just named it 8250 for some reason.").

[starkruzr]

so, I tried it a few times, and got it to do this:

PS C:\Users\jtd\Downloads> .\edl /lprog_ufs_firehose_sdm8250_ddr.elf
Found EDL 9008, handshaking... version 2.1
HWID: 000a50e100000000, JTAG: 000a50e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending prog_ufs_firehose_sdm8250_ddr.elf 100% ok, starting... ok, waiting for Firehose... no response, poking...
Could not write device

bkerler's edl was, for whatever reason, able to work fine with this. I was able to read the boot partitions, Magisk them, and write them successfully, then reboot. Zadig says the WinUSB driver is installed for the QDLoader device. idk.

[tom.ereader]

Waiting for your tutorial.(ROOT Boox Note Max)
Thank you

[Renate]

Originally Posted by starkruzr

so, I tried it a few times, and got it to do this:

If there is any non-repeatability then the first suspect is USB cables and/or ports. Also, EDL mode must be cleanly restarted after any failure.

In addition, the Python client was probably using https://github.com/bkerler/Loaders/b...4665_fhprg.bin

A filename doesn't tell me anything without a link to the file.

There are many loaders that would probably work. You can use the same one as for the Tab Ultra C. See: https://www.temblast.com/ref/onyxldr.htm

[starkruzr]

the Tab Ultra C doesn't have the same SoC as the Note Max; rather the Pro does. the same loader still works despite the TUC having a different SoC?

[Renate]

Then I have the Tab Ultra C marked where it should be Tab Ultra C Pro.
Would you know what the HWID on the Tab Ultra C is?

[starkruzr]

Originally Posted by Renate

Then I have the Tab Ultra C marked where it should be Tab Ultra C Pro.
Would you know what the HWID on the Tab Ultra C is?

I don't, unless you found it yourself in this thread. https://www.mobileread.com/forums/sh...=355147&page=2

[starkruzr]

p.s. this is the loader I used, in this zip file in the first post, that worked in Python but not via the Windows tool, on the same machine (dual-booted Windows/Linux) https://xdaforums.com/t/help-each-ot...lable.4296269/

[Renate]

Originally Posted by starkruzr

p.s. this is the loader I used, in this zip file in the first post, that worked in Python but not via the Windows tool, on the same machine

If there really is a discrepancy between the two I'd like to get to the bottom of it but there is not enough information here. It's not clear which loader file the two were actually using. [icode]md5sum[/icode] of the files would help. The Python client can under circumstances pick its own loader.

[twowheels]

Originally Posted by starkruzr

well, I have my Note Max.

Where did you order? I called B&H and they said late January, maybe even early February before they’ll be able to ship my preorder. I’m taking it in stride because they have an easier return policy and it lets me watch how the first impressions settle out, though the free case is tempting me to cancel and reorder direct.

[starkruzr]

Originally Posted by Renate

If there really is a discrepancy between the two I'd like to get to the bottom of it but there is not enough information here. It's not clear which loader file the two were actually using. [icode]md5sum[/icode] of the files would help. The Python client can under circumstances pick its own loader.

I did explicitly give it this loader file both with your tool and bkerler's. it sounds like you're saying bkerler's sometimes ignores it?

[starkruzr]

Originally Posted by twowheels

Where did you order? I called B&H and they said late January, maybe even early February before they’ll be able to ship my preorder. I’m taking it in stride because they have an easier return policy and it lets me watch how the first impressions settle out, though the free case is tempting me to cancel and reorder direct.

e-reader.ca. can't recommend them enough, they were fast as hell.

[Bookchin]

Originally Posted by starkruzr

e-reader.ca. can't recommend them enough, they were fast as hell.

What are your impressions of the Note Max so far?

How do you like the text. refresh, features, etc?

With it being so thin, do you find it flimsy or fragile at all?

[starkruzr]

Originally Posted by Bookchin

What are your impressions of the Note Max so far?

How do you like the text. refresh, features, etc?

With it being so thin, do you find it flimsy or fragile at all?

So far I've really enjoyed the image and text quality. There are definitely ghosting bugs that need to be resolved. It is also fast as hell compared to every other Boox device I've used or seen.

It actually feels very sturdy. It's theoretically the same thickness as the 10.3 but I think they've done something to stiffen the frame while not making it very heavy at all.