I have searched around for a couple days, but there doesn't seem to be anyone who has posted about this issue with a Droid 4. So here is what I have.
I rooted my Droid 4 using the RazrBlade method without incident. Afterwards I wanted to flash Cyanogenmod onto it, but did not have a custom recovery like ClockworkMod or TWRP set up yet. So, looking around led me to download the latest safestrap .apk so I would have a recovery capable of flashing Cyanogenmod. The latest version of safestrap would not work for me because of a parsing error, I looked around and found that some people were having the same issue and fixed it by downloading an earlier version of safestrap to their Droid 4. So, I found a safestrap 2.x.x version, downloaded that and followed the directions accordingly. I now had a functional (to my knowledge) recovery that would allow me to flash CyanogenMod. So I downloaded the .zip file from the CyanogenMod website for Droid 4, and attempted to flash it using the recovery that safestrap 2.x.x set up.
Everything looked okay for the install, no errors were reported, phone was at least at 80% battery, but once the phone rebooted, after the Motorola spash screen, there was a blank screen. The phone is on, evidenced by the backlight being visibly seen, but otherwise there is no evidence that it is trying to boot up any ROM. There is no loop whatsoever, just a blank screen.
First, I thought it was a bad install, afterall, it wouldn't be the first time. But when I turned it off (only possible via PWR&Vol.- button combo) it did not give the option to go into the safestrap recovery mode upon booting back up.
But I am not without a working knowledge of how to pull a phone out of a softbrick state, so I quickly connected my phone to a computer set up to take adb commands and tried to reboot my phone into the recovery mode. I connected my phone to my PC, left it on the blank screen mode and typed the adb command [adb devices] to confirm that it was acknowledged by my computer, it was, and attempted to reboot it into the recovery mode with the command [fastboot reboot-recovery]. It responded by rebooting, but led back to the backlit blank screen. I thought that this might be an issue with the wires or drivers or something to that effect, so I reattempted with a usb cord that was supplied by Motorola, and reinstalled all the appropriate drivers. Nothing worked, so I moved everything to a new computer freshly set up to take adb commands. I connected my phone and it was immediately recognized by the new computer, but it still would not respond to any adb commands. Attempting to reboot into recovery yields a blank screen still.
By this point I do not care if my phone is rooted or if I have to restore it to factory settings. So I look up solutions that flash it back to the stock 4.1.2 ROM. I find one that does this, but it requires that I am in AP Fastboot Flash Mode. I put it in the aforementioned mode, but it is not recognized by the adb terminal. It is listed as an adb device if it is in "blank screen mode" but not while in AP Fastboot Flash Mode. Shortly after this the battery is too low to program anyway, so I turn it off and set it to charge. But instead of a "battery charging" screen, I am greeted with the Motorola splash screen for as long as the phone is connected to the charger. Every time the phone is removed from the charger it, immediately and without pause, loses power and cannot be powered on until placed back on a charger.
Looking around some more, because I am increasingly desperate to solve this problem, I find something called RSD Lite, which will reflash the stock firmware to the phone and it will behave as if it was reset to factory settings. I plug the phone up to the computer, it powers on, I boot it up to the AP Fastboot Flash Mode and RSD Lite sees the phone as a fastboot device, and is ready and willing to fix it, but the battery is too low to program.
The battery is incapable of being charged by a wall outlet by any means that I have tried (will list below), BUT... If I connect my phone to a computer, and after the phone is connected, turn the phone off, a little green LED light appears at the top left and stays for at least 15 minutes until the Motorola splash logo appears and my phone connects to the computer. The phone recieves power in this mode evidenced by the fact that it does not instantly power down after it is disconnected from the power source. But at this point in time, the battery does not charge enough to cause a change in the AP Fastboot Flash Mode to allow it to be OK to Program.
Here is some misc info that might be needed:
Modes that I have access to
1.) Motorola Splash Screen + "Blank Screen Mode": This mode connects to the computer and is registered by the device number XT894. After the Moto Splash Screen there is a backlit blank screen I call "Blank Screen Mode". This mode is recognized by adb commands but not by RSD Lite. Any time an adb command is used apart from rebooting, command prompt says <waiting for device> and the device does not respond.
2.) Motorola Splash Screen Only: This mode is only accessible by connecting the phone to a wall outlet. This mode does not charge the phone and if the phone does not have any power otherwise, will power down without warning upon being disconnected from the power source.
3.) Boot Mode Selection Menu: This mode provides various options that appear to do nothing. The "Recovery" option that is supposed to bring me to the default android recovery mode instead brings me to the Motorola Boot Logo and then to a green android laying down with a red triangle over it (with an exclamation point). I am able to access AP Fastboot Flash Mode from here.
4.) AP Fastboot Flash Mode: In this mode, the device is recognized by the computer as an adb fastboot device (not as an XT894 device). It does not respond to adb commands, and the adb terminal does not acknowledge the phone in this mode. RSD Lite does acknowledge the phone in this mode, but trying to begin the process to reflash the stock firmware causes the "Low Battery/ No Program" text on the phone to flicker and result in a failure in the RSD Lite program. It lists the reason as: Phone return(ed) Fail.
5.) Computer Charging Mode: When connected to a computer, and immidiately powered off, a green LED light turns on. After leaving the phone for some time, the phone can be disconnected and stands on it's own power without needing to be connected to a power source to remain on. In this mode, the screen is not on, and the phone is not recognized by the computer at all.
Methods I Have Attempted to Use to Charge Phone
1.) Plugging Moto Stock USB charging cable to computer and leaving it: This causes the 1st mode listed above to occur, and no charge is held. After 10 minutes of "charging" upon disconnecting cable, phone shuts off abruptly, and without any warning.
2.) Plugging Moto Stock USB into USB to Wall Outlet Plug: This causes 2nd Mode listed with similar results to above.
3.) Plugging Motorola Wall Outlet Charging Cable to Phone: See above
4.) ALL Above Methods + Boot Mode Selection Menu BD Tools Mode: I read that if you were to connect your phone to a wall outlet after booting it up into the Boot Mode Selection Menu, and selecting BD Tools, the phone would boot up to the Motorola Boot Logo screen, then show a battery charging similarly to how one does if you charge your phone after it shuts down from having 0% Battery. This was not the result I received. Similar results to #1
I apologize if there is some blatant simple answer here, but I have looked everywhere to find a solution to no avail. I included everything that occured between then and now so as to facilitate this process, and hope that I am not stepping on any toes with the wall of text I just posted.
Thanks in advance, if more info is needed (or if the post needs to be formatted in an easier to read way) just say so.
Sounds like you will need a motorola factory cable. I think that's what they are called. It provides power directly to the phone allowing you to fastboot. I know you can find them on ebay. I believe team black hat also sells an adapter to turn your regular OEM cable into a factory cable.
Your other alternative would be to sacrafice a usb cable and attach to the battery terminals directly to charge the battery. If you google it you should be able to find directions for how to do this. I believe someone posted a how to on youtube for the razr which should give you a good idea of what you would be getting into.
Good luck!
Droid 4 - Avatar
Fixed It
Thanks for the help.
I didn't feel like paying $12 dollars and waiting several days to purchase one of those special factory cables, so I ended up taking a non-USB charger, spicing it, and hooking it directly to the battery terminals like you said. After I did that, it automatically said that it was "OK to Program".
The only problem I had was that RSD Lite wasn't able to fix it, I had to download some other app that ran things through command prompt while the device was in AP Fastboot mode. But the end result was the same.
I found out that the problem that caused all this was me not flashing the CyanogenMod firmware into ROM Slot-1 while in the safestrap recovery mode. I flashed it to the "Stock" ROM Slot instead.
Thanks again for the help, I learned a lot, and I am glad I didn't have to shell out money for a new phone. :laugh:
Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance
JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks
Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!
Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....
Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.
Hi,
I have a major issue since the update to CM13.0-20160524-NIGHTLY-huashan. I litteraly spent the whole week trying everything I found on internet in order to solve it without success.
My problem is the following one: I uninstalled the gapps to manually update it for the latest version of Android (Android 6.0.1), when I tried to boot to the recovery nothing happened the phone just restart, same when trying to boot to the bootloader. I tried everything adb reboot recovery adb reboot bootloader, I tried flashtool, I used the developper options to reboot to recovery, I tried manually by holding the volume button while restarting, I tried the flashify application. Nothing, I am not able in anyway to access neither the recovery nor the bootloader. The phone is just restarting, the led is first blue then goes red then green then red and restart. However, I have a root shell on the phone with adb shell.
If anyone have a solution, can help me please do it. An Android phone without the gapps is quite useless.
Thank you very much,
same problem,my phone is now without working android (after i tried instal CyanogenMod 13.0 Unofficial SaberMod.....still loading cyanogenmod logo) and without working fastboot and recovery so im lost :/
Hello, since the LED bar lights up this means your device is soft bricked, in which, mostly are recoverable.
What interests me is that you tried to, quote, "uninstall gapps".. If you previously have gapps, you don't need to "uninstall" gapps in order to update to the next build. Just flash the new build zip and gapps will be preserved. Also I am quite skeptical about what you did, as I never heard of a way to actually uninstall gapps. Basically if someone wants to remove gapps, he needs to format the System partition and then flash the ROM zip again..
Are you sure you failed to boot into flashmode? the correct procedure to do so is
Make sure the device is turned off
Make sure the USB cable is connected to your PC
Hold the volume DOWN button
Still holding the button, insert the USB cable to the XSP
LED will light up green, indicating flashmode
But even so, since you are on an unlocked bootloader, recovering from this brick is rather easy.
Get yourself a TWRP img file from the TWRP basketbuild folder
Open flashtool
Make sure the device is turned off
Make sure the USB cable is connected to your PC
Hold the volume UP button
Still holding the button, insert the USB cable to the XSP
LED will light up blue, indicating fastboot mode
On flashtool, click the lightning icon and select fastboot mode
On the right of the new window that appears, select "Select kernel to flash"
Navigate to your TWRP img file and select it
When flash completes, unplug your XSP from the USB cable
This will flash TWRP into /boot partition. So when you start your device, it will go straight to recovery.
Now, flash the ROM zip
Thanks for your help TechnoSparks, however, as I told you and expected even following your exact procedure my phone just restart. The led brights up bleu for few seconds then the phone put itself in charging mode. And when I said I delete the gapps, I meant that I deleted the google play store from my phone (this app was anyway not working after update). I tried to use flashtool but it is the same, can't get into fastboot mode, the phone just normally starts or put itself in charge. Isn't a manual solution on how to flash a recovery only using adb shell?
AresS31 said:
Thanks for your help TechnoSparks, however, as I told you and expected even following your exact procedure my phone just restart. The led brights up bleu for few seconds then the phone put itself in charging mode. And when I said I delete the gapps, I meant that I deleted the google play store from my phone (this app was anyway not working after update). I tried to use flashtool but it is the same, can't get into fastboot mode, the phone just normally starts or put itself in charge. Isn't a manual solution on how to flash a recovery only using adb shell?
Click to expand...
Click to collapse
That seems to be related to your USB cable (since that is the famous issue). Can you try to charge your phone WITHOUT it stop charging (i mean suddenly the LED disappears and when you tap the screen the charging icon doesnt show)?
If it so does happens that your device doesnt want to charge, it seems to me that you are having a loose USB port which possibly from your XSP, or, your USB cable is no longer up for the challenge
You will need to find another reliable USB cable for you to try. Try to charge your XSP to see if that particular USB cable is reliable for you. Try to wiggle the wire a little bit, moving the XSP from different directions and see if it would still charge. If it still charge, then this is the USB cable for you to use. Do the mentioned steps above again.
If you insist and want to use the same USB cable, you will need to find a "sweet spot" so that the connection between your XSP and the USB cable will remain reliable.
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
AvZPablo4 said:
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
Click to expand...
Click to collapse
You can use instead SPFT.
I used SP Flash Tool. I watched a YouTube tutorial:
I didn't had luck, It said me : PTM changed from the ROM; It must be downloader. Please select "Formato Allí + Download" scene and try again
It didn't work on Format All . It grave me this error: ERROR : STATUS_UNKNOWN_STORAGE_SECTION_TYPE (0xC003000C). [HINT]:
I tried to search solutions but nothing.
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
SubwayChamp said:
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
AvZPablo4 said:
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
Click to expand...
Click to collapse
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
SubwayChamp said:
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
Click to expand...
Click to collapse
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
AvZPablo4 said:
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
Click to expand...
Click to collapse
Windows not recognizing is normal in this state because your device is trying to boot to system, then Windows can't detect it as MTP BUT to have the device detected properly for preloader mode, you firstly have to install all the proper MediaTek drivers, then, from LibUSB entries listed choose one from all, i.e. Dispositivo Compuesto USB, it doesn't matter that it is the right entry, but this entry, if it is succesfully changed, would serve to recognize it, always that the VCom, and preloader drivers are properly installed.
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
AvZPablo4 said:
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
Click to expand...
Click to collapse
You have to keep pressed the buttons, even while the device is connected to the PC, your device will pass through various states, then quickly you have to release your fingers.
Well, preloader is a kind of bootloader, in MediaTek.
Use this tool, to bypass, https://androidfilehost.com/?fid=17825722713688275528 when you have success from the tool, then just run SPFT, uncheck the options LIB USB DA match storage and Storage Life Cycle, also check USB full speed.
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
AvZPablo4 said:
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
Click to expand...
Click to collapse
The tool is mirrored from other sites though https://gsmatoztool.com/mtk-auth-bypass-tool-v26-new-update-latest-tool/
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Also download the UsbDk 64-Bit installer from the site I linked, with mtk-client tool you also can do some things.
SubwayChamp said:
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Click to expand...
Click to collapse
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
AvZPablo4 said:
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
Click to expand...
Click to collapse
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
SubwayChamp said:
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
Click to expand...
Click to collapse
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
AvZPablo4 said:
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
Click to expand...
Click to collapse
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off, and interchanging the buttons.
SubwayChamp said:
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off.
Click to expand...
Click to collapse
I kept pressing vol up + vol down for like 10 min, but, nothing
AvZPablo4 said:
I kept pressing vol up + vol down for like 10 min, but, nothing
Click to expand...
Click to collapse
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
SubwayChamp said:
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
Click to expand...
Click to collapse
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
AvZPablo4 said:
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
Click to expand...
Click to collapse
Not much I can do. I recommended all the best to bypass this. If you have taken it in consideration, then you should sort it out.
- Uninstall all the drivers, reinstall exactly only what you need.
- Be sure that LibUSB is properly installed.
- Install the UsbDK 64 bits installer from the site I linked and try also the mtk-client tool.
- The option Format all except bootloader in SPFT may help, but consider that it may erase your calibration data and IMEI, mainly.