Database Users

[Q] Understanding GladRoot Root script for 1.26-1.83

I was looking at the code for GladRoot (http://forum.xda-developers.com/showthread.php?t=1016060) and I had a couple of questions I was hoping someone could answer.
First of all, does anyone have the code for psneuter?
Secondly, if the goal of rooting is to Superuser.apk, why is temporary root access necessary? I've never used adb before this, but isn't the point that developers can easily do things like install applications using it? The superuser apk might grant super user access after it's installed, but before that it's just like any other apk.
I'd appreciate it if someone could answer these questions. Thanks.

Anyone want to help me out? Doesn't seem like too hard of a question...

Id take a look at What is root access on google. It sounds like you have no idea about the basics. There is a ton of info for beginners even on this site. If I misunderstood you I apologize but your question would only leave me to believe you need to learn the basics. Good luck
Sent using the phone with the biggest balls....Atrix 4G

Gladroot doesn't give temporary root access either unless it changed.
Sent using the phone with the biggest balls....Atrix 4G

dupreeks said:
Id take a look at What is root access on google. It sounds like you have no idea about the basics. There is a ton of info for beginners even on this site. If I misunderstood you I apologize but your question would only leave me to believe you need to learn the basics. Good luck
Sent using the phone with the biggest balls....Atrix 4G
Click to expand...
Click to collapse
Well I'm definitely a beginner, but not that beginner. I'll show you what I'm talking about:
Code:
rem If we do, since we need to run several commands as root, use psneuter to
rem temporarily root the device.
echo.
echo Obtaining temporary root access...
%~dp0adb push %~dp0bin\psneuter /tmp/psneuter > NUL 2>&1
if not errorlevel 0 set message=Unable to send psneuter. && goto abort
set retval=
for /f "tokens=*" %%l in ('%~dp0adb.exe shell "/bin/chmod 6755 /tmp/psneuter > /dev/null 2>&1 && echo PASS"') do set retval=%%l
if "%retval%" neq "PASS" set message=Unable to chmod psneuter. && goto abort
set retval=
for /f "tokens=*" %%l in ('%~dp0adb.exe shell "/tmp/psneuter > /dev/null 2>&1"') do set retval=%%l
if "%retval%" neq "" set message=Unable to execute psneuter. && goto abort
echo.
echo Waiting for root access to kick in...
timeout /t 5 /nobreak > NUL 2>&1
So what I said was correct. GladRoot definitely get's temp root access. After it does that, it changes some settings and installs superuser.apk:
Code:
rem Remount the /system read/write.
echo.
echo Mounting /system as read/write...
%~dp0adb.exe shell mount -o rw,remount /dev/block/mmcblk0p12 /system > NUL 2>&1
rem Install sqlite3 for additional system changes required later in the script.
rem This is silent because it shouldn't interfere with anything even if it's
rem not used.
%~dp0adb.exe push %~dp0bin\sqlite3 /system/bin > NUL 2>&1
%~dp0adb.exe shell chmod 6755 /system/bin/sqlite3 > NUL 2>&1
echo.
echo Ready to root.
echo.
pause
rem Let's root!
rem Check for duplicate busybox installation and remove it.
echo.
echo Cleaning up SuperOneClick mess...
%~dp0adb.exe shell "find /system/xbin -type l | xargs rm" > NUL 2>&1
%~dp0adb.exe shell rm /system/xbin/busybox > NUL 2>&1
rem Copy su over and set permissions for use.
echo.
echo Rooting your device ...
%~dp0adb.exe push %~dp0bin\su /system/bin > NUL 2>&1
%~dp0adb.exe shell chmod 6755 /system/bin/su > NUL 2>&1
rem Install the Superuser app for allowing other apps root access.
echo.
echo Installing Superuser app...
%~dp0adb.exe install -r %~dp0bin\Superuser.apk > NUL 2>&1
echo.
echo Root complete.
echo.
So again my question is why do you need temp root access to install superuser.apk?

Temp root access is needed because superuser is installed in system/apps in the system partition. Without root a user does not have read write permissions in the system partition. This means a user cannot uninstall apps or install apps with out root permission. Temp access allows a script or person to modify the system partition, in this case it gives apps access to permanent root. The source code for psneuter is here.

on21st said:
Temp root access is needed because superuser is installed in system/apps in the system partition. Without root a user does not have read write permissions in the system partition. This means a user cannot uninstall apps or install apps with out root permission. Temp access allows a script or person to modify the system partition, in this case it gives apps access to permanent root. The source code for psneuter is here.
Click to expand...
Click to collapse
Yeah that pretty much sums it up. Gladroot was and still is my method of root. I wish I could unlock the boot loader with my current 1.8.3 setup I have and not lose anything. If anyone has a solution I would really appreciate it. I like my phone how it is but want to be able to make nand backups basically. I am not huge on CM7 and it doesn't seem like there are many stable roms for the Atrix right now.

You can there should be a pudding for 1.8.3. I remember using it. It wipes data and allows you to unlock the boot loader if you choose. HERE
Just choose the correct sbf to download and then follow instructions in thread.

I somehow got root

Using this
I let it run twice, and now it works great... weird.

running 2.3.4/4.5.621?

sd_shadow said:
running 2.3.4/4.5.621?
Click to expand...
Click to collapse
Seriously need root back on my phone. Is this build 4.5.621 on android 2.3.4?????
I had to get warranty replacement, and replacement is upgraded!!!!!!
Please let me know.
Sent from my DROID2 using Tapatalk 2

I tried the same thing you said you did and got nothing. which build version are you on? im on this god forsaken .622 on the r2d2 and nothing will work for root. if anyone has heard any news about accomplishing it please let me know

I Tried it a bunch of times on .621 and could not obtain root.
Data:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
$ su
su: permission denied
$ /system/xbin/su
/system/xbin/su: not found
$ mount -o remount,rw /dev/block/mtdblock3 /system
if [ -e /data/local/12m.bak ];
mount: Operation not permitted
$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
exit
$ exit
(success)
> mv /data/local/12m /data/local/12m.bak
(success)
> ln -s /data /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
> exit
> exit
$ su
mount -o remount,rw /dev/block/mtdblock3 /system
su: permission denied
$ /system/xbin/su
/system/xbin/su: not found
$ mount -o remount,rw /dev/block/mtdblock3 /system
if [ -e /data/local/12m ];
mount: Operation not permitted
$ if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
exit
$ exit
(success)
> mv /data/local/12m.bak /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
> exit
> exit
su
/system/xbin/su
$ su
su: permission denied
$ /system/xbin/su
/system/xbin/su: not found
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
$ exit
(success)
> mv /data/local.prop /data/local.prop.bak
> echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
> echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
$ mv /data/local.prop /data/local.prop.bak
failed on '/data/local.prop' - Permission denied
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
$ echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ exit
(success)

Yeh that's about all anyone is going to get until a dev figures out the sbf now that it has finally been leaked
*alarmed sputter* from R2D2

I really don't know how it happened. Like, at all. But... it works now '
Sent from my DROID2 using xda premium

i doubt it
i doubt you got root on .621/.622

I had it working until the data wipe I did today. Will report back with this attempt here.
No updates available, managed to get wifi tether for root users and ultimate backup to work properly. Trust me, I had it.
It looks like something about having it already rooted originally may help me here. Weird...

Here, have some video proof:
http://www.youtube.com/watch?v=5iwcwoa6Vx0

possible
Before i mistakenly downgraded i did have root on the update. But if you wipe completly then you will lose root forever (untill root is found)

When I first got the update, I had my SU and such icons, but it wasn't actually rooted. Ran the script, it's rooted now... weirdness, man.

I hope someone figures this out soon this phone sucks as totally stock.

That's what mine was!
Also, I did a /data wipe, no problems.
Sent from my DROID2 using xda premium

mewshi said:
That's what mine was!
Also, I did a /data wipe, no problems.
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Were you on .629?? Cause i need help with .629

seb559e said:
Were you on .629?? Cause i need help with .629
Click to expand...
Click to collapse
Would you mind paying a modicum of attention? Good lord, this isn't even the D2G forum.

[Q] About root Motorola RAZR 201M(XT902)

Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...

Sorry buddy. Nothing works. We 201m users are SOL.

Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/

Thanks Paul!
No luck with that either. Appreciate the feedback, however.

I hope somebody will study the XT902 root.

goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!

Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)

root
help!!!

Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
　・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
　・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
　・Superuser.apk（in the above downloaded）
　・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
　（色々表示されるので↓が出る間で待つ）
　Unlocked LSM.
　Do setresuid...
　OK.
　[email protected]:/data/local/tmp #
　（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!

I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.

Thank u!
thank u so much.!1

sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step

Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!

Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.

sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.

could u provide more friendly filehost?
i can't find the download button there

Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.

Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.

Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help

kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4

[Q] Help with EFS restore

Hello,
I have a verizon note 3 with mi9
I rooted via kingo and tried to back up my efs via:
http://forum.xda-developers.com/showthread.php?t=2447342
basically I forgot to install busybox, the process did not work, the script modified my phone's files but i'm not exactly sure which ones
for example in the phone directory i dont have files in /efs (http://www.note2forum.com/forum/gal...dden-menu-dialer-verizon-galaxy-note-3-a.html)
i wanted to enable the Hidden Menu (Dialer) on Verizon Galaxy Note 3.
So I have unrooted via Kingo app now. And I did a factory reset. I still do not see any files in the /efs folder on the phone
I want to know what I should do to fix the EFS files.
My phone still works to make calls and have internet, but I'm afraid to do anything further.
Thank you in advanced

You can't see efs without a root browser. Unlikely there ever was an issue.
Sent from my SM-N900V using xda app-developers app

akellar said:
You can't see efs without a root browser. Unlikely there ever was an issue.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Thanks, okay I rerooted the phone. I am using ES file explorer and I can see alot of files in the folder efs/ now. I'm guessing they are all there since my phone seems to still work.
anyways below is what the script I was using was doing, maybe someone can explain whats going on, and confirm stuff didn't get deleted. I have no idea whats going on there.
:BACKUP
CLS
 @ECHO *****************************************
 @ECHO * BACKUP EFS *
 @ECHO *****************************************
CHOICE /C YN /M "WARNING: Do you wish to Continue? (This will make EFS BACKUP)"
IF ERRORLEVEL 2 GOTO MENU
 @ECHO --- STARTING ----
 @ECHO --- WAITING FOR DEVICE
bin\adb wait-for-device
 @ECHO --- Backup efs image ---
bin\adb shell "echo | getprop > /sdcard/getprop.txt"
bin\adb pull /storage/sdcard0/getprop.txt
bin\adb shell "echo | getprop ril.product_code > /sdcard/version.txt ; getprop gsm.version.baseband >> /sdcard/version.txt ; getprop ril.serialnumber >> /sdcard/version.txt"
bin\adb pull /sdcard/version.txt
setlocal enabledelayedexpansion
for /f "tokens=*" %%a in (version.txt) do set "var=!var!%%a_"
echo %var%
bin\adb shell su -c "make_ext4fs -s -l 20M /sdcard/efs.img /efs"
bin\adb shell su -c "dd if=dev/block/mmcblk0p3 of=/sdcard/%var%EFS.raw.img"
bin\adb shell su -c "busybox tar cZvf /sdcard/%var%EFS.tar.gz /efs"
bin\adb pull /sdcard/efs.img
bin\adb pull /sdcard/%var%EFS.raw.img
bin\adb pull /sdcard/%var%EFS.tar.gz
bin\tar.exe -c efs.img >> %var%EFS.tar
bin\md5sum.exe -t %var%EFS.tar >> %var%EFS.tar 2>nul
REN %var%EFS.tar %var%EFS.tar.md5
bin\7za.exe a %var%EFS.zip %var%EFS.tar.md5 %var%EFS.raw.img %var%EFS.tar.gz getprop.txt
del *.img *.txt *.gz *.md5
 @ECHO -
 @ECHO -
 @ECHO Finished. Output file is %var%EFS BACKUP
) ELSE ( @ECHO "ERROR: PACKAGING does not exist" )
pause
goto MENU

ROOT-ing a phone with a broken screen / adbkey.pub problems

Hello, so.. Before, my problem was about getting adb to work in recovery, which someone told me to install TWRP, that worked, and I got USB Debugging turned on.
Now, I seen that I need to root my phone, so I can push the adbkey.pub to data/misc/adb/adb_keys..
I tried pushing adbkeys.pub there already (without root, in recovery), and the phone still wants me to press ok, when the prompt of the RSA key pops up.
Have TWRP, ADB works when phone is in Recovery..
Phone not ROOT-ed. Which might be my problem..
USB Debugging works
adbkey.pub has been sent to data/misc/adb/adb_keys around 3 times
Generated new adbkey.pub already..
The things I did:
adb shell mount /system
abd shell
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
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
exit (Exited out of adb shell)
adb push adbkey.pub /data/misc/adb/adb_keys
I had copied adbkey.pub to the adb folder.
Again, like I said in my last thread, I don't care about losing data. Flashing stuff would not be a problem with me.
If you are wondering, I am using windows.
EDIT: Regenerated another adbkey... The key is actually differient this time.. Will go into TWRP and push this key.

Has it worked with another key?
Stuck in the same situation at the moment.