Related
Hi All,
I am having an issue with my S4 that when I plug them into my computer I get USB device not recognized. I have searched the forum for the past 2 days trying all kinds of different solutions the major one was changing my USB/charging port board on my phone.
I need to ODIN my device to an MJ7 image. At first I got the error and did a factory reset through safestrap recover. Still got the error so I did an advance wipe of every option. (Looking back shouldnt have done that) That took away my recovery, but I can get to download mode, but its not detected by my computer to use ODIN with. So I am stuck without a custom recovery without the ability to boot into anything.
Here is what I have tried so far:
1. Reinstall/uninstall drivers, reinstall/uninstall kies.
2. Changed USB ports on computer.
3. Changed USB cables
4. Changed computers from Win 8 x64 to Win 7 x64.
5. Changed computer to my MACbook using Heimdall.
6. Changed USB charging port board on my phone.
7. Tried everything again. *Still doesnt detect it*
Any ideas that I havent done already, or how to fix? I do have nandroid backup of my ROM, but dont have a custom recovery to flash it.
Cant ODIN back cause its not detected by my computer. Thanks in advance for your help.
Is USB debugging still checked on phone? You must use the USB cable provided with phone...
safestrap enabled, Hyperdrive driven
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
odlay75 said:
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
Click to expand...
Click to collapse
Tried Samsung Mobile phone drivers version 1.4.6.0 and still the same outcome "USB device not recognized". I went down to a local electronics store and bought two different brand microUSB data cables. Tried them both along with my original one from samsung, and still the same result. Any other ideas??
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
odlay75 said:
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
Click to expand...
Click to collapse
Go to Saferoot thread in dev forum...your answer may be there
safestrap enabled, Hyperdrive driven
Hey guys,
So I wanted to try out the newest CM12 ROM with A5.0 but seems like it didnt exactly happen how I wanted it. Rooting the device and then installing the XZDualRecovery without a problem. Then downloaded the ROM and gapps.
I have SGP311 (pollux_windy) so I downloaded that version of the CM12 at first. It said that my device is pollux, which I ofc was dumb enough to just skip and download the pollux ver and then install that one. So I installed the pollux ver instead of pollux_windy and when I hit restart device I didnt see it boot again.
So I wanted to connect it to my PC, PC didnt recognize it ofc. Only way my PC regonizes my tab is by fastboot mode. I had to install a driver for that. And even then only the Sony Mobile Flasher by Androxyde recognised it. I run into bootloop various times before with my tab and Emma always fixed it but thats unfortunately not the case here as Emma doesnt recognise it either :/
So now here's the problem, I can only do fastboot mode (not flashmode) and the only program able to do sth with my device is this Sony Mobile Flasher. I downloaded a official FW there and wanted to install it but it required me to go into the flashmode which I can't.
Is there sth I can do? The only thing working is the LED and fastboot mode.
Is there a way to put the device into flashmode via PC, that would solve all issues or maybe a trick to go into flashmode? As there was some thread about it but the thing they did didnt work for me :/
Please help
Thanks in advance
Nevermind, I just forgot how to use Emma....
For anyone to whom this happens:
Computer: Open Emma from the Start menu of your computer.
Connect a USB cable to your computer.
Phone: Turn off your tab.
Connect your tab to the USB cable while holding the VOLUME DOWN.
Computer: Select the software you want to flash in the Service list. The tool automatically detects the tab and lists available software versions, which are called Services in this flash tool.
Click on Apply Service. The tab will now be flashed.
Phone: When you have flashed your device, you can disconnect your phone from the computer. The first time you start your device after you have flashed it, the boot-up might take a little longer than normal.
Hi all,
by cons for several weeks I've a concern with my redmi Note 2 and I can't find the answer to my problem on the forum or even the Internet.
Since the last update 7.2.2 (global) I have the Recovery MIUI who crushed the TWRP. I changed to test 6.3.17. The update to the .24 went wrong and I don't know why. Since the phone is bootloop. But the problem is that my phone is not recognized by any PC. I tried several PCs, several cables, several drivers, with or without the Fastboot, unable to connect. Therefore impossible to load a new version. I don't think it's material problem because the phone recharge well with a cable to the socket.
Is there another handling or debug decision to restart the phone? I'm in France for information.
thank you in advance if you can point me to a solution !
Hope someone can help me.
Manu
Can the phone boot to miui recovery? If so, you should be able to use miui recovery to flash TWRP (I think you will need one with a signed install zip). You only need to take out the external SD, put it in one of those cheap USB card readers, copy your recovery and ROM to the SD, put it back in the phone, flash TWRP with miui recovery, and then flash the ROM with TWRP (I am assuming that miui recovery can install things from the external SD - if not, then none of this will work).
Hi Bro,
Yes it boot in MIUI recovery but impossible to get access to the SD Card...
I tried to put the file on the SD card but you can't choose the path, I think the recovery will look only in the internal memory ... And as I can't access the internal memory..
I despair !!
Thanks o lot for your help
DarthJabba9 said:
Can the phone boot to miui recovery? If so, you should be able to use miui recovery to flash TWRP (I think you will need one with a signed install zip). You only need to take out the external SD, put it in one of those cheap USB card readers, copy your recovery and ROM to the SD, put it back in the phone, flash TWRP with miui recovery, and then flash the ROM with TWRP (I am assuming that miui recovery can install things from the external SD - if not, then none of this will work).
Click to expand...
Click to collapse
manu33xtro said:
Hi Bro,
Yes it boot in MIUI recovery but impossible to get access to the SD Card...
I tried to put the file on the SD card but you can't choose the path, I think the recovery will look only in the internal memory ... And as I can't access the internal memory..
I despair !!
Thanks o lot for your help
Click to expand...
Click to collapse
Ok - but have you tried the Mediatek SP Flash Tool?
Of course yes but the real problem is that the phone is not recognized by the PC and therefore can't load anything ...
Even changing drivers or cables or PC, nothing to do.
DarthJabba9 said:
Ok - but have you tried the Mediatek SP Flash Tool?
Click to expand...
Click to collapse
manu33xtro said:
Of course yes but the real problem is that the phone is not recognized by the PC and therefore can't load anything ...
Even changing drivers or cables or PC, nothing to do.
Click to expand...
Click to collapse
So, when the battery is removed, and you connect the USB cable, the phone is not even vibrating (and making that weird sound) every couple of seconds or so?
Yes you're right : every 10s the phone vibrate...
DarthJabba9 said:
So, when the battery is removed, and you connect the USB cable, the phone is not even vibrating (and making that weird sound) every couple of seconds or so?
Click to expand...
Click to collapse
manu33xtro said:
Yes you're right : every 10s the phone vibrate...
Click to expand...
Click to collapse
Well, then it is very strange that you can't use the SP Flash Tool. If the phone vibrates, then the device is recognised, and you should be able to flash anything you want with the SP Flash Tool! How exactly were you trying to use the Flash Tool?
I tried so many solutions I really don't know exactly how I used the software.
I will again try everything.
But against any changes when I look in the USB settings of the PC, the phone doesn't appear.
I try again just now, thank you for your help.
DarthJabba9 said:
Well, then it is very strange that you can't use the SP Flash Tool. If the phone vibrates, then the device is recognised, and you should be able to flash anything you want with the SP Flash Tool! How exactly were you trying to use the Flash Tool?
Click to expand...
Click to collapse
manu33xtro said:
I tried so many solutions I really don't know exactly how I used the software.
I will again try everything.
But against any changes when I look in the USB settings of the PC, the phone doesn't appear.
I try again just now, thank you for your help.
Click to expand...
Click to collapse
With the SP Flash Tool, all you need is the correct "scatter" file (MT6795_Android_scatter.txt), and the image(s) that you want to flash. If the phone is vibrating, then the SP Flash Tool should be able to connect to it when you click "Download". Just make sure that you first untick everything that you do NOT want to flash. I would try flashing the boot image (boot.img) first. If that succeeds, then try the TWRP recovery image.
Ok. I'm going to try again with "http://en.miui.com/forum.php?mod=viewthread&tid=196175&highlight=sp%2Btool%2Bflash%2Bredmi%2Bnote%2B2"
DarthJabba9 said:
With the SP Flash Tool, all you need is the correct "scatter" file (MT6795_Android_scatter.txt), and the image(s) that you want to flash. If the phone is vibrating, then the SP Flash Tool should be able to connect to it when you click "Download". Just make sure that you first untick everything that you do NOT want to flash. I would try flashing the boot image (boot.img) first. If that succeeds, then try the TWRP recovery image.
Click to expand...
Click to collapse
Well... Install again drivers MTK but nothing... The phone vibrates well but the PC still doesn't see ... It's late now, I look again tomorrow night.
Thanks again.
manu33xtro said:
Ok. I'm going to try again with "http://en.miui.com/forum.php?mod=viewthread&tid=196175&highlight=sp%2Btool%2Bflash%2Bredmi%2Bnote%2B2"
Click to expand...
Click to collapse
manu33xtro said:
Well... Install again drivers MTK but nothing... The phone vibrates well but the PC still doesn't see ... It's late now, I look again tomorrow night.
Thanks again.
Click to expand...
Click to collapse
Perhaps you might want to describe what exactly happens when do you what exactly?
Hi,
Ok that's what I do with an old PC with Win XP.
- install media Tek USB VCOM drivers for Win XP -> installation complete
- launch SP Flash Tool with administrator rights)
- use scatter file from Redmi Note 2 rom
- use download agent "MTK_AllInOne_DA.bin"
- press download button
- connect phone with UCB cable and waiting... and waiting...
- and I can't see it in device manager !
No way again !
I will try again...
DarthJabba9 said:
Perhaps you might want to describe what exactly happens when do you what exactly?
Click to expand...
Click to collapse
manu33xtro said:
Hi,
Ok that's what I do with an old PC with Win XP.
- install media Tek USB VCOM drivers for Win XP -> installation complete
- launch SP Flash Tool with administrator rights)
- use scatter file from Redmi Note 2 rom
- use download agent "MTK_AllInOne_DA.bin"
- press download button
- connect phone with UCB cable and waiting... and waiting...
- and I can't see it in device manager !
No way again !
I will try again...
Click to expand...
Click to collapse
Strange! I am assuming that when you connect the phone with the USB cable, the battery has been removed from the phone? If so, then it should work.
Perhaps you should try first connecting the phone, and then waiting until it has vibrated once or twice, before clicking the "Download" button?
Yes I removed battery before connect the phone to PC. I tried also with battery and nothing changed.
I even changed the cable to be sure.
Which seems to me most strange is that I see nothing in the device manager, as if the phone wasn't connected. Whatever the installed driver is the same result. I think it should at least have the phone on the COM or USB port ...
I will try again this night to be sure with all steps one by one. And I will also try with ACER tablet I and runs Android 5.1. Maybe it will be recognized.
Otherwise I also tried to pass a Linux PC as a last resort.
Thanks again for your help.
DarthJabba9 said:
Strange! I am assuming that when you connect the phone with the USB cable, the battery has been removed from the phone? If so, then it should work.
Perhaps you should try first connecting the phone, and then waiting until it has vibrated once or twice, before clicking the "Download" button?
Click to expand...
Click to collapse
manu33xtro said:
Yes I removed battery before connect the phone to PC. I tried also with battery and nothing changed.
I even changed the cable to be sure.
Which seems to me most strange is that I see nothing in the device manager, as if the phone wasn't connected. Whatever the installed driver is the same result. I think it should at least have the phone on the COM or USB port ...
Click to expand...
Click to collapse
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Hum good question. In fact I don't know. I'll ask the MIUI forum.
I got home late from work so I don't do tests tonight, I'd see it all tomorrow including the connection with my tablet ...
Thanks
DarthJabba9 said:
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Click to expand...
Click to collapse
Hi,
I tried to connect with an Acer Tablet with Android 5.1.1 but nothing appends...
I tried also with a Linux PC (Debian) and if I can see a Samsung A3 phone dirrectly, no way for my Redmi Note 2...
There really I despair : I think I can't access any of the phone. Can't do anything !
If you have any other solution but you help me a lot already, and thanks for that.
Can be a micro crack on the USB plug into the phone if it's not a software problem ... Let's go for it apart and look at this ...
Thanks again bro.
Manu
DarthJabba9 said:
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Click to expand...
Click to collapse
manu33xtro said:
Hi,
I tried to connect with an Acer Tablet with Android 5.1.1 but nothing appends...
I tried also with a Linux PC (Debian) and if I can see a Samsung A3 phone dirrectly, no way for my Redmi Note 2...
There really I despair : I think I can't access any of the phone. Can't do anything !
If you have any other solution but you help me a lot already, and thanks for that.
Can be a micro crack on the USB plug into the phone if it's not a software problem ... Let's go for it apart and look at this ...
Thanks again bro.
Manu
Click to expand...
Click to collapse
I don't think it is a crack on the USB plug. It seems to me to be a low-level driver problem - ie, the drivers on the phone that are active when the phone is not (fully) booted up. I don't have the right terminology for these drivers, but they are possibly part of the bootloader. If that is the problem, then I don't know how you would solve this problem.
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive:
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.