[Q] Rooting acer A700 -- Stuck after wait-for-device adb instruction - Acer Iconia A700 and A510

Hello,
I'm new in this forum but it's not the first time that I come to read and learn brillants topics. But this time I need more specific advices about rooting the acer A700. I did a lot of research yesterday on my side and on internet and I unfornatelly cannot resolve it.
The problem I have is the same of Toad513 in the topics "Full root for A700 and A7001 tablets" post #106.
I follow all the instructions of the method 1 because I don't have a ICS firmware. (I have the EMEA_CUS1) I added some "echo" in the runit script to find where it stucks; the process frezzes on the line "adb wait-for-device". (And "Waiting for device" is written in the terminal). Nothing happens when I restart the tablet (unlike Toast513 post) but if I give in another terminal the command "adb devices" the following lines appear :
Code:
-Wait for connect device...
remote object '/system/xbin/su' does not exist
The file "su" isn't created!
-
Not getting root :(
-
Error!
-
Press any key.
So it's basically almost the same problem.
Toast513 said that the method2 worked, but I don't have the ICS firmware and it's written only for ICS firmware in the guide.
Another question that I have, do I need to install superuser from the market and disabled the anti-virus before launching the script for method 1 ? And where is located the boot.img file I only saw rooting.img in the folder ?
And last question, it is also indicated that OTA firmware upgrading won't work on method 2. So we manually have to flash the tablet when a new firmware is available, that's right ?
I hope being enough accurate and I'm apologize for my bad english
Thanks in advance
PS: As I don't have 10 messages I cannot post in the Full root for A700 thread. It would be good for the other people who don't have the ICS firmware to put a comment to refer here.
further details about my A700 :
Android version : 4.0.4
Kernel version : 2.6.39.4+
Image version : Acer_AV043_A700_RV07RC04_EMEA_CUS1
Build number : Acer_AV043_A7001.025.00_EMEA_CUS1

You have to be corrected on this one...
You DO have ICS, as ICS is Android OS V4 point 0 dot 1,2,3,4.
Jellybean is the next after dot 4, and is at 4.1 dot blabla..
Your Acer Iconia tab, is running ICS from the factory, for the A510, A511, A700 and up so forth.....
(And Gahhh.. Might we even dream a little of a A900? Hehe ;-)
Your last question, yes you are probably guessing right, OTA's normal execution can be broken, requiring a manual flash.
(We can read and understand your english perfectly, dont worry, unless it suddenly gets much worse.. Then we'll let you know)
Omnius
Sent from my A510 using xda app-developers app

ICS -> Ice Cream Sandwich ...
I should know it
But anyone can say me why the first method doesn't work ? It should also work with ICS (Now I know what these letters means ) ? Does someone successfully tried it ? I would to know why it stuck after "adb wait-for-devices"
I also would like to answer and inform ZeroNull according to his guide (the creator of the "Full root for A700 / A701) but I unfortunately can not due to the insufficient number of messages before sending PM.
And last but not least thanks Omnius for your reply

I've gotten the 2nd method to work on mine personally.
The first method told me waiting for device...
I'm running the same firmware as you 1.025

Related

KYOCERA ECHO RECOVERY IMAGE!!!! Full list of Kyocera Echo Tools

First things first, let me give credit where credit is due!
ZergRush - For creating his script to root the echo; and also giving Saridnour the Tools to create is "Kyocera Echo 1-Click" root method.
Saridnour - For his committed work to Hear the Echo (Our Kyocera Echo Website) and creating the recovery image from scratch pretty much!
KyoceraEchoHax - For Advertising the site and helping us to obtain over 200 members in one month (and growing)
Me - For bringing all these random people together
-------------------------------------------------------------------------------------------------
Okay, now to the good stuff
Here is Saridnour's OneClick Root for the Kyocera EchoHERE
The main problem poeple have is the fact that they use USB tethering! YOUR TETHERING MUST BE OFF or this will not work. tethering uses the ADB servers making it unusable while it is active. TURN TETHER OFF!!
Instructions from Saridnour:
Tool will do it all.. You just need to install the Kyocera Echo drivers from their site (links on the tool)
Let me know if you find issue or bugs. I did this pretty quick and hacked out most of it sitting at TacoTime for dinner last night. lol. The FC's drove me nuts until today and think this should be stable for everyone now. No FC's for me in some time. I did the online update as well without issues, but don't reccomend it just yet although the tool can revert you right back if need be.
Usage:
1- Extract files to your computer, open it, and click Rootme.
Thats about it. Follow the steps and you should be golden. And yes.. These will be the driods you were looking for!
-------------------------------------------------------------------------------------------------
Next is Saridnour FULLY FUNCTIONAL recovery image, it has been tested by multiple people and this is the official release! you can get it HERE
Post from Saridnour on the Original Site:
Well at long last, the Recovery Image is now complete and ready for public Release!
.
Thanks to all the donators, beta testers and those who helped this along the way. I will update this as needed to help the install process and give thanks where needed. I was very rushed getting this up as I wanted it out on Halloween.. the ultimate echo treat!! But we all know what happens when we rush..
BUT the file was done and tested prior to so its just the presentation that was rushed
.
A BIG thank you to Na’ven Enigma for sharing some of her websites bandwidth and hosting the files. She wanted to make sure everyone was able to get instant access to the recovery. Please give her a BIG thank you!
.
.
Only known issue is that you cannot mount the device as a usb drive to copy files. This is a common issue with CWM and should have little to no impact as our echo has removable Micro SD cards.
.
.
To install:
-Follow the directions given in the script (IE: Install the drivers from Kyocera for the Echo, Install the driver that is launched from the script (it's not part of the standard echo drivers)
.
- Make sure it is booted to the os and that debug is turned on: (phone settings -> applications -> development -> USB debugging)
.
- Extract the archive to a folder (IE : the Desktop of your computer)
.
- Run the script “SAR_Recovery.bat” (From within the folder noted above ON YOUR PC)
.
- Follow the prompts given, read what it is asking/telling you and take that action (very short and simple)
.
- Exit from the script and you should be done with the upgrade.
.
- Install from the marketplace “Quick Boot” (free) to allow you to boot into recovery as there are no hardware keys known at this time. You can also use ADB if you can’t access the OS, just send this command: ADB reboot recovery.
.
- Backup your device, Find a rom and have FUN!'
.
.
If you can't boot the OS prior to install:
If you can only see the Kyocera bootloader screen and not boot the OS you need to do this another way. Its still easy and you will just need to follows the steps above up to running the script and install the included driver (or from withint the folder you extracted, install the driver) and then connect your device in bootloader mode (Kyocera screen with yellow light on) and from the pc, ope a command prompt, change to the directory that you extraced the files and type this command " Fastboot devices" it should return ??? meaning it can see your device. IF NOT YOU DO NOT HAVE the drivers loaded, are not in bootloader mode, or your usb is not connected [Bad canle/port/etc]). Once it can see your device type "Fastboot flash recovery recovery.img" and it will install CWM. You will then need to run "fastboot boot recovery.img" to boot into recovery. From there you can install your new rom from HTE.
.
.
Note: The whole process takes less than 5 min. If it hangs, has an issue or you are unsure what it did. Give it another couple minutes, pull the plug, reboot and try again. You can not hurt your phone running this as if the install fails or currupts the recovery image, you only need to reboot to the os and the bootloader to correct the issue and this is what this script does to begin with
.
Don’t forget to donate if you find this of use!
.
Enjoy
-------------------------------------------------------------------------------------------------
Now I will ask you all a favor.
So in the last month or so our site (Hear the Echo) has gone from 20 members in the first week to 200+ 3 weeks later. This is great and horrible at the same time. Our bandwidth cannot support 200 people (it wasn't expected to grow so fast). So I please ask you all to donate to HTE and Saridnour. I ask for HTE because we need to expand our Bandwidth because the site has had a minimum of 2-8 members joining DAILY and we cannot hold on much longer (we have about 5 MB left until the site shuts down for the rest of this week, the bandwidth restarts at the beginning of the next month). So PLEASE donate to us. Also, I say Saridnour because I would not be posting right now if it wasnt for his committment and effort for the site. Thank you Saridnour SO MUCH MAN!
Thanks for reading everyone,
Ognimnella (AKA BFG SgtRecon on HTE)
# Bump #
Sent from my PG86100 using XDA App
Great job guys!! I tried to donate, but HTE came up Error and Sardinuor showed the paypal donate, but cannot complete the process. Please check the donation links....
opm said:
Great job guys!! I tried to donate, but HTE came up Error and Sardinuor showed the paypal donate, but cannot complete the process. Please check the donation links....
Click to expand...
Click to collapse
Hey thank you so much for the support, just click the HTE name again and it should be functional! And I will get in contact with Saridnour very soon about finding someway to link his paypal also, again thank you so much
My brother had root with Android 2.2 (z4root method), but the 2.3.4 update caused his phone to not boot up and he got a replacement. Knowing what I know now, I could of used fastboot to flash the recovery.img...
So I'm gonna go try this! Instead of using "Saridnours" method, couldn't we just use this?
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update] - xda-developers
Anyways, I'm gonna try this. So now I can update my old video! lol
http://www.youtube.com/watch?v=cG2DtNAHZR8&hd=1
That if the base of saridnours one click root!
disturb3d1 said:
My brother had root with Android 2.2 (z4root method), but the 2.3.4 update caused his phone to not boot up and he got a replacement. Knowing what I know now, I could of used fastboot to flash the recovery.img...
So I'm gonna go try this! Instead of using "Saridnours" method, couldn't we just use this?
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update] - xda-developers
Anyways, I'm gonna try this. So now I can update my old video! lol
http://www.youtube.com/watch?v=cG2DtNAHZR8&hd=1
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App
AWESOME
Had a few issues with the drivers at first.. But I stepped away, cleared my mind, and tried again and all worked wonderfully! My Echo is now running like a dream!
THANK YOU ognimnella, and Saridnour!! I will donate when I have a little cash to spare!
Kyocera Echo
These are cool phones ! Rock Solid Gorilla glass no scratch surface and can be used as brass knuckles Thanks for root . Now we need some cool roms .Mine is stuck on 2.2.1 stock and will not take the gingerbread update . it would be nice if someone could capture that update and make it our first full flashed rom . You can pick up an echo CHEAP on Ebay . Got mine for 84 bucks and its super fast snapdragon processor and loads of program memory make it a cool toy . STill i had hopes of using it as a Donor Reciever but no luck with Paid Cdma . Hope SOme developers grap these sweet phones .
Android Sooner Single Fastboot Interface wrong platform??
I get "Android Sooner Single Fastboot Interface is the wrong driver for this platform" So what is the right one for the echo. Also when i try fastboot devices I don't get the ??? just another blank space. My device shows up as "Unidentified device or unknown device too. I feel this is the last thing preventing me from un-bricking my phone so if anybody has any can help me i would greatly appreciate it.
I used SAR recovery and i get all the way to the point where I'm in bootloader mode, the amber light is on, and I'm waiting on devices. So I'm out of ideas.
Peezly said:
I get "Android Sooner Single Fastboot Interface is the wrong driver for this platform" So what is the right one for the echo. Also when i try fastboot devices I don't get the ??? just another blank space. My device shows up as "Unidentified device or unknown device too. I feel this is the last thing preventing me from un-bricking my phone so if anybody has any can help me i would greatly appreciate it.
I used SAR recovery and i get all the way to the point where I'm in bootloader mode, the amber light is on, and I'm waiting on devices. So I'm out of ideas.
Click to expand...
Click to collapse
Its been so long since I had this phone idek man. See if you can find saridnour and ask for his help
Sent from my HTC Evo 3D using XDA
I wish that somebody will find the way to flash echo to boostmobile.
Sent from my not Echo using Tapatalk 2 Beta-6
are there any custom ROM
---------- Post added at 01:46 PM ---------- Previous post was at 01:46 PM ----------
could we get a forum?
jamcar said:
are there any custom ROM
---------- Post added at 01:46 PM ---------- Previous post was at 01:46 PM ----------
could we get a forum?
Click to expand...
Click to collapse
Google it
Sent from my PC36100 using Tapatalk 2 Beta-6
Hi, my echo stuck on kyocera logo screen. It was working fine. I tried to update the latest version of android and when it installing it stopped.. then here I am stuck at kyocera logo.. any help?
zerotechservice said:
Hi, my echo stuck on kyocera logo screen. It was working fine. I tried to update the latest version of android and when it installing it stopped.. then here I am stuck at kyocera logo.. any help?
Click to expand...
Click to collapse
Do u know how to use adb and fastboot.?
Sent from my PG86100 using XDA
i got into the HTE part. what next? i have alot of option. I choose reboot echo now.
Now still stuck on kyocera logo
I'm trying but...
I am having to go through cmd to do this and I get as far as "Fastboot Devices" and it says "acess denied". What am I doing wrong?
after installing drivers it stuck on *wating device* have same on both pc, have change usb ports and restar pc, same thing
how can i flash recovery by adb?

[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?

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?

The Lenovo A706 Owners' Thread (Root/CWM/Other Discussions)

The Lenovo A706 Owners' Thread (for Rooting, CWM, and other discussions)
Official Product Page
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------------------------------------------------------------------------------------------------------------
Device Specs:
---------------------------------------------------------------------------------------------------------------
SIM Type: Dual Mini-SIM
Band Coverage: GSM 900/1800/1900 MHz (Asia-Pacific)
GSM 850/1800/1900 MHz (Latin America)
WCDMA 900/2100 MHz (Asia-Pacific)
WCDMA 850/1900 MHz (Latin America)
WLAN: 802.11 a/b/g/n with hotspot capability
Display: 4.5" IPS (Can anyone confirm if it has Gorilla Glass?)
Resolution: 480 x 854
Navigation: 5-point capacitive touch
Processor: Quad-Core Qualcomm MSM 8225Q 1.2GHz
OS: Android™ 4.1 Jelly Bean with LenovoMagic UI
Memory: 1GB RAM
Storage: 4GB Internal Storage (eMMC) with memory card slot
Battery: 2000mAh Lithium Polymer user-replaceable
Dimensions: 136 x 69 x 10.4 mm
Weight: 130g
Sensors: A-GPS, Gravitation, Ambient light sensor, Proximity sensor
Camera: Front: 0.3MP fixed-focus, Rear: 5MP auto-focus
FM Radio: Yes
Color: White
---------------------------------------------------------------------------------------------------------------
This is a good budget device when compared to other devices from lead manufacturers like Samsung, Sony, LG or Huawei.
While searching on the internet I did find some Root & CWM installation methods.
I will be updating the relevant posts as and when needed.
You can look in the list below for what you want to do with your device.
ATTENTION!!! READ THIS BEFORE DOING ANYTHING
---------------------------------------------------------------------------------
Friend, there are two versions of this device in the market:
1. A706 (Chinese model)
2. A706_ROW (International Model)
The ROMs in this thread are only for the A706ROW model of this phone unless otherwise stated.
If you have the chinese model or another model A760 (which is a different model) then the ROMs in this thread are not for you.
Model A706 and A760 are two different models with almost same specifications. This DOES NOT mean that the ROMs of A706ROW are compatible with A760.
Please DO NOT confuse Lenovo A706 with Lenovo A760 as these are two different devices!!! Flash or experiment at your own risk!!!!
If you share a ROM link for any of the above devices, then please mention clearly the device for which the ROM can be used.
What to do with your Device ?
-------------------------------------------
DISCLAIMER:
---------------------
Rooting your device VOIDS your warranty. Remember if you are doing this, it is at your own sole responsibility
and I cannot be held responsible for any damage to your device, data loss, or any personal injury as a result of your actions.
And, If you still feel it is worth the effort, proceed with caution!
FOR NOOBS
--------------------
Read the instructions (click on SHOW to read) before attempting anything from the list below!
First you need to have the Android SDK installed on your computer. Or atleast you need to have the adb & fastboot files available on your computer.
Here's a good post that tells you how to setup ADB and fastboot.
Here's a post that has a list of adb/shell commands for noobs.
Ok, once you are done with the setup of ADB & fastboot on your computer, then you can proceed with the below instructions.
--------------------
IMPORTANT NOTE BEFORE FLASHING:
-------------------------------------------------------------
Recently, I have noticed that many people after buying the phone are flashing any firmware to their phones and most of the time without checking the phone versions and the OS versions. In the stock firmware post, I had mentioned that people having the Chinese version of the phone should NOT flash the ROW (international) firmware otherwise it would mess up their phone and network etc.
SOLUTION FOR SIM ERROR & DOWNGRADING TO CHINESE ROM
-----------------------------------------------------------------------------------------------------
Now, some of the people have already done such a mistake and for those people (who are having SIM or network problems and want to go back to chinese ROM, I am sticking this post by danyno1 to the OP:
(Click SHOW to See the quoted post)
----------------------
danyno1 said:
hi
I've just installed the "A706ROW_1_S_2_001_0020_130821 MegaFull"" rom , and now i have no network coverage, it doesnt recognize my simcards
I live in Iran.
what should i do??
is there any way to unlock it ??
please help me with this situation , i'm in a hurry
------------------------------------------
after reading the whole topic posts, and testing all the methods , the problem is solved [thanks to mixbox360's posts.] i'm going to just copy and paste his 2 separated posts.
BEST soloutions for these 2 common problems :
#1 device doesnt recognize simcards
#2 being unable to downgrade to the chinees stock rom
soloution of the #1 problem :
how I fixed: Just Installed the QNeonModern 1.7 ROM... then I installed the update of a chinese ROM from bootdroid (I mean putt the update.qsb file un the sdfuse directory o my sd card, then power and vol+ to enter the menu and selected SD UPDATE)... thats all... I have again my chinese rom with signal for calls untill we discover how to make work the athk board in the ROW roms.
Hope to be helpfull!
Click to expand...
Click to collapse
soloution for #2 problem:
Ok trying again to put my chinese device in ROW rom with sim signal, and found a solution:
1:Flash via droidboot a chinese stock firmware I used the 130325
2:Rooted device with vroot and installed CWM Recovery via ADB
3:In the procedure to install custom rom Qneon one of the steps is to flash boot.img via fastboot... well I just didn´t do this step and flashed directly Qneon_1.7.1.zip via CWM
4: Did data/factory reset, cache reset and dalvik cache reset
5:Reboot system
An Ready! Finally got my chinese device in spanish and sim signal.
Click to expand...
Click to collapse
ENJOY THE DUAL SIM ANTENNA + ROM WITH MULTIPLE LANGUAGES
CREDITS : mixbox360
Click to expand...
Click to collapse
------------------------------------------
For Installing CWM: Go to Post #2
For Rooting: Go to Post #3
For Stock ROMs: Go to post #4
For Custom ROMs: Go to post #5
Credits:
-------------
- Lenovo for making a surprisingly good budget phone
- And users for buying it!
Enjoy your phone and share your thoughts and helpful insights/useful methods with all other users here so that they can benefit from your research.
CWM Installation Instructions:
-------------------------------------------
Make sure you have all the drivers for your phone installed on your computer. Download for A706 from here. Some other Qualcomm drivers (not sure if required)
Make sure you have USB Debugging enabled, Install from Unknown Sources is enabled and device is detected in ADB run this command:
Code:
adb devices
Download the CWM Recovery for A706 from here.
Unzip the downloaded file to get a "recovery.img" recovery image file.
Press SHIFT key + Right mouse click in the folder where the file is located and select Open Command from Here.
Now, in the command prompt do the following:
a. Reboot into Bootloader mode. Use command:
Code:
adb reboot bootloader
b. Device will reboot and display Lenovo logo. (check if device is in bootloader mode by running command:
Code:
fastboot devices
. If you see a device connected then you have successfully rebooted into fastboot mode.
c. Now, run this command:
Code:
fastboot flash recovery recovery.img
(This will flash the CWM recovery image to the device).
d. Once successful, reboot the device using this command:
Code:
fastboot reboot
. Or, you can keep the power+vol up+ vol down buttons pressed to restart.​
If everything has gone well, this should get CWM installed on your device. Your device is still *not rooted*. Once you have installed CWM, please proceed to the ROOT instructions post to *root* your device.
CREDITS:
---------------
This post (in Vietnamese)
This post for Recovery (in Russian)
This post for Drivers links (in Russian)
And, to all the other great Russian/Chinese forums and sites who have such vast info on Lenovo which we need in English
DISCLAIMER: Rooting your device VOIDS your warranty. Proceed with caution!!!
1. CWM ROOT METHOD
-------------------------------------
Ok, so you have successfully installed CWM and need root.
1. Just download this Root for A706 ( CWM flashable zip file)
2. Reboot phone to CWM Recovery (use command: adb reboot recovery)
3. Flash the zip and then restart into OS.
4. Now, you should get the Super user app in the list.
2. VROOT (ONE-CLICK ROOTING) METHOD
------------------------------------------------------------------
For noobs AND people who either don't want to install CWM or are unsure of it's usage and only want root, can use this guide for VROOT one-click rooting method. The guide has been translated and posted on XDA by zhuhang. The original vroot post/method (in chinese) exists on this site.
CREDITS:
---------------
Same as in the CWM post above.
Thanks to zhuhang for posting the VROOT guide in english (translated from chinese).
DISCLAIMER: Follow these instructions at your OWN risk & responsibility. They are provided AS-IS without any liability.
IMPORTANT NOTE BEFORE FLASHING:
-------------------------------------------------------------
Recently, I have noticed that many people after buying the phone are flashing any firmware to their phones and most of the time without checking the phone versions and the OS versions. In the stock firmware post, I had mentioned that people having the Chinese version of the phone should NOT flash the ROW (international) firmware otherwise it would mess up their phone and network etc.
Solution to the problem is now in the OP. Please follow it if you have SIM error or network issue.
STOCK ROM
--------------------
I am posting a list of stock firmware(s) that I can find for the A706 here, along with instructions on how to install it.
FIRMWARE LIST
-------------------------
Build Number: A706_ROW_S018:
Details:
Firmware Type: Official Release
Languages: English, Russian, Chinese, Indonesian & Vietnamese
Build Date: 15/07/2013
OS: Android 4.1.2 with Lenovo Magic UI
Download Link: Get it from here (Lenovo-Forums.ru)
(You need to click on the green button on the page. Once you click there then you need to register and logged in, to download it.)
CREDIT: This post in Russian.​
This post by 5[Strogino] has a list of stock firmwares and links to download them.
INSTRUCTIONS
-----------------------
A memory card is required.
Boot into Android normally.
Connect your phone to your PC/Laptop with a USB cable and when asked (or in USB connection settings), please select USB Mass storage mode to mount SD card.
On the root of the memory card, create a folder called "sdfuse".
Unzip the downloaded firmware, you will get a QSB file.
Copy the QSB file to the sdfuse folder that we created earlier on the root of SD card.
Note: Please make sure that your phone has atleast 60% power before attempting or beginning upgrade. Or keep charger connected during the process.
SD card upgrade process:
Long press VOL UP + POWER_KEY to enter the droidboot,
A menu will appear. Select the fourth option, SDUPDATE.
At the bottom of the screen, you can see the progress and status of the update
When you see the message "SDCARD UPDATE SUCCESS!!!", this means you successfully completed the upgrade process
Now, reboot your device and hopefully it should be updated.
That's it! If you guys have found any more firmware download links (even for different regions, build etc.) just share them with me along with details and I will add them to the list in this post.
CREDIT: Instructions were taken from this post and formatted and edited for better understanding.
A List of Custom ROMs
------------------------------------
QNeon-Modern ROM (based on Russian Firmware but has English too): Visit the original thread (in Russian)
Please do share more ROMs with me so that I can include them in this list.
help!
hello bro! i got stuck at installing the cwm flashable file. it's saying "Verifying update package.... Installation aborted"
gr8techie said:
RESERVED (for a list of Stock ROMs/Stock ROM installation)
Click to expand...
Click to collapse
Thanks,
Very nice thread. Had the phone for a month but no support anywhere. i need the stock rom, if u have pls pm me.
thanks again
scuderialoki said:
hello bro! i got stuck at installing the cwm flashable file. it's saying "Verifying update package.... Installation aborted"
Click to expand...
Click to collapse
scuderialoki, unfortunate that you got stuck. worked for me without any issues. i upped the same file that i used on mediafire. can you re-download the file and then check if the file is ok by extracting the zip using winrar or winzip? if it is ok then try flashing it again.
guliboy123 said:
Thanks,
Very nice thread. Had the phone for a month but no support anywhere. i need the stock rom, if u have pls pm me.
thanks again
Click to expand...
Click to collapse
guliboy123, i will be putting the link and some instructions on the stock rom post soon. bear with me as i have to check the instructions from the russian/chinese sites and then put it up here. in the meantime, i suggest you take a backup of your current ROM (which is stock) using CWM and then try out the QNeon-Modern ROM. remember u need to flash that ROM using CWM.
thanks
scuderialoki, unfortunate that you got stuck. worked for me without any issues. i upped the same file that i used on mediafire. can you re-download the file and then check if the file is ok by extracting the zip using winrar or winzip? if it is ok then try flashing it again.
Click to expand...
Click to collapse
gr8techie thanks for the reply. i really appreciate it. just downloaded the flashable cwm however it's still the same bro. lemme tell you something though. i rooted the devices before using framaroot and everything is ok but i had to do a factory reset through the settings app in A706. i still see the superuser app in the system apps and i cant uninstall it. when i open the superuser app in the drawer it's giving me an error that the su binary is not installed and su cant install it.
scuderialoki said:
gr8techie thanks for the reply. i really appreciate it. just downloaded the flashable cwm however it's still the same bro. lemme tell you something though. i rooted the devices before using framaroot and everything is ok but i had to do a factory reset through the settings app in A706. i still see the superuser app in the system apps and i cant uninstall it. when i open the superuser app in the drawer it's giving me an error that the su binary is not installed and su cant install it.
Click to expand...
Click to collapse
ok, please tell me if you have CWM installed on your device? I believe it is not installed. if this is the case, then you need to flash CWM and then try installing the zip again.
if it is installed then, i believe the super su from previous rooting maybe causing the problem. check on Playstore for a method to unroot your device. or google it. then you need to root again. hope this solves your problem.
thanks
Hi bro thanks for the reply i attached a screenshot of my root validation. I used an app to identify that. And by the way my recovery is installed. I the super su app is killing it
New page for our devices :good:
I had rooted my Lenovo A706 before You made this page You are faster than me , bro :laugh::laugh:
Hope our A706 will have more ROM, Init , Kernel that make it better
Some picture of mine, they are old ones..I am cooking some new thing on A706...:laugh: hope you like
Anyone know how to switch between few apps on lenovo A706?
long press on home button will only show the google now
Changing input method when typing also an issues i met,
anyway to change the input method when typing?
Can someone upload an official updated rom (ROW) for lenovo a706? It'll be much appreciated.
FREE CALLING SERVICE PROBLEM
guys,, may be you can help me... the problem is i can hear what other people are saying in LINE / Skype /Viber but people can't hear anything i said.
Goog, I want it
Sent from my Lenovo A706 using xda premium
silv3rmoon said:
Anyone know how to switch between few apps on lenovo A706?
long press on home button will only show the google now
Changing input method when typing also an issues i met,
anyway to change the input method when typing?
Click to expand...
Click to collapse
Long press in menu button ^^
---------- Post added at 08:20 PM ---------- Previous post was at 08:18 PM ----------
rapnix said:
FREE CALLING SERVICE PROBLEM
guys,, may be you can help me... the problem is i can hear what other people are saying in LINE / Skype /Viber but people can't hear anything i said.
Click to expand...
Click to collapse
just viber bro...because maybe viber isn't usable for us now..i can use skype , line , zalo and every things else nomarly
@trithong.. bro. also in LINE and TALKRAY i encounter this problem some of us already encounter this problem what version do you have? i have A706ROW.. no problem if only chatting but if i want to use calling features that's were i encounter this kind of problem i can here them but they cannot here me
my A706 can't root.
CWM show Installation abort!
Baseband ver
A706ROW_1_A_2_0046_130604
Internal ver
A706ROW_1_S_2_001_0018_130705

[Completed] Danew Dslide 904

Hi everybody,
Since a few years, I came here for several problems, and I always found the answers without ever needing to sign up. Many thanks for that !
But this time, I can't do otherwise.
I recovered a tablet, a Danew Dslide 904, with Android 4.2.
There is not much information on web, no drivers, no roms. (Even on the manufacturer's catalog, Thanks Danew.)
I would like to put CyanogenMod on this tablet. (or any real OS... please. just a real OS.)
So, my first problem was not having the drivers.
I use Windows 8.1 and Linux (Ubuntu, Mint ...).
On Linux Ubuntu, I modified the "android-51.rules" file and added :
"SUBSYSTEM ==" usb ", ATTRS {idVendor} ==" 1f3a ", MODE =" 0666 ", OWNER =" XXXX "
Since, the command "adb devices" on my shell shows me my tablet.
But, when I run the "fastboot devices", my tablet does not appear in the list. When I run any command for unlock ("fastboot oem unlock", with or without the option "-i 0x1f3a"), it gives me a "FAILED".
Something else, when I reboot Bootloader (Either by "fastboot -i 0x1f3a reboot" (wow, it works... ) or TWRP Manager, my tablet freezes on the Danew Logo, and a reset is required.
With great difficulty, I installed "Root Checker" (and Kingo Root, SuperSu, TWRP...). In "Bootloader", I have a "Unknown".
However, Root Checker reassures me by indicating "Manufacturer : Danew" and Model "Dslide 904"... (i began to doubt it)
I tried to contact the support Danew four times, without answer. By despair, I contacted them on their Facebook page. but nothing. (a wonderfull page, with almost no product, but many soccer article... wah...)
"French Brand" eh... hum...seriously, how to be taken seriously with brands like you Danew...
So, what can I do to use this tablet? by installing the "frisbee" app or "Boomerang"?
Don't hesitate to ask me if you need additional informations.
Hi and welcome to XDA , finally !
So , what exactly is your question ?
So, what can I do to use this tablet? by installing the "frisbee" app or "Boomerang"?
Click to expand...
Click to collapse
This one above ?
Well the answer is kinda painful , you know ... firstly , your tablet comes with only 1gb RAM which will make the apps to perform quite bad or not to perform at all
Secondly , Cyanogen has vanished , dead , dissolved , we have LineageOS now , kinda same but re-written like and your device isn`t listed on their device supported list
Porting a lineageos rom base to your device will be very difficult , a developer needs device sources , a custom recovery and due to hardware`s limitations , almost impossible
If you would like to try yourself I can find some useful links for you here on xda but personally I would say , leave the tablet as it is , sorry
Cheers !

Categories

Resources