HELP!
my Sony Xperia Go ST27i is locked i forgot the PIN for the screen lock. Is it possible to enable USB debugging using PC? my adb is not recognized since usb debugging is not turned on and I can't unlock my bootloader due to this. I can't boot into recovery mode as well.
hayes.asdfg said:
my Sony Xperia Go ST27i is locked i forgot the PIN for the screen lock. Is it possible to enable USB debugging using PC? my adb is not recognized since usb debugging is not turned on and I can't unlock my bootloader due to this. I can't boot into recovery mode as well.
Click to expand...
Click to collapse
Boot into a custom recovery (like TWRP) and try this in Terminal:
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mtp,adb" >>/system/build.prop"
reboot
Now reboot to system and see if ADB is working.
If that doesn't help, try this:
Code:
adb shell
setprop persist.service.adb.enable 1
setprop persist.service.debuggable 1
setprop persist.sys.usb.config mtp,adb
reboot
BTW, you can try as many as wrong pins which would enable you to change the pin again via Google account. That's the best way..
GokulNC said:
Drain your phone charge to 0%
Then plug in your phone, but don't switch it ON.
After 15mins, use your regular key combination like power+volumeUp+volumeDown or whatever to get into bootloader menu.
Open up recovery mode or fastboot mode and do whatever you need.
If you want to enable USB debugging, try this in fastboot mode:
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
If that doesn't help, try this:
Code:
adb shell
setprop persist.service.adb.enable 1
setprop persist.service.debuggable 1
setprop persist.sys.usb.config mass_storage,adb
reboot
BTW, you can try as many as wrong pins which would enable you to change the pin again via Google account.
Click to expand...
Click to collapse
I have a similar problem in that I can't access my phone and settings. I tried the adb shell and it goes error: device '(null)' not found.
Then I tried the
echo "persist.service.adb.enable=1" >>/system/build.prop but again no good "The system cannot find the path specified."
Does the phone really need to be drained for this to work? My phone charge though I can't see it is around 90%.
On the setprop persist.service.adb.enable 1 is says that 'setprop' is not recognized as an internal or external command, operable program or batch file.
Another question that comes to mind is whether doing factory reset removes root?
after a have tried many times to get it work and every time i get a new issue i discovered how to get Camera2API wokr on miui 11
First :
1- you need i custom Recovery like twrp or orangefox
2- adb & fastboot toolsthen after booting into recovery connect your whyred device to pc and open a shell and type adb root and hit enter then adb shell
finally do this commands
Code:
setprop vendor.camera.aux.packagelist com.bsgmod.camera,com.google.android.GoogleCameraWide,com.android.camera
setprop vendor.camera.aux.packagelist2 com.android.systemui
setprop camera.hal1.packagelist com.skype.raider,com.google.android.talk,com.whatsapp
setprop persist.camera.eis.enable 1
setprop persist.vendor.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
setprop persist.vendor.camera.HAL3.enabled 1
setprop persist.vendor.camera.is_type 5
setprop persist.camera.is_type 5
setprop persist.vendor.camera.is_mode 5
setprop persist.camera.is_mode 5
setprop persist.camera.max.previewfps 60
setprop persist.vendor.camera.max.previewfps 60
setprop persist.camera.tnr_cds 1
setprop persist.vendor.camera.tnr_cds 1
setprop persist.camera.tnr.video 1
setprop persist.vendor.camera.tnr.video 1
setprop persist.camera.tnr.preview 1
setprop persist.vendor.camera.tnr.preview 1
setprop persist.camera.tnr.snapshot 1
setprop persist.vendor.camera.tnr.snapshot
setprop persist.camera.llnoise 1
setprop persist.vendor.camera.llnoise 1
setprop persist.tnr.process.plates 2
setprop persist.vendor.tnr.process.plates 2
setprop persist.denoise.process.plates 2
setprop persist.vendor.denoise.process.plates 2
setprop camera.lowpower.record.enable 1
setprop vidc.enc.dcvs.extra-buff-count 2
reboot your device and install google camera, now it works
nice when I come to home will try it. thank you.
Gulicius said:
nice when I come to home will try it. thank you.
Click to expand...
Click to collapse
unfortunately ,wont work for me,got problem enabling camera2api long time
Simple method Flash HAL3_ENABLE_MIUI.zip all gcam works fine
Screenshots ....
arunvij said:
Simple method Flash HAL3_ENABLE_MIUI.zip all gcam works fine
Click to expand...
Click to collapse
I believe this working too,but like i said nothing works for me at past.
But will try it
arunvij said:
Simple method Flash HAL3_ENABLE_MIUI.zip all gcam works fine
Click to expand...
Click to collapse
Flashed via newest RWolf recovery ,xamera probe says Legacy , GCams many vesrions tried crashes
PMGC_7.0.009_Full_Version_v8.apk using this version always perfect
arunvij said:
PMGC_7.0.009_Full_Version_v8.apk using this version always perfect
Click to expand...
Click to collapse
@TBlackScare thanks for sharing. But I think these settings are coming from Oreo & Pie both and so has a lot of unwanted changes.
With MIUI Pie, the camera has moved to vendor partition. So
setprop persist.camera.HAL3.enabled 1 <<----- is not required
setprop persist.vendor.camera.HAL3.enabled 1 <<----- does the work
Also if someone wants to just use Gcam then just below is enough
setprop persist.vendor.camera.HAL3.enabled = 1
Rest all build.prop modifications are for improving MIUI cam.
mGforCe said:
@TBlackScare thanks for sharing. But I think these settings are coming from Oreo & Pie both and so has a lot of unwanted changes.
With MIUI Pie, the camera has moved to vendor partition. So
setprop persist.camera.HAL3.enabled 1 <<----- is not required
setprop persist.vendor.camera.HAL3.enabled 1 <<----- does the work
Also if someone wants to just use Gcam then just below is enough
setprop persist.vendor.camera.HAL3.enabled = 1
Rest all build.prop modifications are for improving MIUI cam.
Click to expand...
Click to collapse
I cant seem to be connecting my device when I on recovery mode, its alwas says "null/no device". any suggestions?
not working on MIUI 11 with stock rom
Hi everybody,
while it worked with STOCK MIUI 10, it is not working with STOCK MIUI 11 on my Xiaomi Redmi note 5 (whyred). And i can't downgrade to MIUI 10.
Any suggestions ?
I have the same issue than tuxnowar. Please fix for MIUI 11 PIE on Redmi Note 5 Global (Whyred)
Hello. carefully follow the tutorial from the link provided, use RedWolf recovery necessarily but do not choose the method with temporary write by adb. First of all, once you have all the necessary files, the first step is to copy the file "HAL3_ENABLE_MIUI_PIE.zip" to the root of the internal memory of the phone. Only then do you start to follow the tutorial !!!
When the phone arrives in the RedWolf recovery menu, from there you choose "Install" and you choose the file copied earlier, before starting the procedure.
After restart your phone should have cam2api enabled. I followed this tutorial and it worked on MIUI 11 !!!
Good luck!
mGforCe said:
@TBlackScare thanks for sharing. But I think these settings are coming from Oreo & Pie both and so has a lot of unwanted changes.
With MIUI Pie, the camera has moved to vendor partition. So
setprop persist.camera.HAL3.enabled 1 <<----- is not required
setprop persist.vendor.camera.HAL3.enabled 1 <<----- does the work
Also if someone wants to just use Gcam then just below is enough
setprop persist.vendor.camera.HAL3.enabled = 1
Rest all build.prop modifications are for improving MIUI cam.
Click to expand...
Click to collapse
It was simple and fast via buildprop editor app. It works, just needed to reboot device. Thanks
Work on Santoni whith pie miui 11?
tuxnowar said:
Hi everybody,
while it worked with STOCK MIUI 10, it is not working with STOCK MIUI 11 on my Xiaomi Redmi note 5 (whyred). And i can't downgrade to MIUI 10.
Any suggestions ?
Click to expand...
Click to collapse
Try flashing this via custom recovery:
https://drive.google.com/file/d/1-NjK2fo0mQ459f2nfh7WflARVkfS_4uU/view
I tried all zips and flashed with orangefox seems to be done but when i probe manual camera test all goes in red, can anybody help me?
Good day! Everything listed above does the job for Android 9 / MIUI 11, but how about Android Q / MIUI 11? Recent update with MIUI 11 based on Android 10 left me sad and broken because now I can't enable Camera2 Api same way I did for Android Pie.
Same for me. How to use gcam in miui11 android q?
Same. Anyone know what to do for Q?
I have been trying to get my POCO F2 into diag mode so I can use it with QPST.
Has anyone tried to do this and was successful?
I'm currently on AOSP so I'm not entirely sure if you have to be on stock for this to work. I google searched not finding a working results, if anyone is on stock or MIUI eu rom and willing to try and report results that would be great.
Within OS root is needed/ EDL reboot the phone to that mode and no root needed.
Root is required and a setup of adb. USB debugging ON.
Qualcomm USB Driver https://androidfilehost.com/?fid=11410963190603864074
QPST 2.7.274 & 2.7.286 a google search finds these.
Open a command prompt
adb shell
su
So far I have tried with my phone booted in the normal OS. If any of these setprops makes the phone not detect USB in windows or you want to go back default, simply toogle USB debugging on and off on your phone in developer options and will remove that prop.
setprop sys.usb.config rndis,diag,adb --> this creates 902D driver port driver in device manager but fails to recognise in QPST configuration.
setprop sys.usb.config diag,serial_cdev,rmnet,adb --> 9091 driver same as above
setprop sys.usb.config diag,serial_cdev,rmnet --> 9092 driver same as above.
setprop persist.vendor.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb -->doesn't recognise the drivers
EDL -
Apparently QPST works in EDL mode, I tried and it doesn't boot it with the rom I have installed so thinking need to be on stock only.
adb reboot EDL --> then a port should show in device manager
OR reboot to twrp and reboot to EDL from there.
Any help would be greatly appreciated.
jbm76 said:
I have been trying to get my POCO F2 into diag mode so I can use it with QPST.
Has anyone tried to do this and was successful?
I'm currently on AOSP so I'm not entirely sure if you have to be on stock for this to work. I google searched not finding a working results, if anyone is on stock or MIUI eu rom and willing to try and report results that would be great.
Within OS root is needed/ EDL reboot the phone to that mode and no root needed.
Root is required and a setup of adb. USB debugging ON.
Qualcomm USB Driver https://androidfilehost.com/?fid=11410963190603864074
QPST 2.7.274 & 2.7.286 a google search finds these.
Open a command prompt
adb shell
su
So far I have tried with my phone booted in the normal OS. If any of these setprops makes the phone not detect USB in windows or you want to go back default, simply toogle USB debugging on and off on your phone in developer options and will remove that prop.
setprop sys.usb.config rndis,diag,adb --> this creates 902D driver port driver in device manager but fails to recognise in QPST configuration.
setprop sys.usb.config diag,serial_cdev,rmnet,adb --> 9091 driver same as above
setprop sys.usb.config diag,serial_cdev,rmnet --> 9092 driver same as above.
setprop persist.vendor.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb -->doesn't recognise the drivers
EDL -
Apparently QPST works in EDL mode, I tried and it doesn't boot it with the rom I have installed so thinking need to be on stock only.
adb reboot EDL --> then a port should show in device manager
OR reboot to twrp and reboot to EDL from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Why want to use QPST at all?
Dadovvv said:
Why want to use QPST at all?
Click to expand...
Click to collapse
I want to use EFS explorer to check the NV items for my carrier. Perhaps edit them after I've backed up EFS.
Volte was working on Android 10, but not working on 11.
jbm76 said:
I want to use EFS explorer to check the NV items for my carrier. Perhaps edit them after I've backed up EFS.
Volte was working on Android 10, but not working on 11.
Click to expand...
Click to collapse
Did you figure out a solution to this?
JazonX said:
Did you figure out a solution to this?
Click to expand...
Click to collapse
Install these usb drivers - https://gsmusbdriver.com/category/xiaomi/page/3
These are the commands -
Both of these work.
adb shelll,
su
setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
Either setprop command will work.
setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl
In regards to the VOLTE issue still no go on A11 - I have been able to access the EFS partition but the ims_user_agent won't stick even if I write to it with in EFS explorer of EFs tools, it doesn't survive a reboot.
jbm76 said:
Install these usb drivers - https://gsmusbdriver.com/category/xiaomi/page/3
Click to expand...
Click to collapse
Hey Mate, Thanks a lot for the response,
That's a lot of models in that page - Which particular one should I pick ?
JazonX said:
Hey Mate, Thanks a lot for the response,
That's a lot of models in that page - Which particular one should I pick ?
Click to expand...
Click to collapse
Do you have the POCO F2? or another phone?
jbm76 said:
Do you have the POCO F2? or another phone?
Click to expand...
Click to collapse
It's an ASUS ROG 5.
Thanks a ton for the command !!!!
Your command worked! My device manager is refreshing, But the EFS Tools finally connected.
Managed to update the first slot..
Only issue now is the second slot command is not working.
{
"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"
}
JazonX said:
It's an ASUS ROG 5.
Thanks a ton for the command !!!!
Your command worked! My device manager is refreshing, But the EFS Tools finally connected.
Managed to update the first slot..
Only issue now is the second slot command is not working.
View attachment 5394561
Click to expand...
Click to collapse
I believe the 2nd slot only works if you have a sim card in that slot.
jbm76 said:
I believe the 2nd slot only works if you have a sim card in that slot.
Click to expand...
Click to collapse
Yeah, Got a sim card already in it..
So close, yet something is not right.
All the other EFSTools versions are giving critical error, bad response etc.
Only this version is working, and that has the option -s issue.
Any ideas ?
Thanks bro, You've helped a lot today !!
JazonX said:
Yeah, Got a sim card already in it..
So close, yet something is not right.
All the other EFSTools versions are giving critical error, bad response etc.
Only this version is working, and that has the option -s issue.
Any ideas ?
Thanks bro, You've helped a lot today !!
Click to expand...
Click to collapse
https://github.com/HomerSp/EfsTools/releases/download/0.10-modded-1.2/EfsTools-0.10-modded-1.2-win32.zip
I found this version worked best.
jbm76 said:
https://github.com/HomerSp/EfsTools/releases/download/0.10-modded-1.2/EfsTools-0.10-modded-1.2-win32.zip
I found this version worked best.
Click to expand...
Click to collapse
This one errors out - Operation time out, or Critical error.
Is there a different driver for Win32 ?
Assuming since this one says Win32, and Im on a Windows 10 X64.
JazonX said:
This one errors out - Operation time out, or Critical error.
Is there a different driver for Win32 ?
Assuming since this one says Win32, and Im on a Windows 10 X64.
Click to expand...
Click to collapse
I used it on Windows 64, worked fine for me.
Did you edit your EfsTools.exe.config file?
JazonX said:
It's an ASUS ROG 5.
Thanks a ton for the command !!!!
Your command worked! My device manager is refreshing, But the EFS Tools finally connected.
Managed to update the first slot..
Only issue now is the second slot command is not working.
View attachment 5394561
Click to expand...
Click to collapse
try it with mcfg_autoselect_by_uim_Subscription01 instead of the -s 1 switch
jbm76 said:
try it with mcfg_autoselect_by_uim_Subscription01 instead of the -s 1 switchView attachment 5394569
Click to expand...
Click to collapse
I have done it using the subscription code;
Modified codes as Subscription00 / Subscription01 as follows;
Both codes were executed successfully.
Codes would be as follows;
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription00
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription01
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / Subscription00
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / Subscription01
Is this modification to the code correct ?
Or is there a Subscription02 ?
After reboot, My IMS still unregistered and No VoLTE in menu.
I'm pushing the mcfg_sw.mbn of Etisalat UAE to the device. This move, and enabling VoWifi profile in PDC both worked in the past for me. Now that PDC is not working, This Efstools is the only option.
I've made a lot more progress with you, Thanks a lot for your responses buddy!
JazonX said:
I have done it using the subscription code;
Modified codes as Subscription00 / Subscription01 as follows;
Both codes were executed successfully.
View attachment 5394855
View attachment 5394857
Codes would be as follows;
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription00
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription01
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / Subscription00
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / Subscription01
Is this modification to the code correct ?
Or is there a Subscription02 ?
After reboot, My IMS still unregistered and No VoLTE in menu.
I'm pushing the mcfg_sw.mbn of Etisalat UAE to the device. This move, and enabling VoWifi profile in PDC both worked in the past for me. Now that PDC is not working, This Efstools is the only option.
I've made a lot more progress with you, Thanks a lot for your responses buddy!
Click to expand...
Click to collapse
Try this instead-
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim_Subscription01 -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription01
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
PDC should work with using that setprop I provided you - it works for EFS explorer and PDC on this device.
If PDC doesn't work - you could try this setprop
setprop sys.usb.config diag,serial_cdev,rmnet,adb to run PDC to select the correct profile.
jbm76 said:
Try this instead-
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim_Subscription01 -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription01
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
PDC should work with using that setprop I provided you - it works for EFS explorer and PDC on this device.
If PDC doesn't work - you could try this setprop
setprop sys.usb.config diag,serial_cdev,rmnet,adb to run PDC to select the correct profile.
Click to expand...
Click to collapse
PDC doesn't work;
Tests are as follows;
Code:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Doesn't result in any change, Doesn't trigger any drive change or installation either.
The previously used code always works, however PDC throws the below error;
Code:
setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
The commands you suggested;
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
both works, Upload takes place.
This command throws the following error;
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim_Subscription01 -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription01
JazonX said:
PDC doesn't work;
Tests are as follows;
Code:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Doesn't result in any change, Doesn't trigger any drive change or installation either.
View attachment 5396527
The previously used code always works, however PDC throws the below error;
Code:
setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
View attachment 5396529
The commands you suggested;
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
both works, Upload takes place.
This command throws the following error;
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim_Subscription01 -t -o /nv/item_files/mcfg/mcfg_autoselect_by_uim_Subscription01
View attachment 5396531
Click to expand...
Click to collapse
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
able to try the efstools commands inside instead? It worked on my oneplus 7pro and may work for zf8 pro too?
mgear356 said:
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
able to try the efstools commands inside instead? It worked on my oneplus 7pro and may work for zf8 pro too?
Click to expand...
Click to collapse
These are the same codes above, In OnePlus they've got a FTM mode in Android 11 where these can be executed.
For ROG 5 - These didnt work.
Hi guys,
I can activate qualcomm diag port only via AsusVoLTE-su_fixed.apk, ,none of the above commands works (setprop sys.usb.config diag,serial_cdev,rmnet,adb triggers random related Rog Phone devices, no diag port though, and the other one nothing at all).
My problem is that I can't get through that EfsTools.exe efsInfo command, it shows corespondig port COMx found in device manager - qualcomm diag COMx, but goes to idle without any feedback. Also tried several efstools versions.... maybe one of you can provide me correct config so I can pass this annoying step. Meanwhile I'm digging after Q X60 .mbn's ....
Cheers!
C:\Users\HieAnh>adb root
restarting adbd as root
C:\Users\HieAnh>adb remount
Not running as root. Try "adb root" first.
Click to expand...
Click to collapse
after i do :"adb root" to cmd,
then i get :"restarting adbd as root"
next i do :"adb remount"
but i get :"Not running as root. Try "adb root" first."
a big question for this problem
my phone is rooted, switch ro.secure=0, ro.debuggle=1
pls help me
What response do you get when you type su in shell?
ze7zez said:
What response do you get when you type su in shell?
Click to expand...
Click to collapse
i get :
C:\Users\HieAnh>adb shell
gracerlte:/ $ su
gracerlte:/ #
Click to expand...
Click to collapse
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
jwoegerbauer said:
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
Click to expand...
Click to collapse
hmm, i just run
adb pull /data/data
Click to expand...
Click to collapse
but i get
/data/data/: 0 files pulled, 0 skipped.
Click to expand...
Click to collapse
why ?
You have to mount /data partitton as RW.