I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.
Related
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Thx Red_81, again. Glad to see u put this here for the i777. Appreciate u sharing this. It should provide some good help for many users. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium
So much easier than trying to explain how to install the sdk and then what commands to run. The only problem is you need to have working drivers.
Sent from my SGH-I777 using xda premium
Red_81 said:
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Click to expand...
Click to collapse
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
lambition said:
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
Click to expand...
Click to collapse
Never mind. I just got it working.
Had to just enter adb command directly. wait-for-device is not working for my phone for some reason.
If you get stuck there again, unplug and plug in the device again.
Sent from my SGH-I777 using xda premium
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Phalanx7621 said:
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Script already does that
Sent from my SGH-I777 using xda premium
Thanks
Thanks i was tinkering with a noria 7" tablet, which hasn't worked right since i got it but for 65 bucks its to be expected, but i used sdk manager to get it to register on my computer as an android adb device and for some reason i tried to turn the wifi on and it crashed and got stuck in a boot loop idk why. like i said hasn't worked right since i bought it. But i did use adb portable like you said to get into recovery mode and it worked great thanks! For other noria users when i figure out how to flash a rom to it i'll start a section here on xda as soon as i figure it out. Thanks again
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
BrockSamsonFW said:
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
Click to expand...
Click to collapse
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
creepyncrawly said:
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
Click to expand...
Click to collapse
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
BrockSamsonFW said:
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
Click to expand...
Click to collapse
It's pretty difficult to recover information from the data partition when the phone is in a state such as you describe. Maybe the developers and technogeeks can do it. I can't. However, depending on where the game saves it's game data, you may be fine. If the game data is saved to the USB memory (internal sd card) then it will still be there once you flash new firmware. Your pictures should also be fine, since they are on the sdcard.
Hello everyone,
I'm writing in the hopes of receiving some guidance re: a small "challenge" a friend issued to me. As you can probably guess, the half of the story that involves my friend's actions on the tablet are word-of-mouth, seeing as the device was given to me in a totally bricked state. Hope you'll be able to assist me somehow!
After using his Galaxy Tab P7500R for some time, the battery stopped charging. He supposedly tried a complete wipe and system restore (for which he was unable to guarantee a successful conclusion), and then the machine ran out of whatever juice had been left behind during the last successful charging cycle, and turned off completely, showing no signs of life whatsoever.
This is where I come in - I was given the "expensive ornament", accompanied by the words "have fun, I've already bought another one".
Symptoms are the following:
1) Powering the device on doesn't work. While the device is connected to the house power grid, there are no indicators of the device doing anything.
2) Connecting the device to a USB port on my laptop, and holding the power button, after 15 seconds my PC signals a device being disconnected via sound, and that disconnection sound is almost immediately followed by a couple, rapid, "halved" 'device connected' sounds. On the other hand, while the device is connected to a USB port on the laptop, if I hold the power button together with volume+, all I hear every 15 or so seconds is the "Device disconnected" sound.
3) After using USBDeview to remove a driver named APX, and after reconnecting the device to the computer via USB (sometimes this requires holding the power button, sometimes all it takes is a reconnection), I will hear a full "device connected" sound; then, an "installing driver" window will open, for the APX driver, which, after looking for the appropriate driver via Windows Update, will give me an error message ("no driver found") on the "unable to install device drivers" window.
4) Opening the device (out of warranty for over a year), and utilizing some testing tools have shown that power does reach as far as the motherboard, and that the batteries are somewhat charged at the moment.
Any ideas?
Thanks in advance for your help!
Lightside
[UPDATE 1]: I successfully installed the NVIDIA USB Boot-Recovery drivers for mobile devices. The tablet is now detected as being connected to my laptop, sounds and everything.
Following some instructions I was able to find on these forums, I tried installing NVFlash, and running the --bl bootloader.bin --go, receiving a "Rcm version 0X4 - Command send failed (usb write failed)" message.
From what I gathered, this is evidence of a locked bootloader. I wasn't able to find any posts dealing specifically with a bricked device that is only recognized in APX mode, and how to unlock the bootloader in such cases. Is there a guide available by any chance?
Update 2 :
I've extracted the battery, but I seem to be unable to remove the residual charge, as the device shows up (APX) as connected, as soon as I plug in my USB cable.
Anyone? :/
Up?
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.
I just got the phone today. i unlocked it with the ASUS-provided tool. No problems. I enabled developer mode and USB debugging, no problem. I can see the device when I connect it to my PC and type "ADB Devices". No problem there.
My problem is when I enter FASTBOOT mode (vol-up + power). If I connect the phone to my PC and type "fastboot devices" it comes up blank.
I tried multiple versions of ADB/Fastboot, and multiple cables and ports on multiple computers. The ROG phone just isn't recognized by fastboot (My old Pixel XL is recognized by Fastboot on the same PC).
Does anybody know why the ROG Phone isn't being picked up by fastboot when adb works fine on the same machine?
[UPDATE 1]: I also updated my USB driver and the device is in Device Manager as ASUS ADB Android Device when plugged in as USB debugging. When in Fastboot mode, the device does not show up in Device Manager at all.
It might not return anything but maybe it could execute commands. I think you want to flash TWRP am i correct?. If so try to run the commands and see if it executes them. I am also facing the same issue but i haven't unlocked my bootloader yet and i have no plans to do it yet.
Update: It seems my laptop doesn't detect my phone in fastboot mode also. If you go to the device manger window nothing changes when you connect your device to the computer/laptop. Could this has to do with me not unlocking the bootloader yet.
This is not the case with my Nexus 6p, when i am in the bootloader mode my laptop detects it fine and it shows a bootloader interface driver in the device manger window. which is obviously not the case for the ROG phone.
By the way when my Asus is on and connected it detects it by its name "ASUS_Z01QD" and not "ASUS ADB Android Device".
Thanks for the reply. Seems we're more or less in the same boat. I guess I'll hang tight until someone smarter than I am posts a step by step rooting guide. Till then, no Fastboot and no TWRP, it seems.
I was able to get fastboot to detect. I plugged the cable into the side USB slot, not the bottom.
When I plug it into the bottom, my device is not detected either.
I am using a USB-A to micro-USB cable with a micro-USB to USB-C adapter.
When I get home, I'll check if the USB-C cable that came with the device works with fastboot when plugged into the side slot.
I contacted ASUS support, and they said to use the USB-C port on the side of the phone. Don't I feel dumb. The only thing I didn't try.
This happens on my rog 3 too.. debug detects on my bottom side. But it only charges on my side port.. any help pls?
So i got it to work. It was my cable problem lol.. all good now and im back to my lovable Android 10!
OK so i was also stucked and nothing seems to be work i put the cable at the side port but same no detection i tried change cable nothing works...
simple is put cable on side and restart bootloader **** this is real works ... lol hit
gimme a like if it works for u too
I was having the same issue. Was thinking I was going to have to start troubleshooting with different cables and computers but just changing to the side port actually worked. Wouldn't have thought of that on my own. I made an account here just to say thank you to this multi year old thread lol.
okay so, i just got this phone. did all updates, enabled bootloader unlocking and made my mi account, downloaded the mi unlock tool and everything.
heres where the problem comes in.
everytime i try the button combination to get into fastboot, it works. but then when i connect my phone to my computer, the fastboot splash screen turns black with little text at the top saying "press any button to shutdown" or something like that. it just wont stay on the fastboot screen, its like its exiting fastboot mode on its own.
why does it do this, and what can i do to fix it?
note: i have downloaded all drivers and software to get this to work, and nothing seems to be coming to light.
please help me, i am very confused.
update: actually, it seems to be fine before i open the mi unlock tool. it seems that when mi unlock tool is not open, it stays in fastboot mode, but as soon as i open mi unlock tool, it just kicks me out of fastboot mode, and goes to a black screen with something at the top saying the exact same thing i mentioned earlier.
Turn on the phone go into developer settings and enable usb debugging, im pretty sure that's it
Deexterity said:
Turn on the phone go into developer settings and enable usb debugging, im pretty sure that's it
Click to expand...
Click to collapse
i already have enabled usb debugging. but for some reason, it won't just stay in fastboot mode.
was thinking about calling xiaomi and seeing what they have to say. because i cant find anything on this matter, so its probably just something im doing wrong. though it may be my version of windows. i have Windows 8.1. so maybe thats the deal?
this is stressful lol
If I'm not mistaken, you should only connect the phone in fastboot mode when the program asks, not before you open it
Deexterity said:
If I'm not mistaken, you should only connect the phone in fastboot mode when the program asks, not before you open it
Click to expand...
Click to collapse
i know, i did that too. but the problem still persists... ill try some other time.
thanks for helping though
First off this is much better place to ask questions. When phone is running and you connect to pc can you access storage?
If not check drivers, try different usb cable, and try different usb ports.
If yes then can you access the phone via adb?
If not it is a pc issue probably drivers.
If so leave phone booted and connected then open unlock software. Once software is up and running go to terminal/command prompt and type "adb reboot bootloader" without quotes.
I don't think it is windows version but with Microsoft anything is possible. I still use windows 7 for all this stuff.
Had the same problem on my Desktop with Ryzen, i tried it on my laptop with Intel Celeron and it worked from the first try without any drivers installed. If you have AMD that might be the cause
Hello.
My personal experience says:
1 Install Drivers on the PC/Laptop.
2 Activate DEVELOPER OPTIONS
3 Accept O E M Unlock
4 Allow usb debugging
5 Shut down Wi-Fi and use only DATA in order to connect - verify the device to the Mi account you have. When connected, press "understood" or ""accept"" (however it pops up).
6 Connect the phone to the PC/Laptop
7 After being connected, shut down the phone and put it in FASTBOOT. Make sure your PC ""reads"" your phone. Do it through command line/power shell, and make sure it shows up as alphanumeric in command line (i hope you know what to type - e.g fastboot devices)
8 Download and use the mi unlock tool (preferable Versions 2.....). Connect through this tool to your Mi account
9 Ask for permission to unlock // unlock your phone if days-hrs have passed. Ignore any pop-up message/warning and go on.
VERY IMPORTANT NOTES:
A. The phone must be recognized from the PC as ADB INTERFACE (in device manager) both in normal and Fastboot modes. Any other case is waste of time.......
B. Use a good cable and have the mobile charged!
C. In case you have another (older) device connected to your account, disconnect-delete it or else you will end up stuck with a ""cannot unlock message""
D. The process will not work if your PC runs some Win 10 versions as well as if built with RHYZEN PROCESSOR. Prefer PCs running win 7 or 8.
E. You must have DATA connection available or else you will not be able to connect-verify the phone to/through your Mi account !!! it is a new (dual function) fail - safe procedure from xiaomi!!!
F. Make sure you have the correct drivers installed to avoid a brick - bootloop etc
Hope it helps!
Gathered from my own experience!
To summarize: The xiaomi imposes too much rodeo and much time spent of the user to just "try" to unlock a simple bootloader, better to change of apparatus and to be happy with the practicality. lol