Database Info

[TOOL]QtADB (AndroidManager for Linux, Windows and MacOS)

hello,
QtADB is window app based on adb.it lets you to copy,remove etc your files and apps from PC and Android Phone
This app is under developing so be tolerant for any bug...
visit QtADB website: http://qtadb.wordpress.com/
Features:
1. File manager
-copying files and dirs between phone and computer
-removing files and dirs
-creating new dir
-and other
2. App manager
-installing apps
-removing apps
-creating backup of apps with data
-restoring backups of apps with data
3. Shell
-opens android shell
4. Screenshot
-take screenshot of your device
-save screenshot to png file
5. Fastboot
-flash bootloader, radio and recovery
-boot recovery
6. Recovery
-nandroid backup/restore
-wipe data
-flash rom
-wipe battery stats
-fix uid mismatches
7. Reboot
-to bootloader
-to recovery
-normal reboot
8. Settings
-set font used by app
-set starting paths (or remember paths on exit)
-and other
9. Automatically detects phone (device, fastboot and recovery mode)
it requires installed AndroidSDK and busybox on phone (so and root)
linux and macOS version reguires installed Qt libraries(libqtgui4, libqt4-declarative and libqt4-network 4.7 version)(install it from synaptic or some similar app)
if you have connected phone but the file list is empty run with root permisions:
1)adb kill-server
2)adb start-server
or:
create file:
gksudo gedit /etc/udev/rules.d/51-android.rules
and insert this line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Ive got HTC Magic with Cyan6 and im testing everything on this. QtADB should work with every phone with busybox
if you have any suggestions/questions or you found any bug please let me know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
More screenshots on official site
I am not responsible for damage done to your phone while using QtADB.
DOWNLOAD FROM OFFICIAL SITE
Do You miss fome feature that QtADB doesn't have? please post Your idea here: http://qtadb.uservoice.com/forums/87039-general
[size=+2]DO YOU HAVE SOME PROBLEMS WITH QTADB? PLEASE READ FAQ FIRST[/size]
If You like QtADB please consider donation:

What language is the windows version written in? Are the libraries able to be referenced from VS?

both versions are in c++ and this is the one source code compiled under windows and linux. it requires Qt libraries for VS
ps.i would like to add some screenshots but i have no permissions:/

where do i put the librays stuff?? im confused.... nvm i think i got it...
ok it says my phones connected for like 5seconds.. then it tells me to connect my phone.??

Nice app thanks!

wow this is AWESOME! thank you!

Looking good! Android management apps are really coming out of the woodwork now
I've attached a screenshot of my own Android manager 'Spot'

Crashes when i try to access a directory on the phone. Win 7 x64 and HTC Desire.

At the beginning, it looks great to use, but then I tried to open any directory, it crashed and forced close

it crashes after 2 - 3 seconds after opening
Windows 7 Pro - HTC Magic 1.5 with Sens UI - official

Acidmax: i dont know why you are having this issues.maybe its because you are using 64bit system...(i will support 64bit when app will be done)
cryshop: what phone?what OS?is phone rooted?which dir are you trying to open (on sdcard/in system).give me something information
crysu_x: "it crashes" has many meanings...what do you see?what error is appearing?what busybox do you have?you have to be more specific
the new version with new upgrades and fixes is almost ready so be patient

Works great for what i've used it for so far. Thank you sir.

@7ymekk : I'm using Windows 7 32bit and rooted HTC Legend.
I tried to open /system folder on the phone.

you know what??if you want to use my app please wait couple of days...i will end my new version and if you'll have the same issue i'll investigate it

how do you install it with ubuntu?

download first attach from first post and install libqtgui4 from synaptic

Hi, this is giving me segfault. I have installed both Sdk and libqtgui4. when i run "adb devices" i can see my tattoo attached.
I run the app, it asks me for the sdk path , then i point it to the "tools" subfolder under the sdk folder and then it segfaults.
This occurs even if i run it with root privileges.
Am i doing anything wrong?
Thanks in advance

if you are expecting some help you have to be more specific! what distro, what phone...the more informations-the better

7ymekk said:
if you are expecting some help you have to be more specific! what distro, what phone...the more informations-the better
Click to expand...
Click to collapse
Oops,
I'm working under Ubuntu 10.04 with a htc tattoo phone.

maybe this evening i will upload new version with screenshots and a lot improvements so i recommend to wait a little if you still will have those problems i will look into this

Crosscompiling glibc for the Note 2, native GNU tools on the phone, runnig problem?

I've followed the steps from http://forum.xda-developers.com/showthread.php?t=1299962 basically, and crosscompiled glibc and some basic GNU tools, to run natively on the Note 2.
Now, I'm running into some problems, which I need help with from crosscompiling gurus...
Basically, what I did:
- Setup crosstool-ng on the PC.
- Downloaded the Note 2 source from Samsung.
- Got include/drm/exynos_drm.h elsewhere on the web, as it was bombing without it, and for some reason, it's not in Samsung sources.
- Built a crosscompiling toolchain. I set:
target architecture - arm
endianness - little
fpu - neon
instruction set mode - arm
eabi - enabled
vendor string - exynos
alias - arm-linux
os - linux
c library - glibc
threading - nptl
- With it, built glibc for the Note, built no prob. Built also GNU tar to start experimenting.
Now, I transfered glibc and the tar dirs to the Note.
As the author says at http://forum.xda-developers.com/showthread.php?t=1299962:
What I've found so far, the cross compiled executable (like simple Hello world), when dynamically linked, gives "no such file or directory" error when tried to be run at the device (WTF, right ). However, when when I do run it with the cross-compiled ld-linux.so (the linker of C library) it runs perfectly...
EUREKA! Found the solution! It's as simple as symbolically linking the library folder of your GlibC as /lib to root file system. You can edit ramdisk accordingly to do this process automatically.
Click to expand...
Click to collapse
Anyhow for me now, when I try to run the tar executable, I get:
Code:
No such file or directory
This even with the glibc lib dir symlinked to /lib, and/or setting LD_LIBRARY_PATH to the glibc lib dir.
file tar gives me:
ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.31, stripped
Click to expand...
Click to collapse
so all's looking right.
Why can't I get it to run?

This is proving to be a somewhat great course on crosscompiling for me.
So, messing with it, and making advances - was able to get the compiled executables to run after bindmounting arm-exynos-linux-gnueabi/sysroot/lib dir, which was built by the toolchain to the phone's /lib directory.
Now getting mixed errors and failures caused by ld etc when running GNU tools built against androids libc, so need to mess with terminal on the phone to get just the glibc to loaded on running, but it's progressing...
It seems I'll be able to do this.

Looking forward to that. Highly interested in php lighttpd mc busybox dropbear that kinda ****.
--
Sent from my N7100 with Perseus 25.4 Omega 5.0 and some stuff of Raubkatze

I'm almost there, I just need to crosscompile gcc and then I can build the necessary GNU tools natively.
I'm just figuring out how to crosscompile gcc, as it depends on mpc, gmp, and mpfr, and having no experience with crosstompiling I'm figuring out how to compile depends and link against them, whether they should be native or crosscompiled...
But I should be able to figure it out soon, very close now towards full working GNU tools on the Note 2.

OK, need help, have asked for it at http://stackoverflow.com/questions/...with-crosstool-ng-have-toolchain-which-archit also.
If anyone could assist, here goes:
I've built the crosscompiling toolchain with crosstools-ng.
I've cross compiled glibc, fine.
Have built a couple native arm (arm-exynos-linux-gnueabi) utils, like tar etc. and confirmed they work on the Android phone, when symlinking the built x-tools sysroot's lib directory to /lib on the android machine.
Now I need to build the native gcc, so I can develop on the machine. I'm having some philosophical problems with crosscompiling, as I'm relatively inexperienced in it.
I'd therefore like to ask how to proceed in steps exactly, as I've already spent two days with a trial-by-error approach, and so far no luck.
So: gcc depends on mpc, which depends on mpfr, which depends on gmp.
So, how do I proceed?
Which architecture deps do I build, with which host target and build options?
make a tools dir and build these deps there, so as not to mess with the functioning toolchain?
gmp (no host, build, target?)
mpfr (same?)
mpc (same?)
then gcc, how? --host=arm-exynos-linux-gnueabi --build=i686-build_pc-linux-gnu --target=arm-exynos-linux-gnueabi ?
Is this right, or am I messing up in some of the above steps?
Incidentally, I've followed this guide http://forum.xda-developers.com/showthread.php?t=1299962 to build the crosstool-ng toolchain, and it recommends compiling the native apps just with --host=arm...
I've been doing that, and they do work on the Android system, though it doesn't seem right to me, shouldn't it be --target=arm...?

nyarnon said:
Looking forward to that. Highly interested in php lighttpd mc busybox dropbear that kinda ****.
--
Sent from my N7100 with Perseus 25.4 Omega 5.0 and some stuff of Raubkatze
Click to expand...
Click to collapse
+1 ... I'm interested too, keep it up OP... So far I've only successfully build my own perl/libperl.so and runs great on my note2 from http://code.google.com/p/perldroid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've proceeded further, have built glibc 2.14 for the N7100, works, compiled gcc and some utils. The problem for now is that there is a bug in glibc 2.14 making statically compiled binaries fail on dynamic calls to libraries... It should be fixed in glibc 2.16...
So am experimenting now, trying to figure out how to add the latest glibc version support to crosstool-ng... If anyone knows, chime in.

[Request] BLU VIVO IV Camera

BLU VIVO IV has a nice Camera Stock Camera app, with many configs and modes, I pulled .apk and .odex from my father's phone and installed as system app into my Nexus 5 but I got FC, can anyone port it?? Thanks..
App Download: Dropbox
Screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rcoliveirajr said:
BLU VIVO IV has a nice Camera Stock Camera app, with many configs and modes, I pulled .apk and .odex from my father's phone and installed as system app into my Nexus 5 but I got FC, can anyone port it?? Thanks..
App Download: Dropbox
Screens:
Click to expand...
Click to collapse
can you get me the folder /system/framework?

opssemnik said:
can you get me the folder /system/framework?
Click to expand...
Click to collapse
Sure!, Click Here to download

rcoliveirajr said:
Sure!, Click Here to download
Click to expand...
Click to collapse
will need one more thing, this device (as all other mediacrap devices) haves a set of modifications to it´s dalvik / framework, these modifications are intended to block dissasembling of the *dex files. in order to bypass that i will need you to the following(it dosen´t require root, however it requires adb and a connection to the pc)
Download this zip:
http://d-h.st/XqG7
extract it to the adb folder, and connect the phone to the pc(with adb already setup on both, phone and pc)
run get_inline.bat(you can right click it -> edit to see the commands if you have any doubts)
after that upload both inline.txt(will be generated by get_inline.bat) and libdvm.so (this one is found at /system/lib) and post the link
or else i can´t decompile it:
Error occurred while disassembling class Lcom.android.camera.gallery3d.common.Ut
ils; - skipping class
java.lang.RuntimeException: Invalid method index: 32
at org.jf.dexlib2.analysis.CustomInlineMethodResolver.resolveExecuteInli
ne(CustomInlineMethodResolver.java:95)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyzeExecuteInline(MethodAna
lyzer.java:1422)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyzeInstruction(MethodAnaly
zer.java:941)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:20
2)
at org.jf.dexlib2.analysis.MethodAnalyzer.<init>(MethodAnalyzer.java:137
)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMetho
dItems(MethodDefinition.java:462)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefini
tion.java:370)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.ja
va:238)
at org.jf.baksmali.Adaptors.ClassDefinition.writeDirectMethods(ClassDefi
nition.java:283)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java
:112)
at org.jf.baksmali.baksmali.disassembleClass(baksmali.java:226)
at org.jf.baksmali.baksmali.access$000(baksmali.java:56)
at org.jf.baksmali.baksmali$1.call(baksmali.java:150)
at org.jf.baksmali.baksmali$1.call(baksmali.java:148)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

opssemnik said:
will need one more thing, this device (as all other mediacrap devices) haves a set of modifications to it´s dalvik / framework, these modifications are intended to block dissasembling of the *dex files. in order to bypass that i will need you to the following(it dosen´t require root, however it requires adb and a connection to the pc)
Download this zip:
http://d-h.st/XqG7
extract it to the adb folder, and connect the phone to the pc(with adb already setup on both, phone and pc)
run get_inline.bat(you can right click it -> edit to see the commands if you have any doubts)
after that upload both inline.txt(will be generated by get_inline.bat) and libdvm.so (this one is found at /system/lib) and post the link
or else i can´t decompile it:
Error occurred while disassembling class Lcom.android.camera.gallery3d.common.Ut
ils; - skipping class
java.lang.RuntimeException: Invalid method index: 32
at org.jf.dexlib2.analysis.CustomInlineMethodResolver.resolveExecuteInli
ne(CustomInlineMethodResolver.java:95)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyzeExecuteInline(MethodAna
lyzer.java:1422)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyzeInstruction(MethodAnaly
zer.java:941)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:20
2)
at org.jf.dexlib2.analysis.MethodAnalyzer.<init>(MethodAnalyzer.java:137
)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMetho
dItems(MethodDefinition.java:462)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefini
tion.java:370)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.ja
va:238)
at org.jf.baksmali.Adaptors.ClassDefinition.writeDirectMethods(ClassDefi
nition.java:283)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java
:112)
at org.jf.baksmali.baksmali.disassembleClass(baksmali.java:226)
at org.jf.baksmali.baksmali.access$000(baksmali.java:56)
at org.jf.baksmali.baksmali$1.call(baksmali.java:150)
at org.jf.baksmali.baksmali$1.call(baksmali.java:148)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Click to expand...
Click to collapse
Ok bro, I'm not with the phone right now (i'll get only on the weekend probably..), but I will send you as soon as I can.

opssemnik said:
will need one more thing, this device (as all other mediacrap devices) haves a set of modifications to it´s dalvik / framework, these modifications are intended to block dissasembling of the *dex files. in order to bypass that i will need you to the following(it dosen´t require root, however it requires adb and a connection to the pc)
Download this zip:
http://d-h.st/XqG7
extract it to the adb folder, and connect the phone to the pc(with adb already setup on both, phone and pc)
run get_inline.bat(you can right click it -> edit to see the commands if you have any doubts)
after that upload both inline.txt(will be generated by get_inline.bat) and libdvm.so (this one is found at /system/lib) and post the link
or else i can´t decompile it:
Error occurred while disassembling class Lcom.android.camera.gallery3d.common.Ut
ils; - skipping class
java.lang.RuntimeException: Invalid method index: 32
at org.jf.dexlib2.analysis.CustomInlineMethodResolver.resolveExecuteInli
ne(CustomInlineMethodResolver.java:95)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyzeExecuteInline(MethodAna
lyzer.java:1422)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyzeInstruction(MethodAnaly
zer.java:941)
at org.jf.dexlib2.analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:20
2)
at org.jf.dexlib2.analysis.MethodAnalyzer.<init>(MethodAnalyzer.java:137
)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMetho
dItems(MethodDefinition.java:462)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefini
tion.java:370)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.ja
va:238)
at org.jf.baksmali.Adaptors.ClassDefinition.writeDirectMethods(ClassDefi
nition.java:283)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java
:112)
at org.jf.baksmali.baksmali.disassembleClass(baksmali.java:226)
at org.jf.baksmali.baksmali.access$000(baksmali.java:56)
at org.jf.baksmali.baksmali$1.call(baksmali.java:150)
at org.jf.baksmali.baksmali$1.call(baksmali.java:148)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Click to expand...
Click to collapse
Sorry for the long time, I just got the phone right now, Here are the files

Calyx OS on pixel 4a (sunfish)

I am trying to install Calyx OS on pixel 4a. I am new to this and have hit several snags in the process but am currently stuck and can not find anyone who has posted a similar problem with solution. I am installing using a microsoft surface pro running windows 10. I have adb and flashboot in the same folder as sunfish-factory-8.2.8 (from calyx website, not unzipped) and the device-flasher from the calyx website. I have updated the google USB driver and am able to unlock the device and find it with fastboot devices command. However, when I run the device-flasher and follow the steps (It seems you are actually not expected to have the device unlocked when starting), I get an error that says " 'powershell' is not a recognized internal or external command, operable program or batch file. " I have repeated the process on another older windows device running windows 7 and got the same error message. Is this a problem with the device-flasher or something with my devices and what is the process to complete installation? Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It looks like it runs a powershell script. I don't think Windows 7 comes w/ Powershell by default. It used to be a closed source install on Microsoft's site but it looks like they made it open source and now release it on Github.
Install PowerShell on Windows, Linux, and macOS - PowerShell
Learn about installing PowerShell on Windows, Linux, and macOS.
docs.microsoft.com
Installing PowerShell on Windows - PowerShell
Information about installing PowerShell on Windows
docs.microsoft.com
specifically, go here https://github.com/PowerShell/PowerShell/releases/tag/v7.1.4
and download either PowerShell-7.1.4-win-x86.msi or PowerShell-7.1.4-win-x64.msi depending on if you use 32 bit or 64 bit Windows and it should work.

jawz101 said:
It looks like it runs a powershell script. I don't think Windows 7 comes w/ Powershell by default. It used to be a closed source install on Microsoft's site but it looks like they made it open source and now release it on Github.
Install PowerShell on Windows, Linux, and macOS - PowerShell
Learn about installing PowerShell on Windows, Linux, and macOS.
docs.microsoft.com
Installing PowerShell on Windows - PowerShell
Information about installing PowerShell on Windows
docs.microsoft.com
specifically, go here https://github.com/PowerShell/PowerShell/releases/tag/v7.1.4
and download either PowerShell-7.1.4-win-x86.msi or PowerShell-7.1.4-win-x64.msi depending on if you use 32 bit or 64 bit Windows and it should work.
Click to expand...
Click to collapse
Thank you for the help. The screenshot is from my surface pro 4 which has powershell. My older laptop may not have had powershell. I think in looking at another OS, that a script is needed to temporarily set the PATH or some sort of attribute so that powershell can be accessed by the executable file. I couldn't acuatlly figure out how to do this. So instead I loaded Graphene which has a surprisingly easy online set up. I haven't gotten to use it much to see if it is actually good but I could at least get it running on the phone.

[DEV] Thor Flash Utility - The new Samsung flash tool

Thor Flash Utility​This is a flash utility for Samsung devices, made from scratch in C#.
To run this, you must have .NET 7 runtime installed on your computer.
Latest release can be found on GitHub - https://github.com/Samsung-Loki/Thor
This tool was tested and works flawlessly, I'm open for any bug reports.
List of platforms​1) Linux (USB DevFS method)
2) Windows (not implemented)
3) Mac OS (not implemented)
How's it different from Heimdall?​Fun fact: Official Odin for Linux works using DevFS, and people report it working when Heimdall didn't.
1) Is able to do NAND Erase All (aka erase userdata) and erase any partition, given the length.
2) Ability to shutdown and reboot into Odin mode (not supported on every device)
3) Not using a USB transfer library and doing it natively for best results
4) Extended the PIT parser with new information being discovered
5) Can flash directly from an Odin .tar / .tar.md5 archive
6) Works with .lz4 files directly without manual extraction
7) Implemented EFS Clear and Bootloader Update options in Odin
8) Is able to change the sales code of the device
Support me​If you would like to support me and my team, donate here.
We're a team of teens (at age of 14-15) making random projects for fun.
Current list of commands​The up-to-date list of commands can be found here.
Usage guide​A comprehensive usage guide can be found here.
What devices were tested?​1) SM-M205FN/DS from 2019 0x00030000 (Unknown1: 0, Unknown2: 0, Version: 3)
2) SM-G355H/DS from 2014 0x00020000 (Unknown1: 0, Unknown2: 0, Version: 2)
Frequently Asked Questions​1) A fatal error occurred. The required library something could not be found.
This is a Linux Package Mixup, use this as reference.
2) What happened to original Thor (or Hreidmar)
This is a rewrite of Thor written from scratch, so I could implement the native USB communication.
Also, the old codebase was severely flawed in my opinion. I archived it here.
Credits​TheAirBlow for Thor Flash Utility
Benjamin-Dobell for documenting much of the Odin protocol

[reserved]

real

Bro finally revived good old Thor/Hreidmar

@TheAirBlow Thx.
Didn't test it yet but just a hint:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link leeds to wrong version acc to your post #1, or doesn't it?

bmwdroid said:
@TheAirBlow Thx.
Didn't test it yet but just a hint:
View attachment 5938745
Link leeds to wrong version acc to your post #1, or doesn't it?
Click to expand...
Click to collapse
Yeah, that was an accident. It is indeed .NET 7

hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)

ilshatiko1988 said:
hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)
Click to expand...
Click to collapse
This tool could probably be used in Termux or in a root shell if you somehow could install .NET 7 Runtime. But, it does require the phone to be rooted for Thor to be able to access the USB devices connected. And additionally, you need a (first phones USB) to (second phone's USB) cable to connect, or have some adapter to make it work.