Rooting through a noob's eyes - Droid Incredible General

I'm not sure how this will be taken by the people here. Everyone seems really helpful when other people ask questions or need help so I may be surprised, but after rooting my Incredible last night and then trying to look into boot animations, removing bloatware and other things I was left with some feelings that took the joy out of being rooted and I wanted to share them.
Laugh if you will, insult if you feel it's necessary. I'm old enough to be able to handle it but beyond all of that I just wanted to say that the "rooting community" are a brilliant bunch of people. The things that you guys do boggles my mind. Since I only just registered I'm forbidden to post links, but if you're so inclined to go read it here it is.
ishootpixels.tumblr.com/
EDIT: I'd also like to add that my wife's netbook is running XP and not Vista. I forgot that we downgraded it (or upgraded however you want to look at it). I've gone back and changed my blog post.

If you would like some help getting where you want to be, PM me and I would be glad to help. I am far from an expert, but after scouring these forums endlessly, I am quite familiar with the process.

@mtag1029 Thanks. I guess my first problem is that whenever I type in "adb" anything, I get that "adb is not recognized as an internal or external command, operable program or batch file."
I've used this method to connect the phone to the netbook...
1. Boot into Clockworkmod recovery by powering off the phone and pressing and holding the volume down and power button until the screen lights up.
2. At the menu press volume down to select Recovery, then press power.
3. At the Clockworkmod main menu select partitions menu, then select mount /system
4. On the computer click Start > Run, and type CMD to open a command prompt.
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
and I get as far as step 6 before I can't go any further which is where I get that message. Right now I'm trying to install a boot animation and sound but I'll also need to be able to get beyond this in order to remove the bloatware. What am I doing wrong?
And THANK YOU again for the help. I'm almost to the point of returning it to stock so I'll at least be able to get Froyo whenever it's released OTA, but I've come so far at this point I'd hate to throw it all away and go back to stock.

IShootPixels said:
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
Click to expand...
Click to collapse
Assuming your sdk folder is in the root of the C drive (i.e. C:\sdk\), the command in step 5 is wrong -- it's supposed to be:
Code:
cd \sdk\tools
with a space. That should get you into the C:\sdk\tools directory, where adb is.
Not sure if the lack of spacing was just a typo, but if not, there ya go Let me know how it works
edit: Just tried cd\sdk\tools, actually works, I thought there had to be a space, but maybe not. I guess the next step would be to make sure there's an adb.exe in your tools folder?

I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Beyond that, when I get into running command lines I have gotten to where it looks like this...
C:\sdk\tools>
No spaces. I'm taking a pic and trying to attach it if my noob status on the forums will allow me.

I don't have the exe file. I didn't need it to root the phone. I don't know where to even get it.

IShootPixels said:
I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Click to expand...
Click to collapse
If you just made the folders, there's nothing in them -- if you go to the tools directory and type "dir", there probably won't be any files unless you extracted some in there.
From the how 2 adb thread by dreamersipaq:
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Click to expand...
Click to collapse
edit: the rest of that thread is located http://forum.xda-developers.com/showthread.php?t=709220 there, if you're interested

gmonox is absolutely correct. You cannot just create the folders. They have to come from the sdk.
Another thing. You mentioned in your blog post that you would like to have froyo. Froyo should be flashed before removing any apps becauseeverything that you have removed will be put back in with froyo.

Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.

IShootPixels said:
Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.
Click to expand...
Click to collapse
Either way works. I renamed mine sdk because I'm too lazy to type android-sdk-windows every time I want to go into adb shell. But it's up to you

Ok, I'm guessing that my question will be answered after I run the setup. I didn't see the link at first to the thread. Apparently my wife's netbook doesn't even have the right java ver. to run the setup.
This is making my brain hurt.

I should have asked this earlier, have you made a nandroid backup?

LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
EDIT: This is going to take awhile I'm guessing. Installing SDK Platform Android 2.2, API 8, revision 2

Okay. The nandroid is the most important. It will save your butt if something goes wrong.

IShootPixels said:
LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
Click to expand...
Click to collapse
Both types of backups are easy to restore, for nandroid you just go into recovery, same place as you backed it up but click Restore and just wait for it. For titanium, go into backup/restore, batch, and there's an option to restore apps, apps+data, and apps+system data I think. If you have the paid version, the apps will all install on their own, but if not I don't think they will.
Are you still on a netbook or can you use a pc? Might be easier if your java's out of date and whatnot to just use a pc, I'm no expert on netbooks but I'd imagine they're stripped down a lot

gmonox said:
Both types of backups are easy to restore
Click to expand...
Click to collapse
Just keep in mind that you need a functioning phone in order to use Titanium. If you mess something up while in adb and the phone will not boot, Titanium is useless. A nandroid however will restore you back exactly how you were before messing around in adb even if the os will not boot.

Well then I'm glad I did the Nandroid BU! Bsically then I guess that because I backed up with Ti first and then with Nandroid, the Nandroid created a back up of my Ti backup. If so I think I just set a record for redundancy.
As for using a netbook, I don't have a choice. I run everything off of my Macbook, or did until now. The only Windows based item in the house aside from my Xboxes is my wife's netbook. I've updated the Java and begun the setup process. I had to do as the thread said and force the http and then go into the available packages and I'm DLing and installing them all because I was afriad that if I didn't I'd find that I needed one I hadn't installed. I'm guessing that since I'm already rooted (and I'm hoping) that once I'm done installing all of these packages that that should be it except for step #4 and #5.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.

I'd also like to add that this is the YouTube video that started this mess. I followed his tutorial on rooting the phone and although the sound was low it was pretty spot on minus one or two things he failed to mention.
However, after watching this video I thought it would be just as easy to install the boot animation as it was to root the phone. Seems the bigger task would be rooting rather than a boot animation. In the hours that you guys have helped me I've learn that this boot video lacks a TRUCK LOAD of information and assumes that the person watching it isn't a noob. Dont' most people that watch tutorial videos watch them because they have no idea what they're doing? I realize now that there's a ton o' stuff missing from it. I still want the animation and sound though.
http://www.youtube.com/watch?v=-Ju9lpH7_4g&feature=channel

Titanium stores backups on your SD card. Nandroid does not backup your SD card, but you are in good shape. Keep us posted.

I'm not sure if step 4 is required, I'm on win7 64bit and I don't recall doing it, but I guess it couldn't hurt. Also, I don't think nandroid backs up your titanium backup -- Ti backup is stored on your SD card

Related

Deploying an app that uses root

I've got a small collection of files I'd like to package (dund, chat, a couple of scripts).
On any other OS I'd just stick it in whatever package management system is in use but I'm finding the documentation to apk's to be very sparse - it just says 'use eclipse' but as there is no java component (I might make a gui one day but I wrote this to get my tomtom working not with anyone else in mind really) and everything requires root access I really don't see how.
Ideally I'd want to just be able to do 'adb install xxx' and it would copy the files to the right place, set the init script to run on boot, and be sorted.. I can't be the first person to want to do that, surely?
TonyHoyle said:
I've got a small collection of files I'd like to package (dund, chat, a couple of scripts).
On any other OS I'd just stick it in whatever package management system is in use but I'm finding the documentation to apk's to be very sparse - it just says 'use eclipse' but as there is no java component (I might make a gui one day but I wrote this to get my tomtom working not with anyone else in mind really) and everything requires root access I really don't see how.
Ideally I'd want to just be able to do 'adb install xxx' and it would copy the files to the right place, set the init script to run on boot, and be sorted.. I can't be the first person to want to do that, surely?
Click to expand...
Click to collapse
The APK format is designed for traditional apps. When you install an APK it pretty much just moves the file to /data/app, and performs a few other maintenance tasks. There's no control over what happens to the files inside.
What you describe is usually done from an update.zip flashed from recovery.
However, if someone wanted to get crazy, one could port ipkg and use that to install arbitrary files to the system, but it would still a two step process (adb push file, adb shell ipkg file). You could even set up an ipkg repository. But this is probably overkill.
Hmm... probably won't bother then. Probably not enough people interested be worth the time.. it's a bit of a niche app (tomtoms have wierd requirements for their DUN stuff so they're a bit of a git to get working).

[STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions)

MANY THANKS TO REV FOR RE-WRITING THIS FOR ME!
(Post was updated on 3/23/2011)
=======================================
This post is to provide a template for using NVFlash to restore/recover your G-Tablet after suffering some kind of malfunction. Specifically, this document tries to provide ALL the information you need to use the NVFlash tool to recover the bekit 1105 software version, which has been found to be safe as a starting point for rebuilding your tablet after having a problem. This post does not include other methods of setting up NVFlash (such as installing the SDK, etc.) because this method is proven and can be easily supported.
I use Ubuntu Linux and know that the Linux instructions below are correct. Others have written Windows instructions and those too have been checked carefully and have been used before successfully.
A WARNING IN ADVANCE: NVFlash makes changes to the partition structure of your device. You should tread carefully and understand the risks. (MOD EDIT Note: It also has been noted a bunch of times that even NVFlashing your G-Tablet will not completely overwrite everything on it.)
The NVFlash setup process begins with a visit to:
http://db.tt/Wm25t7U
(Note: Sometime this DropBox is cranky. If you have trouble with it, check back later.)
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Note: The above "nvflash_gtablet_2010110500" is commonly referred to as bekit version 1105 in many posts relating to nvflashing (especially my posts).
-------------------------------------------
Installation
First, create a folder named "NVFlash" on your PC to put the needed files into and to work from. (Note: You can call it something else if you want to; we're just using "NVFlash" to keep all of us on the same page.)
Next, extract the files you downloaded from the DropBox above into the "NVFlash" directory. The files with linux and windows in the middle of then are the files for setting up NVFlash. (The are taken from the SDK and do not install the whole SDK -- just a simple, operable NVFlash for us to use here.) The files with gTablet in the middle contains the .img files with the software to go on your G-Tablet.
Third, for Windows users, you'll need to have an APX-specific USB driver for the next steps. (The Windows package bekit supplied has an .inf file in it, but the actual drivers are not there). For Linux users, you don't need an extra driver.
One source for the Windows drivers is at
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files. Extract them and go down two levels to the "USB" folder -- and move that into your "NVFlash" directory. The USB folder has the .inf file for installation in it along with two other directories with drivers for the various operating systems. (Note: These drivers, which are the same as the drivers in the SDK, are proven to work with Win 7 64-bit and have the setup include to load into other versions of Windows.) Follow this narrative for actual installation of the drivers.
CHECKPOINT: At this point, you should have the nvflash files, .img files, and USB directory (and files) in you "NVFlash" directory and are ready to begin the recovery process.
Now, you will need to boot into G-Tablet APX mode: hold down the power and volume - button simultaneousl until your G-Tab comes up and the goes back to a black screen. The black screen means it is in APX mode and it is waiting to display the flashing process. In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Connect your G-Tablet to your PC using your miniUSB to USB cable that came with your tablet.
Linux users: At this point, open up a command window to the folder you created, and run this script:
./nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically. If the script does not work, make sure that the shell script and nvflash binary are set as executables.
Windows users: When you connect to the PC, the PC immediately tries to load a driver -- but since it doesn't know where the USB driver files are it will fail. Click through Start/Control Panel/Device Manager and find "APX" listed in the devices with a yellow "!" (exclamation point) on the icon. Select the APX item and find the "Update Driver" button and click it. When it asks where to search, choose the local computer manual selection choice and tell it to Browse.
Point the Browse (and the USB install) at the "USB" directory under the "NVFlash" folder. When pointed at the "USB" directory, the driver installed and I was ready to nvflash. If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Again, for Windows: Run this script which is in the "NVFlash" folder:
nvflash_gtablet.bat
This will wipe the device back to bekit's original TnT stock image except for user data, which is retained. Should take about a minute to run and the device will reboot itself automatically all the way to the main screen.
POST NVFlash:
When your G-Tablet has booted back to the main screen, you will have to check and make sure everything is set up. Particularly, get the wifi on and connected to the Internet. Almost immediately, you should get a notice about an OTA (over the air) update. This is the OTA Update to software version 3588. If it does, go ahead and have it do the update. From there, you can begin using your "stock 3588" G-Tablet.
If you don't get an automatic OTA notification, you can go the to manual "Update" icon on your tablet and have it check for updates -- and hopefully it will find OTA 3588.
Or, if neither of the above happen, you can download 3588 at the following link and install it manually:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
Note: Following is a STICKY from General Forum on the stock recovery process:
http://forum.xda-developers.com/showthread.php?t=892090
NOTICE: There are many threads out there with tell how to do this process. Others tell individuals' problem solving experiences. A few of them may not be right! The above process is not the only way to do this -- but it is fairly straightforward and it is proven. It is recommended for anyone who does not have experience with nvflashing.
***************************************************
Further references (since I'm not a Windows user): http://forum.xda-developers.com/show...0&postcount=28
and http://forum.tegratab.com/viewtopic....bbde76184e550a and http://wiki.tegratab.com/index.php/Nvflash_FAQ
An additional suggestion if you also want to tack on bekit's clockworkmod recovery versus standard recovery: http://forum.xda-developers.com/show...3&postcount=17
Hope this helps!
03/2011 update -- I've been told that this tool has been useful to erase ALL partitions, including user data. I believe you need to re-flash with the bekit 1105 above, AFTER you use this: http://forum.xda-developers.com/showthread.php?t=974422
04/22/2011 update -- I've built out both 1.1-3588-based and 1.2-4349-based versions that have effectively replaced bekit's 1105 image ("nvflash_gtablet_2010110500.zip"), at least on my own device - I'm also addding a clockworkmod recovery option. It is being hosted in the same location as my 1.2-based mods - I will be making updates there, from this point on (as I might update them from time to time).
(you'd still need bekit's Windows or Linux tools, keep in mind) I've been able to bring back my device back from a soft-brick several times, so I feel they are usable.
05/09/2011 update -- A reminder that these images are not being updated, here. I have a newer nvflash post over in the same site where I have my 1.2-based mods. The 1105 bekit image mentioned here is still relevant for 1.1-based ROM users, or you can use my 3588 ot 4349 solution at the other site.
05/10/2011 update -- I have PM'd the moderator to either unsticky this post and / or assign it to someone else, as I do not plan on updating it, here. I believe that there is a 3588 image in the TegraTab IRC that someone created, for example.
Looks good Roebeet. I wrote a little how to a while back on tegratab. I know you are aware but for the benefit of others I wanted to add the following.
One little thing is sometimes when you are done you will get a boot loop. I think it only may happen once as I never saw it again. The fix is to go into Clockwork and partition the internal sd card again. The old settings said 512 for memory, and 256 swap. Bekit updated Clockwork and now you can format all the way to 4gb if you like, and swap should be 0 as it is not used.
Edit: New wisdom says not to partition the internal sdcard to anything but 2048. Folks have had issues with memory errors in the market with anything bigger. 0 for a swap is also the recommendation as Android apparently does not make use of the swap.
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
I need help. I finally got Windows 7 to recognize the device in APX mode but how do I flash from this point. It only shows up in my Device list with all the subfolders in it.
What is this for? Restoring to factory Rom?
Thanks,
Scott
cscotty said:
What is this for? Restoring to factory Rom?
Thanks,
Scott
Click to expand...
Click to collapse
Yes, you can use it for exactly that. I believe bekit added Launcher Pro and superuser, but other than that it's a way to completely wipe the device. Moreso than a standard recovery would do.
The pre-req link doesnt work. Can you update the link?
Thanks
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
stanglx said:
The pre-req link doesnt work. Can you update the link?
Thanks
Click to expand...
Click to collapse
It seems to go up and down (it's bekit's dropbox). Try this:
https://www.dropbox.com/s/wrcd87u1iy31u4e
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
Roebeet sorry but I just noticed for noobs that the linux command needs to be
. nvflash_gtablet.sh
Also if you unzip those files into a premade directory such as "gtablet" when you unzip them each have their own directories and if you ls you can see that the bash script isn't executable from there. So you need to copy either the gtablet files into the platform folders or copy all the files inside both into your "gtablet" folder. Then you can run the ". nvflash_gtablet.sh" command and voila. Sorry I am on Ubuntu and don't know if it is different, but that is the way I run them.
No worries - all replies are welcome! the more info we have, the better.
This should be stickied. Nvflash has saved my gtab many times and I think its the reason why my gtab doesn't really encounter too many Force closes. Its the perfect method to ensure your gtab is clean.
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
ehunyadi said:
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
Click to expand...
Click to collapse
My limited experience with 64-bit Win7 -- the drivers have to be signed, or else they won't work. There's a way to disable that on boot, but you can't permanently disable it. I'm wondering if the APX USB driver is signed?
Open a command prompt as an admin and type
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
This is the only way.. dont worry if the test watermark shows up.. it wont affect anything.
Also... They have a x64 driver - read this
http://tegradeveloper.nvidia.com/tegra/forum/adb-usb-driver
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Your gonna have problems later if you don't repartition to 2048 and 0
satishraman said:
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Click to expand...
Click to collapse
You only have 16gb to start. Partitioning you internal to 4gb uses part of that. I would go back and only use 2gb, and 0 for swap. There are things, like the new market that break with anything but 2gb.
If you mean the settings menu is not showing your external sd card that's normal. Look in a file explorer program in the / directory. Look for SDcard2. That is your external. Same deal, look for usbdisk if you plug in a usb drive.
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
romanrish said:
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
Click to expand...
Click to collapse
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
roebeet said:
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
Click to expand...
Click to collapse
Yeah I thought about that, but figured some people might get confused and forget which one was which. Either way works as well just as long as you keep both files. You should edit your original post and add that in as an option to do at the end. It will keep some from having to look through and creating a new post cause they can't find it, and keep our forums clean.
This should definitely be stickied. Mods please?
P.S. I cannot believe how awesome this forum is(Viewsonic G Tablet). I have gone to other forums and the other devs and users are not as friendly and awesome as the ones we have here. Almost brings a tear to my eye. Great job Roebeet, this should help us noobs out a lot. LOL!

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.
Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium
Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium
Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.
okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?
@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.
Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium

*Recovery Mode - Cannot mount Internal/External SD or Mount USB Fix

This has whooped my a$$ all evening and I've finally found some sort of a work-around for it, thought I'd share.
When I flash a ROM, I really like to nuke everything. Problem with nuking everything is you often cannot mount the phone to the computer to copy over the shiny new Rom
So here's the scenerio:
You're in recovery, you can't mount an SD, you've accidentally (or otherwise) deleted everything off of the INTERNAL card (including your new rom). Clockwork for some reason or another hates you and won't let you mount USB to transfer the ROM over for install. So you're officially dead in the water with no hope in sight.
three magic letters come in to play on this one. ADB.
http://forum.xda-developers.com/showthread.php?t=502010
Moving on now to the point of Post-ADB-Installation...
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory (mine was installed on the C: drive, but yours is wherever you installed it)
Open a CMD.exe window (start, cmd, enter)
navigate yourself to the ANDROID-SDK/PLATFORM-TOOLS/ directory
type this command:
adb push shiny.new.rom-name.zip /sdcard/
now go back to the phone, back into recovery, install from sd, laugh all the way until the next time you think you've destroyed your $600 smart phone.
Hope this works for you!
skipster99 said:
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory
Click to expand...
Click to collapse
Or you could add PLATFORM-TOOLS to your PATH environment variable like most people do.
Also, try Droid Explorer.
skipster99 said:
This has whooped my a$$ all evening and I've finally found some sort of a work-around for it, thought I'd share.
When I flash a ROM, I really like to nuke everything. Problem with nuking everything is you often cannot mount the phone to the computer to copy over the shiny new Rom
So here's the scenerio:
You're in recovery, you can't mount an SD, you've accidentally (or otherwise) deleted everything off of the INTERNAL card (including your new rom). Clockwork for some reason or another hates you and won't let you mount USB to transfer the ROM over for install. So you're officially dead in the water with no hope in sight.
three magic letters come in to play on this one. ADB.
http://forum.xda-developers.com/showthread.php?t=502010
Moving on now to the point of Post-ADB-Installation...
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory (mine was installed on the C: drive, but yours is wherever you installed it)
Open a CMD.exe window (start, cmd, enter)
navigate yourself to the ANDROID-SDK/PLATFORM-TOOLS/ directory
type this command:
adb push shiny.new.rom-name.zip /sdcard/
now go back to the phone, back into recovery, install from sd, laugh all the way until the next time you think you've destroyed your $600 smart phone.
Hope this works for you!
Click to expand...
Click to collapse
All well and good but my simple method after a wipe is to flash a stock rom then CWM root and copy file over .No need to bother with all that Linux stuff and probably easier for noobs and nearnoobs .
jje
I'll check out droid explorer - Thanks
As far as "all that linux stuff" I think one ADB PUSH command from WINDOWS is easier and faster than loading another rom on to the phone. Do what you wanna do, was just something I stumbled upon to help other noobs stuck in the same situation.
skipster99 said:
I'll check out droid explorer - Thanks
As far as "all that linux stuff" I think one ADB PUSH command from WINDOWS is easier and faster than loading another rom on to the phone. Do what you wanna do, was just something I stumbled upon to help other noobs stuck in the same situation.
Click to expand...
Click to collapse
So now they have two methods pity they will never look or search .
jje
+1 for all that linux stuff -- I love it! Droid Explorer is nice too but I feel like a wuss when I use that program because all its doing is executin linuxy stuff.
Hey, WHY are you nuking your sdcard? Thats overkill!!! but whatever floats your boat!

<<Q>>cracked screen. ADB and/or OTG what are my options?

first... its been a while since i have messed with a nexus. so im not on the nexus boards that much. my buddy and i both bought nexus phones during the first day of second round of sales back in 2012. back then there was no otg support. and rooting was done via adb etc. i sold mine shortly thereafter and have not been on the nexus boards since. so please catch me up to speed with my questions and maybe help me to get his files switched from his old nexus with a cracked screen to the new one he just got yesterday.
is there now otg support for this phone?
i found a post to adb past the lockscreen. can i also use adb to pull the backup file (i booted into recovery and did a backup yesterday) on the old and use it on the new? new phone is not rooted yet, but can be.
is there a way to pull specifics from the backup. or pull specific apps with adb? as in he has company passwords and such in a note app that he really needs with a passion.
is there an easier way to get to the files than what i am thinking i have to do? i still need to relearn how to use adb and such, but if i can otg through this and use airdroid that would be wonderful. if adb is the only way to get this done.... would you mind giving me the commands i need to get to and pull the files i need. i can get the paths from his new phone to figure out where they are. i just dont know the commands to do the deed.
thanks a ton for anyone willing to help. <-- seriously.
-patrick
You can get USB Host working BUT it has to be externally powered.
Sent from my Nexus 4 using Tapatalk 4
I hope I'm understanding your exact situation; feel free to let me know where I misunderstood you.
Ok, your friend bought a Nexus 4 a while back, has somehow broken the screen, bought a new Nexus 4, and wants to grab a nandroid backup and a document from a notepad-esque application from it?
If so, this is what I'd do. I'd grab the Nandroid backup from the old device, and restore it onto the new device (again, assuming both old and new devices are the same model i.e. Nexus 4)(also after backing up the new device, in case you ever need or want to revert to a fresh image) and grab the text file. What recovery are you using on the broken phone? I don't know the path for backups for TWRP, but if you're using CWM, the path is /mnt/shell/emulated/clockworkmod/backup/. Ok, let me make this easier by making a step-by-step. Some of it you probably already know how to do but I want to be as clear as possible.
1. Make a nandroid backup on new device in case something goes wrong, or you want to go back in the future
2. Hook up broken device to computer, open a cmd window in the platform-tools folder, containing adb.exe (shift right-click in an Explorer window and hit "Open command window here" is the fastest way)
3. Use this command: adb pull /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/ NameOfBackup
4. That will pull the backup and put it in a folder called NameOfBackup (whatever you called it) in the platform-tools folder containing adb.exe
5. Flash CWM recovery onto new device
6. Hook up new phone to computer and run this command: adb push NameOfBackup /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/
7. Boot into recovery and flash that backup
8. Reboot. It should look exactly like your old phone. Grab the file you want with all the passwords in it and back it up on your computer something. Now you can restore the other backup you made of this device or keep with your backup of the broken phone. Your call.
EDIT:
I just reread my post to make sure I included everything. You might have to move step 5 way up before step 1. You'll need a custom recovery to make a nandroid, so flash a custom recovery first.
Johmama said:
I hope I'm understanding your exact situation; feel free to let me know where I misunderstood you.
Ok, your friend bought a Nexus 4 a while back, has somehow broken the screen, bought a new Nexus 4, and wants to grab a nandroid backup and a document from a notepad-esque application from it?
If so, this is what I'd do. I'd grab the Nandroid backup from the old device, and restore it onto the new device (again, assuming both old and new devices are the same model i.e. Nexus 4)(also after backing up the new device, in case you ever need or want to revert to a fresh image) and grab the text file. What recovery are you using on the broken phone? I don't know the path for backups for TWRP, but if you're using CWM, the path is /mnt/shell/emulated/clockworkmod/backup/. Ok, let me make this easier by making a step-by-step. Some of it you probably already know how to do but I want to be as clear as possible.
1. Make a nandroid backup on new device in case something goes wrong, or you want to go back in the future
2. Hook up broken device to computer, open a cmd window in the platform-tools folder, containing adb.exe (shift right-click in an Explorer window and hit "Open command window here" is the fastest way)
3. Use this command: adb pull /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/ NameOfBackup
4. That will pull the backup and put it in a folder called NameOfBackup (whatever you called it) in the platform-tools folder containing adb.exe
5. Flash CWM recovery onto new device
6. Hook up new phone to computer and run this command: adb push NameOfBackup /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/
7. Boot into recovery and flash that backup
8. Reboot. It should look exactly like your old phone. Grab the file you want with all the passwords in it and back it up on your computer something. Now you can restore the other backup you made of this device or keep with your backup of the broken phone. Your call.
EDIT:
I just reread my post to make sure I included everything. You might have to move step 5 way up before step 1. You'll need a custom recovery to make a nandroid, so flash a custom recovery first.
Click to expand...
Click to collapse
you are awesome. thanks a ton. thats what i needed. just wasnt sure if the imei needed to match or whatnot. cwm is what i am using on the old phone. and ill make sure thats what goes on the new one once i root it. will come back and let you know how it goes. i still need to meet up with him and get his new phone to make things work.
once again. thank you.
ok so he thought he had debugging turned on. but he apparently does not. i keep getting device not recognized by adb. he has an icon of a jellybean with horns or antennas coming out of it. i thought that was the notif icon for debuggin. but after an image search i see that debugging is different.
anywho... it doesnt look like i can rig up an otg cable either because i need to be able to install a zip script before it will work. it looks like i am out of options. i guess i need to tell him to buy another screen. let me fix. and then he can sell it on craigslist and try to get his money back.
if there is anything i am missing... let me know. but for now i seem to have hit the end of the road.
Boot to recovery and use adb.
Either straight up pull the backup (might be more sane to make a tarball and pull that) or push the otg mod and use cwm to flash that.
If you have cwm touch, you can use adb or fastboot to flash the regular cwm.
ziddey said:
Boot to recovery and use adb.
Either straight up pull the backup (might be more sane to make a tarball and pull that) or push the otg mod and use cwm to flash that.
If you have cwm touch, you can use adb or fastboot to flash the regular cwm.
Click to expand...
Click to collapse
cool beans. did not know i could adb in recovery. ill give it a try after work, bout to head to bed. ill search tarball to find out what you are talking about also. i will need to push your .zip to it anyways for the pics and such. i guess i will go ahead and jump on amazon to get the cables and hub.
edit: i used ill and i wll several times. but too tired to go back and re-word. pardon the near impossible to follow post.
How much free space is on the phone? Tarballs are archives similar to zips (although without compression in base form). If you have the space for it, just make a big tarball and adb pull it. Only real reason to go OTG is if you want to be able to use the phone still-- hook up a usb hub, keyboard, mouse, usb stick.

Categories

Resources