yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] spinnersp:
help root b1-720

Cant seem to root my B1-720. Ive tried toolkit v.8.2-8.5. Tried running as admin,in cmd and right click toolkit. Versions .82-.84 all seem to try the root,v85 closes. Anyway im running win7,Tablet is on 4.2.2,i have usb debugging turned on. So I get ti where it says copying image file,then it fails and I get error,Failed to copy image file to Cache.Permission denied. Make sur system.img.gz file suits installed firmware. It does,im on RV03RC01_WW_GEN1.Downloaded from link on first page,renamed to"system.img.gz" and placed in system_image folder. Help please.
[Miscellaneous Android Development] _Tallis_:
Hi there!

I've got a new A3-A20FHD with KK4.4.2 and Mediatek chip MT8127. Any chance of rooting the device?

Thx, _Tallis_
[Miscellaneous Android Development] FahrenGrade:
help

Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.mediatek.connectivity/.CdsInfoActivity }

Warning: Activity not started, its current task has been brought to the front

Successfully started Telnet server on your Acer Iconia A1-810 / A1-811 / A3-A10 / B1-711 / B1-720 running KitKat.

/data/local/tmp/busybox telnet 127.0.0.1 1234 | cat /proc/dumchar_info

exit

exit

127.0.0.1 1234 | cat /proc/dumchar_info <

Part_Name	Size	StartAddr	Type	MapTo

preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd

mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0

ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1

pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0

pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0

nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0

protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2

protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3

seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0

uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0

bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0

recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0

sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4

misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0

logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0

expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0

android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5

Creating system.img.gz (this will take about 7 minutes) ...

/data/local/tmp/busybox telnet 127.0.0.1 1234

dd if=/dev/block/mmcblk0 bs=4096 skip=17664 count=262144 | gzip > /cache/system.img.gz

shell@mango:/ $ /data/local/tmp/busybox telnet 127.0.0.1 1234

telnet: can't connect to remote host (127.0.0.1): Connection refused

96 skip=17664 count=262144 | gzip > /cache/system.img.gz <

/system/bin/sh: can't create /cache/system.img.gz: Permission denied

/dev/block/mmcblk0: cannot open for read: Permission denied

1|shell@mango:/ $ exit

/data/local/tmp/busybox telnet 127.0.0.1 1234

chmod 777 /cache

chmod 777 /cache/system.img.gz

shell@mango:/ $ /data/local/tmp/busybox telnet 127.0.0.1 1234

telnet: can't connect to remote host (127.0.0.1): Connection refused

1|shell@mango:/ $ chmod 777 /cache

Unable to chmod /cache: Operation not permitted

10|shell@mango:/ $ chmod 777 /cache/system.img.gz

Unable to chmod /cache/system.img.gz: Permission denied

10|shell@mango:/ $ exit

opendir failed, Permission denied

fail

THIS KEEPS HAPPENING!
[Miscellaneous Android Development] Atrax2010:
Bricked A1 810

Can someone help me here, yesterday I tried to make an official update for my 810, I downloaded the official KitKat from Acer website, but it couldn't update, said I have wrong model number.

After that the tablet wouldn't restart, I had bootloop.

So I downloaded the proper 4.2 version for my model (ww_gen1) from Acer website, flashed it from SD card, everything went well, I restarted and the phone was again in bootloop, it would get to "Updating applications" and then restart.

So I entered recovery again, made factory reset and from that point on I can't turn on the device.

When it's plugged in i can hear it's connecting to PC but it isn't recognized, then disconnects immediately.

It also doesn't charge at all. When I started the procedure the battery was about 90% so I don't think it's the dead battery.

I had similar issue with my OneX, it was a faulty motherboard, so I'm worried my tablet is hardbricked.

But it makes no sense, it wasn't rooted, I wasn't doing anything dodgy, everything from official software and official guides.

Can I fix this somehow?

Thank you in advance.

Cheers
[Miscellaneous Android Development] nikagl:
Hi Atrax2010,

Did you try the following guide:

Firmwares for flashing - [EN]

I have used it in the past and it worked perfectly. Simply choose the right ROM for you device and flash it with spflashtool and you're good to go. I have also seen some posts where they mentioned to fully discharge the device, or remove the battery (which is a bit more difficult in a tab)...

Let us know what happens with the guide :)

One more thing, it looks like you only used proper Acer firmwares. In that case my advice would be to contact local Acer support, because using the above firmwares is officially unsupported...

Regards,

Nika.
[Miscellaneous Android Development] Paradroid87:
Iconia B1 A71

Hi there,

I'm wondering if you could help me, please. I've followed the bootloader unlock, patch and root instructions for the B1 A71 to the tee and as far as I can tell it all went perfectly. The trouble is, after completing I can no longer switch the screen on. The Windows 7 PC I'm using can still recognise the device over adb (though not mtp) and I was even able to run the unroot successfully, but I can't switch the screen on to actually use the tablet. Has anybody got any ideas on how to proceed?

Edit: on trying to run root again it is still recognised over adb and copies busybox. I get as far as being asked to unlock the screen, which I can't do and attempting to simulate it doesn't work.

All the best and thanks for any help you can give,

Paradroid87
[Miscellaneous Android Development] Atrax2010:
Hello sir. I will try with this guide first. My warranty is not valid anymore either way because I was opening the device before, and changing the screen on my own and so on, so I have to fix this on my own.

I will let you know if I succeeded with this guide.

Thank you.

Cheers.
[Miscellaneous Android Development] Atrax2010:
I just went through the procedure. The tab seems to be flashed OK, I'm an now charging it in the wall charger for 15min as said by instructions, the charging screen is showing so that's a good sign. That's should be it, thank you so much sir.

Tell me one more thing, is there a way for me to upgrade to an official kitkat without rooting? My model ww_gen1 isn't officially supported, but I was wondering if I can flash the 4.4 rom just as I did this one via spft? I really would like kitkat on my device 'cause I've read that it's a lot better with it.

Either way, thank you very much for the help :good:

EDIT: Yup, everything seems to be working, and upon the bootup the phone immediately found a kitkat update. It wasn't finding any before.

I am about to root the device, I only want to remove bloatware.

Does it matter which one system.img.gz I download? I see a few of them for ww_gen1 and I don't know which should I choose. My Image version is RV0HRC03_WW_GEN1. Is it ok to use the RV27RC03_WW_GEN1 for my device?

Cheers
[Miscellaneous Android Development] Optimissimus99:
I would first install all updates, then unlock under KitKat, install cwm and root and THEN remove bloat
[Miscellaneous Android Development] Droidman61:
entonjackson

What a great post but I bought one for my son it is a US A1-810 RVOHRC03 4.4.2. I don't find it in the the list above, is there something I am missing?

Could someone help? Thank you in advance. :)
[Miscellaneous Android Development] entonjackson:
A rooted image of this firmware wasn't shared here yet. But you can always try to root "from scratch". You will need Linux for that.

After you rooted from scratch you will receive a rooted system.img.gz which you can share here.

Good luck.
[Miscellaneous Android Development] murdoch1:
A1-810

Hi.I have the same firmware as stated "Acer_AV0KO_A1-810_RV0HRC03_WW_GEN1"

I have just attempted a root from scratch on my Unbuntu system. Sadly this resulted in a "fail" at the end of the process just as it was creating the "system image".

I have attached the screen shots in order of steps followed. 1 2 & 3.

2 contains the fail error and 3 was a debug log I attempted.

Any help would be useful.
[Miscellaneous Android Development] entonjackson:
I think the telnet server isn't running.

I see you're running Kitkat, so please try it, holding your tablet in portrait mode, before you let the tool start the telnet server.

If you already did this, then you'll have to try starting the telnet server manually.
[Miscellaneous Android Development] murdoch1:
Cheers for your reply. How can I start that process manually. I saw in your FAQ there was a section but it confused the hell out of me. Lol.

Do I just need to type a command to start telnet and if so what command should I use?

Thanks again.

---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------

Nb. On the telnet screen the run box is greyed out I recall. I presume this means it's not running? Didn't seem to be a way to click on this button??
[Miscellaneous Android Development] nikagl:
It actually IS confusing as hell, lol. Trust me - just do it step by step and you should be ok. I also saw the following steps:

http://xdaforums.com/showpost.php?p=40484365
[Miscellaneous Android Development] entonjackson:
This should help you.
[Miscellaneous Android Development] nikagl:
Main things is that you need to do is

1. Push busybox

adb push C:\tools\busybox /data/local/tmp (press enter)

2. change execute permission for busybox

adb shell

chmod 777 /data/local/tmp/busybox

3. open engineering mode

*#*#3646633#*#*

(or use an app for it)

4. goto network utility

goto menu items -> Connectivity -> CDS Information -> Network Utility

5. run telnet

/data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234

etc... :)

If you get errors somewhere, post screenprint please :)
[Miscellaneous Android Development] murdoch1:
Cheers on the exdialler. Typing in the code does not display network utility. Under connectivity tab I only get Bluetooth/WiFi and WiFi ctia.
[Miscellaneous Android Development] nikagl:
I think you are on a firmware where they fixed that. Can you go back to an older release?
[Miscellaneous Android Development] murdoch1:
Typical bloody Acer!!!!!! Not sure. I wouldn't know which former to flash. I know its a ww1 model but I didn't think you could flash an earlier version? Something to do with KitKat boot loader did I read somewhere??
[Miscellaneous Android Development] nikagl:
Btw, I used this app to open engineering mode:

https://play.google.com/store/apps/details?id=com.themonsterit.EngineerStarter
[Miscellaneous Android Development] murdoch1:
Yes tried that also but thanks again. :0). I think I may end up trading it in and getting a nexus 7.

---------- Post added at 06:40 PM ---------- Previous post was at 06:32 PM ----------

I would kindly advise a note being put on the op to reflect the issues faced on those of us whom have already updated to the official ota???
[Miscellaneous Android Development] nikagl:
You're really encouraging us to continue investigation :):). Nevertheless, can you post your exact version? I have an Acer_AV0k0_A1-811_RV02RC06_WW_GEN1 (1.022) which still has CDS Information in the connectivity tab... (haven't actually tested rooting as I don't need root for anything)

---------- Post added at 08:10 PM ---------- Previous post was at 08:00 PM ----------

Just for reference, here's some screenshots of the manual method:

I remember vaguely when the actual telnet session is started, it should show a hash (#) instead of a dollar sign ($) to indicate it has root access (for dd to work).

---------- Post added at 08:25 PM ---------- Previous post was at 08:10 PM ----------

In case you still want to continue, use the following post:

http://xdaforums.com/showpost.php?p=55501154&postcount=52

It references to a textfile which has A1-810 firmwares that can be flashed using the SPFlashtool. It also explains how to use it...needless to say: do it at own risk...
[Miscellaneous Android Development] murdoch1:
Sorry bud.

My image version is Acer_av0k0_a1-810_rv0hrc03_ww_gen1

Build number Acer_av0k0_a1-810_1.055.00_ww_gen1

Image p/n FM.nlxa0.06k
[Miscellaneous Android Development] nikagl:
See my other previous post. I think your only option would be to go back a firmware, download the ones mentioned in the other thread that you can flash with the SP FlashTool (SPFT). Your data will be lost and use at own risk (I have an A1-811 so can't test anything for you).

Possibly wait another day or week to see whether there's people with other tips & tricks?

Regards,

Nika.

---------- Post added at 08:59 PM ---------- Previous post was at 08:33 PM ----------

In case it hasn't been tested before - I have rooted an "Acer_AV0k0_A1-811_RV02RC06_WW_GEN1 (1.022)" from scratch using Ubuntu 14.10.

---------- Post added at 09:22 PM ---------- Previous post was at 08:59 PM ----------

Hmmm... checking now how succesfull my root was. I wonder what the exact release "RV08RC06" was because now, when checking with SuperSU, it looks like it was not so succesfull? SuperSU cannot install nu SU binary and Root Checker says I do not have root (not that I really care, it's just to let know that it seems to not yet work on my AV0k0_A1-811_RV02RC06_WW_GEN1
[Miscellaneous Android Development] Optimissimus99:
NO! With A1-81x KK you actually CANT use NetworkUtility. You must use MTKLogger ( 3-Dot-Settings in MTKLogger) MTKLogger can also be found in Dev Options :)
[Miscellaneous Android Development] nikagl:
I have done root from scratch using ubuntu. All was ok (I can post screenprints if needed) but still seems root is not available. Also note that the issue with RV08RC06 was on a TWN device (Acer_AV052_A1-811_1.092.00_TWN_GEN1 / Acer_AV052_A1-811_RV08RC06_TWN_GEN1, where AV052 usually is JB and AV0k0 is KK if I remember correctly) and I have a WW device (with KK): Acer_AV0k0_A1-811_RV02RC06_WW_GEN1 (1.022)
[Miscellaneous Android Development] nikagl:
Kewl!

Verstuurd vanaf mijn A1-811 met Tapatalk
[Miscellaneous Android Development] Moriveon:
Recovery shell instead of EngMenu command

Hello, guys! I have an idea for an A1-81x owners, who can't run the telnet command from Engineer Menu. There is an other way to execute it, but we need to test it :)

Reboot your tablet into Recovery (even stock recovery will be ok). Then, if you have the stock recovery, choose an "Apply update from ADB" - it will start an ADB server on tablet side. Now, on PC execute following commands:

adb devices
adb shell

Now run that telnet command, and try to continue rooting!
[Miscellaneous Android Development] nikagl:
Well... two things:

1. It did run telnet from both the engineering mode and the mtk logger - i haven't (yet) tried to use the mtk logger telnet as i would need to modify the script to skip opening telnet and directly go for creating the new system.img. I think [MENTION=2292100]murdoch1[/MENTION] should try that too, but I am not sure about the manual steps following the activation of telnet?

2. Recovery doesn't have apply update from ADB. Mine only has reboot, apply update from external storage, wipe data, fastboot mode and demo mode....

Regards,

Nika.

---------- Post added at 11:54 PM ---------- Previous post was at 11:43 PM ----------

I have checked in my device and all files from a1su.tgz are in my /system. So files are in there, they're just not being used by the device when root access is requested?
[Miscellaneous Android Development] kuri_2k:
Hi There,

Is it possible to Root Acer Iconia Talk S A1-724?

Thank you
[Miscellaneous Android Development] _Tallis_:
You could try this command:

adb shell am start -n com.mediatek.engineermode/.EngineerMode com.mediatek.connectivity/.CdsInfoActivity

It's the only way I can start Network Utility on my tablet, using the dialer code doesn't work for me, too.
[Miscellaneous Android Development] nikagl:
Hi all,

Not much action going on here :). I have PM-ed [MENTION=3392632]entonjackson[/MENTION] to know whether he can change the script to include code to use MTK Logger instead of the NetworkUtility and whether he wants to include steps for Acer S1, but no response so far. I have done the process manually and it worked fine. Should work for Acer A1-811 too and other devices on which the Network Utility does not work anymore....

Manual steps for Acer S1 are here:

http://xdaforums.com/android/development/root-acer-liquid-s1-s510-a10-kk-rom-t3004333

Anyone else good at changing the script to include the new steps? :)

Regards,

Nika.
[Miscellaneous Android Development] nikagl:
Hi all,

For A1-811 on Acer_AV0K0_A1-811_RV02RC06_WW_GEN1 / Acer_AV0K0_A1-811_1.025_WW_GEN1 (= KitKat), the selection of MTK Logger in Engineering Mode is 45 pixels down. It now selects Modem Warning Setting... I guess this might be because it's an A1-811 and not A1-810, and therefore includes a modem?

So in the all in one Toolkit (.toolkit.py) "input tap 400 275" should be "input tap 400 320".

I added a variable:

a1_811 = False

I changed the following:

subprocess.call(adb + 'shell input tap 400 275', stdout=dev_null, shell=True)

Into:

if a1_811:
subprocess.call(adb + 'shell input tap 400 320', stdout=dev_null, shell=True)
else:
subprocess.call(adb + 'shell input tap 400 275', stdout=dev_null, shell=True)

and I changed the selection of the device into the following bit:

# Add-on for A1 KitKat
print("")
print("Which device do you have?")
print("[1] Acer Iconia A1-810 / A1-811 / A3-A10 / B1-711 / B1-720 with Android JellyBean")
print("[2] Acer Iconia A1-810 / A3-A10 / B1-711 / B1-720 with Android KitKat 4.4.2 or higher")
print("[3] Acer Iconia A1-811 with Android KitKat 4.4.2 or higher")
print("[Q]uit")
selection2 = ""
if python3:
selection2 = input("Enter a selection: ")
else:
selection2 = raw_input("Enter a selection: ")
if selection2 == "q" or selection2 == "Q":
sys.exit(0)
if selection2 == "1":
kitkat = False
elif selection2 == "2":
kitkat = True
device = "Acer Iconia A1-810 / A3-A10 / B1-711 / B1-720 running KitKat"
system_image_target_dir = "/data/local/tmp"
elif selection2 == "3":
kitkat = True
a1_811 = True
device = "Acer Iconia A1-811 running KitKat"
system_image_target_dir = "/data/local/tmp"
else:
print("E: Only 'Y' or 'N' is allowed!")
main()
# End of Add-on for A1 KitKat

Will test soon... :)

Regards,

Nika.

---------- Post added at 11:13 PM ---------- Previous post was at 10:40 PM ----------

I found another error in the python script. The system_image_target_dir, kitkat and a1_811 variables are not globally defined. When running root it would therefore think it's running it with the procedures of the wrong device...

---------- Post added at 11:17 PM ---------- Previous post was at 11:13 PM ----------

I just executed the script again and the bit with "KEYCODE_DEL" doesn't work either. It's not deleting... I guess KEYCODE_DEL is more a backspace? It should be KEYCODE_FORWARD_DEL according to:

http://developer.android.com/reference/android/view/KeyEvent.html

Regards,

Nika.

---------- Post added at 11:53 PM ---------- Previous post was at 11:17 PM ----------

su = os.path.join("bin", "a1", "su")

is also missing from the kitkat / a1 selection...

---------- Post added 28th January 2015 at 12:23 AM ---------- Previous post was 27th January 2015 at 11:53 PM ----------

/system.img.gz'\n

should be without the single quote:

/system.img.gz\n
[Miscellaneous Android Development] martythebrit:
If anyone's interested I just rooted my Acer A3-A20FHD tablet with Kingo ROOT 1.3.0. I know previous versions didn't work, but this one did, it also installed Super SU.
[Miscellaneous Android Development] _Tallis_:
YES!!! You made my day! It's really working! After rooting I updated the SU-Binary with SuperSu, and now I finally have a rooted A3-A20FHD!
[Miscellaneous Android Development] martythebrit:
Nice.. glad it helped someone.. :D
[Miscellaneous Android Development] nikagl:
Hi [MENTION=4139144]Jessooca[/MENTION],

I can imagine, had the same issues. I still haven't rooted the A1-811 (mobile version of the A1-810) on KK. In my case the script now works, ie. it adds su, etc. (only from Ubuntu!!), but it looks like the su tool used does not work on these KK devices. For the Acer Liquid S1 I had similar issues, and fixed it by using SuperSU instead of Superuser, but I haven't had time yet to add it to the .toolkit.py and try it. As soon as I have something, hopefully somewhere beginning of next week, I will share it with ya'all.

Regards,

Nika.
[Miscellaneous Android Development] kazzxtrismus:
Use an "ubuntu usb OS" to root from scratch.. Its easier than many expect

SuperSU is better than Superuser imho anyway
[Miscellaneous Android Development] Any PlayStore:
Hello everyone. I have a few questions? Looking forward to your help.

1. How to know B1-A71 was Unlock Bootloader?

2. How to root B1-A71? [system.img.gz] Link die

3. How flash recovery?

4. How to flash stock rom? How to update kitkat for A1-B71?

many thanks
[Miscellaneous Android Development] Optimissimus99:
B1 a71 can be unlocked via [MENTION=5889030]FireDiamond[/MENTION]'s way. Then you just need to flash the SuperSu ZIP via CWM
[Miscellaneous Android Development] nikagl:
Hi all,

I have done several changes to the toolkit. I have tested it on my A1-811 and most of it works fine as far as I can see. Changes were only to the root from scratch Python script, so will not affect the .exe when running it in Windows.

Note that most changes were done for A1-811. If used on other devices, please check within this thread whether that device would be included in the changes. SuperSU and Xposed are part of the root from scratch process and it should be possible to use that with all devices when rooting from scratch.

Warning1: Mounting r/w doesn't work (need kernel sources for that)

Warning2: I wasn't able to add a working Xposed framework. I did add whatever the recovery installer does, but it doesn't work. Anyone with experience on how to add Xposed? See also my questions in the Xposed thread

Current changes are:

Added time to several of the steps so you can see progress

Added global variables to make sure kitkat mode for A1-811 works

Added correct su binary for a1

Added selection for A1-811 (MTKLogger has different location on screen)

Added selection for SuperSU or superuser

Added selection for Xposed **not working yet**

Added selection to continue automatically (also import the system instead of waiting for enter)

Removed invalid quote and double exit command

Added forward delete of characters to make sure Run command is empty

Added some additional messages during the root process

Uncomment the telnet server check - not sure why it was commented?

You can download it here.

Regards,

Nika.
[Miscellaneous Android Development] entonjackson:
Sorry guys.

I am very busy these days. Little spare time.

Just wanted to let you know, I'm still here.

These problems with the A811 seem to be tough to solve. Specially if you don't own the device yourself.

If you like, i could upload your version on the 1st page, nikagl.
[Miscellaneous Android Development] nikagl:
No worries [MENTION=3392632]entonjackson[/MENTION], I know how it feels. I just wasn't sure whether you'd appreciate me editing your file. If you can share how you compiled it to be executed in DOS/Windows, I can also add the Windows version.

What version number shall we give it? 0.9.0? Should we wait for some others to test it?

Last but not least: anyone any tips on Xposed?

Regards,

Nika.