yashsingh1/xdaforums huggingface dataset:
[Realme 5 Questions & Answers] doveman:
I've just got my Realme 5i returned after repair (replacement main board) and I've unlocked the bootloader, flashed TWRP and vbmeta9, flashed Magisk and enabled MagiskHide but I can't set a PIN. Whenever I try, after confirming the PIN it returns to the settings screen and shows "Lock Screen Password - Off".

I know I managed to set a PIN before it needed repairing, as when my brother received it from me from his Birthday, he phoned me to ask for the PIN to access it but I can't remember what I did then to get it working.

I tried to install "Realme 5i Magisk Fix for ColorOS by IT&AUTOS.zip" in Magisk as I did that before but now it isn't working and the log says "copying to temp, error unzipping file". Would installing this be what got the screen lock working before?

I've got a TWRP backup of all the partitions from before it was repaired but I can't seem to access them to restore, as when I select the Storage option from Restore it shows the SD card is only 6GB, when it fact it's 128GB and the only file it shows is "257eee4a" which is actually the folder above the dated folders containing the backups.. From the Install option, I can browse the SD card normally and I flashed Magisk from a folder on the card, so I don't know why it's not accessible from the Restore option. If I could, then maybe restoring the System and Data partitions would get me back to the state where the PIN was set but I'd be a bit nervous about restoring the System partition after then main board has been replaced, in case any files are tied to the old hardware.
[Realme 5 Questions & Answers] doveman:
I thought what I might have done to get it working last time is to relock the bootloader (after flashing the stock recovery to prevent bootloop) and then unlock it again but if that is what I did before, it isn't working now.

First I updated to A.20 via the stock recovery, as the service center had flashed A.15. It kept booting to stock recovery after that until I did Format Data and then it booted OK and after locking the bootloader I was able to set a PIN.

Then I unlocked the bootloader and it automatically wiped data but I still had to Format Data to stop it booting into stock recovery and now I can't set the PIN again.

I see there's a 5i Decryption (COs).zip. What does this do? I tried flashing that via TWRP before I tried the above steps but it didn't get the PIN working.
[Realme 5 Questions & Answers] doveman:
I just flashed TWRP and then installed 5i Decryption (COs).zip and wiped Cache/Dalvik Cache and now it gets stuck on the yellow realme logo when I try and boot. Can't even power it off when it's like that but thankfully volume up and power gets me to bootloader and TWRP and doing a factory reset wipe got it booting again.

I still can't turn on the PIN/Lock Screen password though. 😡
[Realme 5 Questions & Answers] doveman:
I tried restoring my TWRP System and Data backup from last August when the Lock Screen password was working but it still doesn't work, so it must be something in one of the other partitions that affects this and I'm reluctant to try restoring those in case it bricks the phone because the main board has been changed.
[Realme 5 Questions & Answers] doveman:
Can anyone help me please? Does anyone have the lock screen password working with unlocked bootloader, or is everyone who has installed custom recovery/rooted their 5i just using it without any password to protect it?
[ONE Android Development] Tomoms:
Well done! I'm personally not interested in NetHunter but it's nice to see some development still happening for our good old Oneplus One :)
[ONE Android Development] JERKBALL:
Thank you very much for keeping up with new Releases for our beloved OPO...

I wiped up my OPO completely and started from scratch...

But after sticking to your tutorial and setting up chroot I get the following:

[-] sdcard /lib/modules/3.4.113-yesimxev-g4885cdc67a2 doesn't exist or isn't mounted. .

Is this related to the new kernel?
[ONE Android Development] yesimxev:
Thanks for mentioning, the modules dir wasn't in the correct place in the zip. It will be fine in the next release. I'll update the links once they are released.

For now, update to the latest app and you can ignore that message, it will remain as a warning only.
[ONE Android Development] Ween Dwijler:
Didn't work for me at all. Back to LOS 16.0.
[ONE Android Development] yesimxev:
Have you updated the NH ap from the store? I'll build a kernel flasher so you have it before release
[ONE Android Development] Ween Dwijler:
Hmmm...... I just spent about a full week to get Nethunter functional on an Oneplus One. It was a very revealing journey, lots of flashing, bricking, flashing, upgrading, downgrading,I've learned a lot.

Tried CM and LOS 16 and 17 with NH for Marshmallow and for Pie. Used the ones from Kali's download site and the ones you linked above. Followed all instructions to the letter and comma, and all variations on it that I could imagine.

The end result is always the samel No bluetooth, no usb.

And since the whole idea is to have a compact mobile to do pentesting on wireless setups and devices in the field, for which we need usb and bluetooth, it seems to be pretty useless. It really puzzles me why the Oneplus One is the preferred device, other than it is a nice Mr. Robot gadget to show of in the bar?

However, I truly want to be proven wrong in my conclusion and work with you to get this sorted out. If you like. I get the idea there are many with similar problems that never got solved and they might have given up and moved on to another device. But I am not afraid of a good challenge, so....... lets do it.

This is what I have:

Oneplus One 16GB

Alfa AWUS036ACH with Realtek rtl8812au chip (have the latest drivers)

Can we make it really work?

(mind you, pentesters at $ 200K a year are probably not willing to spent so much time on getting a tool to work. I'm just a student in pentesting and still learning, so economics are not that much of an issue, yet).

I realise this is all free, open source software. But that doesn't mean it shouldn't be working perfect after proper installing everything.

I hope I can help to make it better.
[ONE Android Development] yesimxev:
I have a OPO with the above install but an updated kernel which not released yet. But I'll provide you tonigh for testing. Although the above should be fully functional other than the modules dir (which is ignored by the latest NH app).

I'm happy to help you as I know how frustrating is to get used to this kind of version vs device specific fight :)

Just to confirm:

No usb or bluetooth? usb hid? Or wlan1? What's your busybox version? Internal or external bluetooth?
[ONE Android Development] Ween Dwijler:
I got that, too. But did the whole thing again and than it was gone.

I noticed that a good way to make sure all reinstalling happens in a "clean" way is to follow this method of working:

1.

TWRP recovery - Wipe all, except USB-OTG. ---> Reboot.

2.

Repeat that 1 more time!!! (counting for residual voltage, causing bits to be persistent in memory, contaminating new install)

3.

Flash LOS 16 or 17 with TWRP from attached USB stick. (If data doesn't show up on USB-OTG, touch it for 5 seconds, release, phone vibrates and the data will be visible. If that doesn't work, unplug the OTG cable, wait 5 seconds and replug it. Repeat previous touch, vibrate etc. If that doesn't work, unplug USB, 5 seconds wait, replug, go to mount and try to mount USB-OTG, return to Install, select Storage and repeat the first step of this no.3 part)

4.

After flash is complete, reboot, setup CM or LOS, activate Developers options by tapping 7x on Build number (you can find that under Settings/about phone). One step back, under settings you find Developer options. Go in there, check Advanced reboot, uncheck Update Cyanogen recovery, check Android debugging. Press right power button shortly, Power options pops up. Choose Reboot, next screen pops up, choose Recovery, confirm with tapping ok.

5.

Back in TWRP, unplug the USB, wait 5 seconds and replug the USB in. Follow the steps I described in 3. to get the data visible. Choose to install Magisk or SuperSU (whatever you like and have). Let it run, when finished reboot again. After reboot is completed, reboot again from LOS to make sure Magisk or SuperSU are completely installed and ready.

6.

Reboot into TWRP Recovery again, do the USB mount trick thing, choose the right version NH zip (you might have, like me, different versions on it) and install NH. When finished, reboot.

7.

Pay attention here!

Back in LOS, check that Magisk or SuperSU are properly installed and working.

Start NH Terminal, popup asks for Superuser rights. You have 10 seconds to grant them! Do it! Follow the further screen instructions, allow for all.

Next, start up NH itself, 10 seconds only for granting SU right!!! Allow all. After this, reboot system.

8.

Start NH terminal, command sudo apt update && sudo apt full-upgrade. Follow the instructions. During that, you get a white window asking for yes or no. Chose Yes and confirm with enter. Another one like that will pop up again a little later, choose the second line (keep present config etc.) and confim with yes and enter.

Let the process run its course. When finished, reboot system again.

9.

Start up NH (if it is not already started), go to Kali Chroot Manager and start it. All should be green now and ready to go.

Happy Hunting!
[ONE Android Development] Ween Dwijler:
After trying to install above twice, with red warning in TWRP that something failed to mount, I abandoned it and switched back to CM and the Marshmallow NH. But that doesn't work either.

At least I got to see lsusb in LOS 16 with NH and your kernel update ten. Before I updated your kernel, lsusb didn't show anything in LOS 16 NH.

Here goes:

Installed 2020.4 Pie. No lsusb readout, no bluetooth.

Next:

TWRP installed your ...ten.zip, rebooted and after 2 attempts (unplug and plug in again) lsusb in NH terminal registered the OTG as hub, on 001.002 was my USB stick. Unplugged the stick, plugged in the AWUS036ACH, and 001.002 became 0bda Realtek 802.11.

Checked in terminal of Android, got the same reading.

So Android sees it on the USB, NH sees it too. However, no wlan1 shows up when I do iwconfig, ifconfig or run airmon-ng.

Are the Realtek rtl8812au drivers already patched into the kernel? (Do I say that right?).

If yes, what prevents NH from getting wlan1?

The wifi adapter is not powered (I thought it could get power from the OPO?). Has that anything to do with it?

Bluetooth is the internal one from OPO. Busybox was installed with the NH version. I'm now back at CM 13 again, so I donno which version in the LOS install I had. I will go back to the machines and get the LOS 16 installed.

Or do you prefer LOS 17?
[ONE Android Development] Ween Dwijler:
Ok, I am ready to go.

- Wiped the OPO completely

- Flashed and installed lineage-17.1-20210128-nightly-bacon-signed.zip

- Did the setup, developers options etc.

- flashed and checked proper install of Magisk

Next step?

NB. I have 2 hours more today. After that it is bedtime for me. We probably have a time difference. For me it will be 3AM in 2 hours.
[ONE Android Development] Ween Dwijler:
Ok, I thought to go on with installing the NH fs from your link. Got the same error:1 again. Error installing zip file 'usb_otg/nethunter-2020.4-generic-armhf-kalifs-full.zip'.

Get the same message for the other one.
[ONE Android Development] yesimxev:
Seems like you haven't done the

adb shell setprop ro.build.system_root_image true

Haven't you flashed the zips from here yet? What did you use? This version is not released yet anywhere, it's here for testing.
[ONE Android Development] Ween Dwijler:
I used the zips you provided in the links above. But, indeed, I didn't do the setprop. Busy getting it back up again....hahaha. Next install will be after the setprop command. Try to do it now. Stay tuned.
[ONE Android Development] Ween Dwijler:
A 5 years old phone is NOT going to beat a 60 year old man.
[ONE Android Development] yesimxev:
8812au is not supported on this device.

Btw are you trying both pie and ten zips on lineage-17.1 rom?
[ONE Android Development] yesimxev:
Keep it up! Flash this kernel https://www.androidfilehost.com/?fid=17248734326145730243
[ONE Android Development] Ween Dwijler:
Ok, used setprop ro.build.system_root_image true, got message "failed to map file and error installing.

This is a new one for me!!

I think TWRP is somehow damaged. Will brick it now and do a full setup again, starting with Color. Tomorrow more about this saga.
[ONE Android Development] yesimxev:
I went back to TWRP 3.4 but 3.5 also flashed everything. The zip might got corrupted? Installs for me fine. I'll make the revert to bluez-4.101 because bluez 5.x is not working on this device
[ONE Android Development] Ween Dwijler:
I used both TWRP 3.4 and 3.5, same result. Sideload didn't work either. Managed to get Magisk flashed. That first had the same error as the rest. Last it went well. So, I thought, lets go for NH too. Nope. Error again.

Tomorrow I will download everything fresh again from the web, and see if it works. Maybe the USB stick got corrupted somehow? Got another one to try.

Which chipset is supported on the OPO, if not 8812au?
[ONE Android Development] Ween Dwijler:
Waaahhhh, goodnight.
[ONE Android Development] yesimxev:
Is the NetHunter my generic fs installer zip is messed up? Can you flash if you adb push the file onto /sdcard/?

Mostly these:

ATH9K_HTC (AR9271, AR7010)

Ralink

RT73

RT2800USB

RT3070

Realtek

RTL8188EUS

RTL8188CU

RTL8188RU

RTL8192CU

RTL8192EU

RTL8723AU
[ONE Android Development] yesimxev:
I wish to be a pentester, in progress ;)
[ONE Android Development] Ween Dwijler:
Part 1

Ok, here we go.

System = LineageOS 17.1, TWRP 3.5 (or 3.4, problem is the same)

Problem 1 -- "Updater process ended with ERROR: 1"

Problem 2 -- after using setprop an extra message occured "failing to map /usb_otg etc."

Problem 1 was fixed with re-flashing the boot.img, however, it only worked for Magisk. Nethunter kept having the same messages: ERROR 1 and Failing to map.

It turns out that TWRP doesn't work well on LineageOS 17.1, causing those messages.

To test this, I re-flashed LineageOS 16.1, flashed Magisk, and after flashed nethunter-2020.4-oneplus1-pie-kalifs-full.zip. No errors occurred.

But... now the next error popped up, in Nethunter chroot.

"sdcard/lib/modules/3.4.113-yesimxev-lineageos-ga06023c36fa-dirty doesn't exist or isn't mounted. "

I've seen that one before. Update && Upgrade didn't solve it. So, I will move on to install LineageOS 17 and see what happens than.

Part 2, about that, will follow later today.
[ONE Android Development] Ween Dwijler:
I don't really understand it. Look at the screenshot of Kali Nethunter website, mentioning the alfa AWUS036ACH as being confirmed to be working with a Nethunter build.

?????
[ONE Android Development] Ween Dwijler:
Part 2

Reinstalled LineageOS 17.1 and it indeed turns out that TWRP doesn't like to work in LOS 17.1 Got the same ERROR 1 as before. So that's it for this combination of agony. At least for me. No 17.1 with TWRP 3.4 or 3.5.

I will see if a lower version will work on it.

To be continued
[ONE Android Development] Ween Dwijler:
Part 3

Indeed TWRP 3.1.1 did work.

First flashed the file nethunter-2020.4-generic-armhf-kalifs-full.zip (downloaded from the link you provided in the beginning of this thread) and after flashed the file kernel-nethunter-20210206_204827-oneplus1-ten.zip (from your last link).

Unfortunately, icons don't show up in program slide. What did I do wrong? Did I first had to install the previous kernel, the one from 20210117_044828? Or the original kernel and than patch these ones on it?
[ONE Android Development] yesimxev:
Please setprop before flashing and copy the nh installer zips to the device after lineage is flashed. I've uploaded a new zip, replaced the link above
[ONE Android Development] yesimxev:
Yes but some devices like OPO doesn't have a patch for that yet
[ONE Android Development] Ween Dwijler:
Ok, I'll go do it now.
[ONE Android Development] Ween Dwijler:
Is it hard to write a patch for it?
[ONE Android Development] Ween Dwijler:
Ok, did the setprop before flashing. Copied the zips from USB to local Download dir/map. Installed first nethunter-2020.4-generic-armhf-kalifs-full.zip and after that kernel-nethunter-20210206_204827-oneplus1-ten.zip (your latest).

Both installs went smooth, no interruptions. After that, rebooted the system. No program icons (NH Terminal, NH, etc.) anywhere.
[ONE Android Development] Ween Dwijler:
This is what it looks like after installing.
[ONE Android Development] yesimxev:
The first patch is starting from kernel 3.10 but this is 3.4 and has to be modified a bit. I simply don't have time, @kimocoder is an expert in kernels, he created the patch. As I see it needs more time for me to backport.

patches/3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch · master · Kali Linux / NetHunter / build-scripts / kali-nethunter-kernel · GitLab

Kernel Builder

gitlab.com

As far as I know, the apps should have been flashed. It did on mine. However, the install script will be updated from next release. For now, please check if everything works fine. FYI only external BT adapter is supported.

Please download nethunter store app https://store.nethunter.com/ to install the apps
[ONE Android Development] yesimxev:
Uploaded a complete zip, this should flash apps too https://www.androidfilehost.com/?fid=17248734326145732098
[ONE Android Development] Ween Dwijler:
To make sure, this is the one running on LOS 17.1?
[ONE Android Development] yesimxev:
I'm sorry you are right, uploading the correct one now
[ONE Android Development] yesimxev:
The one is: https://www.androidfilehost.com/?fid=17248734326145736621
[ONE Android Development] not_the_droid_ur_lookin4:
This is the version of Droid i'm looking.... LOS 17.1 with nethunter... but on the oneplus 6 and or 7 and or 7pro. I'm surprised there's so much recent development for such an old phone. Would this work on a OP6 or OP7? I'm guessing not, right? Any plans for that? Thanks.
[ONE Android Development] Ween Dwijler:
Compare the hardware, if it is the same architecture, it should work. You'll have to try in that case.
[ONE Android Development] yesimxev:
I recommend the OOS 11 (Android 10), even if it's not lineage. Quite powerful.

- android : ten
linux : '4.14'
kernel : 1.1
description : Oxygen OS 11
author : Re4son
source : 'git clone https://github.com/Re4son/android_kernel_oneplus_sm8150_draco -b nethunter-10.0'
features : [BT_RFCOMM, HID-4, Injection, QCACLD, RTL8812AU]

looking at https://gitlab.com/kalilinux/nethun...i-nethunter-devices/-/blob/master/kernels.yml

https://images.kali.org/nethunter/nethunter-2020.4-oneplus7-oos-ten-kalifs-full.zip

But I guess you've got that info alrady
[ONE Android Development] Ween Dwijler:
By the way, I try to get my head around this whole issue with external (USB) wifi on the O+1. NH is running with chroot, meaning effectively it is a kind of VM on Android?
[ONE Android Development] yesimxev:
External wlan is ok, doesn't reboot anymore on unplug. NH is an overlay "on top of the ROM"
[ONE Android Development] Ween Dwijler:
You mean that the Realtek rtl88xx.au drivers will work now?
[ONE Android Development] Ween Dwijler:
Hi, just installed Los 17.1 and Nethunter on top of it. All works good.

Now, how to get the USB working with the Realtek driver? Without it, the whole setup is pretty useless.

All I have now is a pretty nice looking 1+1 which I could use to impress friends in the bar, pretending I am a Mr. Robot. However, they have no clue where I'm talking about, so.......
[ONE Android Development] yesimxev:
I'll try to patch but my weeks are extremely busy now
[ONE Android Development] not_the_droid_ur_lookin4:
I do... but thanks anyway. Tried it... doesn't work for me... but I'm guessing I must have a one in a million bad phone or something because it seems to work for everyone else. Anyway I'm gunna get off this thread because I don't have a OP1 anyway... OP6... so gunna stick to that thread.
[ONE Android Development] Ween Dwijler:
That would be very, very nice. I'm really looking forward to have this working and start to use it in the field.

FYI attached the lsusb readings in kali terminal and android terminal. The realtek shows up, but I guess the drivers are missing.
[ONE Android Development] yesimxev:
There could be several obstructions in these new OSes. Why don't you open an issue on kali-nethunter-devices on gitlab?
[ONE Android Development] Ween Dwijler:
Hi, did you manage to make already some progress with the realtek? Thanks. I know you're a busy bee.
[ONE Android Development] Ween Dwijler:
Where did you get your LOS 17.1 from? I recommend to use the links given by yesimxev. Use Magisk, instead of SuperSU. If you have good cables, a pc and the right drivers, you can play that phone as a fiddle.

I'm using TWRP 3.5.0_9, LOS 17.1 and the Nethunter version provided by yesimxev. It all works fine, except for the USB Wifi (but I believe yesimxev is working on that).

If you backup your data, you can completely erase the 1+1 and start from scratch. Do a bootloader, get TWRP on it, install LOS 17.1, install Magisk on it and as last one Nethunter. It should work.

Ask if you have problems.
[ONE Android Development] MrtnMrtn:
I downloaded both lineage 17.1 and nethunter from the official websites. I will try with the links from yesimxev.

Thanks!
[ONE Android Development] UsPdSr:
Yesimxev explained several times, that at the moment the Realtek 8812au not supported is by this device in general due to the age of the kernel and the fact that so far nobody has written a working patch for it.

Every other chipset, especially the common ones like Atheros9271, Ralink 2800 and many more* are fully supported and working just fine.

There are dozens other (far more portable) Wifi adapter for a couple of bucks on eBay, Amazon etc. - fyi

If not, then look for another device, or simply be patient.

Many heaps

*
[ONE Android Development] Ween Dwijler:
I understand. I already looked for them around here (Thailand) but couldn't find any, yet. Most of the stuff sold here has no brand, and it is impossible to figure out what chipset the adapters have.

I know how to check what chipset is used for a particular brand and model, but searching for it the other way around doesn't seem to work. Frustrating....

Anyway, to narrow down my search, which chipsets have been reported to work with the 1+1? So not supposed to work, but really working in the field (somebody with real life experience with that particular usb wifi model).

If you, or anybody else here can enlighten me with that info? I would be much obliged.
[ONE Android Development] maruf.mld24:
Will this adapter work Tp link rtl-722n v3?
[ONE Android Development] Ween Dwijler:
Did you check the list?
[ONE Android Development] maruf.mld24:
View attachment 5248521

kali nethunter website said TP link TL-wn722n v2/3 may be supported using RTL8812AU driver.

I have TP link TL-wn722n v3.

how can i install the driver?
[ONE Android Development] Ween Dwijler:
I never came that far. But I guess you could try to install it the way you would in Kali. Use the nethunter terminal to do it. I have the rtl8812au drivers, but I think it didn't work. Try it, or buy one that is supported and save yourself the hassle.

Good luck!
[ONE Android Development] maruf.mld24:
Plz Give me a link for rtl8812au driver and installation guide...
[ONE Android Development] Ween Dwijler:
ALFA AWUS036ACH Driver & Support Page

Buy One Now Drivers: Alfa AWUS036AC/AWUS036ACH/AWUS036EAC Windows Vista/7/8/8.1Alfa AWUS036AC/AWUS036ACH/AWUS036EAC Windows 10/8/7 with WPA3 Security support- released 10/4/2019Alfa AWUS036AC/AWUS036ACH/AWUS036EAC Mac OS 10.15 CatalinaAlfa AWUS036AC/AWUS036ACH Mac Mojave/Catalina Installation...

store.rokland.com

Take it from there. Good luck!
[ONE Android Development] maruf.mld24:
sorry but that was not for my adapter tp link tl-722n...
[ONE Android Development] Ween Dwijler:
you wanted the rtl8812au drivers? That's them. If you don't take the trouble to read and pay attention, sorry, you're on your own from here.