I just upgraded to Netarchy 2.2 Rom. I then attempted to restore a data.img file from one of my Nandroid backups.
I copied the data.img to my >androidsdk/tools folder then using Fastboot USB I tried to execute [fastroot flash userdata data.img]from the adb shell.
I got the following error: sending 'userdata' (317381 KB)...FAILED (remote: data length too large)
I did not use Ti Backup for my data, just Nand backup.
Can anyone shed some light on where to go from here. I have searched...
Thanks
Looks like its too big...
Sent from my 4G using XDA App
if your starting a thread in dev that starts with [Q] STOP
Hero's Hero said:
Looks like its too big...
Sent from my 4G using XDA App
Click to expand...
Click to collapse
Thanks Knuckle!
ForayeEvo4g said:
I just upgraded to Netarchy 2.2 Rom. I then attempted to restore a data.img file from one of my Nandroid backups.
I copied the data.img to my >androidsdk/tools folder then using Fastboot USB I tried to execute [fastroot flash userdata data.img]from the adb shell.
I got the following error: sending 'userdata' (317381 KB)...FAILED (remote: data length too large)
I did not use Ti Backup for my data, just Nand backup.
Can anyone shed some light on where to go from here. I have searched...
Thanks
Click to expand...
Click to collapse
Give these steps a try...
How to restore individual components of a nandroid backup.
1. Locate the backup on your SD Card under the folder "Nandroid".
2. Navigate to the target backup folder.
3. Copy the folder(s) that you want to push back to the phone (i.e. data.img to a new directory on your pc; c:\nandroidbackup).
4. Open the cmd prompt (type "fastboot devices" to verify that your pc sees your phone). If not, you will need to change to the directory containing fastboot. This might be be c:AndroidSDK Directory \ tools.
5. Type "adb shell reboot recovery" in the cmd prompt to get to the bootloader. Then type "exit" to quit the adb shell. *Alternatively: manually use the buttons on the phone to get into FASTBOOT mode.
6. At the cmd prompt type "cd:<target folder location>" i.e.
the location of the data.img file (example cd c:\nandroidbackup) to change to the directory with the backup location.
7. At the cmd prompt now type "fastboot flash userdata data.img" [enter]. It should now indicate: "sending" followed by "writing".
8.When done, type "fastboot reboot" [enter].
Good Luck!
kperry1911 said:
Give these steps a try...
How to restore individual components of a nandroid backup.
1. Locate the backup on your SD Card under the folder "Nandroid".
2. Navigate to the target backup folder.
3. Copy the folder(s) that you want to push back to the phone (i.e. data.img to a new directory on your pc; c:\nandroidbackup).
4. Open the cmd prompt (type "fastboot devices" to verify that your pc sees your phone). If not, you will need to change to the directory containing fastboot. This might be be c:AndroidSDK Directory \ tools.
5. Type "adb shell reboot recovery" in the cmd prompt to get to the bootloader. Then type "exit" to quit the adb shell. *Alternatively: manually use the buttons on the phone to get into FASTBOOT mode.
6. At the cmd prompt type "cd:<target folder location>" i.e.
the location of the data.img file (example cd c:\nandroidbackup) to change to the directory with the backup location.
7. At the cmd prompt now type "fastboot flash userdata data.img" [enter]. It should now indicate: "sending" followed by "writing".
8.When done, type "fastboot reboot" [enter].
Good Luck!
Click to expand...
Click to collapse
Thanks for the detailed reply...
I might not have been clear in my post, but the above was exactly what I did, and got the error I'm inquiring about.
Thanks again...
Sorry if you already tried this... The difference I noticed from your original post is in: Step 6. The command "Fastboot Flash...." is entered from the command prompt, not within adb shell at that point.
That was my understanding of the instructions.
This is a super simple method taken from Arcadia 310 on another thread.
This is assuming you have The Android SDK already installed and updated.
Download these files XoomRoot.zip HERE
and FASTBOOT for MAC - HERE
Unzip both archives into your ~/sdk/platform-tools folder.
I AM NOT RESPONSIBLE FOR YOU SCREWING UP YOUR DEVICE, THIS IS VOIDING YOUR WARRANTY ANYWAYS. HIT ME UP ON TWITTER OR HERE IF YOU NEED HELP OR HAVE QUESTION. ON TO DIRECTIONS.
Follow these steps: (After you have unzipped into your folder)
1. Follow the pre requisites above.
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
You should now have root acces! Enjoy!
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
First off thanks for doing this... I figured out my n1 and I can do this too... I'm stuck at the chmod 775 line... I enter that command and its like I didn't enter it... after I proceed to fast boot OEM unlock it tells me that it can't be executed .. what am I doing wrong... God I hate being noobed out... I'm so close!!!
Sent from my Nexus One using XDA App
EDIT: got past that with the help of using fastboot-mac from htc's website... but now I'm stuck on getting the rootboot.img over
Morgan-Brants-Mac-minilatform-tools Chongo$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... FAILED (remote: (0000000f))
Morgan-Brants-Mac-minilatform-tools Chongo$
EDIT2: Well it was due to my xoom being almost dead (not enough juice to flash)
on the other hand this was a refresher course and I now understand ADB a whole lot more... thank you for this educational piece I am now a tiger blood enfused SUPER USER
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
b16a2smith said:
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
Click to expand...
Click to collapse
Thanks.. ill let you know when I get a new phone.. should be soon
Sent from my Nexus One using XDA App
thanks for this. Cant wait to get mine on the 27th
wheeeler said:
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
Click to expand...
Click to collapse
Well the default shell in a mac is bash so wouldn't be:
Code:
echo "export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH" > .bash_profile
This is a video walkthru of rooting that happens to be on a Mac but the process is the same for Windows:
http://www.youtube.com/watch?v=4YkIw0y_Os4
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Magenta you say.
chevyman46933 said:
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Click to expand...
Click to collapse
can anyone help me?
OK, thanks for the initial post and outstanding directions. I've updated what you listed based on what I have seen on my mac. I've just been through this process now and everything is working great. I hope this helps.
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
goonmac-2: platform-tools goon$ ./adb devices
List of devices attached
028040c743e111d7 device
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
FYI - your xoom will just say "Starting..." but it is ready to accept the next step.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
goonmac-2: platform-tools goon$ ./fastboot-mac oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
*after the reboot, initially, I got this error:
goonmac-2: platform-tools goon$ ./adb reboot bootloader
error: device not found
when the reboot completes, you will come to the original setup screen. it is worth noting that you need to select the language and follow the on screen directions. Re-enter your account information etc. When you get to the desktop, your device will then be re-seen by your mac.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... OKAY
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac reboot
rebooting...
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
no issues
goonmac-2: platform-tools goon$ ./adb remount
remount succeeded
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
no issue
goonmac-2: platform-tools goon$ ./adb push su /system/bin
701 KB/s (26336 bytes in 0.036s)
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
no issue
goonmac-2: platform-tools goon$ ./adb shell
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
no issue
# chmod 4755 /system/bin/su
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
no issue
goonmac-2: platform-tools goon$ ./adb push Superuser.apk /system/app
1137 KB/s (196521 bytes in 0.168s)
still stuck at same step, after ./adb reboot fastboot i cant go any farther, the xoom just isnt connected to recieve and additional commands, heres a copy n paste from my terminal...
Mac-Users-Mac-mini:tools Home$ pwd
/Users/Home/desktop/sdk/platform-tools
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
161c10c94180d557 device
Mac-Users-Mac-minilatform-tools Home$ ./adb reboot bootloader
Mac-Users-Mac-minilatform-tools Home$ chmod 755 fastboot
Mac-Users-Mac-minilatform-tools Home$ ./fastboot oem unlock
-bash: ./fastboot: cannot execute binary file
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
Mac-Users-Mac-minilatform-tools Home$
any help/suggestions?
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
wheeeler said:
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
that was exactly it, i was using the fastboot from another post, got the fastboot-mac from the website adn it works perfect!! thanks!!!
xoom unlocked, finally
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
goon55 said:
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
Click to expand...
Click to collapse
For some respason I didnt realize the difference between the two fastboots until he mentioned that and thankfully your ad was right above with the link to htc thanks to you guys im now have rooted and unlocked and overclocked my xoom and its incredible now! Thanks for the patience with me
I did a video that was done on my MAC in the MAC OS. If anyone wants a more visual way to see how this is performed. I follow all these steps exactly. I show how I set my environment PATH, and this actually is what tripped me up, because my user profile wasn't looking at the PATHs I originally setup, but all that is required is entering
echo 'export PATH=xyz:$PATH' >> ~/.bash_profile (this whole line )
Where 'xyz' is your path to the android-sdk/platform-tools/ from the root of your Hard Drive, for most Macs it should be ' /Users/[Ur User Name]/android-sdk/platform-tools '
http://www.youtube.com/watch?v=26EhGGOGUus
Hope this helps
I also have a WiFi Xoom Video Tutorial available available as well. Check it out.
http://www.youtube.com/watch?v=zC6J-hV6SM4
I try to go over common hiccups that I have seen some users have come across as well in the video.
I'm getting the following error:
./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
fastboot-mac is chmod 755, rootboot.img is there, alongside it, I'm in as root and it's still failing for me.
Edit: Nevermind. Right after pulling the reboot before the rootboot.img - or boot.img for wifi users - immediately go into the aforesaid command and it should work just fine.
Took me a couple of times.
Can you unroot on mac?
Ok it's hopefully just something I'm overlooking but haven't gotten it to work so far. I have ADB and Fastboot set up on computer and the phone is T-Mob m8, unlocked, rooted, TWRP, Custom ROM, S-Off, Super CID. I have downloaded the radio zip, extracted the radio.img and put it in the adb folder in my c drive. Now I followed a couple of steps posted:
Fiash via adb:
1. Download the radio.img above
2. Put the radio.img file into your ADB folder
3. Open up command prompt and copy and paste the EXACT lines
4. adb push radio.img /storage/sdcard0/radio.img
5. adb shell
5. su
6. dd if=/storage/sdcard0/radio.img of=/dev/block/mmcblk0p20
7. adb reboot
I get cannot stat "radio.img" no such file or directory any suggestions? thanks
but each time i get a file not found so what is
http://www.androidfilehost.com/?w=f...ce08cd20294c7e0997d32ce5203bee4a606a03d8be1b9
i used this to fix my radio problems. flashable in twrp
Okay, make sure the radio.img is in the folder you have adb and fastboot setup, then do the following once your phone is connected to your computer:
Open command and type the following:
Code:
adb reboot bootloader
fastboot flash radio NAME_OF_FILE_.img
Then reboot your phone afterwards.
Da Kine said:
Okay, make sure the radio.img is in the folder you have adb and fastboot setup, then do the following once your phone is connected to your computer:
Open command and type the following:
Code:
adb reboot bootloader
fastboot flash radio NAME_OF_FILE_.img
Then reboot your phone afterwards.
Click to expand...
Click to collapse
Thanks! got it working, I knew I was having a vegetable moment, I was putting the radio.img in the actual adb folder. Once I removed it from there and put it in the c: drive folder it worked like a charm :good:
Tried these steps
Connect to your Fire TV using ADB
(If you don’t know how, follow up to Step 4 Part 2 in our Windows or Mac guide)
Run the command: adb shell
Run the command: su
(If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
Run the command: chmod 777 /cache
Run the command: chmod 777 /cache/recovery
Run the command: cd /cache/recovery
Run the command: echo “--update_package=/cache/update.zip” > command
Run the command: exit
Run the command (yes, again): exit
Run the command: adb push update.zip /cache
(This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache)
Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery
The update.zip file is on the same folder where the adb platform-tools is located, but when I enter the full path it says no such file or directory.
Mine looks like this C:\Users\XXX\platform-tools>adb push update.zip /cache
What am I doing wrong, please help
CD to the directory first . then enter adb push update.zip /cache
mastafunk said:
CD to the directory first . then enter adb push update.zip /cache
Click to expand...
Click to collapse
I did everything in the same folder.
Do you suggests I go back to root of c folder then go back to the folder again
Copy and paste what you entered and the error..
[url]https://www.dropbox.com/s/rdr3buikslvw1qm/adb.png[/URL]
https://www.dropbox.com/s/rdr3buikslvw1qm/adb.png
Stevie G said:
[url]https://www.dropbox.com/s/rdr3buikslvw1qm/adb.png[/URL]
https://www.dropbox.com/s/rdr3buikslvw1qm/adb.png
Click to expand...
Click to collapse
when you push a file with adb, the file must be in the same folder/path you're running the adb command from. From your example, you need update.zip on your PC at C:\users\Stevie G\platform-tools\
The error is saying the file isn't at that path.
Luxferro said:
when you push a file with adb, the file must be in the same folder/path you're running the adb command from. From your example, you need update.zip on your PC at C:\users\Stevie G\platform-tools\
The error is saying the file isn't at that path.
Click to expand...
Click to collapse
might have issues with the space in Stevie G, try a folder without spaces.
I have read multiple instructions regarding how to root the Pixel XL (non Verizon) which look pretty straight forward; however, one instruction set said to copy the twrp img file to the adb folder while another set of instructions said to copy the twrp img file to the Partition-Tools sub folder. Wondering which is correct (or does it matter)?
Thanks for your help.
If adb.exe and fastboot.exe are in your path, just open a command prompt in the directory the twrp img file is in and run the commands. If not, copy the img file to the directory with adb and fastboot, open a command prompt there, and run the commands. Another alternative is to open a command prompt in the directory with adb and fastboot, and run the commands with the full path of the img file.