Related
Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this
I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.
hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..
Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!
Mod. edit: not dev related, moved to general
Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help
well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3
Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"
Terminal: "adb remount", then push again
damn the next bad message "remount failed: Operation not permitted"
You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927
Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me
You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279
now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to
You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled
Okay thank you very much.
now it was successful
To start off I want to say, I am NOT claiming to have created this exploit, I am merely letting people know that it works on the arc.
All credit for this goes to Chainfire and The Android Exploid Crew
The origional thread is here: http://forum.xda-developers.com/showthread.php?t=1044765
Download here
Install the APK and run it.
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
Click to expand...
Click to collapse
Quote posted by jassired
works for me
So just push the apk to the phone, install and you're done?
no need to "push", just stick it on your sd card and install
diggedy said:
no need to "push", just stick it on your sd card and install
Click to expand...
Click to collapse
I get the error thing...and I can't find the effing map where I need to remove stuff....
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Cim_XII said:
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Click to expand...
Click to collapse
What do you mean?
double post :s will use this later
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Cim_XII said:
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Click to expand...
Click to collapse
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
I don't even know what ADB is....that's how much I know...
Cim_XII said:
I don't even know what ADB is....that's how much I know...
Click to expand...
Click to collapse
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
if you get the error for esset you need to remove all the files inside to /data/local/tmp/
press: adb shell
press ls /data/local/tmp
and remove one by one the files as my example:
$ ls /data/local/tmp/
ls /data/local/tmp/
Superuser.apk
Gingerbreak
runscript
sysrun
$ rm /data/local/tmp/Superuser.apk
rm /data/local/tmp/Superuser.apk
$ rm /data/local/tmp/Gingerbreak
rm /data/local/tmp/Gingerbreak
$ rm /data/local/tmp/runscript
rm /data/local/tmp/runscript
$ rm /data/local/tmp/sysrun
rm /data/local/tmp/sysrun
and now try again with app and may it works (in my case, works)
dh2311 said:
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
Click to expand...
Click to collapse
maybe I should've mentioned I'm on a Mac computer with no access to windows....damn, this is so frustrating....
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
dh2311 said:
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
Click to expand...
Click to collapse
kewl, and the exact commands is in post #1 right?
so this root's the OS, title is confusing, does it enable fastboot? allow you to flash custom roms?
should be....
dh2311 said:
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
Click to expand...
Click to collapse
did exactly what you said, but get the message
adb: permission denied
No does not enable fastboot
As I've seen a few people around having some checksum erros, I decided to write a small HOWTO.
!!!
The most important information needed to recover from a bricked device is the UID
If your device is not bricked and you read this thread ensure that you have saved your UID!
!!!
Because some people do not read big red text, here it is once again:
GET YOUR UID even if your device is not bricked.
If you need help please contact me with PM or ask for help in this thread.
If your device does not boot anymore it may display the following checksum erros:
"LNX checksum error" - when trying to boot into normal mode
"SOS checksum error" - when trying to boot into recovery (VOL- + Power pressed)
<CASE 1> SOS checksum error
Steps:
- Switch off your device by pressing power for ~8sec
- Switch on your device and boot into normal mode
- If LNX checksum error is displayed, stop here and see <CASE 3>
- Download itsmagic (see this thread). Extract "itsmagic" to the tools folder of android sdk.
- Connect your device to your PC (Windows: drivers can be obtained from Acer website)
- If not already done, get your UID using Method 1 of "How to get the UID"
- If not already done, get a dump of mmcblk0_start (see "How to get a dump of mmcblk0_start")
- In the command window type:
Code:
adb push itsmagic /data/local
adb shell
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
exit
- If everything went fine you should see some output of itsmagic
- Reboot and check if you can boot again
- Store your UID and mmcblk0_start to some safe place
Possible reasons for this error
- You tried to install a new recovery without calling itsmagic before
- You have not remove /system/etc/install-recovery.sh
- Your recovery partition is corrupt
<CASE 2> LNX checksum error
Steps:
- Switch off your device by pressing power for ~8sec
- Switch on your device and boot into recovery by pressing VOL- + Power
- If SOS checksum error is displayed, stop here and see <CASE 3>
If you have stock recovery:
- If not already done, get your UID using Method 2 of "How to get the UID"
- Apply an official OTA, see this thread
If you have thor's CWR:
- If not already done, get your UID using Method 1 of "How to get the UID".
- Select "reboot system now"
If you have any other recovery (that does not have itsmagic integrated):
- If not already done, get your UID using Method 1 of "How to get the UID". If Method 1 does not work, try Method 2
- DO NOT apply any official update.zip . Otherwise you will end up in <CASE 3>
- send me a PM or ask for help in this thread.
Possible reasons for this error
- You tried to install install a new kernel / stock update.zip without calling itsmagic (will not occur with thor's CWR)
<CASE 3> SOS and LNX checksum error
- If available, upload the "mmcblk0_start" dump to some file hoster (e.g. dropbox)
- Send me a PM with your UID and a link to "mmcblk0_start"
- If you do not have your UID: DO NOT connect your device to your PC:
- Pray that you are able to recover the UID from a PC the Iconia was already connected once.
- Windows: Try Method 2 of "How to get the UID" but DO NOT connect your device to your PC.
- Linux/Mac: Check old syslogs for messages where your device was connected to your PC (normally some "usb " kernel messages)
Possible reasons for this error
- You tried to install a new kernel athough you already have a SOS checksum error
- You tried to install a new recovery altough you aleady have a LNX checksum error
How to get the UID
Method 1
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb devices
and press RETURN
This will output something like this:
Code:
List of devices attached
370014740c00594 device
The number is your UID.
- Save this number somewhere it won't get lost
Method 2
- Connect your device to your PC and ensure that drivers are properly installed (Windows: Can be downloaded from Acer website)
Windows:
Download this tool (download link is nearly at the end of the page):
- Open the tool
- Sort after VendorID
- Find all devices with VendorID = 0502 and ProductID = 3325. Check the "Serial number" column for these devices.
Linux:
Call (as root) and see the iSerial field for Iconia.
Code:
lsusb -v
Mac:
- Should be visible in system profiler. Sadly I don't own a mac. So if anyone can help me out with this?
How to get a dump of mmcblk0_start
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb shell
su -
dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start
exit
exit
adb pull /sdcard/mmcblk0_start .
- This will create a file "mmcblk0_start" in the tools folder of your android-sdk.
- Copy this file to some safe place
How to install ADB
1. Download android SDK from here. Windows: Download the .zip file instead of the exe file.
2. Extract android SDK somewhere
3. Open a command shell:
- Windows: Press Winkey+R . Some small window appear. Enter "cmd" and click ok. A black command promt window will open.
- Linux/Mac: Open a terminal window
4. "cd" to the "tools" folder of the android sdk by typing the following in the command shell:
- Windows:
Code:
cd "<path to tools folder>"
Sample:
Code:
cd "c:\android\android-sdk-windows\tools"
- Linux/Mac:
Code:
cd /path/to/tools/folder
5. Ensure that your device is connected, that drivers are installed and that USB debugging is enabled (on Iconia: Settings->Applications->Development->USB Debugging)
reserved for me
Im just asking, in case3 u need dump of mmcblk0_start ,but what if dont have it, only UID?
Should i make dump of mmcblk0_start just in case to be insured that evrything will be ok if smth happens?
Any way thks fo tutorial)
Glebaka said:
Im just asking, in case3 u need dump of mmcblk0_start ,but what if dont have it, only UID?
Should i make dump of mmcblk0_start just in case to be insured that evrything will be ok if smth happens?
Any way thks fo tutorial)
Click to expand...
Click to collapse
Having a dump in <case 3> makes everything easier. But it is not mandatory. Nevertheless it's generally a good idea to backup mmcblk0_start.
btw: thor's CWR will backup mmcblk0_start since version 1.2 if you do a nandroid backup.
sc2k said:
How to get a dump of mmcblk0_start
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb shell
dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start
exit
adb pull /sdcard/mmcblk0_start .
- This will create a file "mmcblk0_start" in the tools folder of your android-sdk.
- Copy this file to some safe place
Click to expand...
Click to collapse
Hi there,
after i typed "dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in the adb shell i got an invalid argument error:
Code:
if: illegal argument combination or already set
What i should do?
when i get a SOS checksum error and a LNX checksum error,can i copy files from pc to a500 device? how?
dmue said:
Hi there,
after i typed "dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in the adb shell i got an invalid argument error:
Code:
if: illegal argument combination or already set
What i should do?
Click to expand...
Click to collapse
Sorry, there was a typo. Should be correct now
Thanks for the hint.
kimycai said:
when i get a SOS checksum error and a LNX checksum error,can i copy files from pc to a500 device? how?
Click to expand...
Click to collapse
The procedure for this case is much more complex. If you do something wrong, it is getting even more complicated.
I will not publish details currently, sorry. If you get this error, contact me.
As soon as some tools are finished i will update the OP.
Sent from my HTC Desire using XDA App
sc2k said:
Sorry, there was a typo. Should be correct now
Thanks for the hint.
Click to expand...
Click to collapse
Ah ok, thx.
thank you sc2k!
sc2k said:
The procedure for this case is much more complex. If you do something wrong, it is getting even more complicated.
I will not publish details currently, sorry. If you get this error, contact me.
As soon as some tools are finished i will update the OP.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
really？
waiting……
Hi
After I typed "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in adb i got: "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start /dev/block/mmcblk0: cannot open for read: Premission denied"
What i done wrong?
Raphaello said:
Hi
After I typed "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in adb i got: "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start /dev/block/mmcblk0: cannot open for read: Premission denied"
What i done wrong?
Click to expand...
Click to collapse
You need to be root
Type
Code:
su -
before.
I will update the guide
Thanks but it's doesn't work yet. I have root access. I tried type "su-" but it is the same message "cannot open for read: Premission denied". I install usb drivers and the others think from guide hmmmm....
Raphaello said:
I tried type "su-" but it is the same message "cannot open for read: Premission denied".
Click to expand...
Click to collapse
Did you type su- or su - (notice the space between su and -)?
Also you'll have to confirm su permissions on the tablet.
I typed "su -" with space between su and -
I have USB debugging turn on
When i type "su -" it say "Premission denied"
I really sorry for problem and thanks you for trying to help me
Is your device rooted? Because it has to be.
And if it's rooted did you notice a superuser app popping up after you run the command.
What a shame, I did not notice a superuser app popping up :/ Now it's ok. Thank You very much. I must learn a lot. Only think was taht I can't pull this file to my computer via "adb pull /sdcard/mmcblk0_start" but i copy it directly from device Now I feel safe.
Thanks a lot guys
Well, actually you should be able to dump directly to adb without copying to device to save some time.
like dd if=/dev/mmcblk0p1 count=X bs=Y
but without specifying of= or using of=-
and don't forget to redirect it to file. like "adb shell "dd if ..." > dump_p1". Not sure it will work fine, but I used it once on another device to dump block device image.
i download the android sdk zip file, but is seems that the "tools" folder doesn't include the adb executable file , how should i do?
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
hello
as you see i broke my XT1572 and i can't connect wih any networks, also i cant do the emergency calls
i search for answer long time, flash firmware a thousand times, but now i find that:
https://forum.xda-developers.com/moto-g-2014/help/solved-brlost-signal-fastboot-erase-t3162580
https://forum.xda-developers.com/moto-g/help/hob-dhob-fsc-dumps-moto-g-lte-t3288862
maybe you know from where i can download this files for XT1572, please send me a link
if not and you have got rooted XT1572 (best EU one SIM version but i can try other version), you can do 3 partition dumps (hob, dhob,fsc)
on my phone this partitions are empty
how to do dump:
adb shell
su
dd if=/dev/block/platform/f9824900.sdhci/by-name/dhob of=/data/local/tmp/dhob.img
dd if=/dev/block/platform/f9824900.sdhci/by-name/hob of=/data/local/tmp/hob.img
dd if=/dev/block/platform/f9824900.sdhci/by-name/fsc of=/data/local/tmp/fsc.img
chmod 777 /data/local/tmp/dhob.img
chmod 777 /data/local/tmp/hob.img
chmod 777 /data/local/tmp/fsc.img
exit
exit
dump files to local computer:
adb pull /data/local/tmp/dhob.img dhob.img
adb pull /data/local/tmp/hob.img hob.img
adb pull /data/local/tmp/fsc.img fsc.img
thats all, if you send me this files and this will work, i will return a favor
the same thing happened to me, fatal mistake
kkkonrad said:
hello
as you see i broke my XT1572 and i can't connect wih any networks, also i cant do the emergency calls
i search for answer long time, flash firmware a thousand times, but now i find that:
https://forum.xda-developers.com/moto-g-2014/help/solved-brlost-signal-fastboot-erase-t3162580
https://forum.xda-developers.com/moto-g/help/hob-dhob-fsc-dumps-moto-g-lte-t3288862
maybe you know from where i can download this files for XT1572, please send me a link
if not and you have got rooted XT1572 (best EU one SIM version but i can try other version), you can do 3 partition dumps (hob, dhob,fsc)
on my phone this partitions are empty
how to do dump:
adb shell
su
dd if=/dev/block/platform/f9824900.sdhci/by-name/dhob of=/data/local/tmp/dhob.img
dd if=/dev/block/platform/f9824900.sdhci/by-name/hob of=/data/local/tmp/hob.img
dd if=/dev/block/platform/f9824900.sdhci/by-name/fsc of=/data/local/tmp/fsc.img
chmod 777 /data/local/tmp/dhob.img
chmod 777 /data/local/tmp/hob.img
chmod 777 /data/local/tmp/fsc.img
exit
exit
dump files to local computer:
adb pull /data/local/tmp/dhob.img dhob.img
adb pull /data/local/tmp/hob.img hob.img
adb pull /data/local/tmp/fsc.img fsc.img
thats all, if you send me this files and this will work, i will return a favor
Click to expand...
Click to collapse
did you find how to solve it?
It seems least people using EU rom
I think other stock roms may work