ro.adb.secure=0 device still shows as unauthorized over adb Windows 10 I recently purchased a tablet that is a cheap allwinner a33 based Chinese product. I wanted to connect to it over adb but the RSA key popup would not come up.

The build.prop shows the ro.adb.secure=0 which should mean that the device requires no rsa authentication but my Windows 10 machine still shows the device as unauthorized.

How do I get the device authorized so I can use adb? 

I have no root access and would need adb to root.
I don't think ro.adb.secure is the reason why your phones shows up as unauthorized.

ro.adb.secure is a switch to allow adb to launch at boot (or not). relevant discussion.

Your problem sounds more like a local problem with your adb setup on your laptop. You should try the following steps:


download/install correct adb drivers for your linux/windows machine, which are released for this specific chipset (allwinner a33), possibly you won't find much, but something that is compatible hopefully
try lsusb (linux) to find the USB vendor/product ID for the tablet and search for compatible adb drivers
having the vendor and product ID you should be able to understand whether the USB mode for adb is actually enabled on the phone, i.e. if the phone runs USB with mtp,adb / ptp,adb or with just ptp etc.


example with a Moto G4 Play (msm8916):

shell@harpia:/ $ getprop sys.usb.config                                        
mtp,adb

pi@pi:~ $ lsusb
Bus 001 Device 007: ID 22b8:2e76 Motorola PCS 
................
shell@harpia:/ $ getprop sys.usb.config
ptp,adb

pi@pi:~ $ lsusb
Bus 001 Device 009: ID 22b8:2e84 Motorola PCS 


depending on the USB mode selected on the android phone, the USB product ID is different.

All that is closely related to udev rules (link to relevant discussion), although setting up or manipulating udev rules never solved my problems (and my Raspbian 9 doesn't even have the file /etc/udev/rules.d/51-android.rules).