Database Info

[Q] gramin asusM10 Eglish Rom How to update?

◎Summary：
Welcome to use Garmin-Asus nuvifone M10 updating firmware. You would use this updating program
to update the latest newly version of M10 internal firmware (Firmware and modem). So this will enhance
the M10’s stability and make its performance better. Read the following introduction carefully before
updating.
◎Firmware and Modem Version：
Firmware Version: Garmin-Asus M10_V6.15.0_WWE
Modem Version: V4.7.8-Q2
◎Updating program supports following operation system：
Windows 2000、Windows XP、Windows Vista、Windows7 edition
◎Attention：
1. In order to maintain the computer’s stability and avoid upgrade failures, please close all running programs
before upgrading.
2. Firmware upgrade will erase all data in your device. Use Backup utility to backup your data before starting
update.
((((((3. Do not upgrade your device with the firmware of another language or region.)))))
4. Do not remove the USB cable while upgrading.
5. Make sure M10 is with enough power. Keep the unit turned on.
6. Download updating program nuvifone_M10_V6.15.0_WWE on desktop or PC.
7. Follow below procedures to run updating program.
◎Procedure:
1. Before you start, ensure that your device has at least 60% of battery power left then keep the device on and
turn off the firewall on your computer.
2. Use the USB cable to connect your device with a computer.
3. Ensure that ActiveSync 4.5 or later version for Windows 2000 and Windows XP or WMDC 6.1 or later version
for Windows Vista and Windows7 is installed in your computer.
4. Press Update to start updating.
5. In case of an upgrade failure – please keep USB connected to PC and re-execute firmware, following expert
mode to upgrade.
3 no is not update another region language then how to update English ROM in Italian phone

Teclast a11 tablet 4.1 jelly bean

¿do you know any procedure for root access for my teclast a11 4.1 jelly bean tablet?
i would like to root it. thanks

duendeskt said:
¿do you know any procedure for root access for my teclast a11 4.1 jelly bean tablet?
i would like to root it. thanks
Click to expand...
Click to collapse
Yes, I rooted my Teclast A11 4.1.1 tablet using the files and methods in this post:
Edit: As a new user I can't seem to post links.
I'll write it out instead.
blog dot sina dot com dot cn slash s slash blog_899fd55d01017nsb.html
Note: The site is in Chinese but google translate worked for me!
The root process was easy - the hard part was finding USB-drivers that worked with the tablet. After browsing through countless Chineese forums I got the advice to install an application called Moborobo. The software itself is quite buggy but the USB-drivers seems to work well.
On a different note - my A11 has a very annoying problem. The numbers in it's MAC address are separated by periods instead of colons. Is that the case with your tablet as well?
This makes the tablet unusable for some applications (i.e. Sonos Controller).
Good luck with your rooting!
Edit 2013-01-04: The latest update fixed my problem with the MAC address. You can get it here: http pan dot baidu dot com / share / link?shareid=147758&uk=489415757&third=0

How to get screen off during hdmi out?
I need to get my tablet screen off during hdmi out. It's kinda irritating and waste of battery with screen on during hdmi out. How to get the tablet off screen during hdmi out to tv?
My tablet (Teclast A11) with stock rom jelly bean 4.1.1 v1.11, dated 20121217.
The previous link you suggested only says N101 and teclast A10. Is A11 applicable too?

Alfred271 said:
I need to get my tablet screen off during hdmi out. It's kinda irritating and waste of battery with screen on during hdmi out. How to get the tablet off screen during hdmi out to tv?
My tablet (Teclast A11) with stock rom jelly bean 4.1.1 v1.11, dated 20121217.
The previous link you suggested only says N101 and teclast A10. Is A11 applicable too?
Click to expand...
Click to collapse
Can't help you with your screen off-problem (you may wanna look in to Tasker as it can do almost everything) but I have successfully rooted my A11 with the instructions in the first link. It's the same chipset so I gave it a go and it worked nicely. No guarantees though...

Verified successfully rooted teclast A11 dual core.
n'Anders said:
Can't help you with your screen off-problem (you may wanna look in to Tasker as it can do almost everything) but I have successfully rooted my A11 with the instructions in the first link. It's the same chipset so I gave it a go and it worked nicely. No guarantees though...
Click to expand...
Click to collapse
Step 1 : Download moborobo. Install it to your laptop/pc.
Step 2 : Download TPSparkyRoot-4.1.1Root.7z use winrar.
Step 3: Check all your resources. Inside [TPSparkyRoot-4.1.1Root] folder you should have:
1: RootExplorer.apk
2. SuperSu.apk
3. TPSparkyRoot.bat
Step 4: Switch on Teclast A11 (with more than 40% of battery) plug into microsd data cable. Wait for moborobo to detect and install tablet driver. Ignore typical windows that ask you for usb device driver. Eventually moborobo will do all the job to connect your tablet to pc.
Step 5: On tablet go to --> setting --> enable usb debugging mode. Click the check box next to it. [USB debugging mode]. Also set display to continuosly ON for 30 mins, to avoid sleep.
Step 6: Launch moborobo. Under --> Home. Click refresh to get your tablet connected.
Step 7: After tablet connected by moborobo. Go to App. Install RootExplorer.apk and SuperSu.apk
Step 8: Launch TPSparkyRoot.bat on your pc. Sit back and wait for tablet to restart.
[ you will get message : Rebooting - 1/3 : Continue once your device finishes rebooting]
Step 9: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : Rebooting - 2/3 : Continue once your device finishes rebooting]
Your tablet rebooting second time.
Step 10: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : uid - 0 (root) gid - 0 (root)
If the uid - 0 then continue (hit any key/enter) if not press control+c.
Suppose you will get uid-0 for both.
Finally done. You've successfully root your device. Enjoy!!
Note: You can check your root access by download "root checker" from google play store.

moborobo has no drivers/ not compatible
Alfred271 said:
Step 1 : Download moborobo. Install it to your laptop/pc.
Step 2 : Download TPSparkyRoot-4.1.1Root.7z use winrar.
Step 3: Check all your resources. Inside [TPSparkyRoot-4.1.1Root] folder you should have:
1: RootExplorer.apk
2. SuperSu.apk
3. TPSparkyRoot.bat
Step 4: Switch on Teclast A11 (with more than 40% of battery) plug into microsd data cable. Wait for moborobo to detect and install tablet driver. Ignore typical windows that ask you for usb device driver. Eventually moborobo will do all the job to connect your tablet to pc.
Step 5: On tablet go to --> setting --> enable usb debugging mode. Click the check box next to it. [USB debugging mode]. Also set display to continuosly ON for 30 mins, to avoid sleep.
Step 6: Launch moborobo. Under --> Home. Click refresh to get your tablet connected.
Step 7: After tablet connected by moborobo. Go to App. Install RootExplorer.apk and SuperSu.apk
Step 8: Launch TPSparkyRoot.bat on your pc. Sit back and wait for tablet to restart.
[ you will get message : Rebooting - 1/3 : Continue once your device finishes rebooting]
Step 9: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : Rebooting - 2/3 : Continue once your device finishes rebooting]
Your tablet rebooting second time.
Step 10: Your tablet successfully reboot. Hit enter or any key on your laptop/pc
[you will get message : uid - 0 (root) gid - 0 (root)
If the uid - 0 then continue (hit any key/enter) if not press control+c.
Suppose you will get uid-0 for both.
Finally done. You've successfully root your device. Enjoy!!
Note: You can check your root access by download "root checker" from google play store.
Click to expand...
Click to collapse
Teclast A11 is not compatible to moborobo (any Teclast is not supported regarding the moborobo compatibility list)
I have tried the whole procedure and always it stucks at installing internal moborobo drivers. So i had no success to root Teclast A11 until now.
There is no real root procedure available which works with Teclast A11.
Has anybody real success to root this device????? Please tell us all how you really done it by yourself.
Thank you very much in advance.
ghostworm

Worked for me
ghostworm said:
Teclast A11 is not compatible to moborobo (any Teclast is not supported regarding the moborobo compatibility list)
I have tried the whole procedure and always it stucks at installing internal moborobo drivers. So i had no success to root Teclast A11 until now.
There is no real root procedure available which works with Teclast A11.
Has anybody real success to root this device????? Please tell us all how you really done it by yourself.
Thank you very much in advance.
ghostworm
Click to expand...
Click to collapse
Well I don't know what to tell you - the drivers that came with Moborobo v2.0.7.501 was the only ones that worked for me. I originally had the Android SDK drivers but they didn't work for me with the Teclast A11. When I uninstalled those drivers and then installed Moborobo I could connect to the tablet.
Btw. I have Windows 7 64bit
Other than that I followed the steps outlined in the link on my first post and my tablet is now rooted.

n'Anders said:
Well I don't know what to tell you - the drivers that came with Moborobo v2.0.7.501 was the only ones that worked for me. I originally had the Android SDK drivers but they didn't work for me with the Teclast A11. When I uninstalled those drivers and then installed Moborobo I could connect to the tablet.
Btw. I have Windows 7 64bit
Other than that I followed the steps outlined in the link on my first post and my tablet is now rooted.
Click to expand...
Click to collapse
hmm i can see that Moborobo is buggy because it allows me now to connect to the teclast over wifi only but it still does not reconize the teclast as teclast a11 over usb, and after Moborobo try to connect, it wants to install drivers but it always stucks at 99% of driver installation. Never installed any driver...
i have win8 pro 64bit

Moboro
ghostworm said:
hmm i can see that Moborobo is buggy because it allows me now to connect to the teclast but it still does not reconize the teclast as teclast a11, and after Moborobo try to connect, it wants to install MoboMarket but it was always denied by the teclast itself, even when i download it manually and try to install.
BTW is it really necessery to install MoboMarket just to root the device???
Click to expand...
Click to collapse
I didn't use any of the Mobo*-applications, the only reason I installed it was the USB-driver.
I see that Alfred271 uses Moboro to install some apps on the tablet - I didn't do that. I only ran TPSparkyRoot.bat as outlined in my first link.
This is the google translated instructions i used (Note that they tested it on a different tablet than the A11 but they share chipset so I tried it).
"1 tablet is turned on
. shut down antivirus, 360 and other similar software download address: file name: TPSparkyRoot-4.1.1Root.7z
Tablet checked USB debugging, to allow the installation of third-party software
PC will be installing a pea pod-like functionality software, connect the USB installation drive
Directly run TPSparkyRoot.bat 6.
Note: In step six. Tablet restart three times, each time you restart Ends need to unlock boot into the desktop, press any key to come back to the computer terminal to the next step.
Test platform:
The original road N101 dual engine 2
Taipower A10 dual-core"

n'Anders said:
I didn't use any of the Mobo*-applications, the only reason I installed it was the USB-driver.
I see that Alfred271 uses Moboro to install some apps on the tablet - I didn't do that. I only ran TPSparkyRoot.bat as outlined in my first link.
This is the google translated instructions i used (Note that they tested it on a different tablet than the A11 but they share chipset so I tried it).
"1 tablet is turned on
. shut down antivirus, 360 and other similar software download address: file name: TPSparkyRoot-4.1.1Root.7z
Tablet checked USB debugging, to allow the installation of third-party software
PC will be installing a pea pod-like functionality software, connect the USB installation drive
Directly run TPSparkyRoot.bat 6.
Note: In step six. Tablet restart three times, each time you restart Ends need to unlock boot into the desktop, press any key to come back to the computer terminal to the next step.
Test platform:
The original road N101 dual engine 2
Taipower A10 dual-core"
Click to expand...
Click to collapse
Ok problem solved
the main problem was Windows 8 !!!!!
I tried it on Windows 7 PC and everything worked well, thank you very much...
:good:

Hi all now i have bought another Teclast A11 with Quad-Core CPU, brand new model with much more power.
The name of the product is the same but the ID is different, before it was "D5S7" and the new is "M5A7". So can i use the same rooting files for???
Thanks in advance
Ghostworm

ghostworm said:
Hi all now i have bought another Teclast A11 with Quad-Core CPU, brand new model with much more power.
The name of the product is the same but the ID is different, before it was "D5S7" and the new is "M5A7". So can i use the same rooting files for???
Thanks in advance
Ghostworm
Click to expand...
Click to collapse
That's unlikely to work as the tablets doesn't share chipset or GPU.

Identify tablet
Hi,
I've bought a generic branded tablet, its make/model is "Hi-Level HLV-T1001W".
It is just like the Teclast A11, say, both of them are the same.
If it is not removed before you see, here is a link of product details: http://www.kare.com.tr/?cmd=UrunDetay&StokNo=28543
i think there is enough english words to understand the page, most of the descriptions are in universal english
I want to root this device. But I'm not sure which rooting procedure is appropriate for this device.
My questions:
How can I compare the firmwares of these devices, and sure they are same each other?
Can/should I use the files and procedure defined in this thread for rooting?
Thanks,
A11: http://www.teclast.org/teclast-a11-dual-core-rk3066-android-4-1-jelly-bean-10-1-inch-ips-16gb.html

atakatas said:
Hi,
I've bought a generic branded tablet, its make/model is "Hi-Level HLV-T1001W".
It is just like the Teclast A11, say, both of them are the same.
If it is not removed before you see, here is a link of product details: http://www.kare.com.tr/?cmd=UrunDetay&StokNo=28543
i think there is enough english words to understand the page, most of the descriptions are in universal english
I want to root this device. But I'm not sure which rooting procedure is appropriate for this device.
My questions:
How can I compare the firmwares of these devices, and sure they are same each other?
Can/should I use the files and procedure defined in this thread for rooting?
Thanks,
A11: http://www.teclast.org/teclast-a11-dual-core-rk3066-android-4-1-jelly-bean-10-1-inch-ips-16gb.html
Click to expand...
Click to collapse
They do look very similar (apart from your tablet having bluetooth) but it's still hard to be sure it will work.
If you're thinking about rooting using the files I linked to I would recommend making sure it has a Rockchip RK3066 chipset.
I'd imagine that the Rockchip batch tool will correctly identify the chipset (and possibly the firmware) for you.
Good luck!

n'Anders said:
They do look very similar (apart from your tablet having bluetooth) but it's still hard to be sure it will work.
If you're thinking about rooting using the files I linked to I would recommend making sure it has a Rockchip RK3066 chipset.
I'd imagine that the Rockchip batch tool will correctly identify the chipset (and possibly the firmware) for you.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply.
It has a Rockchip RK3066 chipset as far as I know from the specifications.
I will give it a try after re-checking with some hardware tools.
So, what is the worst scenario if it is not suitable for my device? Brick it or something like a better case that I can recover it?

atakatas said:
Thank you for your reply.
It has a Rockchip RK3066 chipset as far as I know from the specifications.
I will give it a try after re-checking with some hardware tools.
So, what is the worst scenario if it is not suitable for my device? Brick it or something like a better case that I can recover it?
Click to expand...
Click to collapse
I have read about people that was able to restore their seemingly dead tablets through the Rockchip batch tool but I have (luckily) no experience in that department...

Thank you for your advices.
I think, "Rockchip batch tool" is the best starting point in my case. I found some tutorials on firmware update in other forums, I'll try them later. For now, I can go with it unrooted.

ROM
Hi,
Would any one recommend a good Custom ROM for my Teclast A11? I run on the stock ROM which worked fine till Sunday after which it crashed and i updated with a firmware which is not stable either.
Regards

hello guys, i downloaded the original firmware from:
http://www.teclast.com/tools/pad/putcode.html
just write down your id, it is back on the case.

How to Root and avoid bricking
For those that have an Teclast A11 Dual Core and Quad Core M5A7 I've pass my two last days to make experiments.
I've landed in a Root procedure easy to use, and I have discover how to Unbrick in case of failure of Root.
I'll hope you apreciate the guides. It's took a lot of time to write down them all.
How to Root Teclast A11 Dual Core and Quad Core with Android 4.1.1
How to Unbrick Teclast A11 Quad Core M5A7
How to Update firmware to Android 4.2.2
Sorry for my English, I'm Italian.
Have a nice day.

Rooting the ASUS Memo Pad HD 7 (ME173x)

Hi all,
yesterday I succeeded in rooting the new ASUS MeMo Pad HD 7.
Model-Number: ME173X
Android version: 4.2.1
Kernel version: 3.4.5
HD 7 Build: ME173X_WW_User_4.2.1.75146_20130523 release keys
PC operating system: Win.. XP
USB-Driver I used (but there's WdfCoInstaller.dll missing, which I already had on my PC):
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME172V/ASUS_Android_USB_drivers_for_Windows_20130415.zip
Maybe this more complete package would work, too (I didn't try that):
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/ASUS_Android_USB_drivers_for_Windows.zip
Method to root is by using motochopper.
You can follow the next steps in general as described in
http://forum.xda-developers.com/showpost.php?p=40129120&postcount=1
One important thing:
motochopper didn't recognize my HD7 at once, so I did the following
(while being connected with PC via USB and motochopper waiting for device):
While USB debugging activated, go to USB settings an connect it as
integrated CD drive. motochopper will automatically recognize it
and continue with rooting process.
And last but not least:
As always, all you do is your own risk and I'm not responsible for any damage.
Good luck
-----------------------------
EDIT 2013-07-06:
Above procedure for rooting works with the new HD7 update, too (but you have to re-root after the update).
Build version after the update: ME173X_WW_user_4.2.2.51129_20130619 release-keys
-----------------------------
Description for Linux users:
- use motochopper package from link above
- login as root
- extract package
- open console and change to directory where you extracted the package
- chmod +x adb.linux
- chmod +x run.sh
- Check your HD7 will be recognized:
-> ./adb.linux status-window
-> shows "State: unknown"
-> connect HD7 (with usb debugging enabled, connecting as MTP device)
-> above started adb command should show now "State: device"
-> HD7 recognized - greatful, you're ready
-> press Strg-C to abort
- (optional) for more information about your HD7 you can enter: ./adb.linux devices -l
-> this should show something like: D6OKCXXXXXXX device usb:1-3 product:WW_memo model:ME173X device:ME173X
- ./run.sh
-> follow instructions on screen
- you're done
-----------------------------
EDIT 2013-07-16:
Above procedure for rooting works with new HD7 update (but you have to re-root after the update).
Build version after the update: ME173X_WW_user_4.2.2.91525_20130711 release-keys

Thank you very much! I had it attached as a camera, worked fine as well. ^^

ASUS memopad HD 7
quaddler said:
Hi all,
yesterday I succeeded in rooting the new ASUS MeMo Pad HD 7.
Click to expand...
Click to collapse
Thats awesome, but how did you already purchase this when it hasnt hit the stores yet? I cant wait to replace my MSI Winpad with this bad boy

RELLC said:
Thats awesome, but how did you already purchase this when it hasnt hit the stores yet? I cant wait to replace my MSI Winpad with this bad boy
Click to expand...
Click to collapse
Amazon.de apparently received an early batch and sent them out immediately. I was surprised as well, target date was 10 July to 1 August and it arrived 25 June^^

SoWhy said:
Amazon.de apparently received an early batch and sent them out immediately. I was surprised as well, target date was 10 July to 1 August and it arrived 25 June^^
Click to expand...
Click to collapse
sooo jealous. :highfive:

SoWhy is right.
I bought mine last Thursday at amazon.de.
There were also some dealers on Amazon‘s marketplace who had some.

hi
it is possible to enable usb host with the root on the memo pad hd 7?

Memo Pad HD7
Thanks...
Have been looking for Root ever since I got one Device on Friday.
Root seems to be working fine.
By the way - Saturn Germany got stock now as well (blue and white back) - bought 3 more today.
The MircoSD is taking 32GB straight from my Galaxy Note 10.1 - the resolution is really cool and no errors or problems.
I personally can do no more than highly recommend the Tablet.
Change - just made a firmware update to 4.2.2 - root is gone...

Sky0ne said:
Change - just made a firmware update to 4.2.2 - root is gone...
Click to expand...
Click to collapse
Thanks for reporting that.
Do you mean that rooting is no more possible with 4.2.2 firmware?
Current version 4.2.1 is somewhat buggy. Launcher FC quite often. It would make sense to download 4.2.2 but it would be unusable for me without root

LaizyJumper said:
Thanks for reporting that.
Do you mean that rooting is no more possible with 4.2.2 firmware?
Current version 4.2.1 is somewhat buggy. Launcher FC quite often. It would make sense to download 4.2.2 but it would be unusable for me without root
Click to expand...
Click to collapse
Well, I wouldn't say not possible. It's just that I couldn't manage to get it done de same way so far.
The 4.2.2 update is pretty neat. The tablet works more stable now. The home screen rotates and the display is much brighter.
Just some update features I discovered.
As of root I was hoping that someone would discover some different, more stable way - like CF-Autoroot on the Nexus 7.

I‘m a little busy at the moment.
Hope to have a look on 4.2.2 on weekend.

Sky0ne said:
Well, I wouldn't say not possible. It's just that I couldn't manage to get it done de same way so far.
The 4.2.2 update is pretty neat. The tablet works more stable now. The home screen rotates and the display is much brighter.
Just some update features I discovered.
As of root I was hoping that someone would discover some different, more stable way - like CF-Autoroot on the Nexus 7.
Click to expand...
Click to collapse
Does it show the Android version 4.2.2 in System information? Or is it still 4.2.1 (and it says ME173X_WW_user_4.2.2.51129_20130619 in build number)?
I have Android version 4.2.1 and build number mentioned above. And I got it rooted without any problems on Linux (the way it is described in OP).

LaizyJumper said:
Does it show the Android version 4.2.2 in System information? Or is it still 4.2.1 (and it says ME173X_WW_user_4.2.2.51129_20130619 in build number)?
I have Android version 4.2.1 and build number mentioned above. And I got it rooted without any problems on Linux (the way it is described in OP).
Click to expand...
Click to collapse
Funny - you're right... :laugh: Didn't see that one.
Got exactly the same build no (ME173X_WW_user_4.2.2.51129_20130619 release-keys) and above Android Version 4.2.1...
I am running Linux too - couldn't make root so far - did you use some different settings?

Sky0ne said:
Funny - you're right... :laugh: Didn't see that one.
Got exactly the same build no (ME173X_WW_user_4.2.2.51129_20130619 release-keys) and above Android Version 4.2.1...
I am running Linux too - couldn't make root so far - did you use some different settings?
Click to expand...
Click to collapse
Nothing special... The only trouble I had in the beginning was to get ADB responding properly. I have different versions of adb utilities on my PC. Other ones did not work, the one in motochopper package worked fine. I was using the original motochopper files. I had to use root rights (running script with sudo) to get it working. Might be that this is the showstopper for you
Full sequence should be something like this:
* Switch on developer mode (multiple clicks in about box on build number).
* Find developer options in the setup menu. Switch on USB debuging.
* Plug in the USB cable, try different USB modes (I think I made it using cd-rom mode, modes can be changed in storage settings under advanced "USB computer connection" menu from the top-right corner menu icon).
* Run the motochopper script with sudo.

LaizyJumper said:
Nothing special... The only trouble I had in the beginning was to get ADB responding properly. I have different versions of adb utilities on my PC. Other ones did not work, the one in motochopper package worked fine. I was using the original motochopper files. I had to use root rights (running script with sudo) to get it working. Might be that this is the showstopper for you
Full sequence should be something like this:
* Switch on developer mode (multiple clicks in about box on build number).
* Find developer options in the setup menu. Switch on USB debuging.
* Plug in the USB cable, try different USB modes (I think I made it using cd-rom mode, modes can be changed in storage settings under advanced "USB computer connection" menu from the top-right corner menu icon).
* Run the motochopper script with sudo.
Click to expand...
Click to collapse
Thanks a lot - have been trying that already - not working with mine...

Sky0ne said:
Thanks a lot - have been trying that already - not working with mine...
Click to expand...
Click to collapse
Have you tried running adb.linux separately? Does it connect?
Run it first with "kill-server" argument and then "shell", for example.
If you get shell access then you should be able to root it. If not then there is something wrong in your pc setup or tab settings.
I assume it worked before you updated your HD7.

Hello everybody,
as promised I got some time to deal with the update.
In short, rooting with this update works, too (but you have to re-root after the update).
Build version after the update shows: ME173X_WW_user_4.2.2.51129_20130619 release-keys
I updated post #1 and put some additional information for linux users.
Regards
quaddler

My Memo HD7 arrived yesterday an it is great ! (amazon.de / germany)
Rooting procedure worked on Win 7 without installing new drivers very easy.
To turn on Developer Mode to switch USB debugging Mode on:
Build Number:
ME173X_WW_user_4.2.1.75146_20130532
Open “Settings”.
Scroll to the bottom and tap “About phone” or “About tablet”.
At the “About” screen, scroll to the bottom and tap on “Build number” seven times.
You will see a “You are now a developer!” message pop up, then you know you have done it correctly.
Done!
You can now enable/disable it under “Settings” -> “Developer Options” -> “Debugging” ->” USB debugging”.
Then just run "run.bat" from motochopper (http://forum.xda-developers.com/showpost.php?p=40129120&postcount=1) and
follow the instructions.

Sorry for offtopic but any info what's new in this update 4.2.2? I'm from Bulgaria and don't have update yet. l'm still with first version ME173X_WW_User_4.2.1.75146_20130523.
Sent from my ME173X using Tapatalk 2

update
Hello,
I have a question:
After the root any new Update can be install over the air?

[Q] Adventures in OTG trying to connect 2 devices

I have already hooked up mass storage to the nexus 4. I checked usb debugging and MTP on both devices also checked OTG box in synapses for the nexus 4. Next if possible I want to hook 2 devices up through an OTG power Y cable and push and pull files with ADB essentially taking out the PC for when I mess up and have to flash a new OS. (I have access to a PC just bored looking for a different way)
The first device is a rooted nexus 4.
ROM: dirty unicorns v9.1 android 5.0.2
Kernel version: 3.4.106-hells-doctor-FrAndroid
The second device is a Samsung galaxy tab pro
Stock android OS KitKat v4.4
When I think Samsung is the host the nexus 4 shows up as a keyboard and mouse. How can I make the Samsung recognize the nexus 4 as a device??
When I switch the cables around the Samsung notification shows a media device connected but I can't find it. The Nexus 4 notification shows USB Debugging with the little monster. This is a learning process for me so if I forgot any vital info please let me know so I can quickly update. Thanks for the help and guidance.

Odin with SM-J700F not possible?!!?

Hello Specialists!!
I have an really big problem with my phone: "SM-J700F"
I am not able to connect via odin or kies to this one.
But in windowes explorer (Win7 64bit) everything is visible.
In MTP Mode, Usb-Storage and PTP mode.
Also I can acess to the phone via the explorer.
But not with odin and/or Kies.
I tried to installit several times (Kies also Kies3)
Then I tried another win7 computer, but with same result.
The reason is, i wont to root the phone, because of low memory, even after reseting to factory.
I hope really a lot that there is an solution!!!!
Many greetings
Robert

Additional information odin
Hello experts!!
Some additional information what I found out:
When I connect my Samsung Galaxy S5 Neo, everything is working.
So I compared the used driver for both phone (S5 is OK), (J7 is not) in the device manager of windows.
So below you see the entries when the phone is connected:
S5 Neo - OK:
-Modem: Samsung Mobile USB Modem
-Samsung Android Phone: Samsung Android ADB Interface
-Tragbare Geräte: Galaxy S5 Neo (translated means: carryable device)
-USB Controller: Samsung Mobile USB Composite Device
Same with J700F - Not OK:
- Modem: entity is not existing ---> difference
-Samsung Android Phone: Samsung Android ADB Interface ---> is equal
-Tragbare Geräte: full_tangxun6572_we_I ---> different, is the Name whitch is visible in windows explorer
-USB Controller: USB Verbindungsgerät (translatet: USB Connection Device) ---> different (this Entity is already existing, even when no phone is connected)
So I tried to update exactly this driver with the downloaded one from Samsung. For this I had to use no compactible hardware.
When I select almost all INF driver, the right driver was visible during installation, but it could not start (code 10)
I think this is somehow the problem.
With the driver "USB Verbindungsgerät" on the windows side everything is OK. Copy to phone, explore,...
But I think that Kies and Odin don't find the acces point to the USB samsung device....the bridge to this device.
Maybe there is an possibility go give odin an additional command, where odin connect to the right port (_#0006) and HUB (_#0004) which I see in the USB Verbindungsgerät....
Do you can help me please!!!!
BR and good night
Hook

hook02 said:
Hello experts!!
Some additional information what I found out:
When I connect my Samsung Galaxy S5 Neo, everything is working.
So I compared the used driver for both phone (S5 is OK), (J7 is not) in the device manager of windows.
So below you see the entries when the phone is connected:
S5 Neo - OK:
-Modem: Samsung Mobile USB Modem
-Samsung Android Phone: Samsung Android ADB Interface
-Tragbare Geräte: Galaxy S5 Neo (translated means: carryable device)
-USB Controller: Samsung Mobile USB Composite Device
Same with J700F - Not OK:
- Modem: entity is not existing ---> difference
-Samsung Android Phone: Samsung Android ADB Interface ---> is equal
-Tragbare Geräte: full_tangxun6572_we_I ---> different, is the Name whitch is visible in windows explorer
-USB Controller: USB Verbindungsgerät (translatet: USB Connection Device) ---> different (this Entity is already existing, even when no phone is connected)
So I tried to update exactly this driver with the downloaded one from Samsung. For this I had to use no compactible hardware.
When I select almost all INF driver, the right driver was visible during installation, but it could not start (code 10)
I think this is somehow the problem.
With the driver "USB Verbindungsgerät" on the windows side everything is OK. Copy to phone, explore,...
But I think that Kies and Odin don't find the acces point to the USB samsung device....the bridge to this device.
Maybe there is an possibility go give odin an additional command, where odin connect to the right port (_#0006) and HUB (_#0004) which I see in the USB Verbindungsgerät....
Do you can help me please!!!!
BR and good night
Hook
Click to expand...
Click to collapse
Hello, Please what I should try?
BR
Robert

Try this maybe this would help yah connecting thru odin... settings > developers option > able OEM unlock
---------- Post added at 07:38 AM ---------- Previous post was at 07:33 AM ----------
Rooting J7, download a compatible twrp n superuser zip file on XDA, and place the superuser in yur device, then flash twrp via Odin( wait 2 to 4 minutes then Pass appears n yur phone reboots) then go to recovery mode then install superuser.zip

I don't know - not working at all
Hello!
Thanks for supoort!
Yes, I tried always: developer options on and OEM unlock. (on 2 Computers with win7)
But there is on both no entity below ID:COM in odin.
So there is no nonnection... (also in windows, when phone is normal connected (not via download mode) there is no connection from ODIN and KIES)
Bute another phone Galaxy S5 Neo is working.
Shi.....
Many thanks for support!!!!!!!!!!
BR
Hook

Can anybody support me
Hello
Is any possibility for helping?
BR
Robert

Some News
Hello!
What I found out:
When I use *#0808#
There is SP selected and RNDIS+ACM+DM+ADB
Bit when I select MTP+ADB the other one is not deselected and I cannot continue?
Means with OK - no function and Reboot - no function (then both are selected....!)
Do you can support me here?
BR
Hook