Related
not sure if anyone has seen this but i found it posted in another forum dated june 8 (retail launch date) and no one has commented. i dont know enough to try this out my self but looks promising.
Galaxy Tab Rooting Instructions - ADB Method
These instructions provided me with a permanent root workaround when SuperOneClick, run within Windows 7, repeatedly hung "waiting for device". SuperOneClick elegantly automates the ADB method, but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
The procedure below uses components from SuperOneClick but runs the ADB server and commands from within Linux. In this environment the ADB command "adb devices" correctly reports the attached Galaxy Tab, and other ADB commands work correctly as well. To obtain the needed SuperOneClick components, download SuperOneClickv1.9.1.zip to Linux and unzip it there. The SuperOneClick.exe (which is a Windows executable) will be ignored, but other files (see below) will be pushed to the Galaxy Tab during the rooting process.
I'm indebted to authors at http://pastebin.com/i234U96k and http://rootingdroid.com/ for the hack below. Note that there is a modification to require no dependence on a "cp" command at the ADB shell prompt. For some reason "cp" is missing in /system/bin on my Galaxy Tab.
As always, attempt using this procedure at your own risk. Be specifically aware that you may not be able to "unroot" your Galaxy Tab after using this procedure--ever! This procedure doesn't back anything up from the unrooted device, so if "unrooting" it requires restoring something from such a backup, I'm (and you're) stuck with a permanently rooted device. This condition may interfere with your receiving certain updates or downloading DRM content in the future.
1) Download and install TitaniumBackup and SuperUser onto your Galaxy Tab from the Android Market. Note that SuperUser may not be necessary since there are sources for this app below. I'm including it at this step because I had previously installed it prior to the steps below.
2) Download and unzip SuperOneClickv1.9.1 into some Linux folder of your choice. You can get it at http://shortfuse.org/?page_id=2 near the bottom of the page.
3) Install Android SDK for Linux x86 into your home directory on your Linux box. You can get it at http://developer.and.../sdk/index.html The ADB server will be located in ~/android-sdk-linux_x86/platform-tools.
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
Note that there is an alternative source for Superuser.apk and su at http://www.rootingdroid.com at the "Download" link in Step 2.
5) Enter the Linux directory containing the ADB server with the command
cd ~/android-sdk-linux_x86/platform-tools
6) Plug in the Galaxy Tab to the computer, with USB debugging turned on.
7) Test ADB recognition of the Galaxy Tab with the command
./adb devices
You should see messages indicating the ADB server is starting, and then a message similar to
List of devices attached
100020497aab device
If no device is listed, begin investigating by ensuring that USB debugging is turned on. In my experience, when the "adb devices" command is entered from within Windows 7, no device is listed. Again, I think this is related to the "waiting for device" hang when SuperOneClick is run in Windows 7.
8) Push psneuter to the Galaxy Tab with the command
./adb push psneuter /data/local/tmp
9) Make psneuter executable with the command
./adb shell chmod 777 /data/local/tmp/psneuter
10) Run the psneuter exploit with the command
./adb shell /data/local/tmp/psneuter
The message "property service neutered." should appear indicating success.
11) Test for successful rooting with the command
./adb shell
The # prompt should result.
12) Remount the /system volume rw (by default it's ro), so that files can be pushed to /system, with the command
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
13) Return to the Linux computer command line with the command
exit
14) Push Superuser.apk, su and busybox to the /system volume with the commands
./adb push Superuser.apk /system/app/Superuser.apk
./adb push su /system/bin/su
./adb push busybox /system/bin/busybox
15) Make su executable with the command
chmod 4755 /system/bin/su
16) Remount the /system volume as ro with the command
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
17) Verify that su works with the command
su
You should see the # prompt; type the command
exit
and you should see the # prompt again.
18) Power the Tab down and then power it back up. Run TitaniumBackup, which will ask for root privileges that (hopefully) will be granted. It's a good idea to backup your Galaxy Tab before using your new root privileges!
i take no credit for this. all credit to feral urchin for which ever device this works for retail or I/0 but something tells me its for retail because I/o has had an easier way to root for a while..
I am running windows vista ultimate. Should I try this and see if I have the same bug that has been reported for Windows 7?
I have a new Tab 10.1 Retail picked up today.
give it a try let us know the results please
dsh897 said:
but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
Click to expand...
Click to collapse
This might work. I am running Vista Ultimate x64 and my adb does recognize my retail Tab 10.1. See image below.
Now when I execute the command on step 10 I receive this error. . .
"Failed to set prot mask <Inappropriate ioctl for device>"
Suggestions?
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
dsh897 said:
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
Click to expand...
Click to collapse
Yes I copied all those files to the correct directory. Only on my windows machine the it is /android-sdk/platform-tools/
I am a firefighter in the Charlotte, NC area. Just got off tour this morning.
Google searching that error as I type. I'll let you know the progress.
dsh897 said:
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
Click to expand...
Click to collapse
I would like a backup image to odin if needed as well. How do I do this. I have a slight idea but i don't know the directories to pull?
i just disconnected my odin during dump im screwed at the mobile phone and computer! dunno how to get out
trying both volume rockers now. days downloading and flashing android box
just hold the power button for 10 seconds or just goto recovery mode and select reboot
that should get you back to honeycomb.
yea i got it with the power up then the recovery mode thx
How did you get adb to dump. i am running all sorts of commands and nothing works. some help would be greatly appreciated.
i was using odin3 to dump but it doesnt seem to be working correctly i think because its still locked. my next step is to flash the I/0 bootloader / system but im nervous now after it not correctly dumping (failure to write) it just creates a dummy file.
I am at work i will have to play with at home more. and have more resources
I am at an standstill as well. I don't know much more then what I have done thus far. I admittedly know nothing about Linux user privileges so I was never a help to begin with. The image below speaks for itself.
have you been able to flash anything with odin? i think if we can flash the stock i/o bootloader were set
Nope. Dont you think thats a little balzy without a retail dump to fall back on? Although, i could just exchange the device with best buy if something happens...
Sent from my GT-P7510 using XDA Premium App
haha why i havent done it yet. i cant see to get adb to recognize my tablet anymore i was making progress until now
is this method working ok to root a new retail SGT 10.1? thanks
i tried it and this what i got
"Failed to set prot mask (Inappropriate ioctl for device)"
any suggestions, thanks
neonflx said:
is this method working ok to root a new retail SGT 10.1? thanks
Click to expand...
Click to collapse
Nope. I am stuck. He is stuck. We are stuck.
any other methods to root a retail SGT, i took my XOOM back to Cotsco already
Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.
Does anyone if the root stop you from updating the device like GS4?
Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.
Finally success root my shield
oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?
Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app
So, after owning my beautiful Moto X for 1 month, I found that the screen is not nearly as shatter resistant as my old iPhone 4S. After managing to completely shatter it, I called Motorola up for a replacement (which for a customized Pure cost $125) and it was on its way, but before that I needed to get my old data off. Luckily I have unlocked my bootloader and rooted my phone in advance, but i had turned off USB debugging and had a passcode lock. All of the guides for making a full backup assume that you have screen access. After messing around for a few days, I finally managed to make a full backup of my phone. I thought I'd put together this guide for anyone else who has the same issue.
Assumptions
Your bootloader is unlocked and phone rooted (do not try to unlock it now or it will wipe the phone)
Your phone is not encrypted (there's still a way around this which I'll cover but I did not have to use)
You have ADB/fastboot set up on your computer (and have tested it at least once)
Required files/guides
CWM recovery file - http://motoxroot.com/cwmtwrp-recovery-for-moto-x/
Lock Screen removal guide - http://forum.xda-developers.com/showthread.php?t=1409304
SQLite DB editor (I'm on Windows) - http://sqliteadmin.orbmu2k.de/
Androidscrencast - https://code.google.com/p/androidscreencast/
ADB keystroke events - http://thecodeartist.blogspot.com/2011/03/simulating-keyevents-on-android-device.html
Steps
The first thing I did was download the customer CWM image for the 2014 Moto X which can be found here:
Code:
http://motoxroot.com/cwmtwrp-recovery-for-moto-x/
Next I went rebooted the phone into bootloader mode by holding "Volume Down + Power" for about 15 seconds. I could not see images on the screen but I could tell when it lit up.
Note: If you have an encrypted phone, you can use an OTG cable and a standard USB keyboard to type in the password blind. I used something similar for the PIN code, however this guide does not actually need to worry about that
Test that you have fasboot access by running
Code:
fastboot devices
You should see your device listed
Boot the CWM recovery image (you do not have to flash it which is nice)
Code:
fastboot boot XT1095recovery.img
Wait a few seconds and verify that you can now access your phone via ADB
Code:
adb devices -l
If this works, you now have a shell to be able to do the next part which is removing the passcode and enabling USB Debugging I followed the guide at http://forum.xda-developers.com/showthread.php?t=1409304 to do remove the lock screen
Mount the data partition of your phone by running
Code:
adb shell mount data
adb shell mount system
Grab the settings DB from the phone and copy it locally (Other guides say to copy to an intermediary, but since you're using a recovery ROM the files can be directly accessed)
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Open the file in your SQLite editor of choice and run the following statements
Code:
UPDATE secure SET value=65536 WHERE name='lockscreen.password_type';
UPDATE secure SET value=0 WHERE name='lock_pin_autolock';
While we have the settings DB open, it's also a good time to enable ADB Debugging by running the following statements (credits to http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb though I had to mod some more stuff)
Code:
UPDATE global SET value=1 WHERE name='adb_enabled';
UPDATE global SET value=1 WHERE name='development_settings_enabled';
Push the file back to it's original location
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
From here, the next set of commands should be run within the shell. You can access it by running
Code:
adb shell
Remove some existing property files
Code:
rm /data/property/persist.service.adb.enable
rm /data/property/persist.sys.usb.config
Add in the ADB settings
Code:
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
Correct the permissions for the settings.db file
Code:
chown system:system /data/data/com.android.providers.settings/databases/settings.db
chmod 660 /data/data/com.android.providers.settings/databases/settings.db
At this point, everything is ready to go and we're ready to reboot to your real install with no pin code and ADB enabled.
Reboot your phone
Code:
adb reboot
Run androidscreencast (don't worry about the keyboard/mouse instructions they don't work). Chances are the screen will be blank, press the Power button your phone and wait (it's got a *very* slow refresh rate)
Once you see your desktop, you can now run an ADB backup. I like getting everything, but this will take a while because it grabs all images, music, SD card stuff, etc.
Code:
adb backup -apk -shared -all -f backup.ab
On the screencast you'll see the prompt pop up asking you to enter a password and confirm. This was the part that took me a while and you have to do it fairly quickly otherwise it'll time out. In a separate windows run
Code:
adb shell input text <yourpassword>
adb shell input keyevent 61
adb shell input keyevent 61
adb shell input keyevent 66
At this point, you should see a full backup kicking off and running. You can run a logcat to watch the process of it. In some cases a full backup may hang if a resource has a file open, the two commands to work with this are:
Code:
adb shell logcat | grep BackupManagerService
To kill a process the backup is hanging on, enter the shell
Code:
su
ps | grep <nameOfProcess>
am force_stop <nameOfProcess> (the clean way)
kill <pid> (the dirty way)
Hope this helps! This took me a little while to figure out but now I have a full backup and my new Moto X will be here within the
week.
Okay so an ADB full backup sucks for a restore. Luckily I got a nandroid backup instead and that worked much better. There's some stuff you have to do with mapping /sdcard for it to work on the Moto X. I'll update this post soon with that information.
Thanks a lot for this! Helped me recover all my data from a Moto X with a completely broken blank screen!
This is an awesome Guide! Congrats!! I have a different situation. My Moto X 2014 is the XT1097 variant. The phone was neither rooted nor had an unlocked bootloader before the screen died. I downloaded the stock rom for my device, and flashed it with RSD Lite, since the program sees the phone connected in fastboot mode. Do you think I could use this method to reach the desktop? Also, the recovery.img in your guide is for the XT1095. Would it work for the XT1097? I know I can unlock the bootloader via fastboot, but what about rooting? Thanks in advance!!
I'm confused. I bought an M5C5 from Gearbest EU warehouse, which arrived today and it's sitting charging quite happily.
I was expecting to have to flash a custom ROM or manually debloat the thing. However out of the box it has a completely blank AOSP type build on it, just with the Google Play Store added.
Android 5.0, build number is V1.00_20151204, kernel version 3.10.2 (December 7th 2015 10:50:43 CST).
I see a couple of other reports of this around other forums. Does anyone know what's going on? More to the point, before I decide whether to flash a custom or not - is there any way of safely dumping this for others more knowledgeable than me to play about with?
I foolishly flashed a custom over the top of this. Other than being rooted, there's no benefit - in fact the stock is better and faster than the customs I've tried (pure Android launcher, no fluff with "reboot to Windows" or phone junk compiled in).
If you have this build, stick with it!
I read about this new stock version on my country's forums. Unfortunately nobody has dumped yet this version because I'm very interested.
Durete said:
I read about this new stock version on my country's forums. Unfortunately nobody has dumped yet this version because I'm very interested.
Click to expand...
Click to collapse
Yeah, I'm an idiot for not doing it. It looks easy to.
I'm pretty happy with sikke1's "Debloated" stock rom. You should try it. I don't like neither customized roms based in stock roms for different devices.
I'm using Mireks now. If someone dumps the build that seems to be showing up on new Air IIIs then I'm going straight back to that, it was perfect!
hordarian said:
I'm using Mireks now. If someone dumps the build that seems to be showing up on new Air IIIs then I'm going straight back to that, it was perfect!
Click to expand...
Click to collapse
I received my M5C5 with clean stock rom yesterday (also from Gearbest Europe store)
1.) I can try to backup this ROM, if you like, but you have to tell me how....
2.) My plan was to flash to mirek V7, but if I understand you correctly, it's better to stay on stock, right?
PS: In fact, the ROM looks ok, the only thing I'm really missing is root!
Till now I can't find a working instruction how to root this stock ROM....
heino69 said:
I received my M5C5 with clean stock rom yesterday (also from Gearbest Europe store)
1.) I can try to backup this ROM, if you like, but you have to tell me how....
2.) My plan was to flash to mirek V7, but if I understand you correctly, it's better to stay on stock, right?
PS: In fact, the ROM looks ok, the only thing I'm really missing is root!
Till now I can't find a working instruction how to root this stock ROM....
Click to expand...
Click to collapse
(1) It looks like there are a few people that would like the backup
Having not done a partition backup before some digging suggests it requires root or booting from a custom recovery.
This should allow you to root it: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096, it might allow a full backup to SD card as well.
(2) I'm always grateful to all of the ROM developers, but it seems in this case (maybe the first time ever!) the stock ROM is absolutely perfect stock Android! It is a better base for anyone to build a custom ROM from than any of the previous ones!
hordarian said:
This should allow you to root it: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096, it might allow a full backup to SD card as well.
Click to expand...
Click to collapse
I know this thread about rooting, but currently I'm waiting for feedback in another (German) forum about this rooting method, which maybe can brick the Air III...
I used that method to Root my Air III with Sikke1's "Debloated" Rom and to install Xposed.
I guess is pretty sure to use since the Root zip only add Supersu and binaries to /System.
I received my Air III M5C5 from Gearbest three weeks ago, but unfortunately it had the previous bloated Chinese ROM. Although I am very satisfied with Mirek v7, I will be very happy to test this one, if you are able to get it.
Durete said:
I used that method to Root my Air III with Sikke1's "Debloated" Rom and to install Xposed.
I guess is pretty sure to use since the Root zip only add Supersu and binaries to /System.
Click to expand...
Click to collapse
Right, the one who posted the problem stated that he followed the proposed steps (option 5 - CWM, and T4) but after installing the SU.zip the reboot failed....
I'm not sure if he did something wrong, I just want to be sure not to brick my Air III
If i succeed, what tool to use to make a full backup? Titanium backup pro?
---------- Post added at 02:12 PM ---------- Previous post was at 01:30 PM ----------
OK, I successfully rooted my device
If anyone is really interested to have the clean stock ROM, please help me how to make this backup...
I'm really interested, but not sure what should be the next step ...
This looks like a sensible guide: http://androidcreations.weebly.com/how-to-get-android-mounts-and-partition-images.html
And this: http://www.slatedroid.com/topic/7220-how-to-dumping-your-rom-by-adb-raw-nand-dump/
Get the Android SDK on your computer first. Looks like you'll need an SD card as well (there appear to be methods that don't require it but I'm not sure whether they work or not).
Let us know if you're struggling. I can probably put together exact commands for this device based on mine, I'm just distant from it at the moment so might take me a day or two.
Durete said:
I read about this new stock version on my country's forums. Unfortunately nobody has dumped yet this version because I'm very interested.
Click to expand...
Click to collapse
Same here!
I ordered 2 units, one came with an old Teclast ROM full of bloat (so I flashed Mireks v7 ROM) but the other one is clean and fast V1.00_20151204) AnTuTu score is 49887 compared to Mireks v7 rom 48547
Someone please send me some instructions on how to dump it and I will happily upload it somewhere! I would not mind sticking this new Teclast ROM on my other air iii
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
hordarian said:
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
Click to expand...
Click to collapse
Thanks Hordarian.
I will give this a go as soon as I can. I'll also upload whatever I'll dump to my google drive and share so you can have a look. Good suggestion to factory reset before I do the dump. The unit is only 3days old and the only thing installed is Antutu and I am logged on , so I will clear this first and then upload. If I do need to root first then I will do that too.
I'll try to do this on Tuesday.
Thanks for the instructions
Debloated GoogleNow custom roms VS New Stock Rom
Hello,
I too received X98 AIr III with new stock rom. I reflashed my tablet with sikke1 rom to solve the camera problem. (It looks like my x98 might have a defective camera......)
I rooted the sikke1 rom. It works great (well...except the camera).
Sorry. I did not make a back up of stock rom before I flashed.
I am looking forward to having a stock rom back even though I like both roms. Stock rom looked clean (small icons, play store only) and sikke1 rom has large icons (more visible).
Should I go back to stock rom when it is available? I cannot make a choice.....Hmm.
hordarian said:
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
Click to expand...
Click to collapse
Gave Hordarians instructions a quick try... But I guess this (below) means that I need root as the very first command resulted in the below:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
dd: /dev/block/by-name/boot: Permission denied
---------- Post added at 10:42 PM ---------- Previous post was at 10:24 PM ----------
hordarian said:
To do a backup. Assuming you're using Windows. You'll need a MicroSD card of a few GB
Get the latest Intel ADB driver and install it: https://software.intel.com/en-us/an...ion-instructions-for-intel-android-usb-driver
Enable USB debugging on your device (about device, hit build number 7 times to enable developer options, open developer options and tick USB debugging).
Connect device by USB.
Open a command prompt, run the following commands:
Code:
adb shell "dd if=/dev/block/by-name/boot | gzip > sdcard/boot.img.gz"
adb shell "dd if=/dev/block/by-name/system | gzip > sdcard/system.img.gz"
adb shell "dd if=/dev/block/by-name/recovery | gzip > sdcard/recovery.img.gz"
adb pull /sdcard/boot.img.gz
adb pull /sdcard/system.img.gz
adb pull /sdcard/recovery.img.gz
I'm not certain whether the device needs to be rooted first to do this, or whether it's all the required partitions.
Could also pull the entire flash down with the following (needs a substantial SD card!). Not sure this is necessary, and you should 100% do a full factory reset/wipe beforehand or you'll be giving easy access to any data you've got on the device.
Code:
adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"
adb pull /sdcard/mmcblk0.img.gz
Click to expand...
Click to collapse
Thanks for those instructions Hordarian, but as mentioned, it does look like root is needed and this stock ROM does not have it... So, what is the best (easiest) way of rooting? Is it this:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Root link for original rom
guvno said:
Gave Hordarians instructions a quick try... But I guess this (below) means that I need root as the very first command resulted in the below:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
dd: /dev/block/by-name/boot: Permission denied
---------- Post added at 10:42 PM ---------- Previous post was at 10:24 PM ----------
Thanks for those instructions Hordarian, but as mentioned, it does look like root is needed and this stock ROM does not have it... So, what is the best (easiest) way of rooting? Is it this:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Yes. I was able to root the original rom in my tablet using that link. It was fairly easy.
http://forum.xda-developers.com/andr...p-cwm-t2975096