yashsingh1/xdaforums huggingface dataset:
[General Topics] ReDxKinG:
So im looking to upgrade my phone soon. I currently use a Sidekick ID (Yes yes I know). Been a long time reader of the XDA forums so im looking for some expert advice from well, you guys(the experts). From my understanding the Tilt and Wing are pretty much the exact same phone with different carriers with the exception that the 8925(tilt) has double the ram speed and a faster cpu than the Herald(wing) as well as gps. Anyway the OBVIOUS choice is (Or at least I thought it was) the 8925(tilt). I proceeded to do some more research on the phone and soon discovered the Video Driver\No Hardware accelaration problem on those phones which was a huge turn off for me once I found out about it. As far as the Herald(wing) goes, it is obviously alot slower than the 8925(tilt) due to the slow cpu ,and freeing up memory is something that seems to be more of a tedious task that you have to do every so often. A friend of mine owns a Herald(wing) and he uses the OpenTouch Rom by Ttrans1 which is awesome and is definitely better/speedier than the stock rom. Anyway it seems to me that no matter which phone I get, I am taking a loss in some form or another. So I am here to ask you guys, would I be better off with a slow phone WITH proper video hardware acceleration (Herald/Wing) or a much faster Phone WITHOUT proper video hardware acceleration (Tilt/8925). Any advice,comments or suggestions would be greatly appreciated. Thanks :)
[General Topics] ReDxKinG:
32 views and not one response? :(
[General Topics] ReDxKinG:
Anyone??????? No need to be shy...
[General Topics] orb3000:
Both are more or less the same

http://gizmodo.com/gadgets/cellphones/htc-herald-reviewed-verdict-thin-and-awesome-211475.php

http://tecmoviles.com/htc-8925-sencillamente-espectacular/

But black looks better
[General Topics] KyleK29:
.. wait .. why? Wait a month or two and use the upgrade on a newer phone (HTC Rapheal). Or, just upgrade to the HTC Dream if you don't mind an O.S. switch as it has the larger screen.

Trust me, you're going to be disappointed if you do the Tilt/etc and see the new ones out in a month or two at incredible prices (to compete with the iPhone's popularity and price-range).

Not sure if T-Mobile is getting the Rapheal, but AT&T should be getting it at the end of October from what I've been told. Obviously, T-Mobile's HTC Dream (G1) is releasing on the 14th of October I think (for $179 w/2yr).
[General Topics] orb3000:
Or even better, wait a little longer and you can get the HD!!!

That´s a real piece of work!
[General Topics] GiZZy:
you can get teh G1 thats coming out next month. I currently have a wing and im really happy with it, but im selling it and getting the g1.
[General Topics] galaxys:
I second that!! :) The HD will be the ultimate device!
[General Topics] ReDxKinG:
First off,Thanks for the replies, I appreciate it. The general responses seem to be to wait for a newer/better device which makes sense and is the smarter choice Howeverm, the problem (which I failed to mention in my original posting) is that I need to decide within the next week because my job requires me to have a phone with exchange server email(Which I think the sidekick doesnt have and even if it does, the sidekick is not a very "professional" phone and I dont want to use it for work). After reading about the HD though I am DEFINITELY going to upgrade to it when it comes out, but for right now I need to decide between the wing or tilt as I can get either one for 150$. So anyone have any advice as far as those 2 phones go? I understand that they are more or less the same but they both have 2 different problems So I need advice as to which one would be the better choice FOR NOW given the problems they both suffer. Thanks
[General Topics] Legodude522:
I figured I'd just throw this out there, I almost went for the AT&T Tilt but decided to forgo that and got the ETEN Glofiish M800. The Tilt and the M800 are pretty much direct competitors. The M800 has a VGA res screen so I got that :) . As far as I know, the specs were very similar.

There are some reported bugs with the M800, I've fixed all the issues I've had so far and all seems well. :D
[General Topics] ReDxKinG:
Ive read up on the glofiish and while its a pretty cool phone it is outside of my price range. But thanks for the suggestion as I had never even heard of that phone before prior to you mentioning it lol. Unfortunately, My choice is only between the Wing and The Tilt
[Realme 8 Pro] sapu98:
I've been waiting since its release to be able to root it, there are some tutorials online but they look sketchy and I dont trust them.

The only one I would trust is made by the magisk team but it has a link that says "cooming soon" when you try to download the Realme 8 Pro stock rom, which is also not present on the official realme website.

This is what made me skeptic: how can the youtube indian guy have the stock rom meanwhile neither the official website and magisk have it? is it worth to give it a try or if I mess up I wont be able to restore my phone? has anyone tried to do so? which tutorial should i use?
[Realme 8 Pro] mArIuS%:
At this time there is no solution to root realme 8 pro, in-depth test app is not working with this device so far, firmware is not avaleble to download (from a credible source). We just have to wait, i don't know for how long, i just hope devs will find a solution in a shot time.
[Realme 8 Pro] sadique2k22:
Is fileload.coloros.com trusted??
[Realme 8 Pro] StratOS_HTC:
First the bootloader "can" be unlocked and this is the primarly thing to do.

Secondary rom images allready exists.

https://oppostockrom.com/oppo-realme-8-pro-rmx3081

http://www.frpbdteam.online/

Zip and opf's can be extracted .... So boot (kernel and ramdisk) can be modified to work with modified Magisk and all other needed things (Bootloader unlock, FRP, vbMETA, Verity ...) to gain root.

Regarding recovery and flash via current recovery the things are not known yet, also custom recovery options.

Update: Will be very hard to participate for this device ...
[Realme 8 Pro] @Malware:
Yeah
[Realme 8 Pro] mvikrant97:
Stock ROM is here
[Realme 8 Pro] StratOS_HTC:
There are available stock roms, update OTA's but to be able to flash,root ... first the unlock bootloader should be available. Since the HAL is missing from the fastboot and the bootloader is still locked the only thing is to flash is original stock ROM.

Secondary AVB check, meta, recovery, boot, FRP and other things should be done also.

Currently the MSM flash is only available for signed and official files, also MD5 checked flash files.

There is no working piece of tutorial to obtain any of it. Some partially and also magisk patched boot allready done by me, but cannot flash it to test and prepare other needed steps.

Recovery is original, there is no log or cache log currently available to check.
[Realme 8 Pro] Rehankhan189:
Yes, But You have to root realme 8 pro rmx 3081 stock rom as there is no custom rom available i have sucessfully rooted realme 8 pro
[Realme 8 Pro] StratOS_HTC:
EXPORT and GDPR Roms are different.

Guess you have EXPORT and not the GDPR (EU).

No custum roms available just because the bootloader lock and/or EDL verification and/or ABV and/or parted excrypted userspaced super.
[Realme 8 Pro] Ashik640:
Can you please make a guide(in details) about how you've rooted? Step by step.
[Realme 8 Pro] @Malware:
Flash gsi rom
[Realme 8 Pro] @Malware:
Unlock bootloader using adb, patch boot.img using magisk flash
[Realme 8 Pro] ThnhNgn:
Can you have a more specific guideline please?
[Realme 8 Pro] mvikrant97:
A detailed guide is available here! https://magiskapp.com/root-realme-8-pro/#
[Realme 8 Pro] SIRKRA:
Don't trust those links, realme 8 pro is not rootable in any way.
[Realme 8 Pro] Ashik640:
So, is the screenshot of @Rehankhan189 fake?
[Realme 8 Pro] @Malware:
dude are you kidding ?

realme 8 pro can be rooted using magisk (but first unlock bootloder)
[Realme 8 Pro] @Malware:
probably that is not fake because it can be rooted using magisk but first unlock bootloder
[Realme 8 Pro] SIRKRA:
Then ask @StratOS_HTC if it really is, gdpr for sure not, export maybe
[Realme 8 Pro] StratOS_HTC:
GDPR bootloader EU version cannot be bootloader unlocked or rooted ...
[Realme 8 Pro] StratOS_HTC:
... and will even not be able to unlock it (GDPR)... forever ...
[Realme 8 Pro] SanjitMahato:
yes, it is now rootable.

but to root you have to unlock bootloader first
[Realme 8 Pro] kakalkin:
Please tell me how can I get root rights for this phone? My phone is intended for the Russian region, and now I have version 13 of Android, with a locked bootloader. What to do? Please explain step by step
[Realme 8 Pro] melontini:
Not possible, sorry.
[General Questions and Answers] raspiduino:
I have an Galaxy A6 which has the Exynos 7870 CPU. I downloaded the kernel source from the Samsung source page, and when I typed

make menuconfig

it has the Virtualization option. So does that mean the CPU itself support KVM? Thanks!

I just compile the kernel, pack it to boot.img, put boot.img to the AP and flash it using Odin but not work. I want to try if KVM exist to run Windows ARM in QEMU kvm in Termux :)
[General Questions and Answers] sleirsgoevy:
I have the very same device and am currently working on a patch for KVM to work on it. Will post here if I get it working reliably. On the other hand this SoC has its own quirks, I'm not sure if it'll ever be possible to run unpatched guest OSes (some registers are only writable from EL3 (TrustZone), not initialized by that, guest VMs read them, and it can't be trapped).
[General Questions and Answers] raspiduino:
I tried installing a root kernel with stock rom but then it said there is some illegal operation and force me to reset the phone. I have no important data on it so I reset it and then it still displays the error. So I guess if we need root to use

/dev/kvm

(or at least add user to kvm group)
[General Questions and Answers] sleirsgoevy:
WDYM by "root kernel"? Magisk?
[General Questions and Answers] raspiduino:
Yeah the magisk patched kernel.
[General Questions and Answers] sleirsgoevy:
Very weird. For me it once got into "KG state: Prenormal", but was fine otherwise. I first reverted it to full stock, then flashed TWRP from github, then flashed magisk apk via TWRP, then after reboot installed the apk normally. There is a notification about "unauthorized actions", but it does not force anything, I can just ignore it.
[General Questions and Answers] sleirsgoevy:
This seems to work for me. qemu-system-aarch64 in Linux Deploy works with -enable-kvm.

Attached a kernel with KVM enabled + latest Magisk: https://mega.nz/file/d8lGhY7b#NKQZEL3G6bT7SetrHLh4rNgmgg0L5EXJ0Lir_QjAebA

EDIT: uploaded the patch to Github: https://github.com/sleirsgoevy/exynos-kvm-patch
[General Questions and Answers] raspiduino:
Oh thanks you so much! I will try this right now!

Just 3 questions:

- How do you build and pack the kernel? I tried both "make Image" and "make Image.gz" then unpack boot.img using android image kitchen but it did not boot when I flash with Odin.

- Do you get a factory reset prompt when first boot this kernel with stock firmware? I got it once when I tried patching stock kernel with magisk.

- If you get the factory reset prompt in question 2: after reset and setup Android, I cannot get the phone's pin lock and password work anymore. So how to fix this?

Thank you very much!
[General Questions and Answers] raspiduino:
{Mod edit: Quoted post deleted}

Yeah you somehow can boot Windows ARM on it (natively)
[General Questions and Answers] sleirsgoevy:
I used magiskboot for repacking the kernel. Unpack boot.img with `magiskboot unpack boot.img`, replace `kernel` with `Image` (not `Image.gz`), then repack with `magiskboot repack boot.img`, and flash `new-boot.img`. The magiskboot binary can be found in the Magisk installation zip.
[General Questions and Answers] raspiduino:
Edit: It does boot and run :) but the lock screen does not work :( . There is an issue thread in Magisk's github page and it only solve the problem temporarily :( . After reboot it asked again for password.

I will try to fix this.
[General Questions and Answers] sleirsgoevy:
A small status update: Windows on ARM currently halts due to missing support for performance counters in Linux 3.18's KVM. Linux handles its registers as "read all zeroes, write ignored", but Windows expects the counters to actually tick. Probably a proper implementation needs to be backported from newer Linux.
[General Questions and Answers] raspiduino:
I tried your patch on my device, modified a little bit for calling your "preinit_hyp_mode()" function from "init/main.c". I can boot into stock rom, install termux on it and then install qemu-system-arm and qemu-system-aarch64. I also run "chmod 666 /dev/kvm". Then I tried qemu-system-aarch64 with --enable-kvm but it said kvm not found. I also tried qemu-system-arm but it said "kvm_init_vcpu failed: invalid argument". "/dev/kvm" is available. What am I doing wrong?

Also my hard keys (volume up/down and power key) don't work after booting with that kernel but it work with stock rom, although this is not the main problem.

Thanks!
[General Questions and Answers] sleirsgoevy:
Blame Samsung, not yourself. This phone has a 64-bit kernel but 32-bit Android system, thus (the 32-bit build of) qemu-aarch64 thinks that the architecture is incompatible, and qemu-arm cannot utilize the 64-bit interface the kernel is providing. What I did was to install an aarch64 chroot using Linux Deploy, and install qemu on it.
[General Questions and Answers] raspiduino:
I tried installing Debian arm64, Ubuntu arm64, Fedora aarch64 and a Debian Bootstrap .tar.gz from debian.org but none of them work, always falls with "Bad system call" or "sh not found". So could you be more detailed, like which option do you use in Linux Deploy? Thanks!
[General Questions and Answers] sleirsgoevy:
This should not happen, unless for some reason you are trying to do it without using root. If you're using the proper root-enabled chroot, and not the proot hack, changing the architecture in settings should be enough.
[General Questions and Answers] raspiduino:
I see the message "Linux deploy was granted superuser right", but the arm64 install failed, configure failed, deploy failed, ssh and vnc failed :) and if I use Linux deploy telnet then "su -" and "linuxdeploy shell" it said "/system/bin/sh not found" :( . I installed Magisk, busybox extension from magisk. Only the armhf work on my phone.

-------------------------------------------------------------------------------

NOT THAT FAST :)

I sloved it :)

Just install armhf chroot like normal in Linux Deploy, then VNC to that chroot. Type "dpkg --add-architecture arm64" then "apt update" then "apt install qemu-system-arm:arm64". Then "chmod 666 /dev/kvm" and "qemu-system-aarch64 -M virt -cpu host --enable-kvm" It just work :) I loved it !

I can confirm that file "qemu-system-aarch64" is aarch64 executable and it run on my phone :)

Thanks sleirsgoevy my friend :))

View attachment 5402267
[General Questions and Answers] raspiduino:
How did you boot Linux on it? I tried Debian ARM64 netinst vmlinuz and initrd but it does not output anything, even with "-nographic" or "-vga std". I checked QEMU monitor and it show that the register does change.

I also tried Windows ARM but no luck. qemu_efi.fd does not bring up a EFI interface or anything and the registers value doesn't change.
[General Questions and Answers] sleirsgoevy:
For debugging, add proper earlycon options to kernel command line, 'coz it is probably panicking way before late serial is initialized.

Steps to boot Linux:

* dump DTB from your QEMU installation: `qemu -M virt,dumpdtb=dtb.bin`

* use dtc tool from the Linux kernel source to translate it to dts

* modify the dts file as follows:

```

timer {

interrupts = <0x1 0xd 0x304 0x1 0xe 0x304 0x1 0xb 0x304 0x1 0xa 0x304>;

always-on;

compatible = "arm,armv8-timer", "arm,armv7-timer";

clock-frequency = <0x18cba80>; <-- add this

};

```

* now recompile it to dtb and provide to qemu via the -dtb flag

Attached my own patched DTB for -M virt.
[General Questions and Answers] raspiduino:
Linux now boot, thanks!
[General Questions and Answers] raspiduino:
How did you boot QEMU EFI and how did you know Windows not boot due to performance counter? Thanks!

I found U-boot have an option to load efi. I boot it with kvm on my phone and it boot, but halt when load windows efi from arm64 iso.
[General Questions and Answers] sleirsgoevy:
I built ArmVirtPkg from edk2. Needs a patch to work around hacky timer implementation in KVM (it'd probably be better to fix the kernel instead; fixed upstream somewhere in 4.x), but otherwise it works.
[General Questions and Answers] raspiduino:
I found a bunch of ARM/KVM backport of the 3.18 kernel at Chromium page. See it here.

The description is: "

3.18 seems to be missing some support to properly run as a kvm host on arm64 systems, so let's pull back the necessary changes"

Also is this and this (CTRL + F then find "pmu") is what you said about pmu read/write permission on Windows ARM?
[General Questions and Answers] raspiduino:
Could you please send your patch for edk2 here (or at lease the edk2 img)? Thanks!

I tried to patch it but it still hang at some point because interrupt not arrive :((. Tried to replace it with 'ret' but still not work. Also edk2 on kvm become slower than software emulation after it comes to timer interrupt!
[General Questions and Answers] sleirsgoevy:
diff --git a/ArmPkg/Drivers/TimerDxe/TimerDxe.c b/ArmPkg/Drivers/TimerDxe/TimerD - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

This is a patch for EDK2 that works around the timer bugs.

The first patch is against a bug in 3.18 KVM, patched upstream somewhere in 4.x (timer gets disabled after it fires, and needs to be enabled manually). The second patch works around that uninitialized register issue, and cannot be removed without hacking EL3 (Windows will probably need to be binary patched).

EDIT: note: you'll need to use "ramfb" device for the display, VGA emulation is broken on QEMU+KVM on ARM.
[General Questions and Answers] raspiduino:
I think we also need the QEMU's virt-2.11 or 2.12 for Windows too. I tested the same QEMU/KVM version on my RPi 4 and Windows only boot with that option. Also remember to disable highmem by "-M virt 2.12,highmem=off". Otherwise it will cause a BSOD.
[General Questions and Answers] sleirsgoevy:
Uploaded to GitHub a proper (I hope so) fix for one of the timer issues.
[General Questions and Answers] raspiduino:
Yes your patch boot. But Windows on KVM still need further work to boot :((

I have backported the PMU emulation from Linux 5.10.77, it successfully built and Android booted. But when I launch the Windows KVM, the phone reboot. I don't know whats wrong here :((

Btw here is the source tree: https://github.com/raspiduino/a6lte-kvm/tree/dev. It's the stock source with your patch, and to see what changed pls click on the commit. Thanks!

EDIT: here is the interesting thing:

I got something from 'cat /dev/last_kmsg':

sys_regs.h line 113 was in the function 'reset_unknown' https://github.com/raspiduino/a6lte...699055763184f9/arch/arm64/kvm/sys_regs.h#L113

Maybe disable trap to that function will help? I will try tomorrow
[General Questions and Answers] sleirsgoevy:
I would recommend backporting from 4.x kernels, they refactored the code (tldr: removed arm32 host support) in 5.7.
[General Questions and Answers] raspiduino:
I have fully backported sys_regs.c from Linux v4.14, including new required vgic3 functions, but Windows still hang :(. You can see at my github

I will try kernel 5.4 for now. Hope that work.

EDIT: I have checked /proc/kmsg and lastkmsg but no bug or error about kvm, only the trustzone worker service:)
[General Questions and Answers] sleirsgoevy:
Nice, will probably want to check this. Where exactly does it hang now? Does it now get to the boot logo without poking around in gdb?
[General Questions and Answers] raspiduino:
Well sorry for being late to the party :) It probably hang on the windows efi load (the file name is bootaarch64.efi if I remember well). No loading cusor were there and the register hang (checked with info registers). I have booted it on my pi4 kvm and it worked fine, so it's kvm fault.

Btw someone reported that Linux 4.19 should be fine: here

There is no boot logo for win arm, it won't clear the edk2 splash screen.
[General Questions and Answers] raspiduino:
It has been a while, today I come back to your repo and saw the commit backporting PMU. So did you try that and did it work?

Thanks!
[General Questions and Answers] sleirsgoevy:
I do not know any easy way to actually test this stuff, at least from strace output it seems that the relevant ioctl by qemu succeeds. Probably installing the pref in a Linux VM can be useful, at least I now have a proper VM running instead of a hacked-up initramfs.
[General Questions and Answers] Korsunag:
Hello! How to apply it in practice (dtb.bin)?

Here I did not understand a bit :) I have already assembled and flashed the kernel only on Samsung A7 (Exynos 7880). As you can see, the KVM module is involved:

Тут я немного не понял :) Я уже собрал и прошил ядро только на Samsung A7 (Exynos 7880). Как видите, задействован модуль KVM:

But no matter what OS I run with the KVM option, there is always a black screen or "the guest has not initialized the display (yet)".

I ask for help, otherwise I'm stuck here, for the second week I've been trying to run at least Ubuntu arm64.

Но независимо от того, какую ОС я запускаю с опцией KVM, всегда есть черный экран или «гость не инициализировал дисплей (пока)».

Прошу помощи, а то я тут застрял, уже вторую неделю пытаюсь запустить хотя бы Ubuntu arm64.
[General Questions and Answers] raspiduino:
Hello friend! From what I translated (sorry I didn't know Russian :)), you are having problem with display. Can you give your full command line of your Ubuntu VM? Thanks!

Also, I think you should use the ramfb display, since by default QEMU targets ARM virt machine with no display.

I recommend booting Ubuntu with EDK II (uefi) with the patch included in sleirsgoevy's repo!

Thanks and looking forward to your replies!
[General Questions and Answers] Korsunag:
Привет! Если я загружаю Windows без KVM с помощью этой командной строки:

[КОД]qemu-system-aarch64 -name "Windows 10 на ARM64" -M virt -cpu cortex-a53 -smp 3 --accel tcg,thread=multi -m 2048 -pflash /sdcard/qemu/QEMU_EFI.img -device VGA -device nec-usb-xhci -device usb-kbd -device usb-mouse -device usb-storage,drive=boot -drive if=none,id=boot,file="/sdcard/Download/woa_17134.img" - устройство USB-хранилище,диск=drivercdrom-drive file="/sdcard/Download/virtio-win-0.1.185.iso", media=cdrom,if=none,id=drivercdrom-vnc :2[/CODE]

Привет! Если я добавлю параметр KVM: "-enable-kvm", я получу следующее:

[КОД] qemu-system-aarch64 -name "Windows 10 на ARM64" -M virt -cpu cortex-a53 -smp 3 -enable-kvm -m 2048 -pflash /sdcard/qemu/QEMU_EFI.img -device VGA -device nec -usb-xhci -device usb-kbd -device usb-mouse -device usb-storage,drive=boot -drive if=none,id=boot,file="/sdcard/Download/woa_17134.img" -device usb-storage ,drive=drivercdrom -drive file="/sdcard/Download/virtio-win-0.1.185.iso", media=cdrom,if=none,id=drivercdrom -vnc :2[/CODE]

И так со всеми ОС на ARM :( Однако, когда убираю опцию KVM, винда загружается, но очень медленно.
[General Questions and Answers] raspiduino:
Yes, if you disable KVM, QEMU will emulate the whole system and it will run on any host hardware :)

Which UEFI firmware you are using? Where did you get it from?
[General Questions and Answers] Korsunag:
I used this instruction: https://github.com/raspiduino/waq

And the kernel was assembled according to this instruction:

bestofcpp.com - bestofcpp Resources and Information.

bestofcpp.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, bestofcpp.com has it all. We hope you find what you are searching for!

bestofcpp.com