Hello,
I had LOS 17.1 on my tablet (Lenovo X704F). It worked fine apart from microsd reader). I tried to flash stock FW from XDA - https://forum.xda-developers.com/th...-verison-lenovo-tab4-10-t3921073/post79328701 but it keeps reboot all the the time. I cannot finish the basic configuration process. I found another version of stock FW, but to flash it I need to boot it in EDL mode:
https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/
So not having service cable, also cannot take it apart adb was my way last time. But now cannot enter usb debugging, so adb does not see my tablet connected to the PC.
Do you have any clues what else I could do?
It's a bit worrying how few responses to issues there are on here. Did you get anything resolved?
Related
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
I never thought I'd have to go as far as create a thread pleading for help, but after a lot of Google searching I still cannot find someone with the same problem.
I will explain:
I am trying to use fastboot, which I (don't think) I've any problems with in the past.
I can issue commands in normal use via adb from my PC fine.
I can adb reboot bootloader ok, and can get into the bootloader any other way just fine.
I can use the volume keys to navigate the options in the bootloader just fine.
The problem comes with I connect the USB to my PC whilst in fastboot.
Windows fails to recognise the device, and says it may have malfunctioned.
It won't allow me to reinstall the drivers successfully it seems, and seems to have a problem with the USB Host Controller too.
Fastboot immediately freezes, and I'm unable to even navigate using the volume keys, let alone issue commands from my PC.
My question then is twofold:
1. Is there likely to be a problem with the USB port on my device, or some sort of bootloader corruption?
2. Is it possible to return to stock Android without using fastboot?
Finally, I would like to stress that I've seen plenty of similar looking threads, but it seemed that the posters of those threads merely had problems getting in to the bootloader or recovery.
I haven't got that problem, the problem only arises when a USB is connected to the PC, the tablet becomes unresponsive only in bootloader mode.
If anyone has any advice to offer at all, I'd greatly appreciate it.
Additionally, if the problem is solved, I will post a detailed set of instructions in case anybody else should encounter a similar problem in the future.
__________________________________________________________
Update for anyone who happens to read this in the future:
[This guide](http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html) has a useful FAQ at the bottom which helped a little.
I think I managed to determine the problem was likely a duff usb connection, either on my Nexus or on my computer.
I was able to just about hobble through by keeping the cable in the same place.
In case it wasn't just this, this is what I did:
1. Flashed TWRP recovery from their app.
Went into bootloader and failed to do anything
2. Flashed CWM recovery.
Managed to be recognised in fastboot.
I still had problems with my Nexus 'malfunctioning' -- possible the USB.
I updated the drivers using the ones from [this thread](http://forum.xda-developers.com/showthread.php?t=2588979).
3. Flashed a new bootloader image immediately (there were rumours that a dodgy version had been released accidentally). [This](http://www.androidfilehost.com/?fid=23060877489996594) is the one I used.
Then I managed to get the stock ROM flashed, and the bootloader locked up again.
Fastboot freezes whenever USB plugged in
I'm having a problem with this step...
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options.
however, whenever the usb is NOT plugged in (and rebooted bootloader) the button work just fine.
I don't have a recovery currently installed.
The issue is not with drivers on the computer,
happens while usb plugged in both windows and linux or simply just plugged into a wall outlet to charge and with different USB cables.
I need to load fastboot but i'm having this issue. Is the device bricked without hope?
any help would be appreciated.
Nexus 7 2012 Model (grouper)
Boatloader version 3.34
Asus ZMPM1 3/32 model. I was on Havoc Pie official with TWRP 3.2.3. I flashed 327 stock rom using TWRP, now I've lost the TWRP. So when I go to flash TWRP using ADB ,I type the command and the process pauses and the phone shows the message "Press any key to shut down". Please help.
i had the same issue not sure why but it did not work when i connected it to a usb 3.0 port but worked with a usb 2.0 port try that
same problem
Deeptesh Basak said:
Asus ZMPM1 3/32 model. I was on Havoc Pie official with TWRP 3.2.3. I flashed 327 stock rom using TWRP, now I've lost the TWRP. So when I go to flash TWRP using ADB ,I type the command and the process pauses and the phone shows the message "Press any key to shut down". Please help.
Click to expand...
Click to collapse
facing the excat issue. Note: Tried all USB ports in my laptop.
Solved
Deeptesh Basak said:
Asus ZMPM1 3/32 model. I was on Havoc Pie official with TWRP 3.2.3. I flashed 327 stock rom using TWRP, now I've lost the TWRP. So when I go to flash TWRP using ADB ,I type the command and the process pauses and the phone shows the message "Press any key to shut down". Please help.
Click to expand...
Click to collapse
faced the issue untill I realized it was an issue regarding USB 3.0. The phone cannot support such a higher data speed. Use a USB 2.0 hub between your PC and your phone. That solved my problem.
For some reason connecting the phone to a usb 2.0 port in my laptop also did not solve the problem.
Btw, issue came up for me after recent update to pie
Try usb hub
Deeptesh Basak said:
Asus ZMPM1 3/32 model. I was on Havoc Pie official with TWRP 3.2.3. I flashed 327 stock rom using TWRP, now I've lost the TWRP. So when I go to flash TWRP using ADB ,I type the command and the process pauses and the phone shows the message "Press any key to shut down". Please help.
Click to expand...
Click to collapse
UP iam facing that too
I am facing this too , After recent pie update my Camera2api got disabled when trying to enable it I got this issue and still i couldn't enable it
tried another pc and it says okay but still it is in legacy
I have been trying to flash twrp since January. Still no luck. Can anyone help? I have been following the exact steps mentioned in the respective threads for every twrp version i tried. USB 2.0, changing data cables, unlocking using officia unlock tool because unofficially unlock process didn't worked when i tried. It got stuck. All it shows is "press any key to shutdown ".
This is my 3rd android phone which I'm using right now. Always used custom roms. And now its frustrating that I'm stuck at the starting line of it all... Please help me
starlord143 said:
I have been trying to flash twrp since January. Still no luck. Can anyone help? I have been following the exact steps mentioned in the respective threads for every twrp version i tried. USB 2.0, changing data cables, unlocking using officia unlock tool because unofficially unlock process didn't worked when i tried. It got stuck. All it shows is "press any key to shutdown ".
This is my 3rd android phone which I'm using right now. Always used custom roms. And now its frustrating that I'm stuck at the starting line of it all... Please help me
Click to expand...
Click to collapse
You have already tried USB HUB? I switched to USB 2.0 port, but don't work. For me, the USB HUB connection, a particular USB 1.1, works.
renda-l said:
You have already tried USB HUB? I switched to USB 2.0 port, but don't work. For me, the USB HUB connection, a particular USB 1.1, works.
Click to expand...
Click to collapse
I Don't have a usb hub and my patience is also running out. Thanks though
Worked well
Broh. For last two days i also facing the same issue. Today I made it.
Without closing 'command' box in pc, and removing usb,,... keep restart to fastboot mode.
Or
Restart pc without unplugging usb(mobile should be on fast boot mode) direct open flashall_aft.bat/ flashall_bat.cmd....
It it bcoz...fastboot commands are not supported on AMD processors..
U have to use usb 2.0 external hubs as it wont work on built-in usb 2.0 ports also...
Or switch to some intel machine
Restart in FB mode.
Connect phone to pc with 2.0 port.
Type this cmd:
fastboot boot twrp.img
(The file should be in ADB folder itself. Here twrp.img can be replaced with the file name which u have but should be a recovery of your phone only)
This cmd will temporarily boot your device in Twrp; if not try to hard pess those keys to boot to recovery.
From Twrp flash again Twrp.img to flash Twrp permanently. Now again reboot to recovery to test it.
I hope this will help
Asus Zenfone Max pro m2
Guys,
I have a problem that my phone (Asus zenfone max pro m2)was bootloader unlocked but was running Asus Official ROM, recently phone got turned off itself while using and not starting past boot.
When i try to flash on fast boot mode i dont see any devices connected, can someone suggest me further? it ll be really helpful to get my phone back
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
C:\adb>
==============================
Trying fastboot - press any key to shutdown
usb hub worked for me too
@nabinshajm I also tried using both the USB but didn't work. Do you got the solution ?
I recently received an OTA for my Ticwatch E which fails every time it tries to install. So, I captured the OTA url from logcat and downloaded the file to my PC so I could sideload it. However, I quickly discovered that my PC doesn't recognize the device when it's in recovery mode. ADB works fine when the device is on, and will reboot it to recovery, and it recognizes it in fastboot mode as well. Usually, I would find the unrecognized device in Device Manager and configure it to use the Android ADB drivers, however the watch is not found in device manager AT ALL when it's in recovery mode. I've tried the usual steps of switching USB ports and unplugging the watch until it's booted into recovery, those don't work. Furthermore, the watch doesn't have an SD card, so sideloading from the device is not possible. Any suggestions to get the device to be recognized by Windows in recovery mode?
Did you ever find a fix?, I'm in the exact same boat right now.
ClemmerC said:
Did you ever find a fix?, I'm in the exact same boat right now.
Click to expand...
Click to collapse
Yes, it was defective and I RMA'd it. The new one was good to go.
Hi,
I have unlocked Xiaomi Mix 3 5g. Phone never been rooted and I've never tried to apply custom ROM. SInce I've got it I'm on original software: at the moment MIUI Global 12.0.3. I've only had TWRP recovery applied but this wiped out ant went back to original recovery after my phone updated itself last time to 12.0.3.
Basically I've had phone ready to apply custom ROM but never done it accualy. I was always on original MIUI and TWRP recovery was applied to my phone.
A the moment after I connect phone to PC using cable, smartphone discovers PC connection but on PC I cannot see internal memory of my phone. And yes I have all needed drivers installed and I've tried using 3 different cables...
I think that may happened after my phone updated itself last time and went back to original recovery...
The worst problem is that now I cannot flash back to TWRP. When phone is connected to PC and I go to CMD, typing ''adb boot fastboot'' command is working and phone reboots itself to FASTBOOT MODE but once I'm in fastboot mode commands are not working and on flash attempt I only see < waiting for any device >
Any solution for this ?
Try using usb 2.0 ports or different computers.
I sometimes get mine to flash by inputting the command first then plugging the phone in afterwards.