Database Users

Replacing HTC apps with ANDROID ones

Hi,
After reading this thread and learning that you CAN replace HTC's apps with stock Android ones, I have started messing around to see what other apps I can / should change. I'll use this thread as kind of a log, so if I mess things up I can come back and see where I went wrong. Fellow noobs can surely use it too!
I am using SDK in Ubuntu, but the procedure should be pretty similar in Windows.
First, follow the Unlockr's method to root your phone.
Download a stock Android rom and extract its /system/apps folder inside /sdk/tools. I named the folder "Apps-stock
Check if Ubuntu recognises your phone:
Code:
./fastboot devices
Load the recovery image and mount the system:
Code:
./fastboot boot cm-hero-recovery.img
./adb shell mount /system
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on

Nice one!
Please keep us informed!

Thanks for this thread.
Post moved to a more appropriate topic :
http://forum.xda-developers.com/showthread.php?p=4477971#post4477971

Thanks for setting this thread up!
Firstly, you should probably say in the first post that everyone should do a Nandroid backup first - it's saved my bacon. Might be an idea to link to the files, too?
Second, I've got a problem trying to run this method. I removed the original calendar.apk and .odex without any problems, and copied the new one over, but on rebooting, it wasn't in the list of applications anywhere. I browsed there in Astro and opened the file, which gave me an option to install it - which then gave an error of "Calendar could not be installed on this device".
I'm running the MoDaCo 2.1 custom ROM and using the calendar.apk from this thread.
Thanks for your time!

fastboot
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?

dragonflyFZX said:
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
Click to expand...
Click to collapse
fastboot and adb are executables you get from the Android SDK - see here.
This thread does require your phone to be rooted, though, which would require you to have already used adb at least once....

frandavid100 said:
........
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Click to expand...
Click to collapse
how about simply replacing those files using a file explorer (like linda)? possible, or would that screw up my system?

Recovery 1.52 - 1.6x? How?

I have searched for the last 30 mins and can't seem to find what the latest recovery image is, or how to upgrade my phone to it.
I want to get the image that allows the use of ext4 to test out the latest Fresh toast and can't seem to find it.
Anyone got a link or a quick how to?

http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Every version including 1.6.2 and instructions in that link.

Bielinsk said:
I have searched for the last 30 mins and can't seem to find what the latest recovery image is, or how to upgrade my phone to it.
I want to get the image that allows the use of ext4 to test out the latest Fresh toast and can't seem to find it.
Anyone got a link or a quick how to?
Click to expand...
Click to collapse
copy the .img file to your SD card
unmount the sd card from the PC
open CMD
type
abd shell
su
flash_image recovery /sdcard/recovery_filename.img
reboot.

danknee said:
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Every version including 1.6.2 and instructions in that link.
Click to expand...
Click to collapse
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.6.2.img
reboot

Jus10o said:
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.6.2.img
reboot
Click to expand...
Click to collapse
Beat me to it. Yeah, just do that. Keep in mind you need to put it on the root of your SD before that.

Thanks all, got it.

I'm trying to update my recovery using the steps above but I keep getting " 'adb' is not recognized as an internal or external command, operable program or batch file." o_0
Edit: Nevermind, I got it.

[GUIDE] How to fix the GPS issue on CM and others

Hi!
The GPS - issue (GPS searching forever, no fix, status bar does not even show the gps-icon) can be fixed by wiping the efs data.
This data is stored in partition 13 and partition 14 on the G2/DZ/DHD/MT4G.
Update 18.04.2011:
Given the tragic end of a phone because of a mistyped dd-command (see this post) i decided to create a tool to replace the original instructions. I leave the original instructions for people who are confident with dd and don't want do download something to get the job done.
So just to make this clear: Method 1 and Method 2 are alternative ways to do the same thing. I would recommend that you do it using Method 1 but anyways, don't do Method 1 and 2.
Method 1: Removing the efs-data using vision_wipe_efs:
Download vision_wipe_efs from vision_wipe_efs_01.zip (md5sum 7bced5385509a58a7c8b0a54d38a6897)
Remark: The program vision_wipe_efs will create backups of the partition 13 and 14 on the sdcard using the name "/sdcard/part13backup-<time>.bin" and "/sdcard/part14backup-<time>.bin" so make sure that the sdcard is mounted to the phone.
Unpack the zip file to a directory on your PC. Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute this command (as always: do not type the # it only indicates the root prompt in the shell or the $ as the prompt in a non-root shell):
Code:
# adb push vision_wipe_efs /data/local/tmp/
You can also use other ways to copy the file to this directory but the following instructions assume that it is there.
Get a root shell on your phone (either using adb shell or a terminal app) and then use the following command:
If your prompt is not # but $ then first do:
Code:
$ su
and answer the question of Superuser. (Well you should all know this by now )
Code:
# stop rmt_storage
# chmod 777 /data/local/tmp/vision_wipe_efs
# /data/local/tmp/vision_wipe_efs
# reboot
Method 2: Removing the efs-data using dd (BRICK RISK):
To do this you have to get a root shell on your phone (either using adb shell or a terminal app) and then use the following command (as always: do not type the # it only indicates the root prompt in the shell or the $ as the prompt in a non-root shell)
If your prompt is not # but $ then first do:
Code:
$ su
and answer the question of Superuser. (Well you should all know this by now )
Code:
# stop rmt_storage
# dd if=/dev/zero of=/dev/block/mmcblk0p13
# dd if=/dev/zero of=/dev/block/mmcblk0p14
# reboot
After you followed Method 1 or 2 should have your GPS back working.
To wipe the efs is general a good idea if you switched radio-firmware or the ril-libs (which might happen when you switch from one rom to another)
have fun - Guhl

guhl99 said:
Hi!
The GPS - issue (GPS searching forever, no fix, status bar does not even show the gps-icon) can be fixed by wiping the efs data.
This data is stored in partition 13 and partition 14 on the G2/DZ/DHD/MT4G.
To do this you have to get a root shell on your phone (either using adb shell or a terminal app) and then use the following command (as always: do not type the # it only indicates the root prompt in the shell or the $ as the prompt in a non-root shell)
If your prompt is not # but $ then first do:
HTML:
$ su
and answer the question of Superuser. (Well you should all know this by now )
HTML:
# stop rmt_storage
# dd if=/dev/zero of=/dev/block/mmcblk0p13
# dd if=/dev/zero of=/dev/block/mmcblk0p14
# reboot
After this you should have your gps back working.
To wipe the efs is general a good idea if you switched radio-firmware or the ril-libs (which might happen when you switch from one rom to another)
have fun - Guhl
Click to expand...
Click to collapse
please be careful with dd. (this isn't for you, op, but for the other hamfisted folks that try to fix things)
why are there HTML backets in your post ?

Perhaps it should be mentioned to do the inverse beforehand.. just to play it safe.
dd if=/dev/block/mmcblk13 of=/mnt/sdcard/p13backup
dd if=/dev/block/mmcblk14 of=/mnt/sdcard/p14backup
I'd still stop that service beforehand..
although I must say.. my gps is ****ing awful after this.. but meh.. it could just be the time/place/conditions.. and by awful.. I mean.. it locks on.. with an error of 305 ft.. sorta screwy.. nothing is as bad as when I tried to modify the gps.conf to use other servers (like my hd2).. i got a 2-3 mile error with 10 sat locks..
oh.. but this DID fix erratic gps behavior. and I'm betting that the accuracy will even out after a couple reboots/gpslocks.

ohgood said:
please be careful with dd. (this isn't for you, op, but for the other hamfisted folks that try to fix things)
why are there HTML backets in your post ?
Click to expand...
Click to collapse
Of course you are right. Be carefull to write the dd commands correctly. Later i will put a tool on my wiki that wipes the partitions without the use of dd.
Sent from my HTC Vision using XDA App

Did anybody use gps status app to download new gps data after trying this?
Sent from my HTC Vision using XDA Premium App

Alright, it worked, thanks. The notification even shows up in the notification bar now!
Sent from my SilverBullet "HTCDesireZ running CM7"

Just out of curiosity, what is the EFS data?

All I did to fix mine was update the kernal.

theSpam said:
Just out of curiosity, what is the EFS data?
Click to expand...
Click to collapse
Temporary (in our case) radio configuration data.

Nonentity018 said:
All I did to fix mine was update the kernal.
Click to expand...
Click to collapse
Lucky you. Sometimes updating, downgrading radio or kernel can lead to the effect that the systems re-initializes the temporary radio data.

Thanks for the tip but I am still unable to have my GPS work in CM after using this. I had no GPS problems with sense roms but have yet to get GPS working on any of the CM ones. I have tried reflashing numerous times with complete data, cache and system wipes alongside multiple radio/kernel reflashes but this just never works for me . Hopefully future releases of CM somehow get it working otherwise I will have to get back to sense
EDIT: Wow, as soon as I post this I decide to try reflashing my kernel one more time and lo and behold the GPS starts magically working! I did nothing different than what I hadn't already been doing but whatever I'm not complaining

What should be the output of the dd commands?
I got something about not enough space on the device error. I still continued with inputting the codes mentioned in the first post. Upon reboot GPS stopped working on me, it was working previously but really spotty. Ill give it some time until I flash CM7 final.

boost3d23 said:
What should be the output of the dd commands?
I got something about not enough space on the device error. I still continued with inputting the codes mentioned in the first post. Upon reboot GPS stopped working on me, it was working previously but really spotty. Ill give it some time until I flash CM7 final.
Click to expand...
Click to collapse
The errors messages that there is no space left on the device are OK.
The dd commands just writes 0's into the output partition until it is full.

Hello to all,
I've read several posts and tried several things now with no success.
I'm currently on CM7 Stable
Radio 12.28h.60.140fU_26.06.02.27_M
Kernel 2.6.32.28-cyanogenmod_g4f4ee2e [email protected]#1.
GPS symbol shows when launching navigation, but no result. It keeps looking for the location. I wiped the Radio data several times as suggested.
Last thing on my list would be flashing a new radio. Since I've read that it can brick the phone I'm quite cautious.
Any other suggestions?

This is how you tell if your GPS is gonna work or not even before booting the os. If you get that small vibration after the normal bootup vibration, your GPS will not work. Been doing research on this.

Staudamm said:
Hello to all,
I've read several posts and tried several things now with no success.
I'm currently on CM7 Stable
Radio 12.28h.60.140fU_26.06.02.27_M
Kernel 2.6.32.28-cyanogenmod_g4f4ee2e [email protected]#1.
GPS symbol shows when launching navigation, but no result. It keeps looking for the location. I wiped the Radio data several times as suggested.
Last thing on my list would be flashing a new radio. Since I've read that it can brick the phone I'm quite cautious.
Any other suggestions?
Click to expand...
Click to collapse
Changing radio solved my GPS issues, check my sig for the one I'm using.
I have changed my radio a few times since getting my DZ and have never had any problems. Just make sure you read the instructions a couple of times and check the md5 sum of the download and you will be fine.

I fixed it by uploading the gps.vision.so to /system/lib/hw/
But I used ADB instead of root explorer by using the following commands:
adb remount
adb push gps.vision.so /system/lib/hw
adb reboot
Originally Posted by slashjiang View Post
I tried to solve this issue by myself.
I extract the nightly build #34 (which GPS works in my G2), and compare it with #38 (GPS doesn't work), I found the file /system/lib/hw/gps.vision.so is different in both ROM. so, I tried to replace this file in my G2 with the same file which is from #34 by using Root Explorer, after reboot, GPS works. The icon in the notification bar appears.
Run GPS status, satellite signal found.
Run Google Maps, working too.
The gps.vision.so file from #34 is attached in ZIP format. Just download it, extract, and copy it to /system/lib/hw/ and replace original one. Have fun.
Hopes Cyanogen Team solve this issue. Thanks.
Click to expand...
Click to collapse

Just wanted to add that these commands didn't work for me. I replaced the kernal with pershoots and it fixed the problem.

Thank you. This worked for me after replacing gps.vision.so and I'm a total n00b. Much appreciated!

Thanks this worked for me.
Sent from my HTC Vision using XDA App

[Q] Copying nandroid backups to MAC

I am sure this has been asked and answered, but I am not finding the answer. Anyone have a good method for backing up CWM backups to MAC? I know the CWM backups are stored at /data/media/clockworkmod which is not accessible to the MAC. I guess I could copy them to /data/media/0 and then access them from my mac. I guess I could also use ADB, but am looking for something simpler and less data manipulation. If this has been answered, please link me.

1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn

Pirateghost said:
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Click to expand...
Click to collapse
I have done it with ADB. Was hoping for something more elegant. Thank you.
Sent from my Nexus 7 using xda app-developers app

Pirateghost said:
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Click to expand...
Click to collapse
Could you please write it in a more specific way? I'm a noob
I explain what I did:
I opened the terminal and I went in the folder were I keep the fastboot and adb etc..
I tried first with "./adb pull.." but nothing happened (aka: -bash: ./adb: No such file or directory)
Then I tried "./adb-mac pull.." and it didn't work either but I got the following long message:
"Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
etc..."
I tried both commands at first with the mobile on, then I reset it and I went in recovery mode with the same results..
I'm going insane, I even tried to copy the whole folder of clockworkmod with my backup to another folder, but I couldn't see it with my computer.
I'm running mac OS X, I could eventually try also to my PC windows 7.. I just need to copy my backup to a safe place :crying:

After the pull command you need to tell it what to pull
Sent from my Galaxy Nexus

Pirateghost said:
After the pull command you need to tell it what to pull
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry Pirateghost, I meant that I wrote as you said:
./adb-mac pull /data/media{0, clockworkmod, twrp}
and I got just the long message from the Terminal and it doesn't work (even when using ./adb without the "-mac")
edit: ok I solved it:
I used this and it seems working (finally)
./adb-mac pull /data/media clockworkmod

ziovelvet said:
Sorry Pirateghost, I meant that I wrote as you said:
./adb-mac pull /data/media{0, clockworkmod, twrp}
and I got just the long message from the Terminal and it doesn't work (even when using ./adb without the "-mac")
edit: ok I solved it:
I used this and it seems working (finally)
./adb-mac pull /data/media clockworkmod
Click to expand...
Click to collapse
the {0, clockworkmod, twrp} was to indicate that you can pull ONE of those folders at a time, or pull /data/media and get ALL of them at once

[HOW-TO] Lenovo IdeaTab A1000 Rooting

HOW TO ROOT YOUR LENOVO IDEATAB A1000​
<DISCLAIMER>​
By attempting these steps, your warranty will be void. Even worse than that, it might cause crashes, freezes, random explosions, 2nd degree burns, or even turn your beloved tab into $100+ paperweight. What works on mine might not work on yours, so don't attempt if you don't know what you're doing. Do at your own risk. Corrections are welcome. I must admit that I'm not an expert, so any info I posted might be wrong, and I can't offer you much help. I'm not responsible for anything arising from the use of this how-to. I can only wish you good luck.
<WHY ROOT?>​
- Without root or OTA upgrades (at time of writing, Indonesian customers still can't get it), you'll be stuck with ~500MB internal memory. That's annoying.
- You're stuck with the default IO scheduler (cfq) and governor (hybrid, haven't heard that one..)
- You have an incredibly large amount of bloatware you can't get rid of, in that already cramped up internal storage
- Did I mention freedom?
<REQUIREMENTS>​
This method is originally used to root Acer Iconia B1-A71. Somehow I noticed that the two actually has the same chipset, MTK8317 (if it really was relevant ). So I tried the method, and through sheer n00b's luck, it worked like a charm!
Lenovo IdeaPad A1000-G --> 4GB storage, 2G/EDGE. This method haven't been tested on A1000-T/F, different storage cap (16GB, etc.) or other variants, but it should work with slight modification. Screenshots of my specs are attached below. Remember, proceed at your own risk!
A Linux System. Never tried on Windows or Mac. I personally used Linux Mint 15. The source post uses Ubuntu.
working ADB (android-tools-adb). You can get this from synaptics, apt-get, etc. If your system can detect adb devices, you should be fine.
Superuser Binary
Busybox Binary (You can get these two from the links on original post. XDA says noobs can't post links :'( )
ORIGINAL THREAD
<CREDITS>​
XDA Senior Member entonjackson, for writing such a noob-friendly how-to for rooting Acer Iconia B1-A71 and for allowing me to use it for this how-to.
XDA Member alba81, for discovering the method as acknowledged on the original post by entonjackson
All awesome gurus on XDA which I can't mention one by one.
<THE STEPS>​
1. Extract the android sdk to your home folder, e.g. a user named Bob will use like /home/bob
2. Open a terminal
3. Now plug your A1000 into your machine and turn on Debugging Mode (Go into Settings -> Developer Tools, turn on Developer tools, then turn on USB Debugging Mode)
4. Now back at the keyboard of your Linux machine in your terminal type:
Code:
sudo adb devices
The output should be something like:
Code:
123456789ABCDEF device
If it's not, google for it. Somehow your Linux hasn't detected the A1000, although the android sdk for Linux brings all needed drivers with it.
If your device was found, congratulations. The adb connection between your linux machine and your tablet is intact.
5. Now extract the downloaded busybox archive to your home folder, in it there should be a busybox binary. So Bob does:
Code:
sudo ./adb push /home/bob/busybox /data/local/tmp
Code:
sudo ./adb shell
Code:
chmod 755 /data/local/tmp/busybox
6. You should copy the busybox binary into a directory where you can access it as a plain non-root user on the tablet. We need this binary. so we can apply unix tools like telnet, dd, cat, etc. But for now we need it to establish a telnet session between our tablet and our linux machine.
(This point is written on original post. Seems important, but as soon as I finished step 5, I can use those tools)
7. Dial *#*#3646633#*#* to enter Engineer Mode
8. Go to Connectivity -> CDS Information -> Network Utility
9. type the following command:
Code:
/data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
Advice from original poster: copy and paste it from the browser on your tablet, because dependent on which keyboard app installed, this can be freakin tricky. In the next step you will learn, why it's so important why this command should be correct.
10. Tap on Run. You won't get any feedback, so you will never know if the entered command runs properly or not. That's why you should make sure the command is ok.
Now we have started our telnet server on the tablet.
11. Back in the terminal type:
Code:
/data/local/tmp/busybox telnet 127.0.0.1 1234
If you now get an error like couldn't find busybox or something, then either adb push failed or you forgot to chmod, in step 5
12. Now enter:
Code:
cat /proc/dumchar_info
You should get a bunch of lines, try to find a line containing the partition named android
{..... partition list .....}
android 0x0000000028A00000 0x00000000020E8000 2 /dev/block/mmcblk0p3
{..... partition list .....}
13. We will create a dump of our android system. This is the point where different variants *MIGHT* have different parameters. This step is important, as wrong parameter will result in unmountable image.
Stop. Take a deep breath. If you're not familiar with dd, find a good doc of it. There's a plethora of them.
Get yourself a programmer's calculator (Linux Mint 15 has one built in).
Here's what you'll do :
Convert the hex number on the 3rd column into decimal. In my case (0x20E8000) will yield 34504704. Divide by 4096. The result (8424) goes to the skip parameter.
Convert the hex number on the 2nd column. In my case (0x28A00000) will yield 681574400. Divide by 4096. The result (166400) goes to the count parameter.
So the full dd command will look like :
Code:
dd if=/dev/block/mmcblk0 bs=4096 skip=8424 count=166400 | gzip > /cache/system.img.gz
Do a full sanity check before hitting enter! It will take about 5 minutes.
14. After it's finished we must make the image readable for adb, so we do:
Code:
chmod 777 /cache
and
Code:
chmod 777 /cache/system.img.gz
15. Leave the telnet, and then adb shell session by:
Code:
exit
Code:
exit
16. Now we pull our image by
Code:
sudo adb pull /cache/system.img.gz
wait 1-2 minutes.
It should be then located inside /home/bob. It did for me. If not, do a search . It should be a .gz, extract it right there (or /home/bob if it isn't there)
17. Now we need to modify our system image by adding the tiny but helpful su binary. Extract the SU binary to /home/bob.
18. We create a folder where we will mount our system image to. To create it do:
Code:
sudo mkdir /media/a1000
19. Now we mount it:
Code:
sudo mount -o loop /home/bob/system.img /media/a1000
if it fails, then you entered wrong parameters on step 13
20. Now we copy our SU binary to our mounted system image:
Code:
sudo cp /home/bob/su /media/a1000/bin
21. the su binary needs to have the proper rights to make it usable, so we 'suid' it with:
Code:
sudo chmod 06755 /media/a1000/bin/su
22. Let's unmount our baby by:
Code:
sudo umount /media/a1000
and because bob doesn't like a messed up system, he does:
Code:
sudo rm -rf /media/a1000
because he hopefully won't need it anymore.
23. We have to gzip it again to bring it back to where it belongs to. this we do by:
Code:
cd /home/bob
Code:
gzip /home/bob/system.img
24. So here we are now, we made it to the final Boss fight! The next steps are dangerous and should be performed with caution. We copy back our modified system image, which can brick your device, if you do a mistake! Enter adb shell again :
Code:
sudo adb shell
25. Remove the old boring image:
Code:
rm /cache/system.img.gz
26. Leave adb shell
Code:
exit
27. copy our cool new system image containing the su binary:
Code:
sudo adb push /home/bob/system.img.gz /cache
28. Enter adb shell again
Code:
sudo adb shell
29. Usually the telnet server on the tablet is still running, at least in my case it's been like that. That's why we can directly connect to the telnet server with:
Code:
/data/local/tmp/busybox telnet 127.0.0.1 1234
If this doesn't work, then obviously your telnet server isn't running anymore. So on your tablet if the telnet command is still entered (see step 9), tap on Run again and repeat step 29.
30. Now this is the most dangerous step in this how to (no it wasn't the mkdir one). You can copy following command to make sure everything is fine and paste it into your telnet session on your linux terminal.
<WARNING! SANITY CHECK! MAKE SURE *ALL* THE DD PARAMETERS MATCH THE FIRST DD (STEP 13) OR YOUR A1000 WILL TURN INTO A VERY EXPENSIVE PAPERWEIGHT!>
Code:
[B]/data/local/tmp/busybox zcat /cache/system.img.gz | dd of=/dev/block/mmcblk0 bs=4096 seek=8424 count=166400[/B]
After 1-2 minutes you're done, if your tablet or pc or yourself didn't catch fire, everything's fine.
31. Leave telnet / adb shell by doing
Code:
exit
Code:
exit
32. Reboot your A1000 via ADB, then exit
Code:
sudo adb reboot
Code:
exit
33. Unplug your tablet from PC
34. Install Superuser (No, not SuperSU, cause it won't work!). I personally use Superuser by ChainsDD, from Play Store
35. Be lucky. Your tablet and thus you are now free!
Don't forget to hit thanks, if this helps ​

hi, after step 13 (i double checked the command), i get this error
Code:
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
I have the WiFi 4G version

Im too stuck in step 13.....nothing wrong with the script, can u give me a solution?
Im using A1000G also

@ts
Your guide work perfectl, in windows enviroment but mount step still need linux,
I've question are you using DirectoryBinding? Mine always close when playing Real Racing, its very annoying
You have suggeztion or alternative for DirectoryBinding?

Root with Windows ?
Hi,
I am a new member because i bought this tblet but i can't root. I don't have a linux environment, so there is a solution with W8 Pro 64 ?
Thanks a lot for you help,

ulisez said:
hi, after step 13 (i double checked the command), i get this error
Code:
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
I have the WiFi 4G version
Click to expand...
Click to collapse
have you chmod-ed the busybox (or is the chmod successful without error)? Try chmod-ing the /cache before attempting step 13. It seems that you still don't have access to the NAND device (mmcblk0). Have you updated firmware via OTA?
artonelico said:
Im too stuck in step 13.....nothing wrong with the script, can u give me a solution?
Im using A1000G also
Click to expand...
Click to collapse
Do you encounter the same error message like ulisez had? Could you post the screenshot of the partition list (the lines after you execute dumchar_info)?
rmage said:
@ts
Your guide work perfectl, in windows enviroment but mount step still need linux,
I've question are you using DirectoryBinding? Mine always close when playing Real Racing, its very annoying
You have suggeztion or alternative for DirectoryBinding?
Click to expand...
Click to collapse
I personally use Link2SD by Bulent Akpinar to link apps to 2nd partition on my SDcard.
Letsar said:
Hi,
I am a new member because i bought this tblet but i can't root. I don't have a linux environment, so there is a solution with W8 Pro 64 ?
Thanks a lot for you help,
Click to expand...
Click to collapse
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029

sammymaddog said:
have you chmod-ed the busybox (or is the chmod successful without error)? Try chmod-ing the /cache before attempting step 13. It seems that you still don't have access to the NAND device (mmcblk0). Have you updated firmware via OTA?
Do you encounter the same error message like ulisez had? Could you post the screenshot of the partition list (the lines after you execute dumchar_info)?
I personally use Link2SD by Bulent Akpinar to link apps to 2nd partition on my SDcard.
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
Click to expand...
Click to collapse
Link2SD doesn't link app data, do you have any option?

yes i had same message with ulyses, by the way im from indonesia too can i contact you through chat client?
oh yeah im using windows 7 and using cmd as a terminal in linux
thx before bro

sammymaddog said:
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
Click to expand...
Click to collapse
Ok, i see his toolkit. It's very good. I'll wait

rmage said:
Link2SD doesn't link app data, do you have any option?
Click to expand...
Click to collapse
I'm not sure whether the stock kernel of our devices supports init.d, thus supports CronMod/Data2SD. Lenovo locked our bootloader, and currently there's no way around it. So I personally think, Link2SD method are the best option for now.
Let's give it several months until our dev gurus bring their miracles upon this device

The attached image shows mt6577 Hardware, can u provide the Soc details please

Hi, Can any one upload Lenovo ideatab A1000 system.img

in step 20, it appears you are writing to a /bin directory on the android system. However such a directory is not visible either through shell or the system telnet account.
Do I need to understand something else about android to make sense of this.
regards
vidya

one month gone past but the op seems to be in caves or has bricked the device

STOCK ROM
CAN ANY BODY PROVIDE ME A STOCK ROM OF THIS DEVISE
I HV ROOTED SUCCESSFULLY BY A VERY EASY METHOD
BUT SCREWED UP WHILE UPDATING IT SO PLZ PLZ HELP ME OUT
THE DEVICE BOOTS BUT ALL THE APP CRASHES :crying::crying:

VR.gtmini said:
The attached image shows mt6577 Hardware, can u provide the Soc details please
Click to expand...
Click to collapse
VR.gtmini said:
one month gone past but the op seems to be in caves or has bricked the device
Click to expand...
Click to collapse
sorry to make you wait. I'm a last grader university student, and final project stuffs have got me pinned down. Hope you understand
Actually the SoC is MT8317. For some god-knows reason Mediatek have made this SoC with signatures similar to MT6577. But somehow CPU tweaker correctly detects the SoC (MT8317). Maybe it's the CPU-Z bug?
unknown_world said:
Hi, Can any one upload Lenovo ideatab A1000 system.img
Click to expand...
Click to collapse
zod0070 said:
CAN ANY BODY PROVIDE ME A STOCK ROM OF THIS DEVISE
I HV ROOTED SUCCESSFULLY BY A VERY EASY METHOD
BUT SCREWED UP WHILE UPDATING IT SO PLZ PLZ HELP ME OUT
THE DEVICE BOOTS BUT ALL THE APP CRASHES :crying::crying:
Click to expand...
Click to collapse
I'm uploading the modified .img. Let's pray my old HSPA modem won't catch fire by the morning.
vidyadhara said:
in step 20, it appears you are writing to a /bin directory on the android system. However such a directory is not visible either through shell or the system telnet account.
Do I need to understand something else about android to make sense of this.
regards
vidya
Click to expand...
Click to collapse
I think you got it wrong. The write process does not take place on the device. It's on the loop-mounted .img in /mnt/a1000 on your computer (step 18-19). Cheers!

Here's the ALREADY BUSYBOX-ED .img for Ideapad A1000-G 4GB EDGE version. Hope it helps :
www dropbox com/s/rmpnz7c285t5sqz/system.7z

sammymaddog said:
Here's the ALREADY BUSYBOX-ED .img for Ideapad A1000-G 4GB EDGE version. Hope it helps :
www.dropbox.com/s/rmpnz7c285t5sqz/system.7z
Click to expand...
Click to collapse
Thanks for coming back, could u post the MD5 of the system.7z & system.zip.
Also could u provide simple way/steps to directly flash this .img without extracting existing stock system image
My tab A1000-G

do you have stockROM for lenovo A1000G
I need this :crying:

raffly said:
do you have stockROM for lenovo A1000G
I need this :crying:
Click to expand...
Click to collapse
Don't worry, the above link is a stock Lenovo A1000 G ROM, but with pre-root files having no superuser app. Just extract the .7z file
System.7z MD5: 658CA71AC8A230B244F267513857F9A5