Gingerbread only. If you are on ICS this will not work. Don't try! Get the ICS only tool here: http://forum.xda-developers.com/showthread.php?t=1779810
This is based on the original Droid 4 Utility with edits. Contains the complete GB fastboot files to restore your phone, root, unroot, install voodoo rootkeeper, safestrap of BG, etc. Extract after downloading and doubleclick the script to run.
Download here: Droid4 GB Only.zip - 1.19 GB
MD5 checksum posted at the hosting site.
If you have trouble connecting be sure usb debugging is on and you have the latest moto drivers installed. Moto drivers here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/78460/p/30,6720,8302
For menu 1 or 2 your phone must be in fastboot mode first. Enter this by using the tool option or manually by powering off, then hold both volume buttons and pressing power for a few seconds, release the power button and select "ap fastboot".
And of course be sure you have a good usb cable and a full battery if restoring your GB system.
Use at your own risk.
My phone seems to have no Android OS. It also has a dead battery. Plugging in the charger only shows the Motorola Dual Core screen. It won't turn on when connected to the pc. I can still boot to the Boot Mode Selection Menu. I also have a factory cable coming in a couple of days. Will I be able to use this utility using this cable? I can still go into Fastboot connected to the computer with the cable?
badboi_zero said:
My phone seems to have no Android OS. It also has a dead battery. Plugging in the charger only shows the Motorola Dual Core screen. It won't turn on when connected to the pc. I can still boot to the Boot Mode Selection Menu. I also have a factory cable coming in a couple of days. Will I be able to use this utility using this cable? I can still go into Fastboot connected to the computer with the cable?
Click to expand...
Click to collapse
Yes, you can use this utility to reflash .219 to your phone through fastboot. Did the same thing to mine awhile ago and actually used it to reflash stock so I could upgrade to the .217 leak
Sent from my DROID4 using xda app-developers app
I'm having troubles rooting my .219 D4.
I installed the drivers, and according to the Moto device manager, I am up to date. USB Debugging is checked on.
When I try to root it using this tool (menu 3) and the phone is plugged in with charge only mode (using a stock Moto cable), this is what the command prompt spits out. It isn't instant, it's usually done over the course of 2 minutes:
{
"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"
}
It doesn't actually reboot on its own, and after rebooting manually, there is no SU app in my drawer.
I then tried to use menu 3 while in AP Fastboot mode, by using power and both volume buttons to get into the fastboot menu. I plug in my phone to the computer, and run the script and I get this:
It just hangs there for over 5 minutes and the phone doesn't do anything.
Here is the setup for my latter attempt:
Please help me figure this out. Could the drivers be corrupt? I've uninstalled and re installed the device manager from moto a couple of times. Could my anti-virus be blocking something? I think that the issue stems from a problem in the interface between the device and the computer.
Thanks in advance for any help
Hmm..it looks like the tool is possibly seeing more than one ADB server running. I'd the phone and let it up come up normal. Open up a task manager and go to the process tab. Are you seeing more than one ADB.exe process running? For some reason the tool thinks you have more than one device attached and as a result, isn't sure where to send the exploit.
This doesn't explain the troubles with Fastboot however.
When I plug in my phone and open up the tool, one adb.exe shows up in my task manager. Once I run the root script, I see a second one open. I tried killing it, and it will just open up again. How do I fix this?
If this is on the computer side, why wouldn't it explain the Fastboot problem?
SOLVED: Well, the problem wasn't really solved, but I transferred all the necessary tools to a different PC and rooted the device. So it was an issue with the original computer. MY theory is that it was an issue with the ADB interface from the Moto drivers. I'm purely spitballing on that though.
Thanks for the help anyways, guys. Time to have some modding fun!
Is there a mirror? I can't seem to download this...
Thanks for the utility!
I had some complications with the OTA update and realized that a fastboot back to stock was the only remedy. I couldn't find a linux solution (am I missing something?) so I modified the script to use moto-fastboot32. Worked great, thanks again!
Can some provide a mirror for this link? This isn't downloading...
can anyone throw up a mirror of this or a torrent? my download keeps timing out after an hour....
svrnmnd said:
can anyone throw up a mirror of this or a torrent? my download keeps timing out after an hour....
Click to expand...
Click to collapse
Just another request for a new mirror for this file. I would really like to unroot so I can update to ICS.
I don't think you have to unroot to update... If you've made a lot of changes to your system file, you'll probably have to undo them or fastboot back to stock (this includes installing safe strap)
Sent from my Galaxy Nexus using xda app-developers app
Try the ICS tool, it now has fastboot for ICS.
Related
Hi ,
The other day I decided to fxz'ed my phone back to stock. Somewhere during the flash i seemed to have gotten a flash failure, but my phone rebooted and seemed to be fine, stock. I thought nothing of it.
I was out and about today without my car charger and my phone died. When I got home I plugged my phone into my wall charger and instead of the normal battery on my screen the phone booted to this :
AP Fastboot Flash Mode (S) (Flash Failure)
0A.61
Battery Low
Cannot Program
Connect USB
Data Cable
I cant seem to get to any other mode.
Im hoping i didnt brick my phone. Any Help Would be greatly appreciated .
Do this and will reflash the system http://rootzwiki.com/index.php?/top...nd-43V3R-Root-For-The-Bionic-V2.1#entry127684
Sent from my DROID BIONIC using xda premium
Power the phone off. The try to boot into the bootloader (press and hold Vol up / vol Down, then press and hold power until it comes on).
Select Normal boot - if it boots normally this may be something that you have to live with. Every time you turn the phone off and power it back on, you'll need to do this. If you remember to do it then you can bypass directly to the bootloader menu and select boot normally, and not have to see that stupid flash failure message.
My phone does this too. So does cellzealot's. We both tried to do different things in testing and both ended up with the same symptom.
I tried to FXZ back to pure stock to see if I could do it. I was already on 5.7.893, so that in effect may have b0rked the flash, and it sounds like you might have done the same thing.
Try reflashing using a desktop and the back usb ports
Sent from my DROID BIONIC using XDA App
Solution Ever Found?
I have this very same problem. Was a solution ever found? Thanks.
Have also been running into the problem, but I've jerryrigged it to be able to charge the battery. Now I'm at the point where I can't find any method to fix my soft bricked bionic (ran into the problem rolling back to 5.5.893 from 5.7.893). Now I'm stuck on the AP Fastboot menu and can't get past loading the system.img whether that using the RSD Lite methor or the moto-fastboot method. One-click methods haven't worked either and I keep trying anything I can. Please help, I'm desperate right meow.
Is your battery charged? Are you trying to get on .902?
Go to link below. There find the fX files and download the one that will do a full phone format including webtop and bootloader. (Its marked complete)Then make sure all drivers are installed in windows and use RSD lite to flash. It will take over half an hour to flash. Had same problem and it fixed it. The key is the file you use to flash the phone. Needs to be the full file. Rom/Webtop/Bootloader
Here is the link. And be sure you download the complete one and not minimal. Do not uncompress the archive either. Use rsd lite and the file in its entirety. Let rsd do any uncompressing needed
http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
Sent from my DROID BIONIC using Tapatalk
dragon droid said:
Go to link below. There find the fX files and download the one that will do a full phone format including webtop and bootloader. (Its marked complete)Then make sure all drivers are installed in windows and use RSD lite to flash. It will take over half an hour to flash. Had same problem and it fixed it. The key is the file you use to flash the phone. Needs to be the full file. Rom/Webtop/Bootloader
Here is the link. And be sure you download the complete one and not minimal. Do not uncompress the archive either. Use rsd lite and the file in its entirety. Let rsd do any uncompressing needed
http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Pretty sure you don't have to go through all of this...
But whatever works, I guess.
Those are old files. You don't want to use those files anymore and depending on the current state of your phone they won't work anyway.
You need to use RSD Lite 5.5 and the new full .902 XML.zip and it will restore your phone.
The latest driver version is also now 5.5 but the 5.4 drivers should work fine for Bionic.
All of the old tools and methods are no longer current and using the new file either complete with RSD Lite or flashing specific partition images with fastboot, if you know what needs to be fixed, is the way to restore your phone.
All of these methods will require a sufficiently charged battery to succeed or a factory flash cable that bypasses the battery altogether, as well as a PC with at least 4gb of RAM in order to manage the large image files. The time is dependent on you PC specs.
I have the same problem too
{
"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"
}
delisawzrv said:
I have the same problem too
Click to expand...
Click to collapse
Re-read CellZealot's post. If you have any trouble using rsdlite or obtaining the files, hit me up and I will be happy to help.
If your battery is low or dead then you have several options, two of them "free" and several requiring a purchase.
First, find someone with a Bionic that will let you charge your battery in their phone.
Second, cut a charger cable or USB cable and hot wire the stripped ends to the battery terminals in the phone to charge it enough to recover the phone. This is dangerous and not recommended but it will work and can be managed on your own if you have a spare cable.
Third, buy an spare battery which will likely come with enough charge to get through a flash cycle.
Fourth, buy an external battery charger and use it to charge your battery completely and then restore your phone.
Fifth, buy a Motorola Factory flash cable or make one yourself if your are skilled with a micro soldering iron and motivated. This type of cable has a different pin out and has the +5v on pin 1 which bypasses the battery and powers the device directly even without a battery inserted at all.
This is a permanent solution and such a cable can be used to restore any Motorola device and many others that are configured in the same way.
There is only one place to get one publicly, and I should disclose that I am directly involved with that place. We sell these cables and had them produced for us to our specification just for this purpose.
http://shop.teamblackhat.info
I know this post is old, but I've recently rebuilt a Droid. Turns out they CAN charge.
Pull the battery, and hold down one of the keys while replacing battery and connecting to power.
The droid will show the power off charging battery icon then and it charges fine.
Check Youtube, there are several videos.
Imagine the thousands of Droid owners who unnecessarily purchased charging cords, ex
Please my Motorola Droid is stuck on the logo eye and when I try to flash it with the stock ROM, it says "failed" with the tool
Please I need help
DakidMelo said:
Please my Motorola Droid is stuck on the logo eye and when I try to flash it with the stock ROM, it says "failed" with the tool
Please I need help
Click to expand...
Click to collapse
Which tool?
Sent from my perry_f using XDA Labs
Hello, I managed to kill my phone trying to flash a new recovery. It didn't boot anymore and was stuck at the LG screen.
So I tried to flash the stock ROM using NVFlash. I did everything as the tutorial told me to (plug phone in with volume keys pressed, installed drivers correctly et cetera) but when I executed flash.bat, a CMD window openend and it says "NVflash started" for like 30 minutes without doing anything.
It looks 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"
}
Maybe some important information about my phone:
try to unplug and plugin again your cable usb and HH make sure using the original LG cable
I haven't received any original LG cable with my phone. I am using a normal USB to micro USB cable which worked fine. What difference does the cable make?
I tried unplugging and pluggin my phone back in 10 times now, didn't help. Getting a little nervous here.
I have absolutely no clue what I have done but it just worked... Haven't done anything different. I simply plugged the phone back in and started flash.bat, as 15 times before. This time it worked. Maybe I got extreme good luck or extreme bad luck. Either way, I am sorry I cannot provide help for anyone in the future who has the same problem except spam that goddamn flash.bat till it works.
theevilworm said:
I haven't received any original LG cable with my phone. I am using a normal USB to micro USB cable which worked fine. What difference does the cable make?
I tried unplugging and pluggin my phone back in 10 times now, didn't help. Getting a little nervous here.
Click to expand...
Click to collapse
for me, i tried a cheap micro usb cable, it doesn't recognize well. but when i try the original one it does recognize well, and it's good. and can get adb devices
theevilworm said:
I have absolutely no clue what I have done but it just worked... Haven't done anything different. I simply plugged the phone back in and started flash.bat, as 15 times before. This time it worked. Maybe I got extreme good luck or extreme bad luck. Either way, I am sorry I cannot provide help for anyone in the future who has the same problem except spam that goddamn flash.bat till it works.
Click to expand...
Click to collapse
Might be because only ONE NVFlash command can be issued per connection. If for example you run NVFlash --sync first, then you need to unplug and replug it in APX mode before you can run the actual NVFlash command. Caused me a lot of frustration the first time I tried it.
Thank you very much Trym, I was stuck at exact this point and I used NVFlash --sync everytime to check if my phone is really connected! Now it worked perfectly. Thanks!
theevilworm said:
I have absolutely no clue what I have done but it just worked... Haven't done anything different. I simply plugged the phone back in and started flash.bat, as 15 times before. This time it worked. Maybe I got extreme good luck or extreme bad luck. Either way, I am sorry I cannot provide help for anyone in the future who has the same problem except spam that goddamn flash.bat till it works.
Click to expand...
Click to collapse
(wired question) What version of windows do you run? 64-bit or 32-bit? I couldn´t open the NVflash.exe file with win7 64-bit to test it (NVflash --sync) after installing APX drivers. The command window just flash-opens and closes..
thanks
Palm90 said:
(wired question) What version of windows do you run? 64-bit or 32-bit? I couldn´t open the NVflash.exe file with win7 64-bit to test it (NVflash --sync) after installing APX drivers. The command window just flash-opens and closes..
thanks
Click to expand...
Click to collapse
Read the instructions once again. You must open windows cmd and navigate to directory where you have NVFlash.exe. Dont double clikc NVFlash, it will close immediately.
In windows type cmd, navigate with cd command to directory where you have NVflash.exe and type nvflash --sync.
It doesn't matter if you have 32 or 64 bit w7.
Yeah, or run the .bat file...
Sent from the new LG-P990
I have got my phone flashed with nvflash now. I have no idea what nvflash is for though, and no idea what to do further. My phone was in a boot-loop due to having cwm recovery for G2X when I have an O2X. What are the next steps to having a functional phone, preferably a custom ROM such as DjangoManouche or Temasek cm7 if not stock? I cannot find any tutorial when I'm searching, and everything in this place is buried in ICS stuff...
Hi,
So im trying to unlock the bootloader on the Xperia T, and I have checked if im allowed and it says YES, but when I try and connect the device in fastboot mode, I press volume up and then put cable in and then power the device on, the blue light stays on for 3 seconds or so and then the phone just boots up normally leaving the computer to say "Unknown Device". I have tried connecting using USB 2.0 and USB 3.0, while in USB 2.0 the device turns on with the blue led and stays there but fastboot does not bring up the device. Its like its not even connected!?
I am using Windows 8.1 and I have already disabled the driver signature!! I am also pretty sure I have installed the fastboot drivers correctly!
Do you think I should install a fresh copy of Windows 7 and try installing it using that?
Any Ideas!!
Thank You!! Reply ASAP!
hassy786 said:
Hi,
So im trying to unlock the bootloader on the Xperia T, and I have checked if im allowed and it says YES, but when I try and connect the device in fastboot mode, I press volume up and then put cable in and then power the device on, the blue light stays on for 3 seconds or so and then the phone just boots up normally leaving the computer to say "Unknown Device". I have tried connecting using USB 2.0 and USB 3.0, while in USB 2.0 the device turns on with the blue led and stays there but fastboot does not bring up the device. Its like its not even connected!?
I am using Windows 8.1 and I have already disabled the driver signature!! I am also pretty sure I have installed the fastboot drivers correctly!
Do you think I should install a fresh copy of Windows 7 and try installing it using that?
Any Ideas!!
Thank You!! Reply ASAP!
Click to expand...
Click to collapse
What's the point of making a thread about Xperia t in neo forums??
Anyhow Windows 8.1 has driver problems... Best would be to try on 7...
Sent from my Xperia Neo V using Tapatalk 2
Deleted
Some xperia phone have problem staying on fastboot mode if haven't have driver install already on the computer, so to install fastboot driver is you pinpoint to the driver installation in device manager as soon as you plug in your usb, sure the phone will boot normally, but you don't close the driver installation first, you go to select driver manually and select your driver folder then click to it, but stop at the last stage where installation will begin, then shut off phone and plug in usb with volume up and immediately install the driver you select just now.if everything went well you should be able to install the driver...
In W8.1, microsoft change the usb policies, so there is no possible way to connect phone in fastboot mode using windows usb driver, thats normally refer to USB 2.0, but if your USB 3.0 are using chips from Intel, NEC, AMD,etc, and are running driver provided by vendor instead of microsoft then it is possible to run fastboot mode with USB 3.0 port.
hope that help
Thanks!
davidtkf88 said:
Some xperia phone have problem staying on fastboot mode if haven't have driver install already on the computer, so to install fastboot driver is you pinpoint to the driver installation in device manager as soon as you plug in your usb, sure the phone will boot normally, but you don't close the driver installation first, you go to select driver manually and select your driver folder then click to it, but stop at the last stage where installation will begin, then shut off phone and plug in usb with volume up and immediately install the driver you select just now.if everything went well you should be able to install the driver...
In W8.1, microsoft change the usb policies, so there is no possible way to connect phone in fastboot mode using windows usb driver, thats normally refer to USB 2.0, but if your USB 3.0 are using chips from Intel, NEC, AMD,etc, and are running driver provided by vendor instead of microsoft then it is possible to run fastboot mode with USB 3.0 port.
hope that help
Click to expand...
Click to collapse
Now I realised its because im using windows 8.1, Thank You! Better start installing windows 7 now
hassy786 said:
Now I realised its because im using windows 8.1, Thank You! Better start installing windows 7 now
Click to expand...
Click to collapse
gregbradley said:
This is the Xperia T forum
{
"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"
}
Click to expand...
Click to collapse
It was in the neo forums until I reported and got it to move here... Better keep the facepalm with yourself...
Sent from my Xperia Neo V using Tapatalk 2
Fair enough....
Sent from my C6903 using XDA Premium 4 mobile app
the phone was working perfectly a while back, havent used it since i got a new phone, but i tried transferring songs and i get USB device not recognized.
i have tried installing htc sync, htc drivers, but the problem still persists
USB DEVICE NOT RECOGNIZED
i have uninstalled the driver in DEVICE MANAGER, but still no fix
i cant run a RUU or copy other roms, because USB wont mount
i flashed another nandroid on my device, but the problem still persiists
any ideas? everything works except USB MOUNTING
usb mounting = dead? tried everything, from pdanet, to uninstalling, to switching nandroids, nothing fixes it
For_itembine said:
usb mounting = dead? tried everything, from pdanet, to uninstalling, to switching nandroids, nothing fixes it
Click to expand...
Click to collapse
Is your phone seen in Device Manager? 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"
}
plugged it in, driver installed
so weird, hours upon hours, a few days trying to fix, and wam, driver installed
wtf
thanks for your help anyways
For_itembine said:
plugged it in, driver installed
so weird, hours upon hours, a few days trying to fix, and wam, driver installed
wtf
thanks for your help anyways
Click to expand...
Click to collapse
make sure the port is not dirty on your phone with debris !!
I also have the same problem, tries everithing (windows 7) different cables, but I can't flash other recovery as I booted in bootloader/ fastboot it says "fasboot AC"
nkk71 said:
make sure the port is not dirty on your phone with debris !!
Click to expand...
Click to collapse
now its back to usb not recognized, the usb must be stuffed i guess, all my phones work no problem
dammit, i thought running a RUU might help, but i cant get it connected
i mean the phone works, just doesnt want to mount usb storage
Solution fixed
FIXED IT, as i said the usb randomly would work sometimes for a brief period and stop again, in the brief period (dat short time span) i managed to get into fastboot (normally it would say AC) but it said USB, amazing luck, i managed to flash HTC STOCK RECOVERY
than i downloaded the 4.3 update within the phone, updated my phone, and now it WORKS
something must have been corrupted in my system
For_itembine said:
FIXED IT, as i said the usb randomly would work sometimes for a brief period and stop again, in the brief period (dat short time span) i managed to get into fastboot (normally it would say AC) but it said USB, amazing luck, i managed to flash HTC STOCK RECOVERY
than i downloaded the 4.3 update within the phone, updated my phone, and now it WORKS
something must have been corrupted in my system
Click to expand...
Click to collapse
Lucky b****d !
I can't do that, but trough airdroid (wifi) I can manage to copy things on my phone. The problem is that if this method doesn't work for me I will be unable to get it back as it is now, and besides USB everything works perfectly
I think the recovery can be flashed trough terminal emulator without PC, but then how to install the rom?
edit: solved
http://forum.xda-developers.com/showthread.php?p=50379619
different usb cables
Mine is not even recognized in the device Manager. i tried using different usb cables, clean the ports, nothing happens. I also tried updating the OS to Lollipop but still USB is not recognized by the computer. Any other options?
I have the same issue. I don't know what it is or why but God it is frustrating.
usb not recognized
Turn off the phone and thoroughly clean the port on it. I've seen it happen quite a lot, fluff just gets compacted and stuck and breaks contact with enough pins to cause this.
this works for me on samsung tab A
https://forum.xda-developers.com/ga...rging-recognize-android-t3787571#post76460493
Hello everyone my mi a2 not reading pc in device manager too can any help me with this maybe need drivers or more? Thx
robin_vilensky_ said:
Hello everyone my mi a2 not reading pc in device manager too can any help me with this maybe need drivers or more? Thx
Click to expand...
Click to collapse
Just to exclude the easy possibilities:
From your phone's status bar drop-down menu, does it say "charging via usb"? If so, you need to change that to "media transfer" (or something alike).
As for fastboot, this wouldn't actually be nessecary though. Here just make sure you open cmd as an administrator (on Windows, which I assume you're using, since you mention a device manager - on linux you would need to be root).
And, did you activate usb debugging in the developer settings already?
Maybe also do a windows update with your device connected, if still no go.
I have the same problem. I've tried everything without result.
You guys need to give more detailed information, if you want more detailed help..
What ROM are you on?
List everything that is not working.
List your installation procedure.
When did the problem occur for the first time?
What exact steps did you already try?
Which software versions are you using?
For instance using an older fastboot version may result in many problems, but one can only blindly guess with that little concrete info.
If I had such general issues somewhat relating to storage though, I personally would wipe my entire phone in both slots and format data (if you can somehow enter recovery without fastboot ofc, like from a terminal emulator app or via an extended reboot menu present in many custom ROMs).
Oh, and is adb working?
I have Android 9, November.
When I insert the cable into my computer, it starts charging, and an unrecognized usb error appears. There is no mobile option to choose what to do, not even in developer options.
I tried several drivers, not even the MI PC Suit knows cel, is waiting to connect, fastboot also without recognizing. I tried the drivers that have the bootloader unlock topic, unsuccessfully too.
The phone charges normal, and the C to 3jack USB adapter works. I've tried other cables, other computers, and even linux.
I bought the used cell phone, the old owner never plugged it into the computer, so I didn't even know about this mistake.
I've tried system hardreset, unsuccessfully too. I have no recovery installed, and fastboot works.
I see the error in the images, already tried several drivers. There were people who changed the door... sometimes it doesn't even appear, nothing just happens.
{
"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"
}
Badotti said:
I have Android 9, November.
When I insert the cable into my computer, it starts charging, and an unrecognized usb error appears. There is no mobile option to choose what to do, not even in developer options.
I tried several drivers, not even the MI PC Suit knows cel, is waiting to connect, fastboot also without recognizing. I tried the drivers that have the bootloader unlock topic, unsuccessfully too.
The phone charges normal, and the C to 3jack USB adapter works. I've tried other cables, other computers, and even linux.
I bought the used cell phone, the old owner never plugged it into the computer, so I didn't even know about this mistake.
I've tried system hardreset, unsuccessfully too. I have no recovery installed, and fastboot works.
I see the error in the images, already tried several drivers. There were people who changed the door... sometimes it doesn't even appear, nothing just happens.
Click to expand...
Click to collapse
If you are able to use linux - have you made absolutely sure that fastboot was up to date and did you use it as super user (That is after doing "sudo su")?
Phil_Smith said:
If you are able to use linux - have you made absolutely sure that fastboot was up to date and did you use it as super user (That is after doing "sudo su")?
Click to expand...
Click to collapse
fastboot does not detect the phone, neither on windows nor linux .. not even mi suite does, there are several people with the same problem in mi A2 lite and mi A2 too ... it seems like it was after the October update.
Hello! I have a similar problem. did you find a solution?