Database Users

Unable to Re-Root Droid 2 after Gingerbread OTA

Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker

Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?

Hope somebody comes up with an answer - same thing happened to me.

did you use the d3 root method? thats the only one that works 100% on gingerbread.

Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.

SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni

Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.

Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!

My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?

Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.

I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================

drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.

This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!

Awesome! Thanks!

Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!

Awesome!
Thanks! This worked for me as well! (after additional reboot)

Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.

Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew

awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer

It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.

Market wont work on rooted kindle

Not sure what is going on. I rooted the fire, install vendor.app and framework. I open market it has a difficult time with my gmail.account but after a few tries it authenticates successfully. At this point it tries opening the market and fails. I've tried reinstalling, revolting.
I will say that I have not tried root explorer as I cannot understand how to install it (amazon denies my purchasing it since it is not compatible with my device)
Could it be a rights issue? If I need root explorer how can I get it?
Sent from my Kindle Fire using Tapatalk

sideload dat ****

Maybe you should try another version of vending.apk and sideload the root explorer into your fire rather than getting it from amazon.
Then i guess you might need to use the root explorer to modify the permission of vending.apk to rw-r--r--

Easiest fix for this is downloading the Kindle Fire Utilities:
http://forum.xda-developers.com/showthread.php?t=1399889
And once in, go to extras and install google hulabaloo.

http://forum.xda-developers.com/showpost.php?p=20240542&postcount=8

I had so much trouble with the market and other versions of Vendor.apk myself on the stock KF rom and no matter what I did, I ended up with similar issues. Setting permissions isn't really hard at all (most require a chmod 644, which is user/owner read + write, all others just read), and I actually did get it to work just once before having to restore a backup because I screwed something completely unrelated up . If you keep at it, there's a good chance you'll get it right eventually, but I just installed CM7 and couldn't be happier.

I also had trouble at first but I found this videos method to work flawlessly and easily.
http://www.youtube.com/watch?v=rTkegVrnAvA

I got it to work. Hopefully this works for you as it was frustrating for me to have so many problems.
http://forum.xda-developers.com/showthread.php?t=1450232

You are all awesome in my book!!! Thank you. I will keep at it and not give up.
Sent from my Kindle Fire using Tapatalk

success!!! thanks again

Kindle Fire HD 7.2.3

Hi,
I just received Update 7.2.3 I am wondering what could have changed. There is now changelog so far on amazon.com

dang this is a real cat n mouse game going on with amazon. i've been trying to catch up on how i can root my brand new kfhd7 and another update pops up before i even finish reading everything within 24 hours of owning it. is there no way to flash a custom recovery with a fastboot cable?

Thanks for the update. I disabled some files. Let's see if it prevents 7.2.3 from unrooting my device.
Sent from my SPH-L710 using xda premium

have u lost ur root after received the updates?

Yeah i lost my root - but i got it back after rooting it again
just use "Root_with_Restore_by_Bin4ry_v17" and take option 1.
still wondering if there's something new about the update..

Already up?
Already updated?
That to fix what is wrong, what? Or, in order to increase store sales Guernsey
First by a firewall blocking the update, but it can feel a little slow.
7.2.3 and re-routing, just one worry.
Backup routing state does not know, then here too bulletins see I'll have to.
All Merry Christmas

viro18 said:
Yeah i lost my root - but i got it back after rooting it again
just use "Root_with_Restore_by_Bin4ry_v17" and take option 1.
still wondering if there's something new about the update..
Click to expand...
Click to collapse
I have my Kindle Fire HD 7.2.2 and I tried the root and I get so far until
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop "Permission Denied" Does the Root_with_Restore_by_Bin4ry_v17 work?
Because I get this too
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Even after this it asks to reset data on my Kindle I let it reboot and it fails

Khasar2012 said:
I have my Kindle Fire HD 7.2.2 and I tried the root and I get so far until
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop "Permission Denied" Does the Root_with_Restore_by_Bin4ry_v17 work?
Because I get this too
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Even after this it asks to reset data on my Kindle I let it reboot and it fails
Click to expand...
Click to collapse
i did not even install andoird sdk just "Kindle Fire ADB drivers.exe" and killed "adb.exe" process in tasmanager before rooting my device^^

Khasar2012 said:
I have my Kindle Fire HD 7.2.2 and I tried the root and I get so far until
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop "Permission Denied" Does the Root_with_Restore_by_Bin4ry_v17 work?
Click to expand...
Click to collapse
Yup, that is as far as I get too. No one has been able to help me get past this.

Ravynmagi said:
Yup, that is as far as I get too. No one has been able to help me get past this.
Click to expand...
Click to collapse
You guys are using the wrong root method, that one doesn't work anymore. use this one: http://forum.xda-developers.com/showthread.php?t=1886460
choose option 1.

jmandawg said:
You guys are using the wrong root method, that one doesn't work anymore. use this one: http://forum.xda-developers.com/showthread.php?t=1886460
choose option 1.
Click to expand...
Click to collapse
The other thread recommended that as the first step, and then the older qemu method as the second step. So I tried both. And both run into permission denied errors.

First I wanna say when I first got my kindle fire HD 7" I rooted it having 7.2.1 on it.. Amazon pushed the 7.2.2 update, and I lost root so I use Root_with_Restore_by_Bin4ry_v17, and used the normal option as he stated. Once that was done, the kindle was very slow and the screen was flickering and then I used qemuroot v1.0 as instructed and did option 1. It went thru its process and I regained root. I just now checked the kindle and saw 7.2.3 on there now. I went to Root_with_Restore_by_Bin4ry_v17 and chose normal option, and went thru the process and have regained root only by using Root_with_Restore_by_Bin4ry_v17. This was my scenario and excactly what I did each time.

I'm also getting permission denied errors no matter what guide I follow.

djr4x4 said:
First I wanna say when I first got my kindle fire HD 7" I rooted it having 7.2.1 on it.. Amazon pushed the 7.2.2 update, and I lost root so I use Root_with_Restore_by_Bin4ry_v17, and used the normal option as he stated. Once that was done, the kindle was very slow and the screen was flickering and then I used qemuroot v1.0 as instructed and did option 1. It went thru its process and I regained root. I just now checked the kindle and saw 7.2.3 on there now. I went to Root_with_Restore_by_Bin4ry_v17 and chose normal option, and went thru the process and have regained root only by using Root_with_Restore_by_Bin4ry_v17. This was my scenario and excactly what I did each time.
Click to expand...
Click to collapse
Re-rooting is the easy part. Rooting a new 7.2.2 or 7.2.3 seems to be the PITA.

Ravynmagi said:
Re-rooting is the easy part. Rooting a new 7.2.2 or 7.2.3 seems to be the PITA.
Click to expand...
Click to collapse
It would be interesting to see if those who are having difficulty rooting 7.2.2 received their KFHD with 7.2.2 preloaded. I bought my KFHD 7" the first day of availability, never rooted it before, but was able to cleanly root it after it updated to 7.2.2.
I believe that it is possible that Amazon slipstreamed in a minor hardware change (that required the 7.2.2 firmware) that affects how the existing rooting methods operate.

Ravynmagi said:
The other thread recommended that as the first step, and then the older qemu method as the second step. So I tried both. And both run into permission denied errors.
Click to expand...
Click to collapse
Make sure you have the adb "composite" driver listed under the Kindle device in device manager. Otherwise you have the wrong adb driver and this won't work.

Xyth said:
Make sure you have the adb "composite" driver listed under the Kindle device in device manager. Otherwise you have the wrong adb driver and this won't work.
Click to expand...
Click to collapse
I just double checked, says Kindle Fire, then Android Composite ADB Interface, right below it. It always shows up just fine in adb devices.
I just did a factory reset, will start over and give it a few more tries tonight.
---------- Post added at 10:27 PM ---------- Previous post was at 10:13 PM ----------
Well what do you know. It decided to work today. Don't think I did anything different (other than not trying a factory restore earlier).

Try running the first stage twice if you're getting permission errors. was able to root 7.2.3 by running option 1 twice back to back, no Qemu needed.

Anyone know of a temp root method for this?

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
demoncamber said:
Anyone know of a temp root method for this?
Click to expand...
Click to collapse
What exactly do you mean by "temp root method"?
You can Unroot after Root if that is what you want to do. What are you trying to accomplish?

[1/16/2015][Root]Asus MeMo Pad (ME176CX)[Root]

Working Root Method For your Memo Pad 7
1. Extract the File from http://www.mediafire.com/download/lp7ngv5l6vm5lin/AsusIntelRootKit.zip
2. Have Debugging Mode Enable (Setting>About>Software Information>7 Clicks on the Build Number)
Back to Settings>Developer Options and select USB DEBUGGING
3. Open the extracted folder and click "Root" (Follow the instructions)
Your Rooted
Dont update the superuser app!!!!
Install Busybox from the play store
Install and Reboot
Check with root checker
ADB Driver for Asus http://www.mediafire.com/download/u46c7zwf2k2xjr8/AsusADBdrivers.zip

JarrelStudios said:
Working Root Method For your Memo Pad 7
1. Extract the File from http://www.mediafire.com/download/lp7ngv5l6vm5lin/AsusIntelRootKit.zip
2. Have Debugging Mode Enable (Setting>About>Software Information>7 Clicks on the Build Number)
Back to Settings>Developer Options and select USB DEBUGGING
3. Open the extracted folder and click "CheckBeforeActivation" (Follow the instructions)
4. When Device Restarts unlock screen and go back to the same folder and click Root....
Your Rooted
Dont update the superuser app!!!!
Install Busybox from the play store
Install and Reboot
Check with root checker
ADB Driver for Asus http://www.mediafire.com/download/u46c7zwf2k2xjr8/AsusADBdrivers.zip
Click to expand...
Click to collapse
Thanks for the completely bland and incorrect Guide! Nowhere in that ZIP archive is a file called "CheckBeforeActivation". With many hundreds of thousands of these devices in the marketplace, do your fellow XDA members and GET YOUR FACTS STRAIGHT BEFORE YOU POST!!!:silly:

The file was removed as it was it copy of another file
Sent from my K013 using XDA Free mobile app

This method works on my zenfone 4 where else fail using fastboot zip file method

Thanks for posting this!

how come you cant update supersu??

I tried this method to root my device, I have a BBY build. The application says it rooted okay. When I reboot the device and try to install BusyBox it says it doesn't get a response from the device. When I check root with Root Checker Basic it says that the device is not rooted. Any thoughts on what I might be missing?

Is the super user app installed?
Sent from my K013 using XDA Free mobile app

yay, i am now rooted, thankyou for an easy way to do this..
a few questions..
1..how come i cant update the supersu, and how can i prevent this from happening..
2..can i now uninstall the busybox app as its now downloaded the files to the device..
3, is it now safe to uninstall all the asus rubbish on the tablet(what have you uninstalled)

Memo Pad 7 ME572C:
after the latest update 11.8.3.31 (from 11.8.3.30), this root method and the rootzenfone method can no longer root the tablet.

slim_thumb said:
Memo Pad 7 ME572C:
after the latest update 11.8.3.31 (from 11.8.3.30), this root method and the rootzenfone method can no longer root the tablet.
Click to expand...
Click to collapse
Ahh, thanks for this. What I was looking for. I did the update, and now regretting it lol.

I would also like to know why we can't update SuperUser

onimorza said:
I would also like to know why we can't update SuperUser
Click to expand...
Click to collapse
its safe to update it now..before it would remove superuser and you would have to factory reset the re-root

To the OP, it looks like you just reposted the work of twenty-three pin from here:
https://translate.google.de/transla...sts/247110-merry-christmas&edit-text=&act=url
Too bad when you were stealing someone else's work you didn't work slowly enough to notice that he mentions that the Asus 572C should use V2 of his work:
http://www.mediafire.com/download/ui9ipe786dulj98/AsusIntelRootKitv2.zip
Hope this helps someone.

If you check the commands int the .bat file, you will see they are different... Its just basic fastboot commands. And as of recent updates the me572 can't be rooted using this method. So I'll head back to the drawing board as soon as I get time to
Sent from my K013 using XDA Free mobile app

I honestly haven't seen that post before
Sent from my K013 using XDA Free mobile app

JarrelStudios said:
its safe to update it now..before it would remove superuser and you would have to factory reset the re-root
Click to expand...
Click to collapse
Thanks, but meanwhile I've rooted with this method http://forum.xda-developers.com/memo-pad-7/help/rooting-memo-pad-7-rootzenfone-t3000389 and also updated without problem.
Also no need for ADB with that method.

question
abudabu said:
Ahh, thanks for this. What I was looking for. I did the update, and now regretting it lol.
Click to expand...
Click to collapse
Will this work for ASUS 16GB 8" IPS HD Android Tablet, 1.33GHz Intel Bay Trail-T Z3745 quad-core processor, with kit kat 4.4?
(ME180A-A1-WH)
zach

any method of rooting on stock LP?

will this work with latest WW_K013-12.10.1.33-20150917 ? Lolipop 5.0

Rooting Producedure

Anyone tried rooting Pixel XL and how does it works after rooting ? Reviews

Everything works fine here

Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.

AstroDigital said:
Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.
Click to expand...
Click to collapse
I mean is there any bootloop or something and how is everything working any lagging or somethjng

Huzaifaamirka said:
I mean is there any bootloop or something and how is everything working any lagging or somethjng
Click to expand...
Click to collapse
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go

Working fine with ElementalX kernel and root.

hutzdani said:
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go
Click to expand...
Click to collapse
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan

trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
With USB Debuiing enabled open your ADB terminal and type :
"adb shell"
"su"
"mkdir /su/etc; cp /system/etc/hosts /su/etc/hosts; echo "#!/su/bin/sush\nmount -o bind /su/etc/hosts /system/etc/hosts" > /su/su.d/50adaway; chmod 0700 /su/su.d/50adaway"
After this reboot your device and apply ad blocking hosts with the latest ad away build

Thank you for the info!
I wonder if there are plans to update adaway so this procedure will not be needed..
Thanks again great detail
Bryan
Sent from my SM-N900V using XDA-Developers mobile app

Wrong sub forum.

trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
All you have to do is download the 3.2 Dev preview build and enable systemless mode in preferences. Works like a charm.
https://www.androidfilehost.com/?fid=312978532265366394

That's great so with version 3.2 dev no adb procedure is needed?