Hi, I hope I'm in the right part of the forum. If not, I apologize. I can't help it. I've read dozens of different discussion forums.
I have a Xiaomi Redmi Note 9 Pro (joyeuse) running on Android 10 specifically Lineage 17.1.
I can't run my external wifi. The system finds it for me (see photo) but that's it.
{
"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 have installed a custom kernel ( I have tried several versions)
1. https://github.com/Neternels/android_kernel_xiaomi_sm6250/releases/tag/v3
2. https://github.com/Neternels/android_kernel_xiaomi_sm6250/releases/tag/v1
3. https://tgstat.com/channel/@akamekernelchannel
But nothing happened. My wifi usb is AWUS036ACS. I have KALI installed on my laptop where it works normally under 8812au/8821au and everything works. But on nethunter it only detects the wifi with the command "lsusb". I use the Nethunter app (from the kali app store). Wifi I can use is only internal in the mobile.
What am I doing wrong?
How I acted:
1. unlocked the bootloader
2. installed TWRP
3. installed android 10 lineage 17.1
4. installed magisk
5. reboot and system settings
6. installed magisk wirelles nethunter firmware module
7. reboot
8. install all nethunter hangs from nethunter app store
9. reboot and install kernel (I tested all I could find on my joyeuse type)
10. start nethunter
11. connect wifi usb, only detects using lsub (I tried both using USBC to USBA reduction, and USBC to USBA + power reduction)
12. not work…no led blink…
Sorry I'm an "old" newbie so maybe I'm making a mistake somewhere. I also tried various "wake up" commands but no result, the device doesn't exist, etc.
Because the command "lsub" detects the wifi usb device even in case of external power supply and without external power supply.
Or the wrong drivers? I tried to install from aircrack github drivers but it ended with an error and I read somewhere that my type of wifi usb device is supported in kali / nethunter. so I don't know anymore.
Thank you very much for your time and any help
The main thing u are missing you have to just not flash a custom kernel you have to patch it first by nethunterʼs official kernel builder script in order to work wifh,hdmi and bluetooth attacks
Maybe thatʼs the issue
hello bro, Thank you for your reply. but according to everything, it's a driver error (at least I think so) in Kali (notebook), the wifi does not work after installation, but the "lusb" command detects it as rtl8812au/8821. but in reality it is not this model but the rtl8811au model and it does not contain nethunter (as well as kali). I found a working driver where the developer confirmed that it works on Android. the problem is that I can't install it (nethunter does not support "classic installations" according to the procedure on the driver developer page), so I don't know how to insert this already functional driver into the android core (or nethunter?)
Driver is here: https://github.com/morrownr/8821au-20210708
Related
So, I've bought a Xiaomi Mi Pad 3 with a Chinese Rom, and I was following a tutorial to flash a new rom into it.
I basically did the following:
Installed MediaTek Drivers on PC
Opened "Smart Phone Flash Tool"
Specified Download-Agent as DA_SWSEC.bin and Scatter-loading File as the ROM
Unchecked preloader and clicked on "Download"
Connected the Xiaomi Mi Pad 3 to the computer while pressing Volume Down
Then, at this point, the computer crashed with a blue screen of death with the error "BUGCODE_USB_DRIVER". Here is the diagnosis of the error:
{
"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"
}
After that, the Mi Pad won't turn on, won't respond to any button and is not recognized by the computer.... I think I might have hard-bricked it.
I've found a tutorial about recovering a Mi Pad 1, but one of the steps is to make a bridge in the SD Card slot, which Mi Pad 3 don't seem to have.
I'm a developer myself, I know my way on things, I have a VM Linux, I'm willing to open the tablet and do whathever it costs to recover it.
Please, what can I do??
Please, anyone?
I FUC*ING RECOVERED MY FUC*ING TABLET. FUC* YEAH!!!!!!!!!!!!!!
I don't know exactly what it was, but I kinda did the following:
- Installed the latest SP Flash tool from spflashtool.com on my PC
- Installed Mi PC Suite for drivers and such
- To help debug, I had a freeware called "Free Device Monitoring Studio", to better understand what's going on on my USB ports
- I was playing a little with the connection/desconnection of the device on my computer, trying to understand how it was. I saw that Kali Linux running under Oracle VM kinda recognized it as a Mediatek device, but couldn't do anything else than that. With that info, my hopes went a little higher, because it wasn't completely dead after all.
- I opened Flash tool, configured it to used the same ROM and files I was using when I bricked it, because I'm pretty sure they weren't the cause of the brick and clicked "Download"
- Then I began messing with the tablet trying to make it be recognized by SP Flash Tool, upon turning it on and off and switching USB ports and connecting them directly to the motherboard USB ports instead of the frontal USB ports
- Then at one point it suddenly recognized and started downloading and flashing the new ROM. I faced some errors but with Format all + Download and having to disconnect/reconnect the batery to make it recognizable again and some little tweaks here and there, it ended up working.
My tablet is working fine now
Hello All,
I recently decided to switch to stock rom + Magisk root instead of custom + SuperSU. I also wanted to try MicroG and cut out Big G as much as possible. Everything went smoothly for the most part. MicroG settings checklist is all green. Apps working properly, including push message ones. Calendar, contacts, and stuff are syncing correctly without Google. OSM is working fine as a replacement to GMaps.
But...
My device is mysteriously writing about 2-3gb of log data each day (yes, gigabytes). This fills up internal storage to the point where I need to restore a backup from recovery (TWRP) every few days. So, I downloaded a log checker to try and find out which app was being naughty:
{
"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"
}
Magisk pops up quite often, but I assume it's a rooted app via Magisk rather than Magisk itself? I also see "pid=3732", but when I look for a corresponding process ID in OS Monitor, there isn't one. I didn't see anything on the error types that kept popping up (1300, 1306, 1320, 1327, 1400) when I did some net searches for them. So, I'm a bit baffled on what to look for next or how to interpret the rest of the log data.
Could anybody advise me on what step to take next?
For reference, here is my device/status/info:
Model: N915D Samsung Galaxy Note Edge (Japan/SCL24)
OS: Marshmallow 6.0.1 (TWRP 3.2.3-0 via Odin flash)
Root: Yes (Magisk 18.0 via TWRP install)
GApps: MicroG (via Nanodroid Magisk Module/TWRP install)
I've done the following without any success in identifying the problem:
Disabled/debloated almost all non-essential services/apps (via OpenAPK)
Tried both v 2.0 and v 1.1 of the FakeGApps Xposed module
Tried disabling various Xposed and Magisk modules that I was planning to use (Greenify, XTouchWiz, etc.)
Deleted most non-system apps (AFWall, Nextcloud, browsers, VLC, etc.) to try and isolate the problem (i kept Magisk, Xposed, and some diagnostic tools)
Stared really really hard at the phone
Can't remember what else at the moment
If it were an option, I would just go with Lineage OS. However, none of the releases are compatible with the Japanese version of the Galaxy Note Edge apparently. So I need to figure this out, or shop for a different phone >.<
Thank you very much for reading and for any help you can provide!
FYI in case anybody's interested, problem solved (sort of) by downgrading Magisk from 18.0 to 17.3.
Hello everyone!
I'm installing the Windows 11 (10.0.22000.51) in a (unsupported) MacBook Pro Late 2013 using BootCamp from Apple.
I'm following the XDA article bellow:
- "How to install Windows 11 on almost any unsupported PC"
https://www.xda-developers.com/install-windows-11-unsupported-pc/
I've tried to install a Windows 10 and then changed to Dev Channel using script and it didn't work well, the best options to me is:
- Burn Windows 11 to a USB ; and
- Create a hybrid installer .
In both cases, after the installation process finished and when the first reboot was finishing, I've got the message:
- Why did my PC restart?
{
"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"
}
In this screen, I can access the prompt using SHIFT+F10 and then be able to run "explorer", but with limited access to the system. In this same screen, there is a "Next" button, but if I click on it, the PC restart and come back to the same screen. I cannot install the Wifi driver to be able to access internet.
I'm using a MacBook Pro Late 2013 via BootCamp, specs in the following link:
https://support.apple.com/kb/sp691?locale=en_US
The ISO was created based on "Windows 11 Insider Preview 10.0.22000.51 (co_release) amd64" from the UUP Dump site:
https://uupdump.net/selectlang.php?id=e012464d-2c1e-4c36-9051-caa99ff6f213
Please, could you help me to bypass this error and resume my Windows 11 instalation?
Thank you in advance!
Regards,
Jose Silva.
Hey, I'm back to post my solution.
I've mentioned that I tried to install the WiFi driver for the "Broadcom
802.11ac Wi‑Fi wireless networking", to do it, I've used the file:
- Broadcom-FORCED-10x64-BCM43x_7.77.119.0-drp.
The installation was not so easy because I didn't have full access to the system, I did it by calling Control Panel from the command line. Unfortunately, even the installation was successful I'm not able to connect to my WiFi network, even trying by netsh command.
The solution for this case is to use a USB to Ethernet Adapted, in this case:
- Airlink101 USB 3.0 to Ethernet Gigabit Adapter (AGE-1000)
I've connected it directly to the router ethernet port and this device was detected by Windows 11 without any other driver installation.
After one or two reboots, Windows 11 was able to connect to the internet and concludes successfully its own installation.
The PC asks why itself restarts lol
I wanted to add my experience on a Mac Mini 2014.
Same thing happened. Shift F10 command prompt showed a network connection but the setup would not proceed.
I ran the BootCamp setup program on D:\BootCamp\Setup.exe (The install thumbdrive was D and that installed the wifi drivers.
Disconnecting the ethernet cable and connecting to wifi was the trick that allowed the setup to continue.
This worked for me as well. In the command prompt I changed to the d: drive which was what the USB stick is with the bootcamp installer on it and changed the dir to bootcamp then typed setup. It allowed the setup to continue like before but it moved on to allow me to select my Wi-fi then from there it continued the setup.
I did this install on a late 2012 Mac mini on April 25, 2022.
Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"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"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).
Hi all,
On Android 13, Google enabled KVM support for Tensor Chips model(Pixel 6 / 6pro / 6a). So we can run a Virtual machine at full speed, but there is no APP to utilize this feature.
I modified the Limbo Emulator (QEMU), so it can enable the KVM on Pixel 6 Phones. Due to the limitation of the kernel, the APP needs ROOT permission to access the KVM service(/dev/kvm)
Currently, only VNC is working on this APP, and you can only boot directly using the Linux kernel. UEFI did not work on KVM.
Network functions worked, but you may need to set the DNS inside the Guest OS.
Arch Linux for arm64 runs pretty well on Limbo. It runs even faster than Raspi 4. You can download it from ArchLinuxARM-aarch64-latest.tar.gz
Other Linux can also run on the Limbo, but you may need to recompile the kernel to enable virto-related functions.
Download link:
Releases · wasdwasd0105/limbo_tensor
Limbo for Tensor is a QEMU-based Hypervisor for Tensor-based Google Pixel devices such as Pixel 6 & 7 series. - wasdwasd0105/limbo_tensor
github.com
{
"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"
}
Hi, can't install the app, says invalid package
Invalid package
ne0ns4l4m4nder said:
Invalid package
Click to expand...
Click to collapse
marynius said:
Hi, can't install the app, says invalid package
Click to expand...
Click to collapse
You can install an apk package as a test package via adb (command adb install -t limbo~.apk). You can also use LADB to install (tested)
Simple installation of the apk is not possible due to the included test build in the application manifest
Awesome! This will come in handy.
Does anyone know if it would be possible to use the simulate secondary display dev option with a display link device or Chromecast?
A while back I discovered that the second screen will actually automatically tie to the (separate from main phone gui) mouse/ keyboard connected. The start menu of that virtual display opens apps in desktop resizeable mode.
It's just not practical to run a desktop as an overlay. If someone can figure out how to feed it to an external display we'd have a solid makeshift DeX with much more flexibility and potential.
Anyone managed to get a working internet connection on the guest?
Can you please tell us how to run windows arm using your latest update there are many trying to attempt this even by installing native qemu and all trying to create a different version of your app with more commands and also how to run other operating systems besides your provided one