Related
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
joshw0000 said:
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
Click to expand...
Click to collapse
download htc sync that should fix ur problem , it did for me
Yes HTC sync updated mine as soon as your phone is acknowledged by HTC sync it should update your usb drivers
FYI HTC sync did NOT work for me on Windows 7. I had to do some pretty annoying stuff to stop windows from installing the regular drivers automatically. If HTC sync doesn't work I can try to help.
If HTC Sync doesn't help, try the following steps.
1. Unplug your Eris from the PC
2. Open Device Manager and delete the Android device
3. Reboot your PC
4. Once in Windows, connect your Eris
5. The drivers should load automatically, if not point it to the SDK drivers folder
Good luck!
Any more ideas
First I tried downloading HTC Sync on my laptop (running Vista) and that didn't do it. Then I deleted the drivers and tried to manually download them back with the ones in the USB folder of SDK and still it wouldn't work.
So I started over and downloaded SDK and Java to my pc (Windows 7) and tried to update the drivers with the ones found in SDK and it wouldn't let me. So I deleted the drivers, unplugged my phone, and plugged it back up. Before I could attempt to direct it to download the intended USB drivers, Windows 7 had already updated with the drivers of it's choice. I can't win for losing.
If you don't mind using one of those "Live" Linux CDs, you could install the recovery using fastboot.
No need to install anything on the PC, and no drivers are needed for Linux, no SDK, no Java, no adb; just make sure to run fastboot as root.
The downloads of fastboot and the Amon_RA recovery are small, so they will easily fit in /tmp.
bftb0
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
When you have your phone plugges in do you have it set to "charge" or "sync"? I know all the how to's say yo have it set to charge only but the inly way my computer ever finds my phone is if it us set to sync.
-------------------------------------
Sent via the XDA Tapatalk App
I set it to charge. I was finally able to install the correct driver. I selected a Google driver from the list it gave me (which my computer did not like) then went back and updated the drivers with those found in the tools usb folder of SDK. IT FINALLY LET ME!
Now I have a new problem. I'm using the command prompt and trying to create a custom recovery. I set it to the tools directory in SDK (where the flash and recovery images are) and I'm entering the commands exactly like the "how to" instructions have them. I keep getting "adb: not found" errors.
Can anyone tell me what I'm doing wrong?
joshw0000 said:
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
Click to expand...
Click to collapse
Well, in the long run it is probably a good idea to resolve the driver install problems you are having on your PC, because it is very useful to have "adb" around, even if you are already rooted and have the ROM of your choice installed.
But, if you would like to do this, here's an outline below. Note that the point of the "Live" CDs is that you are not installing Linux on your machine, you are just booting it directly from the CD - the OS and hard drive on your PC are untouched.
1) Download an ".iso" file from your favorite Linux distro [ 3 ] for their "live" CD. (BIG download, usually 600+ MB)
2) Burn the .iso file to a CD as a bootable CD. (Most decent CD/DVD burner programs know what an .ISO file is, but might refer to them as a disk image).
3) Boot your PC off it! (You might need to hit a key on your PC right after you power it on to go into a boot menu, or the BIOS setup to change the boot order so your PC will try to boot from the CD/DVD before it tries the hard drive).
4) Copy the fastboot [ 1 ] executable for Linux and the Amon_RA recovery image [ 2 ] to /tmp "somehow" - you could just download it using the Linux browser if your network come up automatically (wired ethernet), or you could put them onto a USB key beforehand, and plug that in after Linux has booted; it should mount automatically.
5) Then, open up a terminal window and become root. (Type either "su" or "sudo /bin/bash" - depends on the Linux distro)
6) Attach your (well-charged) phone to the phone via USB, and power it up in fastboot mode (Send+End simultaneously)
cd /tmp
chmod 755 fastboot
md5sum recovery.img (check file sig)
./fastboot devices (check to see you are connected)
./fastboot flash recovery recovery.img
Obviously, if you need to look something up on the internet, it is useful to be networked, so you can use a web browser. The Linux boot will try to autoconfigure network interfaces automatically, but this is going to be most straightforward with a wired connection (Ethernet). Alternatively, if you have another PC or laptop nearby, you could use that.
Good luck.
Edits:
[ 1 ] Find Linux version of fastboot from HTC midway down this page - md5sum 9851bb6ad29cd4b60c9ba9d011ba9efd
[ 2 ] Amon_RA's recovery is located on this XDA page - md5sum e3932991f097993602af3c7a4b61a4f8
[ 3 ] Ubuntu's Current (x32) CD for v10.04 this page
NOTE: This CD is both a "Live" CD and an Install CD. You DO NOT WANT TO INSTALL ANYTHING; you are using the "Live" CD function - see the "show me how" link under Item #3 ("Try It!") on the above linked page
[ 4 ] Various OpenSuSe 11.2 Live CDs
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
joshw0000 said:
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
Click to expand...
Click to collapse
First, relax and take a deep breath; everything's going to be fine.
In the recovery main menu, there is an Item called something like "MS-USB toggle" or something like that. It does not use the adb driver, it uses a standard "Mass Storage Device" USB driver already on the PC. The purpose of this function is to make the SD Card mount on the PC when the Amon_RA recovery is running.
Try that - it should work.
Then, download a conservative ROM such as Ivanmmj's Official 1.0 alpha, or Jcase's "Plain Jane", and copy it to your SD card.
After you have done that, make sure to check the MD5 sum of that .zip file on the SD card. (You should be doing this already).
Then, cleanly dismount the USB drive from the PC with the "Safely Remove Hardware" thingamabob, and toggle "off" the MS-USB toggle on the phone. Return to the main menu, wipe /data, and then flash the "conservative" ROM.
Then boot the conservative ROM just to verify everything is OK.
Next, Backup anything from the SD card that you don't already have (this step might be optional), and boot into recovery, and unpartition your SD card so that the only thing that is there is the VFAT partition.
For the moment, I'll give you some advice: f*ck A2SD. You need to gain some familarity with how the various versions of a2sd work before you start using it..
Very likely you were just stuck in a boot loop created by the re-partitioning you performed after initial configuration of a ROM that uses a2sd. Frankly, it is easy to create conditions for this, especially if you switch between ROMs that use different versions of a2sd, and/or don't understand that certain versions are not correctly backed up with Nandroid at the moment (e.g CLB).
bftb0
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
My Nook Tablet just updated to the dreaded 1.4.1 version which makes sideloading pretty difficult.
I was reading this article which has steps to sideload apps onto the 1.4.1 NT without rooting it, and pointed to downloading this script on the XDA forums which will push the apk onto the plugged in tablet, as long as the apk is in the same folder as the Sideload script files.
So, steps 1 to 5 weren't a real problem but its Step 6 that I'm stuck on.
There is a Sideload BAT script which seemed to run (its disclaimer is that it will only run if it finds an Android device -- which is a clear indication that it could find and recognize that my Nook Tablet is plugged in). It even says C:\Sideload>adb wait-for-device. However, when I try to tell it to install the apk via Command Prompt (I type in: adb install Amazon_Appstore-release.apk ), it returns "error: device not found" .
Just for good measure, I also type in C:\Sideload\adb devices and it returns: List of devices attached .
I'd greatly appreciate if somebody could help me with this--I really have it up a wall and would just like to put this problem to bed. Thanks!
i'm having the same exact problems here! are there any specific drivers to install?
Yep, I was still fairly a noob at this when I first posted but have learned a lot ever since. Here's what you want to do:
(btw, I factory resetted to 1.4.0--you may need to as well):
When it says "no device found", it's corresponding to this command line : adb install whatevernameofapp.apk . I interpreted "no device found" to mean that it does not know what "adb" means in the command.
For it to recognize all "adb" related commands, you have to have the USB drivers installed. Look for tgps_launcher.apk on this link: http://forum.xda-developers.com/showthread.php?t=1354487. That will set you up with having you Nook to accept third party applications + having it on UBS debug mode.
Then, install the drivers (I saw this YouTube walkthrough because it is NOT intuitive and you want to be sure you're doing it right , it's not the way you would traditionally update drivers for a mouse or keyboard; here: http://www.youtube.com/watch?v=ZtGveN7jbzs )
After that, I followed the instructions on this article, made a folder in C:, called it sideload, and also pasted an .apk. Now, when I do the Commant Prompt, it says this: http://img23.imageshack.us/img23/2914/cmdnookadb.jpg . While, the transfer was successful, I haven't been able to see the app on my tablet. Does anyone know where I can find this (data/local wasn't found when I connected the tablet to my PC either, and it wasn't on my SD or so). Is it because I'm still on 1.4.0?
Let me know if you get it working all the way!
I followed all those directions exactly. I had received the No Device Found error. I followed the Youtube directions to add drivers and it seems like I did it correctly. I am seeing the android device on the device manager.
I tried running the script again and got the same error! I'm now stuck!
I had the amazon marketplace already installed and was using it successfully until my nook updated to 1.4.2. I thought I had ES File Explorer downloaded but for some reason I can't find it! So I now I am trying to sideload ES File Explorer this way but it wont work!
0x2080
^ put that in %userprofile%\.android\adb_usb.ini
Can you give me more specific instructions on how to do that?
FYI - I have ver 1.4.2 and I am NOT rooted. I have already enabled unknown sources and downloaded the amazon market. I was installing 3rd party apps fine before the update.
[HOW-TO] Use ADB tool | Android Debug Bridge
You need to revert to stock 1.4.0, there are easier and faster ways to do that now > check development section. Basically you need to have CWM booting from sdcard then flash stock ROMS posted >> Albert and I have posted 1.4.0 stock ROMs.
~ Veronica
Moved To Q&A
So since cm7 is so close, I decided to try the flashable cwm from indirect. Unfortunately, after that all that happens is my nook tries to boot, I see the white screen with the package, and then it turns off. If I have it plugged in, it will just loop.
I have partitioned a 4gb sandisk with a 50mb FAT 32 partition as the primary, and have given it the lba and boot flags in gparted from my ubuntu laptop. I never could get it to boot off the sd card.
So now I must ask, where do I go from here. I've searched and crawled this forum, but with the boot loop and not being able to boot off of SD, I am unsure where to go next.
Any tips? To me, it looks like it just keeps trying to boot from the recovery. N + Power yields same results as above. Could really use some help with this head scratcher
So you cant access to CWM at all, if not somehow you must make the sdcard method to work in order to apply the fix posted by Indirect, that is the only way im afraid.
~ Veronica
http://forum.xda-developers.com/showthread.php?p=21785424 there's a link to indirects fix for broken recovery.
_______sig starts here______
Even you were a beginner once
If this post helped click the thanks button!
remember QTIP - Quit Taking It Personal
Okay, I get that. I have two questions though,
1: Does this mean I have to do the recovery method vs the bootable sd card?
2: How am I supposed to run commands to a device that keeps rebooting and doesn't give windows time to communicate with it, or will it send commands to it even though its rebooting?
cleverghost said:
Okay, I get that. I have two questions though,
1: Does this mean I have to do the recovery method vs the bootable sd card?
2: How am I supposed to run commands to a device that keeps rebooting and doesn't give windows time to communicate with it, or will it send commands to it even though its rebooting?
Click to expand...
Click to collapse
To apply Indirect's fix first you need to use Goncezilla's CWM sdcard method to boot into CWM once in CWM basically you use adb tools to fix it, use the link posted below by @dodgepot and read the OP carefully to understand the process.
~ Veronica
Thank you for the replies....
So I've gone through and tried once again to get my nook to boot from SD, and still I can't get it to boot. There is a way to do it using DISKPART in windows, I've made the 50mb fat partition, and set it to active. Have there been any other issues with getting it to work?
Poked around the CM7 thread again, apparently CelticWebSolutions was having a problem booting from an sd card.
Anyone know what he did exactly?
It works! Installing android sdk now
cleverghost said:
It works! Installing android sdk now
Click to expand...
Click to collapse
If you are on windows there is no need of SDK it will just give you troubles with the drivers, you should already have the drivers and adb if you rooted your nook tablet before. The adb drivers came in the zip provided for root and should be in C:\ntroot folder.
~ Veronica
I had access to a xp laptop when I did it on before. Using a win 7 64 bit right now, and indirect's batch file stops part of the way through. I had problems in 64 bit before, using the usb drivers from snowball's mod. Guess its a 64 bit problem. (have used usbdeview and I have verified it sets up as an android composite device.)
cleverghost said:
I had access to a xp laptop when I did it on before. Using a win 7 64 bit right now, and indirect's batch file stops part of the way through. I had problems in 64 bit before, using the usb drivers from snowball's mod. Guess its a 64 bit problem. (have used usbdeview and I have verified it sets up as an android composite device.)
Click to expand...
Click to collapse
i have a windows x64 bits too and when i rooted did not have any problem, do not install sdk it is not necessary, run the runmefirst.bat the one that comes in the .zip with the root files not the one that comes in the drivers.zip from Indirect's root. Snowball uses the same drivers as Indirect.
~ Veronica
I did everything stated above ... still a no go.
I tried indirect's driver half a dozen times and can never seem to get it working on x64. I decided to format my laptop and put xp on it. Like I said, last time I used XP, no problems at all.
Edit: Okay, so I tried it on another x64 machine, and I still run into the same issue!
1. run runmefirst.bat
2. Plug in nook
3. Right click nook device with /!\ and update drivers from c:\ntroot
4. Open up bat from indirect's thread
5. Y, Enter
6. Program starts abd..... locks up right after it states it, I waited a good 10 mins for results.
7. Use USBDeview and delete all references to usb mass storage, nook, and android devices. Unplug nook.
8. Plug in nook and repeat 3-6
9. Bang head against wall lol.
It's probably something stupid I overlooked. Feel free to flame away, I'll take it like a man XD. I started with a nook color, but this is pretty much my first tablet experience. You guys have a lot of experience, and I just want to make sure I am not missing something obvious. (I guess I just don't want to seem like a noob, more like a half noob )
Truth be told, I don't know if this is an issue... but I am runing W7x64 Ultimate N
Alright, so adb devices lists my device as "recovery".
I run the script and it still seems to just stop.
Uhmmm the steps you've done are right, I run a windows professional no N edition but that shouldn't be a problem. Maybe try disabling firewall, antivirus if any also Use ccleaner to clean your registries and cache of your machine, reboot and then try again, I want to repeat do not install SDK (just making sure).
~ Veronica
Sent from XDA premium using my Nook Tablet
okay great! Then I do understand the steps.
Yep, no SDK.
Edit: Going to crash now, ill wake up in a bit and take another crack at it. Thanks for your help so far
Alrighty. I woke up again and decided to give it a try from step one. Still a no go. Going to try wiping my drivers again. I've also disabled all antivirus/antimalware....
Looks like its going to be a fun day heh.
ok keep us updated on how you doing.
~ Veronica
Should I see the nook and sd drives mounting in Windows? Right now, I see the drives, but I can't access them. I don't know if that matters or not.....
Also, when I do an adb devices, mine shows as:
Code:
<String of numbers> recovery
Thats correct?
I also took a look at the batch file and might try to run the first few commands to see if I can find where the problem is manually. I have a feeling it's stopping at:
Code:
adb wait-for-device
We'll see though.
EDIT: Unless when you run the command it's supposed to not do anything, then yes. It's hanging.
Alright. Here is what I've found out.
I've done some forum crawling, and I happened upon a post by Loglug where he says to run the following commands:
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
All of the commands work except the second one. It basically echos back and tells me how to use the command. Now, I read a little further into his post and it says that if you do not get the BN recovery after 8 reboots, your recovery partition might be messed up. Could this be what is preventing me from recovering?
EDIT: NEVERMIND! I am up. Sorry, I feel pretty stupid now lol. I just ran the second command wrong -_-. Sorry, my answer was in the forums, just couldn't find it!
So, last night i tried to flash GtabComb to my 1.1 Gtab. After 3 unsuccessful installs (which I now believe are attributed to the system partition size of only 200 rather than 250 [help here would also be apprciated]) i downloaded the latest Rom Manager and updated ClockWork Mod. After the initial scare that my SD card had been totally formatted, i found that for some reason, this new CWM likes to use the second SD card... You know, the one with no backups or anything saved to it. For now, I am running a random ROM (Vegan Gingerbread) until i find out how to switch the SD card read by CMW. So any help guys? It's probably something really simple I'm over looking.. Help is appreciated greatly. Thanks
Edit: On a side note, I finally got GtabComb to load on my tablet! Seems I only needed a little bit of patience...
theshafe said:
So, last night i tried to flash GtabComb to my 1.1 Gtab. After 3 unsuccessful installs (which I now believe are attributed to the system partition size of only 200 rather than 250 [help here would also be apprciated]) i downloaded the latest Rom Manager and updated ClockWork Mod. After the initial scare that my SD card had been totally formatted, i found that for some reason, this new CWM likes to use the second SD card... You know, the one with no backups or anything saved to it. For now, I am running a random ROM (Vegan Gingerbread) until i find out how to switch the SD card read by CMW. So any help guys? It's probably something really simple I'm over looking.. Help is appreciated greatly. Thanks
Click to expand...
Click to collapse
The best way to install CWM is through NVflash. Rom manager is really designed for phones not this tablet. NVflash is simple and easy to use as long as you have a desktop or laptop using either windows or Linux. Here is the link to guide you through those steps. Helped me out when I was in a jam.
http://viewsonic-gtablet-for-dummies...om/nvflash.htm
Thanks for the advice! NVFlashing is a tad of a problem for me, however. I've actually commented on that particualr NVFlashing tutorial earlier today explaining how my computer won't recognize my tablet while it's in APX mode. I seem to have the worst luck with this kid of thing..
Would there another way to change which card is being read?
Do not use Rom Manager on the Gtablet it will mess things up. You can go to this link and download a .zip installable version of CWM for your bootloader. There are versions for installing from either the internal or external sdcard. If you are not installing from the external sdcard, it is best to remove it.
You could also check out this thread, and this one for more info.
It sure does mess things up! And that CWM.zip would be great had I not had another (worse) version already installed.. woe is me. I'll give those threads a read tomorrow and hope something turns up. Thanks for the links!
DaggerDave said:
Do not use Rom Manager on the Gtablet it will mess things up. You can go to this link and download a .zip installable version of CWM for your bootloader. There are versions for installing from either the internal or external sdcard. If you are not installing from the external sdcard, it is best to remove it.
You could also check out this thread, and this one for more info.
Click to expand...
Click to collapse
That would be the way to go but if you can't access the current CWM you cannot get it to install anything. The only other alternative would be to figure out why the computer won't recognize the tablet in APX mode. What OS are you trying it with?
Try this:
Download this .zip file and extract it to your Gtablet's sdcard.
Using a root file manager (ES, Root Explorer, etc.) mount /system as read-write (rw) and move the downloaded files in each folder to their proper locations (copy the system/etc/recovery folder into /system/etc and the files in system/bin into /system/bin) and make sure all the permissions are correct. The recovery images should be -rw-r--r--, the scripts inside of /bin should be -rwxr-xr-x and flash_image should be -rw-r--r--.
Open a terminal emulator and type 'su' (without quotes) and allow SuperUser when it asks. Your shell prompt should go from a '$' to a '#'. Now type 'cwmrecovery.sh' (without quotes) and enter. That should install cwm-08 for you, just exit when it finishes and try to reboot into recovery. You can use the 'fixrecovery.sh' script to flash the stock 1.1 recovery if you ever need to.
See the last thread I linked to in my last post for more info on this. Good luck!
DaggerDave said:
Try this:
Download this .zip file and extract it to your Gtablet's sdcard.
See the last thread I linked to in my last post for more info on this. Good luck!
Click to expand...
Click to collapse
Just extracted to the external SD that was being read from and updated from there with the new CWM and bam! .08 is on and working like a charm. Many thanks!
nobe1976 said:
Another alternative would be to figure out why the computer won't recognize the tablet in APX mode. What OS are you trying it with?
Click to expand...
Click to collapse
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck[/QUOTE]
The OS on the tablet doesn't matter since the APX mode is the tablets download mode. The OS on you computer is what might be the issue, or could even be just a bad USB port or even drivers being used. If the computer keeps promptings that software needs to be installed. Guied the it to install them from the extracted NVflash file and install the ones that are in the pack.
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck
Click to expand...
Click to collapse
As the post above said, the OS on your PC is probably your problem. Which OS are you using? WinXP, Win7? I can't for the life of me get Windows7 to recognize my ICS Gtablet but o'well!
If you are comfortable with using or trying Linux, you could try installing Knoppix on a USB drive and run that. I think Knoppix has everything set up for MTP & ADB already and is 'live' so no real configuration is needed to get it running (except for your wifi of course). Just use the Linux version included in most NvFlash packages. If you have a fairly powerful computer, you could also try running Linux in a VM, but Knoppix doesn't run in a VM very well.
My favorite is Arch Linux (not in a VM). Although you have to build and configure the system yourself from the ground up. Since I started using Linux I have really enjoyed it. It is much faster than Windows, more secure and gives me less problems than the Win PCs I deal with. Check out this site if you are interested in Linux.
DaggerDave said:
As the post above said, the OS on your PC is probably your problem. Which OS are you using? WinXP, Win7? I can't for the life of me get Windows7 to recognize my ICS Gtablet but o'well!
If you are comfortable with using or trying Linux, you could try installing Knoppix on a USB drive and run that. I think Knoppix has everything set up for MTP & ADB already and is 'live' so no real configuration is needed to get it running (except for your wifi of course). Just use the Linux version included in most NvFlash packages. If you have a fairly powerful computer, you could also try running Linux in a VM, but Knoppix doesn't run in a VM very well.
My favorite is Arch Linux (not in a VM). Although you have to build and configure the system yourself from the ground up. Since I started using Linux I have really enjoyed it. It is much faster than Windows, more secure and gives me less problems than the Win PCs I deal with. Check out this site if you are interested in Linux.
Click to expand...
Click to collapse
To top on this excellent information. If you decided to try a Linux disto I would recommend a version of Ubuntu, doesn't really matter which one they are all really user friendly and depending on you pc setup depends on which version of it you can use. I have 11.05 installed on a 2nd partition for doing my Droid stuff on a computer that is around 9 years old, runs smooth. Windows xp is the other alternative which I have used several times NVflashing stuff, but adb seems to run better through Linux in my opinion.
Ah, mind went blank there. Right now, all I have is a windows 7 laptop (my XP desktop and older Vista laptop are probably long gone) Ive attempted to flash before with the vista laptop to no avail. In both instances, I connect the tablet in APX and it was not even recognized as a connected device. I'm hesitant to run Linux, even from a flash drive. If I get the chance to soon, I may very well end up doing it, as it appears the ONLY option.. Thanks for your help guys. If you could think of anyway for Windows 7 to recognize my tablet, please let me know. You guys are a great help. Thanks again!
If you haven't already tried this maybe it will work for you.
- Put the tablet into APX mode, then plug in the USB. Windows7 will drag on then fail installing the drivers, as usual.
- Go to Control Panel->Hardware and Sound->Device Manager and find the '!' (unknown device)
- Right click and choose Properties, then Uninstall Driver (if it is an option)
- Next, click on Update Driver, then choose Browse My Computer ...
- Navigate to the NVFlash folder (the one you extracted from the nvflash .zip you downloaded)
- Open the folder inside called 'usbpcdriver' or similar, and select the .inf file (NvidiaUsb.inf) and choose to install it. Once it installs, it should recognize the tablet as a MTP device. If not turn off the tablet, unplug the USB, restart Windows and plug it back in when it is finished rebooting and start the tablet in APX mode again. If it still doesn't recognize it try the whole process over agian.
I can understand being hesitant toward running Linux but running from a flash drive or in a VM is pretty safe, as in if you mess up the OS you can always start over without damaging Windows. Done it many times! Try running Ubuntu in a virtual machine such as Virtual Box, it is almost as user friendly as windows and you can have the VM capture USB devices such as the Gtablet which Ubuntu should recognize. Probably won't run very fast on a laptop but if you have at least a dual core with 2 GB of ram it should be pretty smooth.
Not trying to push Linux on you or anything, just some suggestions. From what I hear most of the Gtab devs use Windows7 and it seems to work great for them!
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
ewgrashorn said:
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
Click to expand...
Click to collapse
Are you using adb on Ubuntu? You have to run adb start-server as root.
Mevordel said:
Are you using adb on Ubuntu? You have to run adb start-server as root.
Click to expand...
Click to collapse
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
ewgrashorn said:
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
Click to expand...
Click to collapse
The build property ro.adb.secure=0 will override that. You can try putting it in build.prop, but if it doesn't work, you'll have to put it in /default.prop, which requires modifying the kernel ramdisk. While you're at it, ro.secure=0 will give you an automatic root shell.