-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fl3xbl0w #20
Comments
Without root on the adb you can use adb shell to copy "/dev/block/platform/fe330000.sdhci/by-name/*" to sdcard and then zip and use adb pull to grab it from the sdcard folder which is not protected |
I have a backup of files from a system update that the machine received ( The file list at the time of the update within the
Some info that I got at the time was this:
|
Here are the uploaded files https://archive.org/download/HP-22_T56_EEA, I'll push an update into my website so it gets documented 😄 Also, I wasn't able to dump the files you asked, I got the following output:
|
Thank you SO much! I will keep you posted |
There it is!! Pot of gold, thank you my friend. Now we can easily make any ROM for this board. |
Lovely! I'm glad I could help 😄 keep me updated if you build an image for it! |
Yes I'll have us a working ROM shortly, you will be able to wipe the board clean and start fresh with a rooted 8.1 android OS, I've been very close to having this completed I really really needed that dts file but I had already wiped my board before retrieving it.... |
I apologize there's one more missing item that you should be able to get pretty easy when you have time. From maskrom using rkdeveloptool I need the partition structure so I can merge what I have correctly, I've tried using standard addresses and it's looping back into a loader mode so I'm guessing it's off, here's my output currently using command "rkdeveloptool ppt" % rkdeveloptool ppt An update of those addresses from a functioning board will help rebuild with the modified ROM, also if anyone working on this needs anything I've extracted all the data from the dump you sent over earlier and I'm happy to pass that along to whomever may need it. |
We're actively using the treadmill and I don't have access to the DBG_USB, it may take a bit since I'm on other things as well... ADB is the only thing I have quick access to, already tried a ton of exploits over time with no luck 🤣 I need to replace some capacitors tho, because the speakers started making a crackling noise (and very likely a cap issue), so I can take a chance there! |
Rkdeveloptool ppt gives me an error. |
tds04, YES absolutely! I've been having trouble with the image files from the first dump, the device tree does not seem to be complete and I haven't been able to extract the boot.img other then a hexdump which has been helpful but I had kind of hit a dead end so help would be greatly appreciated. Here's a quick update to where I'm currently at... I have been able to determine that the board kernel is based at least in part on the "rk3399-tve1030g-avb" included with the kernel build readily available, I've been able to use that in conjunction what I can get from the recovered dtb, I have built an android rom based on what I've pieced together but I've ran into a couple issues, I haven't been able to get the screen working yet (this portion of the recovered dtb is incomplete, from what I can get in the hexdump it looks like the board is using an edp bridge but the biggest issue is that my solder work is lousy and I have damaged the defaultt uart/debug port, I'm unable to verify functionality. Ideally if you I can get an image dump would be amazing, I'm not confident enough it what I have to pass that off and potentially damage your hardware. |
What's the error you're getting and which platform are you running rkdevelop? |
If you can get adb via usb try adb shell ls /dev/block/by-name/ see if you can see the partitions, it might be possible to copy those over the sdcard folder and then copy from there over to your local system, I dont think you'll be able to pull it directly from /dev/block/by-name |
I don’t have a Linux computer setup right now so tried with a live version
of kali.
Seems to work and recognizes the tablet in loader and mask room mode
Gives an error of partition not found
I will setup a dedicated box this weekend and try again
Sent from Gmail Mobile
…On Tue, Nov 12, 2024 at 6:26 PM alphab0ing ***@***.***> wrote:
Rkdeveloptool ppt gives me an error. I will try again with different usb
cable or maybe different power adapter.
What's the error you're getting and which platform are you running
rkdevelop?
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVBHUYCC2L64NTCEF2ZJEP32AKTFZAVCNFSM6AAAAABMYVWWEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZSGEYTINBUGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Ok I have had adb working so I will try that as well
Sent from Gmail Mobile
…On Tue, Nov 12, 2024 at 6:31 PM alphab0ing ***@***.***> wrote:
If you can get adb via usb try
adb shell ls /dev/block/by-name/
see if you can see the partitions, it might be possible to copy those over
the sdcard folder and then copy from there over to your local system, I
dont think you'll be able to pull it directly from /dev/block/by-name
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVBHUYAC7RGCXJE6GXGLXWL2AKTV7AVCNFSM6AAAAABMYVWWEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZSGEYTQOJZG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yeah I can make myself available when you get a dedicated setup we can do a live conference, I'm not an expert but I have spent a TON of time on this board, I think ADB will likely be the easiest path forward, if I could somehow get the screen working on mine (via a real dtb or boot.img?) then that would be huge for things on my end, I'll attach a copy of my progress dts/dtb if you guys wanted to have look maybe I'm missing something?? I can't seem to get proper voltage on the USB ports, I'm getting 3.4V which I'm hoping is just a bus configuration and then the screen issue.. |
It looks like @barrenechea has already gone the adb route without very much success, from his earlier post he's been able to identify the direct path for each of the partitions...
Maybe by knowing the exact path it MIGHT let you copy to SDCARD or another directory where you could use adb pull to grab them maybe try something like;
When you run the rkdevtool in windows is it coming as maskrom specifically? Root shouldn't matter when you're in maskrom and give the addresses you recovered in the partition table you shared you should be able to use rkdeveloptool to dump from terminal for example once you're in maskrom;
One thing to note that on these boards there's a button over near the emmc, when holding that button down while resetting the board it WILL get you to MaskROM but I haven't been able to find out anything tells me specifically what that button does I don't really see the purpose of having it along side a recovery button if it serves an identical purpose, I can't be sure it doesn't erase the emmc or something to that effect rather then just force maskrom like a recovery button would. Just something to be aware of... |
tim@tim-HP-EliteBook-840-G1:~$ sudo rkdeveloptool list-partitions LBA start (sectors) LBA end (sectors) Size (bytes) Name00 16384 24575 4194304 uboot_a |
`tim@tim-HP-EliteBook-840-G1:~$ sudo rkdeveloptool -h -h, --help, help print this help text list List the detected devices in rockusb mode this one has more options than the other rkdeveloptool |
Was that the linux tool?? looks a little different then the one I use on my mac, where did the upload go?? I thought I saw it but then I can no longer |
this tool is from ubuntu https://manpages.ubuntu.com/manpages/noble/man1/rkdeveloptool.1.html |
Hope this helps! |
all this was from loader mode, i can switch to maskrom with the command line or the button but all i get are errors
|
@tds04 Thanks for your help this is Fantastic! Also thanks for the tool, that's a new one I haven't seen yet, I'll see what I can get from this image dump. The original dump from @barrenechea included a part_table.bin file that I have not been able to extract any information from so the LBA start/sectors information you provided will be a huge help reconstructing a gpt. @barrenechea , I noticed you had updated the webpage for the project and I thought I could give a little more information that might be helpful to you guys, I updated the image that you had posted of the board itself added the 4-pin uart location and a little more information on the unknown button. Also in my research trying to get as much information as I could to rebuild a device tree I came across the board publicly offered by Vantron that which this board is almost certainly some sort of variant, the information from that board which is publicly available was helpful especially as it relates to the possibility of a Micro SD slot, it seems our board does have the capabilities to add a MicroSD and I'll include the structure for it in the device tree so that anyone wanting to solder one on would have a functioning MicroSD slot, there's also other peripherals on this board that are not being utilized for the purpose of the bowflex specifically the LVDS/LCD and additional backlighting options that could be enabled if someone were to want to use a different screen setup for example. This is awesome I had put this onto the back burner having seemingly hit a dead end and this is a very helpful path forward, thanks guys! |
no it just ends there |
so whats happening is i flash loader.bin and i get that info, |
So after you flash loader, and idb, uboot, what do you get when you reset the board and let it try and go into u boot? It should try and load boot image but it's not there so you'll get an error but you should be able to interrupt the boot (ctrl-c) that will get you to a uboot console from console we can do some debugging and try to figure out where the problem is with the lcd. I'll work on these images, looks like the data is there maybe the sector address is off I'll see if I can extract another way. |
nothing happens on screen, doesn't even reload |
When you're connected after booting the loader you can type rkdeveloptool Rd, that will reset the device, then you can watch your uart |
I tried loading everything again it's weird . Nothing on screen |
New Text Document.txt |
https://drive.google.com/drive/folders/1_ehMxyKZcj89EaGT6mgumpFnKsek09cO |
nanopi4# printenv |
this is from my good board in putty. |
This link is to something else? |
that is a android 10 i found that loads but no screen thought maybe something useful in there |
https://drive.google.com/drive/folders/17gwgJ2vduj8SWKFlqBGzbz5WDJMp179A?usp=drive_link this is everything i got from good board |
I think if you can interrupt the boot process "ctrl-c" and get uboot console on your working board then we can probably donwload the device tree that way without having to extract it. |
=> printenv Environment size: 3128/32764 bytes |
good board |
=> help |
=> showvar |
printenv |
=> printenv Environment size: 3128/32764 bytes |
This might work...
That might give you the device tree to copy/paste |
looks like fdt is 0x08300000 so like this..
|
Can you send me a picture of your good board??? Yours has edp disable which is opposite of dump 1 and your calling for ptn3460 probe which is an edp bridge i'm wondering if the board is the same or very similar? |
That's very odd, one is setup to use mipi dsi and the other edp, completely different... |
I've been trying to get the edp bridge to work, let me try one thats setup like the fdt you just sent me and use mipi_dsi...i'll send over in just a min. |
Here's mipi dsi configuration.. run the boot loader, rkdeveloptool gpt parameter_gpt.txt |
Hey! I created a new Discord server It is pretty barebones, but feel free to join here! https://discord.gg/uX85bh73. Comms should be more fluent over there 😄 |
nothing on uart |
Can you please forward all of the dump files you have from the bowflex Vantron rk3399 board? I've been working on this for several weeks, I've packaged a complete ROM that is 95% functional based on device tree's from other similar devices, I really would love to get my hands on the original u-boot / dtb....Anything you have would be greatly appreciated and I'm happy to share whatever I find of course! Here's the dtb/device tree I've assembled for the board, working uart ports/ USB ports, the display works however the settings aren't entirely correct so I'm getting backlight and lines on the screen, i've identified and confiugured the bluetooth/wifi device and mapped out for adding an sdcard to the board which is pre-built in since Vantron is essentially using their rk3399 board just white labled for
nautical/bowflex.
Vantron-Bowflex_alphab0ing.zip
``
The text was updated successfully, but these errors were encountered: