Related
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
hushpup131 said:
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
Click to expand...
Click to collapse
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
jamcar said:
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
Click to expand...
Click to collapse
I am not able to get into the APX mode. The basis of my belief is there is no audible signal (USB to PC) and there is no new window opening inviting me to explore a new drive.
I have disconnected the battery both short term as well as over night, no response from the power only and power plus volume – buttons.
The charge light has turned green; no response from the buttons.
Measuring the voltage at the charger tip read 12+ volts. I am using a new USB to PC cable. Out of curiosity I unplugged the battery connector and re-connected to see the charge light switch off and on while the charger was connected. As a novice here, I suspect that test eliminated the charging circuit as a fault.
I'm in UBUNTU
loaded and extracted gtab.nvflash.1.1.branch.20110422 with cwmv8.zip
the response says:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
- what does this mean?
1. Is there any sort of display brightening (even briefly?) after you power on? In APX mode, for example, the screen will brighten slightly, then go dead again.
2. Try this test on Ubuntu to see if the tablet has gone into APX mode:
Code:
[I]Power off gTab.
Power on gTab using Power & Vol [-].[/I]
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[18045.279886] usb 1-1.2: new full speed USB device number 6 using ohci_hcd
[18045.384823] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7820[/B]
[18045.384830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18045.384835] usb 1-1.2: Product: APX
[18045.384839] usb 1-1.2: Manufacturer: NVIDIA Corp.
$
A USB product id of 7820 indicates APX mode on the gTab.
Post the exact output (if any) of your run here.
For reference this is the output when the gTab is running either CWM or the ROM:
Code:
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to the gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[17516.799429] usb 1-1.2: new full speed USB device number 5 using ohci_hcd
[17516.911353] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7100[/B]
[17516.911361] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17516.911366] usb 1-1.2: Product: NVIDIA Harmony
[17516.911370] usb 1-1.2: Manufacturer: NVIDIA
[17516.911374] usb 1-1.2: SerialNumber: 0270308341006257
$
The product id will be 7100.
[email protected]:~$ coonected USB to Gtab, power button plus vol minus 2 minutes
coonected: command not found
[email protected]:~$ sudo dmesg -c >/dev/nul
bash: /dev/nul: Permission denied
[email protected]:~$ pwd
/home/ubuntu
[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ pwd
/
[email protected]:/$ sudo dmesg -c >/dev/null
[email protected]:/$ dmesg
[email protected]:/$
[email protected]:/$
It's not surprising that you got no output--I screwed up. The sequence of steps was incorrect: the cable has to be connected between the 2 dmesg commands. Please repeat.
(If you want to insert inline comments on the command line do it like this:
Code:
$ [B]# This is just a comment.[/B]
The shell will ignore everything from the `#' character to the end of the line.)
And, this video is what I recommend to people whose bootloader seems to be trashed--which is what I think your problem is: How to unbrick your Viewsonic G-Tablet
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
The first 2 commands are not needed:
hushpup131 said:
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
Click to expand...
Click to collapse
Yeah, as I suspected, its a bad bootloader and/or other critical partition problem.
If you are certain that the USB cable and ports are OK (check using another device--try a "sudo adb devices" command with a phone, for instance) and you ran the second dmesg command after connecting the USB cable (otherwise, power off and do the sequence again), then your only option now is to follow the K1 pad-shorting procedure shown in the video.
BTW, you didn't answer question #1 in post #5, above. Is there any change in the display brighness after powering on?
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
[13557.908045] usb 4-1: new low-speed USB device number 4 using uhci_hcd
[13558.145227] input: Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input17
[13558.145525] generic-usb 0003:045E:00E1.0003: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00] on usb-0000:00:1a.1-1/input0
[13558.256080] usb 1-4: new high-speed USB device number 6 using ehci_hcd
[13558.397196] scsi9 : usb-storage 1-4:1.0
[13559.397403] scsi 9:0:0:0: Direct-Access Motorola A855 0001 PQ: 0 ANSI: 2
[13559.398816] sd 9:0:0:0: Attached scsi generic sg3 type 0
[13559.403602] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[email protected]:~$
question one, post five... there was no change in the display
There was no change in the display after shorting K1
hushpup131 said:
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
Click to expand...
Click to collapse
Your USB cable seems OK, but, I don't like that line above. Can you describe exactly what you did when you captured that output?
And, run through that dmesg sequence once again exactly as described and post the output. Also, connect the gTab directly to a USB port, and not through a hub.
Hi,
In fastboot mode my linux distro (Debian testing) can see and reboot the device:
Output of lsusb:
Bus 003 Device 011: ID 0502:33a5 Acer, Inc.
but with ./adb devices, I cannot see anything:
No trace in lsusb, debug usb is on, udev rules are ok, adb_usb.ini is ok and with ADB_TRACE="all", everything is ok except that there is no device in adb...
Any clue?
Thanks.
Ps: I did google around...
This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)
Awesome. First thing I'm going to do out of the box.
Sent from my Oneplus One with Tapatalk Pro.
peppy6582 said:
This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)
Click to expand...
Click to collapse
And don't forget, to put device in fastboot, press and hold button that is located on the bottom of the player, plug in the power cord and hold until led light flashes repeatedly.
Fastboot
On Ubuntu, ADB is not ever seeing my NP. I can get it in fastboot mode with the button, and my USB devices enumerate (2 different ones), but ADB never shows it connected.
Code:
[376711.228958] usb 3-2.4: new high-speed USB device number 12 using xhci_hcd
[376711.246426] usb 3-2.4: New USB device found, idVendor=18d1, idProduct=4ee0
[376711.246436] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[376711.246441] usb 3-2.4: Product: fugu
[376711.246445] usb 3-2.4: Manufacturer: Android
[376711.246450] usb 3-2.4: SerialNumber: 13737740
[376772.269599] usb 3-2.4: USB disconnect, device number 12
[376773.252023] usb 3-2.4: new high-speed USB device number 13 using xhci_hcd
[376773.282912] usb 3-2.4: New USB device found, idVendor=8086, idProduct=0a2c
[376773.282919] usb 3-2.4: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[376773.282923] usb 3-2.4: Product: MOOREFIELD
[376773.282926] usb 3-2.4: Manufacturer: INTEL
[376773.282943] usb 3-2.4: SerialNumber: <redacted>
Ahh, I forgot I had to enable USB debugging in the developer menu. The dev menu is enabled by clicking "Build" a handful of times from the "About" menu.
figured it out : windows , device manager , let me choose driver , selected ADB TESTING INTErFACE , all is good. hope this helps others,.
================================================================================================================
using windows 8 , holding down bottom button i get to fastboot , when i run "fastboot devices" i get nothing , when run adb devices i get " emulator-5554 device " ( that was bluestacks ) i had to end task . but still no luck. when i run "fastboot devices" i get nothing , when run adb devices i get nothing
i double checked developer mode , all good , windows 8 calls it FUGU , , in control panel . if i run 'fastboot oem unlock" all i get is "waiting for device "
what step did i miss? any help appreciated./.
I have the same problems running Linux Mint 17.
"adb shell" works OK when booting normally.
"sudo fastboot devices" shows nothing in bootloader/fastboot mode, and no other fastboot commands work. Also see:
<6>[84128.968111] usb 1-5: new high-speed USB device number 55 using ehci-pci
<6>[84129.106293] usb 1-5: New USB device found, idVendor=18d1, idProduct=4ee0
<6>[84129.106305] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
<6>[84129.106313] usb 1-5: Product: fugu
<6>[84129.106319] usb 1-5: Manufacturer: Android
<6>[84129.106324] usb 1-5: SerialNumber: DA4D....
I'm itching for root to explore more.
fastboot problem is due to need for new fastboot.
I've attached the Linux version in my updated SDK. Windows version is in SDK on Google site somewhere I guess.
Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.
bsara said:
Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.
Click to expand...
Click to collapse
And one that doesn't require a working adb connection first.
Device not found
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>
dreadprinz said:
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
The command is "adb reboot-bootloader" not "fastboot"
Also, double check that you have the latest platform tools installed from the SDK manager.
Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed
volwrath said:
Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed
Click to expand...
Click to collapse
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.
bsara said:
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.
Click to expand...
Click to collapse
I don't think so.
I haven't upgraded mine in quite a while and fastboot had no problem seeing the player. I am updating my sdk platform tools as we speak.
But then again I guess they are fairly new since I updated them to play with my google watch
Device not found
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Hmm I don't see Enable oem unlock anywhere.
vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Maybe i am missing something here, but i don't see "Enable OEM unlock" anywhere.
dreadprinz said:
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.
Click to expand...
Click to collapse
You've listed the version of you "Android SDK Tools" not the "Android SDK Platform-tools" (which is found right below it in the SDK manager). At any rate, you probably are having a driver issue (I'm assuming that you're using Windows). I personally can't help you much there since I use Ubuntu, but this tool for Nexus devices might help: http://www.wugfresh.com/nrt. I know that the Player isn't listed there...but with that tool you can install the generic drivers...perhaps it will fix things for you.
Also, as stated before, you can (for the time being) just hold down the button on the bottom of the device while you plug in the device and it will boot into the bootloader (I.E. fastboot mode). Then run "fastboot devices" to see if anything shows up, if not...I would keep looking into the driver instructions on the tool I listed above. Also, to ensure that adb is seeing your device, you can also run "adb devices". Also, make sure that no other android devices that have USB debugging enabled are plugged in while you run your command, otherwise it won't succeed because it won't know which device to pick...or just run "adb -s [DEVICE_ID] reboot-bootloader" where [DEVICE_ID] is the id listed when running adb devices. Good luck.
And that "Enable OEM unlock" stuff is not true...just ignore it. Once in fastboot, you'll just need to run "fastboot oem unlock" twice in a row for the unlock to occur.
Hello,
I have a display malfunction with my Pixel 3a: the display is black
I can boot the device and connect with PC.
However, when I try to use adb commands a confirmation is pending:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
9BMAY1KGP2 unauthorized
Is there any option to fetch all data from the device (adb pull)?
THX
c.monty said:
Hello,
I have a display malfunction with my Pixel 3a: the display is black
I can boot the device and connect with PC.
However, when I try to use adb commands a confirmation is pending:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
9BMAY1KGP2 unauthorized
Is there any option to fetch all data from the device (adb pull)?
THX
Click to expand...
Click to collapse
Not if you haven't enabled usb debugging in developer settings.
Actually I did enable "USB debugging" in developer settings.
However, I do remember that I always had to confirm the request on the device.
With the broken display I cannot confirm.
Question:
Is there anything like SSH with Android devices?
I mean if I setup SSH on a PC I always can connect remotely although there's no display connected to the PC.
Hello, guys
first i read the diff between soft/hard brick, and i think i'm in the soft case, cause i can get in recovery menu.
adb dont see the phone at all,
fastboot can, but not 'fastboot oem unlock' , neither 'fastboot boot recover.img' works. Actually command prompt wait there for ever, untin the PC kernel ( linux deb 11), break fastboot usb connection, with a reason of connection timeout. this timeout is after 30minutes ....
i manage to backup user data for the recovery menu, in 3 files 2x2G 1x1.7G ( i think because of fat ),
but the revcovery menu fail to [ wipe data/factory reset ]. Strange ? Any ideas?
here is the model f the tablet,
==> /var/log/syslog <==
Nov 6 20:12:48 localhost kernel: [1024828.830129] usb 5-2: New USB device found, idVendor=0bb4, idProduct=0c01, bcdDevice= 1.00
Nov 6 20:12:48 localhost kernel: [1024828.830135] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 6 20:12:48 localhost kernel: [1024828.830138] usb 5-2: Product: Android
Nov 6 20:12:48 localhost kernel: [1024828.830140] usb 5-2: Manufacturer: MediaTek
Nov 6 20:12:48 localhost kernel: [1024828.830142] usb 5-2: SerialNumber: mt6582_phone
#---------------------------------------------------------------------------------------------------
# ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
#---------------------------------------------------------------------------------------------------
# Android system recovery (3e)
# A7-30DC_S0000129_150831_ROW
#---------------------------------------------------------------------------------------------------
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
jwoegerbauer said:
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
Click to expand...
Click to collapse
i know, everythinks works just fine, with other android devices.
( i'm using linux by the way )
My problem right now is,
why the stock recovery fail to wipe/factory reset ?
no fastboot or adb
The tablet stuck in he lenovo logo on boot for ever,
so adb dont have any way in this stage
I try 'update cache from ADB' just to see if adb can see it, but no
when 'fastboot boot recovery.img'
the phone (tablet), report get some bytes
but nothing else
when 'fastboot oem unlock', nothing happens, both the phone and the terminal
i use this links for recovery images:
https://forum.xda-developers.com/attachments/recovery_p780_cwm_6-0-1-5-7z.2840100/
https://forum.xda-developers.com/attachments/p780_recovery_twrp_2-6-3-0-zip.2840101
any pins on hardware, to triger factory reset .... ?