Related
I've searched, but the only similar problems either solely involved Windows or ended in a return/RMA. I'm really hoping someone can help me.
Story: I restored a backup using TWRP 2.2.1.3 (ICS). I'm honestly not sure which ROM it was, could have been stock. I was actually restoring it to find out what it was. Before the restore, I wiped data, cache, dalvik cache, and system. The restore went perfectly, no errors or anything out of the ordinary. When I rebooted into the system, it hung on the initial bootsplash. I waited a few minutes before giving up and booting back into recovery. I rebooted by holding down the power button for a while (30 seconds maybe?) and held Volume Down as the tablet booted.
Problem: Instead of the message to press Volume Up to boot into recovery, it just went directly to the screen that comes up after waiting where it counts down the cold boot time and gives you three options - except now, I only have two: Wipe Data and Fastboot. Great, at least I have fastboot. Right? Wrong, apparently. Selecting that option shows the message "Starting Fastboot USB download protocol", but the command
Code:
./fastboot devices
returns a blank line. Likewise,
Code:
./fastboot -i 0x0B05 flash recovery ./openrecovery-twrp-2.2.1.3-tf300t.blob
returns "<waiting for device>".
Attempted troubleshooting: I tried rebooting the device and starting fastboot while attached via USB, and I've tried starting fastboot before plugging in the USB cable. I tried rebooting to the system and using ADB at the hanging bootsplash. There was no ADB access. I've tried restarting the computer while the tablet is plugged in and in fastboot mode.
OS: Debian Testing; ia32-libs, ia32-libs-dev, and ia32-libs-gtk installed
Kernel: 3.5.2 from Debian repos + BFS + BFQ, self-compiled
Previous ROM: Blackbean 8/15
Other: I have not flashed the JB OTA yet (restoring the backup was actually in preparation for the JB OTA; I wanted to see if I had a rooted stock backup). I did not flash the JB version of TWRP. I have used ADB and Fastboot on my tablet successfully in the past on the same computer.
I hope I didn't forget anything relevant. If I think of something else, I'll post it.
Edit: Possible progress? I selected the Wipe Data option, and it loaded TWRP and wiped data. Unfortunately, it immediately attempted to boot the system, which just hung on the initial splashscreen. So, I still have a recovery. I just need a way to boot into it. I'll keep messing around, I guess.
Bump, plus an update.
I realized I should probably run lsusb to see if the computer is actually detecting the tablet. This is the output of "lsusb -v". The output is the same whether the tablet is in Fastboot mode or hanging at the bootsplash. ADB still won't recognize the connected device while on the bootsplash. Interestingly, the iProduct seems to be labeled "Fastboot" in both cases, but fastboot doesn't recognize the tablet either.
Code:
Bus 002 Device 004: ID 0b05:4daf ASUSTek Computer, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0b05 ASUSTek Computer, Inc.
idProduct 0x4daf
bcdDevice 0.00
iManufacturer 1 ASUSTeK COMPUTER INC.
iProduct 2 Fastboot
iSerial 3 00000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 32mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 66
bDeviceProtocol 3
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
I'm really hoping this can help someone. If my computer is recognizing the tablet, there may be some way to bruteforce the tablet into recovery or something, I think.
you may have adb available during the wipe process, you can try to push an install instruction to /cache/recovery/command
Code:
install_package=path to your rescue zip
you could also try to delete /cache/recovery/command and may end up looking at the recovery UI
you would have to be very lucky for this to work
if TWRP uses an external executable to format partitions you could also try to attack that with chmod -x /sbin/mke2fs
and try to get an error screen to display, or replace it with a script that goes in the an endless loop so you have enough
time to
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
untermensch said:
you may have adb available during the wipe process, you can try to push an install instruction to /cache/recovery/command
Code:
install_package=path to your rescue zip
Click to expand...
Click to collapse
Yeah, I tried that, actually, but forgot to add it to my attempted troubleshooting list. I ran "adb devices" before the wipe so it would be able to detect it ASAP, but I got nothing. It just sat on "<waiting for device>" during the whole process.
you could also try to delete /cache/recovery/command and may end up looking at the recovery UI
you would have to be very lucky for this to work
if TWRP uses an external executable to format partitions you could also try to attack that with chmod -x /sbin/mke2fs
and try to get an error screen to display, or replace it with a script that goes in the an endless loop so you have enough
time to
Code:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
I'm assuming this part depends on the first part working. I'll fiddle with it when I get home from work in the morning.
This is so aggravating. I had no idea that restoring a backup could do this. And it's even more frustrating that my computer can see the tablet at a low level but can't seem to interface with it in userspace.
My next step was going to be to try to PM Asus_USA and Gary Key to see if they had any ideas, but I'm sure they would just tell me they can't help and I need to RMA it.
I may try to contact AndroidRoot.mobi to see if they've seen this or have any ideas, but I'm not sure how willing they would be to help, even if they could. If anyone besides Asus_USA can help, it's them. It may be my last hope before RMA.
i have the same problem ecept it wont even leave the asus logo screen when it first starts up can get into recovery fastboot adb apx nothing i cant even get a wipe device i installed the new jelly bean on mine and something whent wrong cause keyboard wifi ect. was malfunctioning so i factory restored it no help tried wiping data in recovery and now its stuck if any one has any ideas for us thanks
I'm sorry but i saw your title and just want to say thank God I'm not the only one! Good luck and i feel your pain. Gnex myself
*This Jedi master be a Ninj-ESS*
ditto
i flashed cwm touch with fastboot but didn't read the tread properly, it was for stock JB, so now it's stuck on asus boot logo with "this device is unlocked" text up top and when i press power + vol down it's stuck on " starting bootloader kernel image" :crying:
I'm going to lurk your thread. Different device and everything but if you figure something in adb maybe I can use it too.
I don't have any other bootloader except stock, my pad was rooted....
I tried the update and it failed, rebooted and ICS popped back up and I received a message stating that the update failed and ICS was being restored.
I put a copy of the update file in the CACHE folder and tried to update again - this event failed as well, but now my computer won't recognize my pad, and the USB option doesn't show up on the stock recovery (pic below).
Checked device manager and the ASUS PAD is showing error code 10 (device stopped)... downloaded new drivers, rebooted computer, tried to figure out how to load Motorola drivers ( http://forum.xda-developers.com/showthread.php?t=1685540 ), but nothing worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like we have similar problems... Hope we don't have to send the pads in to get fixed.
I have gnex and same thing almost. I did a restore from job to pics and its like adb installs drivers backwards.
Sent from my Galaxy Nexus using xda app-developers app
newowner said:
I don't have any other bootloader except stock, my pad was rooted....
I tried the update and it failed, rebooted and ICS popped back up and I received a message stating that the update failed and ICS was being restored.
I put a copy of the update file in the CACHE folder and tried to update again - this event failed as well, but now my computer won't recognize my pad, and the USB option doesn't show up on the stock recovery (pic below).
Checked device manager and the ASUS PAD is showing error code 10 (device stopped)... downloaded new drivers, rebooted computer, tried to figure out how to load Motorola drivers ( http://forum.xda-developers.com/showthread.php?t=1685540 ), but nothing worked.
Looks like we have similar problems... Hope we don't have to send the pads in to get fixed.
Click to expand...
Click to collapse
Hmmm... I was gonna focus on getting fastboot to work, personally. I'll try some things with ADB and the wipe data option like untermensch suggested, too. Maybe there's some kind of exploit we can use to get to the point that we can use untermensch's exploit. I'm gonna compile a new kernel in the morning with USB debugging enabled and see if I can get anything useful from the logs.
Be aware, though, that if anything good comes about, it will be Linux-centric since that's my preferred OS, and I don't really know anything about Windows, especially the changes since XP.
Edit: I see you have the "Android" option. If you select that, what happens? Does the OS boot? Can you access ADB?
EndlessDissent said:
Hmmm... I was gonna focus on getting fastboot to work, personally. I'll try some things with ADB and the wipe data option like untermensch suggested, too. Maybe there's some kind of exploit we can use to get to the point that we can use untermensch's exploit. I'm gonna compile a new kernel in the morning with USB debugging enabled and see if I can get anything useful from the logs.
Be aware, though, that if anything good comes about, it will be Linux-centric since that's my preferred OS, and I don't really know anything about Windows, especially the changes since XP.
Edit: I see you have the "Android" option. If you select that, what happens? Does the OS boot? Can you access ADB?
Click to expand...
Click to collapse
The pad is stuck in boot... with the logo and the rotating circle.
newowner said:
The pad is stuck in boot... with the logo and the rotating circle.
Click to expand...
Click to collapse
Does ADB work for you? I would expect it to at that point in the boot process, but I'm no expert.
How do I get ADB to work with out being connected to the device? The device is not recognized by my computer.
EndlessDissent said:
Does ADB work for you? I would expect it to at that point in the boot process, but I'm no expert.
Click to expand...
Click to collapse
Sent from my DROID RAZR using Tapatalk 2
newowner said:
How do I get ADB to work with out being connected to the device? The device is not recognized by my computer.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
What do you mean it's not recognized by the computer? Did you install the drivers for the device? When the tablet is connected to the computer, does anything show up in Device Manager?
mikeseguin said:
i flashed cwm touch with fastboot but didn't read the tread properly, it was for stock JB, so now it's stuck on asus boot logo with "this device is unlocked" text up top and when i press power + vol down it's stuck on " starting bootloader kernel image" :crying:
Click to expand...
Click to collapse
Same thing here ...
with this message :
Device not seen by the PC ... no usb connection ...
adb devices show nothing ...
EndlessDissent said:
What do you mean it's not recognized by the computer? Did you install the drivers for the device? When the tablet is connected to the computer, does anything show up in Device Manager?
Click to expand...
Click to collapse
Pad is hooked up to computer, via usb, and device manager reads "error code 10 (device stopped)"
Computer has been rebooted, drivers have been reloaded/updated, computer rebooted again, and the pad drivers still don't properly install.
newowner said:
Pad is hooked up to computer, via usb, and device manager reads "error code 10 (device stopped)"
Computer has been rebooted, drivers have been reloaded/updated, computer rebooted again, and the pad drivers still don't properly install.
Click to expand...
Click to collapse
Well, if it shows up in Device Manager, the computer sees it, but I don't know exactly what that error means. I have no idea if it's a driver issue. What drivers have you tried? Did you use the Asus drivers? The universal drivers (I've seen some on XDA; look for "naked universal" drivers)? Others have used Motorola drivers when the Asus ones didn't work.
I really don't know why your tablet would boot all the way to the animation but without ADB access. That's why I think (and hope) it might be a driver issue.
dude, I fixed mine! I had to manually input the driver stuff into the setup.inf file in the drivers folder of sdk because it wasnt in there!! check your hardware id under device manager and then check it against the inf file.
Uh?
Hello all,
I picked up a used TF700T in good shape. Looks like some kid only used it to play Minecraft.
It pulled an OTA update to JB4.2.1, build .10
The goal is to put CROMBi-KK on there; I've read a bunch of the threads on the topic.
So first I tried to get the unlock tool on there...
-downloaded Unlock Tool V8 to PC, hooked up tablet via USB (USB debugging enabled, trusting unknown sources): no luck, getting the "USB device not recognized" error, PC keeps alternating the USB-connect&-disconnect sounds.
-Went ahead and downloaded Unlock Tool V8 straight to tablet. Getting "App not installed" error.
-Went and got Unlock Tool V7 instead, installed successfully - but now getting "network error" repeatedly...
-Read somewhere that signing in to Asus Tracker triggered unlock success for some, so I tried that: the Tracker website won't even take my serial number...
Obviously I am stuck early on - What do I do next?
What's the magic words to use with Asus support, can they even help me?
Asus support might be extra tricky because the previous owner may have registered the serial number...
Any obvious solution I am missing (I have used the forum search, but haven't found any new leads...)?
Do I just keep trying the Unlock tool V7 until the end of days?
bas2205 said:
Obviously I am stuck early on - What do I do next?
Click to expand...
Click to collapse
Had the same problem; it's a common bug with tf700t: some serial numbers (only of tf700t) aren't registered in factory's servers.
I pulled a ticket with ASUS support (here in Germany), explaned the problem, sent them the MAC adress and S/N of my tab and got 3 days later notice, that my tab could be unlocked - and it worked, they registered tab in their korean servers.
das chaos said:
Had the same problem; it's a common bug with tf700t: some serial numbers (only of tf700t) aren't registered in factory's servers.
I pulled a ticket with ASUS support (here in Germany), explaned the problem, sent them the MAC adress and S/N of my tab and got 3 days later notice, that my tab could be unlocked - and it worked, they registered tab in their korean servers.
Click to expand...
Click to collapse
Wow! That's the easiest resolution of that common problem I've ever heard of! Hope it goes just as well for him ^^
BTW, the servers are in Taiwan at HQ I believe
berndblb said:
Wow! That's the easiest resolution of that common problem I've ever heard of! Hope it goes just as well for him ^^
BTW, the servers are in Taiwan at HQ I believe
Click to expand...
Click to collapse
I thought, it was Taiwan, but was to lazy to look it up.
I did not invent this; it has been reported repeatedly in german boards.
Thanks again for the info guys!
I did as recommended, contacted support, telling them my serial number and MAC address. Got a response within ~36h saying they forwarded my request and the other department will take care of it in 10-15 days. So I am crossing my fingers for this to take care of the unlock issue.
I have been trying all sorts of stuff for the USB issue, no success so far. The person I got it from complained about the tablet not charging. Wondering if those two issues are related, I am suspecting a bad USB/charge port. Ordered a spare from ebay and will replace when it gets here next week. At this point (and not being the original owner), I am obviously not worried about warranty issues...
@das chaos : ich weiss allerdings nicht, ob der US-Support da genauso schnell geholfen haette; Gruesse aus TX.
bas2205 said:
@das chaos : ich weiss allerdings nicht, ob der US-Support da genauso schnell geholfen haette; Gruesse aus TX.
Click to expand...
Click to collapse
You're right as I usually am.
Hier muss wohl ein Nest sein!
I did get the spare USB ribbon&port on Saturday and replaced it. Unfortunately, that changed nothing;
I have also tried downgrading to V10.6.1.14.8 and even V10.4.4.25...
Same result, whenever I plug it into a PC (have tried different ones), it just says "USB device not recognized". When I select the "Unknown Device" under Devices&Printers, I don't even get the option of installing a different driver.
I have tried this with the Asus driver installed, then I tried with the 'naked' driver.
Tablet is in MTP mode; I have tried it with "USB debugging" disabled and enabled,nothing works.
Any ideas?
Tough, since you are not the original owner... The USB cable, I mean the external charging/data cable: Do you know if it is the original one?
May it be damaged as in : broken strands or some such?
bas2205 said:
I did get the spare USB ribbon&port on Saturday and replaced it. Unfortunately, that changed nothing;
...
nothing works.
Any ideas?
Click to expand...
Click to collapse
Same result in any of the 3 modes: apx, fastboot, normal?
.... if it's not charging either, you should be soon at an end with the tablet.
@berndblb: I had to buy a new (external) USB/charging cable and wall charger. I bought the ASUS original one straight from them through Amazon.
@das chaos: not sure what you mean - can I still get to APX or fastboot even if the tablet is not recognized upon plugging in?
How would I go about doing that, install first the tool/driver and hope that it assigns drivers properly when I plug in? @sbdags recommended I take a look at this thread (http://forum.xda-developers.com/showthread.php?t=2646279)...
In device manager, it does not show up with an exclamation point, but as an "unknown device"; The catch-22 with that is that Windows claims that the proper driver is installed and doesn't let me load a different driver. The connection is also a bit unstable, disconnecting&reconnecting after a few seconds (looks like an unstable USB stack...
bas2205 said:
@berndblb: I had to buy a new (external) USB/charging cable and wall charger. I bought the ASUS original one straight from them through Amazon.
@das chaos: not sure what you mean - can I still get to APX or fastboot even if the tablet is not recognized upon plugging in?
How would I go about doing that, install first the tool/driver and hope that it assigns drivers properly when I plug in? @sbdags recommended I take a look at this thread (http://forum.xda-developers.com/showthread.php?t=2646279)...
In device manager, it does not show up with an exclamation point, but as an "unknown device"; The catch-22 with that is that Windows claims that the proper driver is installed and doesn't let me load a different driver. The connection is also a bit unstable, disconnecting&reconnecting after a few seconds (looks like an unstable USB stack...
Click to expand...
Click to collapse
If it is shown up in Windows manager, then it is recognized! Only there are not the right drivers installed. For each mode (apx, fastboot, adb) you need a separate driver installed, wich normally are packed together in naked driver pack.
Windows doesn't install drivers of ASUS by it's own. You have to engage forced driver install routine; and there is a warning not to install those drivers. Do it nevertheless otherwise you won't be able to connect to transformers.
Thanks for the link. I was already aware of how to force a driver.
I took some screenshots to clarify where I am stuck.
First I get the USB not recognized error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Then when I inspect it, it says No Drivers are installed.
When I try to point it at the driver through forcing procedure, it ends with " The folder you specified does not contain a compatible software driver for your device", despite me picking the correct inf. Same result for Naked Driver 0.72, 0.73 and the package sdbags referenced...
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
bas2205 said:
Thanks for the link. I was already aware of how to force a driver.
I took some screenshots to clarify where I am stuck.
First I get the USB not recognized error
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Then when I inspect it, it says No Drivers are installed.
When I try to point it at the driver through forcing procedure, it ends with " The folder you specified does not contain a compatible software driver for your device", despite me picking the correct inf. Same result for Naked Driver 0.72, 0.73 and the package sdbags referenced...
Click to expand...
Click to collapse
What do you have under Portable device? Your driver should be there....
Did you only do the 'Search folder for driver' routine or did you also try the ' Let me pick from a list of device drivers' option and then point to the folder with the naked drivers?
.... on second sight:
You seem to have an x64 OS. Are you shure, you got the appropriate drivers for x64? There seem to be different ones on the internet.
http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875/
Scroll through the posts to find people with x64 machines having trouble with drivers.
bas2205 said:
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Click to expand...
Click to collapse
Look under Details (Hardware Ids) for the VID and PID to see if this is really your tablet. These are the ones that I know:
0b05:4c90 = TF700
0b05:4c91 = TF700 in USB Debugging mode
0b05:4c92 to 4c95: TF700 in some other modes
0b05:4daf = Fastboot mode
0955:7030 = APX mode
LetMeKnow said:
What do you have under Portable device? Your driver should be there....
Click to expand...
Click to collapse
Unfortunately, all unrelated:
berndblb said:
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
Click to expand...
Click to collapse
Thanks, I will get right to that homework... I hope it's a driver issue. If it is a hardware issue, since I have already ruled out the internal USB connector and I am dealing with a new USB&chargin cable, that would leave the MoBo...
berndblb said:
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
Click to expand...
Click to collapse
Just tried the Live-CD... no luck! Both "adb devices" and "fastboot devices" returned an empty list despite me following instructions from the other thread.
I guess my last option (after I unlock) would be to try and install TWRP through the app method?
Hi there,
I've try to move my 701L from stock rom to B111 rom, but i totally messed up ...
Right now, i'm only able to go into the bootloader, which is unlocked, but i'm unable to send any commands to it using fastboot.
I'm using adb/fastboot 4.2.2 under debian 8.2.
Here are some output :
[email protected]:~# dmesg
[...]
[ 1685.295589] usb 3-2: new high-speed USB device number 8 using xhci_hcd
[ 1685.459848] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[ 1685.459856] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1685.459860] usb 3-2: Product: Fastboot2.0
[ 1685.459863] usb 3-2: Manufacturer: Fastbo
[ 1685.459865] usb 3-2: SerialNumber: K3Q6R15818000014
[ 1685.460199] option 3-2:1.0: GSM modem (1-port) converter detected
[ 1685.460280] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB2
[email protected]:~# fastboot devices
K3Q6R15818000014 fastboot
[email protected]:~# fastboot flash recovery RECOVERY.img
< waiting for device >
USB Cable is still plugged, ofc.
Edit :
Ho, i'm also able to launch the Huawei eRecovery using vol+ and power during boot, but choise are only : Reboot - Download new version and recovery - Shutdown. I've try the second choise, but it's unable to find any files.
Do you have any ideas ?
Thx
rlksirocco said:
Hi there,
I've try to move my 701L from stock rom to B111 rom, but i totally messed up ...
Right now, i'm only able to go into the bootloader, which is unlocked, but i'm unable to send any commands to it using fastboot.
I'm using adb/fastboot 4.2.2 under debian 8.2.
Here are some output :
[email protected]:~# dmesg
[...]
[ 1685.295589] usb 3-2: new high-speed USB device number 8 using xhci_hcd
[ 1685.459848] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[ 1685.459856] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1685.459860] usb 3-2: Product: Fastboot2.0
[ 1685.459863] usb 3-2: Manufacturer: Fastbo
[ 1685.459865] usb 3-2: SerialNumber: K3Q6R15818000014
[ 1685.460199] option 3-2:1.0: GSM modem (1-port) converter detected
[ 1685.460280] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB2
[email protected]:~# fastboot devices
K3Q6R15818000014 fastboot
[email protected]:~# fastboot flash recovery RECOVERY.img
< waiting for device >
USB Cable is still plugged, ofc.
Edit :
Ho, i'm also able to launch the Huawei eRecovery using vol+ and power during boot, but choise are only : Reboot - Download new version and recovery - Shutdown. I've try the second choise, but it's unable to find any files.
Do you have any ideas ?
Thx
Click to expand...
Click to collapse
It's definitely a driver issue. Try doing it in Windows.
Hi ajsmsg78, thx for your answer. I'll try this as soon as possible.
Extra question : Do you know if this is a rom without gapps preinstalled ?
Regards
I've try fastboot using my work computer, which is also running debian 8.2 (i didn't check my kernel version)... now, how i can restore my gem-701l ...
rlksirocco said:
I've try fastboot using my work computer, which is also running debian 8.2 (i didn't check my kernel version)... now, how i can restore my gem-701l ...
Click to expand...
Click to collapse
I don't own a 701L. Maybe someone else who does can answer that question. You need to either find the stock rom for your 701L or try to upgrade to B111 again.
Ho thanks anyway, really appreciate.
My bootloader is still working, and i'm pretty sure I can restore my 701l.
Hm, strange behaviour ... i now have the same issue with a second PC. No more fastboot commands. Using a third PC is working fine ... very strange.
Edit : fastboot is OK using a liveCD.
stock rom for 701L B003 here
rlksirocco said:
Hm, strange behaviour ... i now have the same issue with a second PC. No more fastboot commands. Using a third PC is working fine ... very strange.
Edit : fastboot is OK using a liveCD.
Click to expand...
Click to collapse
I upload word document to Dropbox : How to flash rom X2 GEM-703L on GEM-702L, GEM-701L (ver.2)
https://www.dropbox.com/s/qmuu6vj05neee1h/Huawei X2 Eng.docx?dl=0&preview=Huawei+X2+Eng.docx
Hi Eennap and audioralf.
I'm now using B111. My main error was jumping from B006 to B111 without flashing the B009.
And regarding the fastboot issue, i assume it's because i was not using the root user.
Anyway, thanks a lot !
Hi guys,
this is the history of this topic:
https://forum.xda-developers.com/pixel-2/help/dead-pixel2-april-patch-t3774267
(if it is needed, I can delete it)
I connected my Pixel 2 my Ubuntu computer and I see this is dmesg:
Code:
[ 86.110107] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[ 86.254520] usb 3-1: New USB device found, idVendor=05c6, idProduct=9008
[ 86.254526] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 86.254530] usb 3-1: Product: QUSB__BULK
[ 86.254533] usb 3-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 86.255428] qcserial 3-1:1.0: Qualcomm USB modem converter detected
[ 86.255681] usb 3-1: Qualcomm USB modem converter now attached to ttyUSB0
I found some old topics here regarding to the same stuff for Nexus 5 devices and old HTC phones.
Anyone has an idea what should I do from here?
At least somehow could I save my data?
Thanks!
d4n3sz said:
Hi guys,
this is the history of this topic:
https://forum.xda-developers.com/pixel-2/help/dead-pixel2-april-patch-t3774267
(if it is needed, I can delete it)
I connected my Pixel 2 my Ubuntu computer and I see this is dmesg:
Code:
[ 86.110107] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[ 86.254520] usb 3-1: New USB device found, idVendor=05c6, idProduct=9008
[ 86.254526] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 86.254530] usb 3-1: Product: QUSB__BULK
[ 86.254533] usb 3-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 86.255428] qcserial 3-1:1.0: Qualcomm USB modem converter detected
[ 86.255681] usb 3-1: Qualcomm USB modem converter now attached to ttyUSB0
I found some old topics here regarding to the same stuff for Nexus 5 devices and old HTC phones.
Anyone has an idea what should I do from here?
At least somehow could I save my data?
Thanks!
Click to expand...
Click to collapse
I am in EXACTLY the same scenario as you, from what you have said in both your posts about this issue.
Have you found a solution yet?
My Pixel 2 is 1 month out of warranty.
I never dropped it or anything.
I was checking my email at work, and it froze and turned off (at >75% battery).
After that, it never turned on again.
Trying to start the Pixel2 with...
Holding Power for a solid minute = No response
Power+VolumeUp = No response
Power+VolumeDown = No response
When I connect to my PC via USB, the phones storage is not found.
It is not found when I use the "ADB Devices" command either.
The only sign of 'life' is in device manager, where it shows up under "Ports (COM & LPT)" as...
"Qualcomm HS-USB QDLoader 9008 (COM3)"
I purchased my phone with a Christmas gift card from a local store called "The Source" (I'm in Canada), so I do not have the benefit of a Credit Card extended warranty...
And because I am on month 13, I am outside of Googles 12 month warranty.
They forwarded me to their "UBreakIFix" and they looked at it and said...
"It could be a broken screen. We could replace it if you like. We'll run a diagnostics test over night to be sure"
So I went in the next day and they said
"It could be a broken screen, but we should try swapping the motherboard first. We can do that for you, for $480 and see about the screen after that"
to which I responded "No thanks!"
To which they responded "Alright. Would you like us to recycle the broken phone for you then? Saves you a trip!"
"NO THANKS, I'LL COME GET IT RIGHT NOW."
What a pathetic attempt at getting their hands on some free spare parts. Ugh.
https://forum.xda-developers.com/android/help/unbricking-qfil-sahara-fail-error-help-t3823986
Different phone same issue it's worth a look.
download skipsoft android toolkit and follow directions. have problems?. ask me. i will help.
bmw9651 said:
download skipsoft android toolkit and follow directions. have problems?. ask me. i will help.
Click to expand...
Click to collapse
Since it uses adb, the message is "Device not detected".
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
let me know how if need help.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
download > Tool all in one. update it. update the drivers button at the bottom. at the top right push button to find you phone. push button to flash factory image. it take you to page where you find you factory image for you phone press download link. go back to tool all in one and find the file then flash the file to you phone.
bmw9651 said:
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
let me know how if need help.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
download > Tool all in one. update it. update the drivers button at the bottom. at the top right push button to find you phone. push button to flash factory image. it take you to page where you find you factory image for you phone press download link. go back to tool all in one and find the file then flash the file to you phone.
Click to expand...
Click to collapse
This is worthless as the phone is bricked, as was stated clearly. If these people could use ADB or fastboot then this problem wouldnt exist.
Death I said:
This is worthless as the phone is bricked, as was stated clearly. If these people could use ADB or fastboot then this problem wouldnt exist.
Click to expand...
Click to collapse
I have never ever trusted those "all in one" tools. Learn to do it the right way; at least if you screw up, it's your own fault.
The tool works fine. it must be the person. I learned to use adb and fastboot first and then took that knowledge and used it in the 2 programs. tool all in one and skipsoft android toolkit. I bricked my phone many times just messing around with it and had it back working again in no time. some people can do this and others do not understand.
socal87 said:
I have never ever trusted those "all in one" tools. Learn to do it the right way; at least if you screw up, it's your own fault.
Click to expand...
Click to collapse
There is no right way, I didn't find a way to fix it. I had to buy a new phone.
Did you ever end up fixing this?
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Blank flash
jhomolac said:
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Click to expand...
Click to collapse
Most likely it's in Emergency download mode (EDL)
You will need a blankflash, several threads on this.
There's one here, that may work.
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
Sent from my Moto E (4) using Tapatalk
EDL mode even though there is no sign of life whatsoever?
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
Some phones will display a charge light some won't like he said it's in edl mode the PC sould display it and u should hear it make sound when u plugs the phone into PC on windows in not sure on Linux machine should b perty much the same on that aspect .One thing u might have to get different blank flashes for the different updates .If don't go the first time try again good luck
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
jhomolac said:
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ocean/ here is a blank flash that should get u going dose the PC recognise ur phone when u plug it in if dose open terminal an PC type fastboot devices if it sees it your in luck I can typ fastboot boot (the name of ur recovery) if it boot into twrp then u might b able to switch it to a slot. There is comands for fastboot to switch but I don't know them
My computer does not notify me when I plug in my phone. But I don't remember it doing that even when I used it before.thank you.
You might need to charge the phone. With a blank/black screen it can appear off when it's not. Thus draining the phone completely. It widely suggested to charge phones to at least 80% before tweaking/rooting.
I will feel like a real dummy if that's the case. It is now on the factory supplies charger. Haha. Crossing my fingers. Thank you
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
jhomolac said:
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
Click to expand...
Click to collapse
It's in edl mode, use the blankflash
Sent from my Moto E (4) using Tapatalk
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
jhomolac said:
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
Click to expand...
Click to collapse
You need QPST to interface with EDL mode. I don't know if anything in here works on Linux, but it definitely works on Windows 10.
QPST Utilities
decided to give this another try. i have managed to get a little further, however this is where i am getting stuck. i wish i was more savy with this stuff. any chance anyone could help me with this?
also, is it nessecary to have an sd card in the device when i do this?
blankflash_from_QCO30.85-18]# /home/joel/Desktop/blankflash_from_QCO30.85-18/blank-flash.sh
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.005] ...cpu.id = 186 (0xba)
[ 0.005] ...cpu.sn = 2335135194 (0x8b2f55da)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.018] Loading programmer
[ 0.019] ...filename = programmer.mbn
[ 0.019] Sending programmer
[ 0.318] Handling things over to programmer
[ 0.318] Identifying CPU version
[ 0.324] Waiting for firehose to get ready
[ 3.338] ...MSM8953 1.0
[ 3.338] Determining target secure state
[ 3.343] ...secure = yes
[ 3.387] Configuring device...
[ 3.394] Flashing GPT...
[ 3.394] Flashing partition with gpt.bin
[ 3.400] Initializing storage
[ 5.763] Target NAK!
[ 5.763] ...num_partition_sectors=61071360
[ 5.763] ...SECTOR_SIZE_IN_BYTES=512
[ 5.763] ...num_physical_partitions=3
[ 5.763] ...OEM_ID=74
[ 5.763] ...Product name=hB8aP>
[ 5.763] ...XML (0 bytes) not validated
[ 5.763] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 5.763] Check qboot_log.txt for more details
[ 5.763] Total time: 5.763s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
sd_shadow said:
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
uwucake2020 said:
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
Click to expand...
Click to collapse
Is there anything on the phone screen?
sd_shadow said:
Is there anything on the phone screen?
Click to expand...
Click to collapse
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
uwucake2020 said:
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
Click to expand...
Click to collapse
Spoiler: It may be hidden in Ports like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}