Database Info

[DEV] unofficial ClockworkMod Recovery 5 for Ingenic JZ4770/JZ4760 tablets

this is a work-in-progress development project for porting ClockworkMod Recovery 5 to Ingenic JZ4770/JZ4760 tablets.
this is not perfect at all. and I'm very busy. progress will be very very slow. I may not be able to answer your question/request. if you have some idea for improvement, please do it freely.
there is no support from any makers/vendors. you must agree all risks by installing non-supported files, it may brick your tablet, and you may lose official support/warranty.
* YOU MUST READ CAREFULLY POST#1, #2, AND #3!
* DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW. IT WILL BRICK YOUR TABLET!
* project page
http://androtab.info/mips/ingenic/clockworkmod/
* supported tablets
ainol NOVO7 Basic and Paladin
Velocity Micro Cruz T100 series (Android 2.2 updated model and Android 2.0 PT701i model)
Velocity Micro Cruz T301
ronzi A3
* changelog
refer git log
* resources
http://developer.mips.com/android/
https://github.com/naobsd/cm_bootable_recovery/compare/ics...ics-mips-naobsd
https://github.com/naobsd/mips_build/compare/mips-ics-mr1...mips-ics-clockworkmod
https://github.com/naobsd/mips_external-busybox/compare/ics...ics-mips

* How to install ClockworkMod Recovery 5 (for ainol NOVO7 Basic/Paladin, Cruz T100 series, Cruz T301)
1. download recovery-signed.zip for your tablet (DO NOT USE FILES FOR OTHER TABLETS!)
2. (if you are using stock recovery)rename it to update.zip, then put it on root of SD card
3. install update.zip from recovery
on stock recovery, update.zip will be installed automatically. on ClockworkMod Recovery, you need to select menu item manually.
* How to install ClockworkMod Recovery 5 (for ronzi A3)
1. download recovery.zip for your tablet (DO NOT USE FILES FOR OTHER TABLETS!), then extract recovery.cpio.img from it
2. make backup of stock recovery
Code:
adb remount
adb shell mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
3. copy recovery.cpio.img into your tablet, then flash it
Code:
adb shell inand_flash_image recovery recovery.cpio.img
* How to boot recovery
push & hold VOL+ while power on
* How to boot recovery (alternative)
Code:
adb reboot recovery
*How to control ClockworkMod Recovery 5
VOL-/HOME: down, VOL+: up, POWER/MENU: select, BACK: back

* Superuser, su, and busybox
it can be installed from ClockworkMod Recovery 5
- Superuser, su, and busybox for JZ4770 ICS
- Superuser, su, and busybox for JZ4760 Froyo
* random notes
- stock recovery
if you installed update.zip from stock recovery, stock recovery image should be renamed as /system/recovery.cpio.img.bak. (unless you didn't remove /system/recovery.cpio.img)
it can be flashed by "inand_flash_image" command. (use "flash_image" command for T100 series except PT701i model)
- mbr, xboot, boot, and recovery areas
backup/restore doesn't work for mbr, xboot, boot, and recovery areas
- time for reboot/poweroff (NOVO7 Basic)
I don't know why but reboot/poweroff take long time (as same as stock rom). you should wait 1 minute. if nothing is happened in 10 minutes, use reset hole

for now I'm preparing to push my changes to github. I'm very busy so it needs some time.
if you made some.zip file to do something for MIPS Android (e.g. superuser.apk with su binary for MIPS), please tell me. I'll add link to post#1.
if you have some idea for next work, please tell me too. (but, as I wrote, I may not be able to answer your request. sorry)

Thanks for your starting thread and project.
I bought a Advanced model but they send us a Basic Novo7.
All we know the incompatibilites using a cpu MIPS, that doesnt allow to run a lot of Android software that for default its compiled for ARM processors.
Im getting a bundle pack of apps running under our device.

Kashamalaga said:
Thanks for your starting thread and project.
I bought a Advanced model but they send us a Basic Novo7.
All we know the incompatibilites using a cpu MIPS, that doesnt allow to run a lot of Android software that for default its compiled for ARM processors.
Im getting a bundle pack of apps running under our device.
Click to expand...
Click to collapse
thank you. I understand your condition.
but here is dev thread for clockworkmod for novo7 basic. if you want to talk about apps which support mips android and/or any general things about novo7b, I recommend you to make new thread for it.

fun_ said:
thank you. I understand your condition.
but here is dev thread for clockworkmod for novo7 basic. if you want to talk about apps which support mips android and/or any general things about novo7b, I recommend you to make new thread for it.
Click to expand...
Click to collapse
I will do as you said

This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source

Also here SHOULD be a working SU for MIPs. It work's on the cruz tablets

vanduhl said:
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Click to expand...
Click to collapse
I couldn't read what you did exactly. if you flashed my image w/o modification, it must not work. as I wrote, DO NOT USE file for other tablet.
please explain what you did, and please explain detail about your tablet before any random work.

fun_ said:
I couldn't read what you did exactly. if you flashed my image w/o modification, it must not work. as I wrote, DO NOT USE file for other tablet.
please explain what you did, and please explain detail about your tablet before any random work.
Click to expand...
Click to collapse
Attempted using the above stated method(understanding you said DO NOT US file on other tablet) I was curious to see as what kind of error would or may of come up. I'm interested in modifying this for the Velocity Cruz T301 tablet(running a JZ4760 processor) as that community of tablet users has been left under the dust. Now with the novo coming out it will further pile under the dust. I have not yet made any modifications to it, although I would very much like to.

vanduhl said:
Attempted using the above stated method(understanding you said DO NOT US file on other tablet) I was curious to see as what kind of error would or may of come up.
Click to expand...
Click to collapse
kernel must not work because it's for NOVO7B. in general, kernel can't be shared among different products.
key assign, and partition layout may be different too. but currently I have no idea how to fix them because I don't have any detail about your tablet...

http://en.ingenic.cn/product.aspx
it seems JZ4760 is NOT MIPS32R2. then I need to recompile userland binaries.
anyway, technical detail is required to support other tablets.

http://bbs.imp3.net/thread-10520163-1-2.html
it seems source code for xboot, android 2.2 and (part of?)kernel source for NOVO7B is released. I don't try to compile them yet so I may be wrong.
I'll check them later.

Is it possible that someday this recovery will be also ported for ainol novo7 Advanced ?

endrju100 said:
Is it possible that someday this recovery will be also ported for ainol novo7 Advanced ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1378594
you should use search engine before post a question.

vanduhl said:
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Click to expand...
Click to collapse
How did you get back to your stock recovery image on the T301? I think I borked mines on a T105 accidentally with ROM Manager. I accidentally pressed the screen too many times while 'exploring' and the delayed input caused ROM Manager to start flashing a recovery. Now I can't boot into recovery. I just see black nothing.
EDIT:
Disregard - My stock recovery boots. I was performing the boot into recovery procedure incorrectly. Also, because the recovery.cpio.img was in /system I assume it was flashed on each power cycle.
Apologize: I have read the complete topic and now understand that at present it is only for Novo.

Please dont use this thread to talk for another devices that arent be Novo7 Basic.
Asi cant start a new thread yet, here is my thread at spanish forum comunity with a full starter packs of mips app + games and a guide to be root.
htcmania. co m/showthread.php?t=303749

I´ve got successfully get a compiled MIPS version of Titanium backup that works like a charm for our device Novo7 Device! Checkout at the link upside.
Regards. (I will open a new thread when i´ve got 50 messages...)

fun_ said:
it seems source code for xboot, android 2.2 and (part of?)kernel source for NOVO7B is released. I don't try to compile them yet so I may be wrong.
I'll check them later.
Click to expand...
Click to collapse
what other info would you like?

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.

[Confirmation] Samsung N7100 clone (Chinese version) rooted now

Actually i don't want to make this new thread but since i'm new here and can't do a reply to the original thread so i make this. I just want to make a confirmation for Bin4ry who owned this awesome thread "Root MANY ANDROID!" that his tool work on my n7100 clone phone. And i want to make some recap for i have done.
my phone spec is:
processor: Mtk6515
RAM: 512 MB
Android version: Android 4.1.2
my computer spec is:
Brand: Asus ee-pc 1215B
Processor: AMD C-60
OS: Windows 7 32 bit
what i have done is:
1- enabling usb debugging mode and unknown sources function (i'm not installing any adb drivers or something sound like that since the first time)
2- i plug in to my laptop, and my device recognized as "sanstar" but strangely it's reacognized with a name "My HTC" on device manager
3- Run cmd and go to the folder where i put the tools.
4- Type runme.bat and choose "1" but somehow it gaves me some error
5- So i watched Bin4ry video for one more time :highfive:
6- And then, i back to step 3 and type "stuff\adb devices" and wait...... not for long it tells me that my device already connected... YAY :fingers-crossed:
7- I did step 4 again...wait for the process and see if restore function already pop up on my android phone and yep, it's showing something ahehehe
8- Click "restore my data" button....my phone restart after that and tadaaa....there's "superuser" showing up :victory:
So thank you so much, Bin4ry

Hello,
I also have the same phone but I had no luck with this method. After searching for a long time, I found SRSRoot which allowed me to Root my phone. It was a tough fight but I now have a rooted Note II clone...
acoet said:
Actually i don't want to make this new thread but since i'm new here and can't do a reply to the original thread so i make this. I just want to make a confirmation for Bin4ry who owned this awesome thread "Root MANY ANDROID!" that his tool work on my n7100 clone phone. And i want to make some recap for i have done.
my phone spec is:
processor: Mtk6515
RAM: 512 MB
Android version: Android 4.1.2
my computer spec is:
Brand: Asus ee-pc 1215B
Processor: AMD C-60
OS: Windows 7 32 bit
what i have done is:
1- enabling usb debugging mode and unknown sources function (i'm not installing any adb drivers or something sound like that since the first time)
2- i plug in to my laptop, and my device recognized as "sanstar" but strangely it's reacognized with a name "My HTC" on device manager
3- Run cmd and go to the folder where i put the tools.
4- Type runme.bat and choose "1" but somehow it gaves me some error
5- So i watched Bin4ry video for one more time :highfive:
6- And then, i back to step 3 and type "stuff\adb devices" and wait...... not for long it tells me that my device already connected... YAY :fingers-crossed:
7- I did step 4 again...wait for the process and see if restore function already pop up on my android phone and yep, it's showing something ahehehe
8- Click "restore my data" button....my phone restart after that and tadaaa....there's "superuser" showing up :victory:
So thank you so much, Bin4ry
Click to expand...
Click to collapse

need room plz
hi
i am need rom not2 i7100
plz help
model:i7100
fcc id:a3lgti7100
bb chip:mt6515
ms board:gt n7100
kernel ver:3.0.13([email protected])(gcc version 4.4.3(gcc))
android ver .4.1.2
sw ver . s005-ssd-hh-l002
custam build verno.0088130115
phone model:GT-N7100
Brand:samsung
cpu hardware:smdk4412
cpu model:armv7proces rev 2 (v71
cpu frequency:200.0~1400.0 MHz
screen resolation:1280.720
Gpu vendor: imaginatio technologies
gpu renderer: power vr sgx 531
gpu versionopen gl: open gl es-cm 1.1

custom rom
acoet said:
Actually i don't want to make this new thread but since i'm new here and can't do a reply to the original thread so i make this. I just want to make a confirmation for Bin4ry who owned this awesome thread "Root MANY ANDROID!" that his tool work on my n7100 clone phone. And i want to make some recap for i have done.
my phone spec is:
processor: Mtk6515
RAM: 512 MB
Android version: Android 4.1.2
my computer spec is:
Brand: Asus ee-pc 1215B
Processor: AMD C-60
OS: Windows 7 32 bit
what i have done is:
1- enabling usb debugging mode and unknown sources function (i'm not installing any adb drivers or something sound like that since the first time)
2- i plug in to my laptop, and my device recognized as "sanstar" but strangely it's reacognized with a name "My HTC" on device manager
3- Run cmd and go to the folder where i put the tools.
4- Type runme.bat and choose "1" but somehow it gaves me some error
5- So i watched Bin4ry video for one more time :highfive:
6- And then, i back to step 3 and type "stuff\adb devices" and wait...... not for long it tells me that my device already connected... YAY :fingers-crossed:
7- I did step 4 again...wait for the process and see if restore function already pop up on my android phone and yep, it's showing something ahehehe
8- Click "restore my data" button....my phone restart after that and tadaaa....there's "superuser" showing up :victory:
So thank you so much, Bin4ry
Click to expand...
Click to collapse
do have any custom rom for this phone.?

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] Please link for ZTE K3DX-V5G firmware.

Please link for ZTE K3DX-V5G firmware.

ZTE K3DX-V5G firmware
Why do you need ZTE K3DX-V5G firmware?
Is there something wrong with your device?
Do you recommend buying the ZTE K3DX-V5G?
The brand name is V5 or ZTE or Guan or Mango.
It is the same device, manufatured by V5 and sold by ZTE, Guan and Mango.
Guan K3DX-V5G
https://deviceatlas.com/device-data/devices/guan/k3dx-v5g/28213760
BangGearWatch | ZTE V5G-K3DX
https://www.banggearwatch.com/pricetracker/zte-v5g-k3dx-5-5-inch-3gb-1369255/
The price was €64 at BangGood, for a short time.
The price was €70 at MyeFOX.
V5 K3DX-V5G 3GB RAM 32GB ROM Qualcomm Snapdragon 617 1.5GHz Octa Core FHD Display 5.5 inches Android 5.1 4G LTE Smartphone
https://www.myefox.fr/telephones/v5...a-core-fhd-ecran-55-pouces-android-5-g-223880
K3DX-V5G supports naked-eye 3D and eye-tracking.
It has a K3DX display with column interlaced mode.
Therefore is fully compatible with PhereoRol3D app.
https://github.com/JackDesBwa/PhereoRoll3D
Get the latest release here
https://github.com/JackDesBwa/PhereoRoll3D/releases
Have you tried PhereoRol3D ?

BootStomp and DR.CHECKER
Your phone has a locked bootloader.
You need to run these two tools: DR.CHECKER and BootStomp.
DR.CHECKER : A Soundy Vulnerability Detection Tool for Linux Kernel Drivers.
It is a single script!
This repo contains all the sources, including setup scripts. Now with an Amazing UI to view the warnings along with corresponding source files.
https://github.com/ucsb-seclab/dr_checker
BootStomp
https://seclab.cs.ucsb.edu/academic/publishing/#bootstomp-security-bootloaders-mobile-devices-2017
Did you manage to root ZTE K3DX-V5G ?

Partitions table
Get an excellent partitions table of ZTE K3DX-V5G
This format is ideal for recovery.
Device Info HW
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw&hl=en_US
NOTE - Find attached the partitions table of SuperD D1 (SuperD C1001). It is another device with Naked-eye 3D and eye-tracking.

Do you own a ZTE K3DX-V5G ?
You do not own a ZTE K3DX-V5G, do you?
V5 K3DX V5G Smartphone Unboxing (3D Video Camera)
https://www.youtube.com/watch?v=KkQhQszdSYs
Mango K3DX-V5G
https://v.youku.com/v_show/id_XMjgxMDI4OTcyOA==.html
3D Dongdong APP: Over 10,000 3D movies provided
http://en.k3dx.com/prolist/7/17.html

Thank you for many information about it.
I did not own it now due to it heat up too much compare with SD 625 / 636 phone.

Discussion V5 K3DX-V5G at russian 4pda forum
Discussion V5 K3DX-V5G
http://4pda.ru/forum/index.php?showtopic=944204
There is new firmware available from chinese versions (latest 1.3)
Firmware in China
http://www.shuajibao.com/rom/Zte/23777
Version 1.3 is not official. It is a custom ROM by this russian guy... Sidorovvitalik.
But development has already stopped because he is selling his ZTE V5 K3DX-V5G.

K3DX V5G stockrom
Please can someone upload the stockrom.

After scouring the internet for hours, I stumbled upon this post:
https://4pda.ru/forum/index.php?showtopic=944204&st=220
And guess what, I found the firmware for the device! Eventually, I was able to fix my bricked K3DX V5G, and here it is:
https://yadi.sk/d/TSjrTYbKBV4KWA
What I did was:
1. Decompressing the file
2. Flashing it with fastboot
3. Device resurrected!
Fastboot commands:
Code:
fastboot flash:raw boot boot.img
fastboot flash system system.img
edit: found out that it is a clone of ZTE v5 pro N940SC

Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.

Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.

asce16 said:
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
Click to expand...
Click to collapse
Are you on Linux or Windows?

Ma'am/Sir. What usb driver did you use to detect your k3dx v5g phone? I cant find compatible to mine, my pc cant detect my k3dx v5g phone. Plsss. Send link. Thanks in advance.

B83C said:
Are you on Linux or Windows?
Click to expand...
Click to collapse
Window.

B83C said:
Are you on Linux or Windows?
Click to expand...
Click to collapse
Also ma'am/sir. can i ask a little favor? Can you send me full guide how to flash this file. Plssss

asce16 said:
Also ma'am/sir. can i ask a little favor? Can you send me full guide how to flash this file. Plssss
Click to expand...
Click to collapse
Hmm well, have u tried peeking at the device manager when you phone is connected to your PC in fastboot mode?
If there's an entry showing your device you will need grab a fastboot binary to flash the firmware.
Here's a link to the tool called minimal ADB and Fastboot: here
You will also need to extract the firmware to somewhere in your drive.
Having done all the extraction and installation,
and since you're on Windows, you should do:
Bash:
\path\to\fastboot flash:raw boot \path\to\boot.img
\path\to\fastboot flash system \path\to\system.img
where \path\to\fastboot points to the path where you have extracted/installed the tool (or if you have added its path to the PATH environment variable, you can avoid the hassle to write the full path), and \path\to\boot.img and system.img points to absolute path of the extracted firmware.
Then, you are good to go!

B83C said:
Hmm well, have u tried peeking at the device manager when you phone is connected to your PC in fastboot mode?
If there's an entry showing your device you will need grab a fastboot binary to flash the firmware.
Here's a link to the tool called minimal ADB and Fastboot: here
You will also need to extract the firmware to somewhere in your drive.
Having done all the extraction and installation,
and since you're on Windows, you should do:
Bash:
\path\to\fastboot flash:raw boot \path\to\boot.img
\path\to\fastboot flash system \path\to\system.img
where \path\to\fastboot points to the path where you have extracted/installed the tool (or if you have added its path to the PATH environment variable, you can avoid the hassle to write the full path), and \path\to\boot.img and system.img points to absolute path of the extracted firmware.
Then, you are good to go!
Click to expand...
Click to collapse
Ma'am/sir. Thanks, it's fix now. Thanks for the help. Godbless and stay safe.

Hello, in case you are looking for a twrp image for the device, here's one I have ported myself:
TWRP_N940Sc_V3
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

B83C said:
Hello, in case you are looking for a twrp image for the device, here's one I have ported myself:
https://www.mediafire.com/file/0547s4g8hdojctq/TWRP_N940Sc_V3.img/fileTh
Click to expand...
Click to collapse
Thankyou! Uhm is there any custom rom? Can you please port a custom rom or upload please i really need it[/url]

John072021 said:
Thankyou! Uhm is there any custom rom? Can you please port a custom rom or upload please i really need it[/url]
Click to expand...
Click to collapse
I regret to tell you that, no. Currently I have been using the phone as a debian server, since the LCD has been inadvertently broken ( I exerted too much force on it ). Moreover, the device doesn't recognize its battery, which suggests that I might have broken some part of it. Therefore, I have kinda lost any hopes for it. Plus, my linux machine is not powerful enough to build an android OS ( what do you expect much from an intel celeron? ).
PS: I might do it once I get my hands on a much powerful one, or maybe a powerful enough VPS? I am not quite sure but currently I am still in high school, meaning that I may or may not have time....
Best regards,
B83C